SAP PRC_INT_GET_PRICING_STATUS Function Module for Get the flag if price is inconsistent due to disabled group processing
PRC_INT_GET_PRICING_STATUS is a standard prc int get pricing status SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get the flag if price is inconsistent due to disabled group processing 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 prc int get pricing status FM, simply by entering the name PRC_INT_GET_PRICING_STATUS into the relevant SAP transaction such as SE37 or SE38.
Function Group: PRC_INT
Program Name: SAPLPRC_INT
Main Program: SAPLPRC_INT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PRC_INT_GET_PRICING_STATUS 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 'PRC_INT_GET_PRICING_STATUS'"Get the flag if price is inconsistent due to disabled group processing.
EXPORTING
IV_PD_HANDLE = "Handle eines Preisfindungslaufes
* IV_BAL_LOG = "Anwendungs-Log: Handle eines Protokolls
IMPORTING
ES_PROFILE = "Profil des API-Aufrufes
EV_PRICING_STATUS = "'X' = cross item pricing done; '-' not done; space = unknown
EXCEPTIONS
NON_EXISTING_HANDLE = 1 IPC_ERROR = 2
IMPORTING Parameters details for PRC_INT_GET_PRICING_STATUS
IV_PD_HANDLE - Handle eines Preisfindungslaufes
Data type: PRCT_HANDLEOptional: No
Call by Reference: Yes
IV_BAL_LOG - Anwendungs-Log: Handle eines Protokolls
Data type: BALLOGHNDLOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for PRC_INT_GET_PRICING_STATUS
ES_PROFILE - Profil des API-Aufrufes
Data type: PRCT_PROFILEOptional: No
Call by Reference: Yes
EV_PRICING_STATUS - 'X' = cross item pricing done; '-' not done; space = unknown
Data type: BOOLEANOptional: No
Call by Reference: Yes
EXCEPTIONS details
NON_EXISTING_HANDLE - Handle existiert nicht
Data type:Optional: No
Call by Reference: Yes
IPC_ERROR - Fehler beim Aufruf des IPC
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for PRC_INT_GET_PRICING_STATUS 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_es_profile | TYPE PRCT_PROFILE, " | |||
| lv_iv_pd_handle | TYPE PRCT_HANDLE, " | |||
| lv_non_existing_handle | TYPE PRCT_HANDLE, " | |||
| lv_ipc_error | TYPE PRCT_HANDLE, " | |||
| lv_iv_bal_log | TYPE BALLOGHNDL, " | |||
| lv_ev_pricing_status | TYPE BOOLEAN. " |
|   CALL FUNCTION 'PRC_INT_GET_PRICING_STATUS' "Get the flag if price is inconsistent due to disabled group processing |
| EXPORTING | ||
| IV_PD_HANDLE | = lv_iv_pd_handle | |
| IV_BAL_LOG | = lv_iv_bal_log | |
| IMPORTING | ||
| ES_PROFILE | = lv_es_profile | |
| EV_PRICING_STATUS | = lv_ev_pricing_status | |
| EXCEPTIONS | ||
| NON_EXISTING_HANDLE = 1 | ||
| IPC_ERROR = 2 | ||
| . " PRC_INT_GET_PRICING_STATUS | ||
ABAP code using 7.40 inline data declarations to call FM PRC_INT_GET_PRICING_STATUS
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