Mapping - Occurence

Hi All,
I have a Header and Detail node each containing some sub elements. My requirement is that one header and multiple Detail will be coming as input. For this requirement how should I set the Occurence in Data Type?
Previously I had every thing as 1(Both min & max). Now I changed the Detail occurence to 0..1.
Still only one Detail is produced as target.
Any pointers in this issue?
Any docs or blog reference would be of great help.
Thanks & Regards,
Jai Shnakar.

Hi,
Check you source message are you getting all the detail records. If you are getting all the detail records then there is no problem with the content conversion and the problem might be with the occurence or mapping.
If content conversion is fine then you try giving the occurence for detail as 0.. unbounded. You can also refer to the post by Vijaya. Also check if your mapping is proper.
Thanks,
Prakash

Similar Messages

XI Mapping Occurence

Anybody have any good documentation on "Occurence"?
Thank-You.

Hi,
it's quite simple
Occurence means how many times a given segment (or field)
can occure
for example 1..1 <--this means it can be only one
(if more or less then you will have a mapping error)
0..unbounded <-- this means there can be any number
Regards,
michal

One IDOC to multiple XML messages

Hi! I am using the graphical mapper in XI to map the SHPMNT03 IDOC to an XML message. The IDOC has a shipment node and potentially multiple delivery nodes, for example:
E1EDT20
- E1EDL20
- E1EDL20
- E1EDL20
I need to create one XML message per E1EDL20 node. I figured I could do this in the mapper but when I execute the map for an IDOC with multiple E1EDL20 nodes, I get a 'Cannot cast 2 to boolean' error. The map executes fine when there is a single E1EDL20 in the IDOC.
As always, help is very much appreciated and points awarded.
Thx, Duncan

Hi Duncan,
Can you just check if this is what you have done,
IR
1. Message Mapping -- Occurence of the Destination message type ( file ) is unbounded
2. Interface Mapping -- Occurence of the Destination Interface ( File ) is unbounded
ID
1. No sender communication channel , sender agreement
2. Receiver communcation channel for FIle with appropriate FILE CONSTRUCTION MODE
3. Receiver Determination and Interface Determination with Sender Interface as the IDOC interface and Receiver Interface as the FILE INTERFACE.
I think there is some misunderstanding on this front.
Multimapping will work if you are trying to do an IDOC to FILE with a 1:N split
just check this and let me know if you ve missed something.
Regards,
Bhavesh

BPM :: n To 1 Collected Payload Pattern issue

Hi
I am working on following scenario -->
Web Page --> HTTP Adapter --> XI with BPM ( Using n To 1 Payload Pattern ) --> RFC Adapter --> SAP R/3 --> XI With BPM --> File Adapter --> Legacy System with Response from RFC
Now everything is configured & when first time I executed the scenario it gives me " Green Flag " under Outbound Status for interface from Web Page to XI. Also date format error in next 2 messages. So I corrected the date format & execute it again.
But since from than I am getting " <b>Red Flag</b> " ( <i>Message has error status on outbound side</i> ) under Outbound status. I checked my BPM under MONI also & all the mapping & configuration is fine. Even I made the Overall messages as 1 but still getting the same error.
I am able to see the correlation ID of message also.
Pls. suggest.

Hi
My Scenario is working now & I am able to correlate the payloads on Vendor Name. But I need to clarify the concept of n:1 Pattern.
In my multi-mapping occurence of source message is 0 to N & Target message is 1. Now when I am sending the message in this format ( coming from web page when i am clicking the SUBMIT button two times ) :
<p3:PurOrder_Request_MT xmlns:p3="http://BpmCollectMsg:AsyncSync:AlertMgt">
         <Total_Msgs/>
         <HEADER>
            <DOCDATE/>
            <VENDOR/>
         </HEADER>
         <ITEMS>
            <PURMAT/>
            <NETPRICE/>
            <UNIT/>
            <PRICEUNIT/>
         </ITEMS>
         <Items_Schedule>
            <QUANTITY/>
            <DELIVERYDATE/>
         </Items_Schedule>
      </p3:PurOrder_Request_MT>
