SAP OBJECT_NUMBER_BORKEY_GET_VB Function Module for NOTRANSL: Objektnummer Verkaufsbelege: BOR-Schlüssel ermitteln









OBJECT_NUMBER_BORKEY_GET_VB is a standard object number borkey get vb SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Objektnummer Verkaufsbelege: BOR-Schlüssel ermitteln processing and below is the pattern details for this FM, 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 object number borkey get vb FM, simply by entering the name OBJECT_NUMBER_BORKEY_GET_VB into the relevant SAP transaction such as SE37 or SE38.

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



Function OBJECT_NUMBER_BORKEY_GET_VB 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 'OBJECT_NUMBER_BORKEY_GET_VB'"NOTRANSL: Objektnummer Verkaufsbelege: BOR-Schlüssel ermitteln
EXPORTING
I_OBJNR = "Object Number

IMPORTING
E_OBJKEY = "BOR Object Key

EXCEPTIONS
KEY_TOO_LONG = 1 OBART_INVALID = 2
.



IMPORTING Parameters details for OBJECT_NUMBER_BORKEY_GET_VB

I_OBJNR - Object Number

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

EXPORTING Parameters details for OBJECT_NUMBER_BORKEY_GET_VB

E_OBJKEY - BOR Object Key

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

EXCEPTIONS details

KEY_TOO_LONG - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

OBART_INVALID - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for OBJECT_NUMBER_BORKEY_GET_VB 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_objnr  TYPE J_OBJNR, "   
lv_e_objkey  TYPE SWO_TYPEID, "   
lv_key_too_long  TYPE SWO_TYPEID, "   
lv_obart_invalid  TYPE SWO_TYPEID. "   

  CALL FUNCTION 'OBJECT_NUMBER_BORKEY_GET_VB'  "NOTRANSL: Objektnummer Verkaufsbelege: BOR-Schlüssel ermitteln
    EXPORTING
         I_OBJNR = lv_i_objnr
    IMPORTING
         E_OBJKEY = lv_e_objkey
    EXCEPTIONS
        KEY_TOO_LONG = 1
        OBART_INVALID = 2
. " OBJECT_NUMBER_BORKEY_GET_VB




ABAP code using 7.40 inline data declarations to call FM OBJECT_NUMBER_BORKEY_GET_VB

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!