SAP /FSCAA/BAPI_SO_DELETE_EXEC Function Module for delete a standing order

Search SAP Function Modules

/FSCAA/BAPI_SO_DELETE_EXEC is a standard /fscaa/bapi so delete exec SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for delete a standing order 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 /fscaa/bapi so delete exec FM, simply by entering the name /FSCAA/BAPI_SO_DELETE_EXEC into the relevant SAP transaction such as SE37 or SE38.

Function Group: /FSCAA/SERVICES
Program Name: /FSCAA/SAPLSERVICES
Main Program: /FSCAA/SAPLSERVICES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function /FSCAA/BAPI_SO_DELETE_EXEC 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 '/FSCAA/BAPI_SO_DELETE_EXEC'"delete a standing order
  EXPORTING
*  PI_TRANS_ID =  "GUID im 'CHAR' Format in Großschreibung
   PI_STANDING_ORDER_ID =  "Standing Order identification
*  PI_TAB_EXTENSIONS =  "Table: Key value pairs for BAPI Extensions

 IMPORTING
   PE_TRANS_ID =  "GUID im 'CHAR' Format in Großschreibung
   PE_TAB_MESSAGES =  "Returnparameter
   PE_SUBRC =  "Return value

.

IMPORTING Parameters details for /FSCAA/BAPI_SO_DELETE_EXEC

PI_TRANS_ID - GUID im 'CHAR' Format in Großschreibung

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

PI_STANDING_ORDER_ID - Standing Order identification

Data type: /FSCAA/STANDING_ORDER_ID
Optional: No
Call by Reference: No ( called with pass by value option)

PI_TAB_EXTENSIONS - Table: Key value pairs for BAPI Extensions

Data type: /FSCAA/TAB_EXTENSIONS
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for /FSCAA/BAPI_SO_DELETE_EXEC

PE_TRANS_ID - GUID im 'CHAR' Format in Großschreibung

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

PE_TAB_MESSAGES - Returnparameter

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

PE_SUBRC - Return value

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

Copy and paste ABAP code example for /FSCAA/BAPI_SO_DELETE_EXEC 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 /FSCAA/BAPI_SO_DELETE_EXEC

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