IDOCs Packaging ? Need some clarification ;-)

[Former Member]

Team,

Simple scenario:

=> JMS (xml) --> ( … XI … ) --> (IDOCs) --> SAP ECC.

This is scenario working fine.

However, If we have 10 IDOC, we have 10 LUW on the backend system (not good for the performance).

To avoid these multiple luw, we are using the IDOC packaging approach (no ccBPM) the wizard (idxpw).

So …

1) XML messages are coming in XI

2) Since we have a filter (sxmsfilter), messages are kept aside for a while

3) Until a job (created using idxpw) wake up and start processing the messages

Our questions:

When does the “packaging” trick arrive ? We do not see the messages in IDXP (with the package icon), but with the yellow dot

thank for you help

MO A+

[Former Member]

Hi XI Team,

Have a look at Sravya's blog

/people/sravya.talanki2/blog/2005/12/09/xiidoc-message-packages

Usually IDOC packaging is created at the sender side as explained in the blog. Have never tried IDOC packaging at receiver end.

In our case, we changed the IDOC XSD to unlimited and used it. It will create a single message in XI.

But in R/3 it is not an IDOC package. It will be a collection of IDOC. Each will trigger a new LUW.

Hope the weblog will give you some idea. If you are able to create an IDOC package at th R/3 do update us. I will give this scenario a try tomo. It is 12:20AM my time

Good Luck

Regards,

Jaishankar

[Former Member]

Hi Jai,

So IDOC packaging is possible only for inbound (sender) scenario ?

Example:

10 IDOCs --- ( XI / get them packaged ) --- 1 IDOC

How about:

1 XML (big) file that has 10 orders --- ( XI / get them packaged) -- 10 IDOCs, but packaged in only 1 LUW ?

I just looked at her (Sravya) blog, this is exactly what i am doing ... but for sending IDOC to my SAP ECC backend (as you mentioned).

In SMQ2, i see a queue name (... XI _SERIALIZED001), is that meant that XI is packaging the IDOC ?

Thanks a lot for your time !

[Former Member]

Team,

I see the following in the (sm37) jog log files:

Message 17E38A188E0D4B303984BCB1C6BF4B81 assigned to package 47C42190C032703BE1000000A573283A

Message 192E7C92C14241CF1206C514F652EF2E assigned to package 47C42190C032703BE1000000A573283A

Message 1C910BFA8E8542CA1F1BCE6188BDF066 assigned to package 47C42190C032703BE1000000A573283A

Message 1CF9DA07DCFC4D5A2B43B5945B6FBD26 assigned to package 47C42190C032703BE1000000A573283A

Message 1F06382867144F290A24C0388FD0EFF1 assigned to package 47C42190C032703BE1000000A573283A

Message 207545099E6443D80F7DA0D66F9C657A assigned to package 47C42190C032703BE1000000A573283A

But ... i do not see the IDOC packages in the IDXP transactions ...

where are they hiding !?!?!

[Former Member]

Hi,

On receiver XSD file of IDOC we change the occurance to unbounded. It creates the multiple segments as per the IDOC packaging concept.

Thus after mapping the IDOC-XMl will be with multiple segments. You will be able to see only one IDOC to be processed as inbound and the all records have packed as segments in it.

Refer

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd...

Thanks

Swarup

[Former Member]

Hi Swarup,

Do you mean that if i want to use idoc packaging (tcode: IDXPW), i must must modify the cardinality on my IDOC (to unbounded) ?

Thank ?