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

Country Accounting


ERP

4. Remove the icon(s) when not applicable



Frequency

5. Remove the icon(s) when not applicable

Monthly

   

 

References

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

KOB1


Forms

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

7424 - Chemplex Order Settlement


Attachments

8. Add the link to attachments or external links




Previous operation << >> Next operation



1. Objective and Scope

1.1. Objective of this Operation

WHY - Describe the objective of the operation

The objective of the procedure is to settle the Chemplex orders to account 57000400. As this account needs to be posted with flow F20 for credits and F30 for debits, it is not possible to do it in normal settlement.

Due to it, we need to post the reclass simulating the settlement removing from the orders to the account 57000400.


This need to be done on D+1 morning.

1.2. Scope

Detail the scope (legal entities, etc.)

This procedure applies for 6402 company code.

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

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 Retrieve the Data

3.1.1. I Check the Orders

The orders to be checked is generally OG-CHEM-INS (for insurance).

Enter in transaction KOB1 with variant CHEMPLEXSETTLE with below parameters:


Controlling Area: Z028

Order: US-CHEM-INS

Posting Date: first to last day of the closing month

Layout: /ChemplexSet


Execute.

See the result. If there are values, you need to proceed further.


3.1.2. I Create the Posting File

Download the template 7424 - Chemplex Order Settlement of the posting file and you need to update the following fields in tab "Template".

  • When doing the posting, certify to take each cost element for the order side as it is simulating the order settlement (don't do it with all cost elements together).


Company Code: 6402;

Header Text: the code or the orders;

Doc. Date and Posting date: last day of the closing month;

Posting Key: 40 for debit and 50 for credit;

GL Account: Take it from KOB1 and the counter part will be always 57000400;

Amount: Take it from KOB1;

Value Date: same as posting date;

CO Order: Order that you are removing the value;

Assignment: OGNR;

Text: Order that you are removing the value;

Transaction Type: use F20 or F30 (F20 = increase = posting key 50 credit as it is liability account / F30 = decrease = posting key 40 debit);



*Do not forget to run controls after populating the fields and check if everything is ok in tab "Posting File";


In the Justification tab, you can include the screenshot of the KOB1 for each item.


Post it.


3.2. I Check the Results

3.2.1. I check if the orders are balanced

After the posting, check the the orders balance if there is 0. To do that, you can repeat step 3.1.1.

3.2.1. I check the account 57000400 flow

Enter in FBL3N with parameters below and check the field "Transaction Type" if there is something against signal:

F20 or F30 (F20 = increase = posting key 50 credit as it is liability account / F30 = decrease = posting key 40 debit);


FBL3N

GL Account: 57000400

Company Code: 6402

All Items: first to last day of the closing month


If there is something wrong, you need to reclass to correct transaction type and verify who posted the document to advise the person to post correctly.

End of document.