IDOC Serialization(EOIO) using IDOC Adapter throwing Mapping error

Hello SDN Gurus,
The scenario I am working on is IDOC(PAYEXT & EUPEXR) --> XI (ABAP Mapping) --> Flat File (IDOC Structure).
The IDOCS produced in Appl system may be in the following order
PAYEXT
PAYEXT
EUPEXR
PAYEXT
PAYEXT
PAYEXT
EUPEXR
I need them to be processed in the same order into flat file.
The scenario is working good except for the serialization. So I did the following
Created two entries in IDXQUEUE one for each message type with the same Queue name in XI system.
Created a new rule for the queue and an associated function module. Used this rule in partner profile for both the message types. I used the following link to create the above two steps.
/people/community.user/blog/2006/11/04/how-to-serialize-idoc-xml-messages-fed-into-xi
The SAP system in based on WAS 6.4.
I can see the queue name & EOIO in the inbound message header.
I am getting a mapping error in ABAP program. If I inactivate the queue(in Appl system SAP ECC), I don't get any error.
Does anybody had this problem earlier? Please advice.
Thanks
Srini Vaidyam

I found an OSS note to resolve my issue. The note number is 1057573.
Whenever the queue is activated, the sender system will not send the <TABNAM> field value in EDI_DC40 structure. This note addresses this problem.
I found out this by comparing the results from SXI_MAPPING_TEST individually for the message that failed after queue is activated and the message that was successful if the queue is inactivated.
Only thing I noticed now is even if you selected the radio button "Trasfer Immediately" in Partner profile of Appl. system, the messages are not sent. They are getting collected. So we need to manually push them out using WE14.
This forum Rocks.
Thanks.
Srini Vaidyam

Similar Messages

How to implement IDOC Serialization(EOIO) using IDOC Adapter

I am sending IDOC from 4.6c to XI to ECC6.0 using IDOC Adapter. I want to ensure that IDOCs are processed serially(EOIO) on the receiver side. I tried setting up the SE16-->IDXQUEUE on XI for the Receiver system and enabled the Queue processing flag on the Receiver communication channel, but the IDOCs are not serialized.
I see that XI is using XBTO_007(EO) Queue. It should be using the queue that I specified in SE16.Please let me know what else needs to be done to implement EOIO for the IDOC adapter.
Please note Sender is 4.6c System while the receiver is ECC 6.0 on WAS>=6.2
Thanks in advance.
Rajeev Gupta

Rajeev,
From http://help.sap.com/saphelp_nw70/helpdata/en/bd/277264c3ddd44ea429af5e7d2c6e69/content.htm
<b>The receiver or sender system must be based on SAP Web Application Server 6.40 or higher.</b>
The blog listed above is when you need to sends Idoc from R3 to XI in EOIO. It does not work with SAP R3 4.6C for the reason above.
For sending Idoc's from XI to R3 ( to ECC in your case ) in EOIO, you need to seelct Queue Processing in the Receiver Idoc adapter and the rest I think is handled implicitly by XI.
Regards
Bhavesh
PS: Have not tried this practically though!
Message was edited by:
Bhavesh Kantilal

How to check IDOC Serialization for custom idoc

In one of my interfaces, we are receiving idocs ARTMAS, INFREC, COND_A and ZMD_ARTHIER in ECC system.Last one is customized one in which basically we have to assign one article to an article hierarchy. So this idoc will contain only article no, hierarchy id and node level in which article will be assigned.
Now here we have to implement idoc serialization so that if ARTMAS in any case fails then INFREC, COND_A and ZMD_ARTHIER idocs should not be posted. We will be using RBDSER04 program for inbound processing.
My concern is that whether we have to do any special coding for serialization check in custom function module for the last idoc ZMD_ARTHIER.
If yes, please please let me know how to do handle that in custom inbound function module.
Edited by: suman pandit on May 19, 2009 10:47 AM

Hi,
you need to create a serialization group (in customizing) and assign all the IDocs (in specific order) to this group incl. your custom IDoc.
When data is transfered first a SERDAT01 IDoc will be sent, after this your IDocs have to follow in specific order. At last again a SERDAT01 follows and triggers the processing in the destination system.
Regards,
Kai

Call to ALDP 3.2 dataservice using Mediator API throwing validation error

Hi,
Call to ALDP 3.2 dataservice using Mediator API with request doc having xsi:type (eg: <ns1:searchBy xsi:type="ns2:ImplXXXIDType">) is throwing validation saying that it is unable to resolve the namespace ns2 .The namespace ns2 is defined at root level. If the namespace ns2 is defined at the element level like this
<ns1:searchBy xsi:type="ns2:ImplXXXIDType" xmlns:ns2="http://www.xxx.com/xyz/datastructure/1/"> it is working fine. We never had this issue with ALDSP 2.5 Mediator API.
Any suggestions or help would be most welcome!
Thanks,
Gkumar

Ok. Now you need to put enough information on the case for someone to investigate. Please attach instructions on how to create a data space that will show this problem. Since customer support will not have your database etc. , if you just create an empty ds function in the same ds as the one that has the problem, like so...
function dummyFunction() as element(....)* {
and then replace the () with the output from the Test View so it looks like...
function dummyFunction() as element(....)* {
<myElement ....>
<otherElement ...>
</myElement>
Once you have a dummy function like that which demonstrates the problem, export your dataspace and attach it to the case.
If you anticipate some of the questions that customer support is going ot ask you (including providing a reproducer), you will save yourself many days (or weeks) of time.

EOIO for IDOCs to XI

Hi,
My scenario is IDOC ---> xi ---> File.
Need to implement EOIO(serialization) for IDOCs coming from ECC.
Checked "Queue Processing" and assigned rule "FIRST_16_OF_MESTYP".
When I send the IDOC using WE19, I get message "IDocs are stored in the queue".
But, IDOCs are not coming to XI. Please help.
Versions: ECC 6.0 & PI 7.0 SPS 13.
Also, do I need to maintain an entry in IDXQUEUE table?

Hi
use similar thread
How to implement IDOC Serialization(EOIO) using IDOC Adapter
Re: Posting idocs in sequence in SAP from file (without BPM)

IDOC to XML using HTTP

Hi Friends,
Is there any possibilities to Convert IDOCs as XML using HTTP Adapter in SAP PI?
Because in my Scenario i need to send Idocs from ECC to Red Prariie using SAP PI.
Also is it there any possibilities using FTPS?
Please help me.
Thanks.

Hi PIstarter,
Sure this is possible. Just treat the IDoc like any other Service Interface that you use in the HTTP Receiver Adapter. You can even use the no-mapping approach if no additional processing is required by PI.
Hope this helps,
Greg

Idoc serialization by Time Stamp

Hi,
I have a need to use Idoc serialization by Date and Time, but from what I noticed the existing program 'RBDAPP01' will automatically turn on serialization by date and time stamp once the field EDIDC-SERIALIZATION is used.My understanding on serialization by Date and Time is as follows:
Once the Serialization object is defined for a unique key (By defining Serialization in 'BD95' and 'BD57'), the function 'IDOC_SERIALIZATION_CHECK' is called in inbound function module for the idoc to see if there is already a record processed for the same key (via table BDSER), and if it is then any Idoc with a time stamp less than the one in BDSER comes for processing it gets an error.
Now my questions is what is the purpose of defining the configuration for Serialization by going to 'BD95' and 'BD57' when RBDAPP01 is already doing the same?
Also please correct me if I there is any flaw in my understanding.
Thanks in advance.

Hi,
Based on what I understood from some SAP documentations (I am not 100% sure though), RBDAPP01 talks about IDoc serialization & the other transactions talks about ALE Serialization. Both are different as I understood from SAP documentation. And ALE serialization is used when you try to send a set of data. LIke material master, classification data. And you can link/serialize these different message types to make sure first material master idoc is processed & after that classificaiton idoc. And IDoc serialization is used to make sure the idocs (same message type) are processed in the same order by using field EDIDC-SERIAL. Something like date/time stamp can be used for this.
Regards,
Gokul

Idoc Serialization Problem

Hi Experts,
We have a requirement where we need to send IDoc's to SAP PI in a sequence from SAP ECC and in the same sequence the Idoc should reach to the SAP PI.
We tried to do the sequencing through IDOC Serialization (From Mastering Idoc Business Scenarios BOOK), but the Idoc are not reached to MONI in the Same Sequence.
Please reply if anyone has done IDOC Serialization.
Regards,
Praveen Kalwa
Edited by: praveen kalwa on Jun 25, 2010 4:59 PM
Edited by: praveen kalwa on Jun 25, 2010 5:08 PM
Edited by: praveen kalwa on Jun 25, 2010 5:14 PM
Edited by: praveen kalwa on Jun 25, 2010 5:15 PM

Hi,
You can do the IDOC serialization in SAP PI by creating a queue .
The logic is, please create queue in PI which should be referred in SAP partner profile rule. We have implemeted this in our landscape which runs perfectly w/o any issues.
Please refer ht[/people/community.user/blog/2006/11/04/how-to-serialize-idoc-xml-messages-fed-into-xi|ht/people/community.user/blog/2006/11/04/how-to-serialize-idoc-xml-messages-fed-into-xi]

Adapter Module deployment error in PI 7.1

Hi Experts,
I have successfully deployed a adapter module on PI 7.1 thru NWDS, I see the ejb in NWA as well...
when i try to use it tit throws this error in comm channel monitoring
Error: javax.ejb.TransactionRolledbackLocalException: (Failed in component: sap.com/UserModule_EAR) Exception raised from invocation of public com.sap.aii.af.lib.mp.module.ModuleData com.sap.adaptermodule.GetHostNameBean.process(com.sap.aii.af.lib.mp.module.ModuleContext,com.sap.aii.af.lib.mp.module.ModuleData) throws com.sap.aii.af.lib.mp.module.ModuleException method on bean instance com.sap.adaptermodule.GetHostNameBean@299c92f0 for bean sap.com/UserModule_EARxml|UserModule_EJB.jarxml|GetHostName in application sap.com/UserModule_EAR.; nested exception is: java.lang.NullPointerException; nested exception is: javax.ejb.EJBException: (Failed in component: sap.com/UserModule_EAR) Exception raised from invocation of public com.sap.aii.af.lib.mp.module.ModuleData com.sap.adaptermodule.GetHostNameBean.process(com.sap.aii.af.lib.mp.module.ModuleContext,com.sap.aii.af.lib.mp.module.ModuleData) throws com.sap.aii.af.lib.mp.module.ModuleException method on bean instance com.sap.adaptermodule.GetHostNameBean@299c92f0 for bean sap.com/UserModule_EARxml|UserModule_EJB.jarxml|GetHostName in application sap.com/UserModule_EAR.; nested exception is: java.lang.NullPointerException; nested exception is: javax.ejb.EJBTransactionRolledbackException: (Failed in component: sap.com/UserModule_EAR) Exception raised from invocation of public com.sap.aii.af.lib.mp.module.ModuleData com.sap.adaptermodule.GetHostNameBean.process(com.sap.aii.af.lib.mp.module.ModuleContext,com.sap.aii.af.lib.mp.module.ModuleData) throws com.sap.aii.af.lib.mp.module.ModuleException method on bean instance com.sap.adaptermodule.GetHostNameBean@299c92f0 for bean sap.com/UserModule_EARxml|UserModule_EJB.jarxml|GetHostName in application sap.com/UserModule_EAR.; nested exception is: java.lang.NullPointerException; nested exception is: javax.ejb.EJBException: (Failed in component: sap.com/UserModule_EAR) Exception raised from invocation of public com.sap.aii.af.lib.mp.module.ModuleData com.sap.adaptermodule.GetHostNameBean.process(com.sap.aii.af.lib.mp.module.ModuleContext,com.sap.aii.af.lib.mp.module.ModuleData) throws com.sap.aii.af.lib.mp.module.ModuleException method on bean instance com.sap.adaptermodule.GetHostNameBean@299c92f0 for bean sap.com/UserModule_EARxml|UserModule_EJB.jarxml|GetHostName in application sap.com/UserModule_EAR.; nested exception is: java.lang.NullPointerException
any help is appreciated
Regards,
Teja

Hi Prateek,
Im facing the same issue...,So i thought I should add to this thread instead of posting a new one
The com channel looks as follows
Processing sequence:
Number      ModuleName                   Type                                  moduleKey
1                ModuleName                     LocalEnterpriseBean          0
2               CallSapAdapter                 LocalEnterpriseBean          2
Module Configuration
I have nt added anything in this module configuration tab...can u help me on this
Edited by: Ibrahim on Sep 9, 2009 12:50 PM

Mapping error in File to File Scenario.

In a file to file scenario some times sender communication channel picked the file, before the file is completely copied to the directory Though the poling intervals is 300 seconds. To my assumption, assume that the sender communication channel lastly polled on 10:10:10 and i am coping a file after 285 sec that is 10:14:55 and file size is 20 mb that takes 50 sec to copy. but the next sender communication channel poling is 10:15:10. here the file is partially copied but the communication channel picked the file and process. The scenarios throws mapping error because of in correct input file. This rarely accords but how to handle this. i want the cc to wait until the file is completely copied to the dir and then poll.

Hi ,
But there is some problem with system i guess. Adapter engine first load the whole file and then send it to Integration engine where after receiver and interface determination , mapping is excuted. So the fact that adapter picked up half of the file and tried to process does not seem correct.
Ideally this behaviour should not occurs.
If you are observing similar with all the adapter , you should also cross check with SAP support team.
Ranjeet Singh.

IDOC to PDF and XML via EMail: using InputAttachment interface in mapping

Hello Together,
I am working on the following scenario:
IDOC --> Transformation Nr. 1 IDOC-XML; Transformation Nr.2 XML- PDF --> Email with 2 Attachments XML and PDF.
Till now Iu2019ve managed "IDOC to Email" with XML-Attachment. Therefore I used MailPackage and SwapBean. Unfortunately I didnu2019t see any possibility to send PDF attachment with MailPackage approach.
Thatu2019s why I decided to change the scenario in this way to avoid using of MailPackage:
u2022 first step: IDOC to FTP (2 XML files)
u2022 second step: FTP (1. file = payload + 2. file= attachment) to Email with one XML-attachment
It works without MailPackage, but I still need the PDF-attachment. In the moment I am trying to read the XML-attachment, to transform XML2PDF and to add the second attachment to the message inside of mapping . I use InputAttachment and OutputAttachment interfaces.
http://help.sap.com/javadocs/pi/SP3/xpi/com/sap/aii/mapping/api/InputAttachments.html
Unfortunately the reading of the XML-attachment with u201CInputAttachementu201D interface inside of mapping doesnu2019t work. Tracing says: "there is no attachment".
So my questions are:
1. Is it possible to work with Input- and OutputAttachement interfaces inside of mapping? Or does it work only inside of adapter module?
2. If it works inside of mapping, how can I test it in design time?
If you see any other way to solve my problem, let me know please.
Thank you a lot, regards Anna

Question Nr. 1:
"... Mapping programs are executed in the Java part of SAP NetWeaver AS. Consequently, the mapping runtime transfers the message payload from the ABAP part of the SAP NetWeaver Application Server to the Java part before the mapping program is executed. Since mapping programs do not usually access any MIME attachments in a message, the default setting is for the mapping runtime to transfer the payload only and not the attachments. This applies for both attachments that are removed as part of MTOM optimization in the Web services runtime, as well as for attachments that a sender sends together with a payload by using proxy methods in the XI runtime.
If you want to access an attachment from a mapping program, it must have been transferred from the ABAP part to the Java part prior to execution. You can configure this in the basic settings of the operation mapping in which you reference the mapping program (select the Read Attachments checkbox)..."

I have a scenario. Import IDOC into PI and PI transform IDOC to Excel. Using mail adapter attach that Excel using pi and send to customer. Can you please help me on the same?

HI Experts,
I have a scenario. Import IDOC into PI and PI transform IDOC to Excel. Using mail adapter attach that Excel using pi and send to vendor. Can you please help me on the same?
Thanks
SaiSreevastav

Hi Sai,
you can use XSLT or java mapping or adapter module to convert IDOC xml to XLS. Please refer the below blog
Convert incoming XML to Excel or Excel XML – Part 1 - XSLT Way
Convert incoming XML to Excel Sheet Part 2 – Adapter Module way
Convert incoming XML to Excel Sheet
then after converting to Excel, you can use the payloadswap bean in mail adapter
XI: Sender mail adapter - PayloadSwapBean - Step by step
regards,
Harish

Difference in idoc adapter header mapping between SP14 and SP19

Hi All,
i have a very strange problem.......i have 2 XI systems : XI-sandbox and XI-dev.....
XI-sandbox is on XI3.0 SP19 whereas XI-dev is on XI3.0 SP14...........
I have a file->XI->idoc scenario which is same on both XI-sandbox and XI-dev....
in receiver idoc adapter, i am using header mapping for sender service and in the sender service i am using XPATH of a field of control rec of idoc.........
this scenario works fine on XI-sandbox which is on SP19 and the idocs are sent to SAP R/3 sandbox...........but this scenario on XI-dev gives error in SXMB_MONI in XI-dev of Call adapter - "No party conversion found".........
So my question is that is there any difference in idoc adapter header mapping between SP14 and SP19.........
Thanks,
Rajeev Gupta
Message was edited by:
RAJEEV GUPTA

><i>so i cant use apply control rec values from payload.........</i>
rajeev,
I know this has nothing to do with the original problem but please do bear.
If I undertood you posts correct, the Sender Partner Name is set in the Idoc Control record in the field SNDPRN in the mapping using some mapping logic.
Now, this is the partner name with which the idoc is to be posted to thge R3 system.
if yes, then like I have pointed above, using "Take Sender From Payload" in the Receivcer Idoc Adapter is a better option as pointed in the SAP help as well.
As you are already populating the idoc control ecord with SNDPRN just make the SNDPRT as LS and then select "Take Sender from Payload" in the receiver Idoc adapter and the Sender Partner Name will not be taken from SDNPRN just as you want.
This is different from "Apply Control Records From Payload" .
Regards
Bhavesh
PS : you can ignore this reply if the situatios is too late to make this change and thanks for the patience.

How to use IDOC and RFC adapter in 1 scenario?

We have AAA field and BBB field and we want to send AAA field to receiver sap system using IDOC adapter and BBB field to receiver sap system using RFC adapter. But how to use IDOC and RFC adapter in 1 scenario and how to map and what are the design and configuration objects we require to create?

To achieve this you have to use
Two Interface Determinations
Two Communication Channels (IDOC & RFC)
& Two Receiver Aggrements.
Use the Enhanced Interface determination and give your conditions there. Based on you condition your interface mapping will be triggered and data will be sent to IDOC & RFC respectively.

Issues with creating and sending BOM XML IDOC to SAP using 2010 WCF-SAP Adapter (without using Biztalk Server)

I'm trying to replace an existing Biztalk 2006 Send BOM IDOC process, and completely remove Biztalk server from the equation. The existing Bizatalk 2006 server receives an input BOM (Bill of Materials) flat file, and using a Biztalk Map (BM08),
and Orchestration, generates an Idoc and sends it to SAP.
In my replacement C# program, I'm using the 2010 WCF-SAP Adapter, and am trying to generate the BOMMAT03 XML IDOC it to SAP.
I generated the BOMMAT03 schema from SAP using the Add Adapter Service in VS 2010. I was able to generate a BM08 XSLT from the existing BMO8 map in the current Biztalk 2006 process. I am able to run a XSLT transform on the input BOM flat
file, and generate an XML file from that.
However, I've run into a few issues. First of which, is that the XML file that is generated from the XSLT transform is NOT the same schema as the BOMMAT03 schema expects. It's somewhat similar, but different enough that I have to manually
translate between the two in my code. I've verified that both the original Bitztalk 2006 process and my replacement program use BOMMAT V3 from SAP. Question--Is Biztalk 2006 server doing some other magic to turn that transormed XML into the BOMMAT03
schema?
I ended writing code which translates the transformed XML into the BOMMAT03 schema (which is a strong typed XML IDOC at this point).
However, when I try to send the BOMMAT03 XML IDOC, I get an exception "Object reference not set to an instance of an object."
idocClient.Send(idocData, ref sadapterTxGuid);
idocData is of type BOMMAT03, and I've verified that the various fields are populated.
Any help is appreciated.

Well, putting in a MSDN subscription support ticket for Biztalk server actually helped with the issue. They didn't find, or fix the issue directly. But one of the examples (https://randypaulo.wordpress.com/tag/idoc/) they sent over, jogged my
memory, and I realized in the code snippet below, I had accidentally deleted the 1st line. Such a simple mistake, yet was easy to overlook. The URL example is almost EXACTLY like my code, but without the transform and translation code to convert
from input XML file to IDOC XML. If someone is interested in that, let me know.
//Forgot the 1st line.
idocClient = new IdocBOMMAT03SIEIS_WED_BOMMAT03V3R700Client(binding, endpointAddress);
idocClient.Send(idocData, ref sadapterTxGuid);
For anyone else interested in knowing, you CAN send a strongly typed IDOC to SAP using C#.NET and the WCF SAP 2010 Adapter, using the IDOC Binding Client class you generated using the Add Adapter Service Reference in VS2010.
The one difference, which no one, not even the tech support from MS could tell me, was why the XSLT which I generated from the original map, did not transform the input BOM XML into the BOMMAT03 XML. Instead, it transformed it into an intermediate
XML, which resembled the BOMMAT03 IDOC XML, but still needed to be translated to the BOMMAT03 IDOC format.
The tech support person swore up and down that it should. But I believe that something happens in Biztalk server, after the Mapping occurs, maybe in the Pipeline, which converts that
intermediate XML into the final BOMMAT03 IDOC XML format.
I do think that the examples are severely lacking in showing how to send a strong typed IDOC using C# and the WCF-SAP Adapter. Even worse, the examples are completely lacking in how to actually generate a weakly typed IDOC. They show how to send
that weakly typed IDOC, but show me, or give me a class to be able to generate it.
I realize that this is not quite the "recommended way" to do it, but in reality, not everyone wants or even needs a full Biztalk installation. For some simple stuff like this, a C#.NET program and WCF-SAP adapter do the trick.

IDOC Serialization(EOIO) using IDOC Adapter throwing Mapping error

Similar Messages

Maybe you are looking for