e*Xchange message parse for RosettaNet (Doc ID 1025132.1)

Last updated on OCTOBER 18, 2006

Applies to:

Sun B2B - Version: 5.0.5 and later
Information in this document applies to any platform.

Symptoms

When RosettaNet messages are passed, eX_ePM may fail to load TP Profile and throw errors if the following version identifiers are not defined according to RosettaNet standards:

Global Business Action/Signal Version Identifier
PIP Version Identifier

If V02.00 is provided in the profile then there will be no problem. But if 2.0 is provided for the above identifiers then the following error will be thrown by eX_ePM


12:26:29.276 MNK I 4844 (monklog:406): eX-RSO20-Inb-main: failed before forwarding msg to internal.
12:26:29.276 MNK I 4844 (monklog:406): UX_X_init_ts: invalid transact_info
12:26:29.292 MNK I 4844 (monklog:406): eX-ROS20-Inb-main: processing error
12:26:29.308 MNK I 4844 (monklog:391): eX-ROS20-Handle-Inbound-Error: message received by ePM is not expected according
12:26:29.308 MNK I 4844 (monklog:391): to DB profile. unique_id= <654292358|3A4|PIDBC-szxrn01-ts11552871214640001125|R
12:26:29.308 MNK I 4844 (monklog:406): equest Purchase Order|Purchase Order Request Action>
12:26:29.323 MNK I 4844 (monklog:391): eX-ROS20-Handle-Inbound-Error: error_data=<6110^ux-init-trans() failed: <UX_X_in
12:26:29.339 MNK I 4844 (monklog:406): it_ts: invalid transact_info>~6032^Unexpected message>
12:26:29.339 MNK I 4844 (monklog:406): eX-ROS20-Handle-Inbound-Error: save data at IC level.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms