SAP GRFN_ISSUE_AUTH_DELETE Function Module for auth create
GRFN_ISSUE_AUTH_DELETE is a standard grfn issue auth delete SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for auth create 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 grfn issue auth delete FM, simply by entering the name GRFN_ISSUE_AUTH_DELETE into the relevant SAP transaction such as SE37 or SE38.
Function Group: GRFN_ISSUE_AUTH
Program Name: SAPLGRFN_ISSUE_AUTH
Main Program: SAPLGRFN_ISSUE_AUTH
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1

Function GRFN_ISSUE_AUTH_DELETE 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 'GRFN_ISSUE_AUTH_DELETE'"auth create.
EXPORTING
IV_OBJECT_ID = "Object ID
EXCEPTIONS
DB_ENTRY_NOT_EXIST = 1
IMPORTING Parameters details for GRFN_ISSUE_AUTH_DELETE
IV_OBJECT_ID - Object ID
Data type: GRFN_API_OBJECT_IDOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
DB_ENTRY_NOT_EXIST -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for GRFN_ISSUE_AUTH_DELETE 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_iv_object_id | TYPE GRFN_API_OBJECT_ID, " | |||
| lv_db_entry_not_exist | TYPE GRFN_API_OBJECT_ID. " |
|   CALL FUNCTION 'GRFN_ISSUE_AUTH_DELETE' "auth create |
| EXPORTING | ||
| IV_OBJECT_ID | = lv_iv_object_id | |
| EXCEPTIONS | ||
| DB_ENTRY_NOT_EXIST = 1 | ||
| . " GRFN_ISSUE_AUTH_DELETE | ||
ABAP code using 7.40 inline data declarations to call FM GRFN_ISSUE_AUTH_DELETE
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