Cross-System Stock Transfer
(Intra-Company-Code)
Use
The purpose of cross-system stock transfer (intra-company-code) is described in the following sections.
Prerequisites
● The basic system landscape for this process (SAP APO, ERP) and the organizational units involved (company codes, profit centers) have no effect on the process flow and handling for the end user.
● The processes have been designed so that they can be used in a wide range of circumstances without a joint planning instance (SAP APO).
● We assume that legacy systems behave as ERP systems for communication between the involved SAP components.
● The following are system prerequisites for implementing the process:
○ SAP Enterprise Core
○ PlugIn 2001.2 (APO Core Interface)
○ APO Rel. 3.0A
● The number of process variants is a result of the combination of system landscape and organizational units:
○ Within a company code
○ Cross-profit center
○ With or without joint SAP APO
Process Flow
The following processes are generally supported by SAP:
...
1. Cross-System Stock Transfer (Intra-Company-Code) within an ERP System with Joint SAP APO
2. Cross-System Stock Transfer (Intra-Company-Code) Between Two ERP Systems with Joint SAP APO
This scenario is realized with the new function for unchecked deliveries.
You can also process stock transport orders between two ERP systems without implementing unchecked deliveries. To do this, you use purchase orders and sales orders. Synchronization between the purchase order and the sales order is only possible using IDocs. The point of issue cannot perform a posting into the stock in transit at the ordering party using an IDoc. This must be done manually. This is the standard ALE scenario Stock Transfers.
Effects on SAP Business Objects
Synchronization of MRP elements in SAP APO:
● The SAP APO stock transfer creates a purchase requisition (PReq) in the ERP System. This PReq generates a receipt element for the ordering plant and an issue element for the supplying plant.
● When the PReq is converted into a purchase order, the MRP elements generated by the PReq are deleted and are replaced by the purchase order.
● The purchase order creates an unchecked delivery in the supplying plant’s system. The reservation created in the supplying plant using the purchase order is deleted and is replaced by the unchecked delivery.
● When the unchecked delivery is converted to a checked delivery, the requirement from the unchecked delivery is deleted in the supplying plant and is replaced with the requirement from the checked delivery.
● The goods issue posting in the supplying plant reduces the stock. The stock change is transmitted to SAP APO. At the same time, the delivery requirement is canceled.
● The GI posting into the stock in transit of the ordering plant results in the cancellation of the receipt element in the ordering plant. The stock change is transmitted to SAP APO and increases the stock in the ordering plant.
● Posting the stock in transit into the physical, unrestricted-use stock results only in a transfer posting of the stock types in SAP APO. The stock in transit is reduced and the unrestricted-use stock is increased.
● If you create a PReq manually in the ERP system, then you can perform an ATP check in SAP APO. To this end, the system creates a temporary requirement in SAP APO. The supplying plant and the confirmed quantity are copied into the purchase requisition. When you save, the temporary requirement in SAP APO is canceled and is replaced by the requirement from the purchase requisition.
Structure of the Complete Concept in Subprocesses
● Delivery for Unchecked Delivery
● Goods Issue for the Delivery
● Goods Receipt for Purchase Order
● Returns