Thursday, July 3, 2014

Wondering why your SNP PA consistency and SNP Planning run takes too long to run? Try this note

Source: https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F64653D3030312669765F7361706E6F7465735F6E756D6265723D3133333135373626
SAP Note 1331567

Symptom
Whenever you create/change/delete APO Master Data, the SNP planning objects need to be updated. This note explains the process for updating SNP Master Data and the time series objects in liveCache.


Other Terms
Delta Queue, /SAPAPO/TS_PAREA_INITIALIZE, /SAPAPO/TS_LCM_CONS_CHECK, /SAPAPO/TS_LCM_QUEUE_UPDATE


Reason and Prerequisites
SNP Master Data is a (redundant) combination of APO Master Data entities and is used to access master data faster. SNP Master Data are so called planning objects and correspond to the aggregates defined in the planning object structure. SNP Master Data is used to access master data more efficiently (performance).


Solution
In order to avoid SNP inconsistencies you must run the initialization of the planning area and planning version after updating master data and before any every Master Data access in SNP (Interactive Planning, Heuristic Planning Run, Optimizer, ...).

The process for updating SNP Master Data cosists of following steps:
    1. Any change in APO Master Data is recorded in Delta Queue Table Level 1 (/SAPAPO/TSQUEUE):
    • Object Type (product, resource, ppm, transportation lane, ...)
    • Object Key (matid, resuid, ...)
    • Action (create, update, delete)
    • Sometimes the model
    2. The change documents stored in /SAPAPO/TSQUEUE are converted into SNP Delta Queue Level 2 entries. This step corresponds to program /SAPAPO/TS_LCM_QUEUE_UPDATE.
           Delta Queue Level 1 is analyzed (model(s) and version(s) are added), the possible characteristic combinations of Master Data are determined and stored to the Delta Queues Level 2.
           As a result, Delta Queue Level 2 will contain the combination of all keys of the changed master data, for all active planning areas and versions that are relevant for SNP.
              There are following Delta Queue Level 2 tables:            Aggregate Delta Queue Level 2 table
           9AMALO /SAPAPO/TSQMLO Material Location
           9AMALORE /SAPAPO/TSQMLOR Material Location Resource
           9AMALA /SAPAPO/TSQMLA Material Lane
           9AMALARE /SAPAPO/TSQMLAR Material Lane Resource
           9AMAPR /SAPAPO/TSQMP Material PPM/PDS
           9ARE /SAPAPO/TSQR Resource
           9AREPR /SAPAPO/TSQRP Resource PPM/PDS
           9AACPR /SAPAPO/TSQAP Activity PPM/PDS
           9AMALOSA /SAPAPO/TSQMLOSA Scheduling Agreement-Mat.-Loc.
           9AMALASA /SAPAPO/TSQMLASA Scheduling Agreement-Mat.-Lane
    3. For the planning area and planning version which is currently processed, the Delta Queue Level 2 entries are processed to create missing SNP Master Data.
              The SNP Master Data Tables are the following:            Aggregate Database table
           9AMALO /SAPAPO/MATLOC  (not SNP)
           9AMALORE /SAPAPO/MATLORES
           9ALORE /SAPAPO/LOCRES
           9AMALA /SAPAPO/MATLANE
           9AMALARE /SAPAPO/MATLARES
           9AMAPR /SAPAPO/MATPPM
           9AMARE /SAPAPO/MATRES
           9AREPR /SAPAPO/RESPPM
           9AACPR /SAPAPO/ACTPPM
           9AMALOSA /SAPAPO/MALOSA
           9AMALASA /SAPAPO/MALASA
    4. For one planning area and planning version, the Delta Queue Level 2 entries are processed to create missing time series objects in liveCache (liveCache anchors). At the end of this step the Delta Queue Level 2 entries are deleted.


Remarks:
  • Steps 2 and 3 are automatically processed before every Master Data access in SNP (Planning Area Initialization, Interactive Planning, Planning Run, Optimizer, ...)
  • Step 4 is not automatically processed, you must run initialization of the planning area and planning version.
    To not impact the performance, you must keep the delta queue level 2 tables as small as possible, this means step 4 needs to be processed for ALL initialized planning areas and planning versions.
  • If your APO Master Data is frequently updated and for performance reasons, the report /SAPAPO/TS_LCM_QUEUE_UPDATE equivalent to step 2 can be scheduled in background.
  • If you change/delete/add master data frequently and run consistency check report without performing snp relevant operations first, it is advised to run the report /SAPAPO/TS_LCM_QUEUE_UPDATE before as the Delta Queue Level 1 remains in this case and this can lead to remaining superfluous data.
  • In certain cases, the deletion of APO Master Data is not reflected to SNP Master Data and resulting of possible superfluous entries. This is due to performance reasons as the update of APO Master Data can occur frequently. It has no impact on SNP functionalities but can be fixed if needed by the consistency check report /SAPAPO/TS_LCM_CONS_CHECK.
  • You can check how many entries are in your system in the queue tables by running report Z_LCM_QUEUE_REORG which is attached to note 960941.




Header Data
Released On 26.04.2011 12:10:23
Release Status Released for Customer
Component SCM-APO-SNP-BF Basic Functions
Priority Recommendations / Additional Info
Category Consulting


Validity
This document is not restricted to a software component or software component version
References
This document refers to:
SAP Notes
1929402  Performance improvement in SNP queue update
1824737  Deadlock with tables of SNP master data
1809718  Don't check master data changes in SNP interactive planning
1560556  Master Data: missing entries for aggregates using resource
1408297  Performance improvement of Delta queue level 2 processing
1344612  Performance: Planning areas with time series key figures
1235120  Performance: SNP master data queue processing
960941  Performance: delta queues level 2 are not deleted
577038  Data inconsistencies in SNP
This document is referenced by:
SAP Notes (9)
577038  Data inconsistencies in SNP
1824737  Deadlock with tables of SNP master data
1235120  Performance: SNP master data queue processing
960941  Performance: delta queues level 2 are not deleted
1560556  Master Data: missing entries for aggregates using resource
1809718  Don't check master data changes in SNP interactive planning
1909789  Entries in table /SAPAPO/TSQUEUE deleted due to missing authorizations
1408297  Performance improvement of Delta queue level 2 processing
1344612  Performance: Planning areas with time series key figures
 
 

1 comment:

Tekslate said...

Excellent Post. Totally justified the subject discussed.