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

WHY - Describe the objective of the operation

The goal of this operation is to guarantee that, at the end of each month, we have no differences between WPX and WP1 systems.

This is the process that include preliminary checks and step by step procedures to make sure there are no differences between the systems.

1.2. Scope

Detail the scope (legal entities, etc.)

This procedure is applied to Composites entities with ITAR materials (7180, 7771, 7772)

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

Balance cost center 7180-9201/7771-9201/7772-9201 in both systems

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 preliminary Checks During the month:

Run tcode ZCO_RECON in WPX:

this check will capture activity hours differences as they arise due to system transferring issues.


Before proceeding to reconciliation below steps have to be completed first:

  1. Calculation of Process Orders Variances tcode KKS1 have to be run in both systems
  2. Process Orders Settlement tcode CO88 have to be run in both systems
  3. Transfer of Process orders COPA postings to WP1 tcode ZWFA03A
  4. Check COPA postings tie in WP1/WPX tkode KE30 - cost center 7180-9201 in WPX should match D05+E05+F05 under KE30 report in both systems.

3.1.1. I proceed with WIP Process

I run tcode ZWFAA07 in both systems

  1. First check if KOC4 balance in WPX matches to WIP balance in WPX, if not include unbalanced orders into WIP calculation.
  2. Calculate WIP differences between the systems and post WIP entry in WP1.
  3. KOC4 Balance in WP1 should have zero balance, if not identify unsettled orders and settle manually via tcode KO88 in WP1.

3.1.2. I run ZCO_RECON report to check if there are any activity hours discrepancies and post manual entry via tcode KB1N

Once the entry is posted I check cost center report in both systems: S_ALR_87013611


I check plant by plant activity hours as they should match in both systems.

3.2. I run ZCO_RECON report for Consumption/Production Differences

Post entry in WP1, please note it's always a reversing entry.

3.2.1. I post the final reconciling entry between the systems if under a certain treshold.

Final reconciling entry is also a reversing entry.

Check on cost center report to make sure cost center 7180-9201/7771-9201/7772-9201 has the same balance.

The final entry that is posted in WP1 will also fix FI-CO difference that falls under the category "PO Difference".

End of document.