Multi-Mapping Error in PI 7.1 - External Definitions

Hi all,
We have just upgraded to PI 7.1 from 7.0 and run into an issue with message multi-mappings, just wondered if anyone else had met the same issue and worked it out...
When creating a message mapping, we are using as the target an external definition which is defined by an XSD generated by a third party tool (Seeburger).
When I map 1:1 (1 source message to one target message) in the message mapper, all is fine but if I try to create a multi mapping, I get an error. The process is:
a) I have a message mapping with one target message, defined as an External Definition.
b) I then go to Signature tab and add a second target message as an External Definition
c) Click back to Definition tab
d) Get the error "Object XXXXX | YYYYY not found" - where XXXXX is the external def name and YYYYY is the namespace (the SWCV namespace that is, not the XML namespace)
This only seems to happen with External Definitions which are autogenerated and I strongly suspect that is has to do with the fact that the tool that generates them always does so without an XML namespace. I have not proved this though (other Ext Defs with namespaces work for multi-mappings but that is not the only difference so I can't be sure that is the issue but have a strong hunch. This problem did not occur in 7.0.
Anyone got any ideas?
Thanks,
Chris

Hi,
This would not be of much help but, I was able to encounter this issue in XI 3.0.
What we did was to manually edit the XSD and add a namespace to it. I'm not sure if PI 7.1 is able to handle mutiple namespaces, so we limited it to this value <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"> and made sure that this value is used for all the External Definitions used in the multi-mapping.
Regards,

Similar Messages

Multi Mapping error

Hi,
I am required to have a IP recieve 3 IDOC types triggered from BD10 . It can trigger 3 or more IDOCs. For Eg.
1 ARTMAS (only 1) , 2 INFRECs and 1 LIKOND.
If anyone IDOC has come then after a waiting period of 1 minute it should come out of FORK.
My IP is like this.
In a FORK there are 4 branches.
1) ARTMAS receiver
2) Loop(infinite) with INFREC Receiver and a Container Operation to collect all IDOCs
3) Loop(infinite) with LIKOND Receiver and a Container Operation to collect all IDOCs
4) A wait Step with a container operation to initialize endtime variable
necesary branches: 4
The Fork Comes out when the end condition is met ie the End variable is Set or if all the IDOCS have come.
Corelation on MATNR.
Next I have the transormation and send step.
In the MM i have 3 Source and 1 Target.
Artmas 0-1 occurance
INFREC 0 - unbounded
LINKND 0-unbounded
I have created the Target with External Definition and have set the correct occurance in the XSD file
I have mapped the neceessary Segments from INFREC and LIKOND and all the Segments of ARTMAS to the Target structure.
In SXMBMONI it says error on Outbound side and
I see Mapping Exception when I seen in WORKFLOW.
Is my design Correct?
I have tested the Interface & Message Mapping they are correct
Request your help.
John Rajesh
<?xml version="1.0" encoding="utf-8" ?>
- <MappingTrace>
<Trace level="1" type="T">Mapping-Namespace:http://test.com/usa/SapRetail/ARTICLE_CLASSIFY/TESTDEMO</Trace>
<Trace level="1" type="T">Mapping-Name:IM_ARTMAS04_TO_ZARTMAS04_PUB01</Trace>
<Trace level="1" type="T">Mapping-SWCV:00000000000000000000000000000000</Trace>
<Trace level="1" type="T">Mapping-Type:JAVA</Trace>
<Trace level="1" type="T">Mapping-Program:com/sap/xi/tf/_MM_ARTMAS04_TO_ZARTMAS04_PUB_</Trace>
<Trace level="3" type="T">Multi mapping required.</Trace>
<Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_MM_ARTMAS04_TO_ZARTMAS04_PUB_.</Trace>
<Trace level="3" type="T">Load b8f12d30-2c45-11da-90af-ef160a892024, http://test.com/usa/SapRetail/ARTICLE_CLASSIFY/TESTDEMO, -1, com/sap/xi/tf/_MM_ARTMAS04_TO_ZARTMAS04_PUB_.class.</Trace>
<Trace level="3" type="T">Search com/sap/xi/tf/_MM_ARTMAS04_TO_ZARTMAS04_PUB_.class (http://test.com/usa/SapRetail/ARTICLE_CLASSIFY/TESTDEMO, -1) in swcv b8f12d30-2c45-11da-90af-ef160a892024.</Trace>
<Trace level="3" type="T">Loaded class com.sap.xi.tf._MM_ARTMAS04_TO_ZARTMAS04_PUB_</Trace>
<Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._MM_ARTMAS04_TO_ZARTMAS04_PUB_</Trace>
<Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_MM_ARTMAS04_TO_ZARTMAS04_PUB_</Trace>
<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns4:Messages/ns4:Message1/ZARTMAS04_PUB/IDOC. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:292) at

