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

Function GRFN_AE_SAVE 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_AE_SAVE'"Audit Enity Save(Create/Update).
EXPORTING
IS_AE = "AE
EXCEPTIONS
DB_ENTRY_AE_ERROR = 1 DB_ENTRY_AO_ERROR = 2
IMPORTING Parameters details for GRFN_AE_SAVE
IS_AE - AE
Data type: GRFN_S_AEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
DB_ENTRY_AE_ERROR -
Data type:Optional: No
Call by Reference: Yes
DB_ENTRY_AO_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for GRFN_AE_SAVE 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_is_ae | TYPE GRFN_S_AE, " | |||
| lv_db_entry_ae_error | TYPE GRFN_S_AE, " | |||
| lv_db_entry_ao_error | TYPE GRFN_S_AE. " |
|   CALL FUNCTION 'GRFN_AE_SAVE' "Audit Enity Save(Create/Update) |
| EXPORTING | ||
| IS_AE | = lv_is_ae | |
| EXCEPTIONS | ||
| DB_ENTRY_AE_ERROR = 1 | ||
| DB_ENTRY_AO_ERROR = 2 | ||
| . " GRFN_AE_SAVE | ||
ABAP code using 7.40 inline data declarations to call FM GRFN_AE_SAVE
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