Request stays yellow

Hi all,
a DTP request with an attribute InfoObject target (time-independent) that has to handle duplicate record keys stays in yellow status. Only non-duplicate entries are transferred and nothing happens anymore. Why?
Many thanks in advance.
Best regards
Tobias

After a while the request turned to green status.

Similar Messages

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.

Request Status stays yellow after successful load

We recently started loading two infocubes from the same data source.
- The Monitor shows that the load completed normally with no errors.
- Manage on the first cube shows that the status is green and the data available for reporting.
- Manage on the second cube shows the data is not avaialble and the status is yellow.
There seems to be no problems with the load. I can manualy force the status from yellow to green and the data is available for reporting. But I don't want to have to manully change the status after each load. Any ideas on why the status stays yellow? Any thoughts on what I can do?
Thanks,
Chris

Nagesh,
Looks like your suggestion will solve this. It was not checked for the one that was staying yellow. It was checked for the cube that would go to green. I'll run a test then come back and award points.
Thanks,
Chris

In the MMC, the dispatcher stays yellow, with the status

Hi all,
In My Solution Manager system, In the MMC, the dispatcher stays yellow, with the status 'Dialog Queue Info unavailable'.
However, the system continues to run. Can you please help on this.
Thanks
suman

Hi,
for this problem, check SAP note 396309 and 72248.
Thanks
Sunny

BDocs stay yellow - status I02 Written to qRFC Queue (intermediate state)

We upgraded our system from SAP CRM 7.0 EHP3 SP3 to SP4.
Now all the BDocs in smw01 stay yellow. I can manually reprocess them, then they become green. There is no error message and there are no dumps in st22.
The CSA* queues are registered. The scheduler says "inactive" (and briefly goes to active when saving a business partner, product or transaction, as it should).
The CSA* queues relevant for each "stuck" business partner, transaction or product is in status "STOP".
There's a note, 1593693 - BDoc's in state I02, but it doesn't help. We don't have a problem with the number or load of the RFC processes (as far as I can tell), there is very little going on on the system, right now I am the only one logged on) and the queues are not in status READY, either.
MW_CHECK says "All post-processing steps are done."
GENSTATUS counts 0 errors or waiting.
MW_MODE is on, of course.
smw3_00 is empty (which it was before the SP installation, too).
The CRM is not connected to an ERP system, it sends búsiness partner and transactional data via the XIF adapter (via web services). Which, up to now, worked just fine.

I was given the solution: Use transaction smq2, search for CSA*, click on the queue, click the unlock button. That worked.

Request still yellow in manage screen after successful load

Hi ,
I have loaded the data into the cube .The load is init .Even thought the load is successfully load the manage screen shows request still yellow in color. I checked everywhere but did not find relevant setting.
Any help please.
Thanks

Hi,
Chk for any active job in SM37 still going on which is related to this load...
And then under details tab chk under extraction--->is the data selection ended or not?
And chk in the manage screen->Environment(in the menu bar)>Autoimatic request proceessing>set quality status to OK is checked or not?-> Chk this box and refresh....
If u chk all the things are in green and successfull u can manually turn the status into green in the manage screen....then auotmatically the reporting symbol comes if there are no aggregates...
rgds,

Request stays in Authorizing state even after approval

