Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Hide If
groupconfluence-users

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 Finance approval workflow 


Panel
bgColor#F7F7F7
titleColor#ffffff
borderWidth1
borderStylenone
Domain: Management Accounting, Costing
Panel
bgColor#F7F7F7
borderWidth1
borderStylenone

Responsibility area:

Table of contents 

Table of Contents
maxLevel2


Panel
borderStylenone
Scope


ERP

WP2


Frequency

 

References



Forms



Attachments


 

 

<<

Page_title
>>



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, the inventory movements, and reallocation of cost center for inventory consumptions, and activity type absorptions match in WPX and WP2.

This is the manual process to validate differences between the systems. Now we use ZCO_RECON in WPX to perform these checks automatically. 

Embedded Google Drive File
docid1uMjXG6hRjwOEmvJL1pxp-xAHDTIkx6WaFGxgXC7Kdus

1.2. Scope

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


2. Definitions

See Finance Glossary:


3. Tasks description

3.1. I run the cost center and KE30 report to check FI/COPA reconciliation in WPX for process order settlements.

3.1.1. I run transaction S_ALR_87013611. Update the controlling area, the year, the period, and the cost center “7180-9201”.

The cost center report should match value fields E05, D05, and F05 on the KE30 report. (same as normal reconciliation in WP2 currently)

3.1.2. I run transaction KE30. Select report “ZZZ-SOLV00”. Update the reporting currency, fiscal year, periods, and company code.

Add D05, E05, F05 together.

3.1.3. I compare both results to confirm that they match. 

If the amounts do not match I take corresponding corrective action to analyze which process order is causing the discrepancy. If a COPA correction is needed this needs to occur in both WP1/WPX as D05, E05, F05 has been transferred from WPX to WP2 post process order settlements.

3.2. I check that the activity absorption ties out in both systems. 

WP1

WP2

3.2.1. I run transaction S_ALR_87013611. Update the controlling area, the year, the period, and the cost centers “7180-9201, 7180-8899, and 7180-6199”. 

WPX

3.2.2. I run transaction S_ALR_87013611. Update the controlling area, the year, the period, and the cost center group “7180”.

3.2.3. I compare the results in both systems to confirm that they match.

If they do not match I analyze the reason of the discrepancy and take corresponding corrective action. 

3.2.4. I run transaction ZWFA04 in WPX in test mode to see what activities have not been transferred. Then rerun the transaction in live mode to execute the transfer.

 If there is an issue due to the reclassification of the R&I/Engineering manual adjustment will be made in WP1.

3.3. I check the production and consumption of materials in both systems.

WP1

WP2

3.3.1. I run transaction MB51. Update the plant(s), posting date, username, and use flat list as the display option.

Execute the transaction. Variant should show posting date, material, plant, movement type, quantity, base unit, unit of entry, amount in local currency, batch, and user name.

Export the report to Excel and analyze the information based on movement type and material.

WPX

3.3.2. I run transaction MB51. Update the plant(s), movement types (select all excluding 501 and 502), posting date, and use flat list as the display option.

Execute the transaction. Variant should show posting date, material, plant, movement type, quantity, base unit, unit of entry, amount in local currency, batch, user name, and order.

Export the report to Excel and analyze the information based on movement type and material.

3.3.3. I compare the quantities and amounts in local currency to confirm if they match. 

If they do not match I analyze the reason of the discrepancy and take corresponding corrective action. 

3.3.4. I determine the differences by material and batch.

If the quantities match, but there is a discrepancy in the actual amounts then there is an issue with the materials and manual adjustments to the orders will need to be made. If the order is TECO then adjustments must be made to COPA and if the orders are REL then adjustments must be made to WIP.

If we determine an issue with price change I find the order quantity to calculate the order adjustment by multiplying the quantity by the price discrepancy. 

3.3.5. I create corresponding journal entries/COPA adjustments in WP2/WPX accordingly.


3.4. I confirm now that the systems reconcile. CCCC-9201 needs to be exact in both systems to finalize the closing.

End of document.

Viewtracker
hidetrue
 

