SAP S_AUTH_DELETE_ORG Function Module for
S_AUTH_DELETE_ORG is a standard s auth delete org 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 s auth delete org FM, simply by entering the name S_AUTH_DELETE_ORG into the relevant SAP transaction such as SE37 or SE38.
Function Group: S_AUTH_TOOL_2
Program Name: SAPLS_AUTH_TOOL_2
Main Program: SAPLS_AUTH_TOOL_2
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function S_AUTH_DELETE_ORG 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 'S_AUTH_DELETE_ORG'".
EXPORTING
* NO_SAP_ROLES = "Customized ('C') or standard menu ('S') flag
EXCEPTIONS
FIELD_IS_NO_ORG = 1 ACTION_CANCELLED = 2 NOT_AUTHORIZED = 3
IMPORTING Parameters details for S_AUTH_DELETE_ORG
NO_SAP_ROLES - Customized ('C') or standard menu ('S') flag
Data type: SMENSAPNEW-CUSTOMIZEDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
FIELD_IS_NO_ORG -
Data type:Optional: No
Call by Reference: Yes
ACTION_CANCELLED -
Data type:Optional: No
Call by Reference: Yes
NOT_AUTHORIZED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for S_AUTH_DELETE_ORG 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_no_sap_roles | TYPE SMENSAPNEW-CUSTOMIZED, " | |||
| lv_field_is_no_org | TYPE SMENSAPNEW, " | |||
| lv_action_cancelled | TYPE SMENSAPNEW, " | |||
| lv_not_authorized | TYPE SMENSAPNEW. " |
|   CALL FUNCTION 'S_AUTH_DELETE_ORG' " |
| EXPORTING | ||
| NO_SAP_ROLES | = lv_no_sap_roles | |
| EXCEPTIONS | ||
| FIELD_IS_NO_ORG = 1 | ||
| ACTION_CANCELLED = 2 | ||
| NOT_AUTHORIZED = 3 | ||
| . " S_AUTH_DELETE_ORG | ||
ABAP code using 7.40 inline data declarations to call FM S_AUTH_DELETE_ORG
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 CUSTOMIZED FROM SMENSAPNEW INTO @DATA(ld_no_sap_roles). | ||||
Search for further information about these or an SAP related objects