SAP PRS_ACC_PERFORM_INSERT_EVENT Function Module for Acrual screen insert event
PRS_ACC_PERFORM_INSERT_EVENT is a standard prs acc perform insert event SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Acrual screen insert event 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 prs acc perform insert event FM, simply by entering the name PRS_ACC_PERFORM_INSERT_EVENT into the relevant SAP transaction such as SE37 or SE38.
Function Group: PRS_EM01_UI
Program Name: SAPLPRS_EM01_UI
Main Program: SAPLPRS_EM01_UI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PRS_ACC_PERFORM_INSERT_EVENT 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 'PRS_ACC_PERFORM_INSERT_EVENT'"Acrual screen insert event.
EXPORTING
LR_NODE = "Web Dynpro: Interface for Context Nodes
IV_DEF_OBJID = "Engagement mgmt: Consolidated Object ID
IMPORTING
EV_INSERT_EVENT = "
EXCEPTIONS
ERROR = 1
IMPORTING Parameters details for PRS_ACC_PERFORM_INSERT_EVENT
LR_NODE - Web Dynpro: Interface for Context Nodes
Data type: IF_WD_CONTEXT_NODEOptional: No
Call by Reference: Yes
IV_DEF_OBJID - Engagement mgmt: Consolidated Object ID
Data type: PRS_OBJIDOptional: No
Call by Reference: Yes
EXPORTING Parameters details for PRS_ACC_PERFORM_INSERT_EVENT
EV_INSERT_EVENT -
Data type: STRINGOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for PRS_ACC_PERFORM_INSERT_EVENT 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_error | TYPE STRING, " | |||
| lv_lr_node | TYPE IF_WD_CONTEXT_NODE, " | |||
| lv_ev_insert_event | TYPE STRING, " | |||
| lv_iv_def_objid | TYPE PRS_OBJID. " |
|   CALL FUNCTION 'PRS_ACC_PERFORM_INSERT_EVENT' "Acrual screen insert event |
| EXPORTING | ||
| LR_NODE | = lv_lr_node | |
| IV_DEF_OBJID | = lv_iv_def_objid | |
| IMPORTING | ||
| EV_INSERT_EVENT | = lv_ev_insert_event | |
| EXCEPTIONS | ||
| ERROR = 1 | ||
| . " PRS_ACC_PERFORM_INSERT_EVENT | ||
ABAP code using 7.40 inline data declarations to call FM PRS_ACC_PERFORM_INSERT_EVENT
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