Split TRFC Queues for a single IDOC

How can I split the Queues at TRFC for a single interface in R/3 --> XI.
Regards
krishna.

Hi,
My scenario is IDOC --> JDBC. Here I have only one IDOC to send data to XI where I have two database systems.
XI-->JDBC: done with splitting the data to two receivers.
R/3-->XI: One IDOC (with EOIO) will come to XI.
When the data meant for two receivers (say 100 messages) has been sent (ie.100 IDOCs) to XI.
As it is EOIO, all the messages meant for two receivers are coming one by one (at TRFC) which sometimes leads to block the queue because of errors in data. So I want to seperate the messages before coming to XI.
Tell me if this is possible?
Regards
Krishna.

Similar Messages

Collect Multiple IDOC(Single IDOC type) to single file using BPM

Hi All,
When i am generating multiple IDOC for the same message type, i am getting multiple payload for the same as a result i used to get multiple files generated in application server.
Now if i use BPM only to collect multiple IDOC to a file then what all the steps that i need to follow for the same.
Ex: I want to post 10 IDOC for a single IDOC type,, Now using BPM in XI i want to collect all the 10 IDOCs with multiple payload into one single message and then want to process this in XI to generate the file.
It would be glad if anyone refer me a good step by step blog for the same.
Thanks in advance,
Jay

Thanks a lot Abhisek.
I have also got a blog explaining the exact thing. But in the blog the ID part was missing which is present in the link you have provided.
I will be glad if you can through some light on the ID part,, however the IR part and the BPM part is now mostly okay to me.
I will configure this today only,, and may seek your help for any huddle.
Thanks a lot once again.
Regards,
Jay.

TRFC Queue

Hi,
Is there any job that can check the trfc queues for any error entries and remove it automatically so that it process the next one in the queue.
Regards
Krish

