SAP FCOM_SRULE_DATA_WRITE Function Module for Write Data
FCOM_SRULE_DATA_WRITE is a standard fcom srule data write SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Write Data 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 fcom srule data write FM, simply by entering the name FCOM_SRULE_DATA_WRITE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FCOM_MD_SRULE
Program Name: SAPLFCOM_MD_SRULE
Main Program: SAPLFCOM_MD_SRULE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FCOM_SRULE_DATA_WRITE 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 'FCOM_SRULE_DATA_WRITE'"Write Data.
EXPORTING
IS_GDATA = "Buffer of COBRA
IMPORTING
EB_ERROR = "Boolean Variable (X=True, -=False, Space=Unknown)
ET_MESSAGES = "Table with BAPI Return Information
IMPORTING Parameters details for FCOM_SRULE_DATA_WRITE
IS_GDATA - Buffer of COBRA
Data type: FCOMS_SRULE_GDATAOptional: No
Call by Reference: Yes
EXPORTING Parameters details for FCOM_SRULE_DATA_WRITE
EB_ERROR - Boolean Variable (X=True, -=False, Space=Unknown)
Data type: BOOLEANOptional: No
Call by Reference: Yes
ET_MESSAGES - Table with BAPI Return Information
Data type: BAPIRETTABOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FCOM_SRULE_DATA_WRITE 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_eb_error | TYPE BOOLEAN, " | |||
| lv_is_gdata | TYPE FCOMS_SRULE_GDATA, " | |||
| lv_et_messages | TYPE BAPIRETTAB. " |
|   CALL FUNCTION 'FCOM_SRULE_DATA_WRITE' "Write Data |
| EXPORTING | ||
| IS_GDATA | = lv_is_gdata | |
| IMPORTING | ||
| EB_ERROR | = lv_eb_error | |
| ET_MESSAGES | = lv_et_messages | |
| . " FCOM_SRULE_DATA_WRITE | ||
ABAP code using 7.40 inline data declarations to call FM FCOM_SRULE_DATA_WRITE
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