Purchase Order (SAP Library - Cross-System Flow of Goods)

Purchase Order

Purpose

Intra-System Versus Cross-System Stock Transfers

In future, the user will not need to differentiate between the document types UB and NB. You can create various stock transport orders as standard purchase orders. In these orders, the prerequisite for cross-system stock transfer orders is that all possible supplying plants have been created in the ordering R/3 system as vendors. You can create several items with different receiving plants within a purchase order. These items belong to either the same company code as the supplying plant or to another company code. Intra-company-code and cross-company-code stock transfers can be processed using the same purchase order.

Process Flow

Communication Purchase Order <-> Delivery

Create purchase order

When you create a purchase order with an outbound delivery in another system, an unchecked delivery item is also created from a purchase order schedule line. At this point availability checks are switched off. The delivery date and delivery type are both split criteria.

Example

Purchase orders that are created manually:

Item 1	Material 4711 1. Schedule line delivery date 6.1 2. Schedule line delivery date 15.6
Item 2	Material 4712 1.Schedule line delivery date 6.1

The transition to an unchecked delivery is as follows:

1. Unchecked Delivery:	Item 1 Item 2	Material 4711 1.6. Material 4712 1.6
2. Unchecked Delivery:	Item 1	Material 4711 15.6.

Change purchase order

If you change any shipping-relevant data in a PO item, then the item is delivered again. Any existing unchecked delivery items are replaced.

Delete purchase order

When you delete a PO item, all corresponding delivery items are also deleted. If a checked delivery item already exists, then the PO item is not deleted.

Display purchase order

The BAPI PurchaseOrder with the method PurchaseOrder.GetDetail is available for displaying the purchase order. This BAPI has cross-system functions.

Triggering the Delivery

The system checks whether the supplying system is resident in another system. If this is the case:

The system skips determination of the shipping data in the purchase order when the supplying plant is resident in another system.
The delivery type is saved in the purchasing document and is transmitted to the LES (Logistics Execution System).
The updates to the shipping due date index are canceled.
An unchecked delivery is created in the LES.
One record for each open schedule line in the purchase order (open means ordered quantity > delivered quantity from a checked delivery) is transmitted to the LES. This also occurs when changes are made to the purchase order. The interface is so extensive (incl. texts, dangerous goods (grid processing)), that the system no longer needs to read any data from the purchase order.
The previous control for determining the delivery type using the assignment of document type <-> supplying plant has been enhanced, so that you can include a different delivery type for intra-company-code and cross-company-code stock transport items in the relevant table.
No delivery scheduling can take place in the ordering system for cross-system stock transfers. If the ordering system is connected to the SAP APO, then it is the APO that performs the delivery scheduling. For this reason, the ATP interface must be provided with data, and the results must be passed on to the LES. If the ordering system is not connected to a SAP APO system, only the desired delivery date is transmitted to the LES.