Problem with same idoc for multiple requirements??

[Former Member]

Hi Ladies and Gentlemen,

I have a requirement to create 2 outbound interfaces (Pick Confirmation and ASN Receipt confirmation) using Idocs. The interfaces will go to the same partner. It appears that Idoc DELVRY03 for message type SHPCON is suitable for both of them. Can we use the same idoc type for multiple interfaces? If so, how does the customer differentiate between a pick confirmation idoc and an ASN receipt idoc if we use the same Idoc and Message type for both, given the data will be similar in both idocs?

Cheers,

Steve

[Former Member]

Hi Steve,

In this case there must be a field telling the category of confirmation. Seeing this field only it can be distinguished between these two confirmationss.

Reward points if useful,

aleem.

[varma_narayana]

Hi Stephen..

Note: We cannot add the Same message type between the Same Partners in the Distribution model - BD64.

I can think of a solution which may help u ...

1. Create a Segment with Two fields (single Char). - WE31

Pick Confirmation Receipt Indicator and

ASN Confirmation Receipt Indicator .

2. Create an IDOC Extension by Adding this Segment to the Root Segment

of IDOC type DELVRY03. - WE30

3. Create 2 Reduced Message types - BD53

For the message type SHPCON.

In 1 reduced message type (Eg: ZPCIK_SHPCON)

Deselect the Field ASN Confirmation Receipt Indicator

In 1 reduced message type (Eg: ZASN_SHPCON)

Deselect the Field Pick Confirmation Receipt Indicator

4. In the Distribution model and Partner profiles Create the Entries for these message types instead of SHPCON.

5. In the Inbound FM of IDOC you need to implement the Enhancement Logic to Determine the Message type and the Indicator value to Process the IDOC.

Let me know how do u find this.....?

<b>Reward if Helpful</b>