Receiving multiple IDocs

hi all;
i have a scenario where i am receiving multiple IDocs and have to keep on receiving tthem till 15 mins.
i implemented the scenario based on
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
but my IDoc messages seems to keep on waiting and the deadline branch not getting executed.
i came across the blog:
Deadline branch not getting executed
can anyone tell what does "missed out the workflow configuration during installation" means in the blog.

Hi Mudit,
"can anyone tell what does "missed out the workflow configuration during installation" means in the blog."
From SAP Help:-
<i>Cross-component Business Process Management is integrated with the business workflow (WebFlow Engine). An integration process can send messages to a workflow and, conversely, messages from a workflow can be processed in an integration process.</i>
For more about WorkFlow:-
http://help.sap.com/saphelp_nw2004s/helpdata/en/a1/172437130e0d09e10000009b38f839/frameset.htm
Regards,
Sushumna

Similar Messages

Creation multiple idocs on creation of a Purchase order

Hi all,
I am having a requirement wherein if I create/change any purchase order with multiple Items in one system, I need to create multiple sales orders in the receiving system with each item. That is, the sending system should send multiple ORDERS idocs to the receiving system with each item as one IDoc and need to create a Sales order for each item in the receiving system.
I am able to configure the systems in such a way that if I create a Purchase order with multiple items, it is sending one ORDERS idoc with multiple and henceforth, creating only one Sales order in the receipient system. But, not able to acheive the scenario I have mentioned above, i.e., creating multiple IDocs with one item each for the same purchase order.
So, Can anybody know how to handle this scenario? Also, can you please let me know whether is there any standard procedure for handling this scenario?

Hi Adithya,
I too facing the same kind of requirement, can u please let me know how you achieved sending multiple idocs.
Thanks,
Kashif

Sending multiple IDocs (all in single file) to FTP via XI

Hi All,
We have a requirement as below where we are looking for various feasible solutions.
The requirement is to collect multiple IDocs in ERP (2000-5000 in number) per day (either Flat File or XML) and needs to be sent as a single File (which has all these IDocs) to FTP Server via XI.
BPM is not allowed to use and we are working on PI 7.0, so IDoc packaging is also not applicable. There is no mapping required, we need to just route them to FTP from ERP System.
Looking forward for various solutions.
Regards,
N. Jayanth Kumar.

Hi,
Using the XML file port at R/3 to collect the Idocs would be a feasible solution. Also, as Sunil as already pointed out, you can configure this as a pass through interface, which will improve your overall processing time.
Another solution can be to pass the Idocs to PI and then use the append mode in the receiver file adapter to collect the days idoc into a single file.
To append only idocs for a particular day, try using dynamic filename, where file would have the date in it. This way, only Idocs for a particular day would be appended.
Regards

Want to add multiple idoc type with single message type.

Hi Gurus,
I have a problem. I want to add multiple idoc type with single message type in WE20.
How we can do this in WE20 or is there any other way to do that?
Please help me.
Thanks in advance.
Srimanta.

hi,
basically in partner profile i.e. in we20 , we add details to the receiver / sender port that we have created using we21.
so what exactly we do in that is that we first use the message type for those idocs that we have created.
now based on those message type we create a process code. now this is the reason why you cannot apply several message types with the same name in we20... as process code is unque for each message type.
so thats why you can only assign the same message name to several idocs in we82 and then in we20 define the process code for that message type.
it will solve your problem.
hope this will help you!!!
Thanks & regards,
punit raval.

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

Multiple IDocs-XI-Single File Scenario

Hi All,
   We need to send multiple IDocs from R/3 to XI and then to a single file using File Adapter. Please help us with your suggestions on how to proceed using a simple solution.
Regards,
Peter

I made a program that solved the issue of collecting the IDOC in to one file.
1. The partent profile should be setup for collect idocs
2. Make a report that will select and dispatch the idocs
seudo code:
select tables with select criteria:
edidc (idoc control)
edid4 (idoc data)
one yo have made you selection into internal tables
it_final_edidc
it_final_edid4
*you can apply rules and data tranformations, eg. PEXR2002 batch per payment type.
CALL FUNCTION 'EDI_OUTPUT_NEW'
           EXPORTING
                onl_option = 'B'
            ERROR_FLAG = ' '
            NAST_RECORD =
           TABLES
                i_edidc     = it_final_edidc
                i_edidd     = it_final_edid4
           EXCEPTIONS
                OTHERS      = 1.
" EDI mesages dispatched
IF sy-subrc EQ 0.
    COMMIT WORK.
    CALL FUNCTION 'DEQUEUE_ALL'
       EXPORTING
            _SYNCHRON = ' '
         EXCEPTIONS
              OTHERS    = 1.
That work like a charm when writting the IDOC to a single file.
But when I send the IDOCS to XI like XML-IDOC I still receive one transaction per IDOC.
if anyone know how to solve that, let me know.
juan

Multiple IDocs to File using BPM

