Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Panel
bgColor#F7F7F7
titleColor#ffffff
borderWidth1
borderStylenone
Domain: Finance Data & Reporting SU Management Accounting
Panel
bgColor#F7F7F7
borderWidth1
borderStylenone

Responsibility area: Maintain Costing Master Data

Table of contents 

Table of Contents
maxLevel2


Panel
borderStylenone
Scope

ERP

Image RemovedImage RemovedImage AddedImage Added

Frequency

References

KA06 - Create a secondary cost element

Cost element - Master Data

Forms

Attachments

Cost element - Master Data


I receive a request to create a secondary cost element >> 
Page_title
>> I maintain cost element hierarchies

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 secondary cost element element category is 21, 42 or 43

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

  • In
PF1
  • PF2 =
 
  • 98xxxxxxxx
  • In
WP1
  • WP2 = 99xxxxxx
The detailed codification rules is in Rules - Cost element Codification

The creation of new secondary cost elements should be done in very limited cases. Usually it is done in the frame of a project when a new process is set-up and requires the creation of a new cost element


Note
titleException

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


The best way to check the last secondary cost element created is to go to Tcode KA03 >> search in tab "N: Cost element" by 99422* or 99432* in WP2 (or 92* in PF2).

Image Added

Check the last number between the specific range.


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

All entities in WP1& PF1In PF2 (Controlling Area: CHEF) & WP2 (Controlling Areas: Z006, Z013, Z025, Z026 and Z028)

2. Definitions

See Finance - Glossary

3. Tasks description

3.1. I

record

create the secondary cost element

Include Page
KA06 - Create a secondary cost element
KA06 - Create a secondary cost element


Note

As a best practice, in WP2 each secondary cost element should be replicated in the 5 controlling areas (Z006, Z013, Z025, Z026 and Z028).


Warning

Once the new cost element is created it must be included in all core cost elements groups (XCS-ALL, ZRCS-FC  & ZSOLV). 

In WP2, the new secondary cost elements only need to be included in ONE controlling area (the other controlling areas will be automatically updated).

I maintain cost element hierarchies

3.2. I check the set of accounts where the cost element should be included

Most of the secondary cost elements are created as reference from another already existing in the system.

Therefore, we should check the sets of accounts where the secondary cost element used as reference, is included.


Go to tcode GS03 and then select "Utilities" >>> "Find values in sets"

Image Added


Select variant "DATA TEAM" and insert the secondary cost element.

After execute.

You should compare the output report of the reference secondary cot element with the one that we have created.


In WP2 :                                                                                                            

Image Added                    Image Added


In PF2 :

Image Added                 Image Added



 3.3. I communicate that a new secondary cost element has been created

I notify the requester.


Viewtracker
hidetrue