SAP BAPI_XMI_SET_AUDITLEVEL Function Module for Set Audit Level of an XMI Session
BAPI_XMI_SET_AUDITLEVEL is a standard bapi xmi set auditlevel SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Set Audit Level of an XMI Session 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 bapi xmi set auditlevel FM, simply by entering the name BAPI_XMI_SET_AUDITLEVEL into the relevant SAP transaction such as SE37 or SE38.
Function Group: SXMI
Program Name: SAPLSXMI
Main Program: SAPLSXMI
Appliation area: S
Release date: 29-Apr-1998
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_XMI_SET_AUDITLEVEL 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 'BAPI_XMI_SET_AUDITLEVEL'"Set Audit Level of an XMI Session.
EXPORTING
* AUDITLEVEL = "Required audit level
IMPORTING
RETURN = "
IMPORTING Parameters details for BAPI_XMI_SET_AUDITLEVEL
AUDITLEVEL - Required audit level
Data type: BAPIXMLOGR-AUDITLEVELOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_XMI_SET_AUDITLEVEL
RETURN -
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_XMI_SET_AUDITLEVEL 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_return | TYPE BAPIRET2, " | |||
| lv_auditlevel | TYPE BAPIXMLOGR-AUDITLEVEL. " |
|   CALL FUNCTION 'BAPI_XMI_SET_AUDITLEVEL' "Set Audit Level of an XMI Session |
| EXPORTING | ||
| AUDITLEVEL | = lv_auditlevel | |
| IMPORTING | ||
| RETURN | = lv_return | |
| . " BAPI_XMI_SET_AUDITLEVEL | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_XMI_SET_AUDITLEVEL
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 AUDITLEVEL FROM BAPIXMLOGR INTO @DATA(ld_auditlevel). | ||||
Search for further information about these or an SAP related objects