SAP BLOG Top Down Distribution in Account based COPA

SAP Blog

Kayıtlı Üye
Katılım
22 Ara 2017
Mesajlar
1,671
Tepki puanı
7
Puanları
6
From this blog post, you will learn the following about the Top-down distribution (TDD) in Account-based COPA. The blog is intended for CO consultants, Business users, etc. This blog discussed the functionality of Top-down distribution in Account-based COPA. TDD is a functionality that is quite complex due to the nature of distribution which can be based on different characteristics. TDD forms as a critical month-end process in management accounting to have P&L breakdown at the maximum granularity.



Content –


  • Introduction to Top-down Distribution
  • SAP TDD variant Setup
  • Characteristic Processing Action
  • Selection Criteria
  • TDD execution results



What is Top-Down Distribution

Top-down distribution is functionality in COPA, by which the P&L item can be distributed to the finer level details characteristics values set or market segments. Financial posting arising through direct posting, order settlement, COPA assessment like – expense, freight, or sometimes discount does not carry all the relevant COPA characteristics. During the reporting, these items do not contribute due to the absence of the relevant characteristics values. Top-down distribution helps in distributing these lines item to a detail level of the characteristics values set while retaining the once which is already coming from the posting.

For a Top-down distribution to work we need below

  1. Actual Data/ Source data – This is the actual data, which has only the limited characteristics set like a discount, freight posting, etc.
  2. Reference Data – This is the data which have the details characteristics values which form as the basis of the distribution
  3. Distribution key – This the parameter on which the data gets distributed, this could be for example – transaction figures in local currency in the reference line items

Example –

Below is the actual data from ACDOCA which is posted to a generic characteristic value like company code, controlling area, Plant, functional area.

Note – I have kept the profit center & segment as intentionally blank.

Actual Data – Discount
GL AccountCom CodCon AreaPlantFunc AreaProf CenSegment$ valueProf Seg
41003000ABCD1001120
41003000ABCD2001120



Below is the reference data from ACDOCA which will serve as the reference for the distribution of the actual data.

Here we can observe some important points

  • There are some characteristics that are the same as the actual data like company code, controlling area, plant, etc. It is logical to say, here that when we distribute the source data, we want them to be copied as it.
  • There are characteristics like functional area, profit center& segment that are different from that of source/actual data. ( actual data have a profit center & segment as blank). Again logically, as these are part of the FI characteristics it should be copied over from the actual data. So we expect TDD result to have these fields as blank
  • There is a characteristic division, which is a reference characteristic from the material master.it would get derived during the posting. We can see it for the material TG22 & SP006 but only material -TG22 has the division for SP006 it has been put manually during the posting. For these characteristics, we would logically ask COPA derivation to work and make the posting correct in case of incorrect values put during the reference data postings.

1-13.png




  • The final two characteristics Material group & Product are the key here, as we would like to see the discount distributed on these two characteristics. These characteristics are distributed
Reference Data
GL AccountCom CodCon AreaPlantFunc ArProf CenSegDivisionMaterial groupProduct$ value
41000000ABCEYB101S1 00L001TG22-500
41000000ABCEYB102S2 00L004SP006-700
41000000ABCEYB103S3YBPM01SP004-900



Distribution key

The $ values posted on the reference data act as a tracing factor for the distribution. The value on the source data is distributed to these characteristics set in the appropriate ratio.

Here for example – The source data have two-line items, which are posted on the same prof segment, therefore, it will be summarized, and the total value is 300$. This 300$ is distributed to the material group and Production combination in the ration of 5:7:9.

So, the outcome of the TDD should be as below –



TDD Output
GL AccountCom CodCon AreaPlantFunc ArProf CenSegDivisionMaterial groupProduct$ value
41003000ABCD300
41003000ABCD-300
41003000ABCD00L001TG2271.42857
41003000ABCDL004SP006100
41003000ABCDYBPM01SP004128.5714



Important Observations –

  • The Actual data is reversed at the prof segment level, we can see it being summarized.
  • Characteristics like company code, controlling area, plant, the functional area got copied
  • FI related characteristics like Func area, prof center, segment got copied by default
  • Division characteristics got rederived & corrected the incorrect posting on the reference data due to derivation.
  • Material group & Product combination receive the 300 in the ration of 5:7:9

L001 + TG22 à -(500)/-(500+700+900) *300 = 71.42
L004 + SP006 à -(700)/-(500+700+900) *300 = 100
YBPM01 + SP004 à -(900)/ -(500+700+900) *300 =128.57



SAP TDD variant Setup

  1. We need to specify the period for the actual and reference data
  2. The reference base need to be single v/f
  3. Click on Processing instruction

1-15.png




Characteristic Processing Action

We can set up the below characteristics action in TDD
1. Copy – We use this action for the characteristics which we want to carry over to the TDD result from the source posting ex-company code, controlling area, plant

2. Sum – We use this action for the characteristics, which we want to be derived in the TDD results
ex – Division, custom characteristics

3. Distribution – We use this action for the characteristics on which we want to distribute the data
ex- Product, Material group, etc.



1-16.png




Selection criteria

Selection criteria help in selecting the sender/Actual data and the reference data. This help in better performance of the TDD run, as only a selected number of profitability segment, would be selected for the distribution and for the distribution key calculation.
Ex- We can restrict the sender and reference data based on the cost element

We can use * to represent all selection & # for blank selection.

1-18.png


1-17.png




TDD execution results

Source data & reference data

3-9.png


TDD Log

4-11.png


TDD Results

5-6.png




Reference

2236046 – S/4 HANA Finance: Processing instructions in KE28 in account-based CO-PA

Okumaya devam et...
 
Üst