EO or EOIO

Hi gurus,
I have to set up an IDoc to File scenarios for daily master data distribution.
I wonder what QoS is better to use and why, since a lot of other messages (EO) are going through xi all the time.
Janos

Thanks, for your prompt answer.
It's just another thing that bothers me.
I have some reservations to use EO for MD distribution, because
I am afraid that the performance of other time critical EO messages
may decrease wheb lot of IDOCs will be sent out. Thus my first thought
was to put the MD Idoc distribution in its own queues, using EOIO for them.
But I am not sure if this it the right approach to achieve that
- MD Idoc distribution (Idoc to file) can be processed slowly,
- other messages (QoS=EO, Proxy to Soap scenario) must be processed fast.
Appreciate any comment.
Janos

Similar Messages

PI 7.11 handling EOIO Backlog in Engine Status for a Receiver Component

Hi
In our PI 7.11 we have for more days had an EOIO Backlog of 120 messages for one of our receiver components when checking the Engine status Backlog tab (RWB -> Component Monitoring -> Adapter Engine -> Engine Status -> Backlog tab -> Receiver Components section)
My question is how I can process the backlog. There is nothing to see in either smq1/smq2/sm58 on the PI system or in smq1/smq2 on the receiver system.
Thanks in advance.
Mikael

HI,
Go to MessagingSystem of the server and there the option for the EOIO Sequence Monitoring will be available and can make use of that...
MessagingSystem link is http://host:port/MessagingSystem there the message which bloking the other messages can be seen...
HTH
Rajesh

EOIO is not working for file- BPM- Proxy scenario.

