Domain: Finance Data & Reporting

Responsibility area: Maintain Costing Master Data

Table of contents 

By default the table of contents displays Heading 1 & Heading 2 (other levels can be added)


Scope

3. Remove the icon when not applicable

ERP

4. Remove the icon(s) when not applicable

Frequency

References

6. Add the link to SAP transaction(s) (when it exists)

KA02 - Change a cost element

Forms

7. Insert the links accordingly and change the link text with the OP name

Attachments

Cost element - Master Data


xx >>  >> xx

1. Objective and Scope

1.1. Objective of this Operation

A secondary cost element represents postings that occur between controlling objects within CO and from CO to COPA. A secondary cost element is essentially an account that exists only in the CO module, not in FI. When costs are moved (e.g., from one cost center to another using an assessment, or from a cost center to a production order), no postings are made in FI. 

The seconday cost element category is 21, 42 or 43

The codification of a secondary cost element depends on the system: 

  • In PF1 = 98xxxxxxxx
  • In WP1 = 99xxxxxx

Once the cost element is created, the update of secondary cost element is done in very limited cases. 


Certain secondary cost elements are designated for Lump Sum invoicing, each with a specific coding structure.

The codification depends on the system and it is related to a specific range:

  • In PF2: 9200000000 until 9200009999
  • In WP2:  if cost element category is 42 (which is most of the times) the range should be : 99422700 until 99422999; if cost element category is 43 the range should be : 99432700 until 99432999

Requests related to this should be initiated by the Intercompany Team.


For more information about this process, please refer to the following link:
Optimic Project and OPTIMIC Master data requirement

1.2. Scope

In PF2 (Controlling Area: CHEF) & WP2 (Controlling Areas: Z006, Z013, Z025, Z026 and Z028)

2. Definitions

See Finance - Glossary

3. Tasks description

3.1. I perform the secondary cost element changes


3.2. I communicate a secondary cost element has been updated

I notify the requester.