Skip to Content
0

Trading Partner Management parameters not considered at run-time to pick required ICO

Mar 20, 2017 at 03:48 PM

116

avatar image
Former Member

Dear Gurus,

We have multiple partners exchanging messages via PI and we are using B2B Add ons for the same.

We have configured one Generic EDI Separator Receiver channel, which receives all the incoming EDI files, splits wherever necessary. As we know, after receiving and splitting the files, it would search for EDI Separator sender channel(s).

We are trying to configure a single EDI Separator Sender channel, which in conjunction with Trading partner management should be able to route all the messages coming from EDI Separator Receiver channel. So we are putting .* for Transaction Set Identifier code, Interchange Sender ID, Interchange Sender ID Qualifier, Interchange Receiver ID, Interchange Receiver ID Qualifier.

We have configured different Trading Partner Agreements also.

The EDI Separator Receiver channel splits the file and immediately searches for the corresponding EDI Separator Sender channel. The TPMContentAccessModule is configured in EDISeparator Sender channel. So, there is no need to keep the checkbox 'Read from Dynamic Headers' checked for the EDI Separator Receiver channel.

The TPMContentAccessModule is reading the incoming files, and based on the Interchange Sender/Receiver ID, finding out the Sender and Receiver party and writing them to message header.

Senders(say AS2)-->EDI Separator Receiver-->EDI Separator Sender (Uses TPM Module to determine partners and other run-time parameters) -->Receivers

We have got different ICO's configured for different sender/receiver combination. But, we observe that, run-time is only taking the communication channel into consideration. As we have only one communication channel which all the ICO's are using. So, the run-time is packing the ICO's randomly instead of pin pointing to the relevant ICO comprising of a particular sender/receiver combination.

So, our question:- Is it really possible to have single EDI Separator Sender channel to handle message coming in different format from different partners(via EDI Separator Receiver)? If yes, then how? SAP claims , it is possible and TPM helps in achieving so.

Thanks,

SS

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Ryan Crosby Mar 20, 2017 at 08:18 PM
0

Hi,

What are you declaring for your sender interfaces in these different ICOs? I don't think there would be any way for the system to determine a proper ICO if you use a dummy interface but may work for explicit interface designations. In our system we have one EDI separator receiver channel used by all flows but we have one sender channel per transaction set and we do the splitting inside one flow for each of those sets. What you are describing I find surprising because a few months ago when I opened a message regarding something for 997 handling the support expert suggested that we should have a specific channel for every scenario. I was under the impression that it could be arranged more generically than what they had suggested so we have kept that but we have not tried on EDI separator sender channel for our system.

Regards,

Ryan Crosby

Show 6 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Hi Ryan,

Thanks for your thought. Irrespective of the interface name provided (Dummy or Specific), the run-time is randomly picking up any ICO, which is attached the dedicated EDI Separator sender communication channel. The behaviour is random.

If we use different channels for separate Transaction Set, everything is working as expected. But, we are struggling to figure out a way to have a single communication channel( Sender EDI Separator).

So, I believe, we have to use different communication channel for different ICO's. But that questions SAP's claim that, in conjunction with Trading Partner Management, we can maintain generic EDI Separator Receiver/Sender. In the TPM agreement, we also tried to specify the Sender Interface name and Namespace (which is not mandatory). It did not solve our problem.

Regards,

0

Have you tried using the single separator sender channels in multiple ICOs but such that there is only one ICO for each unique sending interface and then doing receiver splits? Otherwise have you tried making sure the party for the sender side is linked to the party from the TPM?

Regards,
Ryan Crosby

0
Former Member

Hi Ryan,

Yes, I have one single sender channels, and all the ICO's are using the same. But, the ICO's are configured for different receivers. In my case, there is one sender and multiple receivers.

The TP Agreement is configured correctly as you have asked. The EDI separator receiver channel, after splitting the message is searching for the sender communication channel. Then it finds the single EDI Separator sender communication channel. Then the control is passed to the TPMContentAccess Module, which is figuring out the sending/receiving partners. But before that, the communication channel is already bound to the ICO which is picked randomly.

If I use the TPMContentAccess Module in the AS2 sender channel, I can't see the option working either.

Please advise.

Regards,

Subhendu

0

Hi Subhendu,

Yes, I tried setting up a working example in our system and observed the same type of behavior. I think the best bet is to try something like what we have done but also only have one flow per transaction set. One channel would require interface and receiver splits which would result in some huge flow that could break anytime you deploy updates.

Regards,

Ryan Crosby

0
Former Member

Thanks Ryan for validating our understanding. I am keeping this thread open with a hope that, SAP will throw some light on any alternative approach.

Regards,

Subhendu

1
Former Member

Hi Subhendu,

I am facing the same issue. Did you ever get feedback from SAP on this?

Thanks,

James

0