Switchover failed,primary status is 'not allowed'

hi,
i used AS5+11gR2+dg and got a problem after normal switchover.
1.the switchover_status of primary shows 'not allowed'
2.log seems not SYNC.
3.dgmgrl shows 'incorrect database role'.
everything goes OK before switchover, how could this happen and how to switchover back?
thanks all.

MahirM.Quluzade 撰写:
Can you paste here:
DGMGRL> show configuration;
DGMGRL> show database verbose <primary>
DGMGRL> show database verbose <standby>
Mahir
1.
DGMGRL> show configuration
Configuration - DRtestdb
  Protection Mode: MaxPerformance
  Databases:
    testdb     - Primary database
      Error: ORA-16816: incorrect database role
    sztestdbdg - Physical standby database
      Error: ORA-16810: multiple errors or warnings detected for the database
Fast-Start Failover: DISABLED
Configuration Status:
ERROR
2.
DGMGRL> show database verbose 'sztestdbdg';
Database - sztestdbdg
  Role:            PHYSICAL STANDBY
  Intended State:  APPLY-ON
  Transport Lag:   (unknown)
  Apply Lag:       (unknown)
  Real Time Query: OFF
  Instance(s):
    sztestdbdg
  Database Error(s):
    ORA-16816: incorrect database role
    ORA-16700: the standby database has diverged from the primary database
    ORA-16766: Redo Apply is stopped
  Properties:
    DGConnectIdentifier             = 'sztestdbdg'
    ObserverConnectIdentifier       = ''
    LogXptMode                      = 'ASYNC'
    DelayMins                       = '0'
    Binding                         = 'OPTIONAL'
    MaxFailure                      = '0'
    MaxConnections                  = '1'
    ReopenSecs                      = '300'
    NetTimeout                      = '30'
    RedoCompression                 = 'DISABLE'
    LogShipping                     = 'ON'
    PreferredApplyInstance          = ''
    ApplyInstanceTimeout            = '0'
    ApplyParallel                   = 'AUTO'
    StandbyFileManagement           = 'AUTO'
    ArchiveLagTarget                = '0'
    LogArchiveMaxProcesses          = '4'
    LogArchiveMinSucceedDest        = '1'
    DbFileNameConvert               = '/app/oracle/oradata/testdb/, /oradata/sztestdbdg/sztestdbdg/'
    LogFileNameConvert              = '/app/oracle/oradata/testdb/, /oradata/sztestdbdg/sztestdbdg/'
    FastStartFailoverTarget         = ''
    InconsistentProperties          = '(monitor)'
    InconsistentLogXptProps         = '(monitor)'
    SendQEntries                    = '(monitor)'
    LogXptStatus                    = '(monitor)'
    RecvQEntries                    = '(monitor)'
    SidName                         = 'sztestdbdg'
    StaticConnectIdentifier         = '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.9.198)(PORT=1528))(CONNECT_DATA=(SERVICE_NAME=SZTESTDBDG_DGMGRL)(INSTANCE_NAME=SZTESTDBDG)(SERVER=DEDICATED)))'
    StandbyArchiveLocation          = '/arch/sztestdbdg'
    AlternateLocation               = ''
    LogArchiveTrace                 = '0'
    LogArchiveFormat                = '%t_%s_%r.dbf'
    TopWaitEvents                   = '(monitor)'
