cancel
Showing results for 
Search instead for 
Did you mean: 

How to Create a single EDI files:-from multiple IDOCs-Best practise/method?

Former Member
0 Kudos

Hi ALL

We would like to create a single EDI file from multiple IDOCs....

Can you please, let us know the best possible way to achieve this....

1.Would be by using BPM and collect all IDOCs (particular count 3 or 5)

2.Request ECC to send us an xml which contains 3 or 5 IDOCs in one XML and we have message mapping which has this xml as source structure and map to EDI structure....to generate a single EDI with multiple records.

3.Is there any other option apart from (1) or (2).

The result needed is package data from multiple IDOC in to a single EDI file.....

Please, help us with your best practice suggestions...

Thank you,

Patrick

Accepted Solutions (1)

Accepted Solutions (1)

former_member556412
Active Participant
0 Kudos

hi,

Option 2 is suggested.

regards,

bhanu.

Former Member
0 Kudos

Hi! ALL

Going forward with the option (2) in the above post ..that is...

"Request ECC to send us an xml which contains 3 or 5 IDOC's in one XML

and we have message mapping which has this xml as source structure and

map to EDI structure....to generate a single EDI with multiple records"

We have question with regard to determining the receiver:

The control segment of the IDOC would have the vendor name 
to which these bundled IDOC's belong to.How can we set up our 
configuration scenario to route these IDOC's desired receiver determination. 
As we have about 45 vendors to route these IDOC's as EDI.

So, to summarize here is the scenario:

The .xml file is created with 3 or 5 IDOC's bundled/packaged in it,

PI file adapter picks up the file....but, how would it determine the

correct receiver determination to route it to the corresponding

configuration of the vendor as EDI.

If they were only a small no. of vendors we could have created corresponding

directory folders for each vendor IDOC xml ( and have File adapter for each vendor folder).....as

we have 45 vendors, we need to come up with a more efficient way to

determine the receiver of this IDOC.

Please, let us know your best approach

Thank you,

Patrick.

Edited by: Patrick Jones on Feb 6, 2009 4:10 PM

Edited by: Patrick Jones on Feb 6, 2009 4:12 PM

Edited by: Patrick Jones on Feb 6, 2009 4:13 PM

Satyagadadas
Active Participant
0 Kudos

Hi,

if you consider performance then option 2 is preferable, but the ECC job should be a batch job.

For different vednors you should use content based routing for each reaciver as your target host details are different for each vendor.

Let us know if you have any more concerns.

Thanks,

Answers (3)

Answers (3)

Former Member
0 Kudos

We have the same problem (need to create one file with multiple EDI messages). Let me warn you about that option 2:

We also went for option 2, but now have the problem that we have massive context problems in the mapping, and a very hard time finding out the reason, because the partner requests us to collect all invoices of one day, which are about 100. I managed to configure that in we20, and use XML-HTTP channel to XI (because Idoc collection does not work in the XI 3.0 IDoc adapter). But that XML-file needs so much RAM that you cannot load it into the XI mapping designer tool.

=> for 3-5 messages, collection is ok, but not for 100. If in one of those 100 messages there is a problem, good luck for debugging.

In the meantime, I am strongly thinking about processing every message individually, save the BIC EDI result in a file, and then once daily merging those EDI files with custom code. Has the advantage that you can monitor problems per message.

I think integration process would create only one BIC module call for all collected messages, which again could make monitoring problems for large amount of messages.

about your vendor problem, you can create those vendors as partners in your SAP we20

CSY

former_member750652
Contributor
0 Kudos

Hi Patrick,

Inaddition to the above suggestions i would like to give little information on EDI mapping.Normally thsi kind of IDOC to EDI mapping is done in SEEBURGER BICmapping designer as BICMD files and alter used in XI .So far BIC has got option only for mapping between single IDOC to EDI probably this is the reason why we are suggested to have the XML for the multiple IDOCs rather than going for BPMs.

Thanks,

Ram.

0 Kudos

Option 2 is recommended by SAP.