SAP ISB_OR_MSG_LINE Function Module for Protokollierung Schreiben Message in Protokoll mit Parametern
ISB_OR_MSG_LINE is a standard isb or msg line SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Protokollierung Schreiben Message in Protokoll mit Parametern 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 isb or msg line FM, simply by entering the name ISB_OR_MSG_LINE into the relevant SAP transaction such as SE37 or SE38.
Function Group: JBO3
Program Name: SAPLJBO3
Main Program: SAPLJBO3
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISB_OR_MSG_LINE 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 'ISB_OR_MSG_LINE'"Protokollierung Schreiben Message in Protokoll mit Parametern.
EXPORTING
* I_OBJECT_ID = "
* I_VAR3 = "
* I_VAR4 = "
* I_MSG_LEVEL = "
* I_PROTOCOL_LEVEL = 1 "
I_SEVERITY = "
* I_AG = "
I_MSGNR = "
* I_NEWOBJ = "
* I_VAR1 = "
* I_VAR2 = "
TABLES
ERROR_ITAB = "
IMPORTING Parameters details for ISB_OR_MSG_LINE
I_OBJECT_ID -
Data type: TVS_SFGDT_TYP-KOPF-OBJNROptional: Yes
Call by Reference: Yes
I_VAR3 -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
I_VAR4 -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MSG_LEVEL -
Data type: SPROT_U-LEVELOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PROTOCOL_LEVEL -
Data type:Default: 1
Optional: Yes
Call by Reference: Yes
I_SEVERITY -
Data type: SPROT_U-SEVERITYOptional: No
Call by Reference: No ( called with pass by value option)
I_AG -
Data type: SPROT_U-AGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_MSGNR -
Data type: SPROT_U-MSGNROptional: No
Call by Reference: No ( called with pass by value option)
I_NEWOBJ -
Data type: SPROT_U-NEWOBJOptional: Yes
Call by Reference: No ( called with pass by value option)
I_VAR1 -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
I_VAR2 -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISB_OR_MSG_LINE
ERROR_ITAB -
Data type: BAPIERROptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISB_OR_MSG_LINE 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: | ||||
| lt_error_itab | TYPE STANDARD TABLE OF BAPIERR, " | |||
| lv_i_object_id | TYPE TVS_SFGDT_TYP-KOPF-OBJNR, " | |||
| lv_i_var3 | TYPE TVS_SFGDT_TYP, " | |||
| lv_i_var4 | TYPE TVS_SFGDT_TYP, " | |||
| lv_i_msg_level | TYPE SPROT_U-LEVEL, " | |||
| lv_i_protocol_level | TYPE SPROT_U, " 1 | |||
| lv_i_severity | TYPE SPROT_U-SEVERITY, " | |||
| lv_i_ag | TYPE SPROT_U-AG, " | |||
| lv_i_msgnr | TYPE SPROT_U-MSGNR, " | |||
| lv_i_newobj | TYPE SPROT_U-NEWOBJ, " | |||
| lv_i_var1 | TYPE SPROT_U, " | |||
| lv_i_var2 | TYPE SPROT_U. " |
|   CALL FUNCTION 'ISB_OR_MSG_LINE' "Protokollierung Schreiben Message in Protokoll mit Parametern |
| EXPORTING | ||
| I_OBJECT_ID | = lv_i_object_id | |
| I_VAR3 | = lv_i_var3 | |
| I_VAR4 | = lv_i_var4 | |
| I_MSG_LEVEL | = lv_i_msg_level | |
| I_PROTOCOL_LEVEL | = lv_i_protocol_level | |
| I_SEVERITY | = lv_i_severity | |
| I_AG | = lv_i_ag | |
| I_MSGNR | = lv_i_msgnr | |
| I_NEWOBJ | = lv_i_newobj | |
| I_VAR1 | = lv_i_var1 | |
| I_VAR2 | = lv_i_var2 | |
| TABLES | ||
| ERROR_ITAB | = lt_error_itab | |
| . " ISB_OR_MSG_LINE | ||
ABAP code using 7.40 inline data declarations to call FM ISB_OR_MSG_LINE
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 KOPF FROM TVS_SFGDT_TYP INTO @DATA(ld_i_object_id). | ||||
| "SELECT single LEVEL FROM SPROT_U INTO @DATA(ld_i_msg_level). | ||||
| DATA(ld_i_protocol_level) | = 1. | |||
| "SELECT single SEVERITY FROM SPROT_U INTO @DATA(ld_i_severity). | ||||
| "SELECT single AG FROM SPROT_U INTO @DATA(ld_i_ag). | ||||
| "SELECT single MSGNR FROM SPROT_U INTO @DATA(ld_i_msgnr). | ||||
| "SELECT single NEWOBJ FROM SPROT_U INTO @DATA(ld_i_newobj). | ||||
Search for further information about these or an SAP related objects