Mapping IDOC to message body

Hi,
Is it possible to map an entire structure into a message body ?
We would normally map to a structure but in this case it will just a message body so we have an structure to go into an unstructured message body.
For example we have a structured file
MAterial Def
     Release
     Version
     Application
          Sender
          Reciever
etc....
the target is simply
Addmessage
     LocationID
     Messagebody
     MessageLabel
Is there a way to easily put everything in the structured message inside the message body ?
Thanks

hi Brian,
I am not sure if it will work in your case but map the Messagebody with the root node which u want to map with which is MAterial Def in your case.
then right click on the source node in the mapping and then click on return xml on that.
hope this helps.
thanks and regards,
Praveen t

Similar Messages

I have a scenario, ECC-PI-Message broker. ECC sending IDOC to PI, PI execute mapping and sending data to Message borker.(with almost one to one mapping)., IDOC(AAE)-PI-JMS. Now my requirement is., from PI after mapping we need to save file in SAP fold

I have a scenario, ECC-PI-Message broker. ECC sending IDOC to PI, PI execute mapping and sends data to Message borker(thru JMS channel).(with almost one to one mapping)., IDOC(AAE)-PI-JMS. Now my requirement is., from PI after mapping we need to create file with same data what ever send to Message broker and put the file in SAP folder without touching mapping. Is it possible? Please advise with the steps. We are using the ICO for this senario. Quick response is appriciated.

Hi Pratik,
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42?quicklink=index&overridelayout=true
This link might help.
regards
Anupam

IDOC in Message mapping

Hi folks,
I am working on file to idoc scenario. I Imported the IDOC to my scenario. In Messaga Mapping IDOC structure displaying fields as a documention. but i need techincal names of those fields.
for Example: In my IDOC 1 field is showing companycode but I want to see that field as a BUKRS.
How to see the technical names of IDOC fields in Message Mapping.
Your help is highly appreciated.
Thanks,
Anitha.

Hi bavesh...
thank you so much for very your quick responses..
i got xsd as source..based on xsd i created external definition for source xsd and i created outbound interface based on source external deifinition MI_OUT_WearUnits.
and i imported Idoc and exported as xsd and changed occurance to unbounded and again imported as external definition.
i did mapping between these two external definitions.
and i selected standard idoc for source and target interface for interface mapping and given message mapping of previous step.
In ID
sender agreement :
 sender service :BS_external
 sender interface :MI_OUT_WearUnits
receiver agreement:
 receiver service :R/3
 receiver interface : standard Idoc
Interface determination:
sender service :BS_external
sender interface :MI_OUT_WearUnits
reciever service :R/3
and clicked create
inbound interface : Standard IDOc
i am not getting Interface mapping which i created in IR.
i tried Enhance interface determination also..
please guide me....
waiting for your help.
regards
ram

Using PI to map IDoc BENEFIT3 to EDI 834

Has any used PI/XI to map IDoc BENEFIT3 to EDI 834? We are looking to use this approach but have had problems finding a standard map. You would think SAP would have one since they stand by their BENEFIT3 IDoc being sufficient to map to the 834. This will take forever to do it from scratch or even without an example. Help please.

Hi
You can do 1:n multimapping
in message mapping in messages tab ..add both the structures in target tab and do the mapping
and in operation mapping add both the message interface on the target side
PLease go through this blog
/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible

Error - Split mapping created no messages

Dear Experts,
while executing the IDOC to File scenario in PI 7.0, it shows error as u201C Split mapping created no messages u201C.
To resolve this error I have removed the extra tags with namespace specified as "\SplitAndMerge" in source XML message and also IDOCs used in the Interface maps are standard. no issues with mapping also.
kindly suggest me to solve this issue.
Thanks and Regards,
Srinivas

Hi,
Now i have solved the error of empty file creation. in my target file i am able to populate the data. but now ths issue is --
i have source IDOC with 3 sales items and i need to generate 3 records in Output file. but now i am geeting only the first record.
So please let me know how to get the remaining 2 line items also in my Output file.
Source MT:
Messages                   1..1
      Messages1               1..1
ItemMain                  1..1
item                        0..unbound
      Messages2           1..1
Item2                     0..1
Target MT
Messages                   1..1
    Messages1               1..1
        TItem                          0..1
           item                         0..unbound
   Messages2                1..1
       TItem2                         0..1
