SAP Note 19188 - Allocation: Tracing factor based on external table

Symptom:

1. You implemented Note 319913. However, significant performance problems continue to occur due to inefficient master data determination in the allocation processor during the FI-SL or NewGL allocation with tracing factor 'Fixed percentages' or 'Fixed portions'.

2. The receiving tracing factor should not be defined in the allocation definition, but rather externally, for example, in an EXCEL file.

A separate SAP table containing the relevant tracing factors is available for both problems.
(Before using this table, check that you have actually implemented Note 319913 and that this has not improved performance). The table enables you to reduce the performance problems described in point 1 because the master data is checked more quickly. The table also enables you to solve the problem mentioned in point 2, for example, by loading the data from the EXCEL file into the SAP table.

The following steps should only be performed by a person who is very familiar with the FI-SL application or NewGL.

Other terms

Allocation, performance

Reason and Prerequisites

See the symptoms described above.

Solution

Example:
Set costs of a business area have to be distributed among other business areas and cost centres in a specific relationship.
The sender dimension is RBUSA; the receiver dimensions are RBUSA and RCNTR.

Steps to be performed:

1. Create the table ZZVT (can also have a different name) in the ABAP Dictionary.

The table must have the following structure:
Key fields: ZZDISTKEY (this is the distribution key,
used later for distribution. It can also have a different name).
RBUSA
RCNTR (or all fields that are to be assessed or distributed).

Important: The distribution fields (RBUSA and RCNTR in this case) must have exactly the same name as in the summary table.
Data field: VALUE (must have this name)
You must maintain this table later (for example, using transaction SM31 or SE16).
The allocation determines the tracing factors from this table.
Example:
ZZDISTKEY RBUSA RCNTR VALUE
1 10 4711 30
1 20 4712 70
2 10 4711 40
2 20 4712 60

-> There are two distribution keys (1 and 2); a 30 to 70 distribution takes place in one distribution key, and a 40 to 60 distribution takes place in the other.

2. Use transaction GCIN to add a new field ZZDISTKEY at the end of your summary and line item tables.

3. Add this field in the data field definition for the allocation (table T811H) (Configuration menu:

FI-SL -> Periodic Processing -> Allocation ->
Special Functions -> Data Fields).
Enter the following data on the detail screen:

Table name ZZEXT
Data field ZZDISTKEY

Group 1 Group 2
Table ZZVT
Value field MSL000

In addition, enter text for the data field ZZDISTKEY (for example, Distribution Key for Costs).

4. Add a field to the field group definition.

(Table T811J)
(Configuration menu: FI-SL -> Periodic Processing -> Allocation ->
Special Functions -> Field Groups Assessment/Distribution).

Enter the following data on the detail screen:

Table ZZEXT (name of summary table)
Allocation type V Distribution
Actual/Planned I Actual
Field group ZZDISTKEY Distribution key

Processing
Internal Update Recommended tracing factor 10

Everything else can remain initial.

5. Add the field ZZDISTKEY to the field usage for allocation

(Configuration menu: FI-GLX -> Periodic Processing -> Allocation ->
Field Usage for Assessment or Distribution).
Set the following indicator on the detail screen:

FIELD USAGE IN THE ALLOCATION.
Control Single value

Receiver tracing factor: x x

Everything else can remain initial.

6. Enter the table ZZVT in T800A.

Type = AL, everything else can remain initial.

7. Start report RGZZGLUX to regenerate the FI-SL programs.

Start the program only when nobody is working in the production system, otherwise data can go missing.

8. When you maintain the allocation, you must select your field group for tracing factor field group (PF4 on the field).

You can enter a distribution key of your choice (for example, 1) in the field ZZDISTKEY for the tracing factor selection criteria.

9. Start the relevant allocation.

SAP must note at this point that this solution is also valid for allocations in NewGL.