Use
The
SAP APO Core Interface can be used to transfer the following stock data from SAP R/3 to SAP APO:The above stock types are stored at the following stock management levels in SAP R/3 and are derived from the following tables:
Stock management level |
Table |
Storage location stock |
MARD |
Batch stock |
MCHB |
Stock in transit |
MARC |
Project stock |
MSPR |
Sales order stock |
MSKA |
Special stocks with customer |
MSKU |
Special stocks with vendor |
MSLB |
Special stocks from vendor |
MKOL |
Integration
You can use the integration model to transfer all of the stocks above or just individual stock types, such as sales order stocks.
If the push transfer function is activated, only those stock changes that result from material movements are transferred to SAP APO.
The filter objects required to transfer the stock data are generated at the material/plant level. The advantage of this is that objects that are not created until the first goods movement, e.g. the storage location, can be easily transferred to SAP APO using push technology. This means that you do not have to activate a separate integration model for each new batch or storage location.
For further information, see
Data Transfer.Prerequisites
Data transfer between the SAP R/3 System and SAP APO is possible as of SAP R/3 Release 3.1I For further information, see
Integration of SAP APO and SAP R/3.Stock data can be transferred from an external system to SAP APO via a BAPI.
The following master data objects must be transferred first to ensure that the stock data is transferred smoothly:
Features
Representing stocks in SAP APO
Project stock and sales order stock are managed as special stock in SAP APO.
Stocks that are physically located in a separate plant or storage location in SAP R/3 are also managed for the plant location or sublocation.
Stocks that are physically located on the vendor's premises, e.g. stock with subcontractor, are managed for the vendor location in SAP APO.
Stocks that are physically located on the customer's premises, e.g. consignments or returnable packaging, are managed for the customer location in SAP APO.
Stocks that are originate from the vendor, e.g. consignment stocks, are managed for the plant/storage location in SAP APO. These stocks are not classified according to vendor in APO.
Batches are represented as versions in SAP APO.
Storage locations are represented as sublocations in SAP APO.
Negative stocks cannot be transferred.
SAP APO records movement data in the form of versions. Stock data originating form SAP R/3 is always managed in the active version 000.
Modeling in liveCache
All movement data in SAP APO is managed in the form of orders in the liveCache. The order header contains the following information:
The order items below the order header represent the individual stocks, each of which is categorized in accordance with its sublocation (storage location) and ATP category.
Activities
You can navigate through the stock display in SAP APO as follows:

If SAP APO is not working with the liveCache, the stock is posted in the material master.