SAP PPC1TP_COMP_CONF_DATA_REVERSE1 Function Module for NOTRANSL: PPC1TP_COMP_CONF_DATA_REVERSE 1
PPC1TP_COMP_CONF_DATA_REVERSE1 is a standard ppc1tp comp conf data reverse1 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: PPC1TP_COMP_CONF_DATA_REVERSE 1 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 ppc1tp comp conf data reverse1 FM, simply by entering the name PPC1TP_COMP_CONF_DATA_REVERSE1 into the relevant SAP transaction such as SE37 or SE38.
Function Group: PPC1TP
Program Name: SAPLPPC1TP
Main Program: SAPLPPC1TP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PPC1TP_COMP_CONF_DATA_REVERSE1 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 'PPC1TP_COMP_CONF_DATA_REVERSE1'"NOTRANSL: PPC1TP_COMP_CONF_DATA_REVERSE 1.
EXPORTING
IS_PPC_COMP_CONF = "PPC1TP: Component Confirmation Interface
* IS_MDPA = "View of Planned Order/Dummy Component for BOM Explosion
* IF_SKIPSYNC = "Indicator (X or Blank)
* IF_USEGUIDS = "Indicator (X or Blank)
* IF_RPTONLY = "
TABLES
* IT_MDPMX = "View of Material Components in the Planned Order
EXCEPTIONS
ORDER_ERROR = 1 LINE_ERROR = 2 BAPI_ERROR = 3
IMPORTING Parameters details for PPC1TP_COMP_CONF_DATA_REVERSE1
IS_PPC_COMP_CONF - PPC1TP: Component Confirmation Interface
Data type: PPC_COMP_CONFOptional: No
Call by Reference: Yes
IS_MDPA - View of Planned Order/Dummy Component for BOM Explosion
Data type: MDPAOptional: Yes
Call by Reference: Yes
IF_SKIPSYNC - Indicator (X or Blank)
Data type: AS4FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
IF_USEGUIDS - Indicator (X or Blank)
Data type: AS4FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
IF_RPTONLY -
Data type: AS4FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for PPC1TP_COMP_CONF_DATA_REVERSE1
IT_MDPMX - View of Material Components in the Planned Order
Data type: MDPMOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
ORDER_ERROR -
Data type:Optional: No
Call by Reference: Yes
LINE_ERROR -
Data type:Optional: No
Call by Reference: Yes
BAPI_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for PPC1TP_COMP_CONF_DATA_REVERSE1 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: | ||||
| lt_it_mdpmx | TYPE STANDARD TABLE OF MDPM, " | |||
| lv_order_error | TYPE MDPM, " | |||
| lv_is_ppc_comp_conf | TYPE PPC_COMP_CONF, " | |||
| lv_is_mdpa | TYPE MDPA, " | |||
| lv_line_error | TYPE MDPA, " | |||
| lv_bapi_error | TYPE MDPA, " | |||
| lv_if_skipsync | TYPE AS4FLAG, " | |||
| lv_if_useguids | TYPE AS4FLAG, " | |||
| lv_if_rptonly | TYPE AS4FLAG. " |
|   CALL FUNCTION 'PPC1TP_COMP_CONF_DATA_REVERSE1' "NOTRANSL: PPC1TP_COMP_CONF_DATA_REVERSE 1 |
| EXPORTING | ||
| IS_PPC_COMP_CONF | = lv_is_ppc_comp_conf | |
| IS_MDPA | = lv_is_mdpa | |
| IF_SKIPSYNC | = lv_if_skipsync | |
| IF_USEGUIDS | = lv_if_useguids | |
| IF_RPTONLY | = lv_if_rptonly | |
| TABLES | ||
| IT_MDPMX | = lt_it_mdpmx | |
| EXCEPTIONS | ||
| ORDER_ERROR = 1 | ||
| LINE_ERROR = 2 | ||
| BAPI_ERROR = 3 | ||
| . " PPC1TP_COMP_CONF_DATA_REVERSE1 | ||
ABAP code using 7.40 inline data declarations to call FM PPC1TP_COMP_CONF_DATA_REVERSE1
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