on 12-21-2006 1:35 PM
We have installed APO Livecache with SID other than LCA and I'm being told that it has to be LCA always ?
Is this true ?
If it is, why is the install tool gives the option to pick a SID ?
Or is there a config setting in SAP to change this default setting ?
Thank you
Ravi,
the liveCache itself can have a name other than LCA but the connection names (DBCON) must be LCA and LDA and, as of SCM 5.0, additionally LEA.
Regards
Jörg
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Ravi,
yes, the database connection has always to have the name LCA. Furthermore also the database connection LDA and as of SCM 5.0 the database connection LEA has to exist in an SCM system. With the transaction /SAPAPO/OM13 (tab checks) you can check whether you have set up the connections properly.
Regards
Olaf
Hello Ravi,
Please check the SAP Note No. 829963.
Please review the documents at service.sap.com/scm ->mySAP SCM Technology:
"mySAP SCM Technology" & "liveCache overview " .
In case of a new installation of the liveCache/LCA, you have to create the connections LCA/LDA/LEA
as described in the installation documentation for the SAP liveCache technology - using
Transaction LC10. For example, review the document at
service.sap.com/instguides -> mySAP Business Suite Applications->
mySAP SCM -> Using SAP SCM 5.0 Server->
"Installation - SAP liveCache Technology " in the section
"Common Post-Installation Activities" - "Setting Up the Connection to the liveCache Instance".
Please review the information at service.sap.com/liveCache ->Release Information ->
SAP LC/LCAPPS 5.0
******
You could run /n/sapapo/om13 -> checks & see the status for LCA & LDA & LEA
connections. If the connection is marked by the red semaphore => check errors in /nsm21.
You could run the test connection for LCA & LDA & LEA in db59 transaction and review the results.
****
Please open the OSS ticket to the component 'BC-DB-LVC' or 'BC-DB-LCA' if you have further
questions on this issue.
Thank you and best regards, Natalia Khlopina
Hi Natalia,
Another question, it's still not clear what is LCA and what's is LDA. I couldn't find a clear definition with SAP documents.
for LEA it's clear stat in the note: 829963
As of Release 5.0, liveCache Applications provides a new function which is the so-called lock server. Just like with the Web AS enqueue server, applications can get locks and thus protect objects of the application against parallel changes. In contrast to the Web AS enqueue server, it is possible to lock multi-dimensional selection areas - not just individual objects (for example cost center 200 to 299, and plant 0001 to 0003). This function is used (optionally) in the Business Information Warehouse and (always) in the SCM/APO application Demand Planning. In order to avoid interactions between the new lock server function and other Demand Planning functions within Demand Planning, the new "lock server" function is addressed using the third liveCache connection. For more information on the lock server see Note 816730.
Hello Denny,
The LCA & LDA connections need to be setup correctly in LC10 ->
integration, and they should be pointed to the same liveCache instance, which is connected to your system!!
As you know as of Release SCM 5.0 the LEA connection to the liveCache will be created and you could get answer on the question " What is this third LEA connection used for?" in the SAP notes 829963 & 816730.
The LDA connection to the liveCache is used for the ATP functionality on the APO systems. Also the LDA connection is used by the liveCache application test reports ( //om03, for example ).
All other applications are using LCA connection. And as you know pro liveCache installation guide the LCA connection has to be used for start/stop/initialize and monitore liveCache on your System.
Thank you and best regards, Natalia Khlopina
User | Count |
---|---|
92 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.