SAP CACS27_FFLT_READ_SAMPLE Function Module for LOS: Read Fulfillment Level and Update Settlement Schedule Item if Nec.
CACS27_FFLT_READ_SAMPLE is a standard cacs27 fflt read sample SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for LOS: Read Fulfillment Level and Update Settlement Schedule Item if Nec. 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 cacs27 fflt read sample FM, simply by entering the name CACS27_FFLT_READ_SAMPLE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CACS27_AC_LOS
Program Name: SAPLCACS27_AC_LOS
Main Program: SAPLCACS27_AC_LOS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CACS27_FFLT_READ_SAMPLE 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 'CACS27_FFLT_READ_SAMPLE'"LOS: Read Fulfillment Level and Update Settlement Schedule Item if Nec..
EXPORTING
I_FFLGUID = "GUID in 25-Byte Packed Format
* I_XUPDATESTATUS = '' "
I_SIMU = "Boolean Variable (X=True, -=False, Space=Unknown)
* I_BUSITIME = "Effective Validity (Time Stamp YYYY.MM.DD hh:mm:ss)
* I_TECHTIME = "Technical Validity (Time Stamp: YYYY.MM.DD hh:mm:ss)
* I_OTC = "Object Type Class (OTC) for Logical Service
* I_TOOL = "Tools for Logical Service
IMPORTING
E_FFL_FROM = "Application Log: Table with Messages
E_FFL_TO = "To
E_FFL = "Fulfillment Level
E_RELEASED = "Settlement Schedule Item: Actual Commission Release Status
CHANGING
* C_FLG_ERROR = "Indicator: Commn Case Inconsistent (X = error, ' ' = ok)
C_LOG_HANDLE = "Application Log: Log Handle
IMPORTING Parameters details for CACS27_FFLT_READ_SAMPLE
I_FFLGUID - GUID in 25-Byte Packed Format
Data type: CACSGUIDCOptional: No
Call by Reference: Yes
I_XUPDATESTATUS -
Data type: CHAR01Default: ''
Optional: Yes
Call by Reference: Yes
I_SIMU - Boolean Variable (X=True, -=False, Space=Unknown)
Data type: BOOLEANOptional: No
Call by Reference: Yes
I_BUSITIME - Effective Validity (Time Stamp YYYY.MM.DD hh:mm:ss)
Data type: CACSBUSITIMEOptional: Yes
Call by Reference: Yes
I_TECHTIME - Technical Validity (Time Stamp: YYYY.MM.DD hh:mm:ss)
Data type: CACSTECHTIMEOptional: Yes
Call by Reference: Yes
I_OTC - Object Type Class (OTC) for Logical Service
Data type: CACS_LOS_OTCOptional: Yes
Call by Reference: Yes
I_TOOL - Tools for Logical Service
Data type: CACS_LOS_TOOLOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for CACS27_FFLT_READ_SAMPLE
E_FFL_FROM - Application Log: Table with Messages
Data type: CACSFROMOptional: No
Call by Reference: Yes
E_FFL_TO - To
Data type: CACSTOOptional: No
Call by Reference: Yes
E_FFL - Fulfillment Level
Data type: CACSFFLOptional: No
Call by Reference: Yes
E_RELEASED - Settlement Schedule Item: Actual Commission Release Status
Data type: CACSSESFFLSTATUSOptional: No
Call by Reference: Yes
CHANGING Parameters details for CACS27_FFLT_READ_SAMPLE
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
Copy and paste ABAP code example for CACS27_FFLT_READ_SAMPLE 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_i_fflguid | TYPE CACSGUIDC, " | |||
| lv_e_ffl_from | TYPE CACSFROM, " | |||
| lv_c_flg_error | TYPE CACSCASEERROR, " | |||
| lv_e_ffl_to | TYPE CACSTO, " | |||
| lv_c_log_handle | TYPE BALLOGHNDL, " | |||
| lv_i_xupdatestatus | TYPE CHAR01, " '' | |||
| lv_e_ffl | TYPE CACSFFL, " | |||
| lv_i_simu | TYPE BOOLEAN, " | |||
| lv_e_released | TYPE CACSSESFFLSTATUS, " | |||
| lv_i_busitime | TYPE CACSBUSITIME, " | |||
| lv_i_techtime | TYPE CACSTECHTIME, " | |||
| lv_i_otc | TYPE CACS_LOS_OTC, " | |||
| lv_i_tool | TYPE CACS_LOS_TOOL. " |
|   CALL FUNCTION 'CACS27_FFLT_READ_SAMPLE' "LOS: Read Fulfillment Level and Update Settlement Schedule Item if Nec. |
| EXPORTING | ||
| I_FFLGUID | = lv_i_fflguid | |
| I_XUPDATESTATUS | = lv_i_xupdatestatus | |
| I_SIMU | = lv_i_simu | |
| I_BUSITIME | = lv_i_busitime | |
| I_TECHTIME | = lv_i_techtime | |
| I_OTC | = lv_i_otc | |
| I_TOOL | = lv_i_tool | |
| IMPORTING | ||
| E_FFL_FROM | = lv_e_ffl_from | |
| E_FFL_TO | = lv_e_ffl_to | |
| E_FFL | = lv_e_ffl | |
| E_RELEASED | = lv_e_released | |
| CHANGING | ||
| C_FLG_ERROR | = lv_c_flg_error | |
| C_LOG_HANDLE | = lv_c_log_handle | |
| . " CACS27_FFLT_READ_SAMPLE | ||
ABAP code using 7.40 inline data declarations to call FM CACS27_FFLT_READ_SAMPLE
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.| DATA(ld_i_xupdatestatus) | = ''. | |||
Search for further information about these or an SAP related objects