SAP AC_FLUSH_CALL_INTERNAL Function Module for
AC_FLUSH_CALL_INTERNAL is a standard ac flush call internal 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 ac flush call internal FM, simply by entering the name AC_FLUSH_CALL_INTERNAL into the relevant SAP transaction such as SE37 or SE38.
Function Group: OLEA
Program Name: SAPLOLEA
Main Program: SAPLOLEA
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function AC_FLUSH_CALL_INTERNAL 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 'AC_FLUSH_CALL_INTERNAL'".
EXPORTING
* SYSTEM_FLUSH = "
IMPORTING
MESSAGE_NR = "
MESSAGE_TEXT = "
CHANGING
* XML_DATA_STRING = "
TABLES
* XML_DATA_STREAM = "
EXCEPTIONS
SYSTEM_FAILURE = 1 CALL_METHOD_FAILED = 2 SET_PROPERTY_FAILED = 3 GET_PROPERTY_FAILED = 4 RFC_QUEUE_FAILED = 5 XML_DATA_FAILED = 6 UNKNOWN_ERROR = 7 COMMUNICATION_FAILURE = 8 GUI_NO_MODE_AVAILABLE = 9
IMPORTING Parameters details for AC_FLUSH_CALL_INTERNAL
SYSTEM_FLUSH -
Data type: COptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for AC_FLUSH_CALL_INTERNAL
MESSAGE_NR -
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
MESSAGE_TEXT -
Data type: SY-MSGLIOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for AC_FLUSH_CALL_INTERNAL
XML_DATA_STRING -
Data type: STRINGOptional: Yes
Call by Reference: Yes
TABLES Parameters details for AC_FLUSH_CALL_INTERNAL
XML_DATA_STREAM -
Data type:Optional: Yes
Call by Reference: Yes
EXCEPTIONS details
SYSTEM_FAILURE -
Data type:Optional: No
Call by Reference: Yes
CALL_METHOD_FAILED -
Data type:Optional: No
Call by Reference: Yes
SET_PROPERTY_FAILED -
Data type:Optional: No
Call by Reference: Yes
GET_PROPERTY_FAILED -
Data type:Optional: No
Call by Reference: Yes
RFC_QUEUE_FAILED -
Data type:Optional: No
Call by Reference: Yes
XML_DATA_FAILED -
Data type:Optional: No
Call by Reference: Yes
UNKNOWN_ERROR -
Data type:Optional: No
Call by Reference: Yes
COMMUNICATION_FAILURE -
Data type:Optional: No
Call by Reference: Yes
GUI_NO_MODE_AVAILABLE -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for AC_FLUSH_CALL_INTERNAL 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_message_nr | TYPE SY-SUBRC, " | |||
lv_system_flush | TYPE C, " | |||
lv_system_failure | TYPE C, " | |||
lt_xml_data_stream | TYPE STANDARD TABLE OF C, " | |||
lv_xml_data_string | TYPE STRING, " | |||
lv_message_text | TYPE SY-MSGLI, " | |||
lv_call_method_failed | TYPE SY, " | |||
lv_set_property_failed | TYPE SY, " | |||
lv_get_property_failed | TYPE SY, " | |||
lv_rfc_queue_failed | TYPE SY, " | |||
lv_xml_data_failed | TYPE SY, " | |||
lv_unknown_error | TYPE SY, " | |||
lv_communication_failure | TYPE SY, " | |||
lv_gui_no_mode_available | TYPE SY. " |
  CALL FUNCTION 'AC_FLUSH_CALL_INTERNAL' " |
EXPORTING | ||
SYSTEM_FLUSH | = lv_system_flush | |
IMPORTING | ||
MESSAGE_NR | = lv_message_nr | |
MESSAGE_TEXT | = lv_message_text | |
CHANGING | ||
XML_DATA_STRING | = lv_xml_data_string | |
TABLES | ||
XML_DATA_STREAM | = lt_xml_data_stream | |
EXCEPTIONS | ||
SYSTEM_FAILURE = 1 | ||
CALL_METHOD_FAILED = 2 | ||
SET_PROPERTY_FAILED = 3 | ||
GET_PROPERTY_FAILED = 4 | ||
RFC_QUEUE_FAILED = 5 | ||
XML_DATA_FAILED = 6 | ||
UNKNOWN_ERROR = 7 | ||
COMMUNICATION_FAILURE = 8 | ||
GUI_NO_MODE_AVAILABLE = 9 | ||
. " AC_FLUSH_CALL_INTERNAL |
ABAP code using 7.40 inline data declarations to call FM AC_FLUSH_CALL_INTERNAL
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 SUBRC FROM SY INTO @DATA(ld_message_nr). | ||||
"SELECT single MSGLI FROM SY INTO @DATA(ld_message_text). | ||||
Search for further information about these or an SAP related objects