SAP POC_QUERY_PRC_IN_FOR_LOG_FED Function Module for Read Process Logs in Remote and Local Systems During Federation

Search SAP Function Modules

POC_QUERY_PRC_IN_FOR_LOG_FED is a standard poc query prc in for log fed SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read Process Logs in Remote and Local Systems During Federation 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 poc query prc in for log fed FM, simply by entering the name POC_QUERY_PRC_IN_FOR_LOG_FED into the relevant SAP transaction such as SE37 or SE38.

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

Function POC_QUERY_PRC_IN_FOR_LOG_FED 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 'POC_QUERY_PRC_IN_FOR_LOG_FED'"Read Process Logs in Remote and Local Systems During Federation
  EXPORTING
   IV_E2E_PROCESS_DEF_ID =  "End-To-End Process Definiton ID
   IT_PRC_INTEGRATION_POINTS =  "Processes with Integration Points
*  IT_PROC_INT_POINTS_PROCESSED =  "Processes with Integration Points
*  IV_GET_KPIS = ABAP_FALSE "Boolean Variable (X=True, -=False, Space=Unknown)
*  IV_READ_TEXTS = ABAP_FALSE "Boolean Variable (X=True, -=False, Space=Unknown)
*  IV_PRE_BA_REQ = ABAP_FALSE "Boolean Variable (X=True, -=False, Space=Unknown)

 IMPORTING
   ET_PRC_INSTANCES =  "Process Instances
   ET_PRC_LOG =  "Binding Details for Process Monitor
   ET_VERIFIED_PR_INTR_POINTS =  "Verified Process Integration Points
   ET_PROC_INT_POINTS_PROCESSED =  "Processes with Integration Points
   ET_PRC_INTEGRATION_POINTS =  "Processes with Integration Points to be queried
   ET_LOGICAL_SYS_TO_BE_QUERIED =  "Logical Systems to be queried
   ET_KPI_DATA =  "KPI UI Display
   ET_MESSAGES =  "Application Log Message Data
   ET_PRE_BA_INSTANCES =  "Previous/Predecessor Task and Task Details

.

IMPORTING Parameters details for POC_QUERY_PRC_IN_FOR_LOG_FED

IV_E2E_PROCESS_DEF_ID - End-To-End Process Definiton ID

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

IT_PRC_INTEGRATION_POINTS - Processes with Integration Points

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

IT_PROC_INT_POINTS_PROCESSED - Processes with Integration Points

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

IV_GET_KPIS - Boolean Variable (X=True, -=False, Space=Unknown)

Data type: BOOLEAN
Default: ABAP_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_READ_TEXTS - Boolean Variable (X=True, -=False, Space=Unknown)

Data type: BOOLEAN
Default: ABAP_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_PRE_BA_REQ - Boolean Variable (X=True, -=False, Space=Unknown)

Data type: BOOLEAN
Default: ABAP_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for POC_QUERY_PRC_IN_FOR_LOG_FED

ET_PRC_INSTANCES - Process Instances

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

ET_PRC_LOG - Binding Details for Process Monitor

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

ET_VERIFIED_PR_INTR_POINTS - Verified Process Integration Points

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

ET_PROC_INT_POINTS_PROCESSED - Processes with Integration Points

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

ET_PRC_INTEGRATION_POINTS - Processes with Integration Points to be queried

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

ET_LOGICAL_SYS_TO_BE_QUERIED - Logical Systems to be queried

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

ET_KPI_DATA - KPI UI Display

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

ET_MESSAGES - Application Log Message Data

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

ET_PRE_BA_INSTANCES - Previous/Predecessor Task and Task Details

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

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

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