Error in Mapping Execution

Hi Experts,
   I am doing the dat file to RFC scenario.. development has been done.
   While testing i am facing the problem with mapping execution. I have tested with single record structure and multiple record structure.. but getting the same error.. pls see the below error.
<!--  Request Message Mapping
  -->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
  <SAP:Category>Application</SAP:Category>
  <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
  <SAP:P1>com/sap/xi/tf/_MM_DATA2RFC_</SAP:P1>
  <SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException:</SAP:P2>
  <SAP:P3>Fatal Error: com.sap.engine.lib.xml.parser.ParserE</SAP:P3>
  <SAP:P4>xception: Invalid char #0x0 (:main:, row:5, col:2~</SAP:P4>
  <SAP:AdditionalText />
  <SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_DATA2RFC_; com.sap.aii.utilxi.misc.api.BaseRuntimeException:Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Invalid char #0x0 (:main:, row:5, col:2~</SAP:Stack>
  <SAP:Retry>M</SAP:Retry>
  </SAP:Error>
I have maintained FCC in configuration...
can any one suggest what would be the problem.
Thanks,
Swetha

Hi Stefen,
  You are absolutely right/correct.. i have saved file in another editor with ANSI.. and triggered the interface but now i am facing the problem with message mapping.. pls see the below error.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!--  Request Message Mapping
  -->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
  <SAP:Category>Application</SAP:Category>
  <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
  <SAP:P1>com/sap/xi/tf/_MM_EMFDATA2RFC_</SAP:P1>
  <SAP:P2>com.sap.aii.mappingtool.tf7.MessageMappingExceptio</SAP:P2>
  <SAP:P3>n: Runtime exception when processing target-field</SAP:P3>
  <SAP:P4>mapping /ns1:Z_H_EMF_RFC/IPFILE1/item[2]/TRMDA; r~</SAP:P4>
  <SAP:AdditionalText />
  <SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_EMFDATA2RFC_; com.sap.aii.mappingtool.tf7.MessageMappingException: Runtime exception when processing target-fieldmapping /ns1:Z_H_EMF_RFC/IPFILE1/item[2]/TRMDA; r~</SAP:Stack>
  <SAP:Retry>M</SAP:Retry>
  </SAP:Error>
can you pls suggest abt the above error.
Thanks,
Swetha

