SAP CP_CC_S_ODP_SEQ_PROVIDE_BY_MTK Function Module for NOTRANSL: Bereitstellung von Beziehungswissen Folge









CP_CC_S_ODP_SEQ_PROVIDE_BY_MTK is a standard cp cc s odp seq provide by mtk 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 Folge 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 cp cc s odp seq provide by mtk FM, simply by entering the name CP_CC_S_ODP_SEQ_PROVIDE_BY_MTK into the relevant SAP transaction such as SE37 or SE38.

Function Group: CPCC
Program Name: SAPLCPCC
Main Program: SAPLCPCC
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function CP_CC_S_ODP_SEQ_PROVIDE_BY_MTK 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 'CP_CC_S_ODP_SEQ_PROVIDE_BY_MTK'"NOTRANSL: Bereitstellung von Beziehungswissen Folge
EXPORTING
* I_DATE_FROM = DATE-MIN_GRG "Valid-From Date
* I_PLNFL = "Sequence
* I_FILTER_EXPRESSION = "DE-EN-LANG-SWITCH-NO-TRANSLATION
* I_DATE_TO = DATE-MAX_GRG "Valid-to date
* I_MATERIAL = "Material Number
* I_PLANT = "Plant
* I_SALES_ORDER = "Sales Document
* I_SALES_ORDER_ITEM = "Sales Document Item
* I_PLNTY = "Task List Type
* I_PLNNR = "Key for Task List Group
* I_PLNAL = "Group Counter

TABLES
E_ODP_SEQ_CLASS_DATA = "Data for object dependencies for sequence class

EXCEPTIONS
WRONG_KEY = 1
.



IMPORTING Parameters details for CP_CC_S_ODP_SEQ_PROVIDE_BY_MTK

I_DATE_FROM - Valid-From Date

Data type: ODP_SEQ_CLASS_DATA-DATUV
Default: DATE-MIN_GRG
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_PLNFL - Sequence

Data type: ODP_SEQ_CLASS_DATA-PLNFL
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_FILTER_EXPRESSION - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type: RSDS_TRANGE
Optional: Yes
Call by Reference: Yes

I_DATE_TO - Valid-to date

Data type: ODP_SEQ_CLASS_DATA-DATUB
Default: DATE-MAX_GRG
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_MATERIAL - Material Number

Data type: MTK_CLASS_DATA-MATNR
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_PLANT - Plant

Data type: MTK_CLASS_DATA-WERKS
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_SALES_ORDER - Sales Document

Data type: MTK_CLASS_DATA-VBELN
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_SALES_ORDER_ITEM - Sales Document Item

Data type: MTK_CLASS_DATA-POSNR
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_PLNTY - Task List Type

Data type: ODP_SEQ_CLASS_DATA-PLNTY
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_PLNNR - Key for Task List Group

Data type: ODP_SEQ_CLASS_DATA-PLNNR
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_PLNAL - Group Counter

Data type: ODP_SEQ_CLASS_DATA-PLNAL
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for CP_CC_S_ODP_SEQ_PROVIDE_BY_MTK

E_ODP_SEQ_CLASS_DATA - Data for object dependencies for sequence class

Data type: ODP_SEQ_CLASS_DATA
Optional: 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 CP_CC_S_ODP_SEQ_PROVIDE_BY_MTK 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_plnfl  TYPE ODP_SEQ_CLASS_DATA-PLNFL, "   
lv_i_filter_expression  TYPE RSDS_TRANGE, "   
lv_i_date_to  TYPE ODP_SEQ_CLASS_DATA-DATUB, "   DATE-MAX_GRG
lv_i_material  TYPE MTK_CLASS_DATA-MATNR, "   
lv_i_plant  TYPE MTK_CLASS_DATA-WERKS, "   
lv_i_sales_order  TYPE MTK_CLASS_DATA-VBELN, "   
lv_i_sales_order_item  TYPE MTK_CLASS_DATA-POSNR, "   
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. "   

  CALL FUNCTION 'CP_CC_S_ODP_SEQ_PROVIDE_BY_MTK'  "NOTRANSL: Bereitstellung von Beziehungswissen Folge
    EXPORTING
         I_DATE_FROM = lv_i_date_from
         I_PLNFL = lv_i_plnfl
         I_FILTER_EXPRESSION = lv_i_filter_expression
         I_DATE_TO = lv_i_date_to
         I_MATERIAL = lv_i_material
         I_PLANT = lv_i_plant
         I_SALES_ORDER = lv_i_sales_order
         I_SALES_ORDER_ITEM = lv_i_sales_order_item
         I_PLNTY = lv_i_plnty
         I_PLNNR = lv_i_plnnr
         I_PLNAL = lv_i_plnal
    TABLES
         E_ODP_SEQ_CLASS_DATA = lt_e_odp_seq_class_data
    EXCEPTIONS
        WRONG_KEY = 1
. " CP_CC_S_ODP_SEQ_PROVIDE_BY_MTK




ABAP code using 7.40 inline data declarations to call FM CP_CC_S_ODP_SEQ_PROVIDE_BY_MTK

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 PLNFL FROM ODP_SEQ_CLASS_DATA INTO @DATA(ld_i_plnfl).
 
 
"SELECT single DATUB FROM ODP_SEQ_CLASS_DATA INTO @DATA(ld_i_date_to).
DATA(ld_i_date_to) = DATE-MAX_GRG.
 
"SELECT single MATNR FROM MTK_CLASS_DATA INTO @DATA(ld_i_material).
 
"SELECT single WERKS FROM MTK_CLASS_DATA INTO @DATA(ld_i_plant).
 
"SELECT single VBELN FROM MTK_CLASS_DATA INTO @DATA(ld_i_sales_order).
 
"SELECT single POSNR FROM MTK_CLASS_DATA INTO @DATA(ld_i_sales_order_item).
 
"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).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!