SAP EHPRC_CP_DD01_PROD_DETAIL Function Module for PRC: Product Detail Section
EHPRC_CP_DD01_PROD_DETAIL is a standard ehprc cp dd01 prod detail SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for PRC: Product Detail Section 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 ehprc cp dd01 prod detail FM, simply by entering the name EHPRC_CP_DD01_PROD_DETAIL into the relevant SAP transaction such as SE37 or SE38.
Function Group: EHPRC_CP_DD01
Program Name: SAPLEHPRC_CP_DD01
Main Program: SAPLEHPRC_CP_DD01
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EHPRC_CP_DD01_PROD_DETAIL 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 'EHPRC_CP_DD01_PROD_DETAIL'"PRC: Product Detail Section.
EXPORTING
* IO_REQ_NODE = "custom bopf node
IO_ROOT_NODE = "custom bopf node
IV_TEMPLATE = "Template
IMPORTING
EV_FLG_ERROR = "Error flag
ET_MESSAGES = "Table with messages
EO_PRODUCT_DETAIL = "XML processing for EHSM CDO business object
ET_SUB_KEYS = "Key table
EXCEPTIONS
CX_EHPRC_XML_EXCEPTION = 1 /BOBF/CX_FRW = 2
IMPORTING Parameters details for EHPRC_CP_DD01_PROD_DETAIL
IO_REQ_NODE - custom bopf node
Data type: CL_EHFND_ENA_NODEOptional: Yes
Call by Reference: Yes
IO_ROOT_NODE - custom bopf node
Data type: CL_EHFND_ENA_NODEOptional: No
Call by Reference: Yes
IV_TEMPLATE - Template
Data type: EHFND_TEMPLIDOptional: No
Call by Reference: Yes
EXPORTING Parameters details for EHPRC_CP_DD01_PROD_DETAIL
EV_FLG_ERROR - Error flag
Data type: ESEBOOLEOptional: No
Call by Reference: Yes
ET_MESSAGES - Table with messages
Data type: BAL_T_MSGOptional: No
Call by Reference: Yes
EO_PRODUCT_DETAIL - XML processing for EHSM CDO business object
Data type: IF_EHPRC_XML_PROCESSOROptional: No
Call by Reference: Yes
ET_SUB_KEYS - Key table
Data type: /BOBF/T_FRW_KEY2Optional: No
Call by Reference: Yes
EXCEPTIONS details
CX_EHPRC_XML_EXCEPTION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
/BOBF/CX_FRW - BOPF Exception Class
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EHPRC_CP_DD01_PROD_DETAIL 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_io_req_node | TYPE CL_EHFND_ENA_NODE, " | |||
| lv_ev_flg_error | TYPE ESEBOOLE, " | |||
| lv_cx_ehprc_xml_exception | TYPE ESEBOOLE, " | |||
| lv_et_messages | TYPE BAL_T_MSG, " | |||
| lv_/bobf/cx_frw | TYPE BAL_T_MSG, " | |||
| lv_io_root_node | TYPE CL_EHFND_ENA_NODE, " | |||
| lv_iv_template | TYPE EHFND_TEMPLID, " | |||
| lv_eo_product_detail | TYPE IF_EHPRC_XML_PROCESSOR, " | |||
| lv_et_sub_keys | TYPE /BOBF/T_FRW_KEY2. " |
|   CALL FUNCTION 'EHPRC_CP_DD01_PROD_DETAIL' "PRC: Product Detail Section |
| EXPORTING | ||
| IO_REQ_NODE | = lv_io_req_node | |
| IO_ROOT_NODE | = lv_io_root_node | |
| IV_TEMPLATE | = lv_iv_template | |
| IMPORTING | ||
| EV_FLG_ERROR | = lv_ev_flg_error | |
| ET_MESSAGES | = lv_et_messages | |
| EO_PRODUCT_DETAIL | = lv_eo_product_detail | |
| ET_SUB_KEYS | = lv_et_sub_keys | |
| EXCEPTIONS | ||
| CX_EHPRC_XML_EXCEPTION = 1 | ||
| /BOBF/CX_FRW = 2 | ||
| . " EHPRC_CP_DD01_PROD_DETAIL | ||
ABAP code using 7.40 inline data declarations to call FM EHPRC_CP_DD01_PROD_DETAIL
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