SAP POC_UPDATE_PROCESS_REGISTRY Function Module for Update Process Registry
POC_UPDATE_PROCESS_REGISTRY is a standard poc update process registry SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Update Process Registry 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 update process registry FM, simply by entering the name POC_UPDATE_PROCESS_REGISTRY 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_UPDATE_PROCESS_REGISTRY 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_UPDATE_PROCESS_REGISTRY'"Update Process Registry.
EXPORTING
IV_LOGSYS = "Logical system
IV_PROCESS_TYPE_ID = "Process Definition ID
IV_PROCESS_VERSION = "Process Version
IV_USER = "User Name
* IV_DELETE_FLAG = ' ' "if X(=TRUE) then delete all process regisry entires
* IT_E2E_PROCESS = "End-to-End Process data
* IT_INTEGRATION_POINT = "Integration Point data
IV_CURRENT_VERSION = "Active Version to be used for all New Process Instances
IMPORTING Parameters details for POC_UPDATE_PROCESS_REGISTRY
IV_LOGSYS - Logical system
Data type: POC_LOGSYSOptional: No
Call by Reference: No ( called with pass by value option)
IV_PROCESS_TYPE_ID - Process Definition ID
Data type: POC_PROCESS_TYPE_IDOptional: No
Call by Reference: No ( called with pass by value option)
IV_PROCESS_VERSION - Process Version
Data type: POC_PROCESS_VERSIONOptional: No
Call by Reference: No ( called with pass by value option)
IV_USER - User Name
Data type: SY-UNAMEOptional: No
Call by Reference: No ( called with pass by value option)
IV_DELETE_FLAG - if X(=TRUE) then delete all process regisry entires
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IT_E2E_PROCESS - End-to-End Process data
Data type: POC_T_E2E_PROCESSOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_INTEGRATION_POINT - Integration Point data
Data type: POC_T_INTEGRATION_POINTOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_CURRENT_VERSION - Active Version to be used for all New Process Instances
Data type: POC_PROC_VERSION_NEWOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for POC_UPDATE_PROCESS_REGISTRY 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_iv_logsys | TYPE POC_LOGSYS, " | |||
| lv_iv_process_type_id | TYPE POC_PROCESS_TYPE_ID, " | |||
| lv_iv_process_version | TYPE POC_PROCESS_VERSION, " | |||
| lv_iv_user | TYPE SY-UNAME, " | |||
| lv_iv_delete_flag | TYPE XFELD, " SPACE | |||
| lv_it_e2e_process | TYPE POC_T_E2E_PROCESS, " | |||
| lv_it_integration_point | TYPE POC_T_INTEGRATION_POINT, " | |||
| lv_iv_current_version | TYPE POC_PROC_VERSION_NEW. " |
|   CALL FUNCTION 'POC_UPDATE_PROCESS_REGISTRY' "Update Process Registry |
| EXPORTING | ||
| IV_LOGSYS | = lv_iv_logsys | |
| IV_PROCESS_TYPE_ID | = lv_iv_process_type_id | |
| IV_PROCESS_VERSION | = lv_iv_process_version | |
| IV_USER | = lv_iv_user | |
| IV_DELETE_FLAG | = lv_iv_delete_flag | |
| IT_E2E_PROCESS | = lv_it_e2e_process | |
| IT_INTEGRATION_POINT | = lv_it_integration_point | |
| IV_CURRENT_VERSION | = lv_iv_current_version | |
| . " POC_UPDATE_PROCESS_REGISTRY | ||
ABAP code using 7.40 inline data declarations to call FM POC_UPDATE_PROCESS_REGISTRY
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_iv_user). | ||||
| DATA(ld_iv_delete_flag) | = ' '. | |||
Search for further information about these or an SAP related objects