SAP FCXL_050_SET_DATA Function Module for

Search SAP Function Modules

FCXL_050_SET_DATA is a standard fcxl 050 set 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 050 set data FM, simply by entering the name FCXL_050_SET_DATA into the relevant SAP transaction such as SE37 or SE38.

Function Group: GLAE
Program Name: SAPLGLAE
Main Program:
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function FCXL_050_SET_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_050_SET_DATA'"
  EXPORTING
   SIMULATE =  "
   SIGN_HANDLING =  "
*  ASPECT_ID = '050' "
*  UPDATEMODE =  "
*  WAIT =  "
*  CALLNO =  "

 IMPORTING
   SUCCESS =  "

TABLES
   I_REQUEST =  "
   I_DATA =  "
   E_ERROR =  "
   E_MESSAGE =  "

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 

.

IMPORTING Parameters details for FCXL_050_SET_DATA

SIMULATE -

Data type: SY-DAYST
Optional: No
Call by Reference: No ( called with pass by value option)

SIGN_HANDLING -

Data type: SY-DAYST
Optional: No
Call by Reference: No ( called with pass by value option)

ASPECT_ID -

Data type: FCXL_CASPS-ASPECT_ID
Default: '050'
Optional: Yes
Call by Reference: No ( called with pass by value option)

UPDATEMODE -

Data type: SY-DAYST
Optional: Yes
Call by Reference: No ( called with pass by value option)

WAIT -

Data type: SY-DAYST
Optional: Yes
Call by Reference: No ( called with pass by value option)

CALLNO -

Data type: FCXL_HIRVL-DEPTH
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for FCXL_050_SET_DATA

SUCCESS -

Data type: SY-DAYST
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for FCXL_050_SET_DATA

I_REQUEST -

Data type: FCXL_DREQV
Optional: No
Call by Reference: No ( called with pass by value option)

I_DATA -

Data type: FCXL_DATA
Optional: No
Call by Reference: No ( called with pass by value option)

E_ERROR -

Data type: FCXL_ERROR
Optional: No
Call by Reference: No ( called with pass by value option)

E_MESSAGE -

Data type: FCXL_MESSG
Optional: No
Call by Reference: No ( called with pass by value option)

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)

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

ABAP code using 7.40 inline data declarations to call FM FCXL_050_SET_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.

Search for further information about these or an SAP related objects