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 



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

Uni



ERP

4. Remove the icon(s) when not applicable

PF2


Frequency

5. Remove the icon(s) when not applicable


 

 

References

6. Add the link to SAP transaction(s) (when it exists)



Forms

KE28 Template



Attachments

8. Add the link to attachments or external links


 

 

Previous operation << >> Next operation



. Objective and Scope

1.1. Objective of this Operation

  • COPA Top-down distribution (tcode KE28 or KE28A) is a periodic function that lets you distribute the aggregated data (sum up of the original COPA records) to more detailed levels on the basis of reference information.           

    • The original COPA record can be any record type if relevant, like B type (from shipment cost for example), D type (from cost center assessment)... 

    • The distribution reference can be the posting figure of any COPA value field, as long as the records fall into the same group (defined by ‘Copy’ characteristic, to be explained later).   

  • Generally speaking, when execute KE28, it post a reversal record against original records (after sum up), then post several split records for each combination according to reference ratio.   

 

1.2. Scope

This procedure is just performed on company code 4290 and 6401.


2. Definitions

See Finance Glossary:


3. Tasks description

We Have two main steps on this procedure, the first one is to calculate the cycles allocation and the second on is to run the transaction KE28A


3.1. I update the template

 

3.1.1. I open the monthly template and extract the data


With the template opened I'm going to start to extracting the SAP data.

I execute the Macro in tab "Read me first" - Extraction All. If needed data can be extracted individually. 



In case the Macro has an error, to extract manually follow the steps below:

KE24 - Variant: /KE28 - period: closure period - layout: /KE28-4290


Extract the data and paste values on tab " SAP KE24 database " 

 

For SD Derivatives Div 47 we need to extract the information separately but I going to follow the same as I performed above;

 

KE24 - Variant: /KE287470- period: closure period - layout: /KE28-7470


Extract the data and paste values on tab " KE24 database - Mileage (7470)

Make a filter to see line items just for plant GRU

For Derivatives only chipping condition 21 and "blank" should be considered to GRU plant.

You need to exclude the line items which has no follow this rule:



After that I extract the data from KSB1:

TPT cost center line items

Variant: TPT 4290

Extract data and paste values on tab " SAP TPT KSB1 "


OUTPUT= Once you fill in the orange tabs, the blue ones will be updated for further checking.




3.1.2. I do the checks


3.1.2.1 I check tabs  


I check if there is any difference between the Total of the Pivot table and Total Division AD / A1 / A3 / AO.


If there is any difference, check in transaction KE30 following the steps below:

KE30 - report CHEOPS CONTROL

Division: AD / A1 / A3 / AO



Add plant on the SAP report and check if the qty by plant is the same as distributed in the table of % allocations. 



OBS: Usually there is a difference for 5S00 plant. Go to Profit center details of plant 5B00 and check the amount for PC F25MKXXX92


Now, I need to update the cycle;

CYCLE: 6401RO

Cost center: 5S46100001

2 Segments: 5S461-C412 // 5S461-C402


CYCLE: 6401RO

Cost center: 5S46100002// 5S46100003 // 5S46100004



3.1.2.3 I check tab 


I update the pivot tables and verify if there is any check field with amount, if everything is correct any amount will reflect there.

For some cost centers the allocation information will be sent by the controller Ross Dorsett through ticket with the subject 4290 Peroxide COPA Throughput allocations.

I can see which are those cost center by the information Check Ross* file on tab Tpt cost centers.

 

After that I need to update the cycle.

CYCLE: 4290TP and 6401TP

Cost center: All cost centers on this tab

Segments: The segments name are the same of cost center coding.


3.1.2.4 I check tab 


We receive the information from Leticia Souza. She sends the Fleet file with the information for TPT Assessments

Ticket subject: "6401 *Month* Year - Fleet Process Assessment"

Update pivot tables;

 

After that I need to update the cycle.

CYCLE: 6401TP


For Division 25:

Cost center: 5S19600040

2 Segments: TPT SEA  // TPT-ALL SD


For Division 47

Cost Center: 5S19600041 // 5S19600042 // 5S19600043 // 5S19600044


3.2. I run the cycles

After finish everything on template and with the cycles updated I need to run the cycles;


Transaction KEU5;

Cycles: 6401RO and 6401TP (in this order) - The cycles must be ran before cycle 6401RP and cycles 4290TP and 4290RP to company 4290.

3.3. I execute KE28A

Execute actual distribution → after the cycles are run


3.2.1. I run transaction KE28A in test mode.

Variant: KE28-4290

Flag: Execute Actual Distribution

Period: Closing Period


I need to run first in test mode


 

3.2.2. I Check the log

Transaction KE28L

Include the closing period and the KE28A variant as below:

Run;

I need to verify on Log tab, Currency type 10;


I use transaction KE30 report ZZZ-SOLV00  to check if there is sales to those materials/plants;


Run;


Is there is no QRU information, any distribution needs to be done;



If I have no information of material, I can use the combination of Plant, Division and Profit Center:


KE30;

After check all variants, I can run it on real mode.


3.2.3. I run transaction KE28A on real mode.

First of all I need to check if the period is open;

Transaction: /FIN3/OKP1_BK - Maintain period lock (with CoCode) 


To open the period the current month should be unflagged;

 

Now, Just go back to KE28A and unflagging the test option and run;


To be sure that the transaction ran to correctly, verify if there is the cancel option on KE28L for each variant as below:


3.2.4. I send the confirmation to controllers.

 

With everything finished, I send the confirmation to responsible evolved that the process was ran with template attached to all controllers from 4290;


End of document.