<p3:PurOrder_Request_MT xmlns:p3="http://BpmCollectMsg:AsyncSync:AlertMgt">
         <Total_Msgs/>
         <HEADER>
            <DOCDATE/>
            <VENDOR/>
         </HEADER>
         <ITEMS>
            <PURMAT/>
            <NETPRICE/>
            <UNIT/>
            <PRICEUNIT/>
         </ITEMS>
         <Items_Schedule>
            <QUANTITY/>
            <DELIVERYDATE/>
         </Items_Schedule>
      </p3:PurOrder_Request_MT>
I am getting results in same format means two different nodes of " PurOrder_Request_MT ".
But I was expecting results in this format ::
<p3:PurOrder_Request_MT xmlns:p3="http://BpmCollectMsg:AsyncSync:AlertMgt">
         <Total_Msgs/>
         <HEADER>
            <DOCDATE/>
            <VENDOR/>
         </HEADER>
         <HEADER>
            <DOCDATE/>
            <VENDOR/>
         </HEADER>
         <ITEMS>
            <PURMAT/>
            <NETPRICE/>
            <UNIT/>
            <PRICEUNIT/>
         </ITEMS>
      <ITEMS>
            <PURMAT/>
            <NETPRICE/>
            <UNIT/>
            <PRICEUNIT/>
         </ITEMS>
         <Items_Schedule>
            <QUANTITY/>
            <DELIVERYDATE/>
         </Items_Schedule>
      <Items_Schedule>
            <QUANTITY/>
            <DELIVERYDATE/>
         </Items_Schedule>
      </p3:PurOrder_Request_MT>
As in target they are coming as two different payloads & I am calling the RFC one time only. RFC is taking the data of first payload only. Right now my scenario is working more as creating a batch of payloads who has same Vendor Name. But my RFC doesn't take batch of payloads.
Can you pls. explain what exactly the n:1 pattern means.
Best regards
Lalit

"Scheduled for Outbound processing" message

Hi,
My scenario is: R/3 (IDoc Customer) -> XI -> PC (file) and I use a BPM with option "multi to single".
In the Message Monitoring, I have two steps:
1. Idoc DEBMAS06 --> BPM:
status = "Processed successfully". Thus it's ok.
2. BPM --> my PC:
status = "Scheduled for Outbound processing" and in column "outbound" I have not "IENGINE". There is no other error message and obviously no data are sent to my PC.
Have you already seen this message?
And have you a solution?
Note: Last friday, the same scenario was ok. I have just changed some data inside the mapping (occurence was not change).
Mickael.

Hi,
Try resetting the status to "Ready".
If you get SYSFAIL again, try deleting that particular LUW. If there are other messages waiting in the queue, just click on the unlock queue button and the remaining messages will flow thru.
Regards,
Sridhar

File-to-Idoc, work flow trigger

Hi All,
I need on help in taking decision of the following scenario.
1) I have a file contains multiple records
2) If record starts with 00-02 i need to send the information to idoc processing
3) If others (03-04 etc) I need to send the record information to particular mail-ids on base of 03 0r 04.
4) If any record does not supprot mapping then also i need to send ionformation to particular persons.
It would be greate help in taking design decision.
Thanks and regards,
venu.

