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 SBS-Finance approval workflow
Responsibility area:
Table of contents
Scope
ERP
Frequency
References
Forms
US - 7424 - Process Orders Variance IECRA Template
Attachments
<< US - 7424 - Process Orders Variance Cycle >>
1. Objective and Scope
1.1. Objective of this Operation
The objective of this document is to give the instructions to do the process orders cycle update and execution related to cost center cccc-9201.
With this, it will avoid FI-CO differences.
This procedure needs to be done on D-1 or D+2 and it takes the data for the current period.
The process orders variances need to be assessed to P&L in D45 by CO-PA cycle.
1.2. Scope
It applies to company 7424, cost center 7424-9201 and cycle 742492.
2. Definitions
See Finance Glossary:
3. Tasks description
3.1. I Retrieve the Data
3.1.1. I check the cost center
Enter in KSB1 and take the variant 7424PPvariance with the below parameters:
*remember to change the posting date when selecting the variant.
controlling area = Z028
cost center = 7424-9201
posting date = from first to last day of the closing month
layout = /PPvariance
After execution, see the Reference Procedure field:
COBK = cycle execution (it will appear after some steps forward of this procedure);
MKPF = process orders variance (this needs to be assessed by the cycle);
The objective is to net 0 the sum of both ref. procedures together after the cycle execution.
The layout is not considering the Reference Procedure AUAK that means the process orders settlement, which we will not take in consideration for this procedure.
3.1.2. I check the materials IECRA
To be able to update the cycle, we need to get the correct value by IECRA.
To do that, take the materials and plants and check their IECRA in transaction ZWFAI052.
Now you are able to get the IECRA value from MKPF Reference Procedure.
You can use the template US - 7424 - Process Orders Variance IECRA Template to put the data and get the correct value per IECRA or use another excel if you prefer.
The objective here is to get the correct number per IECRA based on the material and plant in MKPF Reference Procedure in the cost center.
3.2. I Update and Execute the Cycle
3.2.1. I Update the Cycle
When you get the values per IECRA, enter in KEU2:
cycle = 742492
start date = first day for the year of the closing
Enter in segment 7424-9201 by:
and double click in the segment 7424-9201:
Click in Receiver Tracing Factor and include the same amount with the same signal from SAP you have per IECRA:
*you can pagedown to change the page with more IECRA if necessary;
After input all amounts, the total needs to be the same from MKPF Reference Procedure in the cost center:
If correct, save it.
3.2.2. I Execute the Cycle
Enter in transaction KEU5 and include:
period = month of closing;
Fiscal year = year of closing
unflag test run;
cycle = 742492;
start date = first day for the year of the closing;
enter;
Execute. Check if no errors appeared in the results, warning is ok:
3.3. I Check the Result
3.3.1. I Check the Cost Center Result
Enter again in KSB1 with variant 7424PPvariance.
*remember to change the posting date when selecting the variant.
Check if the MKPF and COBK Reference Procedure are netting 0 as below:
If it is netting 0, it is correct. If not, you need to analyze what is the cause (maybe the signal inserted in the cycle or something did wrong).
After that, no FI-CO will appear for this type of difference.