Hierarchy
⤷ 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 | RRULE_RLV |
Short Description | Receiver rule for indirect activity allocation |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | RRULE_RLV | |
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 | Rule |
Medium | 15 | Rule |
Long | 20 | Rule |
Heading | 1 | R |
Documentation
Definition
Controls how receiver tracing factors are determined.
Use
You have the following options:
- Variable portions
The tracing factors are computed automatically by reading the totals record file. You define the criteria by which this data is accessed on the tracing factor tab page.
Example
Sender A distributes 100 production hours to three receivers. The tracing factors are the actual costs
Receiver Cost Elem Amount
B 430000 2000 USD
C 430000 1000 USD
D 430000 2000 USD
Total 5000 USD
The SAP System calculates the following values:
Receiver B: 100 production hours/5000 X 2000 = 40 prod.hours
Receiver C: 100 production hours/5000 X 1000 = 20 prod.hours
Receiver D: 100 production hours/5000 X 2000 = 40 prod.hours
With the function Receiver weighting factors in segment maintenance, additional receiver-specific weighting factores for receiver tracing factors can be stored in variable receiver factors.
The system proposes a default value of 1 (no decimal place).
The system calculates the sender base from the sum of the individually weighted receiver tracing factors.
Example:
Sender A distributes $100,000 to three receivers with the following tracing factors:
Receiver B: 50 portions Receiver weighting factor: 1
Receiver C: 50 portions Receiver weighting factor: 9
Receiver D: 100 portions Receiver weighting factor: 5
This results in the following tracing factors used for allocation:
Receiver B: 50 portions X 1 = 50
Receiver C: 50 portions X 9 = 450
Receiver D: 100 portions X 5 = 500
Total: 1000 portions
The SAP system calculates the following values:
Receiver B: 100,000 $/1000 X 50 = $5,000
Receiver C: 100,000 $/1000 X 450 = $45,000
Receiver D: 100,000 $/1000 X 500 = $50,000
The following receiver tracing factors are also possible:
- Version
- Activity type
- Origin
- Statistical key figure
- Fixed amounts
You define fixed amounts on the tracing factor tab page. The receivers are charged directly with these amounts. The amount credited to the sender is derived from the total of the receiver debits. The rule for determining the sender values is not used here. The SAP system ignores posted sender amounts or defined sender amounts.
- Fixed percentages
You define fixed percentages for the receivers on the Tracing factor screen. The value from the sender is distributed to the receivers according to this percentage. The total of receiver tracing factors must not exceed 100%. The sender base must be fully distributed. If the total of the receiver tracing factors is less than 100%, then a portion of the sender value remains on the sender.
- Fixed portions
You define fixed portions for the receivers on the Tracing factor tab page. This process is similar to the process for fixed percentages, with the exception that the sender is credited in full, unless you defined a percentage remaining value.
Example:
Sender A distributes 100 production hours to three receivers with the following tracing factors:
Receiver B: 50 portions
Receiver C: 50 portions
Receiver D: 100 portions
Total: 200 portions
The SAP system calculates the following values:
Receiver B: 100 production hours/200 X 50 = 25 production hours
Receiver C: 100 production hours/200 X 50 = 25 production hours
Receiver D: 100 production hours/200 X 100 = 50 production hours
History
Last changed by/on | SAP | 19970827 |
SAP Release Created in |