SAP PM_PRIO_REQ_DETERMINE Function Module for NOTRANSL: Bedarfspriorität aus Dringlichkeit in der Instandhaltung ermitte
PM_PRIO_REQ_DETERMINE is a standard pm prio req determine SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Bedarfspriorität aus Dringlichkeit in der Instandhaltung ermitte 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 pm prio req determine FM, simply by entering the name PM_PRIO_REQ_DETERMINE into the relevant SAP transaction such as SE37 or SE38.
Function Group: PRIO_HANDLER
Program Name: SAPLPRIO_HANDLER
Main Program: SAPLPRIO_HANDLER
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PM_PRIO_REQ_DETERMINE 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 'PM_PRIO_REQ_DETERMINE'"NOTRANSL: Bedarfspriorität aus Dringlichkeit in der Instandhaltung ermitte.
EXPORTING
* IV_PRIO_URG = '00' "Requirement Urgency
* IS_RESBD_NEW = "Current Reservation Data That Is to Be Prioritized (Organizational Priority)
* IS_RESBD_OLD = "Old Reservation Data (Before the Change)
* IS_RESBD_DYP = "Reservation Data from Dialog (Screen)
* IS_AFVGD = "Order Operation of the Reservation Data to Be Prioritized
* IS_CAUFVD = "Order Data of the Reservation Item to Be Prioritized
* IS_MSFCV = "Material Master Data of the Current Reservation Item
IMPORTING
EV_PRIO_URG = "Requirement Urgency
EV_PRIO_REQ = "Requirement Priority
ET_MESSAGES = "Return parameter table
EXCEPTIONS
NO_PACT_ENTRY = 1
IMPORTING Parameters details for PM_PRIO_REQ_DETERMINE
IV_PRIO_URG - Requirement Urgency
Data type: PRIO_URGDefault: '00'
Optional: Yes
Call by Reference: Yes
IS_RESBD_NEW - Current Reservation Data That Is to Be Prioritized (Organizational Priority)
Data type: RESBDOptional: Yes
Call by Reference: Yes
IS_RESBD_OLD - Old Reservation Data (Before the Change)
Data type: RESBDOptional: Yes
Call by Reference: Yes
IS_RESBD_DYP - Reservation Data from Dialog (Screen)
Data type: RESBDOptional: Yes
Call by Reference: Yes
IS_AFVGD - Order Operation of the Reservation Data to Be Prioritized
Data type: AFVGDOptional: Yes
Call by Reference: Yes
IS_CAUFVD - Order Data of the Reservation Item to Be Prioritized
Data type: CAUFVDOptional: Yes
Call by Reference: Yes
IS_MSFCV - Material Master Data of the Current Reservation Item
Data type: MSFCVOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for PM_PRIO_REQ_DETERMINE
EV_PRIO_URG - Requirement Urgency
Data type: PRIO_URGOptional: No
Call by Reference: Yes
EV_PRIO_REQ - Requirement Priority
Data type: PRIO_REQOptional: No
Call by Reference: Yes
ET_MESSAGES - Return parameter table
Data type: BAPIRET2_TOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_PACT_ENTRY - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for PM_PRIO_REQ_DETERMINE 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_ev_prio_urg | TYPE PRIO_URG, " | |||
| lv_iv_prio_urg | TYPE PRIO_URG, " '00' | |||
| lv_no_pact_entry | TYPE PRIO_URG, " | |||
| lv_ev_prio_req | TYPE PRIO_REQ, " | |||
| lv_is_resbd_new | TYPE RESBD, " | |||
| lv_et_messages | TYPE BAPIRET2_T, " | |||
| lv_is_resbd_old | TYPE RESBD, " | |||
| lv_is_resbd_dyp | TYPE RESBD, " | |||
| lv_is_afvgd | TYPE AFVGD, " | |||
| lv_is_caufvd | TYPE CAUFVD, " | |||
| lv_is_msfcv | TYPE MSFCV. " |
|   CALL FUNCTION 'PM_PRIO_REQ_DETERMINE' "NOTRANSL: Bedarfspriorität aus Dringlichkeit in der Instandhaltung ermitte |
| EXPORTING | ||
| IV_PRIO_URG | = lv_iv_prio_urg | |
| IS_RESBD_NEW | = lv_is_resbd_new | |
| IS_RESBD_OLD | = lv_is_resbd_old | |
| IS_RESBD_DYP | = lv_is_resbd_dyp | |
| IS_AFVGD | = lv_is_afvgd | |
| IS_CAUFVD | = lv_is_caufvd | |
| IS_MSFCV | = lv_is_msfcv | |
| IMPORTING | ||
| EV_PRIO_URG | = lv_ev_prio_urg | |
| EV_PRIO_REQ | = lv_ev_prio_req | |
| ET_MESSAGES | = lv_et_messages | |
| EXCEPTIONS | ||
| NO_PACT_ENTRY = 1 | ||
| . " PM_PRIO_REQ_DETERMINE | ||
ABAP code using 7.40 inline data declarations to call FM PM_PRIO_REQ_DETERMINE
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.| DATA(ld_iv_prio_urg) | = '00'. | |||
Search for further information about these or an SAP related objects