Error while posting batch managed stock in 107 movement type?

Hi All,
Error while posting batch managed stock in 107 movement type in MIGO, like 'Goods movement not possible with mvmt type 107'
and here in batch tab batch number is not displaying only valuation type is displaying, kindly let me know can it be done by doing any change in field selection with respect to 107 movement type
regards,
Sanjana

Hi,
spro-inventory management-setting for enjoy transaction-setting for goods mvt--field selection per mvt type
107     SGTXT
107     WEMPF
Check here 107 mvt type there or not if not then put.
101     CUSTNAME
101     GRUND
101     SGTXT
101     WEMPF
102     SGTXT
102     WEMPF
103     SGTXT
103     WEMPF
104     SGTXT
104     WEMPF
105     SGTXT
105     WEMPF
106     SGTXT
106     WEMPF
107     SGTXT
107     WEMPF
108     SGTXT
108     WEMPF
109     SGTXT
109     WEMPF
110     SGTXT
110     WEMPF
Regards
Rakesh

Similar Messages

  • Error while posting-(Travel Management)

    Hi Experts,
    I am facing a problem while posting travel expenses to FI,
    when i execute PRFI i am getting a message "For the ISO code INR there is no unique SAP currency code for ALE". It is not an error message and trip will be posted with postable amounts. But when i try to post it in PRRW it is giving an error message "An error occurred in ALE Customizing".
    Please let me know why the system is throwing this error.
    Thanks and Regards,
    Shilpashree

    Hi Ravi Shankar,
    We could solve that ALE Error and now i can post to FI. But now when i create new expense report and settle the same it is taking next posting period automatically and when i post in PRRW it is giving following error.
    Check posting run 0000000042
    E RW609 Error in document: TRAVL 0000000045 AEDCLNT220
    E F5201 Posting period 002 2009 is not open
    Posting run 0000000042 has errors
    I am not able to find the reason for this error. Please let me know how this can be solved.
    Thanks and Regards,
    Shilpashree

  • Error while posting the parked document in ECC 6.0

    Hello ABAPers,
    After upgrade from R/3 4.6c to ECC 6.0, when we try to post the parked documents ,It calls FM :POSTING_INTERFACE_DOCUMENT".
    Inside it a call transaction is done using FBVB which throws error while posting for more than 4 withholding tax types.
    Error : Field WITH_DIALG-WT_BASE(5) does not exist in the screen SAPLFWTD 0100.
    On running BDC in foreground mode ,Error is happening when the withholding dialog opens and screen seems to be small to input all the tax codes i.e it shows only 4-5 rows and hence only 4 tax types passes to the screen and remaining is left out and error is thrown. This results in document not getting posted.
    But in 4.6 c a bigger screen pops up and no error is thrwon.
    We are not able to check FBVB directly, since it does'nt allow Direct call to this transaction.
    We have checked lots of thread and notes ,But nothing seems to be relevant or helpful in our case.
    Could you please help us in resolving this issue/ let us know if any configuration/ screen variant change is required?
    Thanks!
    Regards,
    M M Jaffer.

    Hello Nabheet ,
    It is a standard code. We are calling the FM  'PRELIMINIARY_POSTING_POST_ALL'  for posting the parked document. The FM calls internally another FM 'POSTING_INTERFACE_DOCUMENT'. This calls the transaction FBVB where we get the above error.
    Thanks.

  • Error while posting parked documents

    HI ALL,
    After upgrade when we try to post the parked documents ,It calls FM :POSTING_INTERFACE_DOCUMENT"
    Inside it a call transaction is done using FBVB which throws error while posting for more than 4 withholding tax types.
    Error : Field WITH_DIALG-WT_BASE(5) does not exist in the screen SAPLFWTD 0100.
    On running BDC in foreground mode ,Error is happening when the withholding dialog opens and screen seems to be small to input all the tax codes.
    But in 4.6 c a bigger screen pops up and no error is thrwon.
    We have checked lots of thread and notes ,But nothing seems to be relevant or helpful in our case.
    Please check it.
    Thanks!

    Hi,
    Please follow as given below:
    1. Use T.Code KO31 and enter order and deactivate the control
    2. Then try to post the parked document
    3. And use T.Code KO30 and enter the order to activate the control
    Some times system will check budget availability which already commited for parked documents.
    Hope it will work.
    Chandu

  • BAPI_GOODSMVT_CREATE - Error while posting a Material Document

    Hi Experts,
    We are  trying to do the material document posting using the transaction "MB1C" manually in SAP. The movement type which we are using for the same is "261".  While doing this is, it is asking for a work order number and the Recipient number. We gave the Recipient Number as "123". Material document is created successfully.
    Again using the same transaction  "MB1C" , we are trying to do the reversal of the material document which we posted previously against another work order number for the same material and the serial number if the material is serialised and as well as for the non serialised material.
    Both this case, in SAP the material document is created succesfully. This is done manually in SAP.
    When we are trying to create the material document using the BAPI 'BAPI_GOODSMVT_CREATE', for the above scenario, posting the material document '261' movement type for one work order and the reversal for another work order '262' movement type for the same material (whether it is a serialised or non serialised) we are getting the eror as "RE Qty. transferred exceeded 1 PC: 50,003,695 C001 USED 1200".
    We are passing the following at the item level. MATERIAL Number, Plant, STGE_LOC, ENTRY_QNT, MOVE_TYPE, BATCH, ORDERID, RESERV_NO,  RES_ITEM, ACTIVITY, XSTOB for reversal.
    We are passing the GM_CODE as '05'.
    Please let us know what needs to be changed inorder to create the material document properly without getting errors.
    Thanks in Advance,
    Mohan.

    Hi,
    We fixed this issue by removing the reservation number of the material when we are trying to post the material document with the movement type "262".
    The reason for removing the reservation number for the movement type "262"
    The reservation number is getting created against a work order when we trying to create the work order in IW32. This reservation number is used for validating the stock while we are trying to consume and doing the reversal.
    SAP is allowing us to reverse the consumed quantities only based on the reservartion number and hence we got this error.
    To fix this error, if we are trying to reverse a particular material against a different work order for which it has been consumed previiously, remove the reservation number and item number and try posting the material document.
    Hope this solution will solve your issue:)
    Thanks and Regards,
    Mohan.

  • Error while posting asset aquisition

    Hi to All,
    I am getting following error while posting aquisition entry.
    "Company code 211 manages parallel currencies in Asset Accounting. For each area that posts automatically online to FI, you have to define one dependent depreciation area that adopts both identical values and depreciation terms from depreciation area 01, and which is assigned to currency type 30 and currency GBP. There is no depreciation area of this type defined for depreciation area 01"
    I had made all settings what the error says above but still error persists.
    PLEASE ITS VERY URGENT
    tanuja

    Hi tanuja,
    Please check the setting in the T- code OABT.
    If it helps pls reward some points.
    JS

  • Error while running the Managed server

    Hi
    i am getting the below error while running the Managed server.
    java.lang.IllegalArgumentException: config=oracle.dms.config.DumpConfig@186793e logDir=null agency=oracle.dms.reporter.SpyAgency@181f91a dmsTimer=java.util.concurrent.ScheduledThreadPoolExecutor@95b5c
         at oracle.dms.impl.producer.Dumper.<init>(Dumper.java:100)
         at oracle.dms.app.ServerInitializer.init(ServerInitializer.java:136)
         at oracle.dms.app.BaseInitializer.getInitializer(BaseInitializer.java:360)
         at oracle.dms.app.DmsSpy.init(DmsSpy.java:210)
         at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
         at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
         at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
         at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
         at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
         at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
         at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<Dec 6, 2011 7:47:30 PM IST> <Info> <Deployer> <01hw198371> <managed_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JGJiy3T5EgGqywAhMG1ErYE5000002> <1323181050633> <BEA-149059> <Module dms.war of application DMS Application [Version=11.1.1.1.0] is transitioning from STATE_ADMIN to STATE_PREPARED on server managed_server1.>
    ####<Dec 6, 2011 7:47:30 PM IST> <Info> <Deployer> <01hw198371> <managed_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JGJiy3T5EgGqywAhMG1ErYE5000002> <1323181050711> <BEA-149060> <Module dms.war of application DMS Application [Version=11.1.1.1.0] successfully transitioned from STATE_ADMIN to STATE_PREPARED on server managed_server1.>
    ####<Dec 6, 2011 7:47:30 PM IST> <Error> <Deployer> <01hw198371> <managed_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JGJiy3T5EgGqywAhMG1ErYE5000002> <1323181050726> <BEA-149231> <Unable to set the activation state to true for the application 'DMS Application [Version=11.1.1.1.0]'.
    weblogic.application.ModuleException: [HTTP:101216]Servlet: "Spy" failed to preload on startup in Web application: "dms.war".
    java.lang.IllegalArgumentException: config=oracle.dms.config.DumpConfig@186793e logDir=null agency=oracle.dms.reporter.SpyAgency@181f91a dmsTimer=java.util.concurrent.ScheduledThreadPoolExecutor@95b5c
         at oracle.dms.impl.producer.Dumper.<init>(Dumper.java:100)
         at oracle.dms.app.ServerInitializer.init(ServerInitializer.java:136)
         at oracle.dms.app.BaseInitializer.getInitializer(BaseInitializer.java:360)
         at oracle.dms.app.DmsSpy.init(DmsSpy.java:210)
         at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
         at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
         at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
         at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
         at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
         at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
         at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
         at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
         at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
         at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
         at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: java.lang.IllegalArgumentException: config=oracle.dms.config.DumpConfig@186793e logDir=null agency=oracle.dms.reporter.SpyAgency@181f91a dmsTimer=java.util.concurrent.ScheduledThreadPoolExecutor@95b5c
         at oracle.dms.impl.producer.Dumper.<init>(Dumper.java:100)
         at oracle.dms.app.ServerInitializer.init(ServerInitializer.java:136)
         at oracle.dms.app.BaseInitializer.getInitializer(BaseInitializer.java:360)
         at oracle.dms.app.DmsSpy.init(DmsSpy.java:210)
         at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
         at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
         at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
         at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
         at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
         at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
         at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    can anyone help

    Srinath is 100% correct.
    If the deployment failed, then there will very likely be some mention in the log.
    You state that you checked the log, but you didn't mention whether you found an error, no error, a successful startup, etc. you are providing painfully few details to assist.
    I would bet if you posted your .log and .out logs to Pastebin.com - #1 paste tool since 2002 and provided us links, We would be able to point out the error.
    Lacking that information, my best advice would be to re-install and double-check you're completing all steps in the correct order.
    Also, be sure to always search the product documentation first, the search this forum. For basic issues (e.g., standard installation), there is a high probability that someone else has asked that question.
    I hope that helps,
    -ryan

  • Error while Deploying Performance Management samples in XI R3.0

    Error while Deploying Performance Management samples in XI R3.0
    I get an error when deploying the PM samples. I have set the PM repository pointing to AFDEMO database
    I have used to Java of BO dir as well as the program files\Java (1.6.03)
    I run the runPublishUtil.bat  and get the below error
    Can anyone help me to publish the PM demo's
    Regards
    Ishaq
    Edited by: ishaqbaig on May 10, 2009 1:42 PM

    Error when runPublishUtil,bat
    C:\Program Files\Business Objects\Performance Management 12.0\setup>set JARLOC=..\..\common\4.0\java\lib\
    usage : runPublishUtil.bat [dbusername] [dbuserpassword]
    C:\Program Files\Business Objects\Performance Management 12.0\setup>java -classpath publishUtil.jar;..\..\common\4.0\java\lib\cecore.jar;..\..\common\4.0\java\lib\logging.jar;..\..\common\4.0\java\lib\celib.jar;..\..\common\4.0\java\lib\ceplugins.jar;..\..\common\4.0\java\lib\cesession.jar;..\..\common\4.0\java\lib\corbaidl.jar;..\..\common\4.0\java\lib\ebus405.jar;..\..\common\4.0\java\lib\external\xercesImpl.jar;..\..\common\4.0\java\lib\external\xml-apis.jar;..\..\common\4.0\java\lib\rascore.jar;..\..\common\4.0\java\lib\serialization.jar;..\..\common\4.0\java\lib\cereports.jar com.businessobjects.util.PublishUtil ".\PublishUtil.properties" sa forms45
    caught SDKException
    com.crystaldecisions.sdk.exception.SDKServerException: Enterprise authentication
    could not log you on. Please make sure your logon information is correct. (FWB
    00008)
    cause:com.crystaldecisions.enterprise.ocaframework.idl.OCA.oca_abuse: IDL:img.seagatesoftware.com/OCA/oca_abuse:3.2
    detail:Enterprise authentication could not log you on. Please make sure your logon information is correct. (FWB 00008)
    The server supplied the following details: OCA_Abuse exception 10498 at [.\secpluginent.cpp : 826]  42040 {}
            ...Invalid password
            at com.crystaldecisions.sdk.exception.SDKServerException.map(SDKServerException.java:107)
            at com.crystaldecisions.sdk.exception.SDKException.map(SDKException.java:193)
            at com.crystaldecisions.sdk.occa.security.internal.LogonService.doUserLogon(LogonService.java:701)
            at com.crystaldecisions.sdk.occa.security.internal.LogonService.userLogon(LogonService.java:295)
            at com.crystaldecisions.sdk.occa.security.internal.SecurityMgr.userLogon(SecurityMgr.java:162)
            at com.crystaldecisions.sdk.framework.internal.SessionMgr.logon(SessionMgr.java:422)
            at com.businessobjects.util.PublishUtil.logon(Unknown Source)
            at com.businessobjects.util.PublishUtil.main(Unknown Source)
    Caused by: com.crystaldecisions.enterprise.ocaframework.idl.OCA.oca_abuse: IDL:img.seagatesoftware.com/OCA/oca_abuse:3.2
            at com.crystaldecisions.enterprise.ocaframework.idl.OCA.oca_abuseHelper.read(oca_abuseHelper.java:106)
            at com.crystaldecisions.enterprise.ocaframework.idl.OCA.OCAs._LogonEx4Stub.UserLogonEx4(_LogonEx4Stub.java:80)
            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:585)
            at com.crystaldecisions.enterprise.ocaframework.ManagedService.invoke(ManagedService.java:420)
            at com.crystaldecisions.sdk.occa.security.internal._LogonEx4Proxy.UserLogonEx4(_LogonEx4Proxy.java:222)
            at com.crystaldecisions.sdk.occa.security.internal.LogonService.doLogon(LogonService.java:347)
            at com.crystaldecisions.sdk.occa.security.internal.LogonService.doUserLogon(LogonService.java:676)
            ... 5 more
    Exception in thread "main" java.lang.NullPointerException
            at com.businessobjects.util.PublishUtil.waitForValidInputFRS(Unknown Source)
            at com.businessobjects.util.PublishUtil.main(Unknown Source)
    Edited by: ishaqbaig on May 10, 2009 12:49 PM

  • Error while posting usint tcode f-02 in fi

    Hi all,
    I am getting an error while posting a document using t code f-02.It is allowing me to go through the 3 steps of posting a document  but while saving it gives me the following error message:
    Error accessing function module:fmfk_fikrs_read parameter:ip_fikrsp_fma_objnr
    Message no:f1030
    DIAGNOSIS:
    The application has accessed a funds management or cash management module with parameters messing or defective.
    PROCEDURE:
    Notify your system administrator.
    Hope some body would help me out.
    Thanks

    Hi,
    Not sure if this works out
    try checking img-Financial Accounting-Financial Accounting Global Settings-Company Code-Enter Global Parameters
    double click on company code and see if any thing is assigned in the feild to FM.
    regards
    genie

  • Error while Posting Document in FBV0

    Hi Guys,
    Iam getting following error while Posting Document in FBV0 which is already parked and it is with tax code.
    Error: "No batch input data for screen SAPMF05A 0700"   
    Kindly suggest
    Thanx and Regards
    Munender

    Also have a look at the following notes:-
    =>  Note 26050 - FIPP:Posting not poss. (SAPMF05A,0700,batch input)
    =>  Note 800177 - FB01: No batch input data for SAPMF05A 0700
    thanks
    G. Lakshmipathi

  • Error while posting mb1c

    He seniors,
    I am getting error while posting stock in T. code- MB1C
    Error- G/L account 799999 dose not exists in company code.
    dear seniors please suggest me what is menu path or t. code and what are the settings I should maintain their
    thanks......

    Dear Sundyeep,
    As already explained,please search in google or forum before posting,you can copy paste your error massege in google,it will provide you the relative links.Read the threads at the top of forum.For your error go through this link:-
    CHART OF ACCOUNTS (MOST URGENT)
    Or use Tcode OBC4 and OBC5 to define and assign field status variant to Company Code.
    Thanks,
    Davinder
    Edited by: davinderpalsingh on Sep 5, 2011 3:04 PM

  • Error while posting inventory

    hi all,
    I got an error while posting Inventory at plant level.
    error:
    parameters for plant is not maintain for inventory management.
    Field VM07M-ANZGEB. does not exist in the screen SAPMM07M 0410       
    Field VM07M-GEBEH. does not exist in the screen SAPMM07M 0410     
    is these config issue?
    and how we can do config to resolve this issue.

    You have to maintain Plant Parameters from Inventory side as well in consumption based planning side.
    check out the path,
    SPRO>Materials Management>Consumption Based Planning-->Plant Parameters,
    also
    SPRO>Materials Management>Inventory Magnt and Phy inv.
    -->Plant Parameters.
    Copy, from existing Plant.

  • Serial Number error while posting UD

    Hi all,
    I am getting an error message "Serial number xxxx not suitable for movement type". "Serial number xxxx cannot be used here" while making usage decision for an production material. The error is happening only for the particular GRN. The GRN was done for 251 quantity and the problem is with 97 serial numbers only, for the 154 quantity system did not show any error message.
    First I tried to change the status and update stock details for the serial number thru' IQ02 but there also getting an error message business transaction not allowed.
    Could not change serial no. profile in material master as the particular material has open production orders. Tried to cancel GRN for the material but system is giving the same error "Serial number xxxx not suitable for movement type". "Serial number xxxx cannot be used here". Tried to do posting using the t.code MI10 but there also getting the same error "Serial number xxxx not suitable for movement type". "Serial number xxxx cannot be used here".
    I tried to replicate the error message in development and quality system but could not as system is working fine. The problem occurred only for the select set of serial numbers and not for all.
    When I checked in SCN got an sap note 1229108 in which it is mentioned that the error could be because issuing SL is not mentioned in the order.
    I would like to know whether we can apply sap note directly in production system or not.
    Regards
    V. Srinivasa Ranganath

    Hi Shyam,
    The "97" serial nos are assigned to the same material only. The problem is when the 251 serial numbers were entered at the time of posting GRN, system is updating the stock details only 154 serial numbers only. So when we try to posting in QA32 for 251 quantities system is giving an error "Serial number cannot be used here", "Serial number is not suitable for movement type". Tried to reverse GRN but system is giving same error message.
    Tried changing the status and then update the stock details for 97 serial numbers, system did not allow to enter the stock details. Checked for SAP notes, but they are all already updated in the system. Kindly let me know if I am missing any step or doing something wrong.

  • Error while posting a write up for asset belonging to affiliated company

    Hi,
    I am facing an error while posting a write up for an asset which belong to an affiliated company. Error is
    Transaction type 790 not possible (posting to affiliated company)
    Message no. AA390
    I am using Transaction type 711 which is linked to 790 in custo. Kinldy let me know how to resolve this issue.
    Thanks
    Pragya

    Hi
    According to this note for document type used, we should not select the 'inter company posting' or 'enter trading partner indicator'
    but as i m doing writeup for asset belonging to affiliated company, so i need to set this indicator. the document type used is standard AA
    Is there any other way, to resolve the issue
    Thanks
    Pragya

  • Error while posting depot excise invoice

    Dear SAP Experts,
    We are continually facing the following error while posting "Depot
    Excise Invoice" on Production sever
    "Error in allocating Depot Invoice number interval not found Number
    object J_1IDEPINV"
    Message no is 8I336
    We have already maintained the number interval for the above object i.e
    J_1IDEPINV with respective series group 62.
    Here is the business process:
    1. First, we make transfer posting thr’ MB1B. We get material doc no
    2. Second, we make selection for RG23D for this material doc thr’ J1IJ.
    RG 23D register gets updated
    3. Third, we make ‘verify/post’ thr’ J1IJ itself. Here we are getting the
    error when we post it.
    Please do needful.
    Its an urgent isue
    Regards
    Tushar

    hello,
    In transaction SNRO check number range for object J_1IDEPINV. There you choose number intervals abd check number intervals.
    Regards
    Kedar Kulkarni

Maybe you are looking for