SAP CCSEQ_CYCLE_READ Function Module for NOTRANSL: Zyklen Änderungsreihenfolgegraph lesen
CCSEQ_CYCLE_READ is a standard ccseq cycle read 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: Zyklen Änderungsreihenfolgegraph lesen 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 ccseq cycle read FM, simply by entering the name CCSEQ_CYCLE_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: CCSEQ_DB
Program Name: SAPLCCSEQ_DB
Main Program: SAPLCCSEQ_DB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CCSEQ_CYCLE_READ 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 'CCSEQ_CYCLE_READ'"NOTRANSL: Zyklen Änderungsreihenfolgegraph lesen.
EXPORTING
* IV_ONLY_ONCE = "DE-EN-LANG-SWITCH-NO-TRANSLATION
* IT_AENNR = "Change Numbers
IMPORTING
ET_CYCLE = "Cycles in Change Sequence Graph
IMPORTING Parameters details for CCSEQ_CYCLE_READ
IV_ONLY_ONCE - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: XFELDOptional: Yes
Call by Reference: Yes
IT_AENNR - Change Numbers
Data type: AENNR_TOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for CCSEQ_CYCLE_READ
ET_CYCLE - Cycles in Change Sequence Graph
Data type: CCSEQ_T_CYCLEOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CCSEQ_CYCLE_READ 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_et_cycle | TYPE CCSEQ_T_CYCLE, " | |||
| lv_iv_only_once | TYPE XFELD, " | |||
| lv_it_aennr | TYPE AENNR_T. " |
|   CALL FUNCTION 'CCSEQ_CYCLE_READ' "NOTRANSL: Zyklen Änderungsreihenfolgegraph lesen |
| EXPORTING | ||
| IV_ONLY_ONCE | = lv_iv_only_once | |
| IT_AENNR | = lv_it_aennr | |
| IMPORTING | ||
| ET_CYCLE | = lv_et_cycle | |
| . " CCSEQ_CYCLE_READ | ||
ABAP code using 7.40 inline data declarations to call FM CCSEQ_CYCLE_READ
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