SAP BUPA_NUMBERS_READ Function Module for









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

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



Function BUPA_NUMBERS_READ 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_NUMBERS_READ'"
EXPORTING
* IV_PARTNER = "Business Partner Number
* IV_PARTNER_GUID = "Business Partner GUID
* IV_PARTNER_EXTERNAL = "Business Partner Number in External System
* IV_VALID_TIME = "Validity Time
* IV_RESET_BUFFER = "

IMPORTING
EV_PARTNER = "Business Partner Number
EV_PARTNER_GUID = "Business Partner GUID
EV_PARTNER_EXTERNAL = "Business Partner Number in External System
ES_BUT000 = "

EXCEPTIONS
NO_PARTNER_SPECIFIED = 1 NO_VALID_RECORD_FOUND = 2 INCONSISTENT_PARAMETERS = 3
.



IMPORTING Parameters details for BUPA_NUMBERS_READ

IV_PARTNER - Business Partner Number

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

IV_PARTNER_GUID - Business Partner GUID

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

IV_PARTNER_EXTERNAL - Business Partner Number in External System

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

IV_VALID_TIME - Validity Time

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

IV_RESET_BUFFER -

Data type: BOOLE-BOOLE
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for BUPA_NUMBERS_READ

EV_PARTNER - Business Partner Number

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

EV_PARTNER_GUID - Business Partner GUID

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

EV_PARTNER_EXTERNAL - Business Partner Number in External System

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

ES_BUT000 -

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

EXCEPTIONS details

NO_PARTNER_SPECIFIED -

Data type:
Optional: No
Call by Reference: Yes

NO_VALID_RECORD_FOUND -

Data type:
Optional: No
Call by Reference: Yes

INCONSISTENT_PARAMETERS -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BUPA_NUMBERS_READ 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_ev_partner  TYPE BU_PARTNER, "   
lv_iv_partner  TYPE BU_PARTNER, "   
lv_no_partner_specified  TYPE BU_PARTNER, "   
lv_ev_partner_guid  TYPE BU_PARTNER_GUID, "   
lv_iv_partner_guid  TYPE BU_PARTNER_GUID, "   
lv_no_valid_record_found  TYPE BU_PARTNER_GUID, "   
lv_ev_partner_external  TYPE BU_BPEXT, "   
lv_iv_partner_external  TYPE BU_BPEXT, "   
lv_inconsistent_parameters  TYPE BU_BPEXT, "   
lv_es_but000  TYPE BUT000, "   
lv_iv_valid_time  TYPE TIMESTAMP, "   
lv_iv_reset_buffer  TYPE BOOLE-BOOLE. "   

  CALL FUNCTION 'BUPA_NUMBERS_READ'  "
    EXPORTING
         IV_PARTNER = lv_iv_partner
         IV_PARTNER_GUID = lv_iv_partner_guid
         IV_PARTNER_EXTERNAL = lv_iv_partner_external
         IV_VALID_TIME = lv_iv_valid_time
         IV_RESET_BUFFER = lv_iv_reset_buffer
    IMPORTING
         EV_PARTNER = lv_ev_partner
         EV_PARTNER_GUID = lv_ev_partner_guid
         EV_PARTNER_EXTERNAL = lv_ev_partner_external
         ES_BUT000 = lv_es_but000
    EXCEPTIONS
        NO_PARTNER_SPECIFIED = 1
        NO_VALID_RECORD_FOUND = 2
        INCONSISTENT_PARAMETERS = 3
. " BUPA_NUMBERS_READ




ABAP code using 7.40 inline data declarations to call FM BUPA_NUMBERS_READ

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 BOOLE FROM BOOLE INTO @DATA(ld_iv_reset_buffer).
 


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!