Ansicht
Dokumentation
FINS_ALLOC_TMPL - Define Template for Top-Down Distribution
SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up General Material DataThis documentation is copyright by SAP AG.
Allows you to define the template for top-down distribution
In Margin Analysis, sales revenues, sales deductions, and costs of goods manufactured are generally stored at the customer and/or product level. However, many business transactions, for example - freight invoices, insurance expenses, or advertising, cannot easily be assigned to such a detailed level. Therefore, they need to be posted at a summarized level, such as the division, sales organization, or company code level.
Top-down distribution is a periodic function that lets you distribute this aggregated data to a more detailed level based on reference information (such as sales revenues from the same period).
In this Customizing activity, you define the top-down distribution template which controls how each characteristic is used and processed in top-down distribution. Later, it is used in cycle definition in universal allocation. It determines which Margin Analysis fields are shown on different tabs of the segment definition. It also influences the processing logic during top-down distribution.
- Allocation context (for the moment) is Margin Analysis by default
- Enter a template name
- Enter operating concern for the template
- Enter description for the template
- Enter tolerance setting if necessary
In top-down distribution, the sender data is distributed according to ratio calculated from reference data. It could happen that the corresponding ratios of some line items are extremely small among all reference line items. Therefore, the distributed result contains a very small value, for example 0.01, which is not meaningful for reporting. Tolerance setting can be used to filter out the unnecessary distribution result which contains small value, so that the data volume from the distribution result can be reduced.
- By default, a few frequently used characteristics are listed.
- You can remove characteristics through the 'Delete Characteristics' button.
- You can add additional characteristics through the 'Add More Characteristics' button.
- Choose a characteristic category for each characteristic.
- Retained and Relevant to Reference
- Characteristic set as this category is used for sender data and reference data selection.
- During distribution, this field is used to link sender data to corresponding reference data.
- In the distribution result, the value of this field is retained as it is in sender.
- Retained but Irrelevant to Reference
- Characteristic set as this category is used for sender data and reference data selection.
- During distribution, this field is not used to link sender data to the corresponding reference data.
- After distribution, the value in this field is retained in the distribution result as it is in the sender.
- You should choose this category if you want more characteristic values retained in the distribution result.
Note: Data volume will be increased in the distribution result.
- Summarized
- Characteristic set as this category is used for sender data and reference data selection.
- After sender data and reference data are selected, the value in this field is cleaned up. So, the corresponding sender data and reference data will be summarized.
- In the distribution result, the value of this field will be empty. However, if the derivation logic is defined, the value will be filled from derivation.
Note: You should choose this category if you want to keep limited dimensions in the distribution result to avoid large data volume.
- Distributed:
- Characteristic set as this category is the detailed dimension you want to do the distribution. Value is always initial in sender data.
- The field is only used for reference data selection.
- In the distribution result, the value of this field is filled from the corresponding reference data.
If you don’t want characteristics which are set as “Retained and Relevant to Reference” or “Retained but Irrelevant to Reference” or ‘Summarized’ to be shown on the UI as selection criteria, you can mark the flag 'Hidden on UI'. In this case, the fields will not be shown in the segment. However, the controls of the characteristics will remain.
In top-down distribution, key figures (such as amount, or quantity) of reference data are used as variable portion type to calculate ratio for sender data distribution.
By default, below key figures are available as variable portion type in allocation. You can choose one of them during the cycle definition.
- HSL - Amount in Company Code Currency
- KSL - Amount in Global Currency
- TSL - Amount in Transaction Currency
- MSL - Quantity
- Please be aware that Plan Quantity cannot be set as ‘Variable Portion Type' in the TDD cycle definition. This field does not exist in the ACDOP table.
- VMSL - Valuation Quantity
It is important that all accounting document line items should have the same unit of measurement for the chosen key figure. Otherwise, the calculated ratio is inaccurate. It is suggested to use HSL, KSL, or VMSL.
Distribute freight cost from ‘Product Group’ to ‘Product’ according to sales revenue from each product. According to different configuration of top-down distribution templates, they are largely different.
| Line | Product Group | Product | Distribution Channel | Freight Cost | |
|---|---|---|---|---|---|
| 1 | PG1 | A | 300 | ||
| 2 | PG1 | B | 600 |
| Line | Product Group | Product | Distribution Channel | Sales Revenue | |
|---|---|---|---|---|---|
| 1 | PG1 | P1 | A | 1000 | |
| 2 | PG1 | P2 | A | 1500 | |
| 3 | PG1 | P2 | B | 500 | |
| 3 | PG1 | P2 | C | 1000 |
| Characteristics | Field Category | |
|---|---|---|
| Product Group | Retained and Relevant to Reference | |
| Product | Distributed | |
| Distribution Channel Summarized | ||
| Line | Product Group | Product | Distribution Channel | Freight Cost | |
|---|---|---|---|---|---|
| 1 | PG1 | 900 |
| Line | Product Group | Product | Distribution Channel | Sales Revenue | |
|---|---|---|---|---|---|
| 1 | PG1 | P1 | 1000 | ||
| 2 | PG1 | P2 | 3000 |
| Line | Product Group | Product | Distribution Channel | Freight Cost | |
|---|---|---|---|---|---|
| 1 | PG1 | P1 | 225 | ||
| 2 | PG1 | P2 | 675 |
| Characteristics | Field Category | ||
|---|---|---|---|
| Product Group | Retained and Relevant to Reference | ||
| Product | Distributed | ||
| Distribution Channel | Retained and Relevant to Reference |
| Line | Product Group | Product | Distribution Channel | Freight Cost | |
|---|---|---|---|---|---|
| 1 | PG1 | A | 300 | ||
| 2 | PG1 | B | 600 |
| Line | Product Group | Product | Distribution Channel | Sales Revenue | |
|---|---|---|---|---|---|
| 1 | PG1 | P1 | A | 1000 | |
| 2 | PG1 | P2 | A | 1500 | |
| 3 | PG1 | P2 | B | 500 |
| Line | Product Group | Product | Distribution Channel | Freight Cost | |
|---|---|---|---|---|---|
| 1 | PG1 | P1 | A | 120 | |
| 2 | PG1 | P2 | A | 180 | |
| 3 | PG1 | P2 | B | 600 |
| Characteristics | Field Category | |
|---|---|---|
| Product Group | Retained and Relevant to Reference | |
| Product | Distributed | |
| Distribution Channel | Retained and Irrelevant to Reference |
| Line | Product Group | Product | Distribution Channel | Freight Cost | |
|---|---|---|---|---|---|
| 1 | PG1 | A | 300 | ||
| 2 | PG1 | B | 600 |
| Line | Product Group | Product | Distribution Channel | Sales Revenue | |
|---|---|---|---|---|---|
| 1 | PG1 | P1 | A | 1000 | |
| 2 | PG1 | P2 | A | 1500 | |
| 3 | PG1 | P2 | B | 500 | |
| 3 | PG1 | P2 | C | 1000 |
Please note that the distribution channel doesn’t have to be the same between sender and reference, so it is ignored in the reference data.
| Line | Product Group | Product | Distribution Channel | Sales Revenue | |
|---|---|---|---|---|---|
| 1 | PG1 | P1 | 1000 | ||
| 2 | PG1 | P2 | 3000 |
| Line | Product Group | Product | Distribution Channel | Freight Cost | |
|---|---|---|---|---|---|
| 1 | PG1 | P1 | A | 75 | |
| 2 | PG1 | P2 | A | 225 | |
| 3 | PG1 | P1 | B | 150 | |
| 3 | PG1 | P2 | B | 450 |
