SAP BBP_GET_BILLFROM_ADDR Function Module for









BBP_GET_BILLFROM_ADDR is a standard bbp get billfrom addr 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 bbp get billfrom addr FM, simply by entering the name BBP_GET_BILLFROM_ADDR into the relevant SAP transaction such as SE37 or SE38.

Function Group: BBP_BUPA_ADDR
Program Name: SAPLBBP_BUPA_ADDR
Main Program: SAPLBBP_BUPA_ADDR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function BBP_GET_BILLFROM_ADDR 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 'BBP_GET_BILLFROM_ADDR'"
  EXPORTING
*  IV_PARTNER =  "
*  IV_PARTNER_GUID =  "

 IMPORTING
   EV_STANDARD =  "
   EV_DEFAULT =  "
   ES_ADDRESS =  "
   ES_CENTRAL =  "
   ES_CENTRAL_ORGAN =  "

TABLES
*  ET_RETURN =  "

EXCEPTIONS
   TYPES_NOT_MAINTAINED = 1    ADDRESS_NOT_FOUND = 2    CENTRAL_NOT_FOUND = 3    CENTRAL_ORGAN_NOT_FOUND = 4    PARTNER_NOT_FOUND = 5
.



IMPORTING Parameters details for BBP_GET_BILLFROM_ADDR

IV_PARTNER -

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

IV_PARTNER_GUID -

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

EXPORTING Parameters details for BBP_GET_BILLFROM_ADDR

EV_STANDARD -

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

EV_DEFAULT -

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

ES_ADDRESS -

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

ES_CENTRAL -

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

ES_CENTRAL_ORGAN -

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

TABLES Parameters details for BBP_GET_BILLFROM_ADDR

ET_RETURN -

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

EXCEPTIONS details

TYPES_NOT_MAINTAINED -

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

ADDRESS_NOT_FOUND -

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

CENTRAL_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

CENTRAL_ORGAN_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

PARTNER_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BBP_GET_BILLFROM_ADDR 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_ev_standard  TYPE XFELD, "   
lv_types_not_maintained  TYPE XFELD, "   
lv_ev_default  TYPE XFELD, "   
lv_iv_partner_guid  TYPE BU_PARTNER_GUID, "   
lv_address_not_found  TYPE BU_PARTNER_GUID, "   
lv_es_address  TYPE BUS020_EXT, "   
lv_central_not_found  TYPE BUS020_EXT, "   
lv_es_central  TYPE BAPIBUS1006_CENTRAL, "   
lv_central_organ_not_found  TYPE BAPIBUS1006_CENTRAL, "   
lv_es_central_organ  TYPE BAPIBUS1006_CENTRAL_ORGAN, "   
lv_partner_not_found  TYPE BAPIBUS1006_CENTRAL_ORGAN. "   

  CALL FUNCTION 'BBP_GET_BILLFROM_ADDR'  "
    EXPORTING
         IV_PARTNER = lv_iv_partner
         IV_PARTNER_GUID = lv_iv_partner_guid
    IMPORTING
         EV_STANDARD = lv_ev_standard
         EV_DEFAULT = lv_ev_default
         ES_ADDRESS = lv_es_address
         ES_CENTRAL = lv_es_central
         ES_CENTRAL_ORGAN = lv_es_central_organ
    TABLES
         ET_RETURN = lt_et_return
    EXCEPTIONS
        TYPES_NOT_MAINTAINED = 1
        ADDRESS_NOT_FOUND = 2
        CENTRAL_NOT_FOUND = 3
        CENTRAL_ORGAN_NOT_FOUND = 4
        PARTNER_NOT_FOUND = 5
. " BBP_GET_BILLFROM_ADDR




ABAP code using 7.40 inline data declarations to call FM BBP_GET_BILLFROM_ADDR

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



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!