SAP /ACCGO/BAPI_DELETE_CAS_EVENTS Function Module for BAPI to Delete Application Events
/ACCGO/BAPI_DELETE_CAS_EVENTS is a standard /accgo/bapi delete cas events SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BAPI to Delete Application Events 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 /accgo/bapi delete cas events FM, simply by entering the name /ACCGO/BAPI_DELETE_CAS_EVENTS into the relevant SAP transaction such as SE37 or SE38.
Function Group: /ACCGO/CAS_EVENTS
Program Name: /ACCGO/SAPLCAS_EVENTS
Main Program: /ACCGO/SAPLCAS_EVENTS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function /ACCGO/BAPI_DELETE_CAS_EVENTS 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 '/ACCGO/BAPI_DELETE_CAS_EVENTS'"BAPI to Delete Application Events.
EXPORTING
IV_EVENT_GUID = "
TABLES
ET_MESSAGES = "
IMPORTING Parameters details for /ACCGO/BAPI_DELETE_CAS_EVENTS
IV_EVENT_GUID -
Data type: /ACCGO/E_EVENT_GUIDOptional: No
Call by Reference: Yes
TABLES Parameters details for /ACCGO/BAPI_DELETE_CAS_EVENTS
ET_MESSAGES -
Data type: BAPIRET2Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for /ACCGO/BAPI_DELETE_CAS_EVENTS 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_et_messages | TYPE STANDARD TABLE OF BAPIRET2, " | |||
lv_iv_event_guid | TYPE /ACCGO/E_EVENT_GUID. " |
  CALL FUNCTION '/ACCGO/BAPI_DELETE_CAS_EVENTS' "BAPI to Delete Application Events |
EXPORTING | ||
IV_EVENT_GUID | = lv_iv_event_guid | |
TABLES | ||
ET_MESSAGES | = lt_et_messages | |
. " /ACCGO/BAPI_DELETE_CAS_EVENTS |
ABAP code using 7.40 inline data declarations to call FM /ACCGO/BAPI_DELETE_CAS_EVENTS
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