Goods Issue for the Delivery 

Use

Inventory Management divides the goods issue posting into two parts that run separately in the systems. Posting the GI document in the supplying plant results in a message to the receiving plant. The receiving plant then performs a complementary posting. The goods receipt takes place as usual.

Prerequisites

For information on the prerequisites, see Cross-System Stock Transfer (intra-company-code), Goods Issue for the Delivery, section Prerequisites.

Characteristics

The goods issue takes place after all the necessary steps for the delivery have been completed.

·        The GI results in a transfer posting of the material from the unrestricted-use stock into the restricted-use, but valuated, customer consignment stock.

·        The system must send a shipping notification at goods issue in situations involving one system and in situations involving more than one system.

·        If the batch data is not distributed centrally, then it must be included on the shipping notification. Note: At goods issue, batch master data is distributed using ALE.

·        Goods receipt/issue slips must be created.

·        For deliveries to foreign consignment stores, the system should create sales tax/customs billing documents.

Process Flow

Goods Issue Posting for Consignment Fill-Up

If the supplying plant and the plant that inventory manages the customer consignment stock belong to different business areas, then when a posting is made into the customer consignment stock, the system performs a transfer posting into one of the plants that inventory manages the customer consignment stock. Both systems must be contained in one SAP System.

The GI posting contains the stock transport order data known in the delivery, including the PO item and the logical system of the recipient.

The goods issue for a cross-system stock transfer is differentiated from the integrated transaction using a new movement type.

When you post the goods movement, the system is prevented from reading the purchase order or trying to construct a purchase order history. The two indicators “Other System” and the “Indicator for the Movement” (identifies the goods movement) are used for this purpose.

The system creates a message to the appropriate receiving system for all items with reference to a cross-system consignment order. The system does not perform any validity checks on the recipient’s data before posting begins. Incorrect Customizing results in the update being terminated.

If a goods issue has receiving plants in different logical systems, then the system sends an IDoc for each logical system (SAP-internal message type GOODSMVT_SAPCREATE).

Data Transfer

The IDocs sent by the issuing plant trigger the goods issue postings in the receiving plant.

Background Posting in the Receiving System

Background posting in the receiving system is called by the IDoc and contains the data used to post the goods issue in the supplying plant.

On the receiver’s side, the system creates a material document with quantity 0, because no stock in transit is posted. However, the PO history is updated.

Reversal

For information on reversals, see Cross-System Stock Transfer (intra-company-code), Goods Issue for the Delivery, section Reversal.

Distribution of Batch Master Data and Characteristics

·        Batch information is transported using the IDoc BATMAS02.

·        When you create a cross-system goods issue, the system creates the corresponding IDoc BATMAS02.

·        Changes to the batch data are also distributed using the IDoc BATMAS02.

For more information on this topic, see the documentation on Cross-System Stock Transfer (intra-company-code), Goods Issue for the Delivery, section Distribution of Batch Master Data and Characteristics.

Shipping Notification

For information on this topic, see Cross-System Stock Transfer (intra-company-code), Goods Issue for the Delivery, section Shipping Notification.