SAP FPB_LP_GET_OBJECT_ID Function Module for NOTRANSL: liefert techn. Schlüssel für Kontext für Berichtsliste
FPB_LP_GET_OBJECT_ID is a standard fpb lp get object id 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: liefert techn. Schlüssel für Kontext für Berichtsliste 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 fpb lp get object id FM, simply by entering the name FPB_LP_GET_OBJECT_ID into the relevant SAP transaction such as SE37 or SE38.
Function Group: FPB_LAUNCHPAD_3
Program Name: SAPLFPB_LAUNCHPAD_3
Main Program: SAPLFPB_LAUNCHPAD_3
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FPB_LP_GET_OBJECT_ID 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 'FPB_LP_GET_OBJECT_ID'"NOTRANSL: liefert techn. Schlüssel für Kontext für Berichtsliste.
EXPORTING
ID_ROLE = "Role
ID_INSTANCE = "Instance
ID_OBJ_TYPE = "Object Type for Communication
ID_ADD_CRIT = "Character field, length 32
* ID_TEST_RUN = ' ' "Single-Character Indicator
IMPORTING
ED_OBJECT_ID = "Character field, length 32
EXCEPTIONS
ERROR_ENQUEUE = 1 ERROR_MODIFY = 2 ERROR_DATABASE_LOCKED = 3 INTERNAL_ERROR = 4
IMPORTING Parameters details for FPB_LP_GET_OBJECT_ID
ID_ROLE - Role
Data type: FPB_ROLEOptional: No
Call by Reference: Yes
ID_INSTANCE - Instance
Data type: FPB_APPLOptional: No
Call by Reference: Yes
ID_OBJ_TYPE - Object Type for Communication
Data type: FPB_OBJTYPEOptional: No
Call by Reference: Yes
ID_ADD_CRIT - Character field, length 32
Data type: CHAR32Optional: No
Call by Reference: Yes
ID_TEST_RUN - Single-Character Indicator
Data type: CHAR1Default: SPACE
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FPB_LP_GET_OBJECT_ID
ED_OBJECT_ID - Character field, length 32
Data type: CHAR32Optional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR_ENQUEUE - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
ERROR_MODIFY - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
ERROR_DATABASE_LOCKED - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
INTERNAL_ERROR - Internal error
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FPB_LP_GET_OBJECT_ID 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_id_role | TYPE FPB_ROLE, " | |||
| lv_ed_object_id | TYPE CHAR32, " | |||
| lv_error_enqueue | TYPE CHAR32, " | |||
| lv_id_instance | TYPE FPB_APPL, " | |||
| lv_error_modify | TYPE FPB_APPL, " | |||
| lv_id_obj_type | TYPE FPB_OBJTYPE, " | |||
| lv_error_database_locked | TYPE FPB_OBJTYPE, " | |||
| lv_id_add_crit | TYPE CHAR32, " | |||
| lv_internal_error | TYPE CHAR32, " | |||
| lv_id_test_run | TYPE CHAR1. " SPACE |
|   CALL FUNCTION 'FPB_LP_GET_OBJECT_ID' "NOTRANSL: liefert techn. Schlüssel für Kontext für Berichtsliste |
| EXPORTING | ||
| ID_ROLE | = lv_id_role | |
| ID_INSTANCE | = lv_id_instance | |
| ID_OBJ_TYPE | = lv_id_obj_type | |
| ID_ADD_CRIT | = lv_id_add_crit | |
| ID_TEST_RUN | = lv_id_test_run | |
| IMPORTING | ||
| ED_OBJECT_ID | = lv_ed_object_id | |
| EXCEPTIONS | ||
| ERROR_ENQUEUE = 1 | ||
| ERROR_MODIFY = 2 | ||
| ERROR_DATABASE_LOCKED = 3 | ||
| INTERNAL_ERROR = 4 | ||
| . " FPB_LP_GET_OBJECT_ID | ||
ABAP code using 7.40 inline data declarations to call FM FPB_LP_GET_OBJECT_ID
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.| DATA(ld_id_test_run) | = ' '. | |||
Search for further information about these or an SAP related objects