SAP C_PDM_INSERT_PNODE_SUP_IPPEOBJ Function Module for NOTRANSL: Einfügen der übergeordneten iPPE Objekte in den Browser
C_PDM_INSERT_PNODE_SUP_IPPEOBJ is a standard c pdm insert pnode sup ippeobj 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: Einfügen der übergeordneten iPPE Objekte in den Browser 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 c pdm insert pnode sup ippeobj FM, simply by entering the name C_PDM_INSERT_PNODE_SUP_IPPEOBJ into the relevant SAP transaction such as SE37 or SE38.
Function Group: CPDMDATACOLLECTORIPPE
Program Name: SAPLCPDMDATACOLLECTORIPPE
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function C_PDM_INSERT_PNODE_SUP_IPPEOBJ 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 'C_PDM_INSERT_PNODE_SUP_IPPEOBJ'"NOTRANSL: Einfügen der übergeordneten iPPE Objekte in den Browser.
EXPORTING
* ACTUAL_LEVEL = "Current Level of Node in Product Structure Browser
OBJECT_HANDLE = "ID of Object in Product Structure Browser
* PARENT_LEVEL = "Next Level Up in Product Structure Browser
* RFCDEST = "Logical Destination (Specified When Function Is Called)
* TREE_ID = "ID of Tree in Product Structure Browser
* VALIDFROM = SYST-DATUM "Date and Time, Current (Application Server) Date
CHANGING
* C_LOGSYS = "Logical System
TABLES
NODE_COLLECTION = "Structure of Tree in Product Structure Browser
* PVS_NODE_DATA = "iPPE Nodes in Product Structure Browser
* ALTERNATIVE_DATA = "Alternatives in Product Structure Browser
* POSVAR_DATA = "Component Variants in Product Structure Browser
IMPORTING Parameters details for C_PDM_INSERT_PNODE_SUP_IPPEOBJ
ACTUAL_LEVEL - Current Level of Node in Product Structure Browser
Data type: PDM_TREE-ACTUAL_LEVELOptional: Yes
Call by Reference: No ( called with pass by value option)
OBJECT_HANDLE - ID of Object in Product Structure Browser
Data type: PDM_TREE-OBJECT_HANDLEOptional: No
Call by Reference: No ( called with pass by value option)
PARENT_LEVEL - Next Level Up in Product Structure Browser
Data type: PDM_TREE-PARENT_LEVELOptional: Yes
Call by Reference: No ( called with pass by value option)
RFCDEST - Logical Destination (Specified When Function Is Called)
Data type: PDM_TREE-RFCDESTOptional: Yes
Call by Reference: No ( called with pass by value option)
TREE_ID - ID of Tree in Product Structure Browser
Data type: PDM_TREE-TREE_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
VALIDFROM - Date and Time, Current (Application Server) Date
Data type: SY-DATUMDefault: SYST-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for C_PDM_INSERT_PNODE_SUP_IPPEOBJ
C_LOGSYS - Logical System
Data type: PDM_FIELDCATALOG-LOGSYSOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for C_PDM_INSERT_PNODE_SUP_IPPEOBJ
NODE_COLLECTION - Structure of Tree in Product Structure Browser
Data type: PDM_TREEOptional: No
Call by Reference: No ( called with pass by value option)
PVS_NODE_DATA - iPPE Nodes in Product Structure Browser
Data type: PDM_IPPENODEOptional: Yes
Call by Reference: Yes
ALTERNATIVE_DATA - Alternatives in Product Structure Browser
Data type: PDM_IPPEALTERNATIVEOptional: Yes
Call by Reference: Yes
POSVAR_DATA - Component Variants in Product Structure Browser
Data type: PDM_POSVARIANTOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for C_PDM_INSERT_PNODE_SUP_IPPEOBJ 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_c_logsys | TYPE PDM_FIELDCATALOG-LOGSYS, " | |||
| lv_actual_level | TYPE PDM_TREE-ACTUAL_LEVEL, " | |||
| lt_node_collection | TYPE STANDARD TABLE OF PDM_TREE, " | |||
| lv_object_handle | TYPE PDM_TREE-OBJECT_HANDLE, " | |||
| lt_pvs_node_data | TYPE STANDARD TABLE OF PDM_IPPENODE, " | |||
| lv_parent_level | TYPE PDM_TREE-PARENT_LEVEL, " | |||
| lt_alternative_data | TYPE STANDARD TABLE OF PDM_IPPEALTERNATIVE, " | |||
| lv_rfcdest | TYPE PDM_TREE-RFCDEST, " | |||
| lt_posvar_data | TYPE STANDARD TABLE OF PDM_POSVARIANT, " | |||
| lv_tree_id | TYPE PDM_TREE-TREE_ID, " | |||
| lv_validfrom | TYPE SY-DATUM. " SYST-DATUM |
|   CALL FUNCTION 'C_PDM_INSERT_PNODE_SUP_IPPEOBJ' "NOTRANSL: Einfügen der übergeordneten iPPE Objekte in den Browser |
| EXPORTING | ||
| ACTUAL_LEVEL | = lv_actual_level | |
| OBJECT_HANDLE | = lv_object_handle | |
| PARENT_LEVEL | = lv_parent_level | |
| RFCDEST | = lv_rfcdest | |
| TREE_ID | = lv_tree_id | |
| VALIDFROM | = lv_validfrom | |
| CHANGING | ||
| C_LOGSYS | = lv_c_logsys | |
| TABLES | ||
| NODE_COLLECTION | = lt_node_collection | |
| PVS_NODE_DATA | = lt_pvs_node_data | |
| ALTERNATIVE_DATA | = lt_alternative_data | |
| POSVAR_DATA | = lt_posvar_data | |
| . " C_PDM_INSERT_PNODE_SUP_IPPEOBJ | ||
ABAP code using 7.40 inline data declarations to call FM C_PDM_INSERT_PNODE_SUP_IPPEOBJ
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.| "SELECT single LOGSYS FROM PDM_FIELDCATALOG INTO @DATA(ld_c_logsys). | ||||
| "SELECT single ACTUAL_LEVEL FROM PDM_TREE INTO @DATA(ld_actual_level). | ||||
| "SELECT single OBJECT_HANDLE FROM PDM_TREE INTO @DATA(ld_object_handle). | ||||
| "SELECT single PARENT_LEVEL FROM PDM_TREE INTO @DATA(ld_parent_level). | ||||
| "SELECT single RFCDEST FROM PDM_TREE INTO @DATA(ld_rfcdest). | ||||
| "SELECT single TREE_ID FROM PDM_TREE INTO @DATA(ld_tree_id). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_validfrom). | ||||
| DATA(ld_validfrom) | = SYST-DATUM. | |||
Search for further information about these or an SAP related objects