SAP QIER_LOG_EXCEPTION Function Module for NOTRANSL: Exception in Fehlerprotokoll und Application Log schreiben (mit

Search SAP Function Modules

QIER_LOG_EXCEPTION is a standard qier log exception SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Exception in Fehlerprotokoll und Application Log schreiben (mit 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 qier log exception FM, simply by entering the name QIER_LOG_EXCEPTION into the relevant SAP transaction such as SE37 or SE38.

Function Group: QIER
Program Name: SAPLQIER
Main Program:
Appliation area: Q
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function QIER_LOG_EXCEPTION 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 'QIER_LOG_EXCEPTION'"NOTRANSL: Exception in Fehlerprotokoll und Application Log schreiben (mit
  EXPORTING
   IM_EXCEPTION =  "Name of function module exception
*  IM_MSGTY = 'E' "Message Type
*  IM_MSGID = 'QI' "Message Class
   IM_MSGNO =  "Message Number
*  IM_MSGV1 =  "
*  IM_MSGV2 =  "
*  IM_MSGV3 =  "
*  IM_MSGV4 =  "

.

IMPORTING Parameters details for QIER_LOG_EXCEPTION

IM_EXCEPTION - Name of function module exception

Data type: RS38L-EXCEPTION
Optional: No
Call by Reference: Yes

IM_MSGTY - Message Type

Data type: BALMI-MSGTY
Default: 'E'
Optional: Yes
Call by Reference: Yes

IM_MSGID - Message Class

Data type: BALMI-MSGID
Default: 'QI'
Optional: Yes
Call by Reference: Yes

IM_MSGNO - Message Number

Data type: BALMI-MSGNO
Optional: No
Call by Reference: Yes

IM_MSGV1 -

Data type:
Optional: Yes
Call by Reference: Yes

IM_MSGV2 -

Data type:
Optional: Yes
Call by Reference: Yes

IM_MSGV3 -

Data type:
Optional: Yes
Call by Reference: Yes

IM_MSGV4 -

Data type:
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for QIER_LOG_EXCEPTION 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 QIER_LOG_EXCEPTION

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