SAP CD_CL_S_ODP_ITM_PROVIDE Function Module for NOTRANSL: Bereitstellung von Beziehungswissen Stücklistenposition
CD_CL_S_ODP_ITM_PROVIDE is a standard cd cl s odp itm provide 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: Bereitstellung von Beziehungswissen Stücklistenposition 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 cd cl s odp itm provide FM, simply by entering the name CD_CL_S_ODP_ITM_PROVIDE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CDCL
Program Name: SAPLCDCL
Main Program:
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CD_CL_S_ODP_ITM_PROVIDE 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 'CD_CL_S_ODP_ITM_PROVIDE'"NOTRANSL: Bereitstellung von Beziehungswissen Stücklistenposition.
EXPORTING
* I_DATE_FROM = DATE-MIN_GRG "Valid-From Date
* I_DATE_TO = DATE-MAX_GRG "Valid-to date
* I_STLTY = "BOM category
* I_STLNR = "Bill of material
* I_STLAL = "Alternative BOM
* I_IDENT = "Item ID
TABLES
E_ODP_ITM_CLASS_DATA = "Data for object dependencies for item class
EXCEPTIONS
WRONG_KEY = 1
IMPORTING Parameters details for CD_CL_S_ODP_ITM_PROVIDE
I_DATE_FROM - Valid-From Date
Data type: ODP_ITM_CLASS_DATA-DATUVDefault: DATE-MIN_GRG
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_DATE_TO - Valid-to date
Data type: ODP_ITM_CLASS_DATA-DATUBDefault: DATE-MAX_GRG
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_STLTY - BOM category
Data type: ODP_ITM_CLASS_DATA-STLTYOptional: Yes
Call by Reference: No ( called with pass by value option)
I_STLNR - Bill of material
Data type: ODP_ITM_CLASS_DATA-STLNROptional: Yes
Call by Reference: No ( called with pass by value option)
I_STLAL - Alternative BOM
Data type: ODP_ITM_CLASS_DATA-STLALOptional: Yes
Call by Reference: No ( called with pass by value option)
I_IDENT - Item ID
Data type: ODP_ITM_CLASS_DATA-IDENTOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CD_CL_S_ODP_ITM_PROVIDE
E_ODP_ITM_CLASS_DATA - Data for object dependencies for item class
Data type: ODP_ITM_CLASS_DATAOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
WRONG_KEY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CD_CL_S_ODP_ITM_PROVIDE 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_wrong_key | TYPE STRING, " | |||
| lv_i_date_from | TYPE ODP_ITM_CLASS_DATA-DATUV, " DATE-MIN_GRG | |||
| lt_e_odp_itm_class_data | TYPE STANDARD TABLE OF ODP_ITM_CLASS_DATA, " | |||
| lv_i_date_to | TYPE ODP_ITM_CLASS_DATA-DATUB, " DATE-MAX_GRG | |||
| lv_i_stlty | TYPE ODP_ITM_CLASS_DATA-STLTY, " | |||
| lv_i_stlnr | TYPE ODP_ITM_CLASS_DATA-STLNR, " | |||
| lv_i_stlal | TYPE ODP_ITM_CLASS_DATA-STLAL, " | |||
| lv_i_ident | TYPE ODP_ITM_CLASS_DATA-IDENT. " |
|   CALL FUNCTION 'CD_CL_S_ODP_ITM_PROVIDE' "NOTRANSL: Bereitstellung von Beziehungswissen Stücklistenposition |
| EXPORTING | ||
| I_DATE_FROM | = lv_i_date_from | |
| I_DATE_TO | = lv_i_date_to | |
| I_STLTY | = lv_i_stlty | |
| I_STLNR | = lv_i_stlnr | |
| I_STLAL | = lv_i_stlal | |
| I_IDENT | = lv_i_ident | |
| TABLES | ||
| E_ODP_ITM_CLASS_DATA | = lt_e_odp_itm_class_data | |
| EXCEPTIONS | ||
| WRONG_KEY = 1 | ||
| . " CD_CL_S_ODP_ITM_PROVIDE | ||
ABAP code using 7.40 inline data declarations to call FM CD_CL_S_ODP_ITM_PROVIDE
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 DATUV FROM ODP_ITM_CLASS_DATA INTO @DATA(ld_i_date_from). | ||||
| DATA(ld_i_date_from) | = DATE-MIN_GRG. | |||
| "SELECT single DATUB FROM ODP_ITM_CLASS_DATA INTO @DATA(ld_i_date_to). | ||||
| DATA(ld_i_date_to) | = DATE-MAX_GRG. | |||
| "SELECT single STLTY FROM ODP_ITM_CLASS_DATA INTO @DATA(ld_i_stlty). | ||||
| "SELECT single STLNR FROM ODP_ITM_CLASS_DATA INTO @DATA(ld_i_stlnr). | ||||
| "SELECT single STLAL FROM ODP_ITM_CLASS_DATA INTO @DATA(ld_i_stlal). | ||||
| "SELECT single IDENT FROM ODP_ITM_CLASS_DATA INTO @DATA(ld_i_ident). | ||||
Search for further information about these or an SAP related objects