Hi Manish/ Venu,
The RB SPLIT option is done in the INTERFACE DETERMINATION and not in RECEIVER DETERMINATION.
Let me sum the solution to clarify the doubts,
1. Message Mapping
One between the source file and the destination idoc messagetyep
one between the source file and the destination mail messagetype.
2. Like wise 2 Interface mapping.
occurence of both message types and message interface has to be set to unbounded during message mapping and interface mapping.
Now, in cofiguration XI first does RECEIVER DETERMINATION--> INTERFACE DETERMINATION and then INTERFACE MAPPING.
So, you give the condition in the RECEIVER DETERMINATION on the basis of which the receiver is choosen and then you create the 2 interface determination. one for each Idoc and the mail.
Prior to SP14, when 1:N split was to be done, you had to go for a BPM. Now, the same is not needed due to presence of RB_SPLIT.
Check this link on how RB SPLIT works,
http://help.sap.com/saphelp_nw04/helpdata/en/42/ed364cf8593eebe10000000a1553f7/content.htm
Any further clarification guys??,
Regards,
Bhavesh
Message was edited by: Bhavesh Kantilal

Multiple EDI files at receiver side

Hi,
We have an outbound interface(flat file --> PI --> EDI) where flat file coming in and PI processing it to customers.
Based on a field from input file, i am creating 3 UNH segments in one EDI file. But, we need to create 3 EDI files for each UNH segment.
For eg:
Number(from input file): 001,002,003, for each number I am creating 3 UNHs in one EDI file.
But I need 1 EDI for 001,1 EDI for 002,1 EDI for 003.
Is it possible to create multiple EDI at receiver side.
Please suggest me the possible ways to achieve this requirement.
Regards,
KNR.

Hi Its possible,
-->Number(from input file): 001,002,003, for each number I am creating 3 UNHs in one EDI file.
But I need 1 EDI for 001,1 EDI for 002,1 EDI for 003.
do You have any EDI XML structure in mapping?
In Message mapping signature tab change your mapping occurence 0..unbounded
and in mapping click target structure and click on duplicate subtree .(create 3 times)
and map your structure to 3 different structure of the same target message based on 3 UNHs
it will be basically 1:N mapping without BPM

Number of Item segments determine number of occurences in 1:N multi mapping

I'm trying to split MATMAS05 to multiple occurences of MATMAS05 1:N. The target MATMAS05 I have duplicated it a few times depending on the number of plants.
If E1MARCM-WERKS = 1234 then assign MATMAS05 -> MATMAS05
/ns0:Messages/ns0:Message1/MATMAS05=ifWithoutElse([keepss=false]stringEquals(removeContexts(/ns0:Messages/ns0:Message1/MATMAS05/IDOC/E1MARAM/E1MARCM/WERKS=), const([value=1234])), /ns0:Messages/ns0:Message1/MATMAS05=)
The above logic gives me the error:
11:51:28 Start of test
Compilation of MM_Split_MATMAS05 successful Cannot produce target element /ns0:Messages/ns0:Message1/MATMAS05[2]/IDOC. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd Cannot produce target element /ns0:Messages/ns0:Message1/MATMAS05[2]/IDOC. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
11:51:44 End of test
Could someone kindly advice what is the mistake here?

Hi Abhishek,
The target message in the MM under the tab Messages I have changed the occurence from 1 to 0..unbounded and after that I right clicked and duplicated the subtree for MATMAS05. So now in the MM window it shows as below:
Messages            1:1
Message1          1:1
       MATMAS05      0..unbounded
       MATMAS05      0..unbounded
       MATMAS05      0..unbounded
and my mapping condition is as follows:
/ns0:Messages/ns0:Message1/MATMAS05=ifWithoutElse([keepss=false]stringEquals(removeContexts(/ns0:Messages/ns0:Message1/MATMAS05/IDOC/E1MARAM/E1MARCM/WERKS=), const([value=4510])), /ns0:Messages/ns0:Message1/MATMAS05=)
Regards,
// Saj

Issue with IDOC occurence and SeeBurger message mapping