Hi All,
I have one File to BPM (Merge pattern ) to Proxy scenario.
I have two file communication channel at the sender side and defined QOS as EOIO for both. In SXMB_MONI it assings same queue for all messages.
BPM is merging that messages. However during that it assings different queue for merged messages.
When it comes to proxy , again different queues are assingned to the messages.
Is there any way I can define QOS in BPM or at the proxy side ( I know it should be at the sender side only , but it's not working..)
Thanks & Regards,
Dijesh Tanna.

HI,
Within the current release the BPM will always only use EO (SAP Note 833740).
May be the SAP note 905049 will help you on this ...
Thanks
Swarup

Proxy to File using EOIO

Hi Experts,
I have a scenario where I need to send data from SAP to PI so I am using proxy to file scenario. Here i need to send huge amount of data.
In some blog i saw that proxy can handle only some maximum amount of data.(but not 100% sure how much size of data the proxy can handle)
So i decided to call the proxy multiple times by sending only some 'n' no. of records and kept the receiver file adapter in append mode.
The problem here is the data is not appending in the order in which i am sending from SAP. In sxmb_moni the messages were showing the QoS as 'EO'.
Is it possible to change the QoS to EOIO?
Thanks & Regards
Stephen Rouvier

From SAP documentation:
"The sender of a message uses the attribute Quality of Service (QoS) to determine how a message is delivered"
hence ..as the File adapter supports all Qos, the Proxy can be called with Qos EOIO and the adapter will maintain the Qos as requested.
You should how ever try and send the data in a bulk and see how the Proxy handle it.
What is the nature of the data exported and for what purpose?

Change "Quality of Service" EOIO to EO for a XI Purache Interface in EBP

Hello Colleagues,
we have a PO interface in place but some problems with Message processing at Adapter. To solve the problem we try to change the Quality of Server EOIO to EO but the Quality of Service comes from the EBP system at XML Message header.
Please, in that location on the EBP system are we able to change the Quality of Service?
Many thanks in advance!
Jochen

Hi Barry,
The EBP system send POs (also calalog messages) via integration engine (SXMB_MONI on EBP) to the XI system (Integration Server) and the XI system sends the messages out to the Vendor via SOAP.
The messages which are send by EBP are with QOS EOIO at message header.
Regards,
Jochen

FTP Sender Adapter with EOIO for Large files

Hi Experts,
I am Using XI 3.0 version,
My scenario is File->XI->FIle, I need to pick the files from FTP Server , there are around 50 files in it each of 10 MB Size.
So i have to pick the files from FTP folder in the same order as they put into folder , i,e.., FIFO.
So in Sender FTP Comm channel , i am Specifying
Qos = EOIO
queue name = ACCOUNT
whether the files will be picked in FIFO into the queue XBTO_ACCOUNT?
So my question is,
what is the procedure to specify the parameters so that it will process in FIFO?
What would be the BEST PRACTICE to acheive it for better performance point of view.
Thanks
Sai.

Hi spantaleoni ,
I want to process the files using FTP protocol which should be in FIFO ,
ie.., Files placed first in a folder should be picked up first and remaining one next and so on.
So if i use FTP ,
Then to process the files in sequence i.e, FIFO
the processing parameters
Qos= EOIO
Queue name = ACCOUNT
would process the files in FIFO.
and to process large files (10MB size) what would be the best Polling interval secs.
Thanks,
Sai

Receiver file adapter behave like a EOIO

I have an interface wherein R/3 sends IDocs to XI and the messages have QOS as EO. XI triggers a proxy interface which retrieves a certain data back from R/3. Once the mapping is done in XI, the receiver, a file adapter creates a bunch of files for each message.
Here's the data scale.
1 IDoc triggers 1000+ proxy message interfaces which triggers over 2000+ files.
All messages in the receiver queue (XI_SERIALIZE00xx) go into EOIO status. What is driving this EOIO message type (IDocs are coming in as EO messages).
The problem, if one message gets into system error, all go into holding status. They are all independent of each other. How can I fix this??
Thanks,
Pam

After digging into this further...here's how it is working and I'm figuring out how the queue id got assgined to proxy inbound (sender).
- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:QualityOfService>ExactlyOnceInOrder</SAP:QualityOfService>
<SAP:QueueId>XI_SERIALIZE0012</SAP:QueueId>
</SAP:ReliableMessaging>
Here's the flow.
IDoc message (r/3) to ZIDoc_in (XI) - the messages are EO
ZIDoc_in (R/3 proxy) to ZIDoc_out (XI) - the messages here are set as EOIO with the queueid from above.
ZIDoc_out (XI) to ZFile_in (File receiver) - thousands of messages go in as EOIO
as per this blog
- /people/arulraja.ma/blog/2006/08/18/xi-reliable-messaging-150-eoio-in-abap-proxies
I did not find the queue id set in the abap proxy code. So where is this "XI_SERIALIZExxxx" being set and how is it becoming EOIO?
Not sure if the parameter in the interface determination is doing this since the messages from the proxy shows up as EOIO.
Thanks.

EOIO (File 2 IDOC scenarion) in 4.6c system

Hello Experts,
My client wants to process Exactly once in order message processing in SAP 4.6c system (inbound side)(File 2 idoc ).
I have read from some of the forum threads saying that, to implement this solution using PI, SAP system version WAS should be minimum 6.40.
Can you provide me your inputs for implementing EOIO message processing (File to IDOC ) scenario in 4.6c with / without using PI
Thanks
Sai

Question1:
you want to preserve the message order exactly, choose the Switch Procedure and enter the required number of queues with the new prefix.
The Switch Procedure is time-consuming and performance-intensive and is therefore only to be used in a running productive system.
4. Select Continue and schedule the SXMS_EOIO_REORG report to reorganize the queue by entering the required values.
The Switch Procedure status changes from inactive () to started (). The reorganization job analyzes the old queues according to messages available and creates corresponding stop entries in the new queues. The status also changes from started () to active ().
If the Switch Procedure is active, all new inbound messages are redirected to the new queue set. The reorganization job periodically checks the old queues for messages and deletes the corresponding stop entries in the new queues, as long as no more messages are found in the old queue set all stop entries are deleted from the new queue set.
If you manually delete the stop entries, the queues involved will be stopped with an error message.
http://help.sap.com/saphelp_nwpi71/helpdata/en/46/9555d5e85613eae10000000a155369/content.htm
Question 2:
PI will not bother about what happend in ECC system.It will pass the messages to ECC queue and ECC will Handle EOIO.

In case of EOIO , then QUEUE NAME in File Adapter

Hi
   I'm using File Adpater in the Sender side   (FTP ).. and in the processing parameters if i choose the Quality of Service : EOIO   then system was asking as next parameter is Queue Name .--?
   Here   what can we give as queue name.. Is that is the new name.. Or any existed queue name... how we can identify that particular queue   name..
helpful answers will be appriciated
regards
Jain

>    I'm using File Adpater in the Sender side   (FTP ).. and in the processing parameters if i choose the Quality of Service : EOIO   then system was asking as next parameter is Queue Name .--?
>
>    Here   what can we give as queue name.. Is that is the new name.. Or any existed queue name... how we can identify that particular queue   name..
Go through this...
XI Asynchronous Message Processing: Understanding XI Queues -Part I

File Splitting for Large File processing in XI using EOIO QoS.

Hi
I am currently working on a scenario to split a large file (700MB) using sender file adapter "Recordset Structure" property (eg; Row, 5000). As the files are split and mapped, they are, appended to a destination file. In an example scenario a file of 700MB comes in (say with 20000 records) the destination file should have 20000 records.
To ensure no records are missed during the process through XI, EOIO, QoS is used. A trigger record is appended to the incoming file (trigger record structure is the same as the main payload recordset) using UNIX shellscript before it is read by the Sender file adapter.
XPATH conditions are evaluated in the receiver determination to eighther append the record to the main destination file or create a trigger file with only the trigger record in it.
Problem that we are faced is that the "Recordset Structure" (eg; Row, 5000) splits in the chunks of 5000 and when the remaining records of the main payload are less than 5000 (say 1300) those remaining 1300 lines get grouped up with the trigger record and written to the trigger file instead of the actual destination file.
For the sake of this forum I have a listed a sample scenario xml file representing the inbound file with the last record wih duns = "9999" as the trigger record that will be used to mark the end of the file after splitting and appending.
<?xml version="1.0" encoding="utf-8"?>
<ns:File xmlns:ns="somenamespace">
<Data>
     <Row>
          <Duns>"001001924"</Duns>
          <Duns_Plus_4>""</Duns_Plus_4>
          <Cage_Code>"3NQN1"</Cage_Code>
          <Extract_Code>"A"</Extract_Code>
     </Row>
     <Row>
          <Duns>"001001925"</Duns>
          <Duns_Plus_4>""</Duns_Plus_4>
          <Cage_Code>"3NQN1"</Cage_Code>
          <Extract_Code>"A"</Extract_Code>
     </Row>
     <Row>
          <Duns>"001001926"</Duns>
          <Duns_Plus_4>""</Duns_Plus_4>
          <Cage_Code>"3NQN1"</Cage_Code>
          <Extract_Code>"A"</Extract_Code>
     </Row>
     <Row>
          <Duns>"001001927"</Duns>
          <Duns_Plus_4>""</Duns_Plus_4>
          <Cage_Code>"3NQN1"</Cage_Code>
          <Extract_Code>"A"</Extract_Code>
     </Row>
     <Row>
          <Duns>"001001928"</Duns>
          <Duns_Plus_4>""</Duns_Plus_4>
          <Cage_Code>"3NQN1"</Cage_Code>
          <Extract_Code>"A"</Extract_Code>
     </Row>
     <Row>
          <Duns>"001001929"</Duns>
          <Duns_Plus_4>""</Duns_Plus_4>
          <Cage_Code>"3NQN1"</Cage_Code>
          <Extract_Code>"A"</Extract_Code>
     </Row>
     <Row>
          <Duns>"9999"</Duns>
          <Duns_Plus_4>""</Duns_Plus_4>
          <Cage_Code>"3NQN1"</Cage_Code>
          <Extract_Code>"A"</Extract_Code>
     </Row>
</Data>
</ns:File>
In the sender file adapter I have for test purpose changed the "Recordset structure" set as "Row,5" for this sample xml inbound file above.
I have two XPATH expressions in the receiver determination to take the last record set with the Duns = "9999" and send it to the receiver (coominication channel) to create the trigger file.
In my test case the first 5 records get appended to the correct destination file. But the last two records (6th and 7th record get sent to the receiver channel that is only supposed to take the trigger record (last record with Duns = "9999").
Destination file: (This is were all the records with "Duns NE "9999") are supposed to get appended)
<?xml version="1.0" encoding="UTF-8"?>
<R3File>
     <R3Row>
          <Duns>"001001924"</Duns>
          <Duns_Plus_4>""</Duns_Plus_4>
          <Extract_Code>"A"</Extract_Code>
     </R3Row>
     <R3Row>
          <Duns>"001001925"</Duns>
          <Duns_Plus_4>""</Duns_Plus_4>
          <Extract_Code>"A"</Extract_Code>
     </R3Row>
     <R3Row>
          <Duns>"001001926"</Duns>
          <Duns_Plus_4>""</Duns_Plus_4>
          <Extract_Code>"A"</xtract_Code>
     </R3Row>
          <R3Row>
          <Duns>"001001927"</Duns>
          <Duns_Plus_4>""</Duns_Plus_4>
          <Extract_Code>"A"</Extract_Code>
     </R3Row>
          <R3Row>
          <Duns>"001001928"</Duns>
          <Duns_Plus_4>""</Duns_Plus_4>
          <Extract_Code>"A"</Extract_Code>
     </R3Row>
</R3File>
Trigger File:
<?xml version="1.0" encoding="UTF-8"?>
<R3File>
          <R3Row>
          <Duns>"001001929"</Duns>
          <Duns_Plus_4>""</Duns_Plus_4>
          <Ccr_Extract_Code>"A"</Ccr_Extract_Code>
     </R3Row>
          <R3Row>
          <Duns>"9999"</Duns>
          <Duns_Plus_4>""</Duns_Plus_4>
          <Ccr_Extract_Code>"A"</Ccr_Extract_Code>
     </R3Row>
</R3File>
I ve tested the XPATH condition in XML Spy and that works fine. My doubts are on the property "Recordset structure" set as "Row,5".
Any suggestions on this will be very helpful.
Thanks,
Mujtaba

Hi Debnilay,
We do have 64 bit architecture and still we have the file processing problem. Currently we are splitting the file into smaller chuncks and processsing. But we want to process as a whole file.
Thanks
Steve

MQ Series - Error while reading messages from MQ in Sender adapter if EOIO

Dear all,
we've configured a scenario with a sending JMS-adapter (MQSeries). With configured Quality-Of-Service = EO everything works fine. If we switch to Quality-Of-Service = EOIO we get the following error message:
com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Could not assign next free EOIO sequence number for SC: OUTBOUND_TEST_MQ_SERIES_QUEUE_4__. Reason: Problem inserting b315acf4-61f3-42dc-3642-85450666fe91(OUTBOUND) into the database: java.lang.NullPointerException: DeliveryException: Could not assign next free EOIO sequence number for SC: OUTBOUND_TEST_MQ_SERIES_QUEUE_4__. Reason: Problem inserting b315acf4-61f3-42dc-3642-85450666fe91(OUTBOUND) into the database: java.lang.NullPointerException at com.sap.aii.adapter.jms.core.channel.filter.SendToModuleProcessorFilter.filter(SendToModuleProcessorFilter.java:105)
Any ideas?
Kind regards, Stefan

We have the same issue, how did you solve yours?
For us it works fine with EO but EOIO fails with the same error message...
Kr,
Frederik-Jan.

EOIO Quality of Service

Hi guys,
We have developed a File-XI-Idoc scenario, which works fine.
The problem is that we want each file that is found in the folder where XI reads files, to be processed first and the corresponding Idoc that is produced from the mapping to be posted in receiver R/3 system first.
In order to achieve that we have used EOIO QoS in processing parameters of sender file communication channel. Although, files are processed by XI one by one, since they are put in the same queue, it is not guaranteed that Idocs are posted to R/3 in the same sequence,
We had a case that Idocs were posted exactly at the same time in receiver R/3 system and the one that should be processed second was processed first. The second Idoc (that should be processed first) was locked due to concurrent modification of the same material.
Is there something else that I can do in receiver Idoc adapter, for example??
Evaggelos

Use the Queue Processing option of the receiver Idoc channel
Queue Processing
If the function module IDOC_INBOUND_IN_QUEUE is to be used, set the relevant indicator. It is used for IDocs that are serialized by queues (quality of service is EOIO). This module is only available in SAP Web AS 6.40 and higher. If it is not available, the function module IDOC_INBOUND_ASYNCHRONOUS is called. The indicator only takes effect in SAP systems Releases 4.0 and higher. Calls for the queue processing function module are placed in the qRFC queue.
Regards,
Prateek

IDoc Sender - XI - Proxy Receiver with EOIO?

Hi all,
1) I'm sending custom Message Type/IDoc to XI using function module MASTER_IDOC_DISTRIBUTE from 4.7 ERP/6.2 Basis system.
2) In XI's integration engine I will be mapping the IDoc record layout to my proxy record layout. XI is Netweaver 04/6.4 Basis
3) The last step is to use the Proxy adapter to send the data to my receiver which is a BW Netweaver 04S/7.0 Basis system.
I know how to guarantee EOIO during step 3 and within my receiving system. Can I guarantee steps (1) and (2) above use QoS EOIO? If so any thoughts/discussion on how to do that would be appreciated.
Thanks!

