XI - IDoc - MDMP

Hello!
How can XI send IDocs to a SAP 4.6 MDMP system which needs to receive several Asian languages?
When I change the SM59 settings on XI according to SAP Note 613389 I can send Asian characters to these systems and they are correctly displayed there.
However, the problem is that it only works for one language at a time, e.g if I put in logon language ZH it only works for IDocs with Chinese characters and if I put JA it only works for Japanese.
I was thinking I might be able to create several SM59 destinations with different logon languages and then pick the correct one according to the language flag in the IDoc. But it is not possible to reference different communication channels (pointing to different SM59) for the same business system.
And I also cannot create a new business system for each language because I cannot use same logical system and client in the SLD again.
Regards, Tanja

Hi Tanja,
I do not know if this works, but it may be worth a try:
Create a new business service as receiver and create an IDoc channel for it.
In the receiver agreement add a header mapping for the receiver service, where you put the original business system.
Regards
Stefan

Similar Messages

Integrating MDMP and Unicode systems with IDoc interfaces

Hi,
We are working on integrating SAP R/3 6.20 (MDMP) with SAP PI 7.0 SP10 (Unicode) system. The source will send MATMAS or CLFMAS IDocs with Thai / Japanese characters and PI should transform and post it to SAP ECC 5.0 Target system [IDoc to IDoc scenario].
( SAP R/3 Legacy 620 - Non-Unicode / MDMP ) |----> ( XI - Unicode) -> (ECC - Unicode)
Had a look at few SAP notes (745030 ,656350 and 613389) and it looks like there is no standard way/best practice to handle this scenario.
References:
1.PDF of TECHED Session ID: IM101 Dealing with Multi-Language Garbage?Data Lessons Learned
2.SAP Note 745030 - MDMP - Unicode Interface_Solution Overview.pdf
3.MDMP_Unicode_Transfer_final.doc from SAP Note 745030
4.SAP Note 656350 - Master Data Transfer UNICODE to MDMP Systems with ALE.pdf
5.SAP Note 613389 - ALE SAP system group with Unicode systems (Solution-2)
My understanding per SAP Notes: (Please correct me if I'm wrong)
a. For MDMP integraton we can't use Standard ALE Config instead we have to use Custom Configuration (IDoc collection setting in Partner profile &Scheduling RSEOUT002/RSEOUT00_MDMP and use Function module :IDOC_INBOUND_ASYNCHRONOUS_2 ).
b. The RFC Destinations should use proper logon langauage for correct MDMP IDoc transfer (For sending IDocs with Japanese character, the logon language should be JP).
c. If we want to transfer IDocs in more than one language we need to create multiple Partner profiles/RFC destinations each with specific logon language.
Please guide us in integrating these systems if you have done a similar integrations, following are my questions:
1] Is there any configuration change required at PI layer?
2] Do we need to install codepages in PI Unicode system for all languages used or Unicode system is capable of handling all the languages?
3] Is it necessary to install any SAP Add-on package in R/3 MDMP system inorder to support MDMP to Unicode data transfer?
3] If we want to send MATMAS/CLFMAS IDoc with Thai/Japanese characters from same system, what are the changes required at the Source system?
(Source may send MATMAS/CLFMAS IDoc with either Thai/Japanese characters but not both of them in a single IDoc)
4] Can we use regualr ALE & Partner profile settings for handling multi-byte characters or we need to use IDoc collection and RSEOUT002/RSEOUT00_MDMP report for transfer?
5] Is there any restrictions on the IDoc types (MATMAS,CLFMAS etc) supported in MDMP-Unicode integration solution.
5] Is there any best practice document available for this scenario?
6] Do we need to involve SAP AG for MDMP to Unicode system integrations(As per SAP Note: 656350) ?
Thanks and Regards,
Ananth

Hi Ananth,
as you have already mentioned, you need differents RFC destinations for each language. So you have to make sure, that the IDocs use the right destination according to there content.
If you have messages from PI to MDMP it is the same, you need different channels with different logon languages as well. You need an identifier in the message, that can be used for selecting the correct channel.
It should not be a restricting to any IDoc type, but it is not possible to post a message with different languages (which require different codepages) in one IDoc.
For correct conversion from a non unicode system to unicode, the codepages have to be installed in th OS of the PI server.
Regards
Stefan

