SAP EXPECTED_CASH_FLOW_DATE_GET Function Module for

Search SAP Function Modules

EXPECTED_CASH_FLOW_DATE_GET is a standard expected cash flow date get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.

See here to view full function module documentation and code listing for expected cash flow date get FM, simply by entering the name EXPECTED_CASH_FLOW_DATE_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: FMFA_CORE
Program Name: SAPLFMFA_CORE
Main Program: SAPLFMFA_CORE
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EXPECTED_CASH_FLOW_DATE_GET pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.

CALL FUNCTION 'EXPECTED_CASH_FLOW_DATE_GET'"
  EXPORTING
   I_BUKRS =  "
   I_ZBD1P =  "
*  I_UMSKS = ' ' "
*  I_UMSKZ = ' ' "
   I_SHKZG =  "
*  I_REBZG = ' ' "
   I_KOART =  "
*  I_KUNNR = ' ' "
   I_BUDAT =  "
*  I_VALUT = '00000000' "
*  I_ZFBDT = '00000000' "
   I_ZBD1T =  "
   I_ZBD2T =  "
   I_ZBD3T =  "

 IMPORTING
   E_ZHLDT =  "

.

IMPORTING Parameters details for EXPECTED_CASH_FLOW_DATE_GET

I_BUKRS -

Data type: FMBP-BUKRS
Optional: No
Call by Reference: No ( called with pass by value option)

I_ZBD1P -

Data type: FMBP-ZBD1P
Optional: No
Call by Reference: No ( called with pass by value option)

I_UMSKS -

Data type: FMBP-UMSKS
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_UMSKZ -

Data type: FMBP-UMSKZ
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_SHKZG -

Data type: FMBP-SHKZG
Optional: No
Call by Reference: No ( called with pass by value option)

I_REBZG -

Data type: FMBP-REBZG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_KOART -

Data type: FMBP-KOART
Optional: No
Call by Reference: No ( called with pass by value option)

I_KUNNR -

Data type: FMBP-KUNNR
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_BUDAT -

Data type: FMBK-BUDAT
Optional: No
Call by Reference: No ( called with pass by value option)

I_VALUT -

Data type: FMBP-VALUT
Default: '00000000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_ZFBDT -

Data type: FMBP-ZFBDT
Default: '00000000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_ZBD1T -

Data type: FMBP-ZBD1T
Optional: No
Call by Reference: No ( called with pass by value option)

I_ZBD2T -

Data type: FMBP-ZBD2T
Optional: No
Call by Reference: No ( called with pass by value option)

I_ZBD3T -

Data type: FMBP-ZBD3T
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for EXPECTED_CASH_FLOW_DATE_GET

E_ZHLDT -

Data type: FMEPIN-ZHLDT
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for EXPECTED_CASH_FLOW_DATE_GET Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

ABAP code using 7.40 inline data declarations to call FM EXPECTED_CASH_FLOW_DATE_GET

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

Search for further information about these or an SAP related objects