What is Live Cache in APO

Hi Gurus,
I am working on APO datasource in SNP,
How do the live cache filled up? I have built a cube top of a custom datasource (9AZSNP), everything works fine and i want to know what is behind the live cache, is it directly a user entry planning version template or any underlying tables.
Please advise.
Thanks. Gowda

Hi,
The datasource will use only planning version template, and data will trabsfer from Planning area to BW. Regarding Liveche you talk to APO guys,,, it will store data and it is dynamic..
Check
Feeding Cube from Live Cache
Re: Livecache for SCM/APO
Re: what is the use of Livecache,why can't we go with relation databases...
Thanks
Reddy
Edited by: Surendra Reddy on Mar 7, 2009 5:39 AM

Similar Messages

What is live-cache?

Hi Experts,
Can any one explain what is live-cache and eash access in supply chain management and what is customization in SCM?
Cheers,
Aanand.

In Supply Chain Management, large volumes of data must be permanently available and changeable. For this reason, an addition has been made to the SAP DB OLTP relational database system to enable actual data structures and data flows (such as networks and relationships) to be mapped more easily and effectively. The product is called liveCache. The liveCache is object-oriented, and in contrast to SAP DB OLTP, stores its data in the main memory of the database system.
The SAP liveCache technology significantly increases the speed of the algorithmically complex, data- and runtime-intensive functions of various SAP applications, especially within SAP Supply Chain Management.
It combines the advantages of main memory-based data retention with a complete operating concept, including backup & recovery. The application functions are provided by database procedures (liveCache Applications) having an extremely fast access to all application data which can completely cached in main-memory and are organized in relational but mainly object oriented manner.
The SAP liveCache technology can be characterized by a hybrid main-memory database with intensive usage of database procedure.
For more information, please access the following links:
SAP liveCache technology
http://maxdb.sap.com/doc/7_7/f3/3edeb38ab14f9798d2a800b2c439c9/content.htm
Have a nice day!
Will
SCM Moderator

What is Live Cache Anchor

Hi ,
Some times we see errors like "No Live Cache Anchor Found". Can somebody tell me in detail that what is a live cache anchor and why this inconsistency occurs. Is there a link containing detailed documentation?
Best Regards,
Chandan Dubey

Dear Chandan,
This error message "No Live Cache Anchor Found" states that for one or even for several characteristics combinations (see Transaction /SAPAPO/MC62) a so-called LiveCache anchor does not exist.In this case, a LiveCache anchor is a pointer to one or several time series in the LiveCache.
There is one LiveCache anchor per planning area, characteristics combination (planning object) and model (model belonging to the planning version, see transaction /SAPAPO/MVM). If for one planning area, time series objects were created for several versions with different models, that means several LiveCache anchors exist for the same planning area and for the same characteristics combination.If you created time series objects for several versions of the same model, that means one LiveCache anchor
points to several time series in the LiveCache.
If there is no LiveCache anchor for a planning area, a model and a characteristics combination, this also means that no respective time series exists in the LiveCache and thus, this characteristics combination cannot be used for the planning with this planning area for all versions of the model.If this state occured for a certain characteristics combination, the above-mentioned error message occurs if either exactly this characteristics combination is selected or if a selection contains this characteristics combination.
Possible causes and solutions:
- Time series objects have not yet been created for the selected version.
Solution: Create time series objects (see documentation)
- You are using a planning session with version assignment.For the version that was acutally selected, the time series objects were created, however, this is not the case for the assigned version.
Solution:Create time series objects for the assigned version.
- New characteristics combinations were created without the 'Create time series ob' option (see Transaction /SAPAPO/MC62).
Solution:Execute the report /SAPAPO/TS_LCM_PLOB_DELTA_SYNC for the basis planning object structure of the planning area.This will create the corresponding LiveCache anchors and LiveCache time series for all planning areas that used these basis planning object structure and for all versions of these planning areas for which time series objects already exist.
If none of these possible solutions is successful, you can use report /SAPAPO/TS_LCM_CONS_CHECK to determine and correct the inconsistencies for a planning area ('Repair' option).
I hope this helps.
Regards,
Tibor

Data movement from R/3 DB to APO DB and to Live cache

Dear APO Experts,
I have few questions on live cache and how it works, I understand that Live cache is memory resident database. below are my questions.
1) What sought of data move from R/3 DB to APO DB and then to Live cache DB
2) When data moves from APO DB to Live cache, till how much duration that data stays in live cache
3) And how does data gets pulled in to live cache from APO DB
4) Why do we require live cache logs while data never gets commited to hard disk
5) Do we ever add a datafile to Live cache DB
any info that you provide on this will be really helpfull to me
Thanks,
Chetan

