SAP SUBST_LIST_DELIVERY_COLLISIONS Function Module for Determines Collisions Between a Transport Object and SAP Delivery









SUBST_LIST_DELIVERY_COLLISIONS is a standard subst list delivery collisions SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determines Collisions Between a Transport Object and SAP Delivery 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 subst list delivery collisions FM, simply by entering the name SUBST_LIST_DELIVERY_COLLISIONS into the relevant SAP transaction such as SE37 or SE38.

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



Function SUBST_LIST_DELIVERY_COLLISIONS 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 'SUBST_LIST_DELIVERY_COLLISIONS'"Determines Collisions Between a Transport Object and SAP Delivery
EXPORTING
IV_FRAGID = "
IV_FRAGMENT = "
IV_FRAGNAME = "
IV_CHECKMAP = "
IV_DELIVIN = "
IV_STARTREL = "
IV_TARGETREL = "

IMPORTING
EV_COLLIDES = "
EV_MODEFLAG = "

TABLES
* TT_TODIR = "

EXCEPTIONS
NO_DELIVERY_FOUND = 1 OBJECT_OUT_OF_FOCUS = 2 CALCMODE_FAILED = 3
.



IMPORTING Parameters details for SUBST_LIST_DELIVERY_COLLISIONS

IV_FRAGID -

Data type: TODIR-FRAGID
Optional: No
Call by Reference: No ( called with pass by value option)

IV_FRAGMENT -

Data type: TODIR-FRAGMENT
Optional: No
Call by Reference: No ( called with pass by value option)

IV_FRAGNAME -

Data type: TODIR-FRAGNAME
Optional: No
Call by Reference: No ( called with pass by value option)

IV_CHECKMAP -

Data type: TODIR-RELMAP
Optional: No
Call by Reference: No ( called with pass by value option)

IV_DELIVIN -

Data type: RELEASEMAP-MAPNAME
Optional: No
Call by Reference: No ( called with pass by value option)

IV_STARTREL -

Data type: UVERS-OLDRELEASE
Optional: No
Call by Reference: No ( called with pass by value option)

IV_TARGETREL -

Data type: UVERS-NEWRELEASE
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for SUBST_LIST_DELIVERY_COLLISIONS

EV_COLLIDES -

Data type: GSUGI_PA-W_ISTATUS
Optional: No
Call by Reference: No ( called with pass by value option)

EV_MODEFLAG -

Data type: TODIR-MODSTATUS
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for SUBST_LIST_DELIVERY_COLLISIONS

TT_TODIR -

Data type: TODIR
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

NO_DELIVERY_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

OBJECT_OUT_OF_FOCUS -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

CALCMODE_FAILED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for SUBST_LIST_DELIVERY_COLLISIONS 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_tt_todir  TYPE STANDARD TABLE OF TODIR, "   
lv_iv_fragid  TYPE TODIR-FRAGID, "   
lv_ev_collides  TYPE GSUGI_PA-W_ISTATUS, "   
lv_no_delivery_found  TYPE GSUGI_PA, "   
lv_ev_modeflag  TYPE TODIR-MODSTATUS, "   
lv_iv_fragment  TYPE TODIR-FRAGMENT, "   
lv_object_out_of_focus  TYPE TODIR, "   
lv_iv_fragname  TYPE TODIR-FRAGNAME, "   
lv_calcmode_failed  TYPE TODIR, "   
lv_iv_checkmap  TYPE TODIR-RELMAP, "   
lv_iv_delivin  TYPE RELEASEMAP-MAPNAME, "   
lv_iv_startrel  TYPE UVERS-OLDRELEASE, "   
lv_iv_targetrel  TYPE UVERS-NEWRELEASE. "   

  CALL FUNCTION 'SUBST_LIST_DELIVERY_COLLISIONS'  "Determines Collisions Between a Transport Object and SAP Delivery
    EXPORTING
         IV_FRAGID = lv_iv_fragid
         IV_FRAGMENT = lv_iv_fragment
         IV_FRAGNAME = lv_iv_fragname
         IV_CHECKMAP = lv_iv_checkmap
         IV_DELIVIN = lv_iv_delivin
         IV_STARTREL = lv_iv_startrel
         IV_TARGETREL = lv_iv_targetrel
    IMPORTING
         EV_COLLIDES = lv_ev_collides
         EV_MODEFLAG = lv_ev_modeflag
    TABLES
         TT_TODIR = lt_tt_todir
    EXCEPTIONS
        NO_DELIVERY_FOUND = 1
        OBJECT_OUT_OF_FOCUS = 2
        CALCMODE_FAILED = 3
. " SUBST_LIST_DELIVERY_COLLISIONS




ABAP code using 7.40 inline data declarations to call FM SUBST_LIST_DELIVERY_COLLISIONS

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 FRAGID FROM TODIR INTO @DATA(ld_iv_fragid).
 
"SELECT single W_ISTATUS FROM GSUGI_PA INTO @DATA(ld_ev_collides).
 
 
"SELECT single MODSTATUS FROM TODIR INTO @DATA(ld_ev_modeflag).
 
"SELECT single FRAGMENT FROM TODIR INTO @DATA(ld_iv_fragment).
 
 
"SELECT single FRAGNAME FROM TODIR INTO @DATA(ld_iv_fragname).
 
 
"SELECT single RELMAP FROM TODIR INTO @DATA(ld_iv_checkmap).
 
"SELECT single MAPNAME FROM RELEASEMAP INTO @DATA(ld_iv_delivin).
 
"SELECT single OLDRELEASE FROM UVERS INTO @DATA(ld_iv_startrel).
 
"SELECT single NEWRELEASE FROM UVERS INTO @DATA(ld_iv_targetrel).
 


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!