SAP FCXL_CS_GET_DATA Function Module for
FCXL_CS_GET_DATA is a standard fcxl cs get data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 fcxl cs get data FM, simply by entering the name FCXL_CS_GET_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: FCXS
Program Name: SAPLFCXS
Main Program: SAPLFCXS
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function FCXL_CS_GET_DATA 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 'FCXL_CS_GET_DATA'".
EXPORTING
SIGN_HANDLING = "
RETURN_UNITS = "
* ASPECT_ID = 'CS' "
TABLES
I_REQUEST = "
E_DATA = "
E_MESSAGE = "
E_ERROR = "
EXCEPTIONS
CHARACTERISTIC_NOT_FOUND = 1 HIERARCHY_NOT_FOUND = 2 ILLEGAL_SIGN_HANDLING = 3 CHARACTERISTIC_VALUE_NOT_FOUND = 4 NO_X_SPECIFIED = 5 NO_Y_SPECIFIED = 6 NON_SUMMABLE_CHAR_MISSING = 7 OTHER_ERROR = 8
IMPORTING Parameters details for FCXL_CS_GET_DATA
SIGN_HANDLING -
Data type: SY-DAYSTOptional: No
Call by Reference: No ( called with pass by value option)
RETURN_UNITS -
Data type: SY-DAYSTOptional: No
Call by Reference: No ( called with pass by value option)
ASPECT_ID -
Data type: FCXL_CASPS-ASPECT_IDDefault: 'CS'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FCXL_CS_GET_DATA
I_REQUEST -
Data type: FCXL_DREQVOptional: No
Call by Reference: No ( called with pass by value option)
E_DATA -
Data type: FCXL_DATAOptional: No
Call by Reference: No ( called with pass by value option)
E_MESSAGE -
Data type: FCXL_MESSGOptional: No
Call by Reference: No ( called with pass by value option)
E_ERROR -
Data type: FCXL_ERROROptional: No
Call by Reference: Yes
EXCEPTIONS details
CHARACTERISTIC_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
HIERARCHY_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ILLEGAL_SIGN_HANDLING -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CHARACTERISTIC_VALUE_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_X_SPECIFIED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_Y_SPECIFIED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NON_SUMMABLE_CHAR_MISSING -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OTHER_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FCXL_CS_GET_DATA 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_i_request | TYPE STANDARD TABLE OF FCXL_DREQV, " | |||
| lv_sign_handling | TYPE SY-DAYST, " | |||
| lv_characteristic_not_found | TYPE SY, " | |||
| lt_e_data | TYPE STANDARD TABLE OF FCXL_DATA, " | |||
| lv_return_units | TYPE SY-DAYST, " | |||
| lv_hierarchy_not_found | TYPE SY, " | |||
| lv_aspect_id | TYPE FCXL_CASPS-ASPECT_ID, " 'CS' | |||
| lt_e_message | TYPE STANDARD TABLE OF FCXL_MESSG, " | |||
| lv_illegal_sign_handling | TYPE FCXL_MESSG, " | |||
| lt_e_error | TYPE STANDARD TABLE OF FCXL_ERROR, " | |||
| lv_characteristic_value_not_found | TYPE FCXL_ERROR, " | |||
| lv_no_x_specified | TYPE FCXL_ERROR, " | |||
| lv_no_y_specified | TYPE FCXL_ERROR, " | |||
| lv_non_summable_char_missing | TYPE FCXL_ERROR, " | |||
| lv_other_error | TYPE FCXL_ERROR. " |
|   CALL FUNCTION 'FCXL_CS_GET_DATA' " |
| EXPORTING | ||
| SIGN_HANDLING | = lv_sign_handling | |
| RETURN_UNITS | = lv_return_units | |
| ASPECT_ID | = lv_aspect_id | |
| TABLES | ||
| I_REQUEST | = lt_i_request | |
| E_DATA | = lt_e_data | |
| E_MESSAGE | = lt_e_message | |
| E_ERROR | = lt_e_error | |
| EXCEPTIONS | ||
| CHARACTERISTIC_NOT_FOUND = 1 | ||
| HIERARCHY_NOT_FOUND = 2 | ||
| ILLEGAL_SIGN_HANDLING = 3 | ||
| CHARACTERISTIC_VALUE_NOT_FOUND = 4 | ||
| NO_X_SPECIFIED = 5 | ||
| NO_Y_SPECIFIED = 6 | ||
| NON_SUMMABLE_CHAR_MISSING = 7 | ||
| OTHER_ERROR = 8 | ||
| . " FCXL_CS_GET_DATA | ||
ABAP code using 7.40 inline data declarations to call FM FCXL_CS_GET_DATA
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 DAYST FROM SY INTO @DATA(ld_sign_handling). | ||||
| "SELECT single DAYST FROM SY INTO @DATA(ld_return_units). | ||||
| "SELECT single ASPECT_ID FROM FCXL_CASPS INTO @DATA(ld_aspect_id). | ||||
| DATA(ld_aspect_id) | = 'CS'. | |||
Search for further information about these or an SAP related objects