SAP CMS_BII_TRIGGER_DEX_PROGRAM Function Module for CMS-Basel II: Trigger Data Extraction Program









CMS_BII_TRIGGER_DEX_PROGRAM is a standard cms bii trigger dex program SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for CMS-Basel II: Trigger Data Extraction Program 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 cms bii trigger dex program FM, simply by entering the name CMS_BII_TRIGGER_DEX_PROGRAM into the relevant SAP transaction such as SE37 or SE38.

Function Group: CMS_BII_DEX_MISC
Program Name: SAPLCMS_BII_DEX_MISC
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function CMS_BII_TRIGGER_DEX_PROGRAM 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 'CMS_BII_TRIGGER_DEX_PROGRAM'"CMS-Basel II: Trigger Data Extraction Program
  EXPORTING
   I_DEX_PR_TYP =  "CMS-Basel II: Data Extraction Process Type
*  I_CAG_BLOCK_SIZE =  "CMS-Basel II: Data Extraction Block Size
*  I_CHNG_PNTR_STATUS =  "CMS-Basel II: Object Processing Status
*  I_CHNG_PNTR_DATE_FROM =  "Date from which the change pointers were created
*  I_CHNG_PNTR_DATE_TO =  "Date to which the change pointers were created
*  I_TAB_CAG_TYP_RNG =  "Collateral Agreement Type Ranges
*  I_CAG_VALID_FROM =  "Date to  which the Coll. Agmt is Valid
*  I_CAG_VALID_TO =  "Date from which the Coll. Agmt is Valid
*  I_FLG_BACKGROUND_PROCESS =  "Execute Data Extraction Process in Background
*  I_AST_BLOCK_SIZE =  "CMS-Basel II: Data Extraction Block Size

 IMPORTING
   E_TAB_RC =  "Return Code and corresponding Message
.



IMPORTING Parameters details for CMS_BII_TRIGGER_DEX_PROGRAM

I_DEX_PR_TYP - CMS-Basel II: Data Extraction Process Type

Data type: CMS_DTE_BII_DEX_PR_TYP
Optional: No
Call by Reference: No ( called with pass by value option)

I_CAG_BLOCK_SIZE - CMS-Basel II: Data Extraction Block Size

Data type: CMS_DTE_BII_DEX_BLK_SIZE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_CHNG_PNTR_STATUS - CMS-Basel II: Object Processing Status

Data type: CMS_DTE_BII_OBJ_PR_STAT
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_CHNG_PNTR_DATE_FROM - Date from which the change pointers were created

Data type: CMS_DTE_BII_CHNG_PNTR_DATE_FR
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_CHNG_PNTR_DATE_TO - Date to which the change pointers were created

Data type: CMS_DTE_BII_CHNG_PNTR_DATE_TO
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_TAB_CAG_TYP_RNG - Collateral Agreement Type Ranges

Data type: CMS_TAB_BII_CAG_TYP_RNG
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_CAG_VALID_FROM - Date to which the Coll. Agmt is Valid

Data type: CMS_DTE_BII_CAG_SCR_VALID_FROM
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_CAG_VALID_TO - Date from which the Coll. Agmt is Valid

Data type: CMS_DTE_BII_CAG_SCR_VALID_TO
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_FLG_BACKGROUND_PROCESS - Execute Data Extraction Process in Background

Data type: CMS_DTE_BII_FLG_IN_BACKGROUND
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_AST_BLOCK_SIZE - CMS-Basel II: Data Extraction Block Size

Data type: CMS_DTE_BII_DEX_BLK_SIZE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for CMS_BII_TRIGGER_DEX_PROGRAM

E_TAB_RC - Return Code and corresponding Message

Data type: CMS_TAB_MSG_COL_MESSAGE
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for CMS_BII_TRIGGER_DEX_PROGRAM 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:
lv_e_tab_rc  TYPE CMS_TAB_MSG_COL_MESSAGE, "   
lv_i_dex_pr_typ  TYPE CMS_DTE_BII_DEX_PR_TYP, "   
lv_i_cag_block_size  TYPE CMS_DTE_BII_DEX_BLK_SIZE, "   
lv_i_chng_pntr_status  TYPE CMS_DTE_BII_OBJ_PR_STAT, "   
lv_i_chng_pntr_date_from  TYPE CMS_DTE_BII_CHNG_PNTR_DATE_FR, "   
lv_i_chng_pntr_date_to  TYPE CMS_DTE_BII_CHNG_PNTR_DATE_TO, "   
lv_i_tab_cag_typ_rng  TYPE CMS_TAB_BII_CAG_TYP_RNG, "   
lv_i_cag_valid_from  TYPE CMS_DTE_BII_CAG_SCR_VALID_FROM, "   
lv_i_cag_valid_to  TYPE CMS_DTE_BII_CAG_SCR_VALID_TO, "   
lv_i_flg_background_process  TYPE CMS_DTE_BII_FLG_IN_BACKGROUND, "   
lv_i_ast_block_size  TYPE CMS_DTE_BII_DEX_BLK_SIZE. "   

  CALL FUNCTION 'CMS_BII_TRIGGER_DEX_PROGRAM'  "CMS-Basel II: Trigger Data Extraction Program
    EXPORTING
         I_DEX_PR_TYP = lv_i_dex_pr_typ
         I_CAG_BLOCK_SIZE = lv_i_cag_block_size
         I_CHNG_PNTR_STATUS = lv_i_chng_pntr_status
         I_CHNG_PNTR_DATE_FROM = lv_i_chng_pntr_date_from
         I_CHNG_PNTR_DATE_TO = lv_i_chng_pntr_date_to
         I_TAB_CAG_TYP_RNG = lv_i_tab_cag_typ_rng
         I_CAG_VALID_FROM = lv_i_cag_valid_from
         I_CAG_VALID_TO = lv_i_cag_valid_to
         I_FLG_BACKGROUND_PROCESS = lv_i_flg_background_process
         I_AST_BLOCK_SIZE = lv_i_ast_block_size
    IMPORTING
         E_TAB_RC = lv_e_tab_rc
. " CMS_BII_TRIGGER_DEX_PROGRAM




ABAP code using 7.40 inline data declarations to call FM CMS_BII_TRIGGER_DEX_PROGRAM

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!