SAP ISM_BUPA_CC_PARTNER_DI Function Module for
ISM_BUPA_CC_PARTNER_DI is a standard ism bupa cc partner di 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 ism bupa cc partner di FM, simply by entering the name ISM_BUPA_CC_PARTNER_DI into the relevant SAP transaction such as SE37 or SE38.
Function Group: JGBPCC
Program Name: SAPLJGBPCC
Main Program: SAPLJGBPCC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISM_BUPA_CC_PARTNER_DI 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 'ISM_BUPA_CC_PARTNER_DI'".
EXPORTING
* I_XCOMMIT = "
IMPORTING
E_XERROR = "
TABLES
* T_MESSAGE = "
IMPORTING Parameters details for ISM_BUPA_CC_PARTNER_DI
I_XCOMMIT -
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISM_BUPA_CC_PARTNER_DI
E_XERROR -
Data type: BUS000FLDS-CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISM_BUPA_CC_PARTNER_DI
T_MESSAGE -
Data type: BUS0MSG1Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISM_BUPA_CC_PARTNER_DI 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_xerror | TYPE BUS000FLDS-CHAR1, " | |||
| lv_i_xcommit | TYPE BOOLE-BOOLE, " | |||
| lt_t_message | TYPE STANDARD TABLE OF BUS0MSG1. " |
|   CALL FUNCTION 'ISM_BUPA_CC_PARTNER_DI' " |
| EXPORTING | ||
| I_XCOMMIT | = lv_i_xcommit | |
| IMPORTING | ||
| E_XERROR | = lv_e_xerror | |
| TABLES | ||
| T_MESSAGE | = lt_t_message | |
| . " ISM_BUPA_CC_PARTNER_DI | ||
ABAP code using 7.40 inline data declarations to call FM ISM_BUPA_CC_PARTNER_DI
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 CHAR1 FROM BUS000FLDS INTO @DATA(ld_e_xerror). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xcommit). | ||||
Search for further information about these or an SAP related objects