Business Process: Fork: Error when mapping

Hello everybody,
I am not sure if SXMB_MONI_BPE is throwing me an irritating error?
I have an integration process starting with ONE receive step. After the receive step I have a fork (NOT in a block), with two branches! In every branch there is first a transformation step, then a send step
The hierarchy with other words:
1) receive step
2) fork
2.1) branch #1
2.1.1) mapping
2.1.2) send step
2.2) branch #2
2.2.1) mapping
2.2.2) send step
Although then second branch is almost the same as the first branch, I get an mapping error!
Is this maybe because the received message can ONLY BE USED ONCE(in the first branch)?
What could be the reason?
Thanks a lot, Mario

Hi,
It is not required inside the Block. In your case Block can be used for more readability purpose . You can group your related logcial steps within the Block.
For more on Block-
http://help.sap.com/saphelp_nw2004s/helpdata/en/f6/e1283f2bbad036e10000000a114084/frameset.htm
Hope this helps,
Pls acknowledge ,
Regards,
Moorthy

Similar Messages

  • Error when mapping a node with multiple occurence

    Hi,
    When I try to run my process where I have countries defines in a drop down box in the UI. I get the following error when completing this step. The target in the mapping is a dataobject which should be able to occure multiple times.
    Here is the mapping:
    Source:                                          Target:
    Country(Node)                             Country(Node)
           Country(String)
           Code(String)
    com.sap.glx.adapter.api.AdapterException: com.sap.glx.core.kernel.api.TransitionRollbackException: Exception during prepare, rolling back
    at com.sap.glx.process.adapter.bpmn.impl.BPMNAdapter.startProcesses(BPMNAdapter.java:1444)
    at com.sap.glx.process.adapter.bpmn.impl.BPMNAdapter.startProcesses(BPMNAdapter.java:1540)
    at com.sap.glx.process.impl.ProcessManagerImpl.startProcess(ProcessManagerImpl.java:938)
    at com.sap.glx.process.impl.ProcessManagerBean.startProcess(ProcessManagerBean.java:372)
    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.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
    at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
    at $Proxy453.startProcess(Unknown Source)
    at com.sap.tc.bpem.wdui.procstarter.procstarter.comp.ProcStarterComp.startProcess(ProcStarterComp.java:377)
    at com.sap.tc.bpem.wdui.procstarter.procstarter.comp.wdp.InternalProcStarterComp.startProcess(InternalProcStarterComp.java:175)
    at com.sap.tc.bpem.wdui.procstarter.procstarter.comp.ProcStarterCompView.onActionStartProcess(ProcStarterCompView.java:626)
    at com.sap.tc.bpem.wdui.procstarter.procstarter.comp.wdp.InternalProcStarterCompView.wdInvokeEventHandler(InternalProcStarterCompView.java:325)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:131)
    at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:72)
    at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:156)
    at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.execute(ProcessingEventPhase.java:91)
    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:468)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:52)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1505)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1319)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToApplicationDoProcessing(AbstractExecutionContextDispatcher.java:154)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForAppProcessing.doService(DispatchHandlerForAppProcessing.java:35)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:116)
    at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToApplicationDoProcessing(ExecutionContextDispatcher.java:114)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:80)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:571)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:602)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:523)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:270)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:729)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:256)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:258)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:202)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:116)
    at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToRequestManager(ExecutionContextDispatcher.java:140)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:92)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:104)
    at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
    at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:61)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:466)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:291)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
    at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:240)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
    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.MemoryStatisticFilter.process(MemoryStatisticFilter.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.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
    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:457)
    at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:250)
    at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
    Caused by: com.sap.glx.core.kernel.api.TransitionRollbackException: Exception during prepare, rolling back
    at com.sap.glx.core.kernel.mmtx.AbstractTransactionBase.rollback(AbstractTransactionBase.java:517)
    at com.sap.glx.core.kernel.mmtx.AbstractTransaction.do_prepare(AbstractTransaction.java:174)
    at com.sap.glx.core.kernel.mmtx.AbstractTransaction.commit(AbstractTransaction.java:77)
    at com.sap.glx.process.adapter.bpmn.impl.BPMNAdapter.startProcesses(BPMNAdapter.java:1429)
    ... 100 more
    Caused by: com.sap.glx.core.kernel.api.TransitionRollbackException: Exception during prepare, rolling back
    at com.sap.glx.core.kernel.mmtx.AbstractTransactionBase.rollback(AbstractTransactionBase.java:517)
    at com.sap.glx.core.kernel.mmtx.AbstractTransaction.do_prepare(AbstractTransaction.java:174)
    at com.sap.glx.core.kernel.mmtx.AbstractTransaction.commit(AbstractTransaction.java:77)
    at com.sap.glx.core.kernel.mmtx.PrimaryTransaction.inPrepare(PrimaryTransaction.java:88)
    at com.sap.glx.core.kernel.mmtx.AbstractTransaction.do_prepare(AbstractTransaction.java:172)
    ... 102 more
    Caused by: com.sap.glx.core.kernel.api.TransitionException: An exception occurred while executing the script "_Create_Customer:START_CONTROL_EVENT_Start_0(
          com.sap.glx.adapter.BPMNAdapter:Request request,
          com.sap.glx.adapter.BPMNAdapter:Event_0_Start_0_be1d130db236787f7569b7e757e720a8 event){
      initiator=request:initiator;
      kicker=request:kicker;
      parent=new com.sap.glx.adapter.BPMNAdapter:Instance_0_prcMido_be1d130db236787f7569b7e757e720a8(initiator, null, kicker, false);
      token=new com.sap.glx.adapter.BPMNAdapter:Token_0_prcMido_be1d130db236787f7569b7e757e720a8(parent, 0);
      exit=new com.sap.glx.adapter.BPMNAdapter:Exit();
      exit:addParameter(request);
      exit:addParameter(event);
      exit:onActivation("48EDB5A6AD6960C095D511DDA4DA0013E88242DB", parent, token);
      delete exit;
      controller=new com.sap.glx.adapter.internal.ExceptionAdapter:ExceptionController();
      controller:setContext(token);
      delete controller;
      scope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_8_Create_Customer_be1d130db236787f7569b7e757e720a8(parent);
      role_2=new com.sap.glx.adapter.internal.ContainerAdapter:View_0_Approver_PotentialOwners_be1d130db236787f7569b7e757e720a8(parent, scope, -1, false);
      scope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_0_Create_Customer_be1d130db236787f7569b7e757e720a8(parent);
      role_3=new com.sap.glx.adapter.internal.ContainerAdapter:View_1_Enhance_PotentialOwners_be1d130db236787f7569b7e757e720a8(parent, scope, -1, false);
      scope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_10_Create_Customer_be1d130db236787f7569b7e757e720a8(parent);
      role_4=new com.sap.glx.adapter.internal.ContainerAdapter:View_2_Administrators_be1d130db236787f7569b7e757e720a8(parent, scope, -1, false);
      scope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_1_Create_Customer_be1d130db236787f7569b7e757e720a8(parent);
      role_5=new com.sap.glx.adapter.internal.ContainerAdapter:View_3_Creator_ExcludedOwners_be1d130db236787f7569b7e757e720a8(parent, scope, -1, false);
      scope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_3_Create_Customer_be1d130db236787f7569b7e757e720a8(parent);
      role_6=new com.sap.glx.adapter.internal.ContainerAdapter:View_4_Approver_ExcludedOwners_be1d130db236787f7569b7e757e720a8(parent, scope, -1, false);
      scope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_2_Create_Customer_be1d130db236787f7569b7e757e720a8(parent);
      context_0=new com.sap.glx.adapter.internal.ContainerAdapter:Context_0_DO_Customer2_be1d130db236787f7569b7e757e720a8(parent, scope, 0, false);
      scope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_4_Create_Customer_be1d130db236787f7569b7e757e720a8(parent);
      role_7=new com.sap.glx.adapter.internal.ContainerAdapter:View_5_Create_Customer_In_MDM_PotentialOwners_be1d130db236787f7569b7e757e720a8(parent, scope, -1, false);
      scope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_5_Create_Customer_be1d130db236787f7569b7e757e720a8(parent);
      role_9=new com.sap.glx.adapter.internal.ContainerAdapter:View_7_Enhance_ExcludedOwners_be1d130db236787f7569b7e757e720a8(parent, scope, -1, false);
      scope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_12_Create_Customer_be1d130db236787f7569b7e757e720a8(parent);
      role_8=new com.sap.glx.adapter.internal.ContainerAdapter:View_6_Creator_PotentialOwners_be1d130db236787f7569b7e757e720a8(parent, scope, -1, false);
      scope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_7_Create_Customer_be1d130db236787f7569b7e757e720a8(parent);
      view_11=new com.sap.glx.adapter.internal.ContainerAdapter:View_9_TextVariables_be1d130db236787f7569b7e757e720a8(parent, scope, -1, false);
      scope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_14_Create_Customer_be1d130db236787f7569b7e757e720a8(parent);
      role_10=new com.sap.glx.adapter.internal.ContainerAdapter:View_8_Create_Customer_In_MDM_ExcludedOwners_be1d130db236787f7569b7e757e720a8(parent, scope, -1, false);
      scope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_6_Create_Customer_be1d130db236787f7569b7e757e720a8(parent);
      context_1=new com.sap.glx.adapter.internal.ContainerAdapter:Context_1_DO_Customer_be1d130db236787f7569b7e757e720a8(parent, scope, 0, false);
      message=request:getData();
      mapper=new com.sap.glx.adapter.internal.Transformer:DataMapper();
      yves_in=new com.sap.glx.adapter.internal.Transformer:Data();
      yves_out=new com.sap.glx.adapter.internal.Transformer:Data();
      yves_in:setData("http://mido.se/", "$http://mido.se/:StartProcess2", message, "61302BDB06E4BB8B9F557FC1D1D2ACC9");
      data=context_1:getData();
      scope=new com.sap.glx.adapter.internal.TypeRegistry:GenericScope(null, "872ED00C5EA0B74AE6F92027833B9366");
      copy=scope:copy(data);
      delete scope;
      yves_out:setData("sap.com/glx/", "$sap.com/glx/:DO_Customer", copy, "872ED00C5EA0B74AE6F92027833B9366");
      mapper:map("48EDB5A6AD6960C395D511DD84C80013E88242DB_be1d130db236787f7569b7e757e720a8", yves_in, yves_out);
      data=yves_out:getData("sap.com/glx/", "$sap.com/glx/:DO_Customer", "872ED00C5EA0B74AE6F92027833B9366");
      context_1:setData(data);
      delete yves_in;
      delete yves_out;
      delete mapper;
      delete event;
    at com.sap.glx.core.kernel.execution.transition.ScriptTransition.execute(ScriptTransition.java:69)
    at com.sap.glx.core.kernel.execution.transition.Transition.commence(Transition.java:241)
    at com.sap.glx.core.kernel.mmtx.DirectNestedTransaction.inPrepare(DirectNestedTransaction.java:57)
    at com.sap.glx.core.kernel.mmtx.AbstractTransaction.do_prepare(AbstractTransaction.java:172)
    ... 105 more
    Caused by: com.sap.glx.core.kernel.api.TransitionException: An exception occurred while executing the script command "mapper:map("48EDB5A6AD6960C395D511DD84C80013E88242DB_be1d130db236787f7569b7e757e720a8", yves_in, yves_out)"
    at com.sap.glx.core.kernel.trigger.config.Script.execute(Script.java:675)
    at com.sap.glx.core.kernel.execution.transition.ScriptTransition.execute(ScriptTransition.java:64)
    ... 108 more
    Caused by: java.lang.IllegalStateException: Occurrence violated
    at com.sap.glx.mapping.execution.implementation.node.SdoNode$PrimitiveItemContainer.appendNode(SdoNode.java:372)
    at com.sap.glx.mapping.execution.implementation.assignment.SetAssignment.assign(SetAssignment.java:23)
    at com.sap.glx.mapping.execution.implementation.Interpreter.mapPart(Interpreter.java:145)
    at com.sap.glx.mapping.execution.implementation.Interpreter.mapPart(Interpreter.java:151)
    at com.sap.glx.mapping.execution.implementation.Interpreter.mapPart(Interpreter.java:151)
    at com.sap.glx.mapping.execution.implementation.Interpreter.mapMapping(Interpreter.java:140)
    at com.sap.glx.mapping.execution.implementation.Interpreter.map(Interpreter.java:135)
    at com.sap.glx.core.internaladapter.Transformer$ClassRegistry$MapperClassManager$MapperClassHandler$MapperInvocationHandler.invoke(Transformer.java:1797)
    at com.sap.glx.core.internaladapter.Transformer$TransformerInvocationHandler.invoke(Transformer.java:399)
    at com.sap.glx.core.dock.impl.DockObjectImpl.invokeMethod(DockObjectImpl.java:459)
    at com.sap.glx.core.kernel.trigger.config.Script$MethodInvocation.execute(Script.java:247)
    at com.sap.glx.core.kernel.trigger.config.Script.execute(Script.java:670)

    Hi Michael,
    could you provide much more details about the source and target structures and the mappings you need to define?
    Something like :
    Source:
    Country (single or multiple? )
    ..Country (single or multiple? )
    ..Code (single or multiple? )
    Target
    Country (single or multiple? )  --> does it have the same type as the source node?
    In general If you try to assign a list of values to target which accepts single value you are most likely to get exception like the one given in your post.
    In other words let's assume :
    Country[]     Country
    ..Country------>Country
    ..Code
    this will throw exception at runtime in most of the cases.
    The reason is that the result of select Country/Country is a list with all Countries. And then the engine will try to assign this list to the single valued target node.
    Is this what you have described or it si something different?
    BTW for the example above there is a fix in SP1 and such kind of mappings are marked as erroneous.
    Best Regards,
    Boris

  • Business Transaction Profile - Error when using Z-Transaction Type

    Dear Experts,
    we are using SAP CRM 7.0 (Support Level 0007 - SAPKU70007). I have created a Z-Business Transaction Profile Z_IC_SERVICE.
    SAP Help says:
    Enter the transaction type to be used as a default in your scenario in the IC WebClient. For example, choose the transaction type 0010 (Interaction Record) if an interaction record is to be created automatically. The system creates this interaction record automatically after the interaction has started (for example, after accepting a call). During this, the activity clipboard in the interaction record is filled with the relevant data.
    So when I am using the transaction type 0010 (Interaction Record) in my Business Transaction Profile all is OK that means I can search for accounts and I can confirm them to go on with the process.
    BUT: When I entering here a Z Transaction Type (Z000) the systems shows the errors:
    - Error occurred in class CL_ICCMP_CUCOIREC_IMPL, event InteractionStarted.
    - Error occurred in class CL_ICCMP_CUCOIREC_IMPL, event BPConfirmed.
    Then I have made a copy of the transaction type 0010 (Name of copy: Z010) and tried to use it in my Business Transaction Profile the system says:
    Customizing settings missing. Assign partner functions to Z010
    Anybody know what to do and where to avoid errors? Note 1346892 is obsolete in this case because we already have the highest Support Package Level.
    Best Regards
    Oliver

    Hi yes you were right. In the case of both transaction type I have corrected the customizing parameters in
    SPRO -> Customer Relationship Management -> Interaction Center WebClient -> Business Transaction -> Assign Partner Functions to Business Transactions
    In the case of Transaction Type Z010 I had Z-Partner Functions and and that leaded to the errors:
    - Error occurred in class CL_ICCMP_CUCOIREC_IMPL, event InteractionStarted.
    - Error occurred in class CL_ICCMP_CUCOIREC_IMPL, event BPConfirmed.
    In case of the Transaction TYPE Z000 I forgot to assign the Partner Functions that is why this error appeared:
    Customizing settings missing. Assign partner functions to Z010
    Thread Closed

  • Business Process Engine Error and Adapor Monitor JPR error in PI 7.0 Server

    Hello,
    I have installed PI7.0 Server on windows server. When I use SXMB_IFR tcode I got RWB screen and RWB Business Process Engine is in red. though I have configured automatic workflow customizing through SWF_XI_CUSTOMIZING tcode. Still i am getting BPE is showing Red.
    The Second Error :
    Adaptor Monitor area also I am getting JPR is in Red .
    Could some one please help me what to done on my PI server and how to fix?
    Regards,
    Sankaranarayanan.G
    SapBasisConsultant.

    Hello,
    Thanks for your reply. http://XIHost:Port/ProxyServer/jprselftest   this url what is the Proxy server? Here I am accessing net through some script.  I have maintained Business system also.
    What to be done? SLD is working fine..
    Regards,
    Sankaranarayanan.G
    SAP BASIS CONSULTANT.

  • Business Process Engine error in component monitoring

    Hello,
    i installed a new version of XI.
    when i check the component monitor whit browser i see that Business Process Engine element have RED led.
    If i look the details, then i have the follow element whit yellow status:
    Maintain Prefix Numbers
    Configure RFC Destination
    Schedule Background Job for Missed Deadline     
    Schedule Background Job for Work Items with Errors
    Schedule Background Job for Event Queue
    Schedule background job for clearing repor
    something during configuration?
    thanks for suggestions

    Hi,
    first thing you should try is:
    1. Start transaction SWU3.
    2. Use the button u201CAutomatic workflow customizingu201D
    it's explained [here|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/10bcbd65-64ea-2a10-9a8d-b653b8e0843c] .
    Regards
    Patrick

  • Business View Connector Error When Developing from Client PC

    We upgraded from CE10 to BOXI 3.1 using Crystal Reports 2008 with Business Views.  Now when developing a report using a BV working in Crystal Reports 2008 on the server on which the BV resides all works fine; when we use Crystal from a client PC and start Crystal, get a BV from the server repository as a database connection,generate a simple report, running  the program returns no data but error 'Cannot Open Database' appears followed by 'Unknown Database Connector Error'.  Why is behavior from Crystal on a client PC different than when running Crystal on a PC that is remote-desktopped into the server, and what need I do so we can develop Crystal reports based on BVs from client PCs?

    Hello,
    If you edit reports locally you also need the database client and configured on the local PC also.
    When you use Remote Desktop you are using everything installed on that PC. Remoting in all you are doing is passing the screen updates to your local PC and nothing else.
    Oh, and you should likely install the BOE Client tools on your local PC also.
    Thank you
    Don
    Edited by: Don Williams on Dec 24, 2010 1:44 PM

  • Error when mapping objects

    When mapping tables from the source databaase to the OLAP database I get "An error occurred creating DimensionMapGroup. CIRCUIT_DIM.MAPGROUP1.DIMENSIONMAPGROUP: ***Error occurred in DELETE_MAPPING_GROUP. I am using AWS 10.0.2.0.3. Any help would be appreciated.

    Don't know if you made a mistake in the version, but please refer to here for best versions to be using: http://www.oracle.com/technology/products/bi/olap/collateral/olap_certification.html
    10.2.0.3 with OLAP patch or 10.2.0.4 code stream is best if on 10g.
    Thanks, Laura
    Edited by: Laura McKechnie on Dec 3, 2009 7:50 PM

  • While processing ALEAUD - "Error when locking the audit statistics"

    Hello,
    I am sending out IDOC for HR data and then prcessing ALEAUD inbound idoc immediatley (setting is done in WE21 partner profiles).
    While processing these incomming idocs, I am getting this error "Error when locking the audit statistics for P01LOGSYS1 IMTIMEDEP HRMD_A" for few idocs. e.g. out of 1000 for 100 idocs this error will happen and IDOC goes to status 51.
    If I try to process thes idocs ALEAUD using background processing and if I schedule 2 jobs at a time then I will get same error and IDOC goes to status 51.
    Can someone help me out?

    Hi
    I tried processing the idocs in background processing as you have suggested using program RBDAPP01 (inbound).
    There are 2 options in this program serial processing and parallel processing. When I select serial processing everyhting goes smooth but it takes long time. But when I select parallel processing I get same locking error mentioned above and only few idocs will get processed successfully with status 53 and all other will error out with status 51.
    If I schedule 2  different jobs in background program RBDAPP01 (inbound) using serial processing then same thing will happen.  only few idocs will get processed successfully with status 53 and all other will error out with status 51.
    And I will get locking error ....
    Note 1333417 says, " these IDocs will be processed via background runs of report RBDAPP01 \ RSEOUT00 (using background work processes) in batch mode leaving dialog work processes free for users and mission-critical processes. Hence you will not encounter the resources problems you are currently experiencing. The only other option would be to try increasing the number of available dialog work processes. The number of dialog processes must be greater than or equal to the total of the number of update and background processes per application server and must be configured across all operation mode
    switches (see SAP note 74141). *However when there are a large number of IDocs being processed this is not a practical solution."*
    Does that mean there is no possoble solution for this issue. If I increase dialog work processes will it be helpfull ?

  • Process flow hangs when mapping execution fails

    Hi,
    Has anyone faced the 'process flow hanging' problem after upgrading to OWB 9.2.0.4? Don't know why this is happening again after the upgrade. The audit browser clearly indicates one of the mappings has failed and workflow tables indicate there was a notification upon failure. The process flow runs several sub process flows each containing 5-6 mappings.
    Also, the mapping that failed (due to unique key violations on the target table) executed the post mapping stored procedure although the post mapping run condition was set to 'ON SUCCESS'. Is this the expected behaviour for the post mapping operator when there are database related failures?
    Our environment is OWB 9.2.0.4 on AIX 5.2.
    Database version is 9.2.0.5. We recently upgraded the database from 9.2.0.4 to 9.2.0.5 and OWB from 9.2.0.2.8 to 9.2.0.4. Process flows are executed using sqlplus.
    Thanks,
    Chethan

    Hi,
    I would expect you to have less issues with 9204 as there were some fixes applied. So I have not seen this before.
    To get into the mapping a little bit more, is this a row based mapping that is under the tresshold? In any case, if you specify "on success" I would expect it to only work on success... A database related error will also cause it to get an error, so this is interesting as well.
    Does the error repeat at any case if there is a failure?
    Jean-Pierre

  • Error when mapping an XML coming as in Source Element

    Hi,
    We have a requirement where the XML is sent in an element as given below :
    The Incoming Payload is of the below format :
    Source :
    <?xml version="1.0" encoding="UTF-8"?>
    <ResponsePayload>
       <RespString><?xml version="1.0" encoding="UTF-8"?>
    <Devices>
       <Device>1</Device>
       <Name>1</Name>
    </Devices></RespString>
    </ResponsePayload>
    The target XML is below :
    Target:
    <?xml version="1.0" encoding="UTF-8"?>
    <Devices>
       <Device/>
       <Name/>
    </Devices>
    I used the below xslt mappings in two steps as suggested by Udo .
    Re: Xml String mapped to XML Node
    XSLT Mapping1 :
    <?xml version="1.0" encoding="UTF-8"?>
    <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
         <xsl:output omit-xml-declaration="yes"/>
         <xsl:template match="/">
              <xsl:for-each select="//RespString">
                   <xsl:value-of select="." disable-output-escaping="yes"/>
              </xsl:for-each>
         </xsl:template>
    </xsl:stylesheet>
    XSLT Mapping 2 :
    <?xml version="1.0" encoding="UTF-8"?>
    <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
         <xsl:template match="/">
              <ResponsePayload>
                   <xsl:copy-of select="//Devices"/>
              </ResponsePayload>
         </xsl:template>
    </xsl:stylesheet>
    When executing Iam getting the belwo error :
    javax.xml.transform.TransformerException: javax.xml.transform.TransformerException: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: The processing instruction target matching "[xX][mM][lL]" is not allowed
    cansomeone help me the reason for the error and how I can correct it .
    Thanks
    Rajesh

    Hi Rajesh,
    i can give you different approach...if the sender side is an File adapter and if ur picking the XML or CSV then write a module in sender file adapter to change the XML file.
    Characters like "<" and "&" are illegal in XML elements.
    "<" will generate an error because the parser interprets it as the start of a new element.
    so u need to add "<![CDATA[" and ends with "]]>"......now the data will come into PI as <![CDATA[<?xml version="1.0" encoding="UTF-8"?>]].
    in the target side the data will be passed as <?xml version="1.0" encoding="UTF-8"?>.
    Regards,
    Phani

  • Retrieving SQL error when map failed.

    Hi,
    Is it possible to retrieve the complete error message when a map failed and send it through email? I don't want to logon to the runtime repository (web browser) each time an error occurs.
    Thanks

    Hello, I use a query like this to retrieve error messages:
    select
    x.audit_execution_id task,
    x.parent_audit_execution_id father_task,
    x.task_name,
    x.return_result result,
    x.last_update_date update_date,
    x.elapse seconds,
    round(x.elapse/60,0) minutes,
    x.number_of_task_errors err,
    x.number_of_task_warnings warn,
    err_mess.message
    from rt_owner.wb_rt_audit_executions x,
    (select m.execution_audit_id, m.message_text message
    from RT_OWNER.all_rt_audit_exec_messages m
    union all
    select r.execution_audit_id, e.run_error_message
    from RT_OWNER.all_rt_audit_map_runs r,
    RT_OWNER.all_rt_audit_map_run_errors e
    where r.map_run_id = e.map_run_id (+)
    ) err_mess
    where
    x.audit_execution_id >= (select max (audit_execution_id)
    from RT_OWNER.wb_rt_audit_executions
    where task_name = 'MY_TASK')
    and err_mess.execution_audit_id (+)= x.audit_execution_id
    and x.return_result <> 'OK'
    order by x.audit_execution_id desc;
    The core is the
    select m.execution_audit_id, m.message_text message
    from RT_OWNER.all_rt_audit_exec_messages m
    union all
    select r.execution_audit_id, e.run_error_message
    from RT_OWNER.all_rt_audit_map_runs r,
    RT_OWNER.all_rt_audit_map_run_errors e
    where r.map_run_id = e.map_run_id (+)
    which retrieves errors occurred during map executions.
    If you want to retrieve process errors, you can look at the RAB_RT_EXEC_PROCESS_RUN_ERRORS view.
    I wanted this info (and other) through e-mail too. Previously I did it through an External Process. Now I define these special activities directly in Oracle Workflow.
    I understand that the next release i.e. Paris will add better support for this?
    Hope this helps- Antonio

  • "Exception Processing Message" error when clicking the Accessing Server Data link on the start page

    When I first started the application, I click the Accessing Server Data link on the start page.  I immediately got the error "Exception Processing Message c0000013 Parameters 75b6bf7c 4 75b6bf7c 75b6bf7c in a dialog box titled "Windows - No Disk".  I had to used Task Manager to remove the box after closing Flash Builder 4.  I then tried the video tutorial on "PHP Services in Flash Builder 4".  I keep receiving an error during service introspection trying to connect to the PHP class.  It was the same error as the other individual "Cannot Connect to PHP Service".  So I tried another tutorial and generated a sample PHP class.  I moved a datagrid on to the stage, droped in the getAllItems function, and configured the return type.  However, when I ran the app, I received the same error "Exception Processing Message" again.  I have attached the screenshot of the error in addition to my phpinfo and log files.

    "The exception process message" is definitely a issue. Is it happening consistently, if so can you file a bug at bugs.adobe.com/flex and give out your machine config details, and the error log.
    With regards to generating a new php file and the introspection error that you are getting, looking at the logs it probably is two fold.
    First off the name of the file and the class name should be the same, are you having employeeServices as the name of the class in employeeServices.php file.
    Second, It seems prior to generating this new file, you had a syntax error at line 5.
    It would be easier to figure out what the error is, if you can also attach the php file, by removing any sensitive information in that.
    Hope this helps.
    Thanks
    -Sunil

  • Please help: ORA-04030: Out of Process memory error when starting 9.0.1 iFS

    When starting the 9.0.1 iFS running on a 9.0.1.4 Database and Tru64 5.1 O/S, the following errors are displayed:
    IFS-35205: Failed to get prepared statement
    java.sql.SQLException:ORA-04030: Out of process memory when trying to allocate 1048 bytes (callheap,kghsstk).
    Database has the following parameters:
    shared pool 150M
    java pool 100M
    large pool 5M
    DB Cache 60M
    DB Block Size 8K
    Sort area size 1M
    Server has 1GB ram, 12GB swap.
    Please can anyone help?

    Hi Alan,
    your help with this is most appreciated!
    I ran your suggested generated SQL script, but at first the same problem was occuring with the first ALTER statement that happened to be generated.
    However, your explanation mentioned the view 'odm_publicobject' and although this view wasn't in the resulting SQL, I found that compiling the similarly named views in this order worked...
    ODMV_PUBLICOBJECT
    ODBV_PUBLICOBJECT
    ODMBS_PUBLICOBJECT
    ODMS_PUBLICOBJECT
    ODUS_PUBLICOBJECT
    ODUV_PUBLICOBJECT
    (Perhaps other combinations would have worked, but in anycase certainly some orders didn't work...)
    At this point, running the complete original generated SQL script then worked successfully and low and behold as you predicted, IFS started successfully.
    (I didn't actually bother removing these 6 already re-compiled views from the original script, so they got re-compiled twice...)
    So this means that we can now actually stop and start IFS as required without re-installing IFS everytime - which is obviously great!
    I will certainly be watching out for 9.0.3, but my understanding for the reason we were going with 9.0.1 in the first place was that this was included in the RDBMS CD-pack, whereas I believe from 9.0.2 onwards it was seperately licensed. I will check with our Oracle dba's.
    But at least we can prove in principle now whether it will suit our requirements....
    Once again, many thanks for looking into this at such a deep level - very much appreciated.
    Graham.

  • JDBC to IDoc ( error when mapping multiple JDBC records to IDoc)

    Hi,
    I am working on JDBC to IDoc scenario, I have declared row as 0 to unbounded and by default the IDoc structure is 1..1.
    Inorder to map multiple rows from JDBC to get multiple IDoc's, I have changed the occurrence of IDoc in "Messages" tab of Message mapping to 0 to unbounded.
    I have mapped "row" to "IDoc".
    When I test the mapping, it works fine, giving the same number of IDoc's with that of row.
    When I test end to end, in SXMB_MONI, it gives me following error:
    <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
      <SAP:P1>MSGGUID 54A3A64E895D48EC3F20C69FEFE2E82B: Tag found instead of tag IDOC BEGIN=</SAP:P1>
    can any one help me out with this.
    Thanks in advance.

    Hi Jwalith,
    Check this blog from Michel
    The specified item was not found.
    Make sure that you changed occurance as per this blog.
    hope this is helpful
    regards,
    Venkat.

  • Error when mapping start date to hire date in GTC

    i'm trying to use gtc trusted recon to provision users in OIM. i am trying to include a start date in my flat file and mapping that to Hire Date on the OIM column in the gtc connector.
    i'm seeing the following exception:
    <Mar 28, 2011 2:10:57 PM EDT> <Error> <oracle.iam.reconciliation.impl> <IAM-5010000> <Generic Error/Information: {0}
    oracle.iam.platform.utils.SuperRuntimeException: -9: Attribute field (HIRE_DATE) does not exist in table USR.
         at oracle.iam.reconciliation.dao.ReconActionDao.executeBulkUserMatchCRUD(ReconActionDao.java:697)
    I've tried a couple of different things here. I first tried supplying the start date field in my flat file with my source data format as yyyy/MM/dd hh:mm:ss z
    and the value in the file as 2011/03/29 06:30:00 EDT. when that didn't work, I set the variable in the staging of the gtc to a literal value (2011/03/29 06:30:00 EDT) instead of getting it from source. But in both instances I'm seeing the above exception. anyone seen this before
    thanks

    rajiv, you are saying to create a new user defined field which i would then map my start date field in gtc to?
    first question with this approach is, shouldn't i be able to use the OOTB Hire Date? Or are you saying this is a bug in OIM
    second, i did try your suggestion, but it is still not working. i'm no longer seeing that error, but at the same time i'm not seeing any exceptions in any of the logs

Maybe you are looking for