Check the following
1. Have u mapped the root level element?
2. Inside interface mapping, when u say read interface, is it diplaying both the interface.
Also check ur input
may be u r not providing proper input
Regards,
Prateek

SP14 Multi-mapping - error in receiver idoc adapter

Hi,
I have a scenario where a business service should send some XML to SAP CRM. I get the file via a sender JMS adapter and try to post it to CRM via a receiver IDOC adapter.
I have created a multimapping (1:N - 1 XML file to many Idocs) as should in the repository.
In the configuration under Interface Determination, I have chosen 'RB_SPLIT' and selected the interface multimapping.
It should be pointed out, that when testing both interface and message mapping i get no error. All idocs seem to be created as they should.
When testing the setup 'real life' the message fails. The error message in the monitor says:
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>InterfaceCollection</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to interpret IDoc interface InterfaceCollection</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Notice that the above error is when trying to send only 1 record, which in turn then should result in only 1 idoc.
If trying to send multiple XML records, i get the following error:
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="OUTBINDING">MMF_ENGINETYPE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>A system error occurred in the outbound binding</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
In the monitor in the payload of 'Request message mapping' I see as many Maindocument, Submaindocument pairs as should be Idocs.
Now i really don't know how to interpret the error messages in both cases, so I'm a little lost here...
It should be pointed out that the idoc being used everywhere in this scenario, has not been modified - from all places it is being used (and only exists) in the 'Imported objects | Idocs' place.
Also the Idoc is also being used as Inbound interface - so no mistakes here either.
I really hope someone can help me here, as I'm otherwise pretty stuck in this case.
Best regards,
Daniel

