SAP UJH_API_GET_PAGE Function Module for BPC: Get a page
UJH_API_GET_PAGE is a standard ujh api get page SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BPC: Get a page 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 ujh api get page FM, simply by entering the name UJH_API_GET_PAGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: UJH0
Program Name: SAPLUJH0
Main Program: SAPLUJH0
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function UJH_API_GET_PAGE 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 'UJH_API_GET_PAGE'"BPC: Get a page.
EXPORTING
I_APPSET_ID = "BPC: AppSet ID
IS_USER = "BPC: User Login Info
I_CONTENT_ID = "BPC: Unique ID (CHAR 22)
IMPORTING
ET_MESSAGE_LINES = "BPC: Messages
E_SUCCESS = "BPC: Bool
ET_CONTENT = "BPC: Content detail for API
ET_RCPT_USER = "BPC: Content recipient user
ET_RCPT_TEAM = "BPC: Content recipient team
ET_CONTENT_OBJ = "BPC: Content Object
IMPORTING Parameters details for UJH_API_GET_PAGE
I_APPSET_ID - BPC: AppSet ID
Data type: UJA_APPSET_INFO-APPSET_IDOptional: No
Call by Reference: No ( called with pass by value option)
IS_USER - BPC: User Login Info
Data type: UJ0_S_USEROptional: No
Call by Reference: No ( called with pass by value option)
I_CONTENT_ID - BPC: Unique ID (CHAR 22)
Data type: UJ0_UNI_IDCOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for UJH_API_GET_PAGE
ET_MESSAGE_LINES - BPC: Messages
Data type: UJ0_T_MESSAGEOptional: No
Call by Reference: No ( called with pass by value option)
E_SUCCESS - BPC: Bool
Data type: UJ_BOOLOptional: No
Call by Reference: No ( called with pass by value option)
ET_CONTENT - BPC: Content detail for API
Data type: UJH_T_API_CONTENTOptional: No
Call by Reference: No ( called with pass by value option)
ET_RCPT_USER - BPC: Content recipient user
Data type: UJH_T_RCPT_USEROptional: No
Call by Reference: No ( called with pass by value option)
ET_RCPT_TEAM - BPC: Content recipient team
Data type: UJH_T_RCPT_TEAMOptional: No
Call by Reference: No ( called with pass by value option)
ET_CONTENT_OBJ - BPC: Content Object
Data type: UJH_T_CONTENT_OBJOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for UJH_API_GET_PAGE 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_appset_id | TYPE UJA_APPSET_INFO-APPSET_ID, " | |||
| lv_et_message_lines | TYPE UJ0_T_MESSAGE, " | |||
| lv_is_user | TYPE UJ0_S_USER, " | |||
| lv_e_success | TYPE UJ_BOOL, " | |||
| lv_et_content | TYPE UJH_T_API_CONTENT, " | |||
| lv_i_content_id | TYPE UJ0_UNI_IDC, " | |||
| lv_et_rcpt_user | TYPE UJH_T_RCPT_USER, " | |||
| lv_et_rcpt_team | TYPE UJH_T_RCPT_TEAM, " | |||
| lv_et_content_obj | TYPE UJH_T_CONTENT_OBJ. " |
|   CALL FUNCTION 'UJH_API_GET_PAGE' "BPC: Get a page |
| EXPORTING | ||
| I_APPSET_ID | = lv_i_appset_id | |
| IS_USER | = lv_is_user | |
| I_CONTENT_ID | = lv_i_content_id | |
| IMPORTING | ||
| ET_MESSAGE_LINES | = lv_et_message_lines | |
| E_SUCCESS | = lv_e_success | |
| ET_CONTENT | = lv_et_content | |
| ET_RCPT_USER | = lv_et_rcpt_user | |
| ET_RCPT_TEAM | = lv_et_rcpt_team | |
| ET_CONTENT_OBJ | = lv_et_content_obj | |
| . " UJH_API_GET_PAGE | ||
ABAP code using 7.40 inline data declarations to call FM UJH_API_GET_PAGE
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 APPSET_ID FROM UJA_APPSET_INFO INTO @DATA(ld_i_appset_id). | ||||
Search for further information about these or an SAP related objects