Planning cube request status yellow

My transaction cube all the while has requests of reportable status. Now, new requests generated by planning processes are in yellow status (QM & technical).
I would like to find out how to tell what is wrong with the yellow requests or is it that this is due to auto maintenance is switched off. How to tell?
What is the impact if I switch it on as green?
Pls advice. Full Points will be awarded to the first clear answer.
Regards
Pascal Gabin

As mentioned - the yellow request is simply an open request, which means if users enter data it will go in that request.
It is important to use the Most Recent Data variable on the Request to make sure the open request gets included in any queries.
You can close the request, turning it green, and then a new open request will be created when the users enter more data.  The system automatically does this whenever the row count in the Request exceeds a certain threshold (sorry - drawing a blank at the moment as to what the threshold is)

Similar Messages

  • REQUEST STATUS YELLOW WHILE MONITOR STATUS GREEN - BI7

    Hellow,
    I try to load data with 0CO_OM_OPA_1, 0CO_OM_WBS_1 into Z cubes which are similar to the business content cubes 0OPA_C11 and 0WBS_C11 respectively.
    ETL is BW3.5 (transfer rule and update rules). When I look at the request in the monitor, I see that everything is green but the request status is yellow and not available for reporting. I can change the status to green manually but this is not a good solution for me.
    By the way the same load works well with te standart cubes.
    I use BI7 but I use BW3.5 business content.
    What could be the reason for such problems?
    Regards,
    Hadar

    Hi Hadar,
    We have exactly the same proble. Have you found a solution to it? I'm using Datasource 0HR_PT_2 to load data into Infocube ZPT_C01 (a copy of 0PT_C01). The monitor of the infopackage is green. There are no errors whatsoever. The status for the request in the Infocube>Manage is set to yellow and the data is not available for reporting. I can set it manually to green, but as you said yourself, it'd be nice to have an automated wway of doing this. Is there any way around this problem?
    Thanks
    Michalis

  • Request status yellow and no records pulled

    Hi ,
    I am working on a newly installed BI system.I have installed 0figl_c10 cube and respective flow.The data source is 0fi_gl_10 which contains 0.1 million records in R/3 trans RSA3.When i try to pull the data nothing is coming into my system except the yellow status of the request with '0' records.
    Can you suggest how we can resolve this considering that its a newly installed  system.
    Thnaks
    Sri

    Check out this thread also [/message/8815574#8815574 [original link is broken]]

  • Plan Cube Load Plan Mode - Green Yellow Request

    When planning, the request status remains Yellow during all changes and functions. If I change the cube to load mode then back to plan mode, this request will turn green and a new yellow request appears. My planning application will have many planning functions and data input, and I would like to be able to create a new request for each Planning function for ease of troubleshooting/repair. Is there a standard functionality to do this?
    I have found I can create a process chain which will switch to load mode then back to plan mode, and can execute this process chain via the web template, but was wondering if there was a better method to doing this.
    Thanks!

    Hi,
    please take that e.g. saving the plan data is only allowed if the cube is in plan mode. That means as soon as two planers are working with your application there is the possibility that the both want to save data at the same point in time. Of course they can not work on the same data set, because the locks will prevent this. But it is possible that they want to save the data at the same time. This means in your case, that the first user sets the cube to load to close the request e.g. by using a planning function and the second user is getting an error message, because the cube is in load mode and can not be planned right now. Do you really want to run in this situation? I would not do it.
    If yes, you may create a customer planning function and switch the cubes. Function RSAPO_SWITCH_BATCH_TO_TRANS and RSAPO_SWITCH_TRANS_TO_BATCH are able to do switch.
    Hope this helps ...
    Regards Matthias Nutt
    SAP Consulting Switzerland

  • Request Status Red

    After data load from ODS to Cube request status is RED.But data successfully transfered and validated the data,exactly it matching.No where I am getting log also.What could be the problem.But forcibly made it to green.But in production i cant change the QM status.Please valuable inputs
    Rajesh

    Hi,
    If it happens only for this target, go to Mange screen ---> Environment (From Menu) ---> Automatic Request Processing ---> Tick the checkbox that Set Quality Status to OK. This will ask a transport request, collect this into TR and move to Quality and Production.
    If this happens for all systems, make the Extraction Monitor settings in SPRO.
    Hope this helps,
    Regards,
    Rama Murthy.

  • T-cube request id blank

    Hello Friends,
    Please could you share with me , under what circumstances can a plan cube request id be blank?
    thanks!!
    regards
    YHogan

    I recalled the answer.

  • Request in Yellow State in Delta update cube.

    Dear Exprts,
    In request , no. of transfered record is 73260 &  added record in cube 73212 with yellow status. Everything O.K. but in Data package  2  in update rule it has  tranfered only 16247 out of 16295. ( this is same diffrence of number of records as in cube ) .
    PSA request is also in yellow state.
    Regards,
    Anand Mehrotra.

    Dear experts,
    Thanks for reply.
    In R/3 & BW  , it showing status job is finished . But  PSA request  is also yellow state.
    In transfer rule ( Data package 2 ) no of tranfered record is equal to added . But Update rule it is different green status.
    how to find out   these records in update rule.
    Regards,
    Anand Mehrotra.

  • Data requests in planning cube

    Hi Friends,
    I like to find out from you how can I delete from the cube data I loaded into a planning cube via planning activities given that the cube only creates new request after n thousand records have filled the request.
    In short, how can I manage the changes I introduced, for example, delete the loaded data to undo?
    regards
    Michael

    Hello Micahel,
    There is one more easy option to delete plan data without having the need to close any open requests. BEWARE .. deleting data using this method will be difficult to undo once saved.
    If you can identify the exact subset of data that you want to delete, you can create a planning level which has all the characteristics and key figures. Create a function of type delete.
    You can then set the selection criteria in the planning level and delete the data. In most cases, we have restricted the access to this functionality to one or two super users only.
    Hope this helps.
    Sunil

  • STATUS YELLOW FOR REQUEST

    Hai all
    I am getting status yellow for request in bi after scheduling info package ( after migeration of data source)
    and in short dump of dataware house work bench I am getting following error : CONNE_IMPORT_WRONG_COMP_TYPE
    EXCEPTION :CX_SY_IMPORT_MISMATCH_ERROR
    AND TEXT OF ERROR AS ( ERROR WHEN ATTEMPTING TO IMPORT OBJECT " HIST2 " )
    THANKS
    CHAITHANYA

    Hi,
    Check is there any Start/Individual routines(ABAP) are there? Usally i occurs when exception raise.Try to debug the update rule solve your problem.
    Regards,
    Saran

  • Request status in infocube is always in yellow status..

    Hi Friends,
    We are loading the data from 3 ODS to one infocube but all the requests from ODS to infocube is always haivng yellow status ( even though load is completed without any errors). We are manually changing the status to Green.
    Any suggestions regarding this problem...
    Thanks in advance

    Symptom
    All requests in InfoCubes have the QM status 'yellow traffic light'.
    Solution
    In the InfoCube administration in the menu
    'Environment -> Request handling...'
    activate the flag 'Set quality automatically' on the popup 'Maintenance of the automatisms'.
    This flag was of no importance before BW Release 2.0.
    This flag is interpreted actively as of BW Release 2.0. For InfoCubes where this flag is deactivated, every request must be set manually to green (available for reporting) or red (incorrect) by a QM action.
    As a result, the individual request can have a different status independent from its monitor load status in different InfoCubes.
    After upgrading from BW1.2B to BW2.0, the flag is interpreted, but is not set for any of the old InfoCubes.
    Therefore data, including old data, is not automatically visible in reporting, if it is not rolled up or compressed.
    In order to accomplish this, you can either activate the flag 'Set quality automatically' or set every request manually to green (administering the InfoCube on the 'Requests' tab in column 'QM status of the request after update').
    This is a button column that only affects the status of this request in this InfoCube!
    By setting the QM status in the monitor for the load log of this request you can set all QM statuses of this request in all updated InfoCubes simultaneously.
    If you change this flag, you choose button 'Refresh' in the tabstrip 'Requests' so that the flag will interpreted and the requests are set to 'Green' in the InfoCube and thus displayed in Reporting.

  • Request Status Stay Yellow

    Hi Expets,
    I am using load 0HR_PT_2.
    Because the load gets warning in the source system the request stay in status yellow
    (HR say all the data is good)
    In the Details tab of the monitor under Extraction i see the warning
    "warnings have appeared when extracting data" (message R3 401)
    And i have to change it to green every morning (because all the data is in received in to the BW)
    how can ignore the warnings or chagne it to green automaticly?
    Or what else can i do?
    Thanks and BR,
    Or.

    Hi,
    In the DTP on the extraction tab you can set the DTP extraction mode to ignore warning and make the request status as green. Once you do this setting your request will become green automatically.
    But I don't know if there is any similar setting in BI 3.5.
    Regards,
    Durgesh.

  • Unable to manually set the BW request status from hanged yellow state

    Hi All,
    We were running a BW upload when it failed due to some ABAP dump. The request remained in the status yellow.
    We tried to manually set the status to red or green in RSA1--> manage (infoprovider)
    This did not allow me to reset the status there.
    I searched the SDN and found this blog: http://scn.sap.com/community/data-warehousing/netweaver-bw/blog/2013/10/23/deleting-dtp-requests-when-the-dtp-step-is-hanged
    But in our case the table : RSBKREQUEST shows "USTATE" and "TSTATE as "0"(zero).  I can reset the status only when it shows 5. So running RSBM_GUI_CHANGE_USTATE in SE37 to reset the status to "0" (zero) is not an option here.
    Iam sure others would have come across this situation before. If you could throw some light on how to reset the BW request status to RED or Green so that I can restart the load again.
    Your help is really appreciated.
    Thanks
    Manmath

    Hi,
    please check the below tables have your DTP request ID.
    Note: Be aware the deleting the request form the data base tables
    RSBKREQUEST
    RSREQDONE,
    RSREQICODS,
    RSICCONT
    Thanks,
    Phani.

  • Creating aggregate based on plan cube

    Hi,
    For the standard baisc cube, we can use the aggregate to improve the query performacne.
    and when the new request comes, it will be ready for reading only after this request is rolled up to aggregate.
    Now I create a aggregate and do the initialzation fill-up for this aggregate, all the requests with green status have been rolled up to the aggregate. There is no any problem.
    but I get one quesion here, for the most updated request, it is usally with yellow status because this cube is ready for input. and this yellow request can not be rolled up to aggregate until it is turned to green. But from our testing, the query can read the required data from both the aggregate and this yellow request. that's to say, it seems the query based on this plan cube can summarize the data from both the aggregate and this yellow request.
    Is there anyone can confirm our testing is correct and it is the specific property of the plan cube?
    Many Thanks
    Jonathan

    Hi Jonathan,
    the OLAP processor knows whether requests are already contained in an aggregate or not; depending on the actualdata setting (cf. note 1136163) the query also is able to read data from the yellow request; this is automatically the case for input ready queries.
    In fact, even the OLAP cache may be involved to read the data, cf. note 1138864 for more details.
    Regards,
    Gregor

  • Compression in a Planning cube

    I was trying to compress 2009-2010 data in a planning cube and when i collapse the request it got csheduled but the compressio  didnt happen.
    When i look at the logs of the batch job it says that -
    No requests needing to be aggregated have been found in InfoCube DE_RBQTPL
    Compression not necessary; no requests found for compressing
    Compression not necessary; no requests found for compressing
    Job finished
    Can you please help me in resolving this issue.
    Thanks,
    Sravani

    Please check that all the request are loaded properly
    into the info cube.
    Is there any yellow request in the cube?.
    Then wait for some time and two the compression.
    Thanks,
    Saveen

  • Error in delta loading from a planning cube

    hi all,
    I am using a delta load from one planning cube to another.When the changed records are of a magnitude of 100 then it is successful but when the records are of magnitude of 100000 then it stays yellow with no data records sent and eventually fails.the packet size is 20000.
    any help is appreciated.

    Hello Ajay,
    Have you checked that your Request is closed in the planning cube? FM RSAPO_CLOSE_TRANS_REQUEST will do it
    It is a customizing issue to tell the infopackage to end "green" when it has no data.
    Transaction Spro ==> SAP Netweaver ==> SAP Business Information Warehouse ==> Automated Processes ==> Monitor Settings ==> Set Traffic Light Color. There you have to set the Traffic light on green if no data is available in the system.
    Hope that helps
    best regards
    Yannick

Maybe you are looking for