Hey Guys
While developing a EDI 850 to IDOC scenario i came across this issue with pre-delivered Seeburger mapping(A_850_V4010_to_I_ORDERS05).
I actually need to post multiple IDOC's to SAP system in the same message so i changed the IDOC occurence to unbounded and re-imported that as a .XSD file in Integration repository.
Earlier the pre-delivered message mappings provided by SeeBurger(under SEEBURGER_HIGH-TECH, 1.7.1 of seeburger) was working fine for me since i was posting only 1 IDOC but now the mapping is failing as the IDOC occurence has changed(unbounded).
Is there a way we can do some settings on SeeBurger server or Bic so that we can use the pre-delivered mapping for Multiple IDOC's as well?
I just want to make sure before i start off with doing whole of the mapping manually.
Thanx
Aamir

Thanx for the input guys
@Deepthi.
Doing whole of mapping manualy is definitely the last option but i m looking for ways to re-use the pre-delivered SeeBurger mapping.
>>Seeburger Mapping is only just to convert XML to EDI and EDI to XML.
Bic mapping designer does this,i m dealing with message mapping of XI(convert source to target) not Bic designer right now,and Bic does more than just XML to EDI and vice versa,it handles other industry standards too.
@Jens
>>The XI message mappings from Seeburger in the Industry solutions are mapping templates
Yeah,but the mapping template i have deals with 850 to ORDERS05,when i change IDOC occurence and re-import it back in Integration repository,it doesn't stays as ORDERS05,it has to be changed to user defined message interface(in my case MI_ORDERS05) so i m unable to use 850 to ORDERS05 template.
@Seshagiri
>>Open the Seeburger SWCV From the IR--goto External Def---Select the right one and copy it and paste it in notepad.
Changing the occurence is not an issue,i want to re-use the pre-delivered mapping in Integration repository,which is not working.
Looks like i need to do it manually
Thanx
Aamir

Issue-Mapping Multiple Source Occurence to Single Target Occurence

Hi Gurus,
I have a requirement where the source has occurence 0 to 4 where as the target has occurence 1 to 1 .
Let the source segment be S where the child elements for S are S1 and S2 .
S1 takes the values 1 , 2 & 3 .
S2 takes the values X , Y & Z .
I need to map S2 to target field T1 if and only if S1 has the value "2" .
How can we achieve this ? I tried using the node functions but couldn't achive as i want the 2nd value of S2 from the given set of values ( X , Y & Z ) .
Please help me out in this issue.
Thanks in advance .
Regards,
Sarat

Hi,
You can use this mapping:
S1 --> removeContext --> equalsS --> ifWithoutElse --> removeContext (used to remove suppressed values) --> T1
constant: 2 -
> / ____________/
S2 > removeContext--
> /
Hope this helps,
Edited by: Mark Dihiansan on Nov 11, 2009 1:44 PM

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

Question on having occurence in operation mapping

Hi Experts,
While configuring operation mapping, for both source and target operations, we can choose occurrence for them.
i have a question that in which scenario we should choice other occurrence (not default 1) for operations.
in message mapping signature tab, we could adjust occurrence for message type to perform 1:n or other mappings.
then what's the difference of uses for these two occurrence setup?

>
Aditya Mutyala wrote:
> Hi Experts,
>
> While configuring operation mapping, for both source and target operations, we can choose occurrence for them.
> i have a question that in which scenario we should choice other occurrence (not default 1) for operations.
>
> in message mapping signature tab, we could adjust occurrence for message type to perform 1:n or other mappings.
> then what's the difference of uses for these two occurrence setup?
I think as per the earlier post it is answered that the occurrence changes are needed in case of N:M mapping or what is called has multimapping.
> in message mapping signature tab, we could adjust occurrence for message type to perform 1:n or other mappings.
> then what's the difference of uses for these two occurrence setup?
as you have asked, the need here is to change the occurrence in operation mapping is for the runtime to understand that there are multiple interface calls to send out messages plus the operation mapping is in a way linked to the message mapping

Mapping: split different nodes into several occurence of a single one