Hello Chetan,
As you know, itu2019s MAXDB/liveCache forum.
What is the version of your system?
The is documentation available at:
   SAP liveCache technology
< Please review document u201CWhat is SAP liveCache technology?u201D >
Sap documents at service.sap.com/scm -> Technology:
u201CliveCache overviewu201D and u201CIntegration overviewu201D
For SAP liveCache documentation also see the SAP note 767598.
Go to SAP link Best Practices for Solution Management: mySAP SCM at   SAP liveCache technology ...
And Review the document u201CManage APO Core Interface in SAP APO (3.x) / mySAP SCM (4.x/ 5.0)u201D
1. As you saw in the reference documents the data transferred from the connected R/3 system to APO.
And the transactional data could be uploaded to the liveCache, if you downloaded them
to the APO database cluster tables first. This procedure steps are running during the
system upgrade < for example, from SCM 5.0 to SCM 7.0 ) u2013 report /SAPAPO/OM_LC_UPGRADE_70 steps. Or you want to migrate the
liveCache to another operating system or convert your system to Unicode,
and therefore you want to back up the liveCache data first so that you
can reload it into the liveCache afterwards - SAP Note No. 632357.
2. Could you collaborate more on this sentence. Could you give examples?
3. u201CAnd how does data gets pulled in to live cache from APO DBu201D
    The data are not pulled from the APO DB to liveCache.
     When you changed the APO data on the system the LCA procedures have been called from ABAP. The objects stored in the class containers in liveCache can be accessed and manipulated only via LCA routines. The registration of the LCA routines is done automatically when the liveCache is started by the LC10. The LCA procedures in the LiveCache are written in C++
and shipped to the customers as binary LCA libraries(LCA build) together with the LiveCache.
< See more details in SAP Note No. 824489 or 1278897 as of SCM 7.0 >
4. See the SAP notes:
               869267     FAQ: SAP MaxDB LOG area
             1377148     FAQ: SAP MaxDB backup/recovery
5. You could run the quicksizer & estimate how much data you are planning to have in liveCache.
     Also the amount of data could be increased by the creation of the new data in APO by users
     Or another reason u2026
     In general you will add the datavolume to solve or prevent the DB_FULL issue,
     See u201C17. What do I do if the data area is full? u201C in SAP note 846890.
Thank you and best regards, Natalia Khlopina

Live Cache Locks

Dear Friends,
What does Live Cache Lock mean? How do we use this and what is it for? How to manage in APO? Can anyone let me know answers pls. Thanks in advance.
Regards
Bala

Hi Bala,
When you create, change and delete orders, rows in relational tables are changed or deleted in the liveCache. The corresponding records stay locked until the end of the transaction. The maximum number of locks on relational records is determined with parameter MAXLOCKS.
If a transaction requires more than 10% of the lock list for locks onto a table, all the multiple row locks are converted into a single table lock (this is called an 'escalation'). If several transactions escalate at the same time, wait situations occur since only one transaction can set the table lock.
There is no 'management' of locks required in APO. If you are seeing many lock escalations in liveCache, an increase in the MAXLOCKS parameter might be necessary.
Thanks,
Ashwath

Live cache start and stop

Hi Guys,
I have some problem in live cache in APO , i was posting in APO forum could not able to find clear findings
so i am diverting my questions here in this forum
basically the APO and R/3 system are running smoothly with no problem in CIF
but accidently we done the below steps
Entered into transaction LC-10
Click Live cache Monitoring
click the folder - Administration
click Operating under - configuration
There are two Icon bar - start LiveCache and stop LiveCache
First i clicked stop and then after few minutes i click start
After some time i try to open the Product view in APO, the system says Live cache not available
can some one help me in this regard
Thanks
Raj

Hi,
Here is the log you asked me
veCache LC1 (restart)
Mon 10/15/2007
03:00 AM
installation path = e:\sapdb\lc1\db
OK
OK
DBMServer 7.6.03   Build 008-123-159-187
starting LC1 into ONLINE
OK
Creating liveCache application procedures
OK
0,OK: everything works fine
0,""e:\sapdb\lc1\db\bin\x_python" "e:\sapdb\lc1\db\env\lapps.py" -R "e:\sapdb\lc1\db" -d LC1 -u SUPERDBA,*"
Installing APPS
Droping Procedures
    LC1ADM
      SAPTS
      SAPLCK
      SAPAPO
      SAPATP
      SAPREP
      SAPSIM
      SAPRPM
      DBPINSTALL
