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.

Similar Messages

KP06 Cost Center Budget Planning System error when locking the data records

Hi,
While updating Cost Center Planning system(KP06) its giving the below error:
System error when locking the data records.
Message no. KI502
Diagnosis
The lock to protect the data records being processed could not be set. The
probable reason for this is that the SAP locking table is full and no more
entries can be added.
Procedure
Inform your system administrator immediately
No planning data has been changed
Message no. K8038
Diagnosis
You used Post. While preparing the data for posting, the SAP System
determined that no changes were made in the available databank values.
System Response
A posting activity price is not necessary
Please help me how can we rectify the above error..
Thanks
VS Rao

Hi,
check the locking entries (t-code SM12).
http://help.sap.com/saphelp_erp2004/helpdata/en/37/a2e3ae344411d3acb00000e83539c3/frameset.htm
Best regards, Christian

"Error when reading ATP delta records"

Hi,
I have created Integration models for Location, Product, ATP Check, ATP Configuration, Stock and Sales Order.
After creating IM's when I tried to run ATP on my Sales Order I'm getting error " "Error when reading ATP delta records".
Can anyone provide me why I'm facing this error.
Thanks in Advance.
Ram

Dear Ram,
For the product/locations you are checking, it appears that ATP objects in the liveCache are missing which normally are created automatically when products and locations are created in APO.
I would advise to recreate all needed products and locations.
In APO, i.e. make again an initial data transfer of the master data from R/3. Previously the existing ones should be deleted to be sure that they will be created again. Then the problem should be solved.
If this does not help please check the the connection and LC settings to LDA and please try to restart the livecache. A potential explanation for the error would be an incorrectly maintained LDA connection to liveCache. Please check this by running transaction /SAPAPO/OM13 and selecting the 'checks' section.
The problem with the LDA connection could be e.g. very simple. If you check the table dbcon, which contains the description of the liveCache connections , if the liveCache names for LCA and LDA are different you should ensure, that the connections LCA and LDA are setup for the same liveCache (con_env in dbcon).
I hope this helps.
Regards,
TIbor

Attribute change run fails - "Error when deleting the data record /B05/X.."

Hello,
I get the error message "Error when deleting the data record /B05/X.." on doing the change run.
I have already done RSRV on this objects and found no errors, but still the activation fails.
please give your suggestions ASAP to fix the issue as it is on production system.
Thanks.

Attribute change run could fails due to 2 reasons-
(1) attribute xchange run is already runnnig for any toher object(monitor lock) (check by thi prog-RSDDS_CHANGERUN_MONITOR)
(2) data is loading deleting from the object on which attribut changerun is running.(go in a manage tab and check)
check this two conditions and rerun the attribute changrun again from program - RSDDS_AGGREGATES_MAINTAIN and give the master data name in the selection.
Hope it helps you.

Error when trying multiple inbound interface determination for IDOC

Hi !
I have this scenario: File -> XI -> IDOC.
For each source file, I need to send multiple idoc packages, all to the same business system, but each package should be the result of different interface mappings.
All mappings have same source and target message types...e.g. source: MT_MyFile, target: CREMAS04.
To avoid creating a generic mapping program, we need to duplicate the current mapping program, make it handle the new case, and then add it as second interface mapping in Interface Determination, with same inbound interface, but different interface mapping, without conditions. All interface mapping should execute.
We are receving this error:
<SAP:Code area="IF_DETERMINATION">CX_ID_PLSRV</SAP:Code>
<SAP:P1>Inbound interface was found more than once (for same sender and receiver) for outbound interface urn:xxxxx/xxxx:.MI_xx_xxxxxxxx_xxx_xx</SAP:P1>
<SAP:Stack>Error when determining the inbound interface: Inbound interface was found more than once (for same sender and receiver) for outbound interface urn:xxxxx/xxxx:.MI_xx_xxxxxxxx_xxx_xx Inbound interface was found more than once (for same sender and receiver) for outbound interface urn:xxxxx/xxxx:.MI_xx_xxxxxxxx_xxx_xx</SAP:Stack>
Any clues?
Regards,
Matias.

Hi Satish !
Thanks.
I need to send different IDOCs to SAME business system.
In Interface determination I need this:
Inbound Interface -
Condition -
Interface Mapping
IF_1 no condition M_1
IF_1 no condition M_2
I need to send BOTH IDOC packages to same business system.
But it keeps throwing the posted error.
Regards,
Matias.

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

