SAP UJO_API_GET_APPLICATION Function Module for Common read and write: get application









UJO_API_GET_APPLICATION is a standard ujo api get application SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Common read and write: get application 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 ujo api get application FM, simply by entering the name UJO_API_GET_APPLICATION into the relevant SAP transaction such as SE37 or SE38.

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



Function UJO_API_GET_APPLICATION 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 'UJO_API_GET_APPLICATION'"Common read and write: get application
EXPORTING
* I_APPSET_ID = 'APSHELL' "
* I_APPLICATION_ID = 'PLANNING' "
* I_LEVEL_INPUT = '2' "

IMPORTING
ES_APPLICATION = "Restfull: Application Information
E_JSON_VALUE = "json result
.



IMPORTING Parameters details for UJO_API_GET_APPLICATION

I_APPSET_ID -

Data type: STRING
Default: 'APSHELL'
Optional: No
Call by Reference: No ( called with pass by value option)

I_APPLICATION_ID -

Data type: STRING
Default: 'PLANNING'
Optional: No
Call by Reference: No ( called with pass by value option)

I_LEVEL_INPUT -

Data type: STRING
Default: '2'
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for UJO_API_GET_APPLICATION

ES_APPLICATION - Restfull: Application Information

Data type: UJO_S_APPL_INFO
Optional: No
Call by Reference: Yes

E_JSON_VALUE - json result

Data type: STRING
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for UJO_API_GET_APPLICATION 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 STRING, "   'APSHELL'
lv_es_application  TYPE UJO_S_APPL_INFO, "   
lv_e_json_value  TYPE STRING, "   
lv_i_application_id  TYPE STRING, "   'PLANNING'
lv_i_level_input  TYPE STRING. "   '2'

  CALL FUNCTION 'UJO_API_GET_APPLICATION'  "Common read and write: get application
    EXPORTING
         I_APPSET_ID = lv_i_appset_id
         I_APPLICATION_ID = lv_i_application_id
         I_LEVEL_INPUT = lv_i_level_input
    IMPORTING
         ES_APPLICATION = lv_es_application
         E_JSON_VALUE = lv_e_json_value
. " UJO_API_GET_APPLICATION




ABAP code using 7.40 inline data declarations to call FM UJO_API_GET_APPLICATION

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_i_appset_id) = 'APSHELL'.
 
 
 
DATA(ld_i_application_id) = 'PLANNING'.
 
DATA(ld_i_level_input) = '2'.
 


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!