SAP ISB_MESSAGE_AND_DETAIL Function Module for IS-B: Nachrichten ausgeben, Detailprotokoll steuern
ISB_MESSAGE_AND_DETAIL is a standard isb message and detail SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-B: Nachrichten ausgeben, Detailprotokoll steuern 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 message and detail FM, simply by entering the name ISB_MESSAGE_AND_DETAIL into the relevant SAP transaction such as SE37 or SE38.
Function Group: JBT4
Program Name: SAPLJBT4
Main Program: SAPLJBT4
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISB_MESSAGE_AND_DETAIL 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_MESSAGE_AND_DETAIL'"IS-B: Nachrichten ausgeben, Detailprotokoll steuern.
EXPORTING
* OBJNR = "
* NO_DETAIL = ' ' "
* DEBUGGING = "
* RBESTO = "
MSGNR = "
* AG = 'J2' "
* SEVERITY = 'E' "
* VAR1 = "
* VAR2 = "
* VAR3 = "
* VAR4 = "
TABLES
PAR_SPROT_K = "
EXCEPTIONS
IMPORT_ERROR = 1
IMPORTING Parameters details for ISB_MESSAGE_AND_DETAIL
OBJNR -
Data type: JBIXGSC-OBJNROptional: Yes
Call by Reference: No ( called with pass by value option)
NO_DETAIL -
Data type: JBIXGSC-SKALKZDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
DEBUGGING -
Data type: SPROT_K-NVERFAOptional: Yes
Call by Reference: No ( called with pass by value option)
RBESTO -
Data type: JBDBSTD-RBESTOOptional: Yes
Call by Reference: No ( called with pass by value option)
MSGNR -
Data type: SPROT_K-MSGNROptional: No
Call by Reference: No ( called with pass by value option)
AG -
Data type: SPROT_K-AGDefault: 'J2'
Optional: Yes
Call by Reference: No ( called with pass by value option)
SEVERITY -
Data type: SPROT_K-SEVERITYDefault: 'E'
Optional: Yes
Call by Reference: No ( called with pass by value option)
VAR1 -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
VAR2 -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
VAR3 -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
VAR4 -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISB_MESSAGE_AND_DETAIL
PAR_SPROT_K -
Data type: SPROT_KOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
IMPORT_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISB_MESSAGE_AND_DETAIL 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_objnr | TYPE JBIXGSC-OBJNR, " | |||
| lt_par_sprot_k | TYPE STANDARD TABLE OF SPROT_K, " | |||
| lv_import_error | TYPE SPROT_K, " | |||
| lv_no_detail | TYPE JBIXGSC-SKALKZ, " ' ' | |||
| lv_debugging | TYPE SPROT_K-NVERFA, " | |||
| lv_rbesto | TYPE JBDBSTD-RBESTO, " | |||
| lv_msgnr | TYPE SPROT_K-MSGNR, " | |||
| lv_ag | TYPE SPROT_K-AG, " 'J2' | |||
| lv_severity | TYPE SPROT_K-SEVERITY, " 'E' | |||
| lv_var1 | TYPE SPROT_K, " | |||
| lv_var2 | TYPE SPROT_K, " | |||
| lv_var3 | TYPE SPROT_K, " | |||
| lv_var4 | TYPE SPROT_K. " |
|   CALL FUNCTION 'ISB_MESSAGE_AND_DETAIL' "IS-B: Nachrichten ausgeben, Detailprotokoll steuern |
| EXPORTING | ||
| OBJNR | = lv_objnr | |
| NO_DETAIL | = lv_no_detail | |
| DEBUGGING | = lv_debugging | |
| RBESTO | = lv_rbesto | |
| MSGNR | = lv_msgnr | |
| AG | = lv_ag | |
| SEVERITY | = lv_severity | |
| VAR1 | = lv_var1 | |
| VAR2 | = lv_var2 | |
| VAR3 | = lv_var3 | |
| VAR4 | = lv_var4 | |
| TABLES | ||
| PAR_SPROT_K | = lt_par_sprot_k | |
| EXCEPTIONS | ||
| IMPORT_ERROR = 1 | ||
| . " ISB_MESSAGE_AND_DETAIL | ||
ABAP code using 7.40 inline data declarations to call FM ISB_MESSAGE_AND_DETAIL
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 OBJNR FROM JBIXGSC INTO @DATA(ld_objnr). | ||||
| "SELECT single SKALKZ FROM JBIXGSC INTO @DATA(ld_no_detail). | ||||
| DATA(ld_no_detail) | = ' '. | |||
| "SELECT single NVERFA FROM SPROT_K INTO @DATA(ld_debugging). | ||||
| "SELECT single RBESTO FROM JBDBSTD INTO @DATA(ld_rbesto). | ||||
| "SELECT single MSGNR FROM SPROT_K INTO @DATA(ld_msgnr). | ||||
| "SELECT single AG FROM SPROT_K INTO @DATA(ld_ag). | ||||
| DATA(ld_ag) | = 'J2'. | |||
| "SELECT single SEVERITY FROM SPROT_K INTO @DATA(ld_severity). | ||||
| DATA(ld_severity) | = 'E'. | |||
Search for further information about these or an SAP related objects