Skip to Content

This article describes the logic of filling the Cash management attributes in the FI document.

Further, these attributes are involved in creating entries in the Exposure Hub.

 

FDTAG «Planning Date»

The determination of the planned date is performed in the function module PAYDAY_DETERMINATION. The algorithm for determining the planned date is described in the note 24883 – «CMF: Determination of value/planning date».

Planning date is not filled for down payment requests (tr. F-47/F-37) and payment requests (tr. F-59).

The FDTAG attribute is filled in the FI document positions under the following conditions:

  1. Type of account (BSEG-KOART) = ‘S’ AND Planning level filled in master data of GL account (SKB1-FDLEV). The planned date is filled with the value of the “Valuation date” attribute (BSEG-VALUT). If the “Valuation date” attribute is empty, the planned date is filled with the value of the “Posting Date” (BKPF-BUDAT) attribute.
  2. BSEG-KOART «Type of account» = ‘K’ AND BSEG-UMSKZ «Special G/L Indicator» empty AND BSEG-LFB1 «Planning group» not empty.
    The system iterates through the conditions and when the conditions are met, the following steps are not performed:
  • BSEG-REBZT «Follow-On Document Type» = ‘V’ «Credit memo».
    The planned date is copied from the related account payable position.
  • (BSEG-SHKZG «Debit/Credit Indicator» = ‘H’ «Credit» OR BSEG-REBZG « Number of the Invoice the Transaction Belongs to» not empty) AND T035-DATYP «Cash Management: Control Planning Date for Planning Groups» not empty. The description of the algorithm for filling in the planned date is given in the help to the field T035-DATYP:
    If you want to deviate from the standard calaculation of the planning date for customer and vendor groups, the following possibilities exist:
    ‘+’ = Cash discount due date 1 (payment baseline date + days for cash discount terms 1)
    ‘++’ = Due date for net payment (payment baseline date + days for net payment)
    ’00’ to ’99’ = Difference days for payment baseline date.
    Deviation from the standard calculation can then be useful if sporadic large payments or advance payments from the customer would completely distort planning date determination on the basis of the payment history, then the payment history recording should therefore stay switched on.
  • (BSEG-SHKZG «Debit/Credit Indicator» = ‘H’ «Credit» OR BSEG-REBZG « Number of the Invoice the Transaction Belongs to» not empty) AND T035-DATYP «Cash Management: Control Planning Date for Planning Groups» empty.
    Payment date = payment baseline date (BSEG-ZFBDT) + days for net payment (BSEG-ZBD1/2/3T).
  • In other cases.
    Payment date = payment baseline date (BSEG-ZFBDT).
  1. BSEG-KOART «Type of account» = ‘D’ AND BSEG-UMSKZ «Special G/L Indicator» empty AND BSEG-FDGRV «Planning group» not empty.
  2. The system iterates through the conditions and when the conditions are met, the following steps are not performed:
  • BSEG-REBZT «Follow-On Document Type» = ‘V’ «Credit memo».
    The planned date is copied from the related account receivable position.
  • (BSEG-SHKZG «Debit/Credit Indicator» = ‘S’ «Debit» OR BSEG-REBZG « Number of the Invoice the Transaction Belongs to» not empty) AND T035-DATYP «Cash Management: Control Planning Date for Planning Groups» not empty.
    The description of the algorithm for filling in the planned date is given in the help to the field T035-DATYP (see point 2 for previous item).
  • (BSEG-SHKZG «Debit/Credit Indicator» = ‘S’ «Debit» OR BSEG-REBZG « Number of the Invoice the Transaction Belongs to» not empty) AND KNB1-XZVER «Indicator: Record Payment History».
    Payment date = baseline date for payment (BSEG-ZFBDT) + net days (BSEG-ZBD1/2/3T) + average days in arrears of net payments (KNB4-AGS01,AGS02,AGS03) for the last three periods.
  • (BSEG-SHKZG «Debit/Credit Indicator» = ‘S’ «Debit» OR BSEG-REBZG « Number of the Invoice the Transaction Belongs to» not empty) AND T035-DATYP «Cash Management: Control Planning Date for Planning Groups» empty.
    Payment date = payment baseline date (BSEG-ZFBDT) + days for net payment (BSEG-ZBD1/2/3T).
  • In other cases.
    Payment date = payment baseline date (BSEG-ZFBDT).

 

