SAP CNV_00001_CHECK_SEQUENCE Function Module for Check relationships between tables

Search SAP Function Modules

CNV_00001_CHECK_SEQUENCE is a standard cnv 00001 check sequence SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check relationships between tables 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 cnv 00001 check sequence FM, simply by entering the name CNV_00001_CHECK_SEQUENCE into the relevant SAP transaction such as SE37 or SE38.

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

Function CNV_00001_CHECK_SEQUENCE 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 'CNV_00001_CHECK_SEQUENCE'"Check relationships between tables
  EXPORTING
*  PACKID =  "Conversion: Conversion package number
*  FIND_CYCLE =  "Define whether a cycle should be found in case of conflicts
*  TAB_RELATIONSHIPS =  "Additional relationships between tables
*  TAB_SEQNUM =  "Conversion: Structure for new sequence of tables
*  MANDT =  "Client
*  CNVPACK =  "Standard table of CNVPACK

 IMPORTING
   CONFLICT =  "Conflict between relationships occurs
   CYCLE =  "Sequence relatioships between tables

.

IMPORTING Parameters details for CNV_00001_CHECK_SEQUENCE

PACKID - Conversion: Conversion package number

Data type: CNVPACK-PACKID
Optional: Yes
Call by Reference: Yes

FIND_CYCLE - Define whether a cycle should be found in case of conflicts

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

TAB_RELATIONSHIPS - Additional relationships between tables

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

TAB_SEQNUM - Conversion: Structure for new sequence of tables

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

MANDT - Client

Data type: T000-MANDT
Optional: Yes
Call by Reference: Yes

CNVPACK - Standard table of CNVPACK

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

EXPORTING Parameters details for CNV_00001_CHECK_SEQUENCE

CONFLICT - Conflict between relationships occurs

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

CYCLE - Sequence relatioships between tables

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

Copy and paste ABAP code example for CNV_00001_CHECK_SEQUENCE 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.

ABAP code using 7.40 inline data declarations to call FM CNV_00001_CHECK_SEQUENCE

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.

Search for further information about these or an SAP related objects