| group | confluence-users |
|---|
Tasks to be completed when documenting an operation (from creation to publication)
1. Enter the Title of the operation / page
2. Add the following Labels :
Scope of applicability: ww, country_accounting
Country or group of countries (if applicable): belux, china, france, italy, lam, nam, uk_ie, bulgaria, dach, netherlands, iberia, poland, latvia, australia, india, japan, south_korea, thailand, singapore, new_zealand, emea_transversal, apac_transversal
Unit and Domain according to the List of labels to be used in the Finance Service Line space
E.g. 1: WW Operation in Financial Accounting under domain "Central Finance Processes & Compliance":Labels to be used: ww, financial_accounting, central_fin_proc_compliance
- Labels to be used: country_accounting, france, financial_accounting
(for country operations, the Domain is always country_accounting)
3. Fill in all fields as described above
4. Name the title of each section using OPD methodology naming convention - Infinitive verb without the “to”, mainly action verb...something) - " I do something..."
5. Once the description of the operation is completed, ensure it is approved and published by launching the SBS-Finance approval workflow
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
| Domain: Finance Data & Reporting SU Management Accounting |
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Responsibility area: Maintain Costing Master Data |
Table of contents
| Table of Contents | ||
|---|---|---|
|
| Panel | ||
|---|---|---|
| ||
ScopeERP(to be confirmed!) Frequency (to be filled) ReferencesKA06 Cost element - Master Data(to be confirmed!) FormsAttachments
|
1. Objective and Scope
1.1. Objective of this Operation
1.2. Scope
2. Definitions
See Finance Glossary:
- ...
3. Tasks description
WHAT and HOW - Main content of the operation
The content should be mainly organized in 2 levels of Headings to ensure a proper link with the Table of Contents.
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 secondary cost element category is 21, 42 or 43
The codification of a secondary cost element depends on the system:
- In PF2 = 98xxxxxxxx
- In WP2 = 99xxxxxx
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 | ||
|---|---|---|
| ||
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:
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).
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: |
1.2. Scope
In PF2 (Controlling Area: CHEF) & WP2 (Controlling Areas: Z006, Z013, Z025, Z026 and Z028)
2. Definitions
3. Tasks description
Select the level of heading in the "Paragraph" option.3.1. I
recordcreate the secondary cost element
3.1.1. Step 1 of Task 1
3.1.2. Step 2 of Task 1
...
| Include Page | ||||
|---|---|---|---|---|
|
| 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 & 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). |
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"
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 :
In PF2 :
3.3. I
3.2. Icommunicate that a new secondary cost element has been created
3.2.1. Step 1 of Task 2
3.2.2. Step 2 of Task 2
End of documentI notify the requester.
| Viewtracker | ||
|---|---|---|
|