×

[PR]この広告は3ヶ月以上更新がないため表示されています。
ホームページを更新後24時間以内に表示されなくなります。




Sapass

 Simplify SAP R/3 development with Excel VBA/VB RFC  
Home> Bapi>OutboundDelivery



Index

OutboundDelivery

OutboundDelivery


The business object Outbound delivery is a combination of sales
materials which are delivered together to a ship-to party. It forms the basis for processing shipping functions to a shipping point.


Structure
The outbound delivery can include shipping materials and/or services as
well as return deliveries of a material by the customer.
A customer delivery contains several items containing a sales material
(if necessary with the relevant plant batch) and a delivery quantity.


Items can be structured in a hierarchy which makes it possible to
differentiate charges or separate materials in a bill of materials.


A further subdivision of items contains materials to be delivered that are identified individually: serialized material.


Integration
The customer delivery contains materials or services that have been
entered in an order in a sales organization or via several sales areas.
Several business partners other than the ship-to party can be assigned to different partner functions in the customer delivery.


11-Dec-2005


Methods

Available Methods


  • ConfirmDecentral : BAPI for outbound delivery verification from a decentralized system [ BAPI_OUTB_DELIVERY_CONFIRM_DEC ]
  • GetListOutput : Selection of delivery output [ BAPI_LIKP_GET_LIST_MSG ]
  • ProcessOutput : Process delivery output [ BAPI_LIKP_PROCESS_MSG ]
  • ProcessOutputDirect : Process delivery output without list [ BAPI_LIKP_PROCESS_MSG_DIRECT ]
  • SaveReplica : Duplication of deliveries [ BAPI_OUTB_DELIVERY_SAVEREPLICA ]
  • SplitDecentral : BAPI for the subsequent delivery split from a decentralized system [ BAPI_OUTB_DELIVERY_SPLIT_DEC ]

11-Dec-2005


ConfirmDecentral

ConfirmDecentral


You can use this method to report back outbound deliveries from a WM system to an enterprise resource planning (ERP) system.

Example

Which required data do you need for reporting back ?
Two examples of how the BAPI is used are shown below: reporting back
the delivery without (quantity) changes of the item data and reporting back the delivery with changes of the item data.

1. The item data of the delivery is reported back unchanged.

