This appendix lists integration messages, describes why the message occurs, and describes
what you need to do as a result of receiving the message.
You might find these error messages in a TransmissionReport element.
Integration Message
| Heading |
Data |
| Message: |
THE DATE ELEMENT {0} WITH VALUE {1} IS NOT OF FORMAT
YYYYMMDDHHMMSS |
| Occurs When: |
An invalid date format error occurs when the date is not provided in
the format YYYYMMDDHHMMSS. |
| Corrective Action: |
Enter the date using the required format. |
Integration Message
| Heading |
Data |
| Message: |
DATA CONVERSION FAILED FOR THE ELEMENT {0} WITH VALUE {1} |
| Occurs When: |
A data conversion error occurs when character data cannot be
converted to an internal data type. |
| Corrective Action: |
Eliminate extraneous characters from the data element. |
Integration Message
| Heading |
Data |
| Message: |
THE ELEMENT(S) {0} WITH VALUE(S) {1} IS A DUPLICATE PRIMARY
KEY |
| Occurs When: |
A duplicate Key error occurs when the primary key for a given element
already exists in the GLog database. |
| Corrective Action: |
Change the Transaction Code element from I to IU. |
Integration Message
| Heading |
Data |
| Message: |
THE DATE ELEMENT {0} WITH VALUE {1} IS NOT OF FORMAT
YYYYMMDDHHMMSS |
| Occurs When: |
A PKNotFoundError most often occurs when an attempt is made to update
or delete data that does not exist in the GLog database. |
| Corrective Action: |
If your Transaction Code is U, then use UI instead. If your
Transaction Code is D, then there is no corrective action. |
Integration Message
| Heading |
Data |
| Message: |
THE FOREIGN KEY ELEMENT {0} WITH VALUE {1} COULD NOT BE FOUND IN
TABLE {2} COLUMN {3} |
| Occurs When: |
A FK Not Found Error occurs when a referenced primary key does not
exist in the GLog database. |
| Corrective Action: |
Correct the XML data value such that it refers to a primary key that
does exist in the GLog database. |
Integration Message
| Heading |
Data |
| Message: |
THE REQUIRED ELEMENT {0} IS MISSING |
| Occurs When: |
A missing required element error occurs when a required element has
been omitted from a GLogXMLElement. |
| Corrective Action: |
Provide the missing required element in your XML data. |
Integration Message
| Heading |
Data |
| Message: |
THE I_TRANSACTION_NO WITH VALUE {0} DOESN'T EXIST IN THE
DATABASE |
| Occurs When: |
An ITransactionNoNotFoundError occurs when a GLogXMLElement, such as
a Tender Response, refers to a transaction number that does not exist in
the G-Log I_TRANSACTION table. |
| Corrective Action: |
Refer to an existing transaction number. |
Integration Message
| Heading |
Data |
| Message: |
THE TRANSACTION CODE {0} is not valid. Valid codes are
I,U,D,IU,UI,NP |
| Occurs When: |
An invalid transaction code error occurs when the Transaction Code
element is specified with an invalid value. |
| Corrective Action: |
Specify a valid Transaction Code in your XML data. |
Integration Message
| Heading |
Data |
| Message: |
THE TRANSACTION CODE {0} IS NOT SUPPORTED IN THIS INTERFACE. VALID
CODES ARE {1} |
| Occurs When: |
A transactionCodeNotSupported occurs when the TransactionCode element
is specified with an unsupported value. |
| Corrective Action: |
Correct the XML data to specify a valid TransactionCode. |
Integration Message
| Heading |
Data |
| Message: |
THE ELEMENT {0} AND THE ELEMENT {1} CANNOT BOTH BE SPECIFIED |
| Occurs When: |
A conflicting element error occurs when two elements have been
provided in a G-Log XML Element, when only one out of the two may be
used. |
| Corrective Action: |
Eliminate one of the two conflicting elements in your XML
data. |
Integration Message
| Heading |
Data |
| Message: |
THE NUMBER ELEMENT {0} WITH VALUE {1} IS NOT IN A NUMBER
FORMAT |
| Occurs When: |
An invalid number format error occurs when non-numeric characters are
specified in a numeric element. |
| Corrective Action: |
Eliminate the non-numeric characters in your XML data. |
Integration Message
| Heading |
Data |
| Message: |
WE REQUIRE A {0} ELEMENT WITH VALUE {1} IN THE {2} ELEMENT |
| Occurs When: |
A missing element error occurs when an element with a particular
value is required. |
| Corrective Action: |
Provide the element with the required value as indicated in the error
message. |
Integration Message
| Heading |
Data |
| Message: |
THE BOOLEAN ELEMENT {0} WITH VALUE {1} MUST BE EITHER Y or N |
| Occurs When: |
An invalid Boolean error occurs when a Boolean element is provided
with a value other than Y or N. |
| Corrective Action: |
Provide either Y or N in the indicated Boolean element in your XML
data.Table 20‑14 |
Integration Message
| Heading |
Data |
| Message: |
THE ACTION CODE {0} is not valid. Valid codes are A, D |
| Occurs When: |
An invalid action code error occurs when an action code is specified
with a value other than A or D. |
| Corrective Action: |
Provide either A or D in your XML data. |
Integration Message
| Heading |
Data |
| Message: |
THE ELEMENT {0} WITH VALUE {1} is not valid. Valid codes are
{2} |
| Occurs When: |
An invalidCodeError occurs when a code is specified that is not valid
for that element |
| Corrective Action: |
Correct the XML data to provide a valid value. |
Integration Message
| Heading |
Data |
| Message: |
THE ACTIVITY {0} is not valid. Valid codes are D, P or O |
| Occurs When: |
An invalidActivityError occurs when an activity is specified with a
value other than P, D or O. |
| Corrective Action: |
Correct the XML data to provide anyone of D, P or O. |
Integration Message
| Heading |
Data |
| Message: |
CAUGHT THE FOLLOWING EXCEPTION WHILE PROCESSING TRANSACTION:
{0} |
| Occurs When: |
A transactionProcessorException occurs when the integration layer
validation method has not checked for a given error condition, and the
condition is caught by the underlying database. Most often this error
occurs when an attempt is made to update the Transportation and Global
Trade Management Cloud database so that one or more database referential
integrity constraints are violated. For example, this error occurs if
you attempt to delete a transportation order after one or more releases
have been created. |
| Corrective Action: |
No particular correction can be defined. Analyze the error based on
the requirements of the data in the underlying database. |
Integration Message
| Heading |
Data |
| Message: |
ELEMENT {0} VALUE {1} HAS LENGTH {2} WHICH EXCEEDS THE MAX LENGTH {3}
OF TABLE {4} COLUMN {5} |
| Occurs When: |
The length of an element value exceeds the length of the
corresponding database column |
| Corrective Action: |
Correct the XML data to provide a value which does not exceed the
maximum length. |
Integration Message
| Heading |
Data |
| Message: |
ELEMENT {0} VALUE {1} EXCEEDS THE MAX LENGTH {2} |
| Occurs When: |
The length of an element value exceeds the length of the
corresponding database column |
| Corrective Action: |
Correct the XML data to provide a value which does not exceed the
maximum length. |
Integration Message
| Heading |
Data |
| Message: |
ERROR VALIDATING MAX LENGTH OF ELEMENT {0} VALUE {1} - CHECK TABLE
NAME {2} COLUMN NAME {3} |
| Occurs When: |
The specified table/column information could not be found. |
| Corrective Action: |
Call Support. |
Integration Message
| Heading |
Data |
| Message: |
TRANSACTION NUMBER {0} APPLICATION {1} PRIMARY KEY {2} TRANSACTION
CODE {3} SUCCESSFULLY PROCESSED |
| Occurs When: |
A transaction success informational message occurs when a transaction
has been successfully processed. |
| Corrective Action: |
No action needed. |
Integration Message
| Heading |
Data |
| Message: |
UNABLE TO PROCESS DUE TO MULTIPLE SHIPMENTS MATCHED ON {0} |
| Occurs When: |
A matchMultipleShipment error message occurs when
ShipmentRefnums/EquipmentNumber match different Shipment_GID. This type
of error happens when receiving a TenderResponse or a
ShipmentStatus. |
| Corrective Action: |
Correct the XML data to provide ShipmentRefnum values which
correspond to the same Shipment. |
Integration Message
| Heading |
Data |
| Message: |
WE REQUIRE A {0} ELEMENT WITH A VALUE MATCHING A {1} IN THE {2}
TABLE |
| Occurs When: |
A missingRequiredDataError occurs when an element with a particular
value is missing from the database table. |
| Corrective Action: |
Correct the database data to provide the value as indicated in the
error message. |
Integration Message
| Heading |
Data |
| Message: |
ORDER {0} IS NOT MODIFIABLE AND SO COULD NOT BE MODIFIED OR
DELETED. |
| Occurs When: |
An orderNotModifiable informational message occurs when the status on
an order is not "WKFLW_ORDER_OB_MODIFIABLE". This can occur if an order
is in a state that restricts it from being modified, or an agent is
setup to restrict modification. |
| Corrective Action: |
If you want to be able to modify the order, you may have to change
the state of the order or modify the agent that handles order
modifications. |
Integration Message
| Heading |
Data |
| Message: |
UNABLE TO raiseNewXMLTopicsForRedoTransmissions, STACK TRACE:
{0} |
| Occurs When: |
|
| Corrective Action: |
None. |
Integration Message
| Heading |
Data |
| Message: |
THE SAVED QUERY {0} RETURNS NO DATA |
| Occurs When: |
The saved query in the SShipUnit element did not return any
values. |
| Corrective Action: |
Verify that the integration saved queries are correct and that the
desired ship units exist. |