SAP UJB_API_GET_INST_MONITOR Function Module for BPC: Get BPF Instance Monitor

Search SAP Function Modules

UJB_API_GET_INST_MONITOR is a standard ujb api get inst monitor 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 BPF Instance Monitor 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 ujb api get inst monitor FM, simply by entering the name UJB_API_GET_INST_MONITOR into the relevant SAP transaction such as SE37 or SE38.

Function Group: UJB1
Program Name: SAPLUJB1
Main Program: SAPLUJB1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function UJB_API_GET_INST_MONITOR 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 'UJB_API_GET_INST_MONITOR'"BPC: Get BPF Instance Monitor
  EXPORTING
   I_APPSET_ID =  "BPC: AppSet ID
   IS_USER =  "BPC: User Login Info
   I_INSTANCE_ID =  "BPC: ID used in BPF

 IMPORTING
   E_SUCCESS =  "BPC: Generic indicator
   ET_MESSAGE_LINES =  "BPC: Messages
   ES_INST_MONITOR =  "BPC: BPF Instance Monitor

.

IMPORTING Parameters details for UJB_API_GET_INST_MONITOR

I_APPSET_ID - BPC: AppSet ID

Data type: UJ_APPSET_ID
Optional: No
Call by Reference: No ( called with pass by value option)

IS_USER - BPC: User Login Info

Data type: UJ0_S_USER
Optional: No
Call by Reference: No ( called with pass by value option)

I_INSTANCE_ID - BPC: ID used in BPF

Data type: UJB_ID
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for UJB_API_GET_INST_MONITOR

E_SUCCESS - BPC: Generic indicator

Data type: UJ_FLG
Optional: No
Call by Reference: No ( called with pass by value option)

ET_MESSAGE_LINES - BPC: Messages

Data type: UJ0_T_MESSAGE
Optional: No
Call by Reference: No ( called with pass by value option)

ES_INST_MONITOR - BPC: BPF Instance Monitor

Data type: UJB_S_API_INST_MONITOR
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for UJB_API_GET_INST_MONITOR 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.

ABAP code using 7.40 inline data declarations to call FM UJB_API_GET_INST_MONITOR

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.

Search for further information about these or an SAP related objects