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

Function PRS_EVENT_ACC_NEXT 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_EVENT_ACC_NEXT'"Engagement mgmt: ACC screen NEXT event.
EXPORTING
IV_DMR_NO = "Sales and Distribution Document Number
IMPORTING
ET_DMRP_GRP = "Engagement mgmt:Table type for Valuation
EXCEPTIONS
ERROR = 1
IMPORTING Parameters details for PRS_EVENT_ACC_NEXT
IV_DMR_NO - Sales and Distribution Document Number
Data type: VBELNOptional: No
Call by Reference: Yes
EXPORTING Parameters details for PRS_EVENT_ACC_NEXT
ET_DMRP_GRP - Engagement mgmt:Table type for Valuation
Data type: PRST_DMRP_GRPOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR - Error
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for PRS_EVENT_ACC_NEXT 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_iv_dmr_no | TYPE VBELN, " | |||
| lv_et_dmrp_grp | TYPE PRST_DMRP_GRP. " |
|   CALL FUNCTION 'PRS_EVENT_ACC_NEXT' "Engagement mgmt: ACC screen NEXT event |
| EXPORTING | ||
| IV_DMR_NO | = lv_iv_dmr_no | |
| IMPORTING | ||
| ET_DMRP_GRP | = lv_et_dmrp_grp | |
| EXCEPTIONS | ||
| ERROR = 1 | ||
| . " PRS_EVENT_ACC_NEXT | ||
ABAP code using 7.40 inline data declarations to call FM PRS_EVENT_ACC_NEXT
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