Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
KALC (Package) Cost Accounting allocations RK-S
Basic Data
| Data Element | NORMFLAG |
| Short Description | Ind. for negative tracing factor |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | FLAG | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Neg.TrFact |
| Medium | 15 | Scale neg.TrFac |
| Long | 20 | Scale neg.trac.fact. |
| Heading | 1 | S |
Documentation
Definition
Indicator controlling whether negative tracing factors occurring in the receivers are scaled or not.
Use
Negative tracing factors occur if the tracing factors are derived from the database instead of defined as fixed values or percentages. This could be the case for distributions according to activity types or statistical key figures.
A particular problem arises if some receivers have positive tracing factors and others have negative tracing factors. If the negative values are not scaled, then not only the sender is credited. Receivers with negative values are also credited and receivers with positive tracing factors are debited by a larger amount.
Example:
Sender S1 distributes 1000.- to receivers R1 and R2.
Tracing factor, R1: 100
Tracing factor, R2: -90.
The sender base is the sum of the tracing factors, 10.
R1 receives 1000 X 100 / 10 = 10,000.-
R2 receives 1000 * -90 / 10 = -9000.-
R2 credits 9000 based on the R1 costs.
Iterative processing can result in errors if the integration does not converge, and therefore ends or supplies incorrect data.
Scaling functions as follows:
1. Scales the tracing factor with the lowest value to 0
2. Increases the other tracing factors accordingly
In the example, then:
1. The tracing factor for R2 is scaled to 0
2. The tracing factor for R1 is raised from 90 to 190
Sender S1 credits the balance to R1. R2 is neither debited nor credited.
Procedure
If you set the indicator "Negative tracing factor" in the cycle header data, this serves as a default value for segments you create for the cycle. You can overwrite the value during segment definition of the tracing factors. The indicator set in the the segment tracing factors is always valid.
History
| Last changed by/on | SAP | 20130529 |
| SAP Release Created in |
