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 Form name



Attachments

8. Add the link to attachments or external links




Previous operation << >> Next operation



1. Objective and Scope

1.1. Objective of this Operation

The main purpose of this procedure is to check the netback Join Ventures sales.

D1

1.2. Scope

4290 and 4291


2. Definitions

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

See Finance Glossary:

  • NAM


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.

Select the level of heading in the "Paragraph" option.

3.1. I do the JV sales invoice check

3.1.1. Updating the report attached


Receiving an e-mail from supply chain department with following information with it we can starting completing the template attached.

In this report you will updated all the cells in blue, starting on the date in the line 2, the price per STN (netback sales) line A10 is adjusted after each quarterly (controller will provide this information), with the e-mail information you can complete the line D32 (PO number) and D35 ( delivery number).


The section 1 and 2 you need to open the purchase order on ME23N.


Transaction ME23N - Good receipt posted in 4290


Transaction ME23N - Good issue posted in 4291


The section 3 and 4 display the invoice on VF03.


The last section is to save the documents number as a support, on the vendor account FBL1N according to instruction in blue in the file.

 

3.1.2. I check if there is some difference 


After complete the figures instructed above revise the netback is correct in column M line 48 the result of formula needs to be the same netback on the column A10 and in the column M69 if shows a higher difference the controller needs to be informed it means that the billing to Asahi is not 20% of the total.

...

3.2. I do something...

3.2.1. Step 1 of Task 2 (I do something...)

3.2.2. Step 2 of Task 2 (I do something...)

...


End of document.