MDMP Idocs enable to use SPRAS

Hi Experts
I have been dealing with MDMP issues in idocs flowing from my 4.5 MDMP system to ECC 6.0.
Basically text in some of the idocs get garbled specifically for Chinese Characters.
Basically based on some investigation we can use XI and the only change should be to add the SPRAS in the needed segments in order to handle it and interpret the data in the specified Language.
For Example I need to enable SPRAS for Segment E1FIPOS, is there any way to change it in ECC? Since the system is not allowing me to change.
Will XI interpret the idocs if we are able to add SPRAS?
Thanks in advance.

Hi,
U can change this in ECC . Goto t.code we19.
give the existing IDOC number or idoc type in the selection screen and execute.
then u will get all the segments for the given IDOC type .
then u can give your values in which segment you required and process the IDOC.
Hope this helps ..
Regards,
Sharath

Sending IDOCs from an MDMP to a Unicode system

Colleagues
I have been trying to send IDOCs containing Chinese characters from an MDMP system to a Unicode system. The data is not being translated from the Chinese code page 8400 to Unicode format.
To date I have created a new IDOC segment, within the original IDOC, which contains the language dependant data preceded by a language element. I have also maintained SM59 on the receiving system (Unicode) to mark the sending system (in SM59 defined as an R/3 connection) as non-unicode, and activated the MDMP settings and mapping the language key ZH to codepage 8400. I have also checked that the language key and code page is valid in the unicode box.This still doesnt work.
I was under the impression that the RFC system would translate the IDOC line by line and if it found a language key in the segment translate it using the code page assigned to that language, but this doesnt seem to be the case. The sending system is 4.5C and the receiving system 4.7.
Is there anyway to get this to work without playing with the IDOC processing routines such as IDOC_INBOUND_ASYNCHRONOUS? Is there something Im missing?
Thanks in advance for your help.

Hi,
Perhaps you may want to try to use IDoc file interface instead of RFC.
You can use standard program RSEINB00 to process and post the IDoc file.
Regards,
Ferry Lianto

Idoc failed in Bi system "Could not find code page for receiving system".

Dear Experts,
i am getting below error ,Idoc failed in Bi system "Could not find code page for receiving system".
All the idocs have been successfully posted except one which is giving this error
Idoc status 02 - could not find code page for receiver system.
Please guide me
thanks
vamsi

Hello Vamsi,
check Note 647495 - RFC for Unicode ./. non-Unicode Connections
If your ERP system sends e. g. chinese data to the SCM system, how should the system know which codepage to use? You have to set the MDMP flag in your ERP system in SM59 and configure in the MDMP extended settings which codepage should be used for what language.
Please check this thread - IDoc error - Could not find code page for receiving system
Hope it helps,
Thanks & Regards,
Amit Barnawal

Customer Master Idoc gets some fields as garbage with English Lang

Hi
We are using SAP 4.6C MDMP system. This is not unicode. We are sending customer idoc. The customers are created in Japanese and English language.
When we login in Japanese language and send IDOC then the content looks fine.
When we login with English language and send IDOC then we get some garbage character.This is because the customer was created in Japanese language and the IDOC is being sent with English language code page.
I am thinking of copying the RBDMIDOC program and include a logic which will check if the customer is Japanese and logon language is Japanese only then send the idoc.Similarly if customer is not japanese and logonlanguage is not japanese then send the idoc.
Has any one faced issue with IDOC and the data being maintained in different language.
Please share your thoughts.
*point will be rewarderd
Thanks
prashanta

Hi Anuj,
This is a configuration change that can be done via tcode NACE.
The Idocs will be automatically triggered and sent.
Ask your functional consultant for further details.
Regards,
Jovito.

Data is posting wrongly in Idoc

