ISU_DB_INSTSET_INSTCAUSE_JOIN SAP Function module - INTERNAL: Mass Access via Join to INSTSET and INSTCAUSE

ISU_DB_INSTSET_INSTCAUSE_JOIN is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name ISU_DB_INSTSET_INSTCAUSE_JOIN into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: BREDBSELECT
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM ISU_DB_INSTSET_INSTCAUSE_JOIN - ISU DB INSTSET INSTCAUSE JOIN

CALL FUNCTION 'ISU_DB_INSTSET_INSTCAUSE_JOIN' "INTERNAL: Mass Access via Join to INSTSET and INSTCAUSE
  EXPORTING
    x_setno =                   " setno         Number of processed backlog set
    x_msgid =                   " msgid         Message identification
    x_msgno =                   " msgno         System message number
    x_cause =                   " causes        Error Causes for Extracts from Backlog Sets
  IMPORTING
    y_i_instset_info =          " iinstsetcauses  Table of Field Strings with  [ INSTSET ,  INSTCAUSE ]
  EXCEPTIONS
    NOT_FOUND = 1               "               Object Not Found
    SYSTEM_ERROR = 2            "               Other Error
    .  "  ISU_DB_INSTSET_INSTCAUSE_JOIN

ABAP code example for Function Module ISU_DB_INSTSET_INSTCAUSE_JOIN

The ABAP code below is a full code listing to execute function module ISU_DB_INSTSET_INSTCAUSE_JOIN including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_y_i_instset_info  
 
 TYPE IINSTSETCAUSES
.


DATA(ld_x_setno) = 'Check type of data required'.

DATA(ld_x_msgid) = 'Check type of data required'.

DATA(ld_x_msgno) = 'Check type of data required'.

DATA(ld_x_cause) = 'Check type of data required'.
.

CALL FUNCTION 'ISU_DB_INSTSET_INSTCAUSE_JOIN'
  EXPORTING
    x_setno =                    ld_x_setno
    x_msgid =                    ld_x_msgid
    x_msgno =                    ld_x_msgno
    x_cause =                    ld_x_cause
  IMPORTING
    y_i_instset_info =           ld_y_i_instset_info
  EXCEPTIONS
    NOT_FOUND =                  1
    SYSTEM_ERROR =               2
    .  "  ISU_DB_INSTSET_INSTCAUSE_JOIN

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_y_i_instset_info
 
 TYPE IINSTSETCAUSES ,
ld_x_setno
 
 TYPE SETNO ,
ld_x_msgid
 
 TYPE MSGID ,
ld_x_msgno
 
 TYPE MSGNO ,
ld_x_cause
 
 TYPE CAUSES .


ld_x_setno = 'Check type of data required'.
ld_x_msgid = 'Check type of data required'.
ld_x_msgno = 'Check type of data required'.
ld_x_cause = 'Check type of data required'.