SAP ISU_DB_BACKLOGS_SINGLE Function Module for INTERNAL: Single Access to Table ISU_BACKLOGS









ISU_DB_BACKLOGS_SINGLE is a standard isu db backlogs single SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for INTERNAL: Single Access to Table ISU_BACKLOGS 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 isu db backlogs single FM, simply by entering the name ISU_DB_BACKLOGS_SINGLE into the relevant SAP transaction such as SE37 or SE38.

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



Function ISU_DB_BACKLOGS_SINGLE 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 'ISU_DB_BACKLOGS_SINGLE'"INTERNAL: Single Access to Table ISU_BACKLOGS
EXPORTING
X_ACTCAT = "Activity
X_SETNO = "Number of processed backlog set

IMPORTING
Y_BACKLOGS = "Definition of backlog sets

EXCEPTIONS
NOT_FOUND = 1 SYSTEM_ERROR = 2
.



IMPORTING Parameters details for ISU_DB_BACKLOGS_SINGLE

X_ACTCAT - Activity

Data type:
Optional: No
Call by Reference: Yes

X_SETNO - Number of processed backlog set

Data type: ISU_BACKLOGS-SETNO
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for ISU_DB_BACKLOGS_SINGLE

Y_BACKLOGS - Definition of backlog sets

Data type: ISU_BACKLOGS
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NOT_FOUND - Object Not Found

Data type:
Optional: No
Call by Reference: Yes

SYSTEM_ERROR - Other Error

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISU_DB_BACKLOGS_SINGLE 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_x_actcat  TYPE STRING, "   
lv_not_found  TYPE STRING, "   
lv_y_backlogs  TYPE ISU_BACKLOGS, "   
lv_x_setno  TYPE ISU_BACKLOGS-SETNO, "   
lv_system_error  TYPE ISU_BACKLOGS. "   

  CALL FUNCTION 'ISU_DB_BACKLOGS_SINGLE'  "INTERNAL: Single Access to Table ISU_BACKLOGS
    EXPORTING
         X_ACTCAT = lv_x_actcat
         X_SETNO = lv_x_setno
    IMPORTING
         Y_BACKLOGS = lv_y_backlogs
    EXCEPTIONS
        NOT_FOUND = 1
        SYSTEM_ERROR = 2
. " ISU_DB_BACKLOGS_SINGLE




ABAP code using 7.40 inline data declarations to call FM ISU_DB_BACKLOGS_SINGLE

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 SETNO FROM ISU_BACKLOGS INTO @DATA(ld_x_setno).
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!