SAP BUPA_IDENTIFICATION_ADD Function Module for









BUPA_IDENTIFICATION_ADD is a standard bupa identification add 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 bupa identification add FM, simply by entering the name BUPA_IDENTIFICATION_ADD into the relevant SAP transaction such as SE37 or SE38.

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



Function BUPA_IDENTIFICATION_ADD 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 'BUPA_IDENTIFICATION_ADD'"
EXPORTING
* IV_PARTNER = "Business Partner Number
* IV_PARTNER_GUID = "Business Partner GUID
* IV_IDENTIFICATIONCATEGORY = "BP Identification Category
IV_IDENTIFICATIONNUMBER = "BP Identification Number
IS_IDENTIFICATION = "SAP BP: BAPI Structure for Identification Numbers
* IV_X_SAVE = 'X' "Indicator: Save Address?
* IV_IDENTIFICATIONTYPE = "

TABLES
* ET_RETURN = "Return Parameters
.



IMPORTING Parameters details for BUPA_IDENTIFICATION_ADD

IV_PARTNER - Business Partner Number

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

IV_PARTNER_GUID - Business Partner GUID

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

IV_IDENTIFICATIONCATEGORY - BP Identification Category

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

IV_IDENTIFICATIONNUMBER - BP Identification Number

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

IS_IDENTIFICATION - SAP BP: BAPI Structure for Identification Numbers

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

IV_X_SAVE - Indicator: Save Address?

Data type: BAPI4001_1-SAVE_ADDR
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_IDENTIFICATIONTYPE -

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

TABLES Parameters details for BUPA_IDENTIFICATION_ADD

ET_RETURN - Return Parameters

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

Copy and paste ABAP code example for BUPA_IDENTIFICATION_ADD 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_et_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_iv_partner  TYPE BU_PARTNER, "   
lv_iv_partner_guid  TYPE BU_PARTNER_GUID, "   
lv_iv_identificationcategory  TYPE BAPIBUS1006_IDENTIFICATION_KEY-IDENTIFICATIONCATEGORY, "   
lv_iv_identificationnumber  TYPE BAPIBUS1006_IDENTIFICATION_KEY-IDENTIFICATIONNUMBER, "   
lv_is_identification  TYPE BAPIBUS1006_IDENTIFICATION, "   
lv_iv_x_save  TYPE BAPI4001_1-SAVE_ADDR, "   'X'
lv_iv_identificationtype  TYPE BU_ID_TYPE. "   

  CALL FUNCTION 'BUPA_IDENTIFICATION_ADD'  "
    EXPORTING
         IV_PARTNER = lv_iv_partner
         IV_PARTNER_GUID = lv_iv_partner_guid
         IV_IDENTIFICATIONCATEGORY = lv_iv_identificationcategory
         IV_IDENTIFICATIONNUMBER = lv_iv_identificationnumber
         IS_IDENTIFICATION = lv_is_identification
         IV_X_SAVE = lv_iv_x_save
         IV_IDENTIFICATIONTYPE = lv_iv_identificationtype
    TABLES
         ET_RETURN = lt_et_return
. " BUPA_IDENTIFICATION_ADD




ABAP code using 7.40 inline data declarations to call FM BUPA_IDENTIFICATION_ADD

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 IDENTIFICATIONCATEGORY FROM BAPIBUS1006_IDENTIFICATION_KEY INTO @DATA(ld_iv_identificationcategory).
 
"SELECT single IDENTIFICATIONNUMBER FROM BAPIBUS1006_IDENTIFICATION_KEY INTO @DATA(ld_iv_identificationnumber).
 
 
"SELECT single SAVE_ADDR FROM BAPI4001_1 INTO @DATA(ld_iv_x_save).
DATA(ld_iv_x_save) = 'X'.
 
 


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!