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 Finance approval workflow 


Domain: 1. Enter the Domain identified in OPD matrix (for Country specific operations, Domain = Country Accounting)

Responsibility area: 2. Enter the responsibility area described in OPD matrix ("N/A" for Country Accounting Operations)

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

PF2 / WP2


Frequency

5. Remove the icon(s) when not applicable

 

References

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

MM01 & MM03

Transaction MM17


Forms

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



Attachments

8. Add the link to attachments or external links


 

 

Previous operation << >> Next operation



 Objective and Scope

1.1. Objective of this Operation

The Origin group aggregates the materials by product family.

The Origin Group is a very critical field for the Integrated Manufacturing & Energy Performance report and it should be updated in order to give a better and more consistent split of the product family in the production costs analysis.

1.2. Scope

All PF2 and WP2 entities.


2. Definitions

See Finance Glossary:

  • SU MAC - Service Unit Management Accounting
  • FICO views - Accounting and Costing Material views


3. Tasks description


Material Origin Group will be a mandatory field to update in the Material Master Data.

In order to do that, the Site controller should fulfill the FICO Template (Link here) with the respective origin group whenever Accounting and Costing views are needed.

Please be aware that the FICO views are under SU MAC- Data Management team responsibility. The Creation of a new Origin group is under IS Team scope.


Below are the flow of the activities to be performed by the Site controllers.


3.1. I verify the origin group code to assign to the material

3.1.1. I review the material description

     Check the material description, by accessing transaction MM03.

            

  •  The corresponding origin group should be aligned with the material description.

3.1.2. I verify the origin group codes available in the system 

      Check the existing origin groups , by accessing transaction MM03.

      In case it is a new material without costing views, just access any existing material.

               


                   or use transaction Z1K_CHECKMAT (PF2 only):

                  


 By searching for "key words", the system will show the already existing Origin groups:

                



3.1.2. I determine the origin group code according to the GBU guidelines


    • If Material Origin Group pretended already exists, go to section 3.3.
      • If so, then use this group Code


    • If no Group code exists, a new Origin Group is required
      • Review with GBU industrial controller for guidance (could be new product line) and follow section 3.2.  
      • After confirmation of new Group name, , apply section 3.3.


3.2. I request the creation of a new origin group 


        Request New Origin Group through Service One (as shown below) with the Information of the new Origin Group code + Description required.

                 > Financial Services > IT - Controlling (CO) / IT- Asset/ IFRS16 / IT- Intercompany

              


Then, DT Team will handle your request. Please provide to IS Team the new 4 digit code and respective description, considering the existing codification. For WP2, it is also need to inform which controlling areas should be considered (Z001, Z006, Z013, Z025, Z026 and Z028).


3.3. I request to update the origin group of the material


       Request to insert Origin Group must be done through Service One, using the category below, with the information required filled

              > Financial Services > Finance Data > Material Management - Accounting and costing views > Request information about Material Accounting and Costing (FICO) Views

              


  •  If the FICO views are already created and it is just required to update the origin group, fill the template accordingly:

                            Type of Request: Modification

                            Add the Source System + Material code + Plant + Origin Group (Column AE)

                       

  • So, if it is a new material, without the FICO views created yet, then you just need to fill the template as usual (support documentation) and add the information of the respective origin group:

                         Type of Request: Creation


      Then, SUMAC - Data Management Team will handle your request.

             

In some cases, the material already exists for a long time, but it is not possible to assign a grouping if the material does not have a costing view set up. 

The Controller needs to determine if it is a critical material and request the creation of FICO views.