Hi All,
I have configured a scenario of multiple IDocs to file using BPM. In this scenario while I am triggering IDoc from R/3 system it is sent to the external program. I am getting in the status record of WE05 as IDoc is sent to an external system with status code 03. But I am unable to view the same message in moni of the XI system.
Also I have checked the ALE settings on both the sender and receiver side and it is fine.
Also in SM58 nothing is there in queue.
Can anyone solve this issue of mine?
Cheers,
Neethu.

Hi,
in many cases it's a problem with the RFC connection. You should try an authorization test in SM59 of the R/3 system.
This might also be useful:
http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/frameset.htm
Regards
Patrick

Multiple Idocs to XI with exception handling.

Hi,
I m doing a scenario,sending multiple idocs to file via XI.while doing dis,i m using BPM.For the BPM part i m following the blog https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2034..but [original link is broken] [original link is broken] [original link is broken] [original link is broken] wen i check in SXMB_MONI,my message isn't successfully processed out f BPM.In this,exception is triggered at d beginning.and it always throw exception and message not successfully processed out f BPM.In the workflow it is showing error in the first step and remaining steps are compIeted.Here, i m throwing exception by the use f deadline branch.Can,anybody tell me how to handle dis exception/error?

Hi Rajeev,
I am using a loop with in a block inside the BPM inside which receive step and container element is used.In parallel to loop branch,i m using deadline and exception branch same as in blog 2034.i m using infinite loop wid time limit mentioned in the deadline branch.After coming out f dis block,i m using transformation step and den send step is used.When i check in graphical workflow,i m getting error in send step stating that an empty container element is used while sending.But,wen i m checking technical workflow,i m getting error in first step after the creation of workflow and workflow started messages in the log details.after which the exception occured is shown in the workflow system..
Thanks,
Anoop Garg

Splitting to multiple IDoc

hi,
my scenrio is flie to idoc.
i recevie the file and i want to split the message coming from the file to different idoc based on a field(e.g doc. number).
i am using BPM..plz suggest me the steps type that is necessary for this process...
thanks....

please have the steps in bpm as
1. Receive step ( message received form the file content conversion )
2. Transformation step with I:N mapping with AP and AR as target message types
3. A fork without end condition
4. A Block in each of the branches of folk
5. A Send step in each of the blocks
/people/sudharshan.aravamudan/blog/2005/12/01/illustration-of-multi-mapping-and-message-split-using-bpm-in-sap-exchange-infrastructure
File->different type of mesages->split->IDOCs
also we can achieve this with XSLT see the below link may be useful..
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping

COLLECTION OF MULTIPLE IDOC

Hi All,
I am working with a scenario to collection of multiple idoc using BPM . I am working with this scenario https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2034.The [original link is broken] [original link is broken] [original link is broken] above link is almost same as my requirement .But in this link i dont find the settings for directory.Please help me to solve.
Is there any sender communication channel is required?
How any receiver detemination ,interface mapping,sender agreement and receiver agreement is required?
Please help.
Regards,
Somenath

Hi,
ID is quite simple to develop when you are done with your BPM in IR.
Import your Business Process in ID.
You need to create two receiver determinations. one from your IDoc to to your BPM and One from BPM to Actual receiver.
Same holds good for interface determination.
there will be one receiver agreement for the actual receiver,(BP to Actual file) which will contain your file adapter.
You do not need any sender agreement or communication channel when IDoc is sender as IDoc channel resides on ABAP stack.
Kulwinder
Reward if Helpful

BPM: Multiple IDOC collect into one file

Hi
I have done collecting multiple IDOCs of same type into one file using BPM
I have used the following blog which is collecting different types of IDOCs.
IDOCs (Multiple Types) Collection in BPM
But i have done collecting of IDOCs which are same type.
Source side it is showing successful and its reaching to BPM also . But in target i am not getting any file. Could any one please help me how to check where exactly I am failing.
Thanks & Regards
Sowmya

Check whether the Outbound Status is successful or not in sxm_moni. Is there any message created from Integration Process to receiver File system.
Check this
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/80a22ce8-8e72-2b10-3fba-e9511c6f0b8b
Regards,
Prateek

Create multiple idoc with multiple receivers based on value mapping table

Hi,
Scenario:
Step1 : sender sends a finance doc iin the form of an idoc. This idoc will have multiple line items based on profit center. Do determine the value of receiving comp code(header field) n receiving system(logical sys name) value mapping table has to be used.
Solution so far: I can put an rfc lookup for fetching receiving comp code from mapping table with i/p paraameter as profit center . And split the incoming idoc based on comp code value by using split by value. Now I need your advise 2 take this further.
Issue 1 : say the incoming idoc has 4 line seg wid 4 diff profit center
Profit center.       Rec comp code.   Recv sys
P1.                       C1.                        R1
P2.                       C2.                        R1
PS.                       C2.                        R1
P3.                       C3.                        R2
Nw using this info, I want 3 diff idocs to be created for each unique comp code.
Idoc 1 : for C1 wid one line item + 1 for reconsilation ( to be generated additionally)
Idoc2 : for C2 wid 2 line items + 1 for reconsilation
Idoc 3: for C3 wid 1 line item + 1 for reconsilation
Idoc 1 and idoc 2 shud be sent to R1.
Idoc 3 shud be sent to R2.
Kindly advise on this

