SAP C_PDM_INSERT_ROUTING_MATERIALS Function Module for NOTRANSL: Einfügen der Materialien zum Arbeitsplan in den Strukturbrowser
C_PDM_INSERT_ROUTING_MATERIALS is a standard c pdm insert routing materials 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 Materialien zum Arbeitsplan in den Strukturbrowser 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 routing materials FM, simply by entering the name C_PDM_INSERT_ROUTING_MATERIALS into the relevant SAP transaction such as SE37 or SE38.
Function Group: CPDMDATACOLLECTOR1
Program Name: SAPLCPDMDATACOLLECTOR1
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function C_PDM_INSERT_ROUTING_MATERIALS 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_ROUTING_MATERIALS'"NOTRANSL: Einfügen der Materialien zum Arbeitsplan in den Strukturbrowser.
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 in Function Call)
* TREE_ID = "ID of tree in Product Structure Browser
* VALIDFROM = SYST-DATUM "ABAP System Field: Current Date of Application Server
TABLES
MATERIAL_DATA = "Material Data in Product Structure Browser
NODE_COLLECTION = "Structure of Tree in Product Structure Browser
IMPORTING Parameters details for C_PDM_INSERT_ROUTING_MATERIALS
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 in Function Call)
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 - ABAP System Field: Current Date of Application Server
Data type: SY-DATUMDefault: SYST-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for C_PDM_INSERT_ROUTING_MATERIALS
MATERIAL_DATA - Material Data in Product Structure Browser
Data type: PDM_MATERIALOptional: No
Call by Reference: Yes
NODE_COLLECTION - Structure of Tree in Product Structure Browser
Data type: PDM_TREEOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for C_PDM_INSERT_ROUTING_MATERIALS 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_actual_level | TYPE PDM_TREE-ACTUAL_LEVEL, " | |||
| lt_material_data | TYPE STANDARD TABLE OF PDM_MATERIAL, " | |||
| lv_object_handle | TYPE PDM_TREE-OBJECT_HANDLE, " | |||
| lt_node_collection | TYPE STANDARD TABLE OF PDM_TREE, " | |||
| lv_parent_level | TYPE PDM_TREE-PARENT_LEVEL, " | |||
| lv_rfcdest | TYPE PDM_TREE-RFCDEST, " | |||
| lv_tree_id | TYPE PDM_TREE-TREE_ID, " | |||
| lv_validfrom | TYPE SY-DATUM. " SYST-DATUM |
|   CALL FUNCTION 'C_PDM_INSERT_ROUTING_MATERIALS' "NOTRANSL: Einfügen der Materialien zum Arbeitsplan in den Strukturbrowser |
| 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 | |
| TABLES | ||
| MATERIAL_DATA | = lt_material_data | |
| NODE_COLLECTION | = lt_node_collection | |
| . " C_PDM_INSERT_ROUTING_MATERIALS | ||
ABAP code using 7.40 inline data declarations to call FM C_PDM_INSERT_ROUTING_MATERIALS
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 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