Hierarchy
BBPCRM (Software Component) BBPCRM⤷
FI-FM-PO (Application Component) Postings⤷
FMRE (Package) Funds Management: Earmarked Funds
Basic Data
| Data Element | ADDITIV_CONSUMPTION_LOGIC |
| Short Description | Additive Consumption Logic of Earmarked Funds |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR1_X | |
| 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 | Add. Logic |
| Medium | 19 | Add. Rdctn Logic |
| Long | 38 | Add. Redctn Logic of Earmarked Funds |
| Heading | 0 |
Documentation
Definition
Additiv consumption logic for document chain "Earmarked Funds (EF)/(Down Payment Request)/Down Payment/Invoice". If the flag is activated, an additiv consumption logic is applied to the document chain. The alternative logic differs from the standard logic in the way down payment, down payment requests and invoices are handled. In comparison to the standard logic, the alternative logic works under the assumption that related documents clear each other and therefore each document is relevant for earmarked funds consumption. In this case it is not necessary to determine the relevancy using consumption buckets for each of the transaction types ( Down Payment Request. Down payment, Invoice).
Example
Earmarked funds document with amount #100
1st down payment request #50
1st down payment (offsets/clears request) #50
Invoice (offsets down payment) #60
2nd down payment request #30
Standard Concept:
Every bucket (such as, down payment request, down payment, invoice) builds a single consumption line and all buckets consume the earmarked funds amount in parallel. The highest bucket value finally determines the document consumption, for example:
Document amount: #100
Sum of all down payments: #50
Sum of all down payment requests: #80
Sum of all Invoices: #60
The down payment request bucket wins and the document is finally consumed by 80# resulting in a residual available amount of 20#. Nevertheless, it is possible to post another invoice of 40#.
Additive Concept
Each document (such as down payment request, down payment, invoice) consumes the EF document individually, but at the same time consumption is deleted through cleared documents. In the example, these are represented by the lines with a minus sign in front. The cleared line is then actually represented by the amount 0 in the consumption display of the earmarked funds.
Earmarked funds document with amount #100+
1st down payment request #50
1st down payment (clears request) #50-
#50+
Invoice (clears down payment) #50+
#60+
2nd down payment request #30+
The EF document is finally consumed by #90 (30# 2. down payment request + 60#). This results in a residual available amount of #10.
This logic is only possible if the automatic clearing of down payments has been activated for the document types in the document chain.
Note that the document type configuration at the time of EF document creation is relevant for the consumption logic. The consumption logic is then stored in the EF document header and can be displayed there. It is not possible to change the consumption logic in the EF itself nor is it possible to change the consumption logic for existing documents posted with a specific document type.
Use
Dependencies
You maintain the consumption logic in the configuration for the EF document type.
Example
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in | 604 |
