Invalid Sender and Receiver Id msg shown in activity log

21

Venkidi,

It was definitely the GS routing mode. When I tried your setting, I saw the same behavior.

As Rob suggested, in your situation it needs to be set to off.
I would also follow his advice to leave the default EDITPA enabled.

By the way, the GS06 and GE02 segments in the sample doc you sent have leading zeros. This violates the X12 spec, so if anyone in the loop actually validates for compliance, it will fail.

Regards,
-Mark

22

Hi Mark and Rob,

I did the changes suggested by Rob. Its now working fine.

Before I close this thread, I have some more doubts:

  1. Does the default TPA gets created automatically.
  2. What is the order of processing in the TPA.(My first entry in the TPA is the Unknown- will it match one by in the order it appears in TPA)
  3. Why did it work when the default TPA’s setting was turned off(GS routing) even though it was disabled.

Regs,
Venkidi.

23

Venkidi,

The default TPA is indeed created automatically on install.

I think webMethods expects no duplicates for any specific combination of sender and receiver in a TPA, so order of processing should not be an issue. TPAs are not like processing rules in that regard. Since (as you said from the start) you had a TPA that corresponded to valid partner ids, only the custom TPA should take effect.

When I tested it, leaving the default TPA disabled did not prevent things from working correctly using my custom TPA. ( At least apparently ). So that would explain why the GS routing setting for the default TPA had no effect.

Nevertheless I agree with Rob that if the docs say you shouln’t disable the default TPA, it would be wise to conform.

Regards
-Mark

24

Hi Mark and Rob,

When i test by disabling the default TPA i get the done w/errors.

One more doubt if the WM expects the sender and receiver in TPA why the error occurs when i disable the default TPA.

Moreover if there is no match in TPA what happens.

Regs,
Venkidi.

25

That is not what happened for me once GS Routing was set properly in the custom TPA. Maybe Rob can explain that.

The default TPA (with sender and receiver as unknown) is what would be used if there is no match.

26

“…when i add the interchange info in administration server.”

I had misread that when I had first responded. I thought you meant in the TN Console. Sorry.

Are you using non-standard processing? Do you need to? I ask because if you don’t need to use non-standard processing then you can remove all the config you put into the EDI config in Administrator. If that config is still set up, it may be playing a factor here.

27

Hi Rob,

I am not using the non-standard processing any more. As per ur comments in previous mails i had enabled the default TPA and set the GSrouting to off.Then it was working. Actually my doubt how will the default TPA come into picture when i have defined a TPA for my sender and receiver with the same properties of default TPA.

Regs,
venkidi.

28

The default EDITPA is used when values are not set in the partner-specific EDITPA. So if you leave a field unset in the partner-specific EDITPA, it will use the value from the default.