SAP CP_CC_P_IMPORT_SEQ Function Module for NOTRANSL: Bearbeiten von Folgen im Direct Input









CP_CC_P_IMPORT_SEQ is a standard cp cc p import seq 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: Bearbeiten von Folgen im Direct Input 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 p import seq FM, simply by entering the name CP_CC_P_IMPORT_SEQ into the relevant SAP transaction such as SE37 or SE38.

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



Function CP_CC_P_IMPORT_SEQ 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_P_IMPORT_SEQ'"NOTRANSL: Bearbeiten von Folgen im Direct Input
EXPORTING
I_TRANSACTION_HEADER_INTERF = "
I_SEQ_DATA_INTERF = "Sequences
I_OPR_DATA_INTERF = "Operations
* I_OPR_REF_DATA_INTERF = "
* I_OPR_WC_REF_DATA_INTERF = "Standard Tasks
* I_OPR_ALLOC_DATA_INTERF = "
I_PLNTY = "
I_PLNNR = "Task List Group
I_PLNAL = "Group Counter

TABLES
* RETURN = "Return Parameter(s)
.



IMPORTING Parameters details for CP_CC_P_IMPORT_SEQ

I_TRANSACTION_HEADER_INTERF -

Data type: TRANSFER_HEADER_INTERFACE
Optional: No
Call by Reference: Yes

I_SEQ_DATA_INTERF - Sequences

Data type: CPCDT_SEQ_INTERF_TAB_TYPE
Optional: No
Call by Reference: Yes

I_OPR_DATA_INTERF - Operations

Data type: CPCDT_OPR_INTERF_TAB_TYPE
Optional: No
Call by Reference: Yes

I_OPR_REF_DATA_INTERF -

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

I_OPR_WC_REF_DATA_INTERF - Standard Tasks

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

I_OPR_ALLOC_DATA_INTERF -

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

I_PLNTY -

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

I_PLNNR - Task List Group

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

I_PLNAL - Group Counter

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

TABLES Parameters details for CP_CC_P_IMPORT_SEQ

RETURN - Return Parameter(s)

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

Copy and paste ABAP code example for CP_CC_P_IMPORT_SEQ 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:
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_i_transaction_header_interf  TYPE TRANSFER_HEADER_INTERFACE, "   
lv_i_seq_data_interf  TYPE CPCDT_SEQ_INTERF_TAB_TYPE, "   
lv_i_opr_data_interf  TYPE CPCDT_OPR_INTERF_TAB_TYPE, "   
lv_i_opr_ref_data_interf  TYPE CPCDT_OPR_REF_INTERF_TAB_TYPE, "   
lv_i_opr_wc_ref_data_interf  TYPE CPCDT_OPR_WC_REF_INTERF_TAB_TP, "   
lv_i_opr_alloc_data_interf  TYPE CPCDT_OPR_ALLOC_INTERF_TB_TP, "   
lv_i_plnty  TYPE TSK_CLASS_DATA-PLNTY, "   
lv_i_plnnr  TYPE TSK_CLASS_DATA-PLNNR, "   
lv_i_plnal  TYPE TSK_CLASS_DATA-PLNAL. "   

  CALL FUNCTION 'CP_CC_P_IMPORT_SEQ'  "NOTRANSL: Bearbeiten von Folgen im Direct Input
    EXPORTING
         I_TRANSACTION_HEADER_INTERF = lv_i_transaction_header_interf
         I_SEQ_DATA_INTERF = lv_i_seq_data_interf
         I_OPR_DATA_INTERF = lv_i_opr_data_interf
         I_OPR_REF_DATA_INTERF = lv_i_opr_ref_data_interf
         I_OPR_WC_REF_DATA_INTERF = lv_i_opr_wc_ref_data_interf
         I_OPR_ALLOC_DATA_INTERF = lv_i_opr_alloc_data_interf
         I_PLNTY = lv_i_plnty
         I_PLNNR = lv_i_plnnr
         I_PLNAL = lv_i_plnal
    TABLES
         RETURN = lt_return
. " CP_CC_P_IMPORT_SEQ




ABAP code using 7.40 inline data declarations to call FM CP_CC_P_IMPORT_SEQ

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 PLNTY FROM TSK_CLASS_DATA INTO @DATA(ld_i_plnty).
 
"SELECT single PLNNR FROM TSK_CLASS_DATA INTO @DATA(ld_i_plnnr).
 
"SELECT single PLNAL FROM TSK_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!