SAP SD_DELIVERY_SUBSEQUENT_ALLOWED Function Module for









SD_DELIVERY_SUBSEQUENT_ALLOWED is a standard sd delivery subsequent allowed 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 sd delivery subsequent allowed FM, simply by entering the name SD_DELIVERY_SUBSEQUENT_ALLOWED into the relevant SAP transaction such as SE37 or SE38.

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



Function SD_DELIVERY_SUBSEQUENT_ALLOWED 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 'SD_DELIVERY_SUBSEQUENT_ALLOWED'"
  EXPORTING
*  BLIKP = ' ' "Delivery header
*  BLIPS = ' ' "Delivery item
*  BTVLK = ' ' "Delivery type
*  BTVLP = ' ' "Delivery item category
*  BVBUK = ' ' "Delivery header status
*  BVBUP = ' ' "Delivery item status
   FOFUN =  "Follow-on function (from table TVFO)
*  BVBPA = ' ' "
*  BCALLER =  "

EXCEPTIONS
   ERROR = 1    WARNING = 2
.



IMPORTING Parameters details for SD_DELIVERY_SUBSEQUENT_ALLOWED

BLIKP - Delivery header

Data type: LIKP
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

BLIPS - Delivery item

Data type: LIPSVB
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

BTVLK - Delivery type

Data type: TVLK
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

BTVLP - Delivery item category

Data type: TVLP
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

BVBUK - Delivery header status

Data type: VBUKVB
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

BVBUP - Delivery item status

Data type: VBUPVB
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

FOFUN - Follow-on function (from table TVFO)

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

BVBPA -

Data type: VBPA
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

BCALLER -

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

EXCEPTIONS details

ERROR - Follow-on function not allowed

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

WARNING - Follow-on function allowed, but W-message

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

Copy and paste ABAP code example for SD_DELIVERY_SUBSEQUENT_ALLOWED 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_blikp  TYPE LIKP, "   SPACE
lv_error  TYPE LIKP, "   
lv_blips  TYPE LIPSVB, "   SPACE
lv_warning  TYPE LIPSVB, "   
lv_btvlk  TYPE TVLK, "   SPACE
lv_btvlp  TYPE TVLP, "   SPACE
lv_bvbuk  TYPE VBUKVB, "   SPACE
lv_bvbup  TYPE VBUPVB, "   SPACE
lv_fofun  TYPE TVFO-FOFUN, "   
lv_bvbpa  TYPE VBPA, "   SPACE
lv_bcaller  TYPE VBPA. "   

  CALL FUNCTION 'SD_DELIVERY_SUBSEQUENT_ALLOWED'  "
    EXPORTING
         BLIKP = lv_blikp
         BLIPS = lv_blips
         BTVLK = lv_btvlk
         BTVLP = lv_btvlp
         BVBUK = lv_bvbuk
         BVBUP = lv_bvbup
         FOFUN = lv_fofun
         BVBPA = lv_bvbpa
         BCALLER = lv_bcaller
    EXCEPTIONS
        ERROR = 1
        WARNING = 2
. " SD_DELIVERY_SUBSEQUENT_ALLOWED




ABAP code using 7.40 inline data declarations to call FM SD_DELIVERY_SUBSEQUENT_ALLOWED

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.

DATA(ld_blikp) = ' '.
 
 
DATA(ld_blips) = ' '.
 
 
DATA(ld_btvlk) = ' '.
 
DATA(ld_btvlp) = ' '.
 
DATA(ld_bvbuk) = ' '.
 
DATA(ld_bvbup) = ' '.
 
"SELECT single FOFUN FROM TVFO INTO @DATA(ld_fofun).
 
DATA(ld_bvbpa) = ' '.
 
 


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!