SAP BAPI_CUSTOMERCRM_CHANGE Function Module for Proxy BAPI for Customer Upload in SFA Context: Customer Data Changes









BAPI_CUSTOMERCRM_CHANGE is a standard bapi customercrm 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 Proxy BAPI for Customer Upload in SFA Context: Customer Data Changes 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 customercrm change FM, simply by entering the name BAPI_CUSTOMERCRM_CHANGE into the relevant SAP transaction such as SE37 or SE38.

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



Function BAPI_CUSTOMERCRM_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_CUSTOMERCRM_CHANGE'"Proxy BAPI for Customer Upload in SFA Context: Customer Data Changes
  EXPORTING
   I_UPLOAD_ID =  "Unique Reference Number
*  I_BANKCHANGE =  "Single-Character Flag
   I_TRANS_MODE =  "Single-Character Flag
*  I_ORIGIN =  "Origin of Upload Object
*  I_CUSTCHANGE =  "BAPI Structure Master - General Data
*  I_SALESCHANGE =  "BAPI Structure Customer Master Data: Sales Data
   I_DESTIN =  "RFC Destination Server System
   I_SFA_REL =  "SFA Release in server system
   I_KEYWORD_IN =  "Keyword for customer enhancements
   I_CUSTOMER =  "BAPI Structure: Customer, General Data
   I_ADDRESS =  "BAPI Structure: Customer Address
   I_ADRCHANGE =  "BAPI Change Structure: Correction Structure BAPICUSADR
   I_SALESORG =  "BAPI Structure: Customer/Sales Data
   I_TAXDATA =  "BAPI Structure: Customer Control Data

 IMPORTING
   E_STATUS =  "

TABLES
   TI_STDTEL =  "BAPI Structure: Telephone (Business Address Services)
*  TI_ROLECHANGE =  "BAPI Structure Customer Master - Partner Roles
   TI_EXTENSION =  "Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT
   TI_SFA_KEYS =  "Input Table Structure for SFA Key in Proxy Function Module
   TI_STDFAX =  "BAPI Structure: Fax Numbers (Business Address Services)
   TI_STDTTX =  "BAPI Structure: Teletex Numbers (Business Address Services)
   TI_STDTLX =  "BAPI Structure: Telex Numbers (Business Address Services)
   TI_STDMAIL =  "BAPI Structure: E-Mail Addresses (Business Address Services)
*  TI_BANK =  "BAPI Structure: Customer Bank Data
*  TI_LOADING_POINTS =  "BAPI Structure: Customer, Unloading Point
   TI_ROLES =  "BAPI Structure: Customer, Partner Roles
*  TI_BANKCHANGE =  "BAPI Structure Customer Mastser - Bank Details
.



IMPORTING Parameters details for BAPI_CUSTOMERCRM_CHANGE

I_UPLOAD_ID - Unique Reference Number

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

I_BANKCHANGE - Single-Character Flag

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

I_TRANS_MODE - Single-Character Flag

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

I_ORIGIN - Origin of Upload Object

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

I_CUSTCHANGE - BAPI Structure Master - General Data

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

I_SALESCHANGE - BAPI Structure Customer Master Data: Sales Data

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

I_DESTIN - RFC Destination Server System

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

I_SFA_REL - SFA Release in server system

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

I_KEYWORD_IN - Keyword for customer enhancements

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

I_CUSTOMER - BAPI Structure: Customer, General Data

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

I_ADDRESS - BAPI Structure: Customer Address

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

I_ADRCHANGE - BAPI Change Structure: Correction Structure BAPICUSADR

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

I_SALESORG - BAPI Structure: Customer/Sales Data

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

I_TAXDATA - BAPI Structure: Customer Control Data

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

EXPORTING Parameters details for BAPI_CUSTOMERCRM_CHANGE

E_STATUS -

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

TABLES Parameters details for BAPI_CUSTOMERCRM_CHANGE

TI_STDTEL - BAPI Structure: Telephone (Business Address Services)

Data type: BAPICUSTEL
Optional: No
Call by Reference: Yes

TI_ROLECHANGE - BAPI Structure Customer Master - Partner Roles

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

TI_EXTENSION - Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT

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

TI_SFA_KEYS - Input Table Structure for SFA Key in Proxy Function Module

Data type: BAPICRMSFK
Optional: No
Call by Reference: Yes

TI_STDFAX - BAPI Structure: Fax Numbers (Business Address Services)

Data type: BAPICUSFAX
Optional: No
Call by Reference: Yes

TI_STDTTX - BAPI Structure: Teletex Numbers (Business Address Services)

Data type: BAPICUSTTX
Optional: No
Call by Reference: Yes

TI_STDTLX - BAPI Structure: Telex Numbers (Business Address Services)

Data type: BAPICUSTLX
Optional: No
Call by Reference: Yes

TI_STDMAIL - BAPI Structure: E-Mail Addresses (Business Address Services)

Data type: BAPICSMAIL
Optional: No
Call by Reference: Yes

TI_BANK - BAPI Structure: Customer Bank Data

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

TI_LOADING_POINTS - BAPI Structure: Customer, Unloading Point

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

TI_ROLES - BAPI Structure: Customer, Partner Roles

Data type: BAPICUSPAR
Optional: No
Call by Reference: Yes

