Goods Issue for the Delivery

Purpose

For more information, see Cross-System Stock Transfer (Intra-Company-Code) , Goods Issue for the Delivery , section Purpose .

In contrast to stock transfers within a company code, here only the document update in the receiving system is required. The system does not need to construct a stock in transit.

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

  • 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.

  • Goods receipt/issue slips must be created.

Prerequisites

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

Process Flow

Goods Issue Posting for Stock Transfers

See Cross-System Stock Transfer (Intra-Company-Code) , Goods Issue for the Delivery , section Goods Issue Posting for Stock Transfers .

You select the business transaction (quantity and value updates) using the movement type. This movement type is determined using the schedule line category in Customizing for Sales and Distribution.

Movement Type

Function

643

Goods issue with NB logic. The stock is posted against a consumption account (posting key GBB) and is not inventory managed in any system until goods receipt. However, you can use reporting to report on the stock on a quantity or value basis.

Data Transfer

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

Background Posting in the Receiving System

See Consignment , Goods Issue for the Delivery , section Background Posting in the Receiving System .

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 BATMAS03.

  • When you create a cross-system goods issue, the system creates the corresponding IDoc BATMAS03.

  • Changes to the batch data are also distributed using the IDoc BATMAS03.

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 .