Hierarchy
SAP_FIN (Software Component) SAP_FIN⤷
TR (Application Component) Treasury⤷
FFLQ (Package) Liquidity Calculation
IMG Activity
| ID | SIMG_FLQC13 | Settings for FI Mechanisms |
| Transaction Code | S_AXA_22000120 | (empty) |
| Created on | 20040629 | |
| Customizing Attributes | SIMG_FLQC13 | Settings for FI Mechanisms |
| Customizing Activity | SIMG_FLQC13 | Settings for FI Mechanisms |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | FI-MECHANISMEN |
Use
This assignment mechanism evaluates, amongst other things, the customer and vendor line items related to the payment.
Requirements
Standard settings
Activities
Partial Conversion:
The partial conversion allows assignment to liquidity items, even if only part of the corresponding payment could be cleared.
If you have not set this indicator, an assignment is only made to a payment for liquidity items when the payment is completely cleared. If multiple clearing documents are used to carry out the complete clearing for which different liquidity items were determined, then the actual document is split according to the items. However, if a partial amount has not yet been cleared, assignment is not carried out either for the entire payment or for the partial amounts that have already been cleared.
If the partial conversion indicator is set, the actual document is split even if the entire payment has not yet been cleared. The assignment mechanism assigns suitable liquidity items to the cleared partial amounts. The remaining amount stays at the old item.
N:M Treatment:
It is often the case that N bank statement postings with M postings are cleared together in bank clearing accounts. In this case, the assignment mechanisms for the liquidity calculation cannot always trace which postings in the subledger belong to which postings in the bank account. No liquidity items can be determined.
You can create a workaround in this case by activating the N:M treatment. The item with the highest amount is first identified from the postings in the bank accounts and chosen as a "representative" for all payment items for this document. The amount of representatives is increased so that it corresponds to the total of N payment amounts. At the same time, the others - now already in the represented payments in the liquidity calculation - are excluded from further assignments in which dummy liquidity items are assigned to them. These items are recognized by the liquidity calculation as being "not relevant for liquidity." The keys for these dummy liquidity items are defined in the "Incoming Transfer" field for incoming payments and in the "Outgoing Transfer" field for outgoing payments. The representative is then distributed proportionately to up to M determined liquidity items.
Info Accounts in the Application:
This indicator determines whether the query-relevant G/L accounts should be maintained in the application.
If the indicator is not set, these accounts can only be maintained in Customizing which usually requires authorization from the implementation team.
Evaluation of GR/IR Line Items:
This function is only relevant for the third mechanism when evaluating the invoices. For more information, see the F1 Help.
Evaluate Intermediate Status
In the second step, the evaluation mechanism uses clearing to track a related document chain until it encounters a document line item to evaluate. This end point characteristic depends primarily on the account. With regard to G/L accounts line items this includes the GR/IR account (if the GR/IR indicator is set, see below), all accounts for the profit and loss statement, and all query-relevant G/L accounts without the "Continue" indicator (see below). If this indicator is set, document line items, which have a query-relevant G/L account indicated by "Continue" but which have not yet been cleared, are also evaluated.
Reduction of the Document Cluster in FI
Document chains are often very complicated. The reason for this is due to large documents which have line items included in different clearing procedures, and large clearing procedures with hundreds of cleared line items. However, the incorporation of customer-defined exit modules enables you to retain an overview here. The content code, meaning the reduction heuristic, must be created within the implementation project.
Example
The following example explains the N:M treatment function:
Payment a) EUR 500 Clearing 1) EUR 300 => Regular Customer Sales
Payment b) EUR 100 Clearing 2) EUR 300 => Other Sales
Different liquidity items (LI) are determined for both clearing postings, such as regular customer sales and other sales.
Due to the amount here, the representative is payment a. The actual document for payment a is split into two actual accounts, namely a' and a'' (see below). Since the representative now covers the other payments, the actual documents for payments a'' and b are set at the dummy liquidity items mentioned above. The liquidity calculation characteristically ignores these actual documents in further assignment processes. This leads to the following result:
Payment a) Replaced and therefore no longer exists
Payment a') EUR 600 => Representative
Payment a'') EUR 100 => Assignment to dummy LI "Outgoing Transfer"
Payment b) EUR 100 => Assignment to dummy LI "Incoming Transfer
Payment a' is now split into two actual documents according to the clearing documents. In this case, their amounts are the same:
Payment a' 1) EUR 300 => Assignment to LI "Regular Customer Sales"
Payment a' 2) EUR 300 => Assignment to LI "Other Sales"
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| FLQASSET | S - Table (with text table) | FLQC13 |
History
| Last changed by/on | SAP | 20130218 |
| SAP Release Created in | 2005_1_470 |
