SAP BAPI_IDENTIFICATION_CHANGE Function Module for SAP BP, BAPI: Change Identification Number
BAPI_IDENTIFICATION_CHANGE is a standard bapi identification 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 SAP BP, BAPI: Change Identification Number 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 identification change FM, simply by entering the name BAPI_IDENTIFICATION_CHANGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: BUBA_3
Program Name: SAPLBUBA_3
Main Program: SAPLBUBA_3
Appliation area:
Release date: 26-Nov-2001
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_IDENTIFICATION_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_IDENTIFICATION_CHANGE'"SAP BP, BAPI: Change Identification Number.
EXPORTING
BUSINESSPARTNER = "Business Partner Number
IDENTIFICATIONCATEGORY = "BP Identification Category
IDENTIFICATIONNUMBER = "BP Identification Number
IDENTIFICATION = "SAP BP: BAPI Structure for Identification Numbers
IDENTIFICATION_X = "SAP BP: BAPI Structure for Identification Number: Update Bar
TABLES
* RETURN = "Return Parameters
IMPORTING Parameters details for BAPI_IDENTIFICATION_CHANGE
BUSINESSPARTNER - Business Partner Number
Data type: BAPIBUS1006_HEAD-BPARTNEROptional: No
Call by Reference: No ( called with pass by value option)
IDENTIFICATIONCATEGORY - BP Identification Category
Data type: BAPIBUS1006_IDENTIFICATION_KEY-IDENTIFICATIONCATEGORYOptional: No
Call by Reference: No ( called with pass by value option)
IDENTIFICATIONNUMBER - BP Identification Number
Data type: BAPIBUS1006_IDENTIFICATION_KEY-IDENTIFICATIONNUMBEROptional: No
Call by Reference: No ( called with pass by value option)
IDENTIFICATION - SAP BP: BAPI Structure for Identification Numbers
Data type: BAPIBUS1006_IDENTIFICATIONOptional: No
Call by Reference: No ( called with pass by value option)
IDENTIFICATION_X - SAP BP: BAPI Structure for Identification Number: Update Bar
Data type: BAPIBUS1006_IDENTIFICATION_XOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_IDENTIFICATION_CHANGE
RETURN - Return Parameters
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_IDENTIFICATION_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_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_businesspartner | TYPE BAPIBUS1006_HEAD-BPARTNER, " | |||
| lv_identificationcategory | TYPE BAPIBUS1006_IDENTIFICATION_KEY-IDENTIFICATIONCATEGORY, " | |||
| lv_identificationnumber | TYPE BAPIBUS1006_IDENTIFICATION_KEY-IDENTIFICATIONNUMBER, " | |||
| lv_identification | TYPE BAPIBUS1006_IDENTIFICATION, " | |||
| lv_identification_x | TYPE BAPIBUS1006_IDENTIFICATION_X. " |
|   CALL FUNCTION 'BAPI_IDENTIFICATION_CHANGE' "SAP BP, BAPI: Change Identification Number |
| EXPORTING | ||
| BUSINESSPARTNER | = lv_businesspartner | |
| IDENTIFICATIONCATEGORY | = lv_identificationcategory | |
| IDENTIFICATIONNUMBER | = lv_identificationnumber | |
| IDENTIFICATION | = lv_identification | |
| IDENTIFICATION_X | = lv_identification_x | |
| TABLES | ||
| RETURN | = lt_return | |
| . " BAPI_IDENTIFICATION_CHANGE | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_IDENTIFICATION_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 BPARTNER FROM BAPIBUS1006_HEAD INTO @DATA(ld_businesspartner). | ||||
| "SELECT single IDENTIFICATIONCATEGORY FROM BAPIBUS1006_IDENTIFICATION_KEY INTO @DATA(ld_identificationcategory). | ||||
| "SELECT single IDENTIFICATIONNUMBER FROM BAPIBUS1006_IDENTIFICATION_KEY INTO @DATA(ld_identificationnumber). | ||||
Search for further information about these or an SAP related objects