Solution : https://service.sap.com/sap/support/notes/614240 (Connexion à SAP Service Marketplace requise)
Résumé :
This SAP Note addresses issues with liquidity calculation transparency during the derivation of liquidity items from invoice-related expense and revenue information using Transaction FLQAD and Program RFLQ_ASSIGN_REX. Users find the first derivation step from payments straightforward but require clearer rules for the subsequent processes. This note provides detailed guidelines, ensuring that prerequisites such as the implementation of Note 571225 are met. It specifies rules for selecting line items to generate liquidity data, emphasizing the evaluation paths and conditions including account types and the use of the FURTHER indicator, to improve rule transparency and application consistency.
Mots Clés :
relevant reconciliation accounts generates, loss accounts pure info, basic functional reason, general ledger accounts, gr/ir accounts, gr/ir account, vendors info accounts, fi bank account, naive idea implemented, bank-vendor-revenue
Notes associées :
| 980933 | Document chains with down payments in the forecast |
| 974581 | Evaluation of document chains with down payments |
| 944529 | Scaling of the contribution of partial payments |
| 878970 | Behavior at: Evaluate intermediate status (FLQC13) |
| 819269 | Amounts on buffer item in spite of clearing |
| 731563 | Migration: Cash budget management in liquidity calculation |
| 731562 | Liquidity calculation: Enhancements in plug-in 2004.1 |
| 721326 | FLQAD: Too many items involved in the second step |
| 685341 | Intermediate statuses for assignment of liquidity item |
| 670204 | FLQAD: Assignment in second step not clear |
| 611866 | FLQAD: Stop after first step despite buffer item |
| 591208 | Liquidity calculation: Technical documentation |
| 571225 | FLQAD:Too many documents are read in the second step |
| 412605 | Implementation of the liquidity calculation |