Hi all,
We are facing issues with data is posting wrongly in File to Idoc scenario. When we test this scenario everything shows success in XI but in R/3 idoc generating with 64 status and data is not posting correctly. Suppose our second field if we send more than 20 length it is trimming upto 20 only. If we change offset to take 40 length to second field again it is taking 20 legth of sceond field and rest of third field values. As i have been checked with Abapper they were saying like whatever data we are sending to R/3 it will be coming as a single structure(Sdata) . But i have been checked outbound XML also in that everything shows fine. Is there anything problem in Xi . I have been re-imported idoc in XI also and it is equipment master Idoc. They have been used offset also still no use. My doubt is why from second field on wards data is posting worngly.They have used structure sdata.
Example:
Suppose, Outbound XML in XI:
<Idoc>
<Field1>abc
<Field2>4364255166110335211
<Field3>Computer
<Field4>Laptop
<Field5>sdas
<Idoc>
Idoc in R/3:
Field1:abc
Field2:43642551661 Computer Laptop
Field3:      sdas
Field4:
Field5:
Could anybody help me on this. Why is data wrongly posting here...
Rgrds,
Aparna.

Hi,
i have faced same issue before.
   in receiver communication channel for IDoc you have to specify some important parametres port and sap release so on...
   while cretaing a port you have to give rfc destination in your port by using t-code IDX1.
go to rfc destination which was you given in port. check in your destination, tab MDMP & UNICODE.
Flag or disflag the option UNICODE/NO-UNICODE and test again.
once again check your message mapping.
regrds,
ganesh.
Edited by: ganesh.nijampudi on Nov 30, 2011 7:47 AM

XI JMS Adapter encoding and codepage (MDMP) problem

Hi
I have a scenario where i convert an IDoc into a target structure and post it onto a Websphere MQ queue using JMS adapter. The SAP system which sends the idoc is a non/unicode system and i can receive data which can either danish, polish etc. Within XI the mapping works fine and the data is transferred to the MQ series queue. But when the third party system tries to get the message from the queue it says it downloads the message and is unable to convert the downloaded message due to invalid content (special danish, polish characters). Also the CCSID and encoding expected is 1252 and 546 respectively, but whenever i send message to the queue the CCSID is 1252 but encoding is 273.
Any idea as to why the above is happening, and how can it be corrected.
Also if anybody had faced any issues with respect to code page problems and resolved it with JMS as either sender or receiver, please share the same with me as well.
I am repeating that my SAP system is non-unicode (MDMP) system.
thanks
Sameer
Message was edited by:
Sameer Shadab

Sameer,
I guess u can ask the third party to set CodedCharSet in GetMessageOptions. Actually my MQ knowledge is around 4 yrs old but I remember we had similar problem when we were pushing messages on remote queue of MQ on AS-400. I hope they resolved by setting this value.
Regards
Rajeev

IDOC to XI, wrong data

Hi Experts,
I am facing a strange error..
from we 19 when I trigger the idoc.. the data is correct ....
Im focusing on the second last field in the idoc ...but when it comes to XI in sxmb_moni in the inbound message...
the value of this field gets shifted to the last field...
I have re imported the IDOC and done the mapping as well.. but somehow the field from SAP does nt come into XI...
pls share ur thoughts...
Regards,
Teja

HI,
Make sure you have to check the segments and idoc are released or not. one more thing you have to check the rfc destination of type unicode settings R3 and PI in your destination tab MDMP & UNICODE.Flag or disflag the option UNICODE/NO-UNICODE and test again.and once agian re improting idoc into PI......
hope it will help you..
regards,
ganesh.

Customer Master Data interface to external using Seeburger on MDMP

Hi Experts,
   Currently, customer master data is interfaced to external system via IDOC. The middleware used is Seeburger.
   If the system is changed to MDMP, would there be any impact to this interface?
   Is Seeburger communicates in Unicode? If so, when the data is translated to Unicode when the data from R/3 is non-unicode?
   Thank you.
Regards,
Bing Fatt

Thanks Uwe,
I tried to create IDoc with BD10 for material master and I am getting two error msg as below.
Msg one
1 master IDocs set up for message type MATMAS
then Msg two
0 communication IDoc(s) generated for message type MATMAS
Is it able to get why this msg is comng and no IDoc's were generated..
Regards,
Senthil

IDOC encoding

Hi all,
I am sending IDOCs from PI 7.0 SP12 to SAP 4.6C. The problem is that some characters are garbled on the backend.
On the PI side (sxmb_moni) I see all characters in the payload correctly. Payload type is application/xml with encoding utf-8.
But on the backend side some characters in the Idoc are garbled.
It seems that IDOC is not converted from UTF-8 to ISO-8859, which is the code page of 4.6C.
Any suggestion how to solve this?
Thanks, janos