Database Status:
ERROR
3.
DGMGRL> show database verbose 'testdb';
Database - testdb
  Role:            PRIMARY
  Intended State:  TRANSPORT-ON
  Instance(s):
    testdb
  Database Error(s):
    ORA-16816: incorrect database role
  Properties:
    DGConnectIdentifier             = 'testdb'
    ObserverConnectIdentifier       = ''
    LogXptMode                      = 'ASYNC'
    DelayMins                       = '0'
    Binding                         = 'optional'
    MaxFailure                      = '0'
    MaxConnections                  = '1'
    ReopenSecs                      = '300'
    NetTimeout                      = '30'
    RedoCompression                 = 'DISABLE'
    LogShipping                     = 'ON'
    PreferredApplyInstance          = ''
    ApplyInstanceTimeout            = '0'
    ApplyParallel                   = 'AUTO'
    StandbyFileManagement           = 'MANUAL'
    ArchiveLagTarget                = '0'
    LogArchiveMaxProcesses          = '4'
    LogArchiveMinSucceedDest        = '1'
    DbFileNameConvert               = '/app/oracle/oradata/testdb/, /oradata/sztestdbdg/sztestdbdg'
    LogFileNameConvert              = '/app/oracle/oradata/testdb/, /oradata/sztestdbdg/sztestdbdg'
    FastStartFailoverTarget         = ''
    InconsistentProperties          = '(monitor)'
    InconsistentLogXptProps         = '(monitor)'
    SendQEntries                    = '(monitor)'
    LogXptStatus                    = '(monitor)'
    RecvQEntries                    = '(monitor)'
    SidName                         = 'testdb'
    StaticConnectIdentifier         = '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.9.197)(PORT=1528))(CONNECT_DATA=(SERVICE_NAME=testdb_DGMGRL)(INSTANCE_NAME=testdb)(SERVER=DEDICATED)))'
    StandbyArchiveLocation          = '/arch/testdb'
    AlternateLocation               = ''
    LogArchiveTrace                 = '0'
    LogArchiveFormat                = '%t_%s_%r.dbf'
    TopWaitEvents                   = '(monitor)'
Database Status:
ERROR

