SAP TI_UNDERL_CASHFLOW_CONSTRUCT Function Module for Set Up Cash Flow for Underlying Transactions for Futures
TI_UNDERL_CASHFLOW_CONSTRUCT is a standard ti underl cashflow construct SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Set Up Cash Flow for Underlying Transactions for Futures processing and below is the pattern details for this FM, 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 ti underl cashflow construct FM, simply by entering the name TI_UNDERL_CASHFLOW_CONSTRUCT into the relevant SAP transaction such as SE37 or SE38.
Function Group: TB56
Program Name: SAPLTB56
Main Program: SAPLTB56
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TI_UNDERL_CASHFLOW_CONSTRUCT 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 'TI_UNDERL_CASHFLOW_CONSTRUCT'"Set Up Cash Flow for Underlying Transactions for Futures.
EXPORTING
I_SOFTYP = "
I_WZBETR = "
I_SZSREF = "
* I_BUKRS = "
* I_RANL = "
* I_RLDEPO = "
I_DBLFZ = "
I_DELFZ = "
I_PKOND = "
I_SZBMETH = "
I_BZBETR = "
TABLES
E_BEWEG = "ausgehende Bewegungen
IMPORTING Parameters details for TI_UNDERL_CASHFLOW_CONSTRUCT
I_SOFTYP -
Data type: VTIDERI-SOFTYPOptional: No
Call by Reference: No ( called with pass by value option)
I_WZBETR -
Data type: VTBFHAPO-WZBETROptional: No
Call by Reference: No ( called with pass by value option)
I_SZSREF -
Data type: VTBFINKO-SZSREFOptional: No
Call by Reference: No ( called with pass by value option)
I_BUKRS -
Data type: VZBEWEG-BUKRSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_RANL -
Data type: VZBEWEG-RANLOptional: Yes
Call by Reference: No ( called with pass by value option)
I_RLDEPO -
Data type: VZBEWEG-RLDEPOOptional: Yes
Call by Reference: No ( called with pass by value option)
I_DBLFZ -
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
I_DELFZ -
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
I_PKOND -
Data type: VTBFINKO-PKONDOptional: No
Call by Reference: No ( called with pass by value option)
I_SZBMETH -
Data type: VTBFINKO-SZBMETHOptional: No
Call by Reference: No ( called with pass by value option)
I_BZBETR -
Data type: VTBFHAPO-BZBETROptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for TI_UNDERL_CASHFLOW_CONSTRUCT
E_BEWEG - ausgehende Bewegungen
Data type: VZBEWEGOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TI_UNDERL_CASHFLOW_CONSTRUCT 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.| DATA: | ||||
| lt_e_beweg | TYPE STANDARD TABLE OF VZBEWEG, " | |||
| lv_i_softyp | TYPE VTIDERI-SOFTYP, " | |||
| lv_i_wzbetr | TYPE VTBFHAPO-WZBETR, " | |||
| lv_i_szsref | TYPE VTBFINKO-SZSREF, " | |||
| lv_i_bukrs | TYPE VZBEWEG-BUKRS, " | |||
| lv_i_ranl | TYPE VZBEWEG-RANL, " | |||
| lv_i_rldepo | TYPE VZBEWEG-RLDEPO, " | |||
| lv_i_dblfz | TYPE SY-DATUM, " | |||
| lv_i_delfz | TYPE SY-DATUM, " | |||
| lv_i_pkond | TYPE VTBFINKO-PKOND, " | |||
| lv_i_szbmeth | TYPE VTBFINKO-SZBMETH, " | |||
| lv_i_bzbetr | TYPE VTBFHAPO-BZBETR. " |
|   CALL FUNCTION 'TI_UNDERL_CASHFLOW_CONSTRUCT' "Set Up Cash Flow for Underlying Transactions for Futures |
| EXPORTING | ||
| I_SOFTYP | = lv_i_softyp | |
| I_WZBETR | = lv_i_wzbetr | |
| I_SZSREF | = lv_i_szsref | |
| I_BUKRS | = lv_i_bukrs | |
| I_RANL | = lv_i_ranl | |
| I_RLDEPO | = lv_i_rldepo | |
| I_DBLFZ | = lv_i_dblfz | |
| I_DELFZ | = lv_i_delfz | |
| I_PKOND | = lv_i_pkond | |
| I_SZBMETH | = lv_i_szbmeth | |
| I_BZBETR | = lv_i_bzbetr | |
| TABLES | ||
| E_BEWEG | = lt_e_beweg | |
| . " TI_UNDERL_CASHFLOW_CONSTRUCT | ||
ABAP code using 7.40 inline data declarations to call FM TI_UNDERL_CASHFLOW_CONSTRUCT
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.| "SELECT single SOFTYP FROM VTIDERI INTO @DATA(ld_i_softyp). | ||||
| "SELECT single WZBETR FROM VTBFHAPO INTO @DATA(ld_i_wzbetr). | ||||
| "SELECT single SZSREF FROM VTBFINKO INTO @DATA(ld_i_szsref). | ||||
| "SELECT single BUKRS FROM VZBEWEG INTO @DATA(ld_i_bukrs). | ||||
| "SELECT single RANL FROM VZBEWEG INTO @DATA(ld_i_ranl). | ||||
| "SELECT single RLDEPO FROM VZBEWEG INTO @DATA(ld_i_rldepo). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_i_dblfz). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_i_delfz). | ||||
| "SELECT single PKOND FROM VTBFINKO INTO @DATA(ld_i_pkond). | ||||
| "SELECT single SZBMETH FROM VTBFINKO INTO @DATA(ld_i_szbmeth). | ||||
| "SELECT single BZBETR FROM VTBFHAPO INTO @DATA(ld_i_bzbetr). | ||||
Search for further information about these or an SAP related objects