Technical Status is in yellow but total status is in Red

Folks,
My Init load failed due to RFC errors, in the monitor Total is showing Red Status but the Technical is still showing yellow status and I am unable to delete the failed PSA request to re-start my Init load, please let me know how to resolve this issue.
Thanks,
Kumar

Hi ,
did you cancel the job in source system .. first cancel that job  and the delete that request ..
request might take long to delete due the more no of records ..
check the deletion job in source system wether its progressing or not .. In general you can follow this if you face this kind of issue further ..
regards,
shikha

Similar Messages

  • IP status is in Yellow but job is finished

    Hi ,
    I am working on BW system in which I am loading the data from IP to Data Target directly without PSA.
    Here I am facing a problem that load is failed but If I go to IP Monitor, I am able to see that request is in yellow color.
    I have gone to ST22 but thera is no dump.
    Would you please tell me what could be the root cause fo this one.
    Regards,
    K.Krishna.

    Hi krishna,
    What is the source system? -- ecc or flat file?
    from the load monitor screen check the below options...
    First check if the source system job finished or not?
    Check if there are any HUNG TRFC from source to BW system which did not processed.
    if the source system job is finished , check for the TIDs from the job log and go to TRFC screen and try to manually flush the hung TRFCs...the load will goto green.
    Regards
    KP

  • Job completed but status showing still yellow

    Hi Experts,
    One of full load status tab showing yellow, but the job completed when i checked in SM37.
    I am loading from ODS to Cube there is no PSA. we are using 3.5 version.

    Hi David,
    Check the load in the details tab weather all the data packets are in green status.If at all the idocs are hung or TRFCs are hung you may face this issue. try to manually flush the hung Idocs and TRFCs.
    If everything is fine wait for the PID  process to finish- some times it happen the PID might be running at the background.
    If everything is fine n the status of the request is yellow -try to change the status of the load to green.
    Regards
    KP
    Edited by: prashanthk on Oct 5, 2010 2:22 PM

  • How to stop the process chain showing status as yellow but no process step

    Dear Friends,
    How to stop the process chain showing status as yellow but no process step is running in that process chain.
    We have manually triggered the process chain for sales it finished successfully till load data but the next step is create index and DB statistics. Both of this steps are in unscheduled position only and no background job for this.
    Please guide me.
    Thanking you in advance.
    Regards,
    Shubhangi

    Hi,
      At times even I have faced this situation.  During those times, running the Function module RSPC_PROCESS_FINISH by passing the right parameters came to my rescue.
    Regards,
    Raj

  • The difference between the QM status and total status of a request?

    Hi Experts,
    I have some confusion about the concept of the status of a request. In the data target management window, we have QM status and technical status of a request, and in the monitor, we have total status of the request. Can somebody tell me the difference between the three. Please give me some detailed info about this or provide me some document regarding this. your great help will be highly appreciated.
    Eileen

    QM status can be edited..but technical status cannot be edited..
    in the monitor..only total status can be edited..
    please see this link..gives the required info..
    http://help.sap.com/saphelp_nw04/helpdata/en/80/1a663ce07211d2acb80000e829fbfe/frameset.htm
    Vishvesh

  • Exact Difference between Total  Status And QM Status

    Hello All,
    I want to know Exact Difference between Total Status in Monitor And QM Status in Data Target.when these two are going to be changed manually. i am facing a Problem.
    daily delta upload is going on from R3 to BW.Today it has given a problem while loading data. please give me u r ideas on this. how this delta should be Success.By changing which status ( Total, QM status) i need to chage for deleting the failure Request , to load delta again.
    thanks in advance.
    Eswar

    The global monitor queue time can be set in transaction RSCUSTV2. This is the time that the system allows to elapse before it sets a request to 'Terminated'. If the time of the last received message that logged a processing step on the monitor for this request has taken longer than the monitor queue time, the traffic light in the monitor is set to red. 
    If the monitor traffic light was set to red due to the queue time, this does not necessarily mean that the request can no longer be successful. 
    If the data is very delayed by the time it reaches BW (because the source system needs a long time for the extraction or because the link between the source system and BW was interrupted) or if the processing in BW needs a very long time in which the processing step does not log any messages on the monitor, the monitor traffic light becomes red and jumps back to yellow as soon as a new log for this request reaches the monitor. If you manually set the QM status in the monitor, this also does NOT prevent the updating of data for this request in BW! However, then the request can no longer turn green, since the manually set QM status always overrides the technical status of the monitor.
    Bye,
    Roberto

  • Server0 process in yellow and in status "starting apps" from many times

    Hi to all,
    platform windows/SQL
    I have a problem , I just made a system copy of my BI-Java (NW 7.0 SR3 ) using database independent system copy method.
    I make the export : all OK.
    I make the import ( system copy tool sapinst ) : All ok without errors.
    Now I'm tryng to start the Java ap server ( ABAP IS UP AND WORKS ) but it doesn't start : in MMC I see the java server0 process in yellow and in status "starting apps" from many times.
    Please help , what can I do ?

    I Eric ,
    I waited , but still yellow :
    here is the dev_server0 , it is very very  long file so i post most important parts of the log
    trc file: "F:\usr\sap\JBX\JC00\work\dev_server0", trc level: 1, release: "700"
    node name   : ID5856350
    pid         : 2460
    system name : JBX
    system nr.  : 00
    started at  : Mon Nov 15 18:32:02 2010
    arguments       :
           arg[00] : F:\usr\sap\JBX\JC00\exe\jlaunch.exe
           arg[01] : pf=F:\usr\sap\JBX\SYS\profile\JBX_JC00_sappino
           arg[02] : -DSAPINFO=JBX_00_server
           arg[03] : pf=F:\usr\sap\JBX\SYS\profile\JBX_JC00_sappino
    [Thr 1676] Mon Nov 15 18:32:02 2010
    [Thr 1676] *** WARNING => INFO: Unknown property [instance.box.number=JBXJC00sappino] [jstartxx.c   841]
    [Thr 1676] *** WARNING => INFO: Unknown property [instance.en.host=sappino] [jstartxx.c   841]
    [Thr 1676] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c   841]
    [Thr 1676] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c   841]
    JStartupReadInstanceProperties: read instance properties [F:\usr\sap\JBX\JC00\j2ee\cluster\instance.properties]
    -> ms host    : sappino
    -> ms port    : 3901
    -> OS libs    : F:\usr\sap\JBX\JC00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : normal
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : F:\usr\sap\JBX\JC00\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : sappino
    -> ms port    : 3901
    -> os libs    : F:\usr\sap\JBX\JC00\j2ee\os_libs
    -> admin URL  :
    -> run mode   : normal
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : F:\usr\sap\JBX\JC00\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID5856300  : F:\usr\sap\JBX\JC00\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID5856350  : F:\usr\sap\JBX\JC00\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID5856300            : F:\usr\sap\JBX\JC00\j2ee\cluster\instance.properties
    -> [01] ID5856350            : F:\usr\sap\JBX\JC00\j2ee\cluster\instance.properties
    [Thr 1676] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 1676] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 2796] JLaunchRequestFunc: Thread 2796 started as listener thread for np messages.
    [Thr 1116] WaitSyncSemThread: Thread 1116 started as semaphore monitor thread.
    [Thr 1676] Mon Nov 15 18:32:03 2010
    [Thr 1676] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 1676] CPIC (version=700.2006.09.13)
    [Thr 1676] [Node: server0] java home is set by profile parameter
         Java Home: C:\JAVA_SDK_64BIT
    [Thr 1676] JStartupICheckFrameworkPackage: can't find framework package F:\usr\sap\JBX\JC00\exe\jvmx.jar
    JStartupIReadSection: read node properties [ID5856350]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : C:\JAVA_SDK_64BIT
    -> java parameters    : -Djco.jarm=1 -verbose:gc -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -XX:NewSize=341m -XX:MaxNewSize=341m -XX:MaxPermSize=192m -XX:PermSize=192m -XX:DisableExplicitGC -XX:PrintGCDetails -XX:+PrintGCTimeStamps -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc
    -> java vm version    : 1.4.2_26-b03
    -> java vm vendor     : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
    -> java vm type       : server
    -> java vm cpu        : amd64
    -> heap size          : 2048M
    -> init heap size     : 2048M
    -> stack size         : 2M
    -> root path          : F:\usr\sap\JBX\JC00\j2ee\cluster\server0
    -> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : F:\usr\sap\JBX\JC00\j2ee\os_libs
    -> main class         : com.sap.engine.boot.Start
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : F:\usr\sap\JBX\JC00\exe\jstartup.jar;F:\usr\sap\JBX\JC00\exe\jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 50021
    -> shutdown timeout   : 120000
    [Thr 1676] JLaunchISetDebugMode: set debug mode [no]
    [Thr 2372] JLaunchIStartFunc: Thread 2372 started as Java VM thread.
    [Thr 2372] [JHVM_PrepareVMOptions] use java parameters set by profile parameter
         Java Parameters: -Xss2m
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 1048576 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Djco.jarm=1
    -> arg[  4]: -verbose:gc
    -> arg[  5]: -Djava.awt.headless=true
    -> arg[  6]: -Dsun.io.useCanonCaches=false
    -> arg[  7]: -Djava.security.policy=./java.policy
    -> arg[  8]: -Djava.security.egd=file:/dev/urandom
    -> arg[  9]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[ 10]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[ 11]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[ 12]: -XX:NewSize=341m
    -> arg[ 13]: -XX:MaxNewSize=341m
    -> arg[ 14]: -XX:MaxPermSize=192m
    -> arg[ 15]: -XX:PermSize=192m
    -> arg[ 16]: -XX:+DisableExplicitGC
    -> arg[ 17]: -XX:+PrintGCDetails
    -> arg[ 18]: -XX:+PrintGCTimeStamps
    -> arg[ 19]: -XX:SurvivorRatio=2
    -> arg[ 20]: -XX:TargetSurvivorRatio=90
    -> arg[ 21]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 22]: -verbose:gc
    -> arg[ 23]: -Dsys.global.dir=F:\usr\sap\JBX\SYS\global
    -> arg[ 24]: -Dapplication.home=F:\usr\sap\JBX\JC00\exe
    -> arg[ 25]: -Djava.class.path=F:\usr\sap\JBX\JC00\exe\jstartup.jar;F:\usr\sap\JBX\JC00\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 26]: -Djava.library.path=C:\JAVA_SDK_64BIT\jre\bin\server;C:\JAVA_SDK_64BIT\jre\bin;C:\JAVA_SDK_64BIT\bin;F:\usr\sap\JBX\JC00\j2ee\os_libs;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;c:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\WINDOWS\system32\WindowsPowerShell\v1.0;F:\usr\sap\JBX\SYS\exe\uc\NTAMD64
    -> arg[ 27]: -Dmemory.manager=2048M
    -> arg[ 28]: -Xmx2048M
    -> arg[ 29]: -Xms2048M
    -> arg[ 30]: -Xss2M
    -> arg[ 31]: -DLoadBalanceRestricted=no
    -> arg[ 32]: -Djstartup.mode=JCONTROL
    -> arg[ 33]: -Djstartup.ownProcessId=2460
    -> arg[ 34]: -Djstartup.ownHardwareId=M1883233260
    -> arg[ 35]: -Djstartup.whoami=server
    -> arg[ 36]: -Djstartup.debuggable=no
    -> arg[ 37]: -Xss2m
    -> arg[ 38]: -DSAPINFO=JBX_00_server
    -> arg[ 39]: -DSAPSTARTUP=1
    -> arg[ 40]: -DSAPSYSTEM=00
    -> arg[ 41]: -DSAPSYSTEMNAME=JBX
    -> arg[ 42]: -DSAPMYNAME=sappino_JBX_00
    -> arg[ 43]: -DSAPDBHOST=SAPPINO
    -> arg[ 44]: -Dj2ee.dbhost=SAPPINO
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    [Thr 2372] Mon Nov 15 18:32:04 2010
    [Thr 2372] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 3844] Mon Nov 15 18:32:07 2010
    [Thr 3844] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 3844] Mon Nov 15 18:32:08 2010
    [Thr 3844] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 3844] Mon Nov 15 18:32:09 2010
    [Thr 3844] JLaunchISetClusterId: set cluster id 5856350
    [Thr 3844] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 3844] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    Mon Nov 15 18:33:09 2010
    66.769: [GC 66.779: [DefNew
    Mon Nov 15 18:33:12 2010
    : 174592K->12719K(261888K), 2.4968787 secs] 174592K->12719K(2009856K), 2.5007114 secs]
    Mon Nov 15 18:33:28 2010
    85.012: [GC 85.019: [DefNew
    Mon Nov 15 18:33:31 2010
    : 187311K->15802K(261888K), 2.9950002 secs] 187311K->15802K(2009856K), 2.9962968 secs]
    Mon Nov 15 18:33:42 2010
    99.362: [GC 99.363: [DefNew
    Mon Nov 15 18:33:43 2010
    : 190394K->18114K(261888K), 1.3817075 secs] 190394K->18114K(2009856K), 1.3817727 secs]
    Mon Nov 15 18:34:04 2010
    121.270: [GC 121.270: [DefNew: 192706K->22709K(261888K), 0.4353252 secs] 192706K->22709K(2009856K), 0.4354424 secs]
    Mon Nov 15 18:34:14 2010
    131.077: [GC 131.079: [DefNew
    Mon Nov 15 18:34:15 2010
    : 197301K->29493K(261888K), 0.9813876 secs] 197301K->29493K(2009856K), 0.9823920 secs]
    [Thr 3344] Mon Nov 15 18:34:36 2010
    [Thr 3344] JHVM_RegisterNatives: registering methods in com.sap.security.core.server.vsi.service.jni.VirusScanInterface
    Mon Nov 15 18:34:44 2010
    160.965: [GC 160.966: [DefNew
    Mon Nov 15 18:34:47 2010
    : 204085K->40068K(261888K), 3.8189779 secs] 204085K->40068K(2009856K), 3.8194810 secs]
    [Thr 3532] Mon Nov 15 18:34:54 2010
    [Thr 3532] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
    [Thr 4932] Mon Nov 15 18:34:57 2010
    [Thr 4932] JHVM_RegisterNatives: registering methods in com.sap.i18n.cp.ConverterJNI
    Mon Nov 15 18:35:09 2010
    186.312: [GC 186.315: [DefNew: 214660K->44513K(261888K), 0.4742509 secs] 214660K->44513K(2009856K), 0.4773469 secs]
    [Thr 3844] Mon Nov 15 18:38:32 2010
    [Thr 3844] JLaunchISetState: change state from [Starting (2)] to [Starting applications (10)]
    Mon Nov 15 18:39:18 2010
    435.575: [GC 435.576: [DefNew: 219105K->48184K(261888K), 0.2394759 secs] 219105K->48184K(2009856K), 0.2397480 secs]
    Mon Nov 15 18:39:20 2010
    Excluding compile:  com.sap.engine.services.webservices.jaxrpc.encoding.TypeMappingImpl::initializeRelations
    Mon Nov 15 18:39:23 2010
    440.506: [GC 440.506: [DefNew: 222776K->50686K(261888K), 0.1335379 secs] 222776K->50686K(2009856K), 0.1335965 secs]
    Mon Nov 15 19:42:07 2010
    [Unloading class sun.reflect.GeneratedMethodAccessor14]
    [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor127]
    [Unloading class sun.reflect.GeneratedMethodAccessor13]
    [Unloading class sun.reflect.GeneratedMethodAccessor105]
    [Unloading class sun.reflect.GeneratedMethodAccessor99]
    [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor135]
    [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor4]
    [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor96]
    [Unloading class sun.reflect.GeneratedMethodAccessor128]
    Mon Nov 15 19:42:08 2010
    [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor17]
    [Unloading class sun.reflect.GeneratedMethodAccessor119]
    [Unloading class sun.reflect.GeneratedMethodAccessor64]
    [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor29]
    [Unloading class sun.reflect.GeneratedMethodAccessor47]
    [Unloading class sun.reflect.GeneratedMethodAccessor86]
    [Unloading class sun.reflect.GeneratedConstructorAccessor72]
    [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor14]
    [Unloading class sun.reflect.GeneratedMethodAccessor109]
    [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor82]
    [Unloading class sun.reflect.GeneratedMethodAccessor156]
    [Unloading class sun.reflect.GeneratedMethodAccessor147]
    [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor94]
    [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor65]
    [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor93]
    Mon Nov 15 19:42:09 2010
    [Unloading class sun.reflect.GeneratedMethodAccessor107]
    [Unloading class sun.reflect.GeneratedMethodAccessor142]
    [Unloading class sun.reflect.GeneratedSerializationConstructorAccessor2]
    Mon Nov 15 20:19:06 2010
    : 1488916K->1046521K(1747968K), 3204.1629115 secs] 1749638K->1046521K(2009856K), 3204.1631834 secs]

  • 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

  • Status remains as Yellow, for no data

    hi ,
    in our master data load process chain, a datasource which has 0 records in the sourcesystem returns 0 records in BI. but the status remains as yellow , instead of green.
    since the status is yellow the next process is not getting triggered. only if we manually change the status to green, the process chain continues. wht shall we do to change the status to green automatically.

    Hi DOLLY,
    you need to cofigure  a small setting at Infopackage for this.
    RSA1-> infopackage -> scheduler -> Trafic light color for Empty request -> select green and save it.
    for 0 to 0 records load will show as Green.
    Regards
    Daya Sagar

  • Total status

    what is difference between total status and technical status in monitor screen?in which situation we use them?

    Praveen,
       Total status refers to the entire load process of a particular request. Tech refers to the internal display of the process like transfer of Idocs from source.

  • Support Desk Message is Sent to SAP; But the status is not updated

    Hi All,
    We have Solution Manager 7.0 SP15 with Windows Server and Oracle.
    Service Desk is configured.
    One user has reported a problem from satellite system.
    It arrived to Service Desk of Solution Manager.
    The support team message processor changed the status to "In Process"
    and asked sapadmin user(who can forward messages to SAP) to forward this message to SAP.
    sapadmin user(SAP-OSS) has performed the action "Send Message to SAP" successfully.
    But the status of the message is still "In Process". It didn't change to "Sent to SAP".
    Question is:
    1. Where and How to check the message is really sent to SAP or not?
    2. Why the status is not changed to SAP? Is anything needs to be done yet?
    I have checked this thread and performed the actions. But still it doesn't work.
    Send support message to SAP, don't refresh info at service desk
    Regards,
    Sanjai

    Rohit,
    Thanks.
    I have implemented this note.
    I get different error now when the user try to do the action "Send Message to SAP".
    The error is: "You do not have authourization to send notification to SAP".
    The user has the following roles:
    Z:M_SAP_SM_SOLUTION_ALL
    Z:M_SAP_SOCM_IT_OPERATOR
    Z:M_SAP_SOCM_REQUESTER
    Z:M_SAP_SUPPDESK_ADMIN
    Z:M_SAP_SUPPDESK_CREATE
    Z:M_SAP_SV_FDB_NOTIF_BC_ADMIN
    Z:M_SAP_SV_SOLUTION_MANAGER
    Z:SAP_MAINT_OPT_ADMIN
    SAP Note 1140822 resolved this issue.
    We are able to forward the message to SAP.
    Regards
    Sanjai

  • 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

  • I purchased the newest software update for my ipod touch 1st generation and it is saying it is it will now begin download but the status bar doesn't even appear? How can I start the download?

    I purchased the newest software update for my ipod touch 1st generation and it is saying it is it will now begin download but the status bar doesn't even appear? How can I start the download?

    Well first off you shouldn't have had to pay for a download (just an assumption from the word "purchased".
    If you are trying to install iOS 5 on your iPod touch, it won't work they arent compatible. I suggest checking what version of software you are trying to install and posting it in this forum so people can have a better understanding.

  • HTTP Status Code 200 Received But Error During Response Parsing

    Hi Experts,
    We are testing a simple Proxy(ECC) to File scenario in QA. This interface was working fine in Dev but we are getting the following error here in QA:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    <!--  Call Adapter  -->
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">OK_BUT_NO_XI_MESSAGE</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>HTTP Status Code 200 Received But Error During Response Parsing: No XI Response Received XML element Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    We searched other threads but could not get any solution. Please provide suggestions.
    Thank You.
    Regards,
    Anandan

    the problem was due to high volume message (247 MB ) ...Java stack was not able to process this huge message ,that is the reason ,it started automatically  and as a result  , "HTTP Status Code 200 Received But Error During Response Parsing" due to unavailability of AFW during Call adapter step in the pipeline processing...
    We have done the following activities in order to solve this problem....
    increase the value of  icm/HTTP/max_request_size_KB to 512MB
                                        icm/wp_roll_timeout   to maximum
                                        HTTP TIMEOUT to 1800 sec
                                       icm/wp_roll_timeout   to maximum
                                         mpi/total_size_MB  to maximum
                                       mpi/buffer_size  to maximum
    and then increased the maxthreadcount ,maxcontentlength using config tool...
    and also increased the java heap size to maximum....
    After doing everything ,the file has been successfully processed....
    the problem has been resolved...

  • All records loaded to cube successfully but the request is in red status

    All the records are loaded from r3 to target, but the status of the request is still in RED, what is the reason and how to resolve it?

    Hi,
    If you find the records are loaded to cube and request is still red, Follow any one of the following options.
    1. Make the request to green manually
    2. Check the extraction monitor settings in SPRO -
    > SAP Customizing Implementation Guide  ---> Business Intelligence  --->  
        Automated Processes  -
    > Extraction Monitor Settings. Check how the settings are done if you are authorized.
    3. Go to Manage of the target ---> Environment ---> Automatic Request processing ---> Check the option Set Quality Status to OK
    Hope this helps,
    Regards,
    Rama Murthy.
    Edited by: Rama Murthy Pvss on May 11, 2010 7:39 AM

Maybe you are looking for