SAP PRC_PD_ITEM_GET_TRACE Function Module for Abholung Preisfindungstrace









PRC_PD_ITEM_GET_TRACE is a standard prc pd item get trace SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Abholung Preisfindungstrace 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 pd item get trace FM, simply by entering the name PRC_PD_ITEM_GET_TRACE into the relevant SAP transaction such as SE37 or SE38.

Function Group: PRC_PRICING_API
Program Name: SAPLPRC_PRICING_API
Main Program: SAPLPRC_PRICING_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function PRC_PD_ITEM_GET_TRACE 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_PD_ITEM_GET_TRACE'"Abholung Preisfindungstrace
EXPORTING
IV_PD_HANDLE = "Handle eines Preisfindungslaufes
* IV_BAL_LOG = "Anwendungs-Log: Handle eines Protokolls
IV_ITEM_NO = "Positionsnummer

IMPORTING
ES_PROFILE = "Profil des API-Aufrufes
ET_TRACE = "Preisfindungstrace pro Preisfindungslauf
EV_XML = "An XML String
ET_XML = "XML Line From IPC
ES_CALC_TRACE = "Structure for Price Calculation Trace

EXCEPTIONS
NON_EXISTING_HANDLE = 1 NON_EXISTING_ITEM = 2 WRONG_CALL = 3 IPC_ERROR = 4
.



IMPORTING Parameters details for PRC_PD_ITEM_GET_TRACE

IV_PD_HANDLE - Handle eines Preisfindungslaufes

Data type: PRCT_HANDLE
Optional: No
Call by Reference: Yes

IV_BAL_LOG - Anwendungs-Log: Handle eines Protokolls

Data type: BALLOGHNDL
Optional: Yes
Call by Reference: Yes

IV_ITEM_NO - Positionsnummer

Data type: PRCT_ITEM_NO
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for PRC_PD_ITEM_GET_TRACE

ES_PROFILE - Profil des API-Aufrufes

Data type: PRCT_PROFILE
Optional: No
Call by Reference: Yes

ET_TRACE - Preisfindungstrace pro Preisfindungslauf

Data type: PRCT_TRACE_T
Optional: No
Call by Reference: Yes

EV_XML - An XML String

Data type: PRIT_XML_LINE
Optional: No
Call by Reference: Yes

ET_XML - XML Line From IPC

Data type: IPCT_XML_LINE_T
Optional: No
Call by Reference: Yes

ES_CALC_TRACE - Structure for Price Calculation Trace

Data type: PRCT_CALC_TRACE
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NON_EXISTING_HANDLE - Handle existiert nicht

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NON_EXISTING_ITEM - Position existiert nicht

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

WRONG_CALL - Falscher Aufruf

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

IPC_ERROR - Fehler beim Aufruf des IPC

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for PRC_PD_ITEM_GET_TRACE 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_et_trace  TYPE PRCT_TRACE_T, "   
lv_iv_bal_log  TYPE BALLOGHNDL, "   
lv_non_existing_item  TYPE BALLOGHNDL, "   
lv_ev_xml  TYPE PRIT_XML_LINE, "   
lv_iv_item_no  TYPE PRCT_ITEM_NO, "   
lv_wrong_call  TYPE PRCT_ITEM_NO, "   
lv_et_xml  TYPE IPCT_XML_LINE_T, "   
lv_ipc_error  TYPE IPCT_XML_LINE_T, "   
lv_es_calc_trace  TYPE PRCT_CALC_TRACE. "   

  CALL FUNCTION 'PRC_PD_ITEM_GET_TRACE'  "Abholung Preisfindungstrace
    EXPORTING
         IV_PD_HANDLE = lv_iv_pd_handle
         IV_BAL_LOG = lv_iv_bal_log
         IV_ITEM_NO = lv_iv_item_no
    IMPORTING
         ES_PROFILE = lv_es_profile
         ET_TRACE = lv_et_trace
         EV_XML = lv_ev_xml
         ET_XML = lv_et_xml
         ES_CALC_TRACE = lv_es_calc_trace
    EXCEPTIONS
        NON_EXISTING_HANDLE = 1
        NON_EXISTING_ITEM = 2
        WRONG_CALL = 3
        IPC_ERROR = 4
. " PRC_PD_ITEM_GET_TRACE




ABAP code using 7.40 inline data declarations to call FM PRC_PD_ITEM_GET_TRACE

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!