Ansicht
Dokumentation

Delivery Order Processing ( RELNSD_40_SLS_MAIS )

Fill RESBD Structure from EBP Component Structure   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Short text

Delivery Order Processing

Description

Delivery order rrocessing has been designed for component suppliers in the automotive industry. It is based on the Material Information System (MAIS) procedure.

In delivery order processing, the customer transmits material release data informing the component supplier of the materials that are required, and the date on which the customer's forwarding agent will pick up these materials.

This data is contained in what is called a pick-up sheet, which functions much like a just-in-time (JIT) delivery schedule. However, unlike the JIT delivery schedule which is continually renewed, the pick-up sheet is unique. The quantities and dates in the pick-up sheet are fixed, meaning that they must be fully delivered before the pick-up sheet can be set to complete.

Customizing changes

There are no new Customizing activities for the delivery order. However, there have been additions to the standard system:

• A scheduling agreement type for scheduling agreements with delivery orders - LZM
  

• A scheduling agreement item category - LZMA
  

• An order type for delivery orders - TAM
  

• An item category for delivery orders - TAMA
  

• An order type for correcting cumulative delivery order quantities - MAKO
  

• Copying control from scheduling agreements with delivery orders, to delivery orders
  

• An indicator in table TVAK to identify delivery order and external agent corrections

Effect on batch input

Changes to the Interface

The forecast delivery schedule in scheduling agreements with delivery orders contains the following new fields:

• Quantity to be delivered
  

Specifies the item quantity yet to be delivered in delivery orders related to the scheduling agreement.

• Total cumulative delivery order quantity and quantity in transit
  

Specifies the total cumulative quantity of an item in all delivery orders.

• Cumulative delivery order quantity and quantity in transit
  

Specifies the cumulative quantity of an item for a specific delivery order.

You can select a delivery order number using a matchcode, or manually enter one in the delivery order field.

The above cumulative quantities are influenced by the order, not by the delivery as in the case of forecast delivery schedules.

The delivery order is similiar to a sales order and can be processed as such. It contains the following new fields:

• Pick-up date and time
  

Specifies the date and time at which the customer's forwarding agent is to pick up materials.

• Sequence number
  

Indicates the sequence in which the delivered materials are used to assemble automobiles.

• Receiving point
  

Specifies the location at the customer address where materials are received.

For information on changes to EDI relevant to Delivery Order Processing, see the release note New Functions in EDI.

New procedure

The customer transmits material release data in a pick-up sheet. An EDI subsystem receives the inbound pick-up sheet and converts it to an intermediate document (IDoc) which is then stored in the R/3 System. The component supplier can process the IDoc using any of the inbound EDI message functions available in the standard system.

The system generates a delivery order on the basis of the pick-up sheet IDoc. It uses data from the pick-up sheet, such as the customer material number and unloading point, to determine the related scheduling agreements and schedule lines. It then creates an item for each material, unloading point, and delivery order schedule line. The delivery order generates new requirements that reduce requirements from the related scheduling agreement. The supplier can process a delivery order in the same way as a standard order.

Deliveries are created on the basis of delivery orders. The supplier can create one delivery for each unloading point, and combine deliveries into one shipment for each pick-up sheet number.

With partial deliveries, the supplier can create a subsequent delivery on the basis of the delivery order, or set the system to automatically complete the order. The cumulative delivery order quantity increases with each delivery order.

All data relevant to payment, including the pick-up sheet number, is contained in the delivery order and delivery. The customer can then refer to the pick-up sheet number in payment transactions.

Delivery orders and the deliveries created from pick-up sheets are displayed in the document flow.

Constraints

The R/3 System can process only inbound pick-up sheets. Other types of EDI messages are not supported in delivery order processing.

Also, we recommend that you not use delivery orders for KANBAN Processing.

BAL Application Log Documentation   General Material Data  
This documentation is copyright by SAP AG.

Length: 5747 Date: 20240603 Time: 092936     sap01-206 ( 90 ms )