EDI Ack - wrong 997 Separator channel selected by PI
With our inbound EDI interfaces using the B2B add-on, we are seeing this issue of the wrong separator sender comm channel being selected for the '997' acknowledgement. Even though we have eliminated the wild card * entry where possible, there is still more than one channel with the same select criteria for 997. For example, more than one 997 separator sender channel configured like this one:
When the separator receiver splits the inbound message, and PI searches for the 997 separator sender using the fields shown above, it finds more than one channel, and may not select the channel defined in the integrated configuration. Even if there is another channel configured like this one, but with a sender ID, and it still defaults the one above first. So when the correct 997 sender channel doesn't get identified, processing doesn't flow through the desired integrated configuration, receivers or receiver comm channels.
More information that might be helpful - We have developed more than one EDI inbound interface per transaction set. The reason for multiple interfaces is to meet business requirements for mapping, file archiving, and timing. Our installation is PI 7.31 single stack. We use the SFTP adapter to transmit files between our VAN and PI through a DMZ server. Our interface configuration uses a business system as the communication component, and we use the X12 converter module with ANSI X12.
I would greatly appreciate any thoughts on how to correct the 997 ack processing. I did search the forums, but just found basic how to on setting up a 997 ack.
I opened an incident with SAP on this. Their reply was that the EDI separator sender channel will use the criteria in the channel for selection, and that is the only criteria it will use.
So it appears that if you have more than 1 separator sender channel per EDI transaction set you must differentiate completely using qualifier and/or sender / receiver id. There is no other way to control which channel PI will select.