I've been trying to debug this for days now and it completely breaks my lab - until it fixes itself after some random time and then breaks again
I created a simple approval workflow which seeks approval from [//Target/Owner] when joining an Owner Approval Group. The request makes it to the Group Owner, but when the group owner approves the request, it stays stuck in Authorizing state and the user
doesn't become a member of the group. The WF also remains in Running status even after the request is approved.
I've seen some similar problems around on the internet, and all seem to suggest Exchange related issues. I don't have an exchange setup in my lab, but I don't think not being able to send an email would completely break the approval process. Besides, it
does seem to spring back to life randomly and it all starts working again before breaking - very intermittent.
I've been messing around with the PS WF activity (which I use to calculate custom approvers), but I have disabled that WF completely for now and I'm just using OOTB activities and approvers.
Any suggestions on what the issue could be (apart from exchange)? There are no errors in the event logs either, but there are loads of exchange related errors/warnings which are expected. Alternatively, is there somehow I can disable the "feature"
where FIM tries to send an email?
Thanks

Yep, the approval responses are generated but the request still stays in Authorizing with the workflow in Running state.
What makes this even more bizzare is the intermittent nature of the issue, it just seems to resolve itself after some time then break again.
One thing I have noticed is that the problem starts when I use my custom WF to add approvers to the WF dictionary - the first activity is a powershell activity which calculates the approvers and the next one is the OOTB approval activity which sends an email
to [//WorkflowData/Approver]. However, the PS script runs just fine, and the approver gets the request but after approval nothing happens (although approval responses are generated)

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.

How to delete request in yellow traffic light?

Hi experts:
I created one infopackage yesterday to load the vendor text from our DEV source system. Its update mode is "Initialize Delta Process". When I right click on the infopackage and select manage, I see this request is still in yellow and 'Request has a yellow traffic light in the monitor - Cannot be deleted.' And when I go to Data selection I got the information: "Init. select. for field name currently running in request ***".
Does anybody know how to delete the request still in running or in yellow traffic?
Another thing is when I double click on the infopackage a warning message will pop up with: " Assign a language field to IOBJ 0LANGU; danger of short dump". Do I need to take care of this warning?
Thanks to everyone for your time in advance~
Tim

Hi,
Make the request forcefully into RED and then delete it, you can do it in RSMO or goto Obejct and Manage and then Click on YELLOW color Ball and then it will popup one window there make to red and delete it.
The reasons for Yellow
Check the DataSource in RSA3, if it is working fine and able to see the data in RSA3, there is no problem in DS level, then checl the Mappings and any routines in BW for that DS, if this is also fine then check the below options.
See Dumps in ST22, SM21 also.
Check RFC Connection between ECC and BW systems, i.e. RSA1-->Source System->Right Click on Source system and Check.
You must have the following profiles to BWREMOTE or ALEREMOTE users.So add it. Bcoz either of these two users will use in background to get extract the data from ECC, so add these profiels in BW.
S_BI-WHM_RFC, S_BI-WHM_SPC, S_BI-WX_RFC
And also check the following things.
1.Connections from BW to ECC and ECC to BW in SM59
2.Check Port,Partner Profiles,and Message Types in WE20 in ECC & BW.
3.Check Dumps in ST22, and SM21.
4.If Idocs are stuck i.e see the OLTP Idoc numbers in RSMO Screen in (BW) detials tab see in bottom, you can see OLTP Idoc number and take the Idoc numbers and then goto to ECC see the status in WE05 or WE02, if error then check the log else goto to BD87 in ECC and give the Idoc numbers and execute manually and see in RSMO and refresh.
5.Check the LUWs struck in SM58,User Name = * (star) and run it and see Strucked LUWs and select our LUW and execute manually and see in RSMO in BW.
See in SDN
Re: Loading error in the production system
Thanks

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

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

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)

Getting 0 records request is yellow status past 1 day

hi
i am doing initialization , i run inforpackage i am getting yellow status, and showing 0-0 records past 1 day
ple let me know solution

Hi,
What does the extraction job log say in R/3 system....
Chk the log and provide the details...
And also chk the RFC connections, SM58, ST22 in R/3 system...
rgds,

SCSM 2012 R2 - Activities have been completed but Service Request staying In Progress

I have noticed that a number of service requests that are shwoing with the status as 'In Progress' have actually had all the related activities resolved.
Once the activities are all closed the request should automatically go to Compelted, why is this not happening on some of my Service Request????
tamrep

There were in deed some needing attention under activity status changed, but no errors showing in the log.
I re-ran them all and they succeeded so maybe this was it. Have you come across it before? I'll need to keep an eye on this.
There wasn't anything requiring attention under Service request Status changed, which i was surprised with.
tamrep

Dialog ABAP+Java instance fails to go to green (stays yellow)

ECC 6.0 SPS 13 (NW 17)
Win 2003
SQL 2005 (latest patch)
Using System Copy SR3
After performing a Hom system copy (from PRD) of my QAS system, the Java "component" of the dialog instance attached to the central instance fails to start. The central instance's java component loads just fine, but I get the following error in the jvm.bootstrap file of the DI.
Bootstrap MODE:
<INSTANCE GLOBALS>
determined by parameter [ID0328058].
Exception occurred:
com.sap.engine.bootstrap.SynchronizationException: Database initialization failed! Check database properties!
     at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:476)
     at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:146)
     at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:971)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
==[ Caused by: ]==----
com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
     at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:364)
     at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:129)
     at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)
     at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:149)
     at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:236)
     at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:49)
     at com.sap.engine.bootstrap.Synchronizer.<init>(Synchronizer.java:74)
     at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:473)
     at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:146)
     at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:971)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by: com.sap.sql.log.OpenSQLException: Could not load class com.microsoft.sqlserver.jdbc.SQLServerDriver.
     at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:106)
     at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:143)
     at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:608)
     at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:285)
     at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:306)
     ... 14 more
Caused by: java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerDriver
     at com.sap.engine.offline.FileClassLoader.findClass(FileClassLoader.java:691)
     at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:600)
     at com.sap.engine.offline.FileClassLoader.loadClass(FileClassLoader.java:578)
     at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:141)
     at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:134)
     ... 17 more
[Bootstrap module]> Problem occurred while performing synchronization.
Any thoughts on what I can do (without having to re-install the dialog instance) to fix this?

Hi,
I hope this helps you, my Basis team came up with the same problem. It is because of the JDBC driver that SR3 uses seems to be wrong. This is a slightly subtle problem and it took me a while to find.
- Open configtool
- Go to instance --> dispatcher --> Configuration Manager --> Local Properties --> rdbms.driverLocation
- Change it to C:\usr\sap\SMB\DVEBMGS00\exe\mssjdbc\sqljdbc.jar (or similar)
- Go to instance > server> Configuration Manager --> Local Properties --> rdbms.driverLocation
- Change it to C:\usr\sap\SMB\DVEBMGS00\exe\mssjdbc\sqljdbc.jar (or similar)
On my system it was set to C:\usr\sap\SMB\DVEBMGS00\exe\mssjdbc\base.jar;C:\usr\sap\SMB\DVEBMGS00\exe\mssjdbc\util.jar;C:\usr\sap\SMB\DVEBMGS00\exe\mssjdbc\sqlserver.jar;C:\usr\sap\SMB\DVEBMGS00\exe\mssjdbc\spy.jar which is the old school SQL Server driver.
Once you have changed these settings, save, exit configtool and restart the whole cluster. It will then start.
Regards,
John

Request stays yellow

Similar Messages

Maybe you are looking for