| 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 |
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Responsibility area: Maintain Costing Master Data |
Table of contents
| Table of Contents | ||
|---|---|---|
|
| Panel | ||
|---|---|---|
| ||
ScopeERPFrequencyReferencesFormsAttachmentsProfit Center - Master DataPrevious OP <<AttachmentsTemplate Profit Center creation
|
1. Objective and Scope
1.1. Objective of this Operation
(to complete)
The purpose of this document is to describe the process of creating a profit center.
1.2. Scope
(to complete)This document applies to all the processes of creating a profit center.
2. Definitions
See Finance - Glossary:
...3. Tasks description
3.1.
II receive the request to create a profit center
I receive a request to create a new profit center.
3.2.
II confirm that the request is made by an authorized requester
Only authorized requesters should be able to ask for data.
In the case of Costing master data, which is the case of the profit center, usually it's a GBU/function Controller.
Check that the requester is an “authorized requester” in document
| Google Drive Live Link | ||
|---|---|---|
|
This list is maintained by the Process Expert Costing assigned to Data Management.
3.3.
II analyze and validate the information provided in the request
I check that the profit center that needs to be created follows these rules:
| Include Page | ||||
|---|---|---|---|---|
|
3.4.
II create the profit center
| Include Page | ||||
|---|---|---|---|---|
|
3.4.1. I transfer the new group of profit center and new profit center in MDG
All new profit center groups and new profit center created have to be transferred from PF2 & WP2 to MDG system (Profit center D* and F* only for PF2).
| Expand | ||
|---|---|---|
| ||
Execute
|
| Expand | ||
|---|---|---|
| ||
And execute
You will have a message validate:
New message , validate:
|
3.4.2. I replicate the newly created profit center into the other active controlling areas (only applicable in WP2 and EXCEPT for GBUs CBS and NBD):
In WP2, since we can not restrict the usage of the profit center to a certain controlling area, it is recommended that whenever creating a new profit center in a certain controlling area, it's also extended to the VPART nodes in the other active controlling areas (EXCEPT for GBUs CBS and NBD).
It's common that some intercompany processes occur between companies operating in different controlling areas, where the origin profit center is taken in the several subsequent steps in the other controlling area.
In order to avoid blocking this particular processes or generating assignments to dummy profit centers (Example: Z006-9999 in controlling area Z006), it's better to have all the profit centers available in all the active controlling areas.
You can find the VPART nodes in each profit center hierarchy at the bottom of the list:
There's only one VPART node per GBU. You should create the required VPART profit center by copy from the one created in the main controlling area and just change the related profit center group parameter, so it gets properly assigned to the VPART nodes and not in any other controlling area nodes.
For example, if we create a profit center in controlling area Z006, we need to create it in the other controlling areas (Z013, Z025, Z026 and Z028) inside the VPART node related to the GBU of the profit center created in CoA Z006.
| Info | ||
|---|---|---|
| ||
Name Should be the "BFC GBU code + 00" + "hyphen" + "GBU descrip" (example "CM00 - Comp Mater") Long Text Should be the "BFC GBU code + 00" + "hyphen" + "GBU description" + "hyphen" + "VPART" (example "CM00 - Composite Materials - VPART") Person Responsible Should be the GBU name:
Department If the profit center is created at company level:
If the profit center is created at plant level:
Profit Center Group Should be the last node of the VPART node related to the GBU (example: "Z028-VP079" - CGUVP079 CM Partners profit centers) |
Example of profit center 8347-P1253 -> Profit center created in controlling area Z006 and extended to VPART nodes in other controlling areas:
3.4.3. I check that newly created profit center's IECRA and ENTRP codes are properly assigned in tables ZWFAT111 and ZWFAT113 (only applicable in WP2):
- In table ZWFAT111, you should ensure that the IECRA code linked to the newly profit center created is properly assigned, ensuring that the link between the IECRA and the BFC activity 1 code/market is set accordingly for the related company code.
- In table ZWFAT113, you should ensure that the ENTRP code linked to the IECRA of the newly profit center created is properly assigned, ensuring that the link between the ENTRP code and the GBU code is set accordingly for the related company code.
3.5.
I communicate that a new profit center has been created
I notify the requester.
End of document.
| Viewtracker | ||
|---|---|---|
|