FDLEV «Planning Level» and FDGRP «Planning Group»

Planning level is not filled for down payment requests (tr. F-47/F-37) and payment requests (tr. F-59).

The algorithm of definition of attributes FDLEV and FDGRP in the FI document positions:

In the include SAPFF001 form finanzdispo_stammdaten performed Initial filling.

If BSEG-KOART = ‘D’, BGEG-FDGRG = KNB1-FDGRP.

If BSEG-KOART = ‘K’, BSEG-FDGRP = LFB1-FDGRP.

If BSEG-KOART = ‘S’, BSEG-FDLEV = SKB1-FDLEV.

 

Follow determination of the planned date is performed in the function modules CASH_FORECAST_LEVEL_AND_DATE and CASH_FORECAST_LEVEL_AND_DATE_2.

If the following conditions are met, the definition is not fulfilled:

  • BSEG-KOART <> D/K/S.
  • If BSEG-KOART = S, bseg-fdgrp <> space OR bseg-fdlev = space.
  • If BSEG-KOART = D/K, bseg-fdgrp = space.
  • If bseg-umsks = ‘W’ AND bseg-zfbdt is empty.
  • If bseg-fdtag is empty.

 

Logical tree for filling attribute FDLEV:

 

FQFTYPE «Flow Type».

When the FI document is posted, the function module FQM_RWIN_PROJECT_AP_AR is triggered, which calls the method cl_fqm_adapter_ap_ar = PROJECT.

This method fills the attribute FQFTYPE (in method GET_FLOW_TYPE_FOR_ACCIT) and additionally all dimensions FQM_FLOW (in method MAP_ACCIT_2_FQM_FLOW).

1-st step:

2-nd step.

The system attempts to identify whether the document is an customer or vendor invoice by the following condition (:

((BSEG-KOART «Account type» = ‘D’ «Customer») OR (BSEG-KOART «Account type» = ‘K’ «Vendor»)) AND BSEG-XUMSW «Indicator: Sales-Related Item» AND In document don’t exist accounts with type BANK_CLEARING_ACCOUNT and BANK_ACCOUNT

If the document is defined as an invoice and the type of account is not the Customer / Vendor and not the Incoming / Outgoing tax, then the following logic works (method PROCESS_INVOICE):

3-d step.

Additional logic to override previously defined flow types:

cl_fqm_adapter_ap_ar =>GET_FLOW_TYPE

In addition, the logic for determining the type of flow is described in the documentation:

https://uacp2.hana.ondemand.com/doc/0f7c7e573452a96be10000000a4450e5/3.6/en-US/frameset.htm

 

In the SPRO, it is possible to change the standard logic for determining FLOW TYPE using the settings:

  • Financial Supply Chain Management > Cash and liquidity management > Cash management > Flow types > Define flow types
  • Financial Supply Chain Management > Cash and liquidity management > Cash management > Flow types > Assign Flow Types to G/L Accounts

 

FDWBT «Planned Amount in Document or G/L Account Currency»

The determination of the planned date is performed in the function module CASH_FORECAST_AMOUNT.

Planning amount is not filled for down payment requests (tr. F-47/F-37) and payment requests (tr. F-59).

The FDWBT attribute is filled in the FI document positions under the following conditions:

 

HBKID «House bank» and HKTID «House bank account»

Attributes HBKID and HKTID are automatically filled in when you create a FI document with a Bank account statement (include RFEBBU00 form fb01_bseg_soll).

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply