Supply Chain Management with APO

24
3 SAP APO
Architecture
By design it is possible to use different versions of any model for simulation
purposes. Note that the ATP time series are only available for the active
version and the according flag has to be set when creating the version.
Before copying a version, it must be considered that the data volume is
usually rather huge. Note 519014 describes some of the problems which
might occur during the copying of a version and how to solve them. Versions
are copied and maintained with the transaction /SAPAPO/MVM. For
the copying it is recommended to select only the orders and use the transaction
/SAPAPO/TSCOPY to copy the time series. The requirement for the
live cache memory increases nearly linear with the number of simulation
versions, which is in many cases already a knock-out criterion for the use
of multiple versions.
If the master data is transferred from SAP ERP via CIF, it is automatically
assigned to the active model 000. But if the master data is created in
SAP APO it has to be assigned manually to the model. This can be done
either in the SCE or from the maintenance of the respective objects:
Location
Product
Resource
PPM
Fig. 3.9. Assignment of master data objects to the model
For the resource and the PPM you have to enter the object to assign it, for
the location and the product master only the object name has to be filled in.
3.4 Planners
In SAP APO most of the organisational entities from SAP ERP are
unknown. Since SAP APO is only concerned with the logistics and not
with the accounting and costing, there are no company codes and no cost
centers. Except for the locations – which is unlike in SAP ERP a master
data in SAP APO – the main organisational entity is the planner. There
are different planners for DP, SNP, PP/DS and TP/VS.
The planner is an organisational entity which is used within and across
application for selection purposes (e.g. in some standard reports, the work