IDOC packaging

[Former Member]

Hi,

I have a requirement in which i have to collect MBGMCR IDOCs based on the BOL number and send them out as a packet.

I know that we can package multiple IDOCS by maintaining a packet size in WE20 and then using the RSEOUT00 program to send it out.

But here i wouldnt know how many IDOCS will have to be packed together until runtime. The BOL field has to be matched up to check whether they are related to each other. Any thoughts on how to do this?

[Former Member]

So I suspect you're using IDoc type MBGMCR01, which basically can only hold data for a single material document. Therefore the standard inbound processing cannot be done in packages.

Now for the outbound sending, as far as I know you don't have the possibility to create IDoc packages based on IDoc content in R/3 or ECC. I'm not sure I understand why you'd want to do that, because you'd still end up with individual IDocs (instead of one IDoc per bill of lading, which I'd call a real grouping), they are just transferred within the same RFC call to another system (assuming you use a RFC type connection).

If you'd still want to go ahead and send them out as IDoc packages, I think you'd have to create your own program. This also means that you'd have select the option Collect IDocs in the partner profile and then schedule or somehow trigger your custom program.

Depending on the port type you're using, you'd have to use the right function module for sending. E.g. an R/3-type outbound port would mean you can utilize IDOCS_OUTPUT_TO_R3 and pass it the bunch of IDocs you want to send.

Cheers, harald

[Former Member]

Hi Herald,

Let me give you the reason i want to package.

Ok here is my complete scenario.

An MBGMCR IDoc, that i have configured in the outbound mode will be triggered when we post an material document.

Now here in our company we have the concept of blanket PO, where 1 PO may generate multiple partial POs. So the materials are received based on these partial POs.

Now we have to send the MBGMCR Idocs to a client of ours who pay out our frieght vendors based on the MBGMCR IDoc.

And in their system they cant handle partial POs. If they get 2 MBGMCR IDocs with the same PO number its will bomb in their system.

So i have to collect all the MBGMCR IDocs pertaining to a single PO based on the BOL and send it across together.

Any more Ideas as to how i can handle this kind of scenario?

[Former Member]

Sorry, I don't fully understand your process. You're mentioning a blanket PO, but say that there's multiple partial PO's being generated. This sounds as if you should have unique numbers (as opposed to having using just the blanket PO for several items until the value limit is reached).

Anyhow, apart from that I'm wondering what your freight vendor, who receives the MBGMCR messages, uses the PO number for. If you just need a reference to link up freight costs and PO, maybe you should change the frame of reference and use the material document number instead (i.e. fill the field that contains now the PO with the material document number). Of course that's not possible if your vendor has a reference to your PO and needs that number. Or, if they need the PO number maybe you could add the material number as a postfix (or something else to make it unique, e.g. <EBELN>'-'<MBLNR>).

In the end though it sounds like you're looking on packaging on content level, not packaging of several IDocs and sending them as a packet. Because if I understand your explanation right, the IDocs would still fail as long as they're separate IDocs. So if my above suggestions don't work, it seems as if you'd have to combine your IDocs into one per PO number (which also sounds odd, because if you're sending material documents, you'd have to fiddle with the contents of the MBGMCR01 IDoc anyhow and make up a combined document number for the material document and then fix item numbers?!).

Not sure if my comments are of any help, but can't really say much, because the process and requirements are unclear to me...