SAP DRB_OBJKEY_FORMAT Function Module for
DRB_OBJKEY_FORMAT is a standard drb objkey format 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 drb objkey format FM, simply by entering the name DRB_OBJKEY_FORMAT into the relevant SAP transaction such as SE37 or SE38.
Function Group: ASH0
Program Name: SAPLASH0
Main Program: SAPLASH0
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function DRB_OBJKEY_FORMAT 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 'DRB_OBJKEY_FORMAT'".
EXPORTING
I_BORIDENT = "Object Relationship Service: BOR Object Identifier
IMPORTING
E_OUTPUT = "Text/Icon/Symbol
TABLES
* T_MESSAGES = "DRB: Message
IMPORTING Parameters details for DRB_OBJKEY_FORMAT
I_BORIDENT - Object Relationship Service: BOR Object Identifier
Data type: BORIDENTOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DRB_OBJKEY_FORMAT
E_OUTPUT - Text/Icon/Symbol
Data type: SDRBBOR-BITM_DESCROptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for DRB_OBJKEY_FORMAT
T_MESSAGES - DRB: Message
Data type: SDRBMSGOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for DRB_OBJKEY_FORMAT 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_e_output | TYPE SDRBBOR-BITM_DESCR, " | |||
| lv_i_borident | TYPE BORIDENT, " | |||
| lt_t_messages | TYPE STANDARD TABLE OF SDRBMSG. " |
|   CALL FUNCTION 'DRB_OBJKEY_FORMAT' " |
| EXPORTING | ||
| I_BORIDENT | = lv_i_borident | |
| IMPORTING | ||
| E_OUTPUT | = lv_e_output | |
| TABLES | ||
| T_MESSAGES | = lt_t_messages | |
| . " DRB_OBJKEY_FORMAT | ||
ABAP code using 7.40 inline data declarations to call FM DRB_OBJKEY_FORMAT
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 BITM_DESCR FROM SDRBBOR INTO @DATA(ld_e_output). | ||||
Search for further information about these or an SAP related objects