SAP BUPR_CONTP_ADDR_GET_DETAIL Function Module for
BUPR_CONTP_ADDR_GET_DETAIL is a standard bupr contp addr get detail 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 bupr contp addr get detail FM, simply by entering the name BUPR_CONTP_ADDR_GET_DETAIL 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 BUPR_CONTP_ADDR_GET_DETAIL 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 'BUPR_CONTP_ADDR_GET_DETAIL'".
EXPORTING
* IV_PARTNER = "
* IV_PARTNER_GUID = "
* IV_CONTACTPERSON = "
* IV_CONTACTPERSON_GUID = "
* IV_ADDRNUMBER = "
* IV_ADDRGUID = "
IMPORTING
ES_ADDRESS = "Address Data
TABLES
* ET_ADDR_VERS = "
* ET_ADPRT = "PRT Addresses
* ET_ADSSF = "SSF Addresses
* ET_ADURI = "URI Addresses
* ET_ADPAG = "Pager Numbers
* ET_COMREM = "Remarks for Communication Types
* ET_RETURN = "Messages
* ET_ADTEL = "Telephone Number
* ET_ADFAX = "Fax Number
* ET_ADTTX = "Teletext Number
* ET_ADTLX = "Telex Number
* ET_ADSMTP = "E-Mail Addresses
* ET_ADRML = "RML Addresses
* ET_ADX400 = "X400 Addresses
* ET_ADRFC = "RFC Addresses
IMPORTING Parameters details for BUPR_CONTP_ADDR_GET_DETAIL
IV_PARTNER -
Data type: BU_PARTNEROptional: Yes
Call by Reference: No ( called with pass by value option)
IV_PARTNER_GUID -
Data type: BU_PARTNER_GUIDOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_CONTACTPERSON -
Data type: BU_PARTNEROptional: Yes
Call by Reference: No ( called with pass by value option)
IV_CONTACTPERSON_GUID -
Data type: BU_PARTNER_GUIDOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_ADDRNUMBER -
Data type: AD_ADDRNUMOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_ADDRGUID -
Data type: BU_ADDRESS_GUIDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BUPR_CONTP_ADDR_GET_DETAIL
ES_ADDRESS - Address Data
Data type: BAPIBUS1006002_ADDRESSOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BUPR_CONTP_ADDR_GET_DETAIL
ET_ADDR_VERS -
Data type: BAPIAD3VLOptional: Yes
Call by Reference: Yes
ET_ADPRT - PRT Addresses
Data type: BAPIADPRTOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_ADSSF - SSF Addresses
Data type: BAPIADSSFOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_ADURI - URI Addresses
Data type: BAPIADURIOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_ADPAG - Pager Numbers
Data type: BAPIADPAGOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_COMREM - Remarks for Communication Types
Data type: BAPICOMREMOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_RETURN - Messages
Data type: BAPIRET2Optional: Yes
Call by Reference: No ( called with pass by value option)
ET_ADTEL - Telephone Number
Data type: BAPIADTELOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_ADFAX - Fax Number
Data type: BAPIADFAXOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_ADTTX - Teletext Number
Data type: BAPIADTTXOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_ADTLX - Telex Number
Data type: BAPIADTLXOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_ADSMTP - E-Mail Addresses
Data type: BAPIADSMTPOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_ADRML - RML Addresses
Data type: BAPIADRMLOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_ADX400 - X400 Addresses
Data type: BAPIADX400Optional: Yes
Call by Reference: No ( called with pass by value option)
ET_ADRFC - RFC Addresses
Data type: BAPIADRFCOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BUPR_CONTP_ADDR_GET_DETAIL 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_es_address | TYPE BAPIBUS1006002_ADDRESS, " | |||
lv_iv_partner | TYPE BU_PARTNER, " | |||
lt_et_addr_vers | TYPE STANDARD TABLE OF BAPIAD3VL, " | |||
lt_et_adprt | TYPE STANDARD TABLE OF BAPIADPRT, " | |||
lt_et_adssf | TYPE STANDARD TABLE OF BAPIADSSF, " | |||
lt_et_aduri | TYPE STANDARD TABLE OF BAPIADURI, " | |||
lt_et_adpag | TYPE STANDARD TABLE OF BAPIADPAG, " | |||
lt_et_comrem | TYPE STANDARD TABLE OF BAPICOMREM, " | |||
lt_et_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
lt_et_adtel | TYPE STANDARD TABLE OF BAPIADTEL, " | |||
lv_iv_partner_guid | TYPE BU_PARTNER_GUID, " | |||
lt_et_adfax | TYPE STANDARD TABLE OF BAPIADFAX, " | |||
lv_iv_contactperson | TYPE BU_PARTNER, " | |||
lt_et_adttx | TYPE STANDARD TABLE OF BAPIADTTX, " | |||
lv_iv_contactperson_guid | TYPE BU_PARTNER_GUID, " | |||
lt_et_adtlx | TYPE STANDARD TABLE OF BAPIADTLX, " | |||
lv_iv_addrnumber | TYPE AD_ADDRNUM, " | |||
lt_et_adsmtp | TYPE STANDARD TABLE OF BAPIADSMTP, " | |||
lv_iv_addrguid | TYPE BU_ADDRESS_GUID, " | |||
lt_et_adrml | TYPE STANDARD TABLE OF BAPIADRML, " | |||
lt_et_adx400 | TYPE STANDARD TABLE OF BAPIADX400, " | |||
lt_et_adrfc | TYPE STANDARD TABLE OF BAPIADRFC. " |
  CALL FUNCTION 'BUPR_CONTP_ADDR_GET_DETAIL' " |
EXPORTING | ||
IV_PARTNER | = lv_iv_partner | |
IV_PARTNER_GUID | = lv_iv_partner_guid | |
IV_CONTACTPERSON | = lv_iv_contactperson | |
IV_CONTACTPERSON_GUID | = lv_iv_contactperson_guid | |
IV_ADDRNUMBER | = lv_iv_addrnumber | |
IV_ADDRGUID | = lv_iv_addrguid | |
IMPORTING | ||
ES_ADDRESS | = lv_es_address | |
TABLES | ||
ET_ADDR_VERS | = lt_et_addr_vers | |
ET_ADPRT | = lt_et_adprt | |
ET_ADSSF | = lt_et_adssf | |
ET_ADURI | = lt_et_aduri | |
ET_ADPAG | = lt_et_adpag | |
ET_COMREM | = lt_et_comrem | |
ET_RETURN | = lt_et_return | |
ET_ADTEL | = lt_et_adtel | |
ET_ADFAX | = lt_et_adfax | |
ET_ADTTX | = lt_et_adttx | |
ET_ADTLX | = lt_et_adtlx | |
ET_ADSMTP | = lt_et_adsmtp | |
ET_ADRML | = lt_et_adrml | |
ET_ADX400 | = lt_et_adx400 | |
ET_ADRFC | = lt_et_adrfc | |
. " BUPR_CONTP_ADDR_GET_DETAIL |
ABAP code using 7.40 inline data declarations to call FM BUPR_CONTP_ADDR_GET_DETAIL
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.Search for further information about these or an SAP related objects