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: Costing

Responsibility area: Ensure Costing Allocations

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)

KSU5 KEU5 KSV5; KSV5; KEU5


Forms

IFRS16 Scheme



Attachments

8. Add the link to attachments or external links

Assessment cycles - PF1

Assessment cycles - WP1

Distribution cycles - PF1

Distribution cycles - WP1

COPA cycles - PF1

COPA cycles - WP1



Previous OP << >> I check that cost centers are balanced





1. Objective and Scope

1.1. Objective of this Operation

The objective of this operation is to guarantee that all costs posted in Cost Centers are allocated correctly to the final PL of the respective company.

1.2. Scope

This procedure is applied to all companies WW.


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

3.1. I verify that the previous dependent steps have been performed

  • Monthly postings
  • Orders and WBS settlement

3.2. I guarantee that IFRS16 Cost Centers will be properly allocated

Go to FBL3N and select variant “CHECK IFRS16”. Update the field company code and the end-date, and execute it.

Note:

  • If you are doing the D-2 check and you only have Cost-Centers that already had costs in previous months of the one that you are closing, then We can assume that the cost-center has the correct allocation and the check ends here
  • If you have a Cost-Center with costs for the first time in the month that you are closing continue following the steps below


Check which new CCtrs have line items for the first time in this month – in the example below, we have CCtr T717400000 appearing for the first time in September, so for this CCtr we need to make a specific analysis to see if the amounts from IFRS16 are being allocated correctly (the other ones, we assume were already corrected in the previous closures when they appeared for the first time):

It's necessary to check how this specific CC is being allocated to COPA and to guarantee that the part of the amount that relates to IFRS16 is being allocated to the correct PL headings. To do so, follow this scheme.


Note:

After the cycles run we can confirm if the amount was correctly allocated according to the scheme mentioned above.

In order to do it, go to KE24 and select variant "CHECK IFRS16". This variant and respective layout are already selecting the necessary ValueFields and Cost Elements that relate to IFRS16. So we should find here the same amount as in FBL3N:


In this case, we have the 5,786 k€ correctly reported in COPA, as well as the 918,351 k€. However, there is 1 amount of 7,768 k€ which is missing in COPA. What actions should be taken?

1) Find the origin cost center(s) in FBL3N which is causing the difference .

2) Review the scheme of the cycle's allocation for that specific cost center to make sure that this amount will be correctly reported in the coming months.

3) Make a COPA correction in order to correct the cumulated amount, decreasing the amount from it was wrongly allocated and adding it in the correct value field + cost element.


Important: It's not mandatory to have the amount in FBL3N and COPA linked to the same Cost Center. Due to the cycles allocation, several times we have different CC associated. The important thing is to check if the value in the origin (FBL3N) matches with the one in COPA (KE24).


NOTE FOR THE ANALYSIS: One good report to analyze these differences is S_ALR_87013635 with variant "CHECK_IFRS16" (update company code + periods). This report shows the original IFRS16 movements + respective IFRS16 allocations for each CC so, if something is not correctly allocated, the CC will not be at zero:



While making this analysis, please pay attention to the following:

a) All gaps between FBL3N and KE24 should appear here, if they are related to CC (which is around 95% of the situations). If your gap is not here, it means that it's coming from WBS or Orders' allocation.

b) If there was any COPA correction made to correct past amounts, everything will be OK between FBL3N and KE24, anyway the gap will still appear here (because the correction was done on COPA side, and not on the CC line items). This means that we need to pay extra care when analyzing these gaps, and make sure that there was no correction already performed in COPA, otherwise we will double the amounts.


3.3. I perform the cost center allocation (for Distribution, Assessment and CO-PA)


 Click on the option below according to the type of Cycle.

 

 

 


End of document.