Creating Procedures
    LC1ADM
      dbpinstall
        FORCE_CHECKPOINT
        WAIT_FOR_CHECKPOINT
        FORCE_AND_WAIT_FOR_CHECKPOINT
      SAPAPO
        APS_COM_VERSION_GET
        APS_PROPAREA_CHANGE
        APS_PROPAREA_GET_DATA
        APS_PEGAREA_CHANGE
        APS_PEGAREA_GET_DATA
        APS_PROPAREA_GET_ALL
        APS_ORDERTYPE_GET_ALL
        APS_ORDER_GET_ALL
        APS_PEGID_GET_ALL
        APS_IPPE_GET_ALL
        APS_RESOURCE_GET_ALL
        APS_PLAN_VERS_GET_ALL
        BAS_PLAN_VERS_GET_ALL
        APS_PLAN_VERS_GET_ALL_DEFECT
        APS_PCM_GET_ALL
        APS_OBJECT_GET_ALL
        APS_OBJECT_EXISTS
        APS_CONTAINER_CHANGE
        APS_CONTAINER_GET_DATA
        APS_GET_ALL_CONTKEYS
        APS_PLAN_VERSION_CHANGE
        APS_PLAN_VERSION_GET
        APS_THROW_DBP_ERROR
        APS_SCHEMA_CREATE
        APS_SCHEMA_DELETE
        APS_SCHEMA_GET_ALL
        APS_SCHEMA_GET_ALL_DEFECT
        APS_TIME_GET
        APS_MIXIN_ATP_DELTAS
        APS_MLEVEL_ATP_PROT_DEL
        APS_REORG_ATP
        APS_REPAIR_ATP
        APS_GET_ATP_DATA
        APS_ALERTS_GET_DATA
        APS_ALERTS_IN_ORDER_NET
        APS_ALERTS_DELAY_ORDER_NET
        APS_TRACELEVEL_READ
        APS_TRACELEVEL_CHANGE
        APS_TRACELEVEL_GET_ALL
        APS_TRACE_WRITE
        APS_CUST_GET_DATA
        APS_CUST_CHANGE
        APS_CHECK_PERS_DATA
        APS_PERS_OBJ_EDIT
        APS_IPPE_CHANGE
        APS_IPPE_GET_DATA
        APS_IPPE_GET_ORDERS
        APS_IPPE_GET_BY_IO
        APS_ORDER_GET_TIMES
        APS_RG_OF_COVER_MATRIX
        APS_RANGE_OF_COVER_GET
        APS_OPT_GET_ACTIVITY_NET
        APS_OPT_GET_ACTIVITY_NET2
        APS_OPT_UPDATE_ACTIVITY_NET
        APS_BS_SEND64
        APS_PERFTEST_1
        APS_PERFTEST_2
        APS_PERFTEST_3
        APS_PERFTEST_4
        APS_PERFTEST_5
        APS_PERFTEST_6
        APS_PERFTEST_7
        APS_PERFTEST_8
        APS_PERFTEST_9
        APS_PERFTEST_COMB
        APS_PERFTEST_READ_100
        APS_PERFTEST_WRITE_100
        APS_PERFTEST_READ_1000
        APS_PERFTEST_WRITE_1000
        APS_PERFTEST_READ_8000
        APS_PERFTEST_WRITE_8000
        APS_PERFTEST_TRANSMISSION
        APS_IO_RESET_NETCHG_FLAG
        APS_ORDER_GET_DATA
        APS_ORDER_CREATE
        APS_ORDER_CHANGE
        APS_ORDER_DELETE
        APS_ORDER_MODIFY
        APS_FLEX_ORDER_CHANGE
        APS_CHARACT_MODIFY
        APS_CONSTRAINT_MODIFY
        APS_PEGID_SELECT_ORDERS
        APS_ORDER_GET_REQMTS
        APS_ORDER_GET_SUPPLY
        APS_PCM_DELETE
        APS_PCM_GET_ORDERS
        APS_PEGID_GET_IO
        APS_PEG_REFRESH_IO
        APS_PEGID_COUNT_IO
        APS_PEGID_GET_VIRT_PEG
        APS_PEGID_GET_ORDERS
        APS_PEG_CAT_GET_ORDERS
        APS_SEARCH_DESC_CHAR
        APS_FIX_PEGGING_CHANGE
        APS_PEGARC_TYPE_CHANGE
        APS_PEGPARAM_CHANGE
        APS_PEGID_GEN_PM_TRACE
        APS_ACT_STATUS_CHANGE
        APS_ACT_UNPLAN
        APS_ACT_GET
        APS_SFW_INITIALIZE
        APS_SFW_IONODE_SCHEDULE
        APS_SFW_GET_NEXT_SET
        APS_SFW_SCHEDULE_SET
        APS_SFW_TERMINATE
        APS_STOCK_TSERIES_CMP
        APS_STOCK_TSERIES_GET
        APS_ACT_SCHEDULE
        APS_ACT_GET_BY_RES
        APS_ACT_GET_BY_ORDER
        APS_ACT_GET_BY_PEGAREA
        APS_RESOURCE_GET
        APS_ORDER_GET
        APS_PEGAREA_GET
        APS_PROD_GET_BY_PEGAREA
        APS_CUS_ORDER_CHANGE
        APS_CUS_ORDER_GET
        APS_CUS_SCHD_GET_BY_PEG
        APS_CUS_SCHD_GET_BY_IO
        APS_DELIVERY_CONF
        APS_DELIVERY_MESSAGE
        APS_FORECAST_GET_BY_PEG
        APS_RESOURCE_CHANGE
        APS_RESOURCE_GET_DATA
        APS_CAPA_PROFILE_GET
        APS_PERS_OBJ_ANALYZE
        APS_RES_COLL_MERGE
        APS_RES_MAX_COLL_BUFFER
        APS_STOCK_CHANGE
        APS_STOCK_GET
        APS_STOCK_GET_BY_UID
        APS_SETUPMATRIX_CHANGE
        APS_SETUPMATRIX_UPDATE
        APS_SETUPMATRIX_GET_DAT
        APS_RESOURCE_GET_BRUTTO
        APS_TIMING_PATTERN_GET
        APS_BUCKETS_GET_NETTO
        APS_DATE_VECTOR_CHANGE
        APS_DATE_VECTOR_GET
        APS_TIMESTREAM_CHANGE
        APS_TIMESTREAM_GET_DATA
        APS_TIMESTREAM_GET_BY_RES
        APS_TLO_GET_RANGE
        APS_TRANS_ORDER_CHANGE
        APS_TRANS_ORDER_GET
        APS_DRP_AMOUNT_GET
        APS_DRP_FLOW_GET
        APS_DRP_IO_GET
        APS_DRP_CONTI_IO_GET
        APS_SNP_ORDER_GET
        APS_SNP_CAPA_GET
        APS_SPP_FORECAST_MODIFY
        APS_SPP_PUR_REQ_MODIFY
        APS_SPP_FORECAST_EXT_MODIFY
        APS_SPP_ORD_AMOUNT_GET
        SAPAPO_COMTEST_1
        SAPAPO_COMTEST_2
        SAPAPO_COMTEST_NEW_PLANVERS
        APS_SET_TEST_PARAMS
        SAPAPO_CLEANUP
        SAPAPO_RESET_GLOBALS
      SAPATP
        SAPATP_READ_TIMEAXIS
        SAPATP_READ_CSV_ARRAY
        SAPATP_SETUP_TIMEAXIS
        SAPATP_CLEAR_TIMEAXIS
        SAPATP_CHECK_AVAILABILITY
        SAPATP_LS_LOGFILES
        SAPATP_RM_LOGFILES
        SAPATP_CREATE_MATRIX_OBJECT
        SAPATP_DELETE_MATRIX_OBJECT
        SAPATP_GET_MATRIX_OBJECTS
        SAPATP_REORG_MATRIX
        SAPATP_GET_CHAR_KEY
        SAPATP_GET_CHAR_KEY_MULTI
        SAPATP_GET_CHAR_LIST
        SAPATP_READ_MATRIX
        SAPATP_MATRIX_FIND_VERSIONS
        SAPATP_READ_VPL_TIMEAXIS
        SAPATP_READ_BUCKET_PARAMS_SIM
        SAPATP_READ_TIMEAXIS_BOMID
        SAPATP_PAC_CHECK
        SAPATP_DELTA_EXIST_ANCHOR
        SAPATP_DELTA_GET_REMOVE_ATP
        SAPATP_DELTA_GET_REMOVE_ALLVPL
        SAPATP_DELTA_GET_AGGREGATES
        SAPATP_DELTA_GET_POSG_ATP
        SAPATP_DELTA_READ_TOTAL
        SAPATP_DELTA_READ_TRGUID_APS
        SAPATP_DELTA_READ_DELNRAPS
        SAPATP_DELTA_ADD_ATP
        SAPATP_DELTA_UPD_ALLVPL
        SAPATP_DELTA_UPD_ATP
        SAPATP_DELTA_COMPRESS_APS
        SAPATP_DELTA_REMOVE_TRGUID
        SAPATP_DELTA_UPD_POSG_ATP
        SAPATP_DELTA_GET_UPD_POSG_ALVP
        SAPATP_DELTA_CHANGE_POSGUID
        SAPATP_DELTA_REMOVE_DATE
        SAPATP_DELTA_GET_PLUIDS_F_TRG
        SAPATP_DELTA_GET_PLUIDS_F_DAT
        SAPATP_DELTA_CLEAR_ANCHOR
        SAPATP_DELTA_GET_ALL_ADMIN_ANC
        SAPATP_DELTA_DELETE_ALLOC_ANC
      SAPLCK
        LCK_ENQUEUE
        LCK_DEQUEUE
        LCK_RELOAD
        LCK_CONSISTENCY
        LCK_LIST_ALL
        LCK_LIST_SINGLE
        LCK_LIST_BY_AREA
        LCK_LIST_BY_OWNER
        LCK_LIST_BY_USER
        LCK_LIST_OWNERS
        LCK_DEQUEUE_OWNER
        LCK_STATISTICS
        LCK_ENQUEUE02
        LCK_DEQUEUE02
        LCK_LIST_ALL02
        LCK_LIST_SINGLE02
        LCK_LIST_BY_AREA02
        LCK_LIST_BY_OWNER02
        LCK_LIST_BY_USER02
      SAPSIM
        SIM_SIMSESSION_CONTROL
        SIM_SIMSESSION_COPY
        SIM_SIMSESSION_SAVEAS
        SIM_SIMSESSION_UNDO
        SIM_SIMSESS_HAS_DELTAS
        SIM_SIMSESSION_GET_DATA
        SIM_SIMSESSION_GET_DELTAS
        SIM_SIMSESSION_GET_ALL
        SIM_SIMSESSION_GET_ACTIVE
      SAPREP
        REP_INIT
        REP_CLOSE
        REP_CHECK
        REP_CHECK_MULTI
        REP_ACKNOWLEDGE
        REP_REVERT
        REP_RETHEAD_READ
        REP_RET_READ
        REP_CAPA_CHANGE
        REP_DEMAND_CHNG
        REP_PLNVERS_READ
        REP_PLVERS_READ
        REP_TX_READ
        REP_DELTAS_REORG
        REP_CONSI_CHK
        REP_DELPOS_DEL
        REP_NEWPOS_DEL
        REP_DELPOS_GET
        REP_NEWPOS_GET
        REP_REVERT_MULTI
        REP_INST_DELETE
        REP_INST_CREATE
        REP_DEM_INIT_REC
        REP_CHECK_EXIST
        REP_TIMELINE_CRE
        REP_INST_CHECK
        REP_CHK_LOCK_GET
        REP_CHK_LOCK_SET
        REP_CHK_LOCK_DEL
        REP_DELTA_DISP
        REP_POSGUID_DISP
        REP_CORR_QTY
        REP_CHECK_NEW
        REP_RESERVE_DEBUG
        REP_ACKN_RES_FOR_TX_DEBUG
      SAPRPM
        RPM_ACTS_FOR_WORKCENTER
        RPM_ADD_NODES
        RPM_BF_CALC_ORDER_STATUS
        RPM_BF_DELETE_ORDER_STATUS
        RPM_BF_MODIFY_STATUS
        RPM_BF_READ_ORDER_STATUS
        RPM_CHG_R_ORD_CF
        RPM_COPY_RES_ORD
        RPM_CREATE_MATRIX
        RPM_CUSTOMIZING_MODIFY
        RPM_CUSTOMIZING_READ
        RPM_DEL_RES
        RPM_DEL_RES_ORD
        RPM_DELETE_MATRIX
        RPM_DELETE_ONE_CONFIG
        RPM_MATRICES_FOR_CUOBJ
        RPM_MATRICES_FOR_ORDID
        RPM_MATRICES_FOR_ORDID_MUL
        RPM_MATRICES_REORG
        RPM_MATRIX_PROPERTIES
        RPM_MATRIX_PROPS_UPDATE
        RPM_MODIFY_CONFIGS
        RPM_MODIFY_ONE_CONFIG
        RPM_PARKED_ORDERS_READ_ALL
        RPM_READ_A_R_ORD
        RPM_READ_ALL_ACTIVITIES
        RPM_READ_ALL_CONFIGS
        RPM_READ_ALL_NODES
        RPM_READ_ALL_ORDERS
        RPM_READ_ALL_POSVARS
        RPM_READ_ALL_RES
        RPM_READ_ALL_TOKENS
        RPM_READ_CONFIGS_W_TOKENS
        RPM_READ_ONE_CONFIG
        RPM_READ_ONE_ORDER
        RPM_READ_ORDER_BOM
        RPM_READ_ORDER_BOM_MUL
        RPM_READ_ORDER_SEQUENCE
        RPM_READ_ORDERS_FOR_POSVAR
        RPM_READ_POS4RS1
        RPM_READ_POS4RS2
        RPM_READ_RES_ORD
        RPM_READ_RES4POS
        RPM_READ_ROW_BITS
        RPM_REORG_HARD
        RPM_REORG_PARKED_ORDERS
        RPM_REORG_SOFT
        RPM_REQS_FOR_MATERIAL_2
        RPM_ROWIDS_FOR_WORKCENTER
        RPM_SESSION_SWITCH
        RPM_STORE_ACTIVITIES
        RPM_STORE_ORDER_SEQUENCE
        RPM_STORE_ORDERS
        RPM_STORE_POSVARS
        RPM_STORE_R_BITS
        RPM_STORE_R_ORD
        RPM_STORE_RESTR
        RPM_STORE_TOKENS
        RPM_TIME_LINES_CREATE
        RPM_TIME_LINES_DELETE
        RPM_TIME_LINES_READ
        RPM_TRANSPOSE_PV_MATRIX
        RPM_TRANSPOSE_TOKEN_MATRIX
        RPM_TRANSPOSED_CONFIGS
        RPM_UPDATE_ROW_BITS_TABLE
        RPM_WRKCINFO_DELETE
        RPM_WRKCINFO_MODIFY
        RPM_WRKCINFO_READ
      SAPTS
        SAPTS_ADAPT_SEASONALITY
        SAPTS_AGGMULT_TIMESERIES
        SAPTS_AGGSINGLE_TIMESERIES
        SAPTS_ASSOCIATE_CH
        SAPTS_CALC_DATA
        SAPTS_CALC_SNP_INFLOW
        SAPTS_CHANGE_CH
        SAPTS_CHANGE_FIX_DATA
        SAPTS_CHANGE_KF
        SAPTS_CHANGE_PT
        SAPTS_CHANGE_RELMODE
        SAPTS_CHANGE_SH
        SAPTS_CHANGE_TG
        SAPTS_CHRANGES_IN_AGG
        SAPTS_CLEAN_OBJECTS
        SAPTS_COMTEST
        SAPTS_CONS_OBJECTS
        SAPTS_COPY_DATA
        SAPTS_CREATE_INCONS_OBJECTS
        SAPTS_CREATE_NEW_LAYER
        SAPTS_CREATE_REGISTER
        SAPTS_CREATE_RELATION
        SAPTS_CREATE_SNP_RELATION
        SAPTS_CREATE_TIMESERIES
        SAPTS_DELETE_KEZ_TS
        SAPTS_DELETE_REGISTER
        SAPTS_DELETE_RELATION
        SAPTS_DELETE_SNP_RELATION
        SAPTS_DELETE_TIMESERIES
        SAPTS_EXTR_CH_GET
        SAPTS_EXTR_CH_SET
        SAPTS_EXTR_KF_GET
        SAPTS_EXTR_KF_SET
        SAPTS_EXTR_PT_GET
        SAPTS_EXTR_PT_SET
        SAPTS_EXTR_TG_GET
        SAPTS_EXTR_TG_SET
        SAPTS_EXTR_TSBUF_GET
        SAPTS_EXTR_TSBUF_SET
        SAPTS_EXTR_TSBUS_GET
        SAPTS_EXTR_TSBUS_SET
        SAPTS_EXTR_TSH_GET
        SAPTS_EXTR_TSH_SET
        SAPTS_EXTR_TSKF_GET
        SAPTS_EXTR_TSKF_SET
        SAPTS_EXTR_TSRLSNP_GET
        SAPTS_EXTR_TSRLSNP_SET
        SAPTS_EXTR_TSRL_GET
        SAPTS_EXTR_TSRL_SET
        SAPTS_EXTR_TS_GET
        SAPTS_EXTR_TS_SET
        SAPTS_GET_AGGREGATED_DATA
        SAPTS_GET_AGGREGATED_DATA_RIW
        SAPTS_GET_ALL_DATA
        SAPTS_GET_ALL_DATA_RIW
        SAPTS_GET_DATA
        SAPTS_GET_DATA_RIW
        SAPTS_GET_INITIAL_DATA
        SAPTS_GET_REG_OBJECTS
        SAPTS_GET_TS_INFO
        SAPTS_GET_TS_INFO2
        SAPTS_INITIALIZE_DATA
        SAPTS_OBJECTS_BY_CHREF
        SAPTS_OBJECTS_BY_KFREF
        SAPTS_OBJECTS_BY_TGREF
        SAPTS_OBJECTS_GET_ALL
        SAPTS_OBJECTS_IN_AGG
        SAPTS_OBJECTS_QUERY_STATE
        SAPTS_QUERY_OBJECTS
        SAPTS_READ_CH
        SAPTS_READ_KF
        SAPTS_READ_PT
        SAPTS_READ_SH
        SAPTS_READ_TG
        SAPTS_REDISAGG_DATA
        SAPTS_REGISTERS_GET
        SAPTS_RELATIONS_GET
        SAPTS_RELATION_GET_DETAIL
        SAPTS_REPLACE_COMPLETE_TSKF
        SAPTS_SET_DATA
        SAPTS_SET_DATA_RIW
        SAPTS_SET_INITIAL_DATA
        SAPTS_SET_UNIT
        SAPTS_TIMESERIES_GET
        SAPTS_TRACE_FILTER
        SAPTS_UPDATE_TIMESERIES
