SAP SUBST_FRAGMENT_DELIVERY_INFO Function Module for

Search SAP Function Modules

SUBST_FRAGMENT_DELIVERY_INFO is a standard subst fragment delivery info SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 fragment delivery info FM, simply by entering the name SUBST_FRAGMENT_DELIVERY_INFO into the relevant SAP transaction such as SE37 or SE38.

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

Function SUBST_FRAGMENT_DELIVERY_INFO 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_FRAGMENT_DELIVERY_INFO'"
  EXPORTING
   IV_FRAGID =  "Program ID in requests and tasks
   IV_FRAGMENT =  "Object Type
   IV_FRAGNAME =  "Object Name in Object List

 IMPORTING
   EV_IS_DELIVERED =  "Is delivered
   EV_IS_SAP_OBJECT =  "
   EV_TO_BE_DELETED =  "to be deleted
   EV_MODEFLAG =  "Results of Distribution Run (Table DDXTT)

EXCEPTIONS
   NO_UPGRADE_ACTIVE = 1    NOT_A_FRAGMENT = 2 

.

IMPORTING Parameters details for SUBST_FRAGMENT_DELIVERY_INFO

IV_FRAGID - Program ID in requests and tasks

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

IV_FRAGMENT - Object Type

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

IV_FRAGNAME - Object Name in Object List

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

EXPORTING Parameters details for SUBST_FRAGMENT_DELIVERY_INFO

EV_IS_DELIVERED - Is delivered

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

EV_IS_SAP_OBJECT -

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

EV_TO_BE_DELETED - to be deleted

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

EV_MODEFLAG - Results of Distribution Run (Table DDXTT)

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

EXCEPTIONS details

NO_UPGRADE_ACTIVE - No active upgrade

Data type:
Optional: No
Call by Reference: Yes

NOT_A_FRAGMENT -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SUBST_FRAGMENT_DELIVERY_INFO 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.

ABAP code using 7.40 inline data declarations to call FM SUBST_FRAGMENT_DELIVERY_INFO

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.

Search for further information about these or an SAP related objects