on ‎2024 Dec 13 5:43 PM
Dear All,
In Cash and Liquidity Management, we derive the liquidity item for Purchase Orders using Queries (Origin X). The same liquidity items are applicable for Goods Receipts (MIGO) transactions as well.
In the MIRO transaction, we will have two line items (GR/IR Dr and Vendor Cr). We can get the liquidity item for the vendor line item using Queris (Origin C).
Request your assistance for helping me understand how the system will derive the liquidity item for the GR/IR account.
Thanks & Regards
Surya
Request clarification before answering.
I will explain my requirement in more detail.
Business Case (simple example)
Material A needs to be treated as Liquidity Item A (Operating Exp 1) and Material B needs to be treated as Liquidity Item B (Operating Exp 2). This can be achieved using Queries (Origin X).
For MIRO, the Accounting Entry would be GR/IR Acc Dr, Vendor Acc Cr. For Vendor Line item we can get the Liquidity Item using Queries (Origin C), but how to get the Liquidity Item for GR/IR Account. Using a default in FLQINFACC will not give me correct representation (as shown above, liquidity item needs to change based on Material). Request your help for the same.
What is SAP's solution for deriving Liquidity Item in MIRO transaction (which needs to derive based on the contents of the Purchase Order)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
You can implement own logic in FCLM_LQF_DERIVE_LQITEM_SAMPLE.
Or you can implement BADI_FCLM_FB2_FINAL_DECISION and remove the 'final' flag in case of GR/IR account, to force the system to trace the document flow further.
Regards,
Kristof
Per my understanding, it is recommend to use Query/Query Sequence in OP release.
In addition, the 'Derivate Function' in Query/Query Sequence accepts customer logic.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 41 | |
| 4 | |
| 4 | |
| 4 | |
| 4 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.