We have multiple inbound scenarios, all using the same business system in the configuration. Within a scenario, the inbound EDI file sender and receiver identifiers may vary, thus the use of '*' in the separator channel. The design behind the multiple '997' channels is so each interface scenario can have it's own integrated configuration for the outbound 997 acknowledgement. This way the files should flow to the correct archive folder, and be placed in the correct location back on the DMZ server, to be sent back to the originator.
Recently, we saw this issue happen: - a new inbound interface was constructed for the actual '997' transaction set. This scenario had only 2 integrated configurations. The first int. config. had a separator receiver that said 'no ack required'. However, because we have multiple separator senders for 997 with the '*', PI actually ignored the 'no ack required', and instead of processing the 997 as an inbound interface, it turned around and sent a 997 file back out. So we have quite a problem it appears.