==================================
Installation successfully finished
==================================
Enable user LC1ADM
OK
OK
liveCache LC1 successfully started.
Mon 10/15/2007
03:00 AM
The Problem we face is before this problem happen we created planning version name 000 , when we open the product view system says planning version is not available
please advise me
Thanks
Raj

SCM5.0 Live Cache issue

Hello,
I am a newer from SCM5.0. I have 2 questions regarding live cache for SCM5.0.
1) if I want to run SNP or PP/DS, the live cache is necessary. that means, we MUST install live cache for APO planning run.
2) From now on, no 32 bit live cache version for SCM5.0. I can just install 64 bit live cache version for SCM5.0. right?
Could anyone give me some comments on the 2 issue? thanks in advance.
Best Regards,
Karl

Hi Karl,
1. In APO whatever runs you take there should be liveCache. The data will be refreshed from database to livecache and is accessed.
In APO data is stored either order series or time series.
2. Yes you have to install 64 bit.
Regards,
Kishore Reddy.

Why we need live cache along with RDB in APO

Hello Expert,
I recently entered to APO module so want to know about live cache and why we really need comparing to RDB and what RDB cannot do that live cache can do?

SRS,
Functionalities are pretty much the same. LiveCache is a relational Database, built on MaxDB.
Advantage of LC is that most of the data is stored in memory rather than on disk storage. Data access and retrieval is substantially faster from memory than from disk storage.
Best Regards,
DB49