HEADER_DATA Header data of outbound delivery


  • Field DELIV_NUMB Delivery number
  • HEADER_CONTROL Header control data

  • Field DELIV_NUMB Delivery number
  • Field GROSS_WT_FLG Gross weight reporting flag

  • DELIVERY Document number of outbound delivery

  • Field DELIV_NUMB Delivery number
  • 1. The items of the delivery are reported back changed.

    HEADER_DATA Header data of outbound delivery


  • Field DELIV_NUMB Delivery number
  • DELIVERY Document number of outbound delivery

  • Field DELIV_NUMB Delivery number
  • ITEM_DATA Item data


  • Field DELIV_NUMB Delivery number
  • Field DELIV_ITEM Delivery item
  • Field DLV_QTY Delivery quantity in sales unit of measure
    or alternatively

  • Field DLV_QTY_IMUNIT Actual delivery quantity in stockkeeping unit
  • ITEM_CONTROL Item control data

  • Field DELIV_NUMB Delivery number
  • Field DELIV_ITEM Delivery item

  • Field CHG_DELQTY Change delivery quantity
  • Field GROSS_WT_FLG Gross weight reporting flag
  • Material number, plant, quantities in floating values, volumes, weights
    and their units are copied from the delivery, if not specified.

    Error messages are recorded in BAPI return parameter RETURN with the following message types:

    E (ERROR)
    W (WARNING)
    I (INFORMATION)


    Further Information

    If the BAPI is used as an external interface for an external system,the packing hierarchy should be described as usual by using external identification numbers for shipping materials
    (HDL_UNIT_EXID_INTO/HDL_UNIT_EXID). The fields can be found in theHANDLING_UNIT_ITEM segment. The shipping unit must be copied into theHDL_UNIT_EXID_INTO field when the system reports back to packing.

    If batch splits that were created in the ERP are reported back, the

    hierarchy fields HIERARITEM and USEHIERITM must not contain information. If split items were created in the Warehouse ManagementSystem and reported back, these two hierarchy fields must contain information.

    If a non-SAP system was used as a decentralized Warehouse Management
    System, the IDoc structure must be defined carefully when the returnmessage is constructed. It is very important that the segment sequence must not be altered.


    11-Dec-2005


    GetListOutput

    GetListOutput


    This method enables you to select delivery outputs in a central systemfrom a decentralized system. Selection is restricted by deliverynumber, output type and transmission medium. The selected outputs arereturned in a table on the BAPI interface. Error messages are stored in
    the BAPI return parameter RETURN with the following message types:

  • E (ERROR)
  • W (WARNING)
  • I (INFORMATION)
  • You must enter the processing mode. Outputs are controlled inprocessing mode. The status and output send time are determined (the
    various statuses and times are listed as an overview in the note). Manyof the same types of outputs exist (messages which only differ increation date and time). Depending on the mode selection takes place as follows (with relation to the newest output):


    1: First processing
    Outputs with the status 0 and time sent 3 are selected.

    2: Repeat processing
    The newest outputs must have status 1 or 2.

    3: Error processing
    The system checks whether the newest output has status 2. The send time
    has no relevance for first processing or repeat processing as theoutputs have already been processed once. Whether an output may berepeated in this mode at all depends on the output type. You can changethe 'can be changed/repeated manually' setting. (T685B-NBEAR).


    Example

    Unprocessed outputs are to be selected for delivery into a centralsytem. By entering the delivery number in the DELIVERYNUMBER parameterand the processing mode '1' in the BAPISHPOUTPUT-PROCESSING parameter, selection will take place.


    The selected outputs can be processed using the 'OutboundDelivery.ProcessOutput ' method.


    11-Dec-2005


    ProcessOutput

    ProcessOutput


    This method processes outputs for delivery.

    All output key attributes entered via the 'MessageKey' parameter areprocessed by the method. If a processing mode is also entered in the'Processing' parameter, only the outputs which correspond to this processing mode are processed.


    The parameter 'DynamicOutputDevice' also offers dynamic control of the output device.

    Error messages are stored in the BAPI return paramter RETURN with the following message types:

  • E (ERROR)
  • W (WARNING)
  • I (INFORMATION)
  • To sort the outputs according to your preferred criteria, use the methods 'OutboundDelivery.GetListOutput' and
    OutboundDelivery.ProcessOutput'. If you do not implement sorting, the outputs will be sorted by key attribute.

    Notes

    You can select outputs using the method 'OutboundDelivery.GetListOutput'.


    11-Dec-2005


    ProcessOutputDirect

    ProcessOutputDirect


    The method includes the methods 'OutboundDelivery.GetListOutput' and 'OutboundDelivery.ProcessOutput.

    The outputs belonging to the deliveries entered in the 'DeliveryNumber' parameter are selected and processed immediately.

    If the 'MessageKey' parameter contains no values, all delivery outputs
    which correspond to the processing mode entered (Processing), are processed.

    The parameter 'DynamicOutputDevice' also offers dynamic control of the output device.

    Outputs can be sorted according to the value entered in the 'SortMessage' parameter.


    Error messages are stored in the BAPI return parameter RETURN with the following message types:

  • E (ERROR)
  • W (WARNING)
  • I (INFORMATION)
  • The processing status of each processed output can be taken from the return parameter 'MessageProtocol'.



    11-Dec-2005


    SaveReplica

    SaveReplica


    You can use this method to distribute outbound deliveries from an ERP system to a WM system.

    The following parameters must be passed on:
    - HEADER_DATA
    - SENDER_SYSTEM
    - HEADER_PARTNER
    - HEADER_DEADLINES
    - ITEM_DATA

    Notes


    Required fields:

    Import parameter HEADER_DATA
    - DELIV_NUMB
    - DLV_TYPE
    Import parameter HEADER_DATA_ORG
    - SHIP_POINT
    - SALESORG
    Import parameter SENDER_SYSTEM
    - SENDERSYSTEM
    Table parameter HEADER_PARTNER
    - PARTN_ROLE = 'WE' Ship-to party is required partner
    - PARTNER_NO
    Table parameter HEADER_DEADLINES

    - TIMETYPE = 'WSHDRLFDAT' Delivery date
    - TIMETYPE = 'WSHDRWADAT' Goods issue date
    Table parameter ITEM_DATA
    - OUTB_DELVRY_NO
    - ITM_NUMBER
    - MATERIAL
    - DLV_QTY
    - SALES_UNIT_ISO or SALES_UNIT
    Table parameter ITEM_DATA_ORG
    - DIVISION
    - DISTR_CHAN
    - PLANT


    Further Information

    HEADER_PARTNER

    Since the partners in the delivery are not managed on an item basis,the ITM_NUMBER field in the BAPIDLVPARTNER segment is left blank and not analyzed.


    HANDLING_UNIT_ITEM

    If the BAPI is used as an external interface for an external system,the packing hierarchy should be described as usual by using external identification numbers for shipping materials(HDL_UNIT_EXID_INTO/HDL_UNIT_EXID).


    11-Dec-2005


    SplitDecentral

    SplitDecentral


    This method allows outbound deliveries that were split in a WarehouseManagement (WM) system from an original outbound delivery to be splitin the Enterprise Resource Planning (ERP) system as well. This methodis normally carried out immediately before the WM system confirms the
    outbound delivery. If they are carried out asynchronously using IDocs, both methods must be serialized using the object type.

    Once the outbound delivery is created in the ERP system (referred to asthe "original delivery" in the following) and replicated in the WM system, you can process it normally. If several other outbound
    deliveries (referred to as "split deliveries" in the following) arecreated from this original delivery by way of a subsequent deliverysplit, you must use this method to create these split deliveries in the ERP system.

    In the SAP standard system, this method is linked to the following scenario:


    As goods issue is posted for an outbound delivery, the systemdetermines whether this delivery was involved in a split process. Thisis the case if this outbound delivery is the original delivery itself,which was already created in the ERP system, or if this outbound
    delivery was created in the WM system as a result of a split. In bothcases, it does not matter whether the delivery was split directly fromthe original delivery or from a delivery that was split previously.

    If a split delivery is posted goods issue, this method is used to
    create the new delivery from the original delivery (or reference delivery--see below).


    The DELIVERYITEMSBELONGTO parameter contains value 'N' in thiscase and the items in the split delivery are listed in the ITEMDATA table.


    If the original delivery is posted goods issue, this method is used tocreate one of the new deliveries (result of the split in the WM system)in the ERP system at this point, for use with future calls. Once theoriginal delivery is posted goods issue in the ERP system, the new
    delivery assumes the role of the original delivery and serves as areference delivery for splitting other outbound deliveries in all future calls.
    In this case, the DELIVERYITEMSBELONGTO parameter contains value 'O' and the items in the original delivery that are to be posted
    goods issue are listed in the ITEMDATA item table.

    You must specify a split profile in the BUSINESSPROCESS parameter in the interface for the subsequent outbound-delivery split that is to be carried out in sequence. In the SAP standard
    system, this split profile is the same one that is used to split the outbound delivery in the WM system. Split profiles must be maintained in the ERP system in Customizing for subsequent deliveries, but not necessarily the same wayas they are maintained in the WM system.


    The system overrides and deactivates the following Customizing settings in this method during the delivery split:

  • Renumber item numbers in old deliveries
  • Renumber Items in New Delivery
  • Delete Normal Items with Quantity 0

  • Delivery Group Splits Not Allowed
  • Delete Items from Delivery Groups if Quantity is 0
  • Check Complete Delivery Indicator During Delivery Split
  • Check Number of Partial Deliveries During Split
  • Control when Correlated Bills of Material are Split

  • Copy Text Item with Quantity 0 Automatically
  • If Split Results Same as Orignial Delivery, Then No Split
  • At item level, a quantity is specified for each item number. Thisquantity reflects the quantity of the item that is to be included in
    the split delivery or the quantity that is to remain in the original delivery. The quantity to be split is limited by the existingquantity. If the OutboundDelivery.ConfirmDecentral method iscalled up following this process, the quantities in the delivery that
    was posted goods issue are corrected. If the original delivery isposted goods issue after these methods were called up, the referencedelivery contains all items in the original delivery, including the ones with a quantity of zero.

    The CURR_QTY field controls which field the structure of the ITEMDATA parameter will appear in:


  • 'A': DLV_QTY (Quantity to be split, given in sales units)
  • 'B': DLV_QTY_STOCK (Quantity to be split, given in base units)
  • Both of these values must be able to be converted to one another by using SALES_QTY_NUM and
    SALES_QTY_DENOM
    , however. The unit of measure can be specified in SAP units (SALES_UNIT, BASE_UNIT) or in ISO units(ISOCODE_SALES_UNIT, BASE_UOM_ISO).

    Handling Units cannot be split, meaning that the items/quantities that are to be split may not be packed.



    11-Dec-2005