Similar Messages

  • Unexpected error during mapping execution

    Hello,
    we are implementing business intelligence for Siebel 8.1. Having one strange issue and hoping anybody could help us out.
    We are using OWB 10.2.0.1. Certain error appears during mapping execution LOAD_SR which basically loads service requests from Siebel DB to data warehouse.
    The mapping is using two tables as input (S_SRV_REQ and S_SRV_REQ_X) which are joined by S_SRV_REQ.ROW_ID = S_SRV_REQ_X.PAR_ROW_ID (+) using Joiner operator, because I always need extension table (S_SRV_REQ_X) rows either filled either containing only nulls (when there is no corresponding extension row). Sadly, this does not work, during execution it generates:
    Error:
    ORA-00997: illegal use of LONG datatype
    ORA-06512: at "DWH_ADM.LOAD_SR", line 32
    ORA-06512: at "DWH_ADM.LOAD_SR", line 3507
    ORA-06512: at "DWH_ADM.LOAD_SR", line 4553
    ORA-06512: at "DWH_ADM.LOAD_SR", line 9984
    ORA-06512: at line 1
    Warning:
    ORA-00997: illegal use of LONG datatype
    In summary, these join conditions generate same error as above:
    S_SRV_REQ.ROW_ID = S_SRV_REQ_X.PAR_ROW_ID (+)
    S_SRV_REQ.ROW_ID (+) = S_SRV_REQ_X.PAR_ROW_ID (+)
    S_SRV_REQ.ROW_ID = S_SRV_REQ_X.PAR_ROW_ID
    Strangely, when I use join condition S_SRV_REQ.ROW_ID (+) = S_SRV_REQ_X.PAR_ROW_ID, it works. But then right join is used and some records get rejected by joiner operation (those who do not have corresponding rows in extension table).
    Could someone help me with this issue?
    Any feedback would be greatly appreciated. Thank you for your time reading this!
    Edited by: user8872556 on Sep 28, 2011 2:21 AM
    Edited by: user8872556 on Sep 28, 2011 2:23 AM
    Edited by: user8872556 on Sep 28, 2011 2:23 AM

    We still were not able to solve this issue, would greatly appreciate any effort to help us out.

  • Runtime error and mapping execution status

    We have set maximum no of error parameter to = 50. When our mapping encounters an exception like Unable to extend space on some table space and at the time of encoutnering this exception no of error count is less than 50 - mapping returns success status. With the result that execution pipe continues with the next mapping. Though we would like to keep error count to 50 or higher value - so as not to interrupt the pipe if there is an insertion or updation failure but we would like the mapping to stop when space error or such an exception comes. Please let us know how can we achieve this.

    Borkur,
    I believe that if you look at the execution status in Workflow Monitor, you'll see that Workflow handles and reports status correctly within the top level flow and all subprocesses.
    However, OWB Audit information for subflows is NOT registered as expected, the subflows always appear with status successful to me, even when mappings fail. I'm not sure whether it is a bug or that success actually means that the flow has concluded/finished (as opposed to status busy). I've had difficulty with OWB Workflow language before, as eg. the workflow AND operator has nothing to do with execution status logic, only with sequencing (ie. a wait-for-all-before-continuing-operator). The operator name and icon graphics are counter-intuitive to me.
    Regards, Hans Henrik

  • Getting error in mapping execution Invalid CHAR

    hi
    i am having file to RFC scenario, and the input file is an xml file and i am getting erron in mapping as below but when i download the payload and load it in the integration repository mapping tool ,i am able to execute it  succesfully. i think the problem is with the encoding , i tried with processing it in utf-8 and ansi. both the format it is giving the sam error.
    <SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MMMMMMMMM_; com.sap.aii.utilxi.misc.api.BaseRuntimeException:Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Invalid char #0xb (:main:, row:1, col:4~</SAP:Stack>
    regards
    sandeep

    >> This is possible only with PI 7.1 ehp1.
    Yes !Our verstion  is SAP EHP 1 for SAP NetWeaver 7.1 so  how can i do this.
    __instead for fixing in PI i can use the belwo java mapping__
    import java.io.InputStream;
    import java.io.OutputStream;
    import java.util.HashMap;
    import java.util.Map;
    import com.sap.aii.mapping.api.StreamTransformation;
    import com.sap.aii.mapping.api.StreamTransformationConstants;
    import com.sap.aii.mapping.api.StreamTransformationException;
    public final class MyMapping implements StreamTransformation {
        public void execute(InputStream in, OutputStream out)
            throws StreamTransformationException {
            // removing non valid characters
         BufferedReader br = new BufferedReader(in);
         out = stripNonValidXMLCharacters(br.readLine());
            // implement mapping ...
    public String stripNonValidXMLCharacters(String in) {
        StringBuffer out = new StringBuffer(); // Used to hold the output.
        char current; // Used to reference the current character.
         if (in == null || ("".equals(in))) return ""; // vacancy test.
        for (int i = 0; i < in.length(); i++) {
        current = in.charAt(i); // NOTE: No IndexOutOfBoundsException caught here; it should not happen.
        if ((current == 0x9) ||
             (current == 0xA) ||
             (current == 0xD) ||
             ((current >= 0x20) && (current <= 0xD7FF)) ||
             ((current >= 0xE000) && (current <= 0xFFFD)) ||
             ((current >= 0x10000) && (current <= 0x10FFFF)))
              out.append(current);
    return out.toString();
    regards
    sandeep
    Edited by: pendyalas on Feb 4, 2011 2:07 PM

  • Error on KEB0 execution ? = Program error: BI service API(component BC-BW)

    Error on KEB0 execution ?
    Iu2019m trying to create a data source on KEB0, but when I try to create, the system give this error:
    u201CProgram error: BI service API (component BC-BW) terminated: MAPI
    Message no. R8401u201D
    Some one knows this message ?
    Thanks !

    Marcus, have you checked following Note?
    504847 - Termination when creating a CO-PA DataSource

  • 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

  • OWB11gR2: Mapping execution in a process flow not visible in OWB Browser

    When a mapping is executed inside a process flow, execution details are not visible in OWB Repository Browser (Control Center reports) - rows processed, errors etc. Mapping row is missing in a log, like it never happened (but it did).
    This auditing information is very important for monitoring reasons (to our customers also) and I just don't get it how this functionality is lost with this version. Another serious bug?

    Hi David,
    I was rather tired and frustrated last evening, so today I noticed some things I didn't yesterday. Your reply gave me a new motivation.
    The conclusion is - a mapping execution in a process flow is logged, but the way activities are displayed in OWB Browser are now different than in previous versions. If I click on 'Execution Job Report' on a process flow, I see all the activities listed except mappings (transformations, assign, file exists, subprocess etc.). If I want to see mapping execution row, I must click on a plus (expand) sign.
    This kind of behavior will make processes with a complex hierarchy (usually we have more than 5 levels of subprocesses) rather vast to monitor. In 10gR2, a drilling down was accomplished by opening a new browser tab (Execution Job Report link) for each subprocess/mapping activity. Now it shall remain on one huge screen (list) that keeps expanding.
    But, if that is the new feature, we shall live with that. If our customers won't like it, they will have to get used to it.
    Thank you for your reply!

  • SMQ2: SYSFAIL Comparison error during the execution of a simple

    Hi folks, I have an operation mapping interface determination with exactly 1 target message of occurence 0..1, that means the mapping output can be nothing for some input messages, that means a target message is not produced so that the output looks like this:
    <?xml version="1.0" encoding="UTF-8"?>
    <Messages><Message1/></Messages>
    In services builder the test finishes successfully when no output message is produced. Also in integration builder i can test the configuration and it works without errors.
    But in runtime the message status is set to "Recorded for Outbound Processing" in SXI_MONITOR and the queue status of the message to "Message has errors". The message stops in SMQ2 with "SYSFAIL" as status and statusText "Comparison error during the execution of a simple" (truncated).
    Anybody experienced the same? How has the output of an operation mapping to look like when no target message is produced?
    I also tested with an output like this when no target is produced, but this results in System error "Split mapping created no messages" in SXI_MONITOR:
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
    <ns0:Message1></ns0:Message1></ns0:Messages>
    Thanks for your help, best regards, Martin

    You seem to be having a multi-mapping involved.
    The operation mapping has to produce at least the start and end tag.....even if the entire message is not present
    Ex:
    <SRC>
    <First>
    <Middle>
    <Last>
    </SRC>
    If above is the structure, then it should be ensured that at least <SRC></SRC> is created by your mapping program....however in your case this is not happening....the tags that you see Messages and Message1 are due to the multi-mapping program and your message should be more than this.
    if you say that occurence is 0..1 then what you can do is map this 0..1 node (root) with at least a blank Constant.
    Unless you create a message (even though empty) you will continue to receive the error message.
    Regards,
    Abhishek.

  • Error in trace log - Error in Mapping EngineODIException

    Hi,
    in the trace log file of OID i am getting the following error:
    Trace Log Started at Mon Sep 24 08:56:34 CEST 2007
    c360f8d929b0427faf0c332e05e78025_85bf9c6eeeec452c8a41c3ab23d03fc6 - Error in Mapping EngineODIException: Exception Connecting to DB :java.sql.SQLException: ORA-01017: invalid username/password; logon denied
    ODIException: Exception Connecting to DB :java.sql.SQLException: ORA-01017: invalid username/password; logon denied
         at oracle.ldap.odip.gsi.DBConnector.connect(DBConnector.java:134)
         at oracle.ldap.odip.prov.ProvWriter.initialise(ProvWriter.java:113)
         at oracle.ldap.odip.engine.ProvThread.mapInitialise(ProvThread.java:642)
         at oracle.ldap.odip.engine.ProvThread.execMapping(ProvThread.java:559)
         at oracle.ldap.odip.engine.ProvThread.runOldVersion(ProvThread.java:543)
         at oracle.ldap.odip.engine.ProvThread.run(ProvThread.java:173)
    java.lang.NullPointerException
         at oracle.ldap.odip.gsi.DBConnector.end(DBConnector.java:210)
         at oracle.ldap.odip.engine.ProvThread.mapEnd(ProvThread.java:718)
         at oracle.ldap.odip.engine.ProvThread.runOldVersion(ProvThread.java:546)
         at oracle.ldap.odip.engine.ProvThread.run(ProvThread.java:173)
    java.lang.NullPointerException
    Exception in Provthread
    It started since I changed password of PORTAL schema.
    everything works but i am wondering what's going on because trc file is now full of those messages
    thanks,
    Branislav

    Hi Sami,
    Check if thse threads can help u,
    Error in BPE Adapter
    BPM - BPE_ADAPTER errors
    BPE Adapter Error
    Exeception during execution error
    ***********Reward points if helpfull************

  • Linkage Error in Mapping and Operation mapping testing for Synchronous in NWDS

    Dear Experts,
    Hope you all are doing fine..
    I am working in a synchronous scenario Proxy via SAP PI 7.4 to JAVA Application supporting JSON.I wrote JAVA program to convert JSON to XML and while performing test for the JAVA mapping in response structure at Operation Mapping,I am receiving following error..
    LinkageError at JavaMapping.load(): Could not load class: json2xml/bin/pack/EsrJson2Xml
    java.lang.NoClassDefFoundError: json2xml/bin/pack/EsrJson2Xml (wrong name: pack/EsrJson2Xml) at
    java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:735)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:716) at java.lang.ClassLoader.defineClass(ClassLoader.java:537)
    at com.sap.aii.ib.server.mapping.execution.MappingLoader.findClass(MappingLoader.java:195)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:372) at java.lang.ClassLoader.loadClass(ClassLoader.java:313)
    I followed some of discussions for the Linkagae error http://scn.sap.com/thread/1418477 but could not help..
    Following are details of my NWDS and PI server:
    SAP NetWeaver Developer Studio
    SAP Enhancement Package 1 for SAP NetWeaver Developer Studio 7.3 SP10 PAT0000
    Compiled the project with JAVA SE-1.6 as well as 1.5
    SAP PO 7.4 Java Only , Release: NW731CORE_10_REL
    SP: 05 JDK: jdk16 Latest Change: 353688
    I have taken care to export all the Jar files used in NWDS to be exported and then imported as Archived files in PI server.
    But could not see the 5 jar files in ESR. I hope there is some issue with name as can see in the log.Can the issue be solved?
    How to test the Operation mapping for Synchronous Message in NWDS?
    Regards
    Rebecca

    Dear Hareesh and Experts,
    I resolved the issue by doing the below steps.
    1. Downloaded the JDK5 and updated the Java console i.e. JRE 15.
    2. I had  created this project using the JAVA Compiler with JAVA SE1.6 initially. Changed this to 1.5 in the Properties of the Project.
    3. Uploaded the project again in ESR Imported Archive.
    The issue is solved.
    Thanks a lot for all your inputs.

  • DIP issue :ActiveChgImp:Error in Mapping EngineODIException: DIP_GEN_INITIA

    Hi,
    I have configured Sync between AD->OID.
    I am getting following Error:
    Trace Log Started at Tue Aug 30 19:06:51 IST 2011
    java.lang.NullPointerException
    at oracle.ldap.odip.engine.ConfigReader.readConfigInfo(ConfigReader.java:264)
    at oracle.ldap.odip.engine.Profile.initConfigInfo(Profile.java:551)
    at oracle.ldap.odip.engine.Profile.initialise(Profile.java:214)
    at oracle.ldap.odip.engine.Profile.initProfile(Profile.java:507)
    at oracle.ldap.odip.engine.SchedEntry.<init>(SchedEntry.java:65)
    at oracle.ldap.odip.engine.Scheduler.addToSyncList(Scheduler.java:975)
    at oracle.ldap.odip.engine.Scheduler.createSyncList(Scheduler.java:492)
    at oracle.ldap.odip.engine.Scheduler.run(Scheduler.java:269)
    Trace Log Started at Tue Aug 30 19:07:03 IST 2011
    ActiveChgImp:Error in Mapping EngineODIException: DIP_GEN_INITIALIZATION_EXCEPTION
    java.lang.NullPointerException
    at oracle.ldap.odip.util.DirUtils.getLastChgNum(DirUtils.java:48)
    at oracle.ldap.odip.gsi.LDAPReader.initAvailableChgKey(LDAPReader.java:933)
    at oracle.ldap.odip.gsi.LDAPReader.initialise(LDAPReader.java:264)
    at oracle.ldap.odip.engine.AgentThread.readerInitialise(AgentThread.java:461)
    at oracle.ldap.odip.engine.AgentThread.mapInitialise(AgentThread.java:510)
    at oracle.ldap.odip.engine.AgentThread.execMapping(AgentThread.java:376)
    at oracle.ldap.odip.engine.AgentThread.run(AgentThread.java:238)
    ActiveChgImp:about to Update exec status
    Updated Attributes
    orclodipLastExecutionTime: 20110830190703
    orclodipConDirLastAppliedChgNum: 62024511
    orclOdipSynchronizationStatus: Mapping Failure, Agent Execution Not Attempted
    orclOdipSynchronizationErrors: Profile Initialization Failure
    Any Pointer on this.
    My Mapping File is :
    DomainRules
    OU=users,OU=Domino User Mig Accounts,DC=atfoods,DC=com:cn=Users, dc=atfoods,dc=com
    OU=TSUsers,OU=HYD Users,OU=HYD Site,DC=atfoods,DC=com:cn=Users, dc=atfoods,dc=com
    #OU=users,OU=Domino User Mig Accounts,DC=atfoods,DC=com:cn=Users, dc=atfoods,dc=com
    #OU=HYD Site,DC=atfoods,DC=com:cn=Users, dc=atfoods,dc=com
    #CN=Users,DC=atfoods,DC=com:cn=Users, dc=atfoods,dc=com
    AttributeRules
    # attribute rule common to all objects
    objectguid: :binary:group :orclobjectguid:string:groupofuniquenames :bin2b64(objectguid)
    ObjectSID: :binary:group:orclObjectSID:string :orclADGroup:bin2b64(ObjectSID)
    distinguishedName: : : :orclSourceObjectDN: :orclADObject
    # attribute rule for mapping windows organizationalunit
    ou: : :organizationalunit:ou: : organizationalunit:
    # attribute rule for mapping directory containers
    cn: : :container: cn: :orclContainer:
    # attribute rule for mapping directordomains
    dc: : :domain: dc: :domain:
    # USER ENTRY MAPPING RULES
    # attribute rule for mapping windows LOGIN id
    sAMAccountName,userPrincipalName: : :user:orclSAMAccountName: :orclADUser:toupper(truncl(userPrincipalName,'@'))+"$"+sAMAccountname
    # attribute rule for mapping Active Directory LOGIN id
    userPrincipalName: : :user:orclUserPrincipalName: :orclADUser:userPrincipalName
    # Map the userprincipalname to the nickname attr by default
    #userPrincipalName: : :user:uid: :inetorgperson:userPrincipalName
    # Map the SamAccountName to the nickname attr if required
    # If this rule is enabled, userprincipalname rule needs to be disabled
    sAMAccountName: : :user:uid: :inetorgperson:
    # Assign the userprincipalname to Kerberaos principalname
    userPrincipalName: : :user:krbPrincipalName: :orcluserv2:trunc(userPrincipalName,'@')+'@'+toupper(truncl(userPrincipalName,'@'))
    # This rule is mapped as SAMAccountName is a mandatory attr on AD
    # and sn is mandatory on OID. sn is not mandatory on Active Directory
    #SAMAccountName: : :user:sn: : person:
    # attributes to map to cn - normally this is the given name
    cn: : :person:cn: :inetorgperson:
    departmentNumber: : :inetorgperson:departmentnumber: :inetorgperson:
    # attribute rule for mapping entry and to create orclUserV2
    # There should be a mapping rule with orcluserv2 objectclass
    # without which the PORTAL may not function properly
    # The next rule shows any attribute of any objectclass can be mapped
    # to different attribute of different objectclass so long as the
    # schema and syntax are compatible.
    #givenName: : :user:displayName: :inetorgperson:
    employeeID: : :user:employeeNumber: :inetOrgPerson:
    physicalDeliveryOfficeName: : :user:physicalDeliveryOfficeName: :organizationalPerson:
    title: : :user:title: :organizationalPerson:
    mobile: : :organizationalperson:mobile: :inetorgperson:
    telephonenumber: : :organizationalperson:telephonenumber: :inetorgperson:
    facsimileTelephoneNumber: : :organizationalperson:facsimileTelephoneNumber: :inetorgperson:
    l: : :user:l: :organizationalperson:
    # mail needs to be assigned valid value for default settings in DAS
    mail: : :user:mail: :inetorgperson:
    #Start of additional attributes added for SSO
    sAMAccountName : : :user:uid: :inetorgperson:truncr(sAMAccountName, '.')+'_'+truncl(sAMAccountName, '.')
    #manager: : :user:manager: :inetorgperson:dnconvert(manager)
    givenName: : :user:givenName: :inetorgperson:
    sn,sAMAccountName: : :user:sn: :inetorgperson:sn|truncl(sAMAccountName, '.')
    displayname: : :user:displayname: :inetorgperson:
    streetAddress: : :user:street: :inetorgperson:
    st: : :user:st: :inetorgperson:
    postalcode: : :user:postalcode: :inetorgperson:
    homephone: : :user:homephone: :inetorgperson:
    department: : :user:departmentnumber: :inetorgperson:
    #End of additonal attributed added for SSO
    # GROUP ENTRY MAPPING RULES
    #cn: : :group:cn: :groupofuniquenames:
    # displayname needs to be assigned a valid value for default settings on DAS
    #SAMAccountName: : :group:displayName: :orclgroup:
    # Description needs tobe assigned a valid value for default settings on DAS
    #Description: : :group:Description: :groupOfUniqueNames:
    #member: : :group:uniquemember: :groupofUniqueNames:
    #managedby: : :group:owner: :groupOfUniqueNames:
    #sAMAccountName: : :group:orclSAMAccountName: :orclADGroup:
    and my activechgimp.properties
    # Profile Name : Name of the profile
    # NOTE - This should be a unique name
    odip.profile.name = ActiveChgImp
    # Profile Password : Specifies the password for accessing this profile
    #odip.profile.password = ProfilePassword
    odip.profile.password = welcome1
    #Welcome123
    # Profile Status : Can be either DISABLE or ENABLE
    # NOTE - Default is DISABLE
    odip.profile.status = ENABLE
    # Synchronization Mode : Specifies the direction of synchronization i.e when the
    # changes are required to be propagated from the 3rd party to OID then the
    # synchronization mode is IMPORT. On the other hand when the changes needs ot be
    # propagated to the 3rd party directory then the synchronization mode is EXPORT.
    odip.profile.syncmode = IMPORT
    # Retry Count : Maximum number of times this profile should be executed
    # in case of an error before the integration server gives up
    # NOTE - the default value is 4
    odip.profile.retry = 5
    # Schedule Interval: The time interval between successive execution of this
    # profile by the integration server.
    # NOTE - the default value is 60 sec. If the previous execution has not
    # compeleted then the next execution will not resume until it completes.
    odip.profile.schedinterval = 60
    # Agent Execution Command : In case of a NON-LDAP interface the command
    # that needs to be executed that would produce the information in LDIF format.
    odip.profile.agentexecommand =
    # Connected Directory Url : The 3rd party directory location
    #odip.profile.condirurl = host:port:sslmode
    odip.profile.condirurl = 192.168.40.56:389:0
    # Connected Directory Account : The Dn or user name used to connect to
    # the 3rd party directory.
    odip.profile.condiraccount = CN=ssoadmintest,OU=SSO,OU=Administrators,DC=atfoods,DC=com
    #ssoadmintest
    # Connected Directory Account : The password used for identification to
    # the 3rd party directory. This password will be prompted to the user.
    odip.profile.condirpassword = Welcome12
    # Interface Type : Whether the LDAP or LDIF or DB or TAGGED format is
    # to be used for data exchange
    # NOTE - Default value is LDAP
    odip.profile.interface = LDAP
    # Config Info : Additional information required for execution of this
    # profile by the integration server.
    # NOTE - The value for this property is the name of the file that contains
    # the additional profile specific information to be used for execution
    odip.profile.configfile = /sso/oracle/infra/ldap/odi/conf/activechg.cfg.master
    # Mapping Rules : Specifies the Mapping Rules to be used for execution
    # of the profile by the integration server.
    # NOTE - The value for this property is the name of the file that contains
    # the domain and attribute mapping rules
    odip.profile.mapfile = /sso/oracle/infra/ldap/odi/conf/activechg.map.master
    # Matching filter Con Dir : Specifies the filter that needs to be
    # applied to the changes that are read from the connected directory
    # before importing to OID
    # NOTE - The default provided here will import from Active Directory the
    # following objectclass:
    # gorup, organizationunit, and user (but not computer)
    #odip.profile.condirfilter = "searchfilter=(|(objectclass=group)(objectclass=organizationalunit)(&(objectclass=user)(!(objectclass=computer))))"
    odip.profile.condirfilter = "searchfilter=(&(objectclass=user)(!(objectclass=computer)))"
    # Matching filter OID : Specifies the filter that needs to be applied
    # to the changes that are read from the OID before exporting to the
    # connected directory
    odip.profile.oidfilter = orclObjectGUID
    # Change Number : Specifies the last applied change number. In case of
    # an export profile this number refer's to OID's last applied change number.
    # However, in case of the import profile this number refers to the last
    # applied change number in the connected directory.
    odip.profile.lastchgnum = 39467751
    # Debug Level : Specifies the debug level of the profile
    odip.profile.debuglevel = 64
    odip.profile.interface = LDAP
    odip.profile.directorytype=ACTIVEDIRECTORY
    ==========
    Profile successfully modified.
    Note: For security reasons it is not recommended to provide a password on the command line, unless you're being prompted for it.

    ldapmody -a -h -p -D -w -f <Filename>
    file
    ===
    dn: orclodipAgentName=ActiveChgImp,cn=subscriber profile,cn=changelog subscriber,cn=oracle internet directory
    modify :add/replace
    Add:orclodipagentconfiginfo
    orclodipagentconfiginfo :[INTERFACEDETAILS]
    orclodipagentconfiginfo :Package: gsi
    orclodipagentconfiginfo :Reader: ActiveChgReader
    orclodipagentconfiginfo :SkipErrorToSyncNextChange: TRUE
    orclodipagentconfiginfo :SearchDeltaSize: 500
    orclodipagentconfiginfo :UpdateSearchCount: 100

  • Logging start & end time of map execution

    Hello,
    I want to log start & end time of execution of my map (OWB 11g), so I've created a table for this purpose and I used it in every map that I want to log time, twice; First for logging start time, and second for end time.
    I pass a constant with SYSTIMESTAMP value through my log table and also name of my map. but the problem is, both of my records' time (start & end) are very near to each other (difference is in milliseconds!) however my map takes time for more than 2 minutes! So, I've changed my map Target Load Order to: [log table for start time] + [Main tables of my map] + [log table for end time]. I've set my map Use Target Load Ordering option True, too.
    Why it doesn't work? Is there any better solution for logging every map execution time in a table, or not?
    Please help me ...
    Thanks.

    To do that, I have created a view that lists all processes that are running or finished. The view contains fields:
    process_name
    process_type (plsqlmap, plsqlprocedure, processflow, etc)
    run_status (success, error, etc)
    start_time
    end_time
    elapse_time
    inserted
    updated
    deleted
    merged
    You could insert into your log table using select x from this view after every map, or, how I do it, is to insert into log table after every process flow. That is, after my process flow is complete I then select all of the details for the maps of the process flow and insert those details into my log table.
    Here is the SQL for my view. This is for 10.2.0.3. For
    CREATE OR REPLACE FORCE VIEW BATCH_STATUS_LOG_REP_V
    AS
    (SELECT PROCESS_NAME,
    PROCESS_TYPE_SYMBOL,
    (CASE
    WHEN RUN_STATUS_SYMBOL IN ('COMPLETE_OK', 'COMPLETE') THEN 'SUCCESS'
    WHEN RUN_STATUS_SYMBOL IN ('COMPLETE_FAILURE') THEN 'ERROR'
    WHEN RUN_STATUS_SYMBOL IN ('COMPLETE_OK_WITH_WARNINGS') THEN 'WARNINGS'
    ELSE 'NA'
    END
    ) RUN_STATUS_SYMBOL,
    START_TIME,
    END_TIME,
    ELAPSE_TIME,
    NUMBER_RECORDS_INSERTED,
    NUMBER_RECORDS_UPDATED,
    NUMBER_RECORDS_DELETED,
    NUMBER_RECORDS_MERGED
    FROM OWB_RUN.RAB_RT_EXEC_PROC_RUN_COUNTS
    WHERE TRUNC (START_TIME) >= TRUNC (SYSDATE) - 3)
    ORDER BY START_TIME DESC;

  • Mapping Execution Status

    Hi,
    When we I want to see the mapping execution status, I used to look into the WB_RT_AUDIT and get the mapping name, map run id, start time, end time and status. Here the status field gives the information as COMPLETE/SUCCESS. This is relating to 9.0.4. Recently, when I upgrade to OWB 10g the same view for the status it gives as 1 and even for error also it shows as 1, how to exactly know the mapping execution status is successful or not. Pls mention the table name and column name to know the status
    Kishan

    Ola Koshan,
    When you look at the audit table WB_RT_AUDIT and check the column RTA_STATUS you'll get a number. When you decode the number you will see wether the mapping is completed, running or ended in an error.
    This can be done like this:
    DECODE (rta_status, 0, 'Running', 1, 'Completed', 2, 'Error','Else')
    Please keep in mind that if you kill a mapping, the status will still be 'running'. This is because the process will not be able to update oracle's repository (because you killed it).
    There is quite a lot you can extract from the Audit tables. I do not quite know what you mean with mentioning the table and column name to know the status... As far is I understood you are looking for the mapping status... Right?
    Regards
    Moscowic

  • Exception during mapping Execution

    Hi Experts
    an Matmas05 xml is coming from MDM system. & it should be posted as Matmas05 in R/3.
    i imported the MDM content in IR. but the fields order in coming Matmas05 xml file and the fields order in
    Matmas05 Idoc  are Not same.
    while Executing Mapping it  throws 'Exception during mapping execution'
    so pls give solution How can i solve...this error
    pls ....urgent.
    thanks & regards
    swapna

    HI swapna,
    The XMl coming from MDM have the different sequence than the original Matmas05 IDOC that you have imported in IR,.
    Lets take it this way as the Original Matmas IDOC structre is not matched up with the sender side Structure.
    You can change the sequence of IDOC XSD file with some tools like Altova xmlSpy and make it same as sender side. Then import the modified XSD file as external defination and use it on sender side.
    On Receiver side your Matmas05 structre sequence should have to be original one.
    Now map the corresponding fields and execute the scenario.
    thanks
    Swarup

  • Error Category Mapping

    Hi all,
      When I try to execute a file to file scenario, I am getting an error. Error Category Mapping, Error Code EXCEPTION_DURING_EXECUTE. The sender service, interface and receiver service, interface is correctly dipslyed in the SXMB_MONI, Monitor for processed XML messages.
    Can any one tell me what is this error and how I can correct it?
    Thanks in Advance.
    Regards,
    Jai Shankar.

    Hi,
    I got the XML message. When I gave it in the Interface Mapping test tab. I got an error
    Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_MM_FILE_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8
    This is the XML format I got from SXMB_MONI
      <?xml version="1.0" encoding="utf-8" ?>
    - <ns:MT_FSOURCE xmlns:ns="urn:Team8:File:File">
    - <Recordset>
    - <Header>
      <EmpId>5601</EmpId>
      <FName>JAI</FName>
      <LName>RAMAKRISHNAN</LName>
      <Project>H</Project>
      </Header>
    - <Header>
      <EmpId>5602</EmpId>
      <FName>JAI</FName>
      <LName>RAMAKRISHNAN</LName>
      <Project>H</Project>
      </Header>
    - <Header>
      <EmpId>5603</EmpId>
      <FName>JAI</FName>
      <LName>RAMAKRISHNAN</LName>
      <Project>H</Project>
      </Header>
      </Recordset>
      </ns:MT_FSOURCE>.
    Kindly tell me what is the error.

Maybe you are looking for