SAP BAPI_CRMISUPROP_CHANGE Function Module for Change Profile Data at Point of Delivery (Header and/or Values)









BAPI_CRMISUPROP_CHANGE is a standard bapi crmisuprop change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change Profile Data at Point of Delivery (Header and/or Values) 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 bapi crmisuprop change FM, simply by entering the name BAPI_CRMISUPROP_CHANGE into the relevant SAP transaction such as SE37 or SE38.

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



Function BAPI_CRMISUPROP_CHANGE 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 'BAPI_CRMISUPROP_CHANGE'"Change Profile Data at Point of Delivery (Header and/or Values)
  EXPORTING
   PODINSTANCE =  "
   PROFILEINSTANCE =  "Profile: Number of IB Component (Instance)
*  HEAD_DATA_ALL =  "Header Data for Profile at Point of Delivery
*  TEST_RUN = ' ' "Switch to Simulation Mode for Write BAPIs

TABLES
*  EXTENSIONIN =  "Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT
*  RETURN =  "Return Parameter
*  VALUES_DATA =  "Profile values
*  USEFACTORS_DATA =  "Consumer Factors
.



IMPORTING Parameters details for BAPI_CRMISUPROP_CHANGE

PODINSTANCE -

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

PROFILEINSTANCE - Profile: Number of IB Component (Instance)

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

HEAD_DATA_ALL - Header Data for Profile at Point of Delivery

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

TEST_RUN - Switch to Simulation Mode for Write BAPIs

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

TABLES Parameters details for BAPI_CRMISUPROP_CHANGE

EXTENSIONIN - Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT

Data type: BAPIPAREX
Optional: Yes
Call by Reference: Yes

RETURN - Return Parameter

Data type: BAPIRET2
Optional: Yes
Call by Reference: Yes

VALUES_DATA - Profile values

Data type: BAPICRMISUPROFILEVALUES
Optional: Yes
Call by Reference: Yes

USEFACTORS_DATA - Consumer Factors

Data type: BAPICRMISUPROFILEVALUES
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for BAPI_CRMISUPROP_CHANGE 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_extensionin  TYPE STANDARD TABLE OF BAPIPAREX, "   
lv_podinstance  TYPE BAPICRMISUPROFILEAUX-PODINSTANCE, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_profileinstance  TYPE BAPICRMISUPROFILEPODHEAD-PROFILEINSTANCE, "   
lt_values_data  TYPE STANDARD TABLE OF BAPICRMISUPROFILEVALUES, "   
lv_head_data_all  TYPE BAPICRMISUPROFILEPODHEAD, "   
lv_test_run  TYPE BAPICRMISUPROFILEAUX-TESTRUN, "   SPACE
lt_usefactors_data  TYPE STANDARD TABLE OF BAPICRMISUPROFILEVALUES. "   

  CALL FUNCTION 'BAPI_CRMISUPROP_CHANGE'  "Change Profile Data at Point of Delivery (Header and/or Values)
    EXPORTING
         PODINSTANCE = lv_podinstance
         PROFILEINSTANCE = lv_profileinstance
         HEAD_DATA_ALL = lv_head_data_all
         TEST_RUN = lv_test_run
    TABLES
         EXTENSIONIN = lt_extensionin
         RETURN = lt_return
         VALUES_DATA = lt_values_data
         USEFACTORS_DATA = lt_usefactors_data
. " BAPI_CRMISUPROP_CHANGE




ABAP code using 7.40 inline data declarations to call FM BAPI_CRMISUPROP_CHANGE

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 PODINSTANCE FROM BAPICRMISUPROFILEAUX INTO @DATA(ld_podinstance).
 
 
"SELECT single PROFILEINSTANCE FROM BAPICRMISUPROFILEPODHEAD INTO @DATA(ld_profileinstance).
 
 
 
"SELECT single TESTRUN FROM BAPICRMISUPROFILEAUX INTO @DATA(ld_test_run).
DATA(ld_test_run) = ' '.
 
 


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!