SAP Function BAPI_OUTB_DELIVERY_CREATENOREF - Generates Delivery Without Reference

Parameter Reference Type Length Default Optional Text
DATE_USAGE BAPIDLVCREATEHEADER-DATE_USAGE C 1 X Usage of a date for scheduling the delivery
DEBUG_FLG BAPIDLVCONTROL-DEBUG_FLG C 1 X Debugging Flag
DISTR_CHAN BAPIDLVCREATEHEADER-DISTR_CHAN C 2 Distribution Channel
DIVISION BAPIDLVCREATEHEADER-DIVISION C 2 Division
DLV_TYPE BAPIDLVCREATEHEADER-DLV_TYPE C 4 Delivery Type
NO_DEQUEUE BAPIFLAG-BAPIFLAG C 1 ' ' X Indicator: Do Not Unlock
SALESORG BAPIDLVCREATEHEADER-SALESORG C 4 Sales Organization
SHIP_POINT BAPIDLVCREATEHEADER-SHIP_POINT C 4 Shipping Point
SHIP_TO BAPIDLVCREATEHEADER-SHIP_TO C 10 Goods Recipient

Parameter Reference Type Length Text
DELIVERY BAPISHPDELIVNUMB-DELIV_NUMB C 10 Delivery Number
NUM_DELIVERIES BAPIDLVCREATEHEADER-NUM_DELIVERIES N 4 Number of created documents

Parameter Reference Length Optional Text
CREATED_ITEMS BAPIDLVITEMCREATED 145 X Generated Delivery Items
DATES BAPIDLVDEADLN 34 Delivery Deadlines
DELIVERIES BAPISHPDELIVNUMB 10 X Delivery Number
DLV_ITEMS BAPIDLVNOREFITEM 181 Delivery Item Without Reference
EXTENSION_IN BAPIPAREX 990 X Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT
EXTENSION_OUT BAPIPAREX 990 X Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT
RETURN BAPIRET2 548 X Return Parameter(s)
SERIAL_NUMBERS BAPIDLVSERIALNUMBER 34 X Serial Number

Functionality
This BAPI creates a delivery without a reference. A delivery split canmean that several deliveries are created.

Interface
Parameter ,, Opt. ,, ,, Description
Import ,, ,, ,,
SHIP_POINT ,, ,, ,, Shipping point
DLV_TYPE ,, ,, ,, Delivery type
SALESORG ,, ,, ,, Sales organization
DISTR_CHAN ,, ,, ,, Distribution channel
DIVISION ,, ,, ,, Division
SHIP_TO ,, ,, ,, Ship-to party
DATE_USAGE ,, X ,, ,, Use of dates in DATES
DEBUG_FLG ,, X ,, ,, Forces termination (ALEanalysis)
Export ,, ,, ,,
DELIVERY ,, X ,, ,, First generated delivery
NUM_DELIVERIES ,, X ,, ,, Number of generated deliveries
Tables ,, ,, Direction ,,
DATES ,, ,, Import ,, Delivery date
DLV_ITEMS ,, ,, Import ,, Delivery items to be createdwithout reference
SERIAL_NUMBERS ,, X ,, Import ,, Serial numbers
EXTENSION_IN ,, X ,, Import ,, Additional input data
DELIVERIES ,, X ,, Export ,, Generated deliveries
CREATED_ITEMS ,, X ,, Export ,, Generated delivery items
EXTENSION_OUT ,, X ,, Export ,, Additional output data
RETURN ,, X ,, Export ,, Error log
Opt.: Optional
Direction: Shows the direction used for table parameters.
Caution:
The exported table parameters are initialized before processing. Thisdeletes any data that was in these parameters before the BAPI wascalled.

Imported parameters (selection)
Use of dates (DATE_USAGE)
DATE_USAGE decides which dates from parameter DATES are copied to thedelivery.

  • DATE_USAGE = '1' Material availability date

  • DATE_USAGE = '2' Delivery date

  • DATE_USAGE = '0' (or no entry for DATE_USAGE) Planned goods issue date

    • See also the documentation for parameter DATE_USAGE.
    DEBUG_FLG
    For internal use only. The DEBUG_FLG can be used in ALE inboundprocessing to force a termination, thereby making the analysis of theprocess easier.
    Delivery dates (DATES)
    The following dates can be entered as a time stamp in this tableparameter:
    • Delivery date

    • Planned goods issue date

    • Loading date

    • Transportation planning date

    • Material availability date

      • See also the documentation for parameters DATE_USAGE and DATES.
      Delivery items to be created (DLV_ITEMS)
      Here, the delivery items to be created are specified. The delivery itemnumber cannot be specified. For more detailed information about optionaland required fields, see the documentation for this parameter.
      External delivery number (DLV_ITEMS-DELIV_NUMB)
      A delivery number from the external number range interval can bespecified.
      Serial numbers (SERIAL_NUMBERS)
      In parameter SERIAL_NUMBERS, serial numbers can be assigned to thedelivery items that supply the specified order items.
      Additional import data (EXTENSION_IN)
      In Parameter EXTENSION_IN, additional data can be transferred. For moreinformation, see the documentation for BAdI BADI_DLV_CREATE_NOREF_EXTIN.

      Exported parameters
      Delivery number (DELIVERY)
      Generated delivery (key field in BOR object type LIKP). In case of adelivery split, this is the first generated delivery.
      Number of generated deliveries (NUM_DELIVERIES)
      In case of a delivery split, more than one delivery may be generated.
      Generated deliveries (DELIVERIES)
      List of all generated deliveries (including DELIVERY).
      Generated delivery items (CREATED_ITEMS)
      List of all generated delivery items.
      Additional export data (EXTENSION_OUT)
      In case of a synchronous call, additional data can be returned to thecaller after delivery creation, in parameter EXTENSION_OUT. See thedocumentation for BAdI BADI_DLV_CREATE_EXTOUT.
      Error log (RETURN)
      Parameter RETURN contains the error log. In the same way as intransaction VL10, deliveries may be created even if there were errormessages during processing. Since an asynchronous caller of the BAPI(ALE) only learns of the success of processing via the RETURN parameter,error messages are converted to warning messages if at least onedelivery could be created. If a delivery is created successfully withconverted error messages, message VLBAPI061 (see below) is output.
      In addition, RETURN contains the following important messages:
      Message ,, Description
      BAPI000 ,, A delivery could be created
      BAPI001 ,, A delivery could not be created
      VLBAPI061 ,, Delivery created with errors (see warning messages)
      VL311 ,, Delivery has been saved
      Thus, in case of an asynchronous call, the VL311 messages tell you whichdeliveries could be created.

      Transactional Behavior

      • No COMMIT WORK.

      • ROLLBACK WORK, if no delivery could be created.

        • Notes

        • This BAPI is not optimized for the creation of large numbers of
          • invoices.
          • The BAPI cannot be called multiple times in one logical unit of work
            • (LUW). After a successful call, a COMMIT WORK is required of the callerbefore this BAPI or another BAPI of function group V50I can be called.
            • The BAPI cannot specify delivery item numbers.

              • Further information

              • Documentation for the parameters

              • Documentation for the BAdIs:

                • BADI_DLV_CREATE_NOREF_EXTIN
                BADI_DLV_CREATE_EXTOUT.

                Description
                Delivery number.
                If more than one delivery is created due to a delivery split, the firstdelivery number is returned.

                Description
                Number of deliveries generated.

                Value range
                0, 1: ,, No deliveries generated, one delivery generated
                > 1: ,, More than one delivery generated due to delivery split

                Description
                Use of a date for scheduling the delivery.

                Value range
                Parameter DATE_USAGE can have the following values:
                Value ,, Description
                '0' ,, Copy all dates from parameter DATES
                '1' ,, Dates are determined from the planned material availabilitydate in parameter DATES
                '2' ,, Dates are determined from the planned delivery date inparameter DATES.

                Default
                '0'

                Description
                The value 'X' forces processing to terminate for analysis purposes,particularly for ALE inbound processing.

                Description
                Distribution channel

                Description
                Division

                Description
                Delivery type

                Description
                Sales organization

                Description
                Shipping point

                Description
                Goods recipient

                Description
                CREATED_ITEMS contains all the generated delivery items.

                Description
                You can use parameter DATES to specify delivery dates or how they arecalculated.
                Component ,, Description
                DELIV_NUMB ,, Not used
                TIMETYPE ,, Logical time (see below)
                TIMESTAMP_UTC ,, UTC time stamp in short form (YYYYMMDDhhmmss)
                TIMEZONE ,, Time zone
                The following date categories TIMETYPE (logical events according totable TTSEGTIME) can be used:
                Date category ,, TIMETYPE
                Delivery date ,, WSHDRLFDAT
                Planned goods issue date ,, WSHDRWADAT
                Loading date ,, WSHDRLDDAT
                Transportation planning date ,, WSHDRTDDAT
                Material availability date ,, WSHDRMBDAT
                For historical reasons, internal format (TTSEGTIME-TIME) is used. Usethis format in programs that fill the parameter DATES.
                Caution:
                When entering a date category on a screen (for example, parameter entryin test mode for transaction SE37), external format must be used, due tothe conversion exits. You will find this in the following tables:
                TIMETYPE ,, Entry
                WSHDRLFDAT ,, 'WS DELIVERY LIKP'
                WSHDRWADAT ,, 'WS GOODS ISSUE LIKP'
                WSHDRLDDAT ,, 'WS LOADING LIKP'
                WSHDRTDDAT ,, 'WS TRANSP DISP LIKP'
                WSHDRMBDAT ,, 'WS MATERIAL AV. LIKP'

                Use
                Depending on parameter DATE_USAGE, the following dates must betransferred:
                DATE_USAGE ,, Required Date
                initial or '0' ,, Planned goods issue date (or specification of alldates)
                '1' ,, Material availability date
                '2' ,, Delivery date
                The dates are to be specified as time stamps with the above datecategory and time zone. The field for the delivery number is not used.
                If the time zone is not specified, the UTC time stamp cannot be converte
                d to local time.

                Notes
                DATE_USAGE = '0':
                If no value is specified for DATE_USAGE or if DATE_USAGE has the value'0', the planned goods issue date is required. Other dates may also betransferred, although all of the following dates must betransferred:

                • Delivery date

                • Planned goods issue date

                • Loading date

                • Transportation planning date

                • Material availability date

                  • If a date is missing, only the planned goods issue date is copied forcalculation of dates.
                  DATE_USAGE = '1' or '2':
                  Dates other than the dates shown above as required are ignored.

                  Description
                  DELIVERIES contains all the generated delivery numbers.

                  Description
                  The parameter DLV_ITEMS specifies the delivery items to be created.
                  Component ,, Optional ,, Required for ,, Description
                  REF_ITEM ,, X ,, Serial numbers ,, Sequence number
                  MATERIAL ,,for text item ,, ,, Material
                  ITEM_CATEG ,, X ,, ,, Item category
                  DLV_QTY ,, X ,, ,, Delivery quantity
                  SALES_UNIT ,, X ,, Delivery qty ,, Sales unit
                  SALES_UNIT_ISO ,, X ,, Delivery qty ,, Sales unit (ISO)
                  PLANT ,, X ,, Storage loc. ,, Plant
                  STGE_LOC ,, X ,, ,, Storage location
                  SHORT_TEXT ,, X ,, Text item ,, Articledescription
                  DELIV_NUMB ,, X ,, ,, External numberassignment

                  Notes

                  • The delivery item number cannot be specified.

                  • The delivery number can only be assigned from the external number range
                    • interval by using DELIV_NUMB.
                    • For the delivery quantity, the sales unit must be specified either in
                      • SALES_UNIT or as an ISO code in SALES_UNIT_ISO.

                      Description
                      In parameter EXTENSION_IN, you can transfer additional data.
                      This data can be processed with the following BAdI:
                      Enhancement spot: ,, ES_SAPVL50I_BADI
                      BADI definition: ,, BADI_DLV_CREATE_NOREF_EXTIN
                      Method: ,, ADDITIONAL_INPUT

                      Description
                      In parameter EXTENSION_OUT, you can return additional data to asynchronous caller.
                      The following BAdI is available for doing this:
                      Enhancement spot: ,, ES_SAPVL50I_BADI
                      BADI definition: ,, BADI_DLV_CREATE_EXTOUT
                      Method: ,, ADDITIONAL_OUTPUT

                      Description
                      Contains the messages that occurred during processing.
                      Delivery created
                      If a delivery could be created, RETURN contains message BAPI 000:
                      "OutboundDelivery has been created. Externalreference: ".
                      No delivery created
                      If no delivery could be created, RETURN contains message BAPI 001:

                      "No instance of object type OutboundDelivery has been created.External reference: ".
                      is only filled if a delivery numberwas transferred by the caller. In this case, an
                      d are the same. Otherwise, is initial.
                      Delivery created with errors
                      In case of success (BAPI000), any error messages that occurred areoutput as warning messages. This is necessary to ensure that the IDocstatus is set to "successful" (53) by ALE in case of an asynchronous
                      If error messages have been converted to warning messages in this way,RETURN contains message VLBAPI 061:
                      "Delivery created with errors (see warning message
                      s)".

                      Description
                      You can use the parameter SERIAL_NUMBERS to assign serial numbers to thedelivery items.
                      The REF_ITEM in DLV_ITEMS and SERIAL_NUMBERS forms the reference betweenserial number and delivery item. The number of the generated deliveryitem may be different from REF_ITEM.