Queries about APO livecache and database

[former_member598176]

Please correct if wrong: Only transaction data coming from R/3 is stored in LiveCache, while master data goes to APO database.

Also, there is a BW component which comes along with APO. Is it the same as APO database as mentioned in the previous statement?

[Damean · Accepted solution]

Curious as to reason why you want to know this, but here's my 2 cents:

Q:  Transaction Data in R/3 in LiveCache (LC) and Master Data in APO Database (APODB)?

Right\ Wrong ; depending on your point of view. Based on actual past observation I notice that master data (Specifically I see product, location and resources) and transactional data (Sales Order, Process Orders) could be found in both APODB and also LC (Surprise?).  Most of the time, master data is actually first loaded into APODB; however as soon as LC is initialized, it's transfer from APODB  to LC; vice versa for the transactional data.

Don't believe me? Try backup the LC data; you will notice it's basically data dump from LC to APODB. Now I presume, there's an exception to my limited observation, but it does make sense ... APODB is basically your persistent storage mechanism to ensure absolute integrity, while LC is in-memory ...

Q: BW component which comes along with APO. Is it the same as APO database?

NOPE ... BW is actually part of the Basis (aka Netweaver) Stack; it's found in most of the Business Suite from ERP, CRM, SRM, etc. It's star schema based BI tool (e.g. Infocube) and NOT the same as APODB. It function like APODB in the sense that this is where the initial DP data are loaded before being transferred to the LC.

HTH ...

[somnath_manna]

First let us understand APO is one application component of SCM system that uses liveCache an in-memory (yes much before HANA was even conceptualised) object-oriented database. Apart from APO there are other applications components like SNC, SPP, F&R, EWM in the SCM system (you can see them in main menu or if you see only APO transaction menu then use t-code /n/scmb/menue to get to main menu of SCM system).

Now let us get BW out of the equation. APO BW is nothing different than BW component available in any SAP Netweaver system. So all the data of APO BW is stored only in Database of the SCM system. It is definitely NOT stored in liveCache. Of course you can question why is it MPOS generate a shadow table in BW where the CVCs are stored. But that is just the key. The actual timeseries data i.e. APO DP keyfigure data is stored in liveCache against the keys which are linked through a gibberish GUID.

Now comes to your main question of master and transaction data coming from R/3 or ECC via CIF. All the data goes into database first. But additionally some master data (Location-Products, Resource TimeStream, PDS master) is moved to liveCache immediately. All transaction data is replicated in liveCache also for APO planning to work. The key point to note is that APO interactive planning uses liveCache data for all planning activities. That means all transaction data and planning / scheduling relevant master data is form liveCache.

Hope this helps.

Somnath

[former_member187488]

Hello,

Sorry but I cannot totally agree with the above replies.

For APO (not all SCM functions), master data (location/product/t-lane/PDS&PPM/quota/hierarchy/resource, etc.) is mostly saved in APO database, and transactional data is saved in liveCache with two different types - liveCache time series (used in DP and SNP) and liveCache orders (used in SNP and PPDS).

BW is acting as a kind of APO DB - when you create planning object structure and planning areas, an internally generated infocube will be created, to hold the master data (e.g. CVCs). That is why you need a embedded BW in APO system. You cannot manually operate these generated cubes -- APO system manages them itself. This embedded BW inside APO may be different from external BW systems. (In above replies, you're talking about external BW.)

Regarding data extraction (to external BW) functionality, it's just the same as in other system - you extract any data into infocube, but the extracted data (in infocube) is never used by any APO functionality directly. You can not say these cubes save any master or transactional data actually for APO systems.

BR, Ada

[kenneth_snyder]

Everyone seems to be correct but also wrong.

Rohit needs to be more specific on his question.

Master data is stored in tables but is also loaded into LC for planning purposes.

Transactional data is normally loaded into LC  but some is also stored into tables (such as forecast consumption information). 

PPDS simulations also complicate the issue.

What is the reason for the question?

Ken

[Former Member]

from book of SCM230 you can understand that mainly the master data is in tables and transaction data in LC

the BW in APO have the similar functions of the independent BW, base on the info cubes build by characteristics.

for this kinds of question, if not a basis, just let it go, when you work and use APO for years, you will know about it. the logcis the arch and how it works.

[Former Member]

just a quick example here, apart from above two useful explanations, for easy of understanding....

In DP module, data coming from ECC doesnt go into LC. any ECC data (transaction or Master data) goes into Cubes, then you need to sync your LC with that information, to access data in Planning books.

this is a continuous support activity you do day in and day out.

Hope it helps.

Sandeep

[Former Member]

Hi Rohit,

Both Transaction and Master data are stored into APO database tables.

Livecache is to do the calculations with respect to the available Master & Transaction data which is of in very high volume, The results of this calculations will be available in livecache and only untill next calculation run as it will be overwritten. Livecache will hold only the planning (predicted) information and not the real information.

Ex. Result of Forecasting will be stored in Livecache which can changed at anytime ( interactive Forecasting & Planning Jobs etc). Forecast results are PIR which is a prediction based on your past sales so storing/saving the large volume predicted information into database tables is of no use and resource consuming. And thus Livecache is used as its a virtual database (not real) which will hold only temporary information.

BW is different nomenclature when compared to Database, it never stores data in the format of RDMS way - Rows and columns rather as Dimension and Fact tables (multidimensional).

Livecache information were pushed into APO cubes (MPOS/Planning Area) so that your predicted information (Forecast/PIR) will remain there which is similar to what you save data in Databases.

Regards

Vinoth