Error when connecting to JDBC

I wrote a JAVA program to test the connection with Oracle. It worked in NT environment, but it did not in Linux Environment. I got the error message: "IO exception: The Network Adapter could not establish the connection."
Here is JAVA code:
import java.sql.*;
class Employee1
public static void main (String args [])
throws SQLException
try{
Class.forName("oracle.jdbc.driver.OracleDriver");
Connection conn =
DriverManager.getConnection ("jdbc:oracle:thin:@203.149.143.1:1521:ora1",
"dxhub", "manager");
Statement stmt = conn.createStatement ();
ResultSet rset = stmt.executeQuery ("select user_id from user_info");
while (rset.next ())
System.out.println (rset.getString ("user_id"));
catch(Exception e)
System.out.println(e.getMessage());
I think there is nothing wrong with JAVA code. There must be something wrong in the Linux environment. I appreciate your help if someone can give me a little advice.
Tony
null

Perhaps you have't listener
Do you sure what your port 1521 - is open?
I recieve this message only if in my "NMAP <myhost> don't have port 1521 is open
- $ORACLE_HOME/bin/lsnrctl
- start
- exit
And everything - ok
null

Error when uploading multiple bank statement in ff_5.

Hi All,
I got below error when trying to upload multiple Electronic bank statement (BAI format) from presentation server on same day.
Acct 4126735166: Statement 00001 already exists; entry ignored.
I understood that there is already an entry in Table febko.
Note: I cannot change any data in the file before uploading.
Please let me know the way to resolve this issue.
Regads,
Dastagir

Hi Pravin,
I cannot delete any records as the uploaded EBS has correct data.
The following scenario will be helpful to understand the issue clearly.
Suppose I uploaded one BAI format EBS for account number 4126735166 on today morning.
On same day evening I received another EBS file from the same bank for the same account number.
So when I tried to upload the second file for the same date, I get the following error.
Acct 4126735166: Statement 00001 already exists; entry ignored.
I understand that SAP Allows to upload only one EBS for a same Account number & same date.
Is there any other option to upload more than one EBS.
Regards,
Dastagir

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

Data Services IDOC Errors when working with a newl Basic Type

Hello,
Just wondering if anyone else has encountered an issue similar to the one I am dealing with. We are trying to create business partners in SAP CRM from Data Services via IDOC. We are not using the standard IDOC, but instead we are using a new IDOC type.
This IDOC type is generated by SAP CRM automatically through a transaction BDFG. This transaction creates a new basic type for an standard IDOC with the additional fields that we have added through the easy enhancement workbench (EEWB).
The issue that we are having is that when we import the IDOC type into data services and we look at the schema many fields and sub-structures of the IDOC are duplicated. This means that we receive hundreds of errors when we try to validate our data flow. I can delete the duplicated sub structures in my query transformation but then the query transformation and the output schema and the idoc input schema are no longer identical.
I have searched all over oss and different web forums for a solution but no one else it seems has even encountered this error. If anyone else has had a similar issue and can offer help it would be greatly appreciated.
Bill

Issue is resolved.
After importing the meta data for the IDOC into data services I then proceeded to edit out all of the duplicate structures and fields from the IDOC.
After making the IDOC structure in data services identical to the structure of the IDOC in SAP I then proceeded to test this IDOC and it executed successfully.

Error when moving multiple emails from one account to another

I have an IMAP account for one of my emails. I have recently changed web hosting and so changed this to a POP account. I don't want to lose all my emails, which is what happened to another one of my accounts when the web hosting was changed. So have opened a new account on mail which is the POP one. I want move all my emails from the IMAP to the POP. I selected all and clicked move but only half went over, now everytime I try to do the remainder I get an error message just literally saying 'There was an error when trying to move 431 emails across' Or something like that. Why is this happening and is there another way of doing it? It's justw eird that half of them moved fine and the rest stayed.

Try Mail/Mailbox/Export Mailbox which will move the mailbox to your desktop. Then Mail/File/Import Mailbox which will put the e-mails in an Import Folder in On My Mac. That will save the e-mails for you.

Soundbooth error when I try to record - WinFile.cpp-705

We are using Soundbooth on a high school classroom computer. When we try to record from a microphone we get the following error message: ..\..\Src\Win\WinFile.ccp-705
Does anyone know what is causing this error?
The permission rights on school computers are fairly restricted. Our school's Tech Department blames the problem on Quicktime. I think this is a permissions issue.
I would appreciate help solving this problem.
Thanks!

Hi Mahesh --
I have Adobe Captivate 6 and use Windows 7 Enterprise. Below is a screen shot of the error. Unfortunatley, it is in German, but it says : Adobe Captivate can't be started. Check to see if Adobe Captivate is configured to be run in adminstrator mode. If so, configure Microsoft Powerpoint to be run in administrator mode and restart Adobe Captivate.
Thanks again.

Error when maintaining output condition records

Hello experts
I m getting an error while maintaining output condition records using VV11. The error reads as "862 System error: system cannot read the structure for table B567". Can you pls help in identifying the root cause.
I checked that the condition table 567 has he correct fields and the field catalogue has the fields.
Thanks
Regards
Srikkanth

Hello
Try to regenerate the condition table B567 using the report RV12A001.
Use TCode SE38, select usage 'B', table '567' and mark the boxes for following indicator
- dictionary
- reports and screens.
Press execute and re-try by maintaining VV11 for the output.
Regards
JP

Error when executing multiple scenarios with same ProgramID for RFC-JDBC

Hi,
I am working on the RFC-JDBC scenario.
I see the following error in the dev_jrfc.trc file when I try to execute multiple scenarios which are using same program id (different communication channels).
RfcException:
    message: Commit fault: com.sap.aii.af.rfc.afcommunication.RfcChannelMismatchException: Wrong Sender Agreement:The Sender agreement does not have channel CC_SAP_XXXXX configured for the functionmodule Z_XXXXX_SO_CREATE_CHANGE
    Return code: RFC_CLOSED(6)
    error group: 108
    key: RFC_ERROR_INTERNAL
Can one program id be used for multiple scenarios? Or do we need to create a new ProgramId for each scenario.
Any response will be highly appreciated.
Thanks
Shyam

Hello Shyam,
>>>>>>>>Do you think that I still need to create a new Program Id for each of these processes.
You should not use same program ID for different RFC adapters. It is recommended by SAP (check FAQ's on RFC).
Although technically you can use but it gives you unpredictable behaviour based on connection pool.

ORA-01461 Error when mapping table with multiple varchar2(4000) fields

(Note: I think this was an earlier problem, supposed fixed in 11.0, but we are experiencing in 11.7)
If I map an Oracle 9i table with multiple varchar2(4000) columns, targeting another Oracle 9i database, I get the ORA-01461 error (Can't bind a LONG value only for insert into a LONG).
I have tried changing the target columns to varchar2(1000), as suggested as a workaround in earlier versions, all to no avail.
I can have just one varchar2(4000) map correctly and execute flawlessly - the problem occurs when I add a second one.
I have tried making the target column a LONG, but that does not solve the problem.
Then, I made the target database SQL Server, and it had no problem at all, so the issue seems to be Oracle-related.

Hi Jon,
Thanks for the feedback. I'm unable to reproduce the problem you describe at the moment - if I try to migrate a TEXT(5), OMWB creates a VARCHAR(5) and the data migrates correctly!! However, I note from you description that even though the problematic source column datatype is TEXT(5), you mention that there are actually 20 lines of text in this field (and not 5 variable length characters as the definition might suggest).
Having read through some of the MySQL reference guide I note that, in certain circumstances, MySQL actually changes the column datatype specified either at table creation time or when interfacing with other databases ( ref 14.2.5.1 Silent Column Specification Changes and 12.7 Using Column Types from Other Database Engines in the MySQL reference guide). Since your TEXT(5) actually contains 20 lines of text, MySQL (database or JDBC driver .... or both) may be trying to automatically map the specified datatype of the column to a datatype more appropriate to storing 20 lines of text.... that is, to a LONG value in this case. Then, when Oracle is presented with this LONG value to store in a VARCHAR(5) field, it throws the ORA-01461 error. I need to investigate this further, but this may be the case - its the first time I've see this problem encountered.
To workaround this, you could change the datatype of the column to a LONG from within the Oracle Model before migrating. Any application code that accesses this column and expects a TEXT(5) value may need to be adjusted to cope with a LONG value. Is this a viable workaround for you?
I will investigate further and notiofy you of any details I uncover. We will need to track this issue for possible inclusion in future development plans.
I hope this helps,
Regards,
Tom.

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

Similar Messages

Maybe you are looking for