Best Reagrds,
Srinivas

MAPPING GENERIC (Split mapping created no messages) error is sxmb_moni

Hello,
We are having thousands of messages failing in sxmb_moni due to MAPPING GENERIC error. It also states that Split mapping created no messages. Where will I start my investiagtion? I already checked both ID and IR but I could hardly determine what causes this error.
Here is a part of the error message from the trace:
<Trace level="2" type="T">......attachment XI_Context not found</Trace>
<Trace level="3" type="T">Mapping already defined in interface determination</Trace>
<Trace level="3" type="T">Object ID of Interface Mapping 6FB317EF58B136D6BEAB6E567934CC40</Trace>
<Trace level="3" type="T">Version ID of Interface Mapping A872F380930B11DAAB6EF47891374079</Trace>
<Trace level="1" type="T">Mapping-Object-Id:6FB317EF58B136D6BEAB6E567934CC40</Trace>
<Trace level="1" type="T">Mapping-SWCV:A872F380930B11DAAB6EF47891374079</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/_GBO_MaterialMaster_StandardBusinessDocument_TO_LOCAL_Governor_</Trace>
<Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
<Trace level="3" type="T">Multi mapping required.</Trace>
<Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_GBO_MaterialMaster_StandardBusinessDocument_TO_LOCAL_Governor_.</Trace>
<Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._GBO_MaterialMaster_StandardBusinessDocument_TO_LOCAL_Governor_</Trace>
<Trace level="1" type="T">*** START APPLICATION TRACE ***</Trace>
<Trace level="3" type="T">Using existing</Trace>
<Trace level="3" type="T">Executing Query: SELECT TO_VALUE FROM ICC_MAPPING_VIEW WHERE FROM_CODING = SIRIUS AND TO_CODING = GS1 AND OBJECT = TRADE-ITEM-TYPE AND FROM_VALUE = 30</Trace>
<Trace level="1" type="T">SELECT TO_VALUE FROM ICC_MAPPING_VIEW WHERE FROM_CODING = SIRIUS AND TO_CODING = GS1 AND OBJECT = TRADE-ITEM-TYPE AND FROM_VALUE = 30 successfully returned: E-HPC_PRODUCTS</Trace>
<Trace level="1" type="T">ret: :E-HPC_PRODUCTS</Trace>
<Trace level="2" type="T">noReceiverFound</Trace>
<Trace level="1" type="T">*** END APPLICATION TRACE ***</Trace>
<Trace level="2" type="T">Java mapping com/sap/xi/tf/_GBO_MaterialMaster_StandardBusinessDocument_TO_LOCAL_Governor_ completed. (executeStep() of com.sap.xi.tf._GBO_MaterialMaster_StandardBusinessDocument_TO_LOCAL_Governor_</Trace>
<Trace level="3" type="T">Message Type 1 Number of Messages 0</Trace>
<Trace level="3" type="T">Message Type 2 Number of Messages 0</Trace>
<Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">No persisting of message after plsrv call, because of config</Trace>
</Trace>
<Trace level="3" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
Thanks in advance!

<Trace level="3" type="T">Using existing</Trace>
<Trace level="3" type="T">Executing Query: SELECT TO_VALUE FROM ICC_MAPPING_VIEW WHERE FROM_CODING = SIRIUS AND TO_CODING = GS1 AND OBJECT = TRADE-ITEM-TYPE AND FROM_VALUE = 30</Trace>
<Trace level="1" type="T">SELECT TO_VALUE FROM ICC_MAPPING_VIEW WHERE FROM_CODING = SIRIUS AND TO_CODING = GS1 AND OBJECT = TRADE-ITEM-TYPE AND FROM_VALUE = 30 successfully returned: E-HPC_PRODUCTS</Trace>
<Trace level="1" type="T">ret: :E-HPC_PRODUCTS</Trace>
<Trace level="2" type="T">noReceiverFound</Trace>
<Trace level="1" type="T">*** END APPLICATION TRACE ***</Trace>
You have used the Trace object to write some Trace in your User Defined Functions. Does this trace make sense in terms of your mapping logic to you?
Did you remove the <messages> tag from your source message?
Also, If you are using multimapping make sure that the mapping creates all the messages in the Target Side and that the Inbound adapter is neither Idoc nor HTTP.
Regards
Bhavesh

Split Mapping created no messages in SXMB_MONI

Hi All,
I have an IDOC to File scenario in which the target forms an XML file based on some RFC lookups. The problem i have is that whenever the RFC do not return any values, i am getting an "Split Mapping Created no messages" error in the SXMB_MONI. Is there any possible way that i could suppress the target and i should not form the target when the RFC do not return any output.
Regards,
Sherin Jose P

The problem i have is that whenever the RFC do not return any values
If you are trying to generate the Parent element using the RFC response then you are bound to get the error as no target structure will be poduced when the RFC does not return any value....may be doing a check on RFC response and then using MapWithDefault or any other term so that at least one valid element is produced will prevent the error from occuring.
Regards,
Abhishek.

How to map idoc segment field E1IDB02-FIIKONTO with BSEG-ESRNR.

Hi,
I have searched for lot of threads in the forum , and also i tried myself but i am not able to map this fields segment with my logic, so please anyone kindly contribute in mapping idoc segment field with the logic given below:
idoc type :PAYEXT outbound idoc.
message type: PEXR2002
This is my logic: i need to populate the ISR number(BSEG-ESRNR ) in idoc segment field( E1IDB02-FIIKONTO)
DATA : str1 TYPE string,
      len1 TYPE i,
      len2 TYPE i,
      str2 TYPE string,
      str3 TYPE string.
str1 = '01-1234-4'. ---> BSEG-ESRNR "ISR Subscriber Number
REPLACE FIRST OCCURRENCE OF '-' IN str1 WITH '_'.
REPLACE ALL OCCURRENCES OF '-' IN str1 WITH space.
CONDENSE str1.
len1 = STRLEN( str1 ).
IF len1 LT '9'.
len2 = '9' - len1.
CASE len2.
   WHEN '1'.
     REPLACE ALL OCCURRENCES OF '_' IN str1 WITH '00'.
   WHEN '2'.
     REPLACE ALL OCCURRENCES OF '_' IN str1 WITH '000'.
   WHEN '3'.
     REPLACE ALL OCCURRENCES OF '_' IN str1 WITH '0000'.
   WHEN '4'.
     REPLACE ALL OCCURRENCES OF '_' IN str1 WITH '000000'.
   WHEN OTHERS.
ENDCASE.
ELSEIF len1 EQ '9'.
REPLACE ALL OCCURRENCES OF '_' IN str1 WITH '0'.
ELSEIF len1 GT '9'.
REPLACE ALL OCCURRENCES OF '_' IN str1 WITH space.
CONDENSE str1.
ENDIF.
Thanks in Advance.

Resolved.

How to map Idoc fields with external file

Hi All,
How to map Idoc fields with external file.
I want to check the settings where Idoc fields are mapped with external file.
Thanks in advance.
Regards,
Govind.

If you have configured a fileport where on trigger of IDOC you are creating the file, you can look at the message type documentation and get the offset values for each field in each segment

HOW TO MAP IDOC TO XML

Hi,
I need to map IDOC to xml but the problem is I have 400 fields in IDOC which are to be mapped to 20 elements in XML.
As it a tedious process to go to 400 fields for each xml element.Is their any better way to find correct field in IDOC with very minial time rather going 400 fields for each xml element.
thanks
sreeram

hi,
>>1)Even SAP it self does not encourage to use ABAP >>MAPPING and
i dont know where you have read this, but ABAP mapping is one of the most popular/ most efficient and highly recomended by SAP. I have used it in tons of places.
>>2)More over Iam not ABAP resource.
you could also do a java mapping.
there is no other easy way if you are not doing abap/java mapping. you are then left with the only option of using the graphical editor.
cheers,
Naveen
Message was edited by: Naveen Pandrangi