Hi,
Thanks for your answers, but I still didnt solve the problem.
My understanding is that I must activate the MDMP in the RFC destination for the backend.
The logon language is set correctly.
I have some doubts that MDMP is set correctly, since I see inside something like this.
Lang Local Remote
SR     0000     1500
RO     0000     1401
SL     0000     1401
HR     0000     1401
MS     0000     1100
UK     0000     1500
CS     0000     1401
Is it correct to have zeros for all Local?
If I try to change Local code page to 4110, which I think is the code page of UTF-8,
I got the following pop-up msgs :
Local     Incorrect codepage: 4110. Must be a system codepage and reference to tables TCP00 and TCP0C,
A system codepage is required here.
The table TCP00 contains all the codepages and TCP00-CPISSYSTEM must be activated for one system codepage.
Other criterion: The code page must appear in TCP0C-CHARCO.
(Currently, 2002-7-2, there are system codepages that appear in TCP0C, but for which the attribute CPISSYSTEM is not activated in TCP00 - for example, 1610).
Please advice what needs to be done here. How to sent IDOCs from IE (UTF-8) to backend (iso-8859-2).
Best regards,
Janos

Unicode and IDOC

Hi All,
We are implementimg new SAP ECC 50 system for HR module.
We also have a 46C system and HR master data will be converted to 50 system and ongoing new objects will be transferred from 50 to 46C using ALE.
ECC 50 will be unicode compliant system and for certain countries like China and Germany, address and family infotypes will be entered in their local language.
So when we create the IDOC from 50 system, going to a 46C non-unicode MDMP system, how will IDOC post in 46C system?
Basically how will be IDOC from a unicode system be posted into a non-unuicode system?
-Thanks
Bhaven

Bhaven,
did you ever find out about this?
If yes, I would like to hear from you on your pains during this Unicode conversion. Did you guys faced any problem specially for some Asian countries (China/Japan/Korea)?
Regards,
Sanjeev Gupta

Unicode error :Outbound Idocs

Hi,
While sending Idocs from Unicode to Non-Unicode(MDMP) system, IDocs are created with error status 02 and error <b>codepage of receiver system cant determind. receiver destination was TESTLS</b> in the sending system.
I checked SM59 to check RFC for receiving system. Can you please let me know what should be the settings for this scenario?
Can somebody please help to solve this issue?
Thanks ,
Yogita

Hi Yogita
I am facing the same issue while installing CUA. Did you find any solution.
thanks
Jay

Greek Letter in IDOC

HI Experts ,
I am mapping a constant containing greek letters to a field in IDOC and then posting it .
The out put of the PI in Runtime is also fine .
But once the IDOC is posted then the greek letters are seen as ##### .
Can anyone please help with this ??

Hey
Please look at the RFC destination in SM59 which you are using to connect XI to R/3
under the "MDMP & Unicode" tab,please select Unicode and save.then try to send message to R/3
Thanks
Aamir

Logical System in IDOC-XI scenario

Hi,
I need help to understand few things in IDOC-XI scenario, could any one help me in this regard.
we use Adapter specific identifiers to map services, we have following type of identifiers 1) Sys.ID & Client No. 2) Logical System.
my questions are
a) Are we use Logical System in B to B scenario ?
b) Are we use LS in reference to the SAP system or Non SAP system ? if a non SAP system....how a non SAP system send an IDOC and why a non SAP system receive an IDOC ( conversion is possible in XI ) ?
Thanks and Regards
Mahesh.

Hay Kumar,
Logical systems can also be used for SAp sytems wich are not installed yet as a virtuall placeholder.
a) yes. if on of your business is a non sap system or a propritery system that you developed yuo'll ue LS.
b) non SAP system can send and recieve IDOCs. so it's possiable to get an IDOC from a system and turn it into an RFC for SAP or get an IDOC from an SAP system and then turn it into something else for another system.
Have a Good One,
Uri Lifshitz.

XI - IDoc - MDMP

Similar Messages

Maybe you are looking for