Hide If
groupconfluence-users

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 Finance approval workflow 


Panel
bgColor#F7F7F7
titleColor#ffffff
borderWidth1
borderStylenone
Domain: Management Accounting, Costing
Panel
bgColor#F7F7F7
borderWidth1
borderStylenone

Responsibility area:

Table of contents 

Table of Contents
maxLevel2


Panel
borderStylenone
Scope


ERP


Frequency

 

References



Forms



Attachments


 

 

<<

Page_title
>>



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, the inventory movements, and reallocation of cost center for inventory consumptions, and activity type absorptions match in WPX and WP2.

The reconciliation is performed using the program ZCO_RECON in WPX to perform the checks automatically.
This is the manual process to validate differences between the systems in case the automatic program is not working or not available.

Embedded Google Drive File
docid1uMjXG6hRjwOEmvJL1pxp-xAHDTIkx6WaFGxgXC7Kdus

1.2. Scope

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


2. Definitions

See Finance Glossary:


3. Tasks description

3.1. I run the cost center and KE30 report to check FI/COPA reconciliation in WPX for process order settlements.

3.1.1. I run transaction S_ALR_87013611. Update the controlling area, the year, the period, and the cost center “CCCC-9201”.

The cost center report should match value fields E05, D05, and F05 on the KE30 report. (same as normal reconciliation in WP1 currently)

3.1.2. I run transaction KE30. Select report “ZZZ-SOLV00”. Update the reporting currency, fiscal year, periods, and company code.

Add D05, E05, F05 together.

3.1.3. I compare both results to confirm that they match. 

If the amounts do not match I take corresponding corrective action to analyze which process order is causing the discrepancy. If a COPA correction is needed this needs to occur in both WP1/WPX as D05, E05, F05 has been transferred from WPX to WP2 post process order settlements.

3.2. I check that the activity absorption ties out in both systems. 

WP2

3.2.1. I run transaction S_ALR_87013611. Update the controlling area, the year, the period, and the cost centers “CCCC-9201, CCCC-8899, and CCCC-6199”. 

WPX

3.2.2. I run transaction S_ALR_87013611. Update the controlling area, the year, the period, and the cost center group “7180”.

3.2.3. I compare the results in both systems to confirm that they match.

If they do not match I analyze the reason of the discrepancy and take corresponding corrective action. 

3.2.4. I run transaction ZWFA04 in WPX in test mode to see what activities have not been transferred. Then rerun the transaction in live mode to execute the transfer.

 If there is an issue due to the reclassification of the R&I/Engineering manual adjustment will be made in WP2.

3.3. I check the production and consumption of materials in both systems.

WP1

WP2

3.3.1. I run transaction MB51. Update the plant(s), posting date, username, and use flat list as the display option.

Execute the transaction. Variant should show posting date, material, plant, movement type, quantity, base unit, unit of entry, amount in local currency, batch, and user name.

Export the report to Excel and analyze the information based on movement type and material.

WPX

3.3.2. I run transaction MB51. Update the plant(s), movement types (select all excluding 501 and 502), posting date, and use flat list as the display option.

Execute the transaction. Variant should show posting date, material, plant, movement type, quantity, base unit, unit of entry, amount in local currency, batch, user name, and order.

Export the report to Excel and analyze the information based on movement type and material.

3.3.3. I compare the quantities and amounts in local currency to confirm if they match. 

If they do not match I analyze the reason of the discrepancy and take corresponding corrective action. 

3.3.4. I determine the differences by material and batch.

If the quantities match, but there is a discrepancy in the actual amounts then there is an issue with the materials and manual adjustments to the orders will need to be made. If the order is TECO then adjustments must be made to COPA and if the orders are REL then adjustments must be made to WIP.

If we determine an issue with price change I find the order quantity to calculate the order adjustment by multiplying the quantity by the price discrepancy. 

3.3.5. I create corresponding journal entries/COPA adjustments in WP2/WPX accordingly.


3.4. I confirm now that the systems reconcile. CCCC-9201 needs to be exact in both systems to finalize the closing.

End of document.

Viewtracker
hidetrue