APO Live cache

Hi guru's,
         i just wanted to know what live cache means? How do we mention live cache? If an APO person says that "data is stored in live cache " what does it mean? How do we extract data from live cache?
I will be very thankfull to you all if i get this answers.
Thanks a Lot
Regards,
Raja

Hello Raja,
For SAP liveCache documentation in English:
http://help.sap.com/saphelp_nw04/helpdata/en/f2/0271f49770f0498d32844fc0283645/frameset.htm
( please see the liveCache terms 'Data Cache' & 'OMS Data' )
As you know objects in liveCache stored in the class containers can be
accessed and manipulated only via LCA ( liveCache Applications ) routines
( Database Procedures ) which are methods of LCA ( COM ) objects.
The registration of the LCA routines is done automatically when the liveCache
is started by the LC10, check the lcinit.log file.
The shared ( dynamic linked )procedures in the LiveCache are written in C++
and shipped to the customers as binary shared libraries ( dynamic linked )
(COM-Routines or LCA-Routines) together with the LiveCache. The original
C++ source code of the libraries is not generally available to the customers.
You can get the complete list of the stored procedures using SQL Studio
(shipped with the LiveCache):
just connect to the LiveCache as Standard livecache user ( SAPR3 or SAP<LC-SID>
By default ) with the password 'SAP'( default ).
You can read the Config-Files ./sapdb/<LC name>/db/sap/xxx.lst
or check the information in the lcinit.log file.
Names of all registered procedures, which have been called from ABAP, you can find
executing 'lc10' transaction on your SAPAPO system:
LiveCache Monitoring ->Problem Analysis -> Database Procedures .
If you need to see the interfaces of the procedures, you may use 'se80'
transaction and navigate in the Development class '/SAPAPO/OM'.
The transaction /n/SAPAPO/OM16 is provided by SAP to get
information about data stored in the LiveCache. If you
would like to get your own views, you should write a special report
in ABAP using "/SAPAPO/OM"-development class functionality.
'/SAPAPO/OM16' itself calls a bunch of OM- functions to read
data from the LiveCache, e.g.:
/SAPAPO/OM_RESOURCE_GET_ALL
/SAPAPO/OM_ORDER_GET_ALL
/SAPAPO/OM_SETUPMATRIX_GET_DAT
/SAPAPO/OM_STOCK_GET_BY_UID
You can get more information about liveCache and LCA object at the following links:
Service.sap.com/scm ( -> mySAP SCM Technology )
Service.sap.com/liveCache
Thank you and best regards, Natalia Khlopina
Message was edited by: Natalia Khlopina

