SAP BUP_IDNUMBER_DETERMINE Function Module for









BUP_IDNUMBER_DETERMINE is a standard bup idnumber determine 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 bup idnumber determine FM, simply by entering the name BUP_IDNUMBER_DETERMINE into the relevant SAP transaction such as SE37 or SE38.

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



Function BUP_IDNUMBER_DETERMINE 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 'BUP_IDNUMBER_DETERMINE'"
EXPORTING
* I_PARTNER = "Partner Number
* I_PARTNERGUID = "
* I_CATEGORY = "ID Categ.
* I_TYPE = "ID Type
* I_XMEMORY = ' ' "
* I_XWA = ' ' "
* I_VALDT = '00000000' "Validity Date
* I_VALDT_SEL = SY-DATLO "

IMPORTING
E_IDNUMBER = "ID Number

EXCEPTIONS
NO_IDNUMBER_FOUND = 1 WRONG_PARAMETERS = 2 INTERNAL_ERROR = 3 NOT_VALID = 4
.



IMPORTING Parameters details for BUP_IDNUMBER_DETERMINE

I_PARTNER - Partner Number

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

I_PARTNERGUID -

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

I_CATEGORY - ID Categ.

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

I_TYPE - ID Type

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

I_XMEMORY -

Data type: BOOLE-BOOLE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_XWA -

Data type: BOOLE-BOOLE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_VALDT - Validity Date

Data type: SY-DATLO
Default: '00000000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_VALDT_SEL -

Data type: SY-DATLO
Default: SY-DATLO
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BUP_IDNUMBER_DETERMINE

E_IDNUMBER - ID Number

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

EXCEPTIONS details

NO_IDNUMBER_FOUND -

Data type:
Optional: No
Call by Reference: Yes

WRONG_PARAMETERS - Wrong parameter passed

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

INTERNAL_ERROR - An internal error has occurred

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

NOT_VALID -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BUP_IDNUMBER_DETERMINE 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_i_partner  TYPE BUT000-PARTNER, "   
lv_e_idnumber  TYPE BUT0ID-IDNUMBER, "   
lv_no_idnumber_found  TYPE BUT0ID, "   
lv_i_partnerguid  TYPE BUT000-PARTNER_GUID, "   
lv_wrong_parameters  TYPE BUT000, "   
lv_i_category  TYPE TB039-CATEGORY, "   
lv_internal_error  TYPE TB039, "   
lv_i_type  TYPE BUT0ID-TYPE, "   
lv_not_valid  TYPE BUT0ID, "   
lv_i_xmemory  TYPE BOOLE-BOOLE, "   SPACE
lv_i_xwa  TYPE BOOLE-BOOLE, "   SPACE
lv_i_valdt  TYPE SY-DATLO, "   '00000000'
lv_i_valdt_sel  TYPE SY-DATLO. "   SY-DATLO

  CALL FUNCTION 'BUP_IDNUMBER_DETERMINE'  "
    EXPORTING
         I_PARTNER = lv_i_partner
         I_PARTNERGUID = lv_i_partnerguid
         I_CATEGORY = lv_i_category
         I_TYPE = lv_i_type
         I_XMEMORY = lv_i_xmemory
         I_XWA = lv_i_xwa
         I_VALDT = lv_i_valdt
         I_VALDT_SEL = lv_i_valdt_sel
    IMPORTING
         E_IDNUMBER = lv_e_idnumber
    EXCEPTIONS
        NO_IDNUMBER_FOUND = 1
        WRONG_PARAMETERS = 2
        INTERNAL_ERROR = 3
        NOT_VALID = 4
. " BUP_IDNUMBER_DETERMINE




ABAP code using 7.40 inline data declarations to call FM BUP_IDNUMBER_DETERMINE

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 PARTNER FROM BUT000 INTO @DATA(ld_i_partner).
 
"SELECT single IDNUMBER FROM BUT0ID INTO @DATA(ld_e_idnumber).
 
 
"SELECT single PARTNER_GUID FROM BUT000 INTO @DATA(ld_i_partnerguid).
 
 
"SELECT single CATEGORY FROM TB039 INTO @DATA(ld_i_category).
 
 
"SELECT single TYPE FROM BUT0ID INTO @DATA(ld_i_type).
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xmemory).
DATA(ld_i_xmemory) = ' '.
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xwa).
DATA(ld_i_xwa) = ' '.
 
"SELECT single DATLO FROM SY INTO @DATA(ld_i_valdt).
DATA(ld_i_valdt) = '00000000'.
 
"SELECT single DATLO FROM SY INTO @DATA(ld_i_valdt_sel).
DATA(ld_i_valdt_sel) = SY-DATLO.
 


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!