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

      • E.g. 2: France Operation in Financial Accounting:
        • 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 




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

5. Remove the icon(s) when not applicable


References

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

KS01


Forms

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


Attachments

8. Add the link to attachments or external links

Cost Center - Master Data



I update/lock an internal order for restructuring and HSE costs << >> I update/block a cost center



1. Objective and Scope

1.1. Objective of this Operation

WHY - Describe the objective of the operation 

(to complete)(error)

1.2. Scope

Detail the scope (legal entities, etc.)

(to complete)(error)

2. Definitions

See Finance Glossary:


3. Tasks description

3.1. I receive the request to create a cost center

3.1.1. Step 1 of Task 1

3.1.2. Step 2 of Task 1

...

3.2. I confirm that the request is made by an authorized requester

Check that the requester is an “authorized requested” in document “LIST OF CO MASTER DATA STAKEHOLDERS”.

This list is maintained by the Process Expert Costing assigned to Data Management.

Besides this list, Reporting (different from “PIF level”) as well as some “auxiliary” cost centers can be requested by the RtR (change RtR)(error) Country Manager or the CAM. It is also applicable for small companies that do not have a Controller.

3.3. I analyze and validate the information provided in the request

3.3.1. I take charge of the request

Make sure it includes the template in its latest release:

3.3.2. I validate that all mandatory fields are informed


3.3.3. I validate the need of a new cost center

Validate that the need behind the request is a cost center, and cannot be fulfilled with another cost object (project (=WBS), internal order, …).

Validate that the need cannot be fulfilled with an existing cost center.


A cost object (and thus a cost center) must be “single” in SAP : 

  • unique codification
  • unique description (both short and long) and object within a plant.

An asset must be linked to a cost center. Thus no other cost object can be used when an asset in involved.

Payroll accounting is based on cost centers. Thus no other cost object can be used when payroll is involved.


Analyze answers to the following questions :

  • Purpose of the requested Cost Center?
  • Requested Cost object to be used for asset or payroll ? If yes, it validates the need of creating a cost center as a cost object.
  • Requested Cost object only to report costs linked to a project ? If yes, a WBS should be suggested.
  • Yearly foreseen amount > threshold defined by PE Costing ? The amount entered gives 2 types of information :
    • It impacts the degree of urgency with which the action is required : a significant amount means the request should probably be processed before next closing.
    • In case of a non-significant amount, we should challenge the creation of a cost center, and suggest an internal order as a cost object.
  • Check in SAP : no pre-existing Cost Center to fulfill the need ? Check for the existence of a compatible C.C. in the same plant. 
    • Use KS13 to display similar cost centers

3.3.4. I perform the controls



3.3.5. I challenge the creation of the cost center

“Return” the workflow request with your comment:

  • suggesting another cost object, 
  • suggesting an existing cost center, 
  • informing that his/her need does not seem a cost center
  • asking for further information.

If mandatory information is missing, or inconsistency is found:  ask for further information. 

3.4. I create the new cost center


3.5. I communicate that a new cost center has been created

I notify the Assessment Cycle Owner maintenance

I notify the requester

End of document.