What is the significance of Live Cache in demand planning ?

Hi all,
Can anyone explain me significance of live cache in the demand planning. What are the issues will turn up for live cache if it is not properly maintained?
Thanks
Pooja

Hi Pooja,
SAP has come up with Live cache concept for storage and most important, quick and efficient processing of transactional data. Its a layer between data base and GUI and even the search methods and storage space has been optimized due to its structure. In DP it is used for storage of time series data whereas in SNP it can store both time series and order series data.
Regarding your second query, it is recommended to have Live cache consistency on a periodic basis for synchrinising data between LC and database tables. You can face many issues due to LC inconsistency as incorrect time series generation, Transactional data discrepancy, COM routine errors during background processing etc.
Let me know if it helps
Regards
Gaurav

BW reporting from APO live cache

It has been 4 years since I have worked on a BW/APO project. Back then, I know that in APO you could backup live cache and then use the backup as the datasource for reporting in BW. Is this still the same or can you go directly against live cache now.
Thanks,
Dean

Hi Somnath,
Can you pl. give me the reference where running reports from internal APO-BW directly is recommended by SAP?
We have a similar situation with our client. It is possible to do reporting from APO cubes directly, but we are not sure since I found this in once of the SAP presentations
SAP recommends for customer to prepare separate systems for APO and BW.
Reasons
The APO system will be tuned for optimal APO functionality performance such as calculating forecasts in demand planning or deriving ATP values
The BW system will be tuned for optimal query performance in order to return results in a timely fashion.

