Regarding Yellow Request Status in InfoCube

Hi All,
I am trying to load the data from DSO to Info Cube. Here DSO is of 7.0 type & InfoCube of 3.x type. Once the data is updated into Info cube, the request is still found in Yellow status. when i checked the monitor of the request, in the status tab all the status are completely green but in the infocube it is still found in yellow status. Also the "Request is available for Reporting" icon is not appearing.
What is the possible cause for the request to remain in yellow status in InfoCube even though the monitor shows Green status. I tried reloading the data completely but still my problem is not solved. Please suggest methods so that request should automatically turn into Green status.
Points will be awarded as per SAP forum rules.
Thanks in advance,
Rajesh

Hi Experts,
I have come up with a new issue.
When I do a full upload from DSO to Infocube, the request in Infocube would remain in yellow status. When i check the monitor status it was completely Green. so in that case i changed the status of request manually to Green as suggested by forum experts.
When I do a INIT upload from DSO to cube, still my request in Infocube would remain in yellow status. Again i changed the status of request manually to Green. But the problem is when i check the monitor of the request, under 'status' tab the status is Green but under 'Details' tab Overall status is still in yellow status. The sub-option 'Databasis (requests) : Not yet finished' is also in yellow status. what is the possible cause for this? how to overcome such problem?
Thanks,
Rajesh

Similar Messages

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.

FM to read yellow status requests from transactional InfoCube

Hi,
I am using the FM RSDRI_INFOPROV_READ to read data from the transactional InfoCube. My problem is that my code using this FM should be able to read data requests that have the yellow status for the transactional InfoCube.
My code using this FM is able to read data from the green requests only but not the yellow requests. I was told in BPS, the yellow requests should turn green automatically after 50K of records have been queue up and ready to be turned green by itself.
Has anyone come across this and help me solve this issue of reading data using FM RSDRI_INFOPROV_READ to read yellow request data. Is there another FM to read both the green and yellow requests?
Please advise. Thanks
RT

Hi Rob,
The function module mentioned by you is correct and it will read the yellow requests please try this, by default the parameter i_rollup_only is set as true set it to false (blank) while calling the function module.
Please see the attached code
CALL FUNCTION 'RSDRI_INFOPROV_READ'
   EXPORTING
     i_infoprov             = p_infocube
     i_th_sfc               = t_sfc
     i_th_sfk               = t_sfk
     i_t_range              = lt_range
     I_PACKAGESIZE          = p_pksize
     i_rollup_only          = rs_c_false
   IMPORTING
     e_t_data               = <fsl_data_read>
     e_end_of_data          = w_end_of_data
   CHANGING
     c_first_call           = l_first_call
   EXCEPTIONS
     illegal_input          = 1
     illegal_input_sfc      = 2
     illegal_input_sfk      = 3
     illegal_input_range    = 4
     illegal_input_tablesel = 5
     no_authorization       = 6
     ncum_not_supported     = 7
     illegal_download       = 8
     illegal_tablename      = 9
     trans_no_write_mode    = 10
     inherited_error        = 11
     x_message              = 12
     OTHERS                 = 13.
Hope this was helpful.
thanks

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 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.

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)

How to set quality status of a request in an infocube by a function module

Hi folks,
in the maintenance of an infocube you have the possibility to go to a dialog called "maintenance of the automatism". That dialog allows you to set a flag therewith the quality status of a processed request is set automatically to green.
Does anybody know how to do that with a function modul or which tables have to be updated in order to do that by a litte ABAP?
Thanks+Cheers, Thomas

Hi Bhanu,
thanks for that one, pretty helpful.
Think of the following scenario:
1. untick the automatic setting of the quality status
2. load 4 requests into the infocube
3. once last request has been loaded tick the automatic setting of quality status
would that mean that once the status flag is ticked all 4 requests become available for reporting?
Cheers, Thomas

Remove reporting status of request ID In Infocube

Hi,
We require some urgent help on following issue
We have planning data request APO_* In Infocube and they are already in reporting status and rolled up aggregate status in the Infocube.
We can not delete the request
We can not reconstruct.
We can not change query,we can not put filter on request ID.
Is there any way we can remove it out from reporting status or take it out of aggregate.Its bit urgent .Is there any control table we can change the status for time being?
Its bit urgent.
Thanks and regards