Functional Specs for Mapping Idocs to EDI

Hello Friends ..
Am new to world of EDI...
can any one explain ..wat do u mean by devolping functional specs for mapping IDocs to EDI..
If you can provide me with examples or if you guys can suggest any site where i can browse some material about EDI..i wud really appreciate...
Best Regards

Hi Rohan,
>>>do u mean by devolping functional specs for mapping IDocs to EDI..
you have to know which idoc fields you have to map to EDI message fields
take a look at those links:
they will show how do you map different IDOC message types to EDI messages
IDOC - EDI mappings:
http://www.sapgenie.com/sapedi/mapping.htm
Analysis of the compatibility of EDIFACT messages in the form of SIMPL-EDI with the IDoc Interface:
http://www.sapgenie.com/sapgenie/docs/SIMPL-EDI-E_ORDERS.doc
Regards,
michal

EWS 1.2, Exchange 2010 SP2/SP3 - Appointment message body gets wrecked on update

We're seeing a very irritating issue with EWS and Exchange when updating the message body on an Appointment. To head it off, it does not appear to be the bug detailed here:
http://blogs.msdn.com/b/dhruvkh/archive/2012/05/18/sending-appointments-from-ews-apps-where-did-my-html-go.aspx
It happens on both 2010 SP2 and SP3. We're creating Appointments with some HTML formatting the message body. Nothing fancy, just a few tables and a little bit of inline styling (since a css style header disappears into a black hole when you try to use it
as part of the Appointment message body). We're able to make a nice-looking message body that goes out in the meeting requests. Well, with the exception of downlevel text at the top, but there doesn't seem to be much we can do about that short of a double-tap
save.
The problem comes into play if we need to update the message body on the Appointment. All of this is automated, so the user cannot directly edit it. If we make any changes to the message body, it completely wrecks the HTML. It's still an HTML-formatted message,
but much of the styling is lost and it looks awful. This happens without fail when we alter the message body of an Appointment with any considerable level of HTML formatting. BodyType is HTML, of course. I've done some digging on the best body algorithm and
some of the MAPI properties related to it. Some interesting bits of note:
When the Appointment is first saved, PidTagRtfInSync is true. PidTagNativeBody is 2, which indicates an RTF message. PidTagBody is present. PidTagRtfCompressed is present. However, PidTagBodyHtml is not present. After updating the Appointment with a message
body edit, PidTagBodyHtml is present, but now PidTagRtfInSync is false and PidTagNativeBody is 3.
If PidTagBodyHtml is set directly as an extended property instead of setting the message body via the EWS Appointment object, then the formatting is wrecked right out of the gate. At least it's consistent that way...
Attempting to set PidTagNativeBody manually had no effect.
When viewing the PR_BODY_HTML contents between a good and bad message, the good one will contain the transformed HTML. It doesn't look much like what we had initially handed to it, but gets changed in the conversion process. The bad one is much closer to
what we wrote in actual HTML, but has still had much of the styling removed. It's as if creating the Appointment does the RTF conversion, but any subsequent changes use a completely different code path serverside and there does not appear to be any way around
it short of even more guess and check with EWS and Exchange chewing up HTML. This is complicated by being unable to find any documentation that details how and what gets changed, discarded, etc in the process.
This will always affect requests, but only seems to affect Appointments in the calendar of attendees if the body includes the downlevel text. Appointments without the downlevel text appear to survive updates with their formatting intact. Appointments with
downlevel text get their formatting wrecked with updates.
Has anyone run into this before? It was painful enough when we found that our previously-used email HTML formatter wouldn't work with EWS and everything had to be inlined, but now it seems that there are even more inexplicable problems to get around. Is
there a way to update the message body without this happening?