Hi Daniel,
I have exactly the same type of scenario (under SPS14 and now also SPS15), sending an XML message over JMS to XI and trying a multi-mapping to many IDocs (actually a list of orders in XML is mapped to n ORDERS Idocs).
I also face problems doing so, when I use the IDoc Adapter as outbound in the Receiver Agreement. I receive the following error:
CO_TXT_MMF_ENGINETYPE
Messages in multi message format can be sent to one adapter engine only
However, I tested the same scenario by just changing the Receiver Agreement to a File Communication Channel and - surprise, surprise - it works. One file per IDoc is created.
Of course, this is not what we want to accomplish, but when I checked this piece of documentation (sorry another link
http://help.sap.com/saphelp_nw04/helpdata/en/42/ed364cf8593eebe10000000a1553f7/content.htm
the IDoc adapter is not listed in the list of Adapters that are supported. Does that mean, that this feature is not supported for generating IDocs? Maybe that's a question for a SAP OSS Message?
I hope that helped you a little further - if you find out more I'd be happy to learn about it.
regards,
Peter

Multi-Mapping Error after copying into new namespace

Hi everybody,
we got a BPM running using a multi-mapping.
We decided to design new namespaces. After copying every IR object (datatype, message-type, mappings etc.) --> SXMB_MONI shows a mapping-error.
But when I take the payload and test the mapping, everything is fine?
Any ideas?
Regards Mario

Hi,
If your payload has Messages tab remove that..and test the payload.
Payload doesn't have any Messages tab.
Just i have given example payload..this payload two strucures it will split into twofiles..and compare your payload should be like same
<?xml version="1.0" encoding="UTF-8"?>
<STRUCTURE>
<EMP_DETAILS>
 <EMPNO>123<EMPNO>
 <EMPNAME>XYZ<EMPNAME>
<EMP_DETAILS>
<STUDENT_DET>
 <STUO>123<STUNO>
 <STUNAME>XYZ<STUNAME>
</STUDENT_DET>
<STRUCTURE>
Regards,
Venu.

Multi Mapping: Error in If Then condition

Hello Guru's,
My requirement is to populate multiple target objects based on the source field called location. For testing I have tried If Location = india then source objects will be mapped to MT_Tfile1 other wise it should be mapped to MT_Tfile2(while mapping i am concatenating Fname and Lanme to Name to MT_Tfile2) . See the below mapping screen for more details.
I am getting error when i try to do test with some input values.
Not able to figure out what could be the error. Can you pls suggest/help what is the issue here?
Thanks
Arun

Hi Bertoni,
I did the mapping for MT-Tfile2 as well. Pls see the below screens hot.
But with this straight mapping, MT_Tfile2 is not populated for the data entered which is not equal to India. It got worked when changed the context of the filed location to messages, see the below screen.
Can you pls explain the logic behind it? i tried to check with display queue but not able to figure out how it worked.
Thanks
Arun

Multi-mapping activate changes error

Good afternoon!
I want to use multi-mapping to split one IDoc(WBBDLD04) to some xml documents.I want XI to create one xml document per segment E1WBB01 of WBBDLD04 IDoc. I set Occurrence = 0..unbounded for target interface in interface mapping . Then I try to activate changes. IX generate errors:
MaterialMasterRequestMapping | http://sap.com/xi/SBO:
A multi-mapping with multiple source or target interface instances is only recommended with asynchronous interfaces, since only a mapping of this type can be used in the process editor. IDoc WBBDLD.WBBDLD04 | urn:sap-com:document:sap:idoc:messages are not asynchronous abstract interfaces
Mapping program Message Mapping MaterialMaster2SBO_GT2 | http://sap.com/xi/SBO does not match the interface mapping. The number or frequencies of source or target messages for the message mapping are not identical to the number or frequencies of source or target interfaces.
Tell me please, what I do wrong?
Thanks!
Lositskiy Alexandr

Alexandr,
You need to create an Abstract from your IDoc (Message Interface).
To use mutli mapping, you need to create a Business Process. Then in your Business Scenario, use your Business Process and reference your multi map.
Hope this helps.
Regards,
Simon

Error: 1:n multi-mapping using BPM for file to file scenario

Hi. Iu2019m trying to do 1:n multi-mapping using bpm scenario. I use file to file. Input file consists of many records and then I want many record to be transformed into many file at target system. I follow step in http://www.riyaz.net/blog/xipi-1n-multi-mapping-using-bpm/. However, I have a problem when file is retrieved in to XI. It doesnu2019t create any output file.
When I look at SXMB_MONI, it shows u201CNo object type found for the message Check that the corresponding process is activated.u201D Besides, it shows error message "Unable to perform action for selected message" when i clikc at PE in SXMB_MONI.
I have check at many previous posts with the same error message but still couldnu2019t solve it. I already activate my BPM and check that status in SXI_CACHE = 0. There is noting left in change list of my IR and ID.
Here is my design and configuration.
IR
Data Type: DT_file_split -> for both input and output file
Message Type: MT_file_split_sender, MT_file_split_receiver
Message Interface: SI_file_split_in, SI_file_split_out, SI_file_abs_source, SI_file_abs_target
Message mapping: MM_file_split for mapping MT_file_split_sender with MT_file_split_receiver
Interface mapping: OM_file_split
u2022 Source = SI_file_split_out
u2022 Target = SI_file_split_in
u2022 Mapping Program = MM_file_split
BPM following this link http://www.riyaz.net/blog/xipi-1n-multi-mapping-using-bpm/.
ID
Import my Integration process
2 Communication Channel for getting input file (CC_File_split_sender) and creating output file (CC_File_split)
2 Receiver determination:
u2022 Source system to BPM using interface SI_File_Abs_source
u2022 BPM to target system using interface SI_File_Abs_target
1 Interface determination:
u2022 from source system to BPM
u2022 Sender interface: SI_File_Split_Out
u2022 Receiver interface: SI_file_abs_source
1 Sender Agreement
u2022 Commu. Component: Source System
u2022 Using interface: SI_File_Abs_source
u2022 Sender Communication Channel: CC_File_Split_Sender
1 Receiver Agreement
u2022 Sender Communication Component: BPM
u2022 Receiver Communication Component: Target System
u2022 Receiver Interface: SI_File_Split_In
u2022 Receiver Communication Channel: CC_File_Split
Anyone know how to fix this?
Thanks,
Pavin

Hi,
Yes, thats the problem.
You are creating file from test tab of 1..N mapping .
In case of 1..N mappping in mapping Extra tags of messages are addded to the data.As shown here:-
Messages
 Message1
 MessageType
When you use this mapping to generate xml message then it will add additional tags for <Messages> and <Message1>, which is not correct. it should only have structure of you MT.
So remove start and end tag of <Messages> and <Message1> from your data file. Mentioned below in bold.
<xml......>
<Messages>
<Message1>
<MT_...>
</MT_...>
</Message1>
</Messages>
This should solve your problem.
Regards,
Sami.

Error in Multi-mapping without BPM

Hi frnds,
I am doing a scenario File-XI-File. I am using the multi-splitting thing in the Message mapping. I have taken care of all the occurance's and "enhanced" thing in the IR and ID resp. I m using SP16. I want to avoid BPM.
But therez sme error cming up. When I check the MONI, its shwing "No messages created from split mapping" and when I test my interface using the Test Configuration in the ID, its shwing error in the Receiver Determination -- "HTTP connection to ABAP Runtime failed. Error: 403 Forbidden"
I have checked most of the blogs and forum suggestions. I have checked the ICF activations as well ...
So, do come back to me with your valuable suggestions, and I will award them points, if they really help me out.
Thanks and regards.
Neetesh

Hi Neetesh,

When I check the MONI, its shwing "No messages created from split mapping"
For this, Can you check the source XML. Does it contain Tags like <messages> .. If yes, you need to remove them from your source XML.
If i am right, you have copied the XML from the TEST tab of the message mapping and pasted it in a notepad and saved it without making any changes at all..... Just do as i have mentioned above and i am sure you will no more get that error message in your MONI....
Also go through this weblog which talks about multi-mapping without BPM,
/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
Regards,
Abhy

Error wile Outbinding of the message in multi mapping

HI
I have a scenario SIEBEL->XI->R/3
the data from siebel system is send through web services
in xi this data is mapped into 2 IDOCS using multi mapping .
I tested the scenario and i am getting the following error .
<SAP:Code area="OUTBINDING">CO_TXT_MMF_ENGINETYPE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Messages in multi-message format can only be sent to one Adapter Engine</SAP:Stack>

Can some one help with this issue
Thanks
Nikhil

Nikhil,
For IDOC bundling, take a look at this blog and note no : 814393.
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
Regards,
Bhavesh

Error in multi mapping bpm

Hi all,
In bpm, i have used a multi mapping transformation. And I get a error message that ' Cannot produce target element, check whether the source instance is valid' . And my two source messages are valid.
But in message mapping, i have given src1 and src2 as source messages in the same order.
But in the Messages_IN tab of bpm, the order of messages is reversed and it is src2 and src1. Can this be the reason for my mapping error? If so, how to rectify this.
If this is not the case, any more suggestions?

Hi Aarthi,
Check your occurence of Target strucuture migth be 1 to 1 or 1 to Unbounded.U r message mapping doesn't populates the data for u r target strucutre.Test u r mapping by giving the valid data( Which data is pass of mapping validations).
In your mapping go to messages tab and check the sequence of your message types are correct or not.If not choose Message types once in correct sequence.
Cheers
Veera
>>> Reward Points,If it is needful.

Multi-Mapping and Message Split using BPM UDFs Error

hi
As per the below blog
Illustration of Multi-Mapping and Message Split using BPM in SAP Exchange Infrastructure
I have just modified the UDFs(1.selectnodeifA 2.selectNodeifB)
1.selectnodeifA
for(int i=0;i<=n;i++)
if(Name.equals("A"))
result.addValue(Node);
2.selectNodeifB
for(int i=0;i<=n;i++)
if(Name.equals("B"))
result.addValue(Node);
while checking I am getting the following errors
Source code has syntax error:
D:/usr/sap/D10/DVEBMGS01/j2ee/cluster/server0/./temp/classpath_resolver/Mapdc8fa4d0896011dd907d001cc01cef0d/source/com/sap/xi/tf/_bpm_mm_.java:132: cannot resolve symbol
symbol : variable n
location: class com.sap.xi.tf._bpm_mm_
for(int i=0;i<=n;i++)
^
D:/usr/sap/D10/DVEBMGS01/j2ee/cluster/server0/./temp/classpath_resolver/Mapdc8fa4d0896011dd907d001cc01cef0d/source/com/sap/xi/tf/_bpm_mm_.java:140: cannot resolve symbol symbol : variable n
location: class com.sap.xi.tf._bpm_mm_
for(int i=0;i<=n;i++)
^
2 errors
The source code given in the blog is correct ? I thought for loop has not completed
pls help
manian

Hi manian,
I was having a look to Illustration of Multi-Mapping and Message Split using BPM in SAP Exchange Infrastructure blog.
The functions are not the same. I mean, yours and blogs functions.
Each function has two parameters, Name and node. Furtheremore, in the blogs' functions is using arrays and you don't.
So, the right code will be
1.selectnodeifA
for(int i=0;i<=node.length();i++)
if(Name.equals("A"))
result.addValue(Node);
However, if you don't need an advance user defined function as you want to process just one element of the node's queue, you will not need to use for sentence.
Something like:
1.selectnodeifA
// for(int i=0;i<=n;i++)
if(Name.equals("A"))
result.addValue(Node);
Hope it is usefull for you.
Carlos

Error when implementing Multi mapping

Hi all,
I am carrying out a scenario which invloves multi mapping. I have read both the interfaces in Interface mapping and I have chose extended interface determination. But the message is not getting processed successfully. I get an error in SXMB_MONI saying "NO_RECEIVER_FOUND". Could you plz help me regarding this?
Thank you
Indudhar

you have to define a Receiver Determination for the Sender & Interface and specify the Receiver there. Furthermore, you will need an Interface Determination to determine the interface of the outgoing message and the mapping
Finally you will require a Receiver Agreement .
http://help.sap.com/saphelp_nw04/helpdata/en/19/8dba88b1db634f891622e909565f7a/frameset.htm
Note: reward points if solution found helpfull
Regards
Chandrakanth.k

File to HTTP Mapping error in PI 7.1

Hi Team,
In my file to HTTP scenario- Im using file content conversion at source side . under MT , i have used Record node, under Record fileds. At target side I have used External definition. To generate multiple records , Im using 0...unbound occurance in External defination.
Example:
MT_SOURCE
-Record
--fileds
External_Definition
-fileds
After 0..unbound the structures looks like..
Source:
Message
-Messages1
--MT_SOURCE
---Record
fields
Target:
Messages
-Messages1
--ExternalDefinatuion
---fields
Now I record context to Messages1 from MT_SOURCE and mapped with Externl_Definition node. My reguirement is , For every record occurance the target structure should generate . I have changed the occurance in Interface mapping as 0..unbound. BUt when im testing with 2 Records , i got the below error...
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">ADAPTER_NOT_MMF</SAP:Code>
<SAP:P1>PLAINHTTP</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Adapter PLAINHTTP cannot process message packages</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
If I used file adapter at receiver side , the messages are processing successfully , so mapping is correct . If I use HTTP im getting the error in MONI. Can anyone suggest whats the issue is ?
Cant we handle multiple records/messages in HTTP adapter.

Hello,
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">ADAPTER_NOT_MMF</SAP:Code>
<SAP:P1>PLAINHTTP</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Adapter PLAINHTTP cannot process message packages</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
If I used file adapter at receiver side , the messages are processing successfully , so mapping is correct . If I use HTTP im getting the error in MONI. Can anyone suggest whats the issue is ?
Cant we handle multiple records/messages in HTTP adapter.
Multi-mapping is not possible when you use Plain HTTP Adapter. You could use SOAP Receiver Adapter and check Do Not Use SOAP Envelope also make sure that your content-type is correct as checking this option changes the content-type to application/xml.
Hope this helps,
Mark

Multi-Mapping runtime issue

Hi, Friend:
We are using BPM to collect two type of message (Msg1 and Msg2) and map to target message (Msg3),
 ------Receive1-------
Start --Fork(start) Fork(stop) ---Transformation--Send
 ------Receive2-------
When we created all the messages from scratch, the process works, the process worked.
After we use external definition (xsd), it always fails on transformation step.
However,if we put the payload to test in message mapping, it success.
Any thoughts ?
Thanks
Liang

Hi, Praba:
We have tested in both multi-mapping, and also interface mapping by using the same payload the causes error in runtime, they are all fine.
The error happens on tranformation step: some nodes have very simple mapping like one to one, it can not create target node (see attached part of trace).
Once we change the complained node mapping from a constant value, the next test shows next target node can not be produced.
If the node is attribute, only required attribute complains, if the node is element, the node with min occurence of 1 complains
<?xml version="1.0" encoding="utf-8" ?>
- <MappingTrace>
<Trace level="1" type="T">Mapping-Namespace:http://xmlfile2xmlfile</Trace>
<Trace level="1" type="T">Mapping-Name:Im_PBC_Audit</Trace>
<Trace level="1" type="T">Mapping-SWCV:64968F80768C11DCC184FCEB0A01071F</Trace>
<Trace level="1" type="T">Mapping-Step:1</Trace>
<Trace level="1" type="T">Mapping-Type:JAVA</Trace>
<Trace level="1" type="T">Mapping-Program:com/sap/xi/tf/_PBC_Request_Response_AuditMapping_</Trace>
<Trace level="3" type="T">Multi mapping required.</Trace>
<Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_PBC_Request_Response_AuditMapping_.</Trace>
<Trace level="3" type="T">Load 64968f80-768c-11dc-c184-fceb0a01071f, http://xmlfile2xmlfile, -1, com/sap/xi/tf/_PBC_Request_Response_AuditMapping_.class.</Trace>
<Trace level="3" type="T">Search com/sap/xi/tf/_PBC_Request_Response_AuditMapping_.class (http://xmlfile2xmlfile, -1) in swcv 64968f80-768c-11dc-c184-fceb0a01071f.</Trace>
<Trace level="3" type="T">Loaded class com.sap.xi.tf._PBC_Request_Response_AuditMapping_</Trace>
<Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._PBC_Request_Response_AuditMapping_</Trace>
<Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_PBC_Request_Response_AuditMapping_</Trace>
<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Messages/ns0:Message1/ns1:BenefitEnrollment. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
Thanks
Liang

Strange Data Mapping Errors after SEM 6 Upgrade. Please assist.

Hi All, I encountered these sudden Mapping errors after I tried to do Testing in Post Upgrade Sand Box. Here I am trying to to perform Collected Reported Financial Data under Data Collection Method for a particular Company Code 3040. Kindly help me with some quick responses as this is kind of high priority. The errors and the Diagnosis Notes I am unable to follow as I do not where I shall write those Mapping Rules they are referring to. I do not even know if that need to apply any SAP Notes as such. Once again Highly appreciate your quick response and Many Thanks in Advance.
Regards, BIP
Input conversion for field Period Value LC has invalid format Message no. UCT8210 Diagnosis The mapping rule for target field Period Value LC contains a move with a selected Input Conversion indicator. Therefore, the system performs an input conversion prior to creating the target data. However, an error in the input conversion occurred while moving the source key figure to the target key figure Period Value LC. This means that the format used for the input conversion is incompatible with the target data. System Response The system will not perform the move. Procedure Examine the mapping rule for field Period Value LC. Either select the Conversion Exit indicator or deselect the Input Conversion indicator. Execute the method again. -
3040 is incompatible with input format for field /1FB/COMPANY Message no. UCT8258 Diagnosis During execution, the method derives the source selection for source field /1FB/COMPANY from the mapping rule for the target field. 3040 is one of the values that were derived for the source selection. The system requires that this value is in the correct SAP-internal format because the Conversion Exit indicator has been selected in the move operator for field /1FB/COMPANY. However, the value 3040 is incompatible with the SAP-internal format. System Response The system attempts to interpret value 3040 as an external format and convert it to the internal format. If this fails, the system is unable to restrict the source selection using source field /1FB/COMPANY. In this case, the system may read more source data than was originally intended, which can affect performance. Procedure In the log, choose the Source button to display the source selections that are used to read the source data. When this appears, examine values selected for field /1FB/COMPANY. If the correct values were selected, you can ignore this message. To prevent this message from being issued, you can select the indicator in the mapping rule used by source field /1FB/COMPANY. If incorrect values were selected, make sure that the mapping rule used by source field /1FB/COMPANY has been defined correctly. If the mapping rule is correct and value (3040) derived for the source selection does not affect the overall result, you can ignore this message. If the source selection does not contain the value 3040 for field /1FB/COMPANY and, because of this, source data that is supposed to be read is not being read, make sure that the mapping rule has been defined correctly. If the source selection does not contain any value for field /1FB/COMPANY, make an estimation as to how much excess source data is being read and whether this might affect system performance. If you do not expect any performance problems, you can ignore this message. In any event, you have the following alternatives if the mapping rule is defined correctly, but the source selection on field /1FB/COMPANY is unsatisfactory: You can define a source selection for field /1FB/COMPANY in the Customizing settings for the method on the Selection tab page. Then the method uses this source selection instead of the source selection derived from inverse interpretation of the mapping rule. You can implement the Business Add-In (BAdI) UC_DATATRANSFER and use the method INVERT to determine the source selection on field /1FB/COMPANY. Then the method uses the result of the INVERT method for the source selection instead of the source selection derived from inverse interpretation of the mapping rule. -
Cannot derive the source selection from target field Version Message no. UCT8252 Diagnosis Field Version has one of the following roles: Consolidation unit Group currency key Fiscal year Posting period Version To delimit the volume of the source data to be read, the system usually derives the source selection from the target selection of such a field. However, the system cannot derive a source selection from field Version. System Response It is possible that a greater volume of source data is being read than is necessary. This can lead to performance issues. Procedure Check whether a mapping rule is defined for field Version. If a mapping rule is defined, you can disregard this warning message. However, if you discover after method execution that the system did not process a large amount of data, and that system performance was not satisfactory, you may want to examine the source selection by choosing the Source button in the log. If the reason for the disregarded data is that too much source data was read because of the unrestricted selection on the source field (which is linked with target field Versionthrough mapping), choose one of the alternatives below: Change the mapping rule for field Version so that the system can derive a delimiting source selection. Implement the Business Add-In (BAdI) UC_DATATRANSFER with the method INVERT to delimit the selection for the source field that is linked via mapping to the target field Version. -
Cannot derive the source selection from target field Group Currency Message no. UCT8252 Diagnosis Field Group Currency has one of the following roles: Consolidation unit Group currency key Fiscal year Posting period Version To delimit the volume of the source data to be read, the system usually derives the source selection from the target selection of such a field. However, the system cannot derive a source selection from field Group Currency. System Response It is possible that a greater volume of source data is being read than is necessary. This can lead to performance issues. Procedure Check whether a mapping rule is defined for field Group Currency. If a mapping rule is defined, you can disregard this warning message. However, if you discover after method execution that the system did not process a large amount of data, and that system performance was not satisfactory, you may want to examine the source selection by choosing the Source button in the log. If the reason for the disregarded data is that too much source data was read because of the unrestricted selection on the source field (which is linked with target field Group Currency through mapping), choose one of the alternatives below: Change the mapping rule for field Group Currency so that the system can derive a delimiting source selection. Implement the Business Add-In (BAdI) UC_DATATRANSFER with the method INVERT to delimit the selection for the source field that is linked via mapping to the target field Group Currency
1 is incompatible with input format for field FISCPERIOD Message no. UCT8258 Diagnosis During execution, the method derives the source selection for source field FISCPERIOD from the mapping rule for the target field. 1 is one of the values that were derived for the source selection. The system requires that this value is in the correct SAP-internal format because the Conversion Exit indicator has been selected in the move operator for field FISCPERIOD. However, the value 1 is incompatible with the SAP-internal format. System Response The system attempts to interpret value 1 as an external format and convert it to the internal format. If this fails, the system is unable to restrict the source selection using source field FISCPERIOD. In this case, the system may read more source data than was originally intended, which can affect performance. Procedure In the log, choose the Source button to display the source selections that are used to read the source data. When this appears, examine values selected for field FISCPERIOD. If the correct values were selected, you can ignore this message. To prevent this message from being issued, you can select the indicator in the mapping rule used by source field FISCPERIOD. If incorrect values were selected, make sure that the mapping rule used by source field FISCPERIOD has been defined correctly. If the mapping rule is correct and value (1) derived for the source selection does not affect the overall result, you can ignore this message. If the source selection does not contain the value 1 for field FISCPERIOD and, because of this, source data that is supposed to be read is not being read, make sure that the mapping rule has been defined correctly. If the source selection does not contain any value for field FISCPERIOD, make an estimation as to how much excess source data is being read and whether this might affect system performance. If you do not expect any performance problems, you can ignore this message. In any event, you have the following alternatives if the mapping rule is defined correctly, but the source selection on field FISCPERIOD is unsatisfactory: You can define a source selection for field FISCPERIOD in the Customizing settings for the method on the Selection tab page. Then the method uses this source selection instead of the source selection derived from inverse interpretation of the mapping rule. You can implement the Business Add-In (BAdI) UC_DATATRANSFER and use the method INVERT to determine the source selection on field FISCPERIOD. Then the method uses the result of the INVERT method for the source selection instead of the source selection derived from inverse interpretation of the mapping rule
Input must be in the format ___,___,__~ Message no. 00088 Diagnosis Your entry does not match the specified input format. System Response The entry in this field was rejected. Procedure The entry must comply with the edit format. The following edit format characters have a special meaning: "_" (underscore) There should be an input character at this point; this should be a number for numeric fields. "." (decimal point) (applies to numeric fields) The decimal point occurs here (setting in the user master record). "," (thousands separator) (applies to numeric fields) This separator occurs (optionally) for more than three figures. Depending on the setting in the user master record, it can be a period or a comma. "V" (applies to numeric fields) The operational sign appears here. If used, it must by at the right margin of the field. The sign is either "-" or " "(space). "~" (tilde) (applies to numeric fields) As of and including this character, leading zeros must also be entered. Otherwise, this character has the same meaning as an underscore. Leading zeros need not be entered on the left of the tilde. They are not output at this position. All other characters have their normal meanings and must be entered in the same position as in the edit format.

Hi Dan,
Could you Kiindly advise me where we need to write the Mapping Rules in Consolidation Monitor? All he time the errors refering to Mapping Rules. The only Tab I seen "Mapping" is in Data Basis But as per my Understanding Iwe do not have much to do there as it is system generated Mapping Tab.
Where we actually go and select/deselct those Input Conversion Indicator/ Conversion exit Indicator.
Highly appreciate your advise.
Thanks and Regards,
BIP

Multi-Mapping Error in PI 7.1 - External Definitions

Similar Messages

Maybe you are looking for