Report /SAPAPO/CHECK_LOCATION_TYPE can be utilized for modifying the location type (say from 1001 to 1002 or vice-versa) of the already existing locations in APO. The table to refer is /SAPAPO/LOCMAP. SAP does not suggest this process.
Two databases are present in SCM APO:
The first database in present in the BW as Info Cubes and second data has been stored in Live Cache. The data stored in Live Cache is primarily utilized for processing and planning specifically during transactions. Cubes are only for preserving the data and backing up data. The main reason for initiating APO as a different server (box) is to make the process of simulation faster by utilizing the Live Cache memory database which is comparatively much faster as compared to accessing the data which is preserved in tables apart from the ECC module.
By using the function mobile, the Planning Version can be frozen and unfrozen. /SAPAPO/TS_PAREA_VERSIO_FREEZE so that no further changes can be made to the planning version.
TSAP R/3 connects with the SAP APO by using the APO Core Interface (CIF) which supplies SAP APO with master and transaction data on a real time basis. CIF is delivered through the R/3 Plug-In, which the user is required to install in his SAP R/3 system. This is the same Plug-In which will be required for connecting a BW or a CRM system.
No, it is not possible. SAP APO requires a different server. The actual size of the SAP APO system varies and depends on the data volume which has to be processed.
PP/DS fixing Horizon defines the PP/DS time Fence – specifically within that period if heuristic is run no orders are modified.
The user is required to utilize OLIX for first deleting the previous MRP planning versions. Then using MCB & for creating the new MRP planning versions by selecting the appropriate version the user wants to create as ICO Version. The info structure here is S094.
All work centers which have been classified with a similar class number and the similar characteristic value in the work center and in the operation are relevant.
Release Profile is used to releasing time series data from DP to SNP/PPDS. The user needs to defining the DP Planning Area and time series keyfigure the data in which is released and the SNP Category Type (typically FA) to which data is released. The user can maintain a Daily Buckets Profile which will help in defining the number of working days (working days determined based on Shipping Calendar maintained for the location master) which starts from on and from the From Date if released online/ interactively or the number of workdays of the planning horizon when the release is performed in background. The Period Split (blank, 1 and 2) field in the SNP2 tab of location-product master determines how will the demand plan be released to SNP from DP (how bucketed data is disaggregate to the workdays).