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
- 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)
- Labels to be used: country_accounting, france, financial_accounting
- E.g. 1: WW Operation in Financial Accounting under domain "Central Finance Processes & Compliance":
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
Responsibility area:
1. Objective and Scope
1.1. Objective of this Operation
The goal of this operation is to guarantee that, at the end of each month, we have no differences between WPX and WP2 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
This procedure is applied to Composites entities with ITAR materials (7180, 7771, 7772)
2. Definitions
See Finance Glossary:
- ...
3. Tasks description
Balance cost center 7180-9201/7771-9201/7772-9201 in both systems
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:
- Calculation of Process Orders Variances tcode KKS1 have to be run in both systems
- Process Orders Settlement tcode CO88 have to be run in both systems
- Transfer of Process orders COPA postings to WP1 tcode ZWFA03A
- Check COPA postings tie in WP2/WPX tcode 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
- First check if KOC4 balance in WPX matches to WIP balance in WPX, if not include unbalanced orders into WIP calculation.
- Calculate WIP differences between the systems and post WIP entry in WP2.
- KOC4 Balance in WP2 should have zero balance, if not identify unsettled orders and settle manually via tcode KO88 in WP2.
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 WP2, 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 WP2 will also fix FI-CO difference that falls under the category "PO Difference".