Similar Messages

  • XML failure with ASN no Process DELIVERY_INFO_GR for ASN in status is not allowed

    Hi All,
    In production , we are having many XML failures while sending inbound delivery to SNC from ECC.
    In SXMB_Moni,  ASN XXXX: Process DELIVERY_INFO_GR for ASN in status is not allowed. Becasue ASN is not exist in SNC but in ECC GR status is complete.
    Please help to resolve the same.
    Regards,
    Sheetal

    Hi,
    Please go the tcode CO02 and click on functions and select the restrict processingand click on unlock
    the reason may be tht some might have locked the produvtion order ,
    hopw it wud have answered ur question.
    rewards if it is useful
    Shawn

  • BAPI_DOCUMENT_CHECKIN2-Status does not allow you to change certain data

    Hi Gurus,
    I am uploading the DIR attached files for the Documents in PLM. We have a custom program written to upload the attached files. When I tried to upload the file I am getting the BAPI Return error as "Status does not allow you to change certain data". The status of all the documents is "RL"
    File format is
    Doc type  Document No   Rev           File Name
    JPS          0021581PS,     X,       /in/PLM/JAPAN/Files/0021581PS.xls
    Please help me I need to upload the data.
    Thanks,
    Deepthi

    Check the status network for your doc type in config. You may find that the current status may not allow you to make changes. You may need to change the current status to another status before you can make the changes you would like.
    The config settings will tell you the status you may set in order to make your changes, if they are allowed.

  • Search request failed! user is not allowed to perform search request

    hello all,
    i am trying to run initial loads on AS java database repository, the user i use in repository is and admin user for NW 7.3 and has full administrator rights.
    still initial loads were not successful  from the configuration guides i came to know Spml_Write_Action role is only for NW 7.0 and below for 7.3 is not using smpl connection i believe.
    this is the only warning in the job log
    Search request failed! <<user>> is not allowed to perform search request.
    default trace log.
    UME#sap.com/tc~sec~ume~wd~kit#C0000A17206800A800000002000021A8#23640950000000004#sap.com/tc~sec~ume~wd~umeadmin#com.sap.security.core.wd.maintainuser.MaintainUserComp.public void saveModifications( )#idm_admin#11##B1AC9AC0EC9211E3C1DF00000168BB76#b9612f91ec9511e38cec00000168bb76#b9612f91ec9511e38cec00000168bb76#0#Thread[HTTP Worker [@186066399],5,Dedicated_Application_Thread]#Plain##
    Error adding roles
    [EXCEPTION]
    com.sap.security.core.wd.exception.UmeUiSecurityException: com.sap.engine.services.jmx.exception.JmxSecurityException: Caller idm_admin not authorized, required permission missing (javax.management.MBeanPermission -\#modifyEntityAssignments[:SAP_J2EECluster="",j2eeType=UmeJmxServer,name=IJmxServer] invoke)
      at com.sap.security.core.wd.umeuifactory.UmeUiFactoryCompInterface.handleThrowable(UmeUiFactoryCompInterface.java:2977)
      at com.sap.security.core.wd.umeuifactory.UmeUiFactoryCompInterface.modifyEntityMappings(UmeUiFactoryCompInterface.java:1272)
      at com.sap.security.core.wd.umeuifactory.wdp.InternalUmeUiFactoryCompInterface.wdInvokeMethod(InternalUmeUiFactoryCompInterface.java:1034)
      at com.sap.tc.webdynpro.progmodel.generation.ExternalControllerPI$ExternalInterfaceInvocationHandler.invoke(ExternalControllerPI.java:339)
      at com.sun.proxy.$Proxy780.modifyEntityMappings(Unknown Source)
      at com.sap.security.core.wd.maintainuser.MaintainUserComp.saveModifications(MaintainUserComp.java:1334)
      at com.sap.security.core.wd.maintainuser.wdp.InternalMaintainUserComp.saveModifications(InternalMaintainUserComp.java:709)
      at com.sap.security.core.wd.maintainuser.ModifyUserView.onActionSave(ModifyUserView.java:630)
      at com.sap.security.core.wd.maintainuser.wdp.InternalModifyUserView.wdInvokeEventHandler(InternalModifyUserView.java:579)
      at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:142)
      at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:75)
      at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:159)
      at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.execute(ProcessingEventPhase.java:94)
      at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
      at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
      at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
      at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:515)
      at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:58)
      at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1671)
      at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1485)
      at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingEmbedded(ApplicationSession.java:919)
      at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:878)
      at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:357)
      at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:325)
      at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:62)
      at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.service(DispatchHandlerForRequestManager.java:39)
      at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.service(DispatchHandlerForRequestManager.java:46)
      at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:270)
      at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToAppContext(ExecutionContextDispatcher.java:68)
      at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:53)
      at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:244)
      at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy$Runner.callRequestManager(JavaApplicationProxy.java:1244)
      at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy$Runner.callEmbeddedApplication(JavaApplicationProxy.java:1122)
      at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy$SendDataAndProcessActionCommand.doExecute(JavaApplicationProxy.java:1605)
      at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy$AbstractCommand.execute(JavaApplicationProxy.java:1488)
      at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy$Runner.execute(JavaApplicationProxy.java:1028)
      at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy.execute(JavaApplicationProxy.java:859)
      at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy.sendDataAndProcessAction(JavaApplicationProxy.java:468)
      at com.sap.tc.webdynpro.portal.pb.impl.JavaApplicationProxyAdapter.sendDataAndProcessAction(JavaApplicationProxyAdapter.java:191)
      at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1668)
      at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:366)
      at com.sap.portal.pb.PageBuilder$PhaseListenerImpl.doPhase(PageBuilder.java:2094)
      at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:251)
      at com.sap.tc.webdynpro.clientserver.phases.PortalDispatchPhase.execute(PortalDispatchPhase.java:50)
      at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
      at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
      at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
      at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:515)
      at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:58)
      at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1671)
      at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1485)
      at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:908)
      at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:880)
      at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:357)
      at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:325)
      at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
      at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:89)
      at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
      at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
      at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
      at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:457)
      at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
      at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
      at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
      at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
      at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
      at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
      at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
      at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
      at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
      at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
      at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
      at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
      at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
      at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
      at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
      at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
      at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
    Caused by: com.sap.engine.services.jmx.exception.JmxSecurityException: Caller idm_admin not authorized, required permission missing (javax.management.MBeanPermission -\#modifyEntityAssignments[:SAP_J2EECluster="",j2eeType=UmeJmxServer,name=IJmxServer] invoke)
      at com.sap.engine.services.jmx.auth.UmeAuthorization.checkMBeanPermission(UmeAuthorization.java:100)
      at com.sap.engine.services.jmx.JmxServerFrame.checkMBeanPermission(JmxServerFrame.java:101)
      at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.checkMBeanPermission(MBeanServerSecurityWrapper.java:438)
      at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:288)
      at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:813)
      at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:367)
      at com.sap.security.core.jmx._gen.IJmxServer$Impl.modifyEntityAssignments(IJmxServer.java:3050)
      at com.sap.security.core.wd.jmxmodel.JmxModelCompInterface.modifyEntityMappings(JmxModelCompInterface.java:569)
      at com.sap.security.core.wd.jmxmodel.wdp.InternalJmxModelCompInterface.wdInvokeMethod(InternalJmxModelCompInterface.java:862)
      at com.sap.tc.webdynpro.progmodel.generation.ExternalControllerPI$ExternalInterfaceInvocationHandler.invoke(ExternalControllerPI.java:339)
      at com.sun.proxy.$Proxy779.modifyEntityMappings(Unknown Source)
      at com.sap.security.core.wd.umeuifactory.UmeUiFactoryCompInterface.modifyEntityMappings(UmeUiFactoryCompInterface.java:1266)
      ... 97 more
    Caused by: java.security.AccessControlException: access denied (javax.management.MBeanPermission -\#modifyEntityAssignments[:SAP_J2EECluster="",j2eeType=UmeJmxServer,name=IJmxServer] invoke)
      at java.security.AccessControlContext.checkPermission(AccessControlContext.java:376)
      at java.security.AccessController.checkPermission(AccessController.java:549)
      at com.sap.engine.services.jmx.auth.UmeAuthorization.checkMBeanPermission(UmeAuthorization.java:84)
      ... 108 more

    Hello,
           recheck that the user has the UME.Spml_Write_Action - SPML is still used in release 7.3. The log still indicates that there is an authorization error.
    Thanks,
    Chris

  • How Can I know, Material status does not allow purchase??

    Hi Experts,
    Pls. clarify me that, How Can I know/track the follwoing things? Which tables I hv to see?
    I hv a list of materials, some r good , some r bad. So, I hv to trace out the bad materials depending on the criteria, So, pls. let me know Which tbls I hv to look?
    1) Material does not exist in plant 1500
    2) Material status does not allow purchase
    3) Decimal places on the quantity may not be supported by unit of measure
    thanq

    thanq
    MATNR status:
    In our system the values for MARC-BESKZ are
    E     In-house production
    F     External procurement
         No procurement
    X     Both procurement types
    My requirement: I need to trace the MATNR from matnr_list for Material status does not allow purchase
    So, am thinking to write IF condn as,
    IF my_itab-matnr <> 'F' or my_itab-matnr <> 'X'.
    --> this matnr is Material status does not allow purchase
    ENDIF.
    Am I correct?
    3) Decimal places on the quantity may not be supported by unit of measure
    This can be retrieved from table T006
    I hv seen but, DO NOT UNDERSTAMD THIS TABLE entries, bcoz, there r values of 0 & 1 for the DECIMAL PLACES filed, partcularly for EA unit - devciaml places value is 0?
    pls. clarify,
    thanq

  • Status profile not allowed for object type

    hi
    i had created a status profile (for having 2 statuses before production order release) and assigned in the order type.
    but while creating the production order i receive the following error.
    Message no - CO622
    status profile not allowed for object type
    please provide your inputs
    regards
    Ramesh

    Ramesh,
    once you cerate a Status profile in BS02 and add status to the same. in the tollbar you will see OBJECT TYPE push button, select teh obejcts like PP/PM order header / operation /comepeoent and PRT ect where that staus can be applied.
    Then assign the statsu profile to order type.

  • VA01 - Material AS_ECIR_TECH1 has status: Sales not allowed

    Dear Gurus,
    In a sales order VA01, after entering a material with all relevant information such as quantities etc. I get this message at the bottom of the page:
    "Material AS_ECIR_TECH1 has status: Sales not allowed"
    1- What does that mean?
    2- How can I change this status so that I can input this order?
    Please advise
    Regards
    Chris

    Hi,
    The status of the 'DChain-spec. status' or 'X-distr.chain status' may have to be changed in the material to make it ready for sales order creation.
    a. Go to MM02 and key in the material number AS_ECIR_TECH1
    b. Select the 'Sales Organization 1' view and enter the details like plant, sales org and Distribution channel and press enter
    c. You will find 'X-distr.chain status' and 'DChain-spec. status' one below the other. Change both the status to appropriate ones (I cannot tell you which is right status as I do not know what values are configured there).
    d. Save the Material and try creating a sales order.
    It should work for you. Let me know your feedback.
    Thanks
    Mukund S

  • Charm: User Statuses error "Status is not allowed"

    Hello,
    We have created some additional statuses for SDHF. When I look at the log in status tab of the record I see the errors
    User status ANGE must not be deleted
    Status PROC is not allowed (Service Process 742)
    The user status 'E0002' must not be set         
    Status ZUTE is not allowed (Service Process 742)
    The user status 'E0004' must not be set         
    Status Test is not allowed (Service Process 742)
    The user status 'E0005' must not be set         
    Status PROD is not allowed (Service Process 742)
    The user status 'E0006' must not be set         
    Status Conf is not allowed (Service Process 742)
    The user status 'E0007' must not be set         
    Status ABGE is not allowed (Service Process 742)
    The user status 'E0008' must not be set         
    Status REL is not allowed (Service Process 742) 
    The user status 'E0009' must not be set         
    Status CANC is not allowed (Service Process 742)
    The user status 'E0010' must not be set         
    Status ZCFS is not allowed (Service Process 742)
    The user status 'E0011' must not be set         
    Status ZFSC is not allowed (Service Process 742)
    The user status 'E0012' must not be set         
    Status ZBPO is not allowed (Service Process 742)
    The user status 'E0013' must not be set         
    Status ZBPA is not allowed (Service Process 742)
    The user status 'E0014' must not be set         
    Status ZCTS is not allowed (Service Process 742)
    The user status 'E0015' must not be set         
    Status ztsc is not allowed (Service Process 742)
    The user status 'E0016' must not be set       
    The help on this shows:
    Status Conf is not allowed (Service Process 742)
    Message no. BS042
    Diagnosis
    The user status 'Conf' has reference number 70.  In the current object status 'Service Process 742', the reference number of a status may not be higher than 10.
    Procedure
    You can only set user status whose reference number is not higher than 10.
    Anyone know where this value of 10 comes from?
    Any idea how this can be fixed?
    Regards,

    Hi,
    Check the Status Profile of SDHF in CRMBS02.
    Chk the Lowest and highest value against the Status.
    Thnx,
    Waseem.

  • Document fields are changable though status does not allow

    Hi All,
    our HR dms consists of three status for any doc types :
    (1) in-preparation IA  (2) to-approve   (3) approved FR
    > in-preparation : is changeable only via the creator profie "one who creates/uploads the documents"
    > to-approve : status type is set to S "locked status" no changes can be done except status change, and this is assigned to the profile of the approvee "one who's approving the documents"
    the status to-approve is custome created
    when this approvee person opens any to-approve document he's unable to do any changes except status change either to (1) or (3) "all other fields are grayed out" However, i have noticed that if he change status to (1) then prior saving the document he clicks the enter key then all the feilds are returned back to updatable ! i know status (1) allows update, but this user has no change authority over status (1) and this has been tested separately and proved that can't change status 1 documents, why only at this situation system is allowing this change.

    hi,
    Daher,
    Please crate networl like this,,
    Doc type -DOC STDescAbbr--
    St Type
    TES--     AA     Work Request     WR--
         I
    TES--     FR     Released     RE--
         S
    TES--     IA     In Work     IW--
         C
    Previous 1, 2, 3,
    1.--     Work request-- AA-----[WR]--     --FR -
    <i>
    2.--     InWork  IA -[IW]---AA,  FR--
    [C]
    3.--     Released -FR -[RE]--     IA,   AA--
    [S]
    benakaraja ES
    Edited by: benaka rajes on Jun 11, 2009 5:38 PM

  • Decrypting FileVault Failed and User Account Not Allowing Login

    So here is the scenario and my problem. I decided to do a clean install of Leopard on my PowerMac G5 and in doing so used Carbon Copy Cloner to copy all the content of my Macintosh HD drive to another internal DataDrive so that I could get my data later and be able to boot into that old installation of the OS for any reason. After the clone was complete I did a clean install of Leopard onto my Macintosh HD volume.
    With the new installation running and updates run I decided to go and get my old data. Turns out I had FileVault protection on in the old installation and could not access my data through the new install. This was the very reason I kept the old installation. I rebooted into the old installation and went to remove FileVault protection. The computer logged out and started decrypting my user folder.
    Two hours into the decryption it failed and prompted me to continue and be returned to my login and state before I started the decryption. Now I can't login to that user because when I attempt to it will say that FileVault needs to be repaired and give you the option to repair. The repair takes a while and then give you the error stating the repair didn't work.
    So I need help figuring out how to get access to my data in that user folder or get that user folder to work so that I can get my info copied to my new installation. Any ideas would be very much appreciated as I feel like I have lost too much for comfort.
    Thanks, Brandon

    First of all thank you for the help. In all my trying to figure it out I didn't try just double clicking on the sparse bundle.
    Because this was my only user on the computer I had to enable the root user to be able to login. Once that was enable I was able to mount the sparsebundle and copy my data out. I didn't get all of it as something did truly get corrupted during the decryption but I did get 99% I think.
    Now with my data coped to another location I can attempt some repairs and see if I am able to get that last percentage point. Thank again.
    Brandon

  • Mouse drag operation failed. Editing is not allowed for this DataSet..

    Hello,
    I am using Visual Studio 2008 and SQL SERVER Management Studio Express 2005.
    I am getting this error when I try to drag a dataset. Please help me to resolve this problem as soon as possible.
    Regards,
    Developer051

    Really quick solution (VS2005) - check the "ZOrder" attribute of the DataSets in the underlying .xss file.
    I had the same problem, but only when I opened one of the XSD designers in Visual Studio. All the others worked fine.
    I found out that 2 of my DataSet Shapes had the same "ZOrder" value ("2") when I opened the XSS file:-
    <DiagramLayout xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" ex:showrelationlabel="False" ViewPortX="7" ViewPortY="15" xmlns:ex="urn:schemas-microsoft-com:xml-msdatasource-layout-extended" xmlns="urn:schemas-microsoft-com:xml-msdatasource-layout">
      <Shapes>
        <Shape ID="DesignTable:DataTable1"ZOrder="2" X="26" Y="44" Height="827" Width="258" AdapterExpanded="true" DataTableExpanded="true" OldAdapterHeight="0" OldDataTableHeight="0"
    SplitterPosition="823" />
        <Shape ID="DesignTable:DataTable2"
    ZOrder="2" X="704" Y="458" Height="130" Width="204" AdapterExpanded="true" DataTableExpanded="true" OldAdapterHeight="0" OldDataTableHeight="0" SplitterPosition="126" />
      </Shapes>
      <Connectors />
    </DiagramLayout>
    I made them different (set one of them to "1", kept the other one as "2") and the DataSet was immediately editable in the designer.
    Hurray!
    I was having the exact same issue and this fixed it right up for me!

  • Material status in master data set not allow create production order. but..

    Dear All expert.
    There is one case I don't understand,  the component material within BOM had been set material plant status which it is not allowed to create Production order ( Porder header Msg & PO/Network item msg = B in OMS4).
    If user use tx:CO01 for create production order, the error message block production order can't be created. It is good .
    However, when user is using Tx: CO41 to convert planned order to production order with that material ( status which not allowed to create production Order) . it is successfully without any error message ..  User successfully create production order without limit.
    Therefore,  is there any configure in IMG was wrong?
    thanks for reading.
    Marco

    Dear R.Brahmankar,
    I had followed your instruction to check. It is very helpful.
    when I check program in CO41 (saplcoup), I found that it only check material  status (FG) on top level of BOM .
    Its don't check component material.
    Function CO_ZF_CHECK_MATSTAT_POS  component item in BOM , the program will not check item plant status.
    When I use TX: CO40 to test. I found that CO40 with Program LCOSD1J - CHECK_MATSTAT_COMP have component material status check.
    I'm not sure is that genic CO41 don't have component material status check?
    ths alot
    Marco

  • Error in NWDS Creating activity is not allowed

    Hi all,
    I received this error and can't use the NWDI fully...
    the error message is:
    FAILED: Creating activity is not allowed because workspace is not modifiable
    all properties in .dtc, .metadata, NWDS folder, and project folders are not set to read only..
    where i need to change to work that??
    Thanks in advanced!

    Hi Bruno Ricciardi,
    While creating the project from DTR, did you create the project from Inactive DC's?
    You should not create a project from Active Dc's.
    Regards,
    Jaya.

  • Failed to load resource: the server responded with a status of 405 (Method Not Allowed) XMLHttpRequest cannot load (WCF service URL). Invalid HTTP status code 405

    Hi,
    while consuming the  WCF service POST method Jquery, getting error in Chrome and firefox, in IE  Its working fine.
    ERROR:Failed to load resource: the server responded with a status of 405 (Method Not Allowed)  XMLHttpRequest cannot load (WCF service URL). Invalid HTTP status code 405.
    Jquery used to call:
    $.support.cors = true
            $.ajax({
                type: "POST",
                url: serviceURL,
                data: JSON.stringify(managedProps),
                useDefaultXhrHeader:false,
                contentType: "application/json; charset=utf-8",
                dataType: "json",
                //processData: true,
                crossDomain: true,
                success: function (data, status, jqXHR) {
                   alert("sucess");
                error: function (xhr) {
                    alert("error");
    WCF sevice Web.config
    <webHttpBinding>
            <!--<binding name="webHttpBindingWithJsonP" transferMode="StreamedRequest" />-->
            <binding name="crossDomain" crossDomainScriptAccessEnabled="true" transferMode="StreamedResponse" />
          </webHttpBinding>
        </bindings>
        <services>
          <service name="DynamicRefinerWCF.DynamicRefiner">
            <endpoint address="" behaviorConfiguration="REST" bindingConfiguration="crossDomain" binding="webHttpBinding" contract="DynamicRefinerWCF.IDynamicRefiner" />
            <endpoint address="mex" binding="mexHttpBinding" contract="DynamicRefinerWCF.IDynamicRefiner" />
            <host>
              <baseAddresses>
                <add baseAddress="http://localhost/example.svc" />
              </baseAddresses>
            </host>
          </service>
        </services>
        <!--<protocolMapping>
            <add binding="basicHttpsBinding" scheme="https" />
        </protocolMapping>-->    
        <!--<serviceHostingEnvironment aspNetCompatibilityEnabled="true" multipleSiteBindingsEnabled="true" />-->
      </system.serviceModel>
      <system.webServer>
        <!--<modules runAllManagedModulesForAllRequests="true"/>-->
        <modules>
          <remove name="WebDAVModule" />
        </modules>
        <handlers>
          <remove name="WebDAV" />
        </handlers>
        <directoryBrowse enabled="true" />
        <httpProtocol>
          <customHeaders>
            <add name="Access-Control-Allow-Origin" value="*"/>
            <add name="Access-Control-Allow-Headers" value="Content-Type"/>
            <add name="Access-Control-Allow-Methods" value="GET, POST, PUT, DELETE, OPTIONS"/>
            <add name="Access-Control-Request-Headers:" value="*" />
            <add name="Access-Control-Request-Method:" value="*" />
          </customHeaders>
        </httpProtocol>
        <!--
            To browse web app root directory during debugging, set the value below to true.
            Set to false before deployment to avoid disclosing web app folder information.
          -->
        <!--<directoryBrowse enabled="true"/>-->
      </system.webServer>
    </configuration>
    Thanks,
    Swathi

    Right on - I have done that a number of times.

  • SRM PO failed: Indicator for GR-based invoice verification used not allowed

    Hi Friends,
        I have an issue with a specific PO failed to transfer from SRM to ECC. We are in ECS scenario, SRM 5.0 Service level 7.0. We are in process of SP upgrade but this issue occured in Production system which is still in old SP level(SP 7.0).
    when I check the App Monitor, I am see the following errors:  but the status shows Auto_Completed
    1. PO: Indicator for GR-based invoice verification used not allowed
    2. PO: Instance XXXXXXXXXX of object type PurchaseOrder could not be changed
    3.  PurchOrder XXXXXXXXXX: Purchase order still contains faulty items
    4.  PO XXXXXXXX: Indicator for GR-based invoice verification used not allowed
    I can see the PO copied over to ECC. but status in SRM PO shows 'Error in Process'.
      BBP_PD for object PO shows:  Created, complete, ordered, In Transfer to Execute, Change was Transmitted  as Inactive status.    Transfer Failed shows Active, Document completed, created.
    I checked BP Maintain  for the vendor and PO and its no different than other POs and Vendors except Vendor had 'Goods Receipt based Invoice Verification' indicator checked in SRM.
    I tried to simulate the same Material, Vendor with GR-IV indicator both on and off, it works fine. Ofcourse this is in Quality box with SP 15 level.
    So, I am not sure if SP level upgrade might help it or not? If there are any other means to test, please advise.
    thanks
    Rao

    I was wondering how I could liquidate the PO by either creating a new PO or ??.
    What you could do to revive the PO in question is that after the upgrade, and after a round of background jobs run for CLEAN_REQREQ_UP and BBP_GET_STATUS_2, ask the buyer to make a dummy change to the PO (for example, change the description of the PO) and order again. This would trigger the transfer to the backend again. And hopefully this time, no error would occur.

Maybe you are looking for