What is meant by set up matrices ,atp matrices ,simultion version in live cache

what is meant by set up matrices ,atp matrices ,simultion version in live cache
Please help

THere are overall versions, and you can copy these and view the data in both SNP and PPDS (or DP as well)
then there are specific simulation versions with the PPDS tool.
See below link.
http://help.sap.com/saphelp_scm70/helpdata/EN/e1/8e51341a06084de10000009b38f83b/frameset.htm
So it saves a version of the production orders. Saves it in livecache and then can either be used or discarded.
j

LIve cache and why BW in apo

helo sap masters
could u plz help me out ..
1. Why should we maintain LIVE Cache separately despite of having in APO tool.???
2. Why should we have BW in APO too in spite of having BW tool seperately ??

Hi Dallyanusha,
1) Livecache is a special inbuild device in APO which does
speedy operations especially during optimisation and retrives
data quickly from database. For effective functioning of
planning activities, livecache in APO is must.
2) BW in APO serves and stores information on business
master data and transactional data objects and can be
extracted to create various queries and reports. This is
more useful during demand planning
Regards
R. Senthil Mareeswaran.

How to identify records deleted in APO live cache while loading into ODS

I am doing FULL load of data everday for APO DP from APO live cache into a ODS. Users at time delete some data from DP planning area. This subsequently needs to get deleted from the ODS.
How can I identify records that were deleted by the user and mark them as deleted in the ODS?
Note that the extractor only returns records that exist currently in the Live Cache.
Thanks for your help.

