SAP CACS_GET_FFL_SEQ1 Function Module for NOTRANSL: Lese SEQ_ID 1 FFL's mittels Objekt- und Zeitdaten
CACS_GET_FFL_SEQ1 is a standard cacs get ffl seq1 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: Lese SEQ_ID 1 FFL's mittels Objekt- und Zeitdaten 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 cacs get ffl seq1 FM, simply by entering the name CACS_GET_FFL_SEQ1 into the relevant SAP transaction such as SE37 or SE38.
Function Group: CACS_FFLT_DBIF
Program Name: SAPLCACS_FFLT_DBIF
Main Program: SAPLCACS_FFLT_DBIF
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CACS_GET_FFL_SEQ1 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 'CACS_GET_FFL_SEQ1'"NOTRANSL: Lese SEQ_ID 1 FFL's mittels Objekt- und Zeitdaten.
EXPORTING
I_FFL_FROM = "From
I_FFL_TO = "To
CHANGING
* C_FLG_ERROR = "Indicator: Commn Case Inconsistent (X = error, ' ' = ok)
C_LOG_HANDLE = "Application Log: Log Handle
TABLES
IT_OBJ = "Fulfillment Level Object Fields
ET_CACS_FFLTIT = "Fulfillment Level Item
EXCEPTIONS
INCOMPLETE_OBJECT_DATA = 1 INVAILD_OBJ_DATA_CONSTELLATION = 2 ILLEGAL_DATES = 3 NO_ENTRIES_FOUND = 4
IMPORTING Parameters details for CACS_GET_FFL_SEQ1
I_FFL_FROM - From
Data type: CACSFROMOptional: No
Call by Reference: Yes
I_FFL_TO - To
Data type: CACSTOOptional: No
Call by Reference: Yes
CHANGING Parameters details for CACS_GET_FFL_SEQ1
C_FLG_ERROR - Indicator: Commn Case Inconsistent (X = error, ' ' = ok)
Data type: CACSCASEERROROptional: Yes
Call by Reference: Yes
C_LOG_HANDLE - Application Log: Log Handle
Data type: BALLOGHNDLOptional: No
Call by Reference: Yes
TABLES Parameters details for CACS_GET_FFL_SEQ1
IT_OBJ - Fulfillment Level Object Fields
Data type: CACS_S_FFLT_OBJOptional: No
Call by Reference: Yes
ET_CACS_FFLTIT - Fulfillment Level Item
Data type: CACS_S_FFLTITOptional: No
Call by Reference: Yes
EXCEPTIONS details
INCOMPLETE_OBJECT_DATA - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
INVAILD_OBJ_DATA_CONSTELLATION - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
ILLEGAL_DATES - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
NO_ENTRIES_FOUND - No entries found
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CACS_GET_FFL_SEQ1 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_it_obj | TYPE STANDARD TABLE OF CACS_S_FFLT_OBJ, " | |||
| lv_i_ffl_from | TYPE CACSFROM, " | |||
| lv_c_flg_error | TYPE CACSCASEERROR, " | |||
| lv_incomplete_object_data | TYPE CACSCASEERROR, " | |||
| lv_i_ffl_to | TYPE CACSTO, " | |||
| lv_c_log_handle | TYPE BALLOGHNDL, " | |||
| lt_et_cacs_ffltit | TYPE STANDARD TABLE OF CACS_S_FFLTIT, " | |||
| lv_invaild_obj_data_constellation | TYPE CACS_S_FFLTIT, " | |||
| lv_illegal_dates | TYPE CACS_S_FFLTIT, " | |||
| lv_no_entries_found | TYPE CACS_S_FFLTIT. " |
|   CALL FUNCTION 'CACS_GET_FFL_SEQ1' "NOTRANSL: Lese SEQ_ID 1 FFL's mittels Objekt- und Zeitdaten |
| EXPORTING | ||
| I_FFL_FROM | = lv_i_ffl_from | |
| I_FFL_TO | = lv_i_ffl_to | |
| CHANGING | ||
| C_FLG_ERROR | = lv_c_flg_error | |
| C_LOG_HANDLE | = lv_c_log_handle | |
| TABLES | ||
| IT_OBJ | = lt_it_obj | |
| ET_CACS_FFLTIT | = lt_et_cacs_ffltit | |
| EXCEPTIONS | ||
| INCOMPLETE_OBJECT_DATA = 1 | ||
| INVAILD_OBJ_DATA_CONSTELLATION = 2 | ||
| ILLEGAL_DATES = 3 | ||
| NO_ENTRIES_FOUND = 4 | ||
| . " CACS_GET_FFL_SEQ1 | ||
ABAP code using 7.40 inline data declarations to call FM CACS_GET_FFL_SEQ1
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