SAP CMS_BII_DEX_PP_0206 Function Module for Save Package Parameters
CMS_BII_DEX_PP_0206 is a standard cms bii dex pp 0206 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Save Package Parameters 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 dex pp 0206 FM, simply by entering the name CMS_BII_DEX_PP_0206 into the relevant SAP transaction such as SE37 or SE38.
Function Group: CMS_BII_DEX_PP
Program Name: SAPLCMS_BII_DEX_PP
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CMS_BII_DEX_PP_0206 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_DEX_PP_0206'"Save Package Parameters.
EXPORTING
I_TAB_PACKPARAMS = "
I_X_UPDATE = "
IMPORTING Parameters details for CMS_BII_DEX_PP_0206
I_TAB_PACKPARAMS -
Data type: CMS_BII_TAB_PP_APPL_PCKG_DATAOptional: No
Call by Reference: Yes
I_X_UPDATE -
Data type: XFELDOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CMS_BII_DEX_PP_0206 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_i_tab_packparams | TYPE CMS_BII_TAB_PP_APPL_PCKG_DATA, " | |||
| lv_i_x_update | TYPE XFELD. " |
|   CALL FUNCTION 'CMS_BII_DEX_PP_0206' "Save Package Parameters |
| EXPORTING | ||
| I_TAB_PACKPARAMS | = lv_i_tab_packparams | |
| I_X_UPDATE | = lv_i_x_update | |
| . " CMS_BII_DEX_PP_0206 | ||
ABAP code using 7.40 inline data declarations to call FM CMS_BII_DEX_PP_0206
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