Try dropping the data from the aggregate and rebuilding it later, after you dealt with the request. Have you updated the request into further data targets? If so, then you need to delete those requests as well. With the aggregate data delete and further updates deleted, you should be able to delete the request, change data in the PSA and then reapply/reconstruct it back into your data target.
Be careful though ... if the aggregate has a huge amount of data, it may take a long time to rebuild. Also, if you transformation/transfer structure has changed, you might not be able to reconstruct the request.
Good luck & Don't rush through this ... you could actually make things worse.
Brian

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.

Request Status not Activating

Dear All,
I have created Datasource and DSO and flat file and also created DTP. If i request perticular request id , its not activating. request status not activating.
With Regards,
Baskaran.

Hi Baskaran,
Follow these steps.
Do the loading process as you are doing i.e. using Info package load to PSA, then using DTP to DSO.
Then after loading data, you go to manage. Then Select your green request and then click activate.
A new window will open. There your request will be green. Again select it and click on start (do not click on stop).
Then you will find refresh button there. Click on it. Your green request will turn yellow. Now go on clicking refresh until your request disappears from there. After that close the window.
Then again click on manage. Click on refresh. Now select active data. Your data will be displayed.
Hope this helps.
thanks,
rahul

InfoPackage error message "Subsequent update (requests) : Status unknown "

After running an InfoPackage the status is set to green, but when you look at the Details tab you see an error message "Subsequent update (requests) : Status unknown " and "With DTP in InfoProvider ZHRPYO00 : Further processed " under it. We did not used to get this error message and don't quite understand why are we getting it now. Could someone explain, please?
Thanks!
Luda

Hi,
Usually this error could be while loading the DSO or loading DSO first and then to other infoprovider.
Error message tab at the monitor should give you clear error message where it went wrong. check this tab.
some time while activating the data this may fail for the DSO object. or some time due to authorization problem to load the data automatically from the DSO to infocubes.
If possible let me know what is error message.
Regards,
Vishwa.

Request Status for Master Data Attributes Load

Dear All,
We are trying to load attribute master data and volume of which is relatively huge around 10,000 records.
We are facing challenge while updating attribute data from master data info object , the load status remains in yellow status and when we went to details screen it states that data is transfered to transfer rule . ( it has been loaded successfully in to PSA).
Could anybody please give some hint on this challenge ??
Regards
Kapadia

Hi Paolo Siniscalco,
You are right, as number of records are more , i have chosen update of "Only PSA" and then "Subsequently in Data Targets".
I tried other option also which is infopackage schedule "Execute in Back ground" and
"Request batch process runs untill all data is updated in BW". And process went in to infinite loop.
Some how i am not able to track out why the request status is not changing .
Regards
Kapadia

Possibillity to close yellow request with ABAP?

Hello experts,
is there any possibility (function module, program, ...) to close the yellow request of a transactional cube ? The reason why we need this functionality is to load all data from our BCS cube to another cube during the day via process chain. This means that we aren't allowed to switch the BCS cube from transactional to normal and back, which would also make the yellow request green.
Any ideas?
Many regards
Martin

Please follow the steps to make the request Red .
If the same you want to include in the Process chain and automate the process you can incude a process type which has a ABAP code attached to it .
Follow the below procedure to make yellow request to RED:
Use SE37, to execute the function module RSBM_GUI_CHANGE_USTATE
From the next screen, for I_REQUID enter that request ID and execute.
From the next screen, select 'Status Erroneous' radiobutton and continue.
This Function Module, change the status of request from Green / Yellow to RED.
Once it is RED, you can manually delete that request...
Assign marks is the best way to appreciate help

Deleted Red Request Reappears in Infocube

Hi all,
We are facing one peculiar problem in which, When we delete one Erroneous request from Infocube, It gets deleted. But, again going to manage and if we check, this request reappears. We deleted all the data from Infocube. We checked Job log which shows that, Request is deleted. Still that request appear in Infocube. Please help us to solve the problem
Thanks and Regards,
Harpal

Hi,
Through SM37 select the job and stop it...it won't stop if it running from long time...for long running job go to SM50 see the process running from your ID....there could be more then one process running ...one is for your session in the system and you cannot kill that....check for the other one and go inside the log to see if it is the right one ...which you want to cancel....just select the process and in the top left you have the option to cancel without core....
In BW, u could do that by forcing the STATUS to RED Signal.
You have to stop the load in the source system if u r loading from R/3 System, for that use transaction SM50 or SM51 to kill the process.
Hope this helps
Cheers
Raj

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

Regarding Yellow Request Status in InfoCube

Similar Messages

Maybe you are looking for