SAP PRS_SET_DMRP_CHANGES Function Module for Engagement mgmt:Update DMRP table by screen activities
PRS_SET_DMRP_CHANGES is a standard prs set dmrp changes 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:Update DMRP table by screen activities 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 set dmrp changes FM, simply by entering the name PRS_SET_DMRP_CHANGES 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_SET_DMRP_CHANGES 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_SET_DMRP_CHANGES'"Engagement mgmt:Update DMRP table by screen activities.
EXPORTING
IT_EDITED = "Engagemeng mgmt:Table type for VBAP and DLI
IMPORTING
EV_NEW_LINE_POSNR = "New line POSNR, if new line not exist then initial
CHANGING
CT_DMRP = "Engagement mgmt:Table type for VBAP
EXCEPTIONS
UNKNOWN_EDIT_TYPE = 1 READ_ERROR = 2 DELETE_ERROR = 3 ERROR = 4
IMPORTING Parameters details for PRS_SET_DMRP_CHANGES
IT_EDITED - Engagemeng mgmt:Table type for VBAP and DLI
Data type: PRST_DMRP_DLIOptional: No
Call by Reference: Yes
EXPORTING Parameters details for PRS_SET_DMRP_CHANGES
EV_NEW_LINE_POSNR - New line POSNR, if new line not exist then initial
Data type: POSNR_VAOptional: No
Call by Reference: Yes
CHANGING Parameters details for PRS_SET_DMRP_CHANGES
CT_DMRP - Engagement mgmt:Table type for VBAP
Data type: PRST_DMRP_DLIOptional: No
Call by Reference: Yes
EXCEPTIONS details
UNKNOWN_EDIT_TYPE - Edit type not known
Data type:Optional: No
Call by Reference: Yes
READ_ERROR - Reading data line not succesful
Data type:Optional: No
Call by Reference: Yes
DELETE_ERROR - Deletind data line error
Data type:Optional: No
Call by Reference: Yes
ERROR - Error
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for PRS_SET_DMRP_CHANGES 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_ct_dmrp | TYPE PRST_DMRP_DLI, " | |||
| lv_it_edited | TYPE PRST_DMRP_DLI, " | |||
| lv_ev_new_line_posnr | TYPE POSNR_VA, " | |||
| lv_unknown_edit_type | TYPE POSNR_VA, " | |||
| lv_read_error | TYPE POSNR_VA, " | |||
| lv_delete_error | TYPE POSNR_VA, " | |||
| lv_error | TYPE POSNR_VA. " |
|   CALL FUNCTION 'PRS_SET_DMRP_CHANGES' "Engagement mgmt:Update DMRP table by screen activities |
| EXPORTING | ||
| IT_EDITED | = lv_it_edited | |
| IMPORTING | ||
| EV_NEW_LINE_POSNR | = lv_ev_new_line_posnr | |
| CHANGING | ||
| CT_DMRP | = lv_ct_dmrp | |
| EXCEPTIONS | ||
| UNKNOWN_EDIT_TYPE = 1 | ||
| READ_ERROR = 2 | ||
| DELETE_ERROR = 3 | ||
| ERROR = 4 | ||
| . " PRS_SET_DMRP_CHANGES | ||
ABAP code using 7.40 inline data declarations to call FM PRS_SET_DMRP_CHANGES
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