TI_BANKCHANGE - BAPI Structure Customer Mastser - Bank Details

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

Copy and paste ABAP code example for BAPI_CUSTOMERCRM_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:
lv_e_status  TYPE CRM_PARA-UPLOADSTAT, "   
lt_ti_stdtel  TYPE STANDARD TABLE OF BAPICUSTEL, "   
lv_i_upload_id  TYPE BAPICRMDH2-REF_ID, "   
lv_i_bankchange  TYPE BAPIFLAG-BAPIFLAG, "   
lt_ti_rolechange  TYPE STANDARD TABLE OF BAPICUSPTX, "   
lv_i_trans_mode  TYPE BAPIFLAG-BAPIFLAG, "   
lt_ti_extension  TYPE STANDARD TABLE OF BAPIPAREX, "   
lv_i_origin  TYPE CRM_PARA-ORIGIN, "   
lt_ti_sfa_keys  TYPE STANDARD TABLE OF BAPICRMSFK, "   
lv_i_custchange  TYPE BAPICUSCHX, "   
lv_i_saleschange  TYPE BAPICUSSLX, "   
lv_i_destin  TYPE CRM_PARA-RFCSERVER, "   
lt_ti_stdfax  TYPE STANDARD TABLE OF BAPICUSFAX, "   
lv_i_sfa_rel  TYPE CRM_PARA-SERVER_REL, "   
lt_ti_stdttx  TYPE STANDARD TABLE OF BAPICUSTTX, "   
lt_ti_stdtlx  TYPE STANDARD TABLE OF BAPICUSTLX, "   
lv_i_keyword_in  TYPE CRM_PARA-KEYWORD_IN, "   
lv_i_customer  TYPE BAPICUSGEN, "   
lt_ti_stdmail  TYPE STANDARD TABLE OF BAPICSMAIL, "   
lt_ti_bank  TYPE STANDARD TABLE OF BAPICUSBK, "   
lv_i_address  TYPE BAPICUSADR, "   
lv_i_adrchange  TYPE BAPICUSADX, "   
lt_ti_loading_points  TYPE STANDARD TABLE OF BAPICUSLDP, "   
lt_ti_roles  TYPE STANDARD TABLE OF BAPICUSPAR, "   
lv_i_salesorg  TYPE BAPICUSSLS, "   
lv_i_taxdata  TYPE BAPICUSTAX, "   
lt_ti_bankchange  TYPE STANDARD TABLE OF BAPICUSBKX. "   

  CALL FUNCTION 'BAPI_CUSTOMERCRM_CHANGE'  "Proxy BAPI for Customer Upload in SFA Context: Customer Data Changes
    EXPORTING
         I_UPLOAD_ID = lv_i_upload_id
         I_BANKCHANGE = lv_i_bankchange
         I_TRANS_MODE = lv_i_trans_mode
         I_ORIGIN = lv_i_origin
         I_CUSTCHANGE = lv_i_custchange
         I_SALESCHANGE = lv_i_saleschange
         I_DESTIN = lv_i_destin
         I_SFA_REL = lv_i_sfa_rel
         I_KEYWORD_IN = lv_i_keyword_in
         I_CUSTOMER = lv_i_customer
         I_ADDRESS = lv_i_address
         I_ADRCHANGE = lv_i_adrchange
         I_SALESORG = lv_i_salesorg
         I_TAXDATA = lv_i_taxdata
    IMPORTING
         E_STATUS = lv_e_status
    TABLES
         TI_STDTEL = lt_ti_stdtel
         TI_ROLECHANGE = lt_ti_rolechange
         TI_EXTENSION = lt_ti_extension
         TI_SFA_KEYS = lt_ti_sfa_keys
         TI_STDFAX = lt_ti_stdfax
         TI_STDTTX = lt_ti_stdttx
         TI_STDTLX = lt_ti_stdtlx
         TI_STDMAIL = lt_ti_stdmail
         TI_BANK = lt_ti_bank
         TI_LOADING_POINTS = lt_ti_loading_points
         TI_ROLES = lt_ti_roles
         TI_BANKCHANGE = lt_ti_bankchange
. " BAPI_CUSTOMERCRM_CHANGE




ABAP code using 7.40 inline data declarations to call FM BAPI_CUSTOMERCRM_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 UPLOADSTAT FROM CRM_PARA INTO @DATA(ld_e_status).
 
 
"SELECT single REF_ID FROM BAPICRMDH2 INTO @DATA(ld_i_upload_id).
 
"SELECT single BAPIFLAG FROM BAPIFLAG INTO @DATA(ld_i_bankchange).
 
 
"SELECT single BAPIFLAG FROM BAPIFLAG INTO @DATA(ld_i_trans_mode).
 
 
"SELECT single ORIGIN FROM CRM_PARA INTO @DATA(ld_i_origin).
 
 
 
 
"SELECT single RFCSERVER FROM CRM_PARA INTO @DATA(ld_i_destin).
 
 
"SELECT single SERVER_REL FROM CRM_PARA INTO @DATA(ld_i_sfa_rel).
 
 
 
"SELECT single KEYWORD_IN FROM CRM_PARA INTO @DATA(ld_i_keyword_in).
 
 
 
 
 
 
 
 
 
 
 


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!