Skip to Content

Problem in Planning Cube Requests

HI All,

In the Planning Cube when ever we save data, some new requests are being created without turning the old requests to green.

This considerably increase the number of requests as we save the data in the cube.

Kindly let me know if any one has encountered the same issue and suggest any feasible solution.



Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Dec 16, 2008 at 07:41 AM

    Hi ,

    When you enter plan data ( less than 50000 records )from report, A request will be added to your cube and this will be in yellow status by default.U wil hv to make it to green manually.

    If you enter more than 50000, request will turn to green automatically.



    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 16, 2008 at 08:33 AM

    Yeah i can understand that it only turns green after specified no. of records.

    But the problem is first i am saving 5000 records to the cube. So it creates a request with a yellow sign. Then i post amother 10000 records. for this it will be added in the existing prev request right. But instead it creates a new request with a yellow sign. Totally there are 2 requests now in the cube though the records are only 15000 which is less that 50000.

    if i again save it another set of 5000 request a third req is added and so on ...

    Kindly help me in this issue.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member


      I have a doubt on this. Isnt it supposed to write the data in the same request?

      Ideally, data requests in transactional cubes stay open until the number of records in the data request exceeds 50,000. When an application is writing data into the request and the limit of 50,000 records is exceeded, the data is stored and the request is closed. (Thus a request can actually contain more than 50,000 records.

      Example: If a request already contains 49,900 records, and someone is using a BPS layout to store 500 records at once, then all the records are into the same request of this InfoCube so that the request contains 50,400 records). As soon as the number of records in this data request exceeds 50,000, this request is closed and the request can be rolled up into defined aggregates if any exist (in asynchronous mode).

      Physically, the design of these InfoCubes may differ with respect to indexing and partitioning (depending on database). For an Oracle DBMS this means, for example: no bitmap indexes on the F fact table and no partitioning of the F fact table by packet dimension (initiated by the BW). Rollup and definition of aggregates, compressing, and so on, is still possible.

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.