Hi Jr,
   I need your help again to fix the below problem please.
   I have a query on Infoset with two ODS and linked with BillingDoc which exists in both ODS.
   Sales Doc & Billing Doc Fields are in ODS1 and Billing Doc & Amount are in ODS2.
If matching BillingDoc is found in ODS2 then report should have Combined data (Sales Doc, Billing Doc & Amount), otherwise just Sales Doc & Billing Doc from ODS1 only.
Tried Inner Join and it gets only matching records.
Left Outer join with ODS1 on left side or Right side doesn't get the requested report.
I found in SDN that with Left Inner join we could get all data from ODS1 and Matching data from ODS2.
How could I get my requested data, PLEASE ?
Thanks,
Venkat.

Is Live Cache System refresh required with APO refresh

Hi APO Experts:
   I have a question concerning the refresh of an APO QAS system. \
   If I have an APO system refreshed from a production APO system, is it required that I refresh the Live Cache as well?
   We have just refreshed our APO QAS system from production and I was thinking it could be easier to just reinstall a new database for Live cache in QAS then refreshing it from production Live Cache......
Please share your words of wisdom. Thanks! - Will S.

Hi Will,
I think LiveCach refresh with production is not required. But you need to down the LC and then start it.
LiveCach is a temporary storage area and it will refresh with database.
I suggest please post this in BASIS forum.
Regards,
Kishore Reddy.

What is Live Cache in APO

Similar Messages

Maybe you are looking for