Allocation Table Synchronization for Order Changes (Seas. Proc.) 

Use

You usually define allocation tables at an early stage in your business processes because you plan and order fashion goods, for example, with a long lead time. If your requirements change after you have created a purchase order but before the goods are delivered, for example, due to new stores opening, you can change the existing purchase order.

The system updates allocation-relevant changes in purchase orders to the relevant allocation tables.

Integration

You make changes to allocation-relevant purchase order items in purchase order processing for Seasonal Procurement. A log provides you with information about changes and about the synchronization of the allocation table.

The system synchronizes an allocation table in the background when purchase orders are changed.

Prerequisites

·        You have generated a vendor order (Seasonal Procurement) as a follow-on document for an allocation table, manually created an allocation table with reference to a purchase order (Seasonal Procurement), or generated an allocation table with reference to a purchase order based on operational assortment planning and control.

·        Apart from the vendor order there are no other follow-on documents for recipients of the corresponding allocation table item.

Direct delivery orders cannot be synchronized.

·        The purchase order item that you change must be uniquely linked to a delivery phase of the distribution center for an allocation table, otherwise synchronization is not possible.

Features

When the following data is changed, the system updates the changes to the allocation table:

·        Purchase order quantity and order unit

·        Delivery date in distribution center

·        Distribution center

·        Flag for allocation table relevance

·        Deletion of a purchase order item

You can use a Business Add-In (BAdI) to specify that when the allocation table is synchronized, the data for the distribution center be adjusted, but not the data for the recipient.

For more information, see Customizing for Logistics - Generalunder Merchandise Distribution → Allocation → Allocation Table → Business Add-Ins for the Allocation Table → BAdI: Synchronizing Allocation Table for Changes to PO Items.

Activities

If you change purchase order items in purchase order processing for Seasonal Procurement and confirm your changes, the system first simulates synchronization of the corresponding allocation items. The changes are only effective in the database once you have saved them.

In both cases, you can check the results of changes in a log.

Synchronization is performed in several steps:

...

       1.      The system checks whether follow-on documents exist for recipients of the allocation table item. If they do, the system cannot change the allocation table and it issues a message to purchase order processing stating this.

       2.      The system copies the changes in the purchase order item to the distribution center of the relevant allocation table item.

       3.      The system copies changes that are relevant for the allocation table item from the purchase order item. While changes to the delivery date are not relevant, changes to quantities, for example, are.

       4.      The system transfers changes that are relevant for recipients for the individual allocation items .

You can use a BAdI to deactivate synchronization of recipient data.

       5.      It is possible that after the system transfers changes from the purchase order item to the allocation table items, these allocation table items will be incomplete. To ensure that the items are complete again and you are able to generate follow-on documents, you must postprocess incomplete allocation table items in the item overview of the allocation table.

See also:

Purchase Order Processing (Seasonal Procurement)