Hello experts,
I would like to do the following mapping :
Source message :
<Employee1>
<P0000>
</P0000>
<P0001>
</P0001>
<Pxxxx>
</Pxxxx>
</Employee1>
And get this result in an Idoc :
<E1PITYP>
<P0000>
</P0000>
</E1PITYP>
<E1PITYP>
<P0001>
</P0001>
</E1PITYP>
<E1PITYP>
<Pxxxx>
</Pxxxx>
</E1PITYP>
I have tried to duplicate subtrees in my Idoc definition to map each node Pxxxx with a duplicate of field E1PITYP, but the Idoc definition is so big that I am lacking of java memory.
Do you have any other clue ?
Many thanks,
Best regards,
Guislain

For graphical mapping, there's no clue.
That's the proper way to do it (duplicate subtree in the target node).
With XSLT/Java mapping, maybe you could accomplish it with something more simple.
Something like:
<xsl:template match="/Employee">
   <IDOC_ROOT_TAG>
      <xsl:for-each select="child::node()">
         <E1PITYP>
            <xsl:copy-of select="."/>
         </E1PITYP>
      </xsl:for-each>
   </IDOC_ROOT_TAG>
</xsl:template>
Regards,
Henrique.

Mapping of Multiple occurences of source field to target

hi,
my scenario is flat file to idoc.
my flat file structure is as below:
docheader
product1
product description1
product2
product description2
in idoc,i need to map product to E1EDP01 and product description to E1EDP19 which occurs inside E1EDP01.
now if i directly map product node to E1EDP01 node and product description to E1EDP19,
Product                     --> E1EDP01
Product description      --> E1EDP19
i will get 2 E1EDP01 nodes .but each E1EDP01 node will be having two E1EDP19 nodes corresponding to incoming 2 product description.
E1EDP01     --> Product1
E1EDP19     --> Product description1
E1EDP19     --> Product description2
E1EDP01     --> Product2
E1EDP19     --> Product description1
E1EDP19     --> Product description2
how to do the mapping such that my first product description goes into first product target mapping and my second product description goes into second product mapping?
E1EDP01     --> Product1
E1EDP19     --> Product description1
E1EDP01     --> Product2
E1EDP19     --> Product description2
thanks,
Anuradha

Could you give us more information posting the MT used for the file?
Do you have always only 2 products in the file?
About mapping I suggest you to see the following blogs:
/people/sravya.talanki2/blog/2005/08/16/message-mapping-simplified--part-i
/people/sravya.talanki2/blog/2005/12/08/message-mapping-simplified-150-part-ii
/people/sravya.talanki2/blog/2006/12/26/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-ii

Multiple occurence of IDOC node for certain input combination in mapping

Hi All,
My scenario is as below:
Input sturucture:
FieldA
FieldB
FieldC
FieldD
FieldX
FieldY
FieldZ
Output structure is IDOC WPUWBW01.
Now field A,B,C and D forms key of my source record. So as far as key remains same i have to post all items in one idoc. I am able to achieve this with combination of split by value Fn and collapse context Fn.
Now in addition to above if my Field B = "1200" and Field Y = "1" it should generate IDOC node twice ...
and if Field B = "1200" and Field Y = "6" it should generate IDOC node once.
Any idea how this can be achieved.
Regards,
Siddhesh S.Tawate
PS: Also let me know how to use the container and queue in UDF's

Now in addition to above if my Field B = "1200" and Field Y = "1" it should generate IDOC node twice ...
and if Field B = "1200" and Field Y = "6" it should generate IDOC node once.
duplicate the IDOC node twice so that you have three IDOC nodes in all.
For two IDOC nodes apply the condition
Field B = 1200
                    ------And ----ifWithoutElse     --------------------TargetIDOCNode
Field Y = 1                     Then(Blank Constant)
For the remaining IDOC node apply the condition:
Field B = 1200
                    ------And ----ifWithoutElse     --------------------TargetIDOCNode
Field Y = 6                     Then(Blank Constant)
You can also try using createIf function....
regards,
Abhishek.

Mapping - Occurence

Similar Messages

Maybe you are looking for