SAP CD_CL_S_ODP_SEQ_PROVIDE Function Module for NOTRANSL: Bereitstellung von Beziehungswissen Folgen
CD_CL_S_ODP_SEQ_PROVIDE is a standard cd cl s odp seq 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 Folgen 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 seq provide FM, simply by entering the name CD_CL_S_ODP_SEQ_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_SEQ_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_SEQ_PROVIDE'"NOTRANSL: Bereitstellung von Beziehungswissen Folgen.
EXPORTING
* I_DATE_FROM = DATE-MIN_GRG "Valid-From Date
* I_DATE_TO = DATE-MAX_GRG "Valid-to date
* I_PLNTY = "Task List Type
* I_PLNNR = "Key for Task List Group
* I_PLNAL = "Group Counter
* I_PLNFL = "Sequence
TABLES
E_ODP_SEQ_CLASS_DATA = "Data for object dependencies for sequence class
EXCEPTIONS
WRONG_KEY = 1
IMPORTING Parameters details for CD_CL_S_ODP_SEQ_PROVIDE
I_DATE_FROM - Valid-From Date
Data type: ODP_SEQ_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_SEQ_CLASS_DATA-DATUBDefault: DATE-MAX_GRG
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_PLNTY - Task List Type
Data type: ODP_SEQ_CLASS_DATA-PLNTYOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PLNNR - Key for Task List Group
Data type: ODP_SEQ_CLASS_DATA-PLNNROptional: Yes
Call by Reference: No ( called with pass by value option)
I_PLNAL - Group Counter
Data type: ODP_SEQ_CLASS_DATA-PLNALOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PLNFL - Sequence
Data type: ODP_SEQ_CLASS_DATA-PLNFLOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CD_CL_S_ODP_SEQ_PROVIDE
E_ODP_SEQ_CLASS_DATA - Data for object dependencies for sequence class
Data type: ODP_SEQ_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_SEQ_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_SEQ_CLASS_DATA-DATUV, " DATE-MIN_GRG | |||
| lt_e_odp_seq_class_data | TYPE STANDARD TABLE OF ODP_SEQ_CLASS_DATA, " | |||
| lv_i_date_to | TYPE ODP_SEQ_CLASS_DATA-DATUB, " DATE-MAX_GRG | |||
| lv_i_plnty | TYPE ODP_SEQ_CLASS_DATA-PLNTY, " | |||
| lv_i_plnnr | TYPE ODP_SEQ_CLASS_DATA-PLNNR, " | |||
| lv_i_plnal | TYPE ODP_SEQ_CLASS_DATA-PLNAL, " | |||
| lv_i_plnfl | TYPE ODP_SEQ_CLASS_DATA-PLNFL. " |
|   CALL FUNCTION 'CD_CL_S_ODP_SEQ_PROVIDE' "NOTRANSL: Bereitstellung von Beziehungswissen Folgen |
| EXPORTING | ||
| I_DATE_FROM | = lv_i_date_from | |
| I_DATE_TO | = lv_i_date_to | |
| I_PLNTY | = lv_i_plnty | |
| I_PLNNR | = lv_i_plnnr | |
| I_PLNAL | = lv_i_plnal | |
| I_PLNFL | = lv_i_plnfl | |
| TABLES | ||
| E_ODP_SEQ_CLASS_DATA | = lt_e_odp_seq_class_data | |
| EXCEPTIONS | ||
| WRONG_KEY = 1 | ||
| . " CD_CL_S_ODP_SEQ_PROVIDE | ||
ABAP code using 7.40 inline data declarations to call FM CD_CL_S_ODP_SEQ_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_SEQ_CLASS_DATA INTO @DATA(ld_i_date_from). | ||||
| DATA(ld_i_date_from) | = DATE-MIN_GRG. | |||
| "SELECT single DATUB FROM ODP_SEQ_CLASS_DATA INTO @DATA(ld_i_date_to). | ||||
| DATA(ld_i_date_to) | = DATE-MAX_GRG. | |||
| "SELECT single PLNTY FROM ODP_SEQ_CLASS_DATA INTO @DATA(ld_i_plnty). | ||||
| "SELECT single PLNNR FROM ODP_SEQ_CLASS_DATA INTO @DATA(ld_i_plnnr). | ||||
| "SELECT single PLNAL FROM ODP_SEQ_CLASS_DATA INTO @DATA(ld_i_plnal). | ||||
| "SELECT single PLNFL FROM ODP_SEQ_CLASS_DATA INTO @DATA(ld_i_plnfl). | ||||
Search for further information about these or an SAP related objects