SAP FPB_LP_GET_PERS_REPORT_DETAILS Function Module for NOTRANSL: nutzerspezifische Anpassung: DB --> Frontend
FPB_LP_GET_PERS_REPORT_DETAILS is a standard fpb lp get pers report details 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: nutzerspezifische Anpassung: DB --> Frontend 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 pers report details FM, simply by entering the name FPB_LP_GET_PERS_REPORT_DETAILS 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): Remote-Enabled
Update:

Function FPB_LP_GET_PERS_REPORT_DETAILS 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_PERS_REPORT_DETAILS'"NOTRANSL: nutzerspezifische Anpassung: DB --> Frontend.
EXPORTING
ID_OBJ_ID = "Object ID
ID_REPORT_ID = "Application name
ID_REPORT_SUB_ID = "Four-digit number
* ID_UNAME = SY-UNAME "User Name
* ID_LANGU = SY-LANGU "Language Key of Current Text Environment
* ID_DO_USE_BW_PERS = "Single-Character Indicator
IMPORTING
ES_DETAILS = "User-Specific Details on Report
IMPORTING Parameters details for FPB_LP_GET_PERS_REPORT_DETAILS
ID_OBJ_ID - Object ID
Data type: CHAR32Optional: No
Call by Reference: No ( called with pass by value option)
ID_REPORT_ID - Application name
Data type: FPB_REPORT_NAMEOptional: No
Call by Reference: No ( called with pass by value option)
ID_REPORT_SUB_ID - Four-digit number
Data type: NUM4Optional: No
Call by Reference: No ( called with pass by value option)
ID_UNAME - User Name
Data type: SY-UNAMEDefault: SY-UNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)
ID_LANGU - Language Key of Current Text Environment
Data type: SY-LANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)
ID_DO_USE_BW_PERS - Single-Character Indicator
Data type: CHAR1Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FPB_LP_GET_PERS_REPORT_DETAILS
ES_DETAILS - User-Specific Details on Report
Data type: FPB_RL_S_PERS_REPORT_DETAILSOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FPB_LP_GET_PERS_REPORT_DETAILS 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_obj_id | TYPE CHAR32, " | |||
| lv_es_details | TYPE FPB_RL_S_PERS_REPORT_DETAILS, " | |||
| lv_id_report_id | TYPE FPB_REPORT_NAME, " | |||
| lv_id_report_sub_id | TYPE NUM4, " | |||
| lv_id_uname | TYPE SY-UNAME, " SY-UNAME | |||
| lv_id_langu | TYPE SY-LANGU, " SY-LANGU | |||
| lv_id_do_use_bw_pers | TYPE CHAR1. " |
|   CALL FUNCTION 'FPB_LP_GET_PERS_REPORT_DETAILS' "NOTRANSL: nutzerspezifische Anpassung: DB --> Frontend |
| EXPORTING | ||
| ID_OBJ_ID | = lv_id_obj_id | |
| ID_REPORT_ID | = lv_id_report_id | |
| ID_REPORT_SUB_ID | = lv_id_report_sub_id | |
| ID_UNAME | = lv_id_uname | |
| ID_LANGU | = lv_id_langu | |
| ID_DO_USE_BW_PERS | = lv_id_do_use_bw_pers | |
| IMPORTING | ||
| ES_DETAILS | = lv_es_details | |
| . " FPB_LP_GET_PERS_REPORT_DETAILS | ||
ABAP code using 7.40 inline data declarations to call FM FPB_LP_GET_PERS_REPORT_DETAILS
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 UNAME FROM SY INTO @DATA(ld_id_uname). | ||||
| DATA(ld_id_uname) | = SY-UNAME. | |||
| "SELECT single LANGU FROM SY INTO @DATA(ld_id_langu). | ||||
| DATA(ld_id_langu) | = SY-LANGU. | |||
Search for further information about these or an SAP related objects