SAP Note

Header Data

Symptom

You use the liquidity invoice and analyze the document chains of the accounting for the determination of liquidity items. In the case that several actual rows are combined by clearing and there is a unique combination of liquidity item, business area, company code for this purpose, you expect a direct assignment of every actual row belonging to the combination found. Example: In the document 001 50  Bank                    100-    actual 002 50  Bank                    150-    actual 003 40  Wage/salary clearing     250     Info with HR-PAY item, you expect that each of the two actual rows is displayed on the HR-PAY item. However, this is not the case. Rather the assignment mechanisms FLQAC and FLQAD issue an error if you did not activate the N:M indicator in Customizing. However, if you activated it, the usual representative creation and move occurs with N:M dummy item, therefore: Actual row 001:  100- on dummy outbound Actual row 002:  100+ on dummy entry                 250- on HR-PAY (Representative) This seems unnecessarily complicated for this simple case.

Other Terms

FLQAC, FLQAD, RFLQ_ASSIGN_FI, RFLQ_ASSIGN_REX, RFLQ_ASSIGN_INV

Reason and Prerequisites

The representative logic in the N:M case has two aims:

l Avoiding an arbitrary splitting (Payments for liquidity items).

l The second assignment step with reading and evaluation of the invoices should not to be carried out repeatedly, only once.

Solution

Implement the attached correction. When you implement the correction, the system response changes as follows: If there is a unique assignment for several combined actual rows in FLQAC or in the first step of the 2-level mechanisms (for example, FLQAD), the usual N:M processing is not executed (Error or representative), instead each of the affiliated actual rows gets this unique combination of liquidity item, business area, company code directly. In the case of 2-level mechanisms, this is only then the case if this liquidity item is not a buffer item and there is therefore no second evaluation step for these actual payments.

Validity

Correction Instructions

    791744 - Unique assignment and N:M logic  

Version   2     Validity: 01.02.2006 - active   Language   English

Released On 01.02.2006 08:43:47

Release Status Released for Customer

Component FIN-FSCM-LP Liquidity Planer

Priority Correction with low priority

Category Program error

Software Component From Rel. To Rel. And Subsequent

PI 2003_1_45B 2003_1_470  

2004_1_45B 2004_1_500  

Correction Instructions

Software Component Valid from Valid to Number

PI 2003_1_45B 2003_1_470 688961

PI 2004_1_46B 2004_1_500 688967

Causes - Side Effects

Support Packages & Patches

Notes / Patches corrected with this note

Note Reason From Version To Version Note Solution Version Support Package

The table does not contain any entries

The following SAP Notes correct this Note / Patch

Note Reason From Version To Version Note Solution Version Support Package

791744 0 0 821485 1  

Support Packages

Software Component Release Support Package

PI 2004_1_45B SAPKIPZI26

2004_1_46B SAPKIPZI36

2004_1_46C SAPKIPZI46

2004_1_470 SAPKIPZI56

2004_1_500 SAPKIPZI66