Hi experts,
U all r pretty close, but let me put this more clearly.
Step1: create multiple idocs based on unique comp code - I'm able to do this using rfc lookup n split by value. So I get 3 idocs each for c1, c2 n c3.
Nw as per the values from value mapping table.
Idoc for c1 contains 1 line seg.
Idoc for c2 contains 2 line segs.
N idoc for c3 contains 1 line seg.
steps2 n 3, where I do not have a confirmed solution yet n need ur advise.
Step 2 : for each idoc generated I need 2 create n additional segment, mapping 4 which will be based on the values in the original segments for that idoc.
In d above scenario, idoc for c1 contains 1 line seg, nw I want 2 add one more seg to it. The amount and pisting key values in this segment wud be calculated based on the values of the amount and posting key belonging to the original segment in this idoc.
Similarly for idoc for c2 there are 2 segs, nw I need one more, means 3 in allm
Hence for idoc for c3, 1 orig already present + 1 more. = total 2.
Nw I need ur advise on how 2 generate this additional seg in each idocm
Step 3: when all dese 3 idocs are generated, ( in this case itz 3, in real time it can be n), I need to find their respective receivers using rfc lookup n then based on the receiver send 2 resp recvng systm
Nw how do I do this?
Please explain with examples if possible 4 bettr understanding.
u2020ђąu03B7kўu03C3u03C5 in advance.

FLATFILE to Multiple IDOCS

HI
My req is FLATFILE to Multiple IDOCS
C,WMMBID01,ZXYGR,SAPXYZ,DEVXY
1,H,20100101,20100919,0000000000000000,VL02
1,I,00000000000039870,72379601,000000000000000000000000,2,BD
1,I,00000000000039872,72379601,000000000000000000000000,2,BD
2,H,20100101,20100919,0000000000000000,VL02
2,I,00000000000039870,72379601,000000000000000000000000,2,BD
2I,00000000000039872,72379601,000000000000000000000000,2,BD
I Have the Flat File with above Format,
Structures
sender
Control record
--A
--B
--C
Header record
--D
--E
Item record
--F
--G
Receiver IDOC
WMMB1D01 1..1
-IDOC 1..999
--EDI_DC40
A
B
C
--E1MBXYH
D
E
--E1MBXY1
F
G
In the Flat file C-Control , h--Header , I --itemm and in the First column from 2nd row is to identify and generate the IDOC
eg ; 1--Ist IDOC
2--2nd IDOC
I am able to read the Flat file
And i have imported the IDOC from External defination with IDOC as 1....9999
Now I need how to map sender and receiver to generate multiple files
thanks

First of all you have to organize your FCC in a different way.
The result XML should be like this:
recordset
C
H
I
I
recordset
H
I
I
you use parameter ignoreRecordsetName = false (or remove it)
then you set recodset parameter Ascending
When you have the structure tht way, you can map recordset to idoc.

Error: Multiple IDOC to File

Hi
I am trying to send Multiple IDOCS to a file. While testing the same I am getting following error.
NO_RECEIVER_CASE_ASYNC
ATTRIBUTE_INV_SND_SERV IDOC to file
Follwing things I have tested:
I have Configured all the directory objects( Receiver Determination and Receiver Agreement)
I have checked the cache. It is up to date
Also the logic system is there is system----> Adapter specific configuration
Thanks
Abhishek

U said u checked system----> Adapter specific configuration
Do this check both for Sender business system and receiver (File) business system. The logical system name for file adapter must be present in SLD.
Regards,
Prateek

One IDOC split to multiple IDOC's

Scenario is in ECC 6.0 and SAP PI 7.0 .
SAP is sending Custom IDOC to PI 7 and PI 7 is sending that to receiver system.
The custom IDOC sometimes contains more than 250 segments and receiver system is not able to process IDOC's with more than 250 segments. Receiver system is having this limitation.
QNS :
(1) What are options to restrict IDOC's creation to 250 segments in SAP
OR
(2) Can it be taken care at SAP PI 7.0 end. Like 1 doc is coming to PI with more than 250 segments and Can PI break this into multiple idoc's of max 250 segment length so that no data loss is there.
Your suggestions are needed for both options.
Thanks in advance..

Try out this mapping-
You need use 1:n mapping by making the occurance of target MT to unbounded.
Idoc -> Index(context,increment1)-> Division by n(250)->floor->SplitByValue->collapseContext->TargetMT
Segment ->Index(context,increment1)-> Division by n(250)->floor->SplitByValue->Target Segment
Iam not sure on how to build this logic in SAP.But the effective way is to implement this restriction in SAP before IDoc reaching PI.

Receiving multiple IDocs

Similar Messages

Maybe you are looking for