Ugh... hopefully I can ask you gentleman how to solve my issue.
I recently implemented code to allow our users to turn-on HTML-encoding for when our Sync'ing app goes to add/update items for them into Exchange.
If thev'ye turned-on HTML formatting, when I create a CalendarItemType's (in C# based off the EWSProxies.EWS.Itemtype) the Body.Value is being set with a string which contains very minimal HTML tags... just 's instead of "\r\n" and for
URL link values we are embedding into the text, I'm encapsulating those within an <a href>
Example: <a href="http://TheWebSite.com/EventDisplay.aspx?uri=1234">Event Display Link</a>
My problem is... when I retrieve an item from Exchange... there is a huge amount of extra HTML encoding it wraps around everything!
By inspecting in the debugger... I've discerned that :
For Appts... the main bunch of text that I inserted in an item when originally creating it is contained just within the <div> tag.
For Tasks... the main bunch of text that I inserted in an item when originally creating it is contained just within the <body> tag (and on these there is no <div> tag created).
I was able to use the HTML Agility Pack and load this Body.Value string into the enhanced HtmlDocument object. I first attempt to parse first for the <div> nodes contents. If the <div> is not-null that's an Appt. If the <div>
is null, I instead parse out the <body> nodes contents, and those are Tasks.
I noticed for Appts :
For every tag I had in my original text.. it appends two consecutive "\r\n" 's after it! No problem I can just do a Replace("\r\n", "") and zap those. But then the <a href> I have in there... it
encapsulates it with a node where it sets a color for the link and also an underline node. I can handle the nodes easy enough with a Replace("","") and a Replace("", "");
But what about the damn node? It's in the format of and I'm sure the \"blue"\ part could be different for every user.
I noticed for Tasks :
It prepends a "\r\n" just inside the begininng<body> tag. Each of the original tags gets an "\r\n" appended behind it. and for the TaskType for the <a href> node IT DOES NOT encapsulate it with the 
and nodes as it does for the Appt.
How can I stop it from changing the Body content when retrieving it? Will it not change anything if I go the extra mile and make sure to wrap everything with an <html> and <body> node when initially creating the items?
Any and all help on this issue is sorely appreciated.
Thank You,
-G

Using same Idoc type & Message type for 2 Interfaces

Hi all,
we have 2 interfaces which uses same Idoc type, message type & Partner No.Only Process code is going to different according to the posting logic.
How can we differentiate both while posting idocs to not mess up each other .
Regards

Hi all,
Say example:
Interface 1 is invoice coming from legacy system to SAP and i have to use AAA.BBB Idoc
Interfaces 2 is accrual coming from legacy system to SAP and i have to use AAA.BBB Idoc
So i am creating partner No with LS_LEGACY and with 2 inbound entries one for each.
Even though i am using the same Idoc types but inside those the process codes are different because they are different in posting logic.
Issue:
From XI perspective i can't differentiate them saying like Invoice interface should execute the entry in the partner profile with invoice process code and accrual interface with accrual process code.
My Idea is to design like this...
Using the Message Code option, While creating partner profile give the MESCODE and in Mapping provide the same MESCODE.
So that even thought i am using the same partner No with same message type & basis types for 2 scenarios, the right interface will trigger the right process code based on the MESCODE mentioned in mapping by carrying the control record values
Please let me know ur views
Regards

Mapping IDOC error

Hi experts,
I'm doing my first scenario IDOC to JDBC, i've problem with mapping
I don't have seen any example in this forum of mapping IDOC, only i have seen the document :
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c09b775e-e56e-2910-1187-d8eba09c7a4a
in this document says about party, only this is possible?
i've testing mapping with payload and message 'XML not well-formed' occurs, i've comparing this message with message download testing and i don't see differences..
the error in runtime workbench is:
'com.sap.aii.utilxi.misc.api.BaseRuntimeException
thrown during application mapping
com/sap/xi/tf/_MM_MATMAS03IDOC_TO_MT_MATERIALES_:
RuntimeException in Message-Mapping transformatio~'
very thanks

Hi,
The error XML Not well formed means that the XML that you've used as a test in message mapping does not conform to XML coding standards.
What you can do is to find a sample XML in SXI_MONITOR then right-click on the lower-right pane then click view source. Copy the all the values using ctrl+a and ctrl+c. Then under test tab in message mapping, click the src or source text view and paste the payload there (overwrite the empty one). Then you can test the mapping for transformation.
Hope this helps,

IDOC send message to third party system

Hi,
I got the below scenario,
1) Data came from 3rd party system through EDI
2) Because the material is not there in SAP system it didn't create sales order
3) IDOC is errored out
4) How to inform the 3rd party system through an IDOC or message that IDOC got errored out?
Thanks
anikaushi

so you mean to say that we can trigger workflow sothat those people or email.
Yes, for error handling and resolution
Can we send the eror message to 3rd party in the form of IDOC immediately afer error IDOC is created in SAP?
You could, but I don't see the point and you'd have to map it. Your EDI system should provide an FA back to the sender upon receipt so that it knows the message was received. The error should go to the person or group that would handle the issue if it's an SAP-related issue such as a master data or config error. I don't know your system/setup, but it doesn't make sense to send a material error back to the sender system if someone is going to fix that in SAP and then re-process the IDOC (and trigger an order confirmation).

Mapping IDOC to message body

Similar Messages

Maybe you are looking for