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: 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


Frequency

5. Remove the icon(s) when not applicable

 

 

 

References

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



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




Previous OP << >> Next OP



1. Objective and Scope

1.1. Objective of this Operation

The purpose of KE27 is to generate new COGS delta entry in COPA for each sales order according to periodic unit price calculated by CKMLCP. Only after this transaction we will have a correct reconciliation between FI and COPA for COGS.


1.2. Scope

Finance Operations:

  1. Run the transaction to see the respective differences in COGS between FI and COPA.
  2. Analyze the origin of the differences.
  3. Correct the differences according to the respective origin.

2. Definitions

Definitions should be added in the Finance Glossary - Add definition and link it to respective Letter in Finance Glossary 

See Finance Glossary:

3. Tasks description

3.1. I run the revaluation of COGS in COPA


3.1.1. Step 1 of Task 1


 


End of document.