> Is there any job that can check the trfc queues for any error entries and remove it automatically so that it process the next one in the queue.
Using this program you can delete RSARFCER Delete various LUWs
[http://help.sap.com/saphelp_nw04/helpdata/en/25/bcfa40badbf46fe10000000a1550b0/content.htm]
Thanks
Siva

Splitting multiple IDoc XML files into single IDoc messages for R/3

Hi all. I have a problem splitting IDoc XML files coming in to XI. I currently have an interface that takes in single store sale IDoc transactions (type WPUBON01) in an IDoc XML file. I then have some complex graphical mapping on the IDoc before sending to R/3 via the IDoc adapter. This works fine. However, we now wish to include multiple sales in one file i.e. many WPUBON01 IDocs. I could use message splitting to do this BUT the mapping is so complex, I do not wish to have to change it to enable the processing of many IDocs in one file instead of just one.
What I want to do: have one mapping splitting a multiple IDoc XML file into single IDoc messages and then another taking these single messages as before and performing the mapping. I cannot find a way to do this in one interface; the main problem I'm having is getting XI to split the multiple IDocs into many single IDoc messages within XI itself. I'd be very grateful for any advice on the best way to do this.
Thankyou.
Stuart Richards (Halfords, UK)

Bhavesh,
Thanks again for a clear explanation... I'm moving forwards but still struggling. I've been on this all afternoon today (after a break on other things) and just cannot get my message to split properly (though the SOAP adapter problem I had earlier is now fixed!). If my initial IDoc XML file contains this format:
<WPUBON01><IDOC>....</IDOC>
<IDOC>....</IDOC>
<IDOC>....</IDOC></WPUBON01>
.. I'm not sure what the cardinaility on the first message mapping and interface mapping should be. I'd have thought the source interface would be 1 and the target would be 0..unbounded but this isn't working. I'm trying different things but I get different errors each time. Currently, I have the above cardinality in my first interface and I'm passing in the following data:
<WPUBON01><IDOC><EDI_DC40><TABNAM>EDI_DC40</TABNAM><MANDT /><DOCNUM /><DOCREL>620</DOCREL><DIRECT>2</DIRECT><IDOCTYP>WPUBON01</IDOCTYP><MESTYP>WPUBON</MESTYP><MESCOD>ST6</MESCOD><SNDPOR>WPUX</SNDPOR><SNDPRT>KU</SNDPRT><SNDPRN>0518</SNDPRN><RCVPOR /><RCVPRT>KU</RCVPRT><RCVPRN>0518</RCVPRN><REFINT>00000003832292</REFINT></EDI_DC40><E1WPB01 SEGMENT="1"><POSKREIS>0518</POSKREIS><KASSID>29</KASSID><VORGDATUM>20071029</VORGDATUM><VORGZEIT>160633</VORGZEIT><BONNUMMER>1001</BONNUMMER><KASSIERER>100</KASSIERER><CSHNAME> </CSHNAME><BELEGWAERS>GBP</BELEGWAERS><E1WPB02 SEGMENT="2"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="3"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="4"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="5"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="6"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="7"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="8"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="9"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="10"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="11"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="12"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="13"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="14"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="15"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="16"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB06 SEGMENT="17"><VORZEICHEN></VORZEICHEN><ZAHLART>PTCS</ZAHLART><SUMME> </SUMME><KARTENNR /><ZUONR>1001</ZUONR></E1WPB06></E1WPB01></IDOC><IDOC><EDI_DC40><TABNAM>EDI_DC40</TABNAM><MANDT /><DOCNUM /><DOCREL>620</DOCREL><DIRECT>2</DIRECT><IDOCTYP>WPUBON01</IDOCTYP><MESTYP>WPUBON</MESTYP><MESCOD>ST6</MESCOD><SNDPOR>WPUX</SNDPOR><SNDPRT>KU</SNDPRT><SNDPRN>0518</SNDPRN><RCVPOR /><RCVPRT>KU</RCVPRT><RCVPRN>0518</RCVPRN><REFINT>00000003832293</REFINT></EDI_DC40><E1WPB01 SEGMENT="1"><POSKREIS>0518</POSKREIS><KASSID>29</KASSID><VORGDATUM>20071029</VORGDATUM><VORGZEIT>160634</VORGZEIT><BONNUMMER>1002</BONNUMMER><KASSIERER>100</KASSIERER><CSHNAME> </CSHNAME><BELEGWAERS>GBP</BELEGWAERS><E1WPB02 SEGMENT="2"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="3"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="4"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="5"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="6"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="7"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="8"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="9"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="10"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="11"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="12"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="13"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="14"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="15"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="16"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB06 SEGMENT="17"><VORZEICHEN></VORZEICHEN><ZAHLART>PTCS</ZAHLART><SUMME> </SUMME><KARTENNR /><ZUONR>1002</ZUONR></E1WPB06></E1WPB01></IDOC><IDOC><EDI_DC40><TABNAM>EDI_DC40</TABNAM><MANDT /><DOCNUM /><DOCREL>620</DOCREL><DIRECT>2</DIRECT><IDOCTYP>WPUBON01</IDOCTYP><MESTYP>WPUBON</MESTYP><MESCOD>ST6</MESCOD><SNDPOR>WPUX</SNDPOR><SNDPRT>KU</SNDPRT><SNDPRN>0518</SNDPRN><RCVPOR /><RCVPRT>KU</RCVPRT><RCVPRN>0518</RCVPRN><REFINT>00000003832294</REFINT></EDI_DC40><E1WPB01 SEGMENT="1"><POSKREIS>0518</POSKREIS><KASSID>29</KASSID><VORGDATUM>20071029</VORGDATUM><VORGZEIT>160634</VORGZEIT><BONNUMMER>1003</BONNUMMER><KASSIERER>100</KASSIERER><CSHNAME> </CSHNAME><BELEGWAERS>GBP</BELEGWAERS><E1WPB02 SEGMENT="2"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="3"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="4"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="5"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="6"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="7"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="8"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="9"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="10"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="11"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="12"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="13"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="14"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="15"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="16"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB06 SEGMENT="17"><VORZEICHEN></VORZEICHEN><ZAHLART>PTCS</ZAHLART><SUMME> </SUMME><KARTENNR /><ZUONR>1003</ZUONR></E1WPB06></E1WPB01></IDOC></WPUBON01>
In the message monitor, I get a chequered flag. Great. However, I get the dreaded error 500 in the SOAP receiver comm channel:
SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
Exception caught by adapter framework: SOAP Error
Delivery of the message to the application using connection AFW failed, due to: SOAP Error.
Any ideas as to what this might be?! I'm getting there.... if I get a solution out of this, I promise to write the blog myself!
Cheers
Stuart

BD87 hide "idoc entries in tRFC queue" by assigning to status or other meth

Hi,
I am working on the inbound side of an idoc interface for message type MATMAS. My problem is that when I enter in BD87 there are more than 400 hundred entries in "idoc entries in tRFC queue". Now, whatever filter I put on the first screen this line appears. Even, if I enter with a specific idoc number. These entries are obviously outbound errors and are completely irrelevant to the interface I am working on but will make the reprocessing screen unnecessarily complicated for the users. So, basically I want to allow the end user to filter out these messages.
I noticed that the errors "idoc entries in tRFC queue" aren't associated to a status and I was wondering if it is possible to give them a status value and so make them sensitive to a status filter. But if this isn't possible any solution to hide these error messages from the end user would be equally valid.
I know someone will probably suggest that the best solution would be to remove all old entries from tRFC queue in SM58 and that there shouldn't be so many idoc in entries in the tRFC queue. The problem is that it is not my role to monitor tRFC in production and if it has not been regularly monitored up to now then it probably won't be in the future.
Many thanks in advance,
Jamie.

Hi Jamie,
To the best of my knowledge the shown outbound RFC entries in BD87 are a feature that cannot be suppressed. I.e. in the coding of BD87 one can see logic where it automatically checks for outbound RFC errors and adds those to the output.
In general IDoc status 03 should be associated with the outbound RFC errors. Yet, when one sees those in BD87, the IDoc status field is empty. Along your train of thought I had also previously tried to suppress those displayed IDocs by adding a filter for suppressing status 03 or blank status, but nothing helps. And as you correctly point out, even when using BD87 on a single IDoc (e.g. specified via IDoc number), the transaction will still display the outbound RFC errors.
So unless somebody else has some good idea or insight, I'm afraid you're stuck with that behavior.
Cheers, harald

IDOCs in TRFC Queue

Hi,
We have a ALE scenario where we send IDOCs to other SAP system.
The IDOCs we send are sitting in TRFC queues, they are not sent to the target system. I checked all the ALE settings, they are fine. The processing mode is "Immediate".
When I go to SM58 I will find the entry for the transaction with status "Transaction Recorded". If I select the entry and press F6 (Execute LUW) the IDOC is sent to the target system and the queue becomes empty.
What I am missing? I dont want to go to SM58 everytime I post an IDOC. I am sure there will be some setting to process the IDOCs from the TRFC queue automatically. Can you please let me know that?
Regards,
Ravikanth

HI,
the problem is caused by immediately processing.
Pipeline:
Outbound Processing -> sender IDOC -> TRFC Queue -> receiver IDOC - Inbound Processing
In case your are using IP (immediately Processing) at sending side your are using 1 LUW to send it to the TRFC Queue and saving IDOC at receving side -STOP.
In case your are using IP at both sides .. your are using 1 LUW for the complete Pipe.
That means this LUW is still open if the IDOc is processed in the receiving system.
ToDO:
Go to your Receiving System and check the Processing Settings. Try to use Background Jobs or get higher Batch Processing to avaoid TRF Queue Jam
Regards,
Gordon

IDoc- XI- IDoc - Problem in TRFC-Queue

Hi everybody,
in Integration Builder i have created an A2A-Scenario (Idoc->XI->IDoc).
After designing and configurating i want to send an IDoc to XI.
But the IDoc stands in the TRFC-Queue with error "no service for system <xxx> client 020 in Integration Directory."
In ID i have set Business Systems for sender and receiver both with outbound/inbound interfaces of idoc-type, which i have upload from relevant sap-system.
What is my fault?
Thanks a lot.
Greetings
Joerg Knaust

hi,
most probably it's a typo
there's no sender agreement if you're sending idocs
from r3 to the xi
1. how does your service in TCODE - IDX1 look like?
sapSID ?
2. adapter specific identifiers (do it step by step):
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a>

How to Split Single Idoc into 2 files and put some delay

Hi,
I have a IDoc to file Scenario. Invoice Idoc to Flat file scenario
this is a reuse Interface
Current Scenario we have graphical mapping(used for lookup and dynamic filename, mostly all the field mappings are 1-1) and ABAP Mapping to convert Idoc to flat file, 1 Idoc will generate 1 file.
In addition to the above case, there is 1 more requirement
Correction Invoice case. where in I get single Idoc with Multiple Item categories (Original data and Correction data)
In this case always I need to send two files(2 Idoc data), first Idoc is for Original Idoc and 2nd is Corrected Invoice, these 2 idocs should be sent with some delay.
In Correction Invoice case, I should generate 2 idocs based on Item category (PSTVY) value.
Suppose I have 4 E1EDP01 segments out of which PSTVY has value "AA" and "BB" repeated twice as shown below
<PSTYV>AA</PSTYV>
<PSTYV>AA</PSTYV>
<PSTYV>BB</PSTYV>
<PSTYV>BB</PSTYV>
So I need to generate 2 Idoc 1 for AA and other for BB.
If there is no correction Invoice, 1 idoc for 1 file will be generated.
Am planning to use BPM to delay the idocs and identigy bpm based on Document type else no bpm...
How do I split the mapping of single Idoc to 2 files based on Item category.
Thanks,
Varun

You can use the multi-mapping to split the message payloads according to business requirement (AA and BB segments values)
/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
And then send to different receivers by adding the conditions on the Receiver Determination (for example, "field = AA" go to Receiver1, and "field = BB" to to Receiver2).
http://help.sap.com/saphelp_nwpi71/helpdata/en/26/5ccd3bb4560f01e10000000a11402f/frameset.htm
Or even Extended (enhanced) receiver determination, should the scenario be more complex:
http://wiki.sdn.sap.com/wiki/display/XI/EnhancedReceiverDeterminationinSAP+XI

Idoc in trfc queue

Hi,
I have requirement where the idocs are sent to external (non sap) system, now when system is down or for some other reason the idocs gets queued up in trfc queue(SM58) , now when the system is up and running these idoc gets passed to the external system without any particular sequence, i.e. suppose for HR data there is 2 idoc for same employee and the IDOC1 should go before IDOC2 , then this not happens when the trfc queue(SM58) is cleared.
I wanted to know how to mantain this idoc Serialization so that the idoc go in sequence, i have gone through some idoc Serialization document but i think its useful when both system is receiveing system is also SAP.

Hi Sudhakar,
Check this:
Re: tRFC & qRFC
Reddy

Idoc stuck in trfc queue

Hi,
I have requirement where the idocs are sent to external (non sap) system, now when system is down or for some other reason the idocs gets queued up in trfc queue(SM58) , now when the system is up and running these idoc gets passed to the external system without any particular sequence, i.e. suppose for HR data there is 2 idoc for same employee and the IDOC1 should go before IDOC2 , then this not happens when the trfc queue(SM58) is cleared.
I wanted to know how to mantain this idoc Serialization so that the idoc go in sequence, i have gone through some idoc Serialization document but i think its useful when both system is receiveing system is also SAP.

duplicate post, locked.
Thomas

Split Single IDOC into Multiple IDOC's Based on Segment Type

Hi Experts,
I have a scenario IDOC to FILE , Split Single IDOC into Multiple IDOC's based on Segment Type
Outbound:
ZIdocName
Control Record
Data Record
Segment 1
Segment 2
Segment 3
Status Record
I should get output like below
Inbound:
ZIdocName
Control Record
Data Record
Segment 1
Status Record
ZIdocName
Control Record
Data Record
Segment 2
Status Record
ZIdocName
Control Record
Data Record
Segment 3
Status Record
Please suggest me step by step process to achieve this task.
Thanks.

Thanks a lot Harish for reply.
I have small doubt. According to your reply , If we have N number of segments in single IDOC with same fields in all segments then for splitting Single IDOC into Multiple IDOC's based on Segment Type we need to duplicate N number of target IDOC tree structure.
Is that possible to Split single IDOC into Multiple IDOC's based on Segment Type using only one Target IDOC structure without duplicating the Target IDOC structure tree.

Single idoc generation for multiple sales orders

Hi,
Pls let me know how do we generate single idoc for multiple sales orders.
Its not collecting idoc. As we know we can generate an idoc for one sales order correspondingly
my requirement is to generate single idoc number for multiple sales orders.
Do we need to write a program.

Amar,
To understand take HRMD_A04 as example. Root segment has Maximum 9999999999 defined.
Segm.type E1PLOGI
Minimum number 1
Maximum number 9999999999
Parent segment
Hier.level 2
This means that this IDOC types has capability to hold multiple HR Master data objects. PFAL program creates this IDOC and it has facility to mention the Objects per process, check selection screen.
I checked for INVOICE01/02 its not possible there. Hope this clarifies.

How to create Single Queue for more than one interfaces(XI)

Hi Experts,
I want to set up a separate queue for 3 interfaces which all are outbound IDOC to FTP.
Please let me know ' Hhow to create a queue for multiple interfaces with Quality of Service 'EO''.
Thanks,
Srinivas P.

The same reason that Apple and 3rd Party vendors put multi-size templates in one file I expect. I am trying to construct an in-house standard template for use in our company, and it is easier to manage if there is only one file to send to people rather than many - both initially and for subsequent edits / updates to the template.
Of course it would be possible to create several templates (one for each size). But since it is clear that templates can be combined, it appears sensible to do this - unless the doing of it is horridly complicated

Performance for messaging queue - queue implemented as single cache entry.

Hey Brian/All,
Has there been any progress on addressing the long standing performance issues with messaging?
i.e. messaging stores a queue within a single cache entry, which means it needs to deserialize, add item, and reserialize every time we add an item to the queue.
For push rep, this means a burst of data can bring messaging to it knees and cause a cluster to fall over (eg: a clear of a large cache, or a remote site that is unavailable causing queues to grow to a very large size).
I have also noticed that when a queue gets very large, the jmx suspend/drain times out, and throws an exception.
Cheers,
Neville.

Hi Friends,
Create a function that needs to be called on the ejbCreate.
Inside this function make the connections as in the snippet below and close it when ejbRemove() or exception.
fis                          = new FileInputStream("D:/MessageRouter_UAT/AppConfig.Properties");
props.load(fis);
fis.close();
String logPath      = props.getProperty("Log_path").trim()+".log";
logHandler      = new FileHandler(logPath);
logHandler.setFormatter(new SimpleFormatter());
logWriter.addHandler(logHandler);
logWriter.setLevel(Level.ALL);
MQEnvironment mqEnv      = null;
mqEnv      = new MQEnvironment();
MQEnvironment.hostname      = props.getProperty("MQ_HOST_NAME").trim();
MQEnvironment.port      = Integer.parseInt(props.getProperty("MQ_PORT").trim());
MQEnvironment.channel      = props.getProperty("CHANNEL_NAME").trim();
MQEnvironment.properties.put(MQC.TRANSPORT_PROPERTY, MQC.TRANSPORT_MQSERIES_CLIENT);
q_Mgr                = new MQQueueManager(props.getProperty("QUEUE_MANAGER").trim());
queueID                = q_Mgr.accessQueue(props.getProperty("ID_Queue").trim(), MQC.MQOO_OUTPUT);
queueSG                     = q_Mgr.accessQueue(props.getProperty("SG_Queue").trim(), MQC.MQOO_OUTPUT);
queueHK                = q_Mgr.accessQueue(props.getProperty("HK_Queue").trim(), MQC.MQOO_OUTPUT);
queueCL                     = q_Mgr.accessQueue(props.getProperty("CL_Queue").trim(), MQC.MQOO_OUTPUT);
Thanks,
Arun Prithviraj

How to configure queues for sending IDOCs from XI in the same order receive

Hi,
We are collecting IDOCs and sending them to XI using a background job (RSEOUT00) from R/3. When XI receiving these collected IDOCs, it's forwarding the received IDOCs into different queues for processing them and sending them to receiver system. Some times some queues are taking longer time to process the received IDOC and in the mean time the latest IDOC received getting processed and sent to receiver system. When the information related to this old IDOC is sent out to receiver system after the latest IDOC information is sent to due to delay in Queue processing, we are getting errors in the receiver system. Can somebody explain the steps to configure queues to process the IDOCs in the same order they received from R/3.

Hi,
Why not tunnel all the IDOCs to one queue for processing ?
Cheers
Colin.

Split TRFC Queues for a single IDOC

Similar Messages

Maybe you are looking for