Hi Shaun,
unfortunately in this case there is no chance..
You could pack idocs and send them all togheter, this is a queue-like processing but is not a robust and stable approach.
All you can do is to enqueue starting from XI configuring the right entries in table IDXQUEUE.
Regards,
Sergio

Best practice for handling errors in EOIO processing on AEX?

Hi,
I'm looing for resources and information describing the best practice on how to handle processing errors of asynchronous integrations with Exactly-Once-In-Order QoS on an AEX (7.31) Java only installation. Most information I've found so far are describing a the monitoring and restart jobs on AS ABAP.
Situation to solve:
multiple different SOAP messages are integrated using one queue with an RFC receiver. On error the message status is set to Holding and all following messages are Waiting. Currently I need to manually watch over the processing, delete the message with status holding and restart the waiting ones.
Seems like I can setup component based message alerting to trigger an email or whatever alert. I still need to decide on how to handle the error and resolve it (ie. delete the errornous message, correct the data at sender and trigger another update). I still need to manually find the oldest entry with status waiting and restart it. I've found a restart job in Background jobs in configuration and monitoring home, but it can be only scheduled in intervals of 1 or more hours.
Is there something better?
Thank you.
Best regards,
Nikolaus

Hi Nikolaus -
AFAIK - For EOIO, you have to cancel the failed message and then process the next message in the sequence manually..
Restart job only works the messages which are in error state but not in holding state.. So you have to manually push the message... So there is no other alternative.
But it should not be that difficult to identify the messages in a sequence..
How to deal with stuck EOIO messages in the XI ... | SCN
Though it is for older version, it should be the same.. you should be able to select the additional columns such as sequence ID from the settings..

Error In Receiver BC adapter(EOIO not supported by protocol BC.)

Hi Experts ,
My Scenario is ABAP proxy to SAP BC .I had bellow error in Receiver BC adapter .
Adapter Framework caught exception: Delivery semantics EOIO not supported by protocol BC.
Error Delivering the message to the application using connection BC_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.InvalidParamException: Delivery semantics EOIO not supported by protocol BC..
Please help how to resolve this .
Regards
Upendra.V
Edited by: upendra v on Oct 4, 2010 2:08 PM

HI Anuradha,
Check the below link for receiver mail configuration and follow the steps accordingly.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a0a27c01-26b0-2c10-bd8a-94498efa7ff6?quicklink=index&overridelayout=true
Regards,
Naveen

File Adapter with EOIO

Hello,
My process : File -> XI -> RFC
I want to use EOIO, so I active "Quality Of Service" EOIO in the file adapter and put the name "FileQueue" for the queue.
When I test it, I can see an error in the adapter framework log via the web browser :
Error - Exception caught by adapter framework: DeliverySemantics EOIO not supported
Error - Delivery of the message to the application using connection AFW failed, due to: DeliverySemantics EOIO not supported.
Then the message is put in a WAIT status and is reprossed 3 or 4 time. Then a System error status is raised.
What's wrong ?
Thanks
Regards,
Chris

It was impossible until SP11.
See SAP NOTE on FAQ RFC Adapter : 730870

EO or EOIO

Similar Messages

Maybe you are looking for