Skip to Content

Live Cache Performance issue using alternate Unit of Measure

Hello, we're experiencing significant drop in performance when updating / saving Time Series KeyFigure values in APO DP.

The problem seems to occur when users are switching to alternative UOM in interactive planning.

For example, when editing data on aggregate level with 850+ corresponding Characteristic Value Combinations(CVC) on the lowest level, saving 12 KF's takes:

- 15 seconds in Planning Area UOM(Unit of Measure)

- 795 seconds in Alternative UOM

With persistant aggregates defined, it is having little impact on performance.

From Application server perspective, we're seing that 99% of the time is spent in LC stored procedure SAPTS_SET_DATA (which invokes LCA functionality), but have no further visibility as to what is happenning inside the LCA.

We're looking for any suggestions on how to trace / debug what is going on inside LCA and how performance can be optimized.

More specifically we're trying to understand how LCA obtains product master UOM conversion factors:

- are these stored in livecache

- are these being passed to SAPTS_SET_DATA as a parameter (this seems unlikely)

- is LCA accessing OLTP (/SAPAPO/MARM table) directly

(any links on how stored procedure is processed will also be helpful)

Will surely reward points for helping us.

Thanks

Srinivas

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Posted on Jan 18, 2008 at 09:40 PM

    Hello Srinivas,

    -> You could use the DB analyzer to find the bottleneck in liveCache.

    For SAP liveCache documentation see the SAP note 767598 .

    Monitor the running application in /nsm50 to see if the most time spent during the LCA routine run.

    -> The liveCache didn't access the "OLTP (/SAPAPO/MARM table- "Units of Measure" ) directly".

    The application call the LCA routines to read or change the data in liveCache.

    As you know objects stored in the liveCache in the class containers can be accessed and

    manipulated only via LCA routines which are methods of LCA objects.

    The shared procedures in the LiveCache are written in C++ and shipped to the customers

    as binary shared libraries (LCA-Routines) together with the LiveCache. The original

    C++ source code of the libraries is not generally available to the customers.

    Names of all procedures, which have been called from ABAP, you can find executing 'lc10'

    transaction on your SAP APO system:

    LiveCache Monitor->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 LCA routine SAPTS_SET_DATA called from

    Function module /SAPAPO/OM_TS_DATA_SET, this FM called by ABAP from application. You could debug, and see the input parameter values, the output parameter values after the LCA routine call, check the runtime of the LCA routine.

    You could also review the Average runtime<ms> & Total Runtime for SAPTS_SET_DATA

    by executing 'lc10' transaction on your SAP APO system:

    LiveCache Monitor->Problem Analysis -> Performance -> OMS monitor

    You can get more information about liveCache and LCA object at the following links:

    service.sap.com/scm -> SAP SCM Technology

    &&

    service.sap.com/liveCache

    -> You could find the list of helpful transactions in //om00, and some of them were developed as

    tools for the LCA support to find the reason of the LCA issues.

    -> For the reported problem I recommend you to create the OSS message to

    the component 'BC-DB-LCA', therefore we could logon to your system via

    OSS and take a look closer on the issue.

    -> The provided information is not enough to get clear on the solution to the

    reported performance problem on your system. The application scenario need to be

    checked; may be you have inconsistencies, please check if the data are in the

    consistent status; check the SCM SP on the system, may be the application team

    has to improve the performance in the ABAP coding; check the liveCache/LCA

    builds, for example, see the 1089914, there are performance improvements in the new

    released LCA build for SCM 5.0.

    Thank you and best regards, Natalia Khlopina

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.