Académique Documents
Professionnel Documents
Culture Documents
Code Short Description Detailed Error Message Meaning How to Remedy Problem Responsible Party
Example(s)
1 Unidentified token No example Trillium rejected the Marketing - (Leads and Incomplete Orders) Mktg (Leads)
name/address pattern. 1. Mktg will daily examine the records and correct any Order
Trillium did not fully obvious problems or reject any obviously bad records. Mgmt (Orders)
understand what it was
2. At the end of each week Mktg will print out all the Req. check first then
examining
Attn records that reside in Error status' 1 to 20 using the IG Trillium
Admin Report. administrator
3. Mktg will give this report to a Call Center Admin
2 Mixed name forms No example Trillium rejected the 4. The Call Center will attempt to contact the people on Mktg (Leads)
name/address pattern. the list and return the list with records with one of the Order
Trillium believes personal following results: Mgmt (Orders)
and business names are
a. Could not contact check first then
combined
b. Corrections to address provided Trillium
c. Address confirmed as correct administrator
3 Hold mail No example Trillium rejected the 5. Mktg will then address each of the records according to Mktg (Leads)
name/address pattern. the results: Order
Trillium believes the mailing a. Reject Record Mgmt (Orders)
address is on hold b. Correct address and reprocess check first then
c. Give to Trillium administrator to adjust the Trillium Trillium
configuration administrator
4 Foreign address No example Trillium rejected the Order Management (Web Orders) Mktg (Leads)
name/address pattern. 1. Order Management will daily examine the records and Order
Trillium believes the address correct any obvious problems, check the address via a Mgmt (Orders)
is not in the United States directory service or contact the customer to confirm or check first then
correct the address. Trillium
2. If the address is confirmed as correct the information is administrator
sent to the Trillium administrator to adjust the Trillium
configuration
5 No names An error occurred while Trillium rejected the 3. If the address will not process in time (address Mktg
Order(Leads)
specified standardizing the record name/address pattern. correction does not work or Trillium reconfiguration takes Mgmt (Orders)
Trillium did not see a name. too long) Order Management can discard the record in IG check first then
and re-create the customer manually in IP (if necessary) Trillium
and then re-create the order manually in OM administrator
NOTE: A manual re-creation of a web order in OM may
require price overwrites if the Web pricing differs from JDE.
Code Short Description Detailed Error Message Meaning How to Remedy Problem Responsible Party
Example(s)
6 No street identified An error occurred while Trillium rejected the Marketing - (Leads and Incomplete Orders) Mktg (Leads)
standardizing the record name/address pattern. 1. Mktg will daily examine the records and correct any Order
Trillium did not see a street obvious problems or reject any obviously bad records. Mgmt (Orders)
name 2. At the end of each week Mktg will print out all the Req. check first then
Attn records that reside in Error status' 1 to 20 using the IG Trillium
Admin Report. administrator
3. Mktg will give this report to a Call Center Admin
7 No Geography No example Trillium rejected the 4. The Call Center will attempt to contact the people on Mktg (Leads)
identified name/address pattern. the list and return the list with records with one of the Order
Trillium did not see following results: Mgmt (Orders)
city/state/postal code a. Could not contact check first then
information Trillium
b. Corrections to address provided
c. Address confirmed as correct administrator
8 Unknown name An error occurred while Trillium rejected the 5. Mktg will then address each of the records according to Mktg (Leads)
pattern standardizing the record name/address pattern. the results: Order
Trillium did not recognize a. Reject Record Mgmt (Orders)
the form of the name
b. Correct address and reprocess check first then
c. Give to Trillium administrator to adjust the Trillium Trillium
configuration administrator
9 Derived genders No example Trillium rejected the Order Management (Web Orders) Mktg (Leads)
conflict name/address pattern. 1. Order Management will daily examine the records and Order
Trillium saw evidence of correct any obvious problems, check the address via a Mgmt (Orders)
both male and female directory service or contact the customer to confirm or check first then
names/titles correct the address. Trillium
2. If the address is confirmed as correct the information is administrator
sent to the Trillium administrator to adjust the Trillium
configuration
10 Multiple middle No example Trillium rejected the 3. If the address will not process in time (address Mktg (Leads)
names name/address pattern. correction does not work or Trillium reconfiguration takes Order
More then one middle name too long) Order Management can discard the record in IG Mgmt (Orders)
was specified and re-create the customer manually in IP (if necessary) check first then
and then re-create the order manually in OM
Trillium
NOTE: A manual re-creation of a web order in OM may administrator
require price overwrites if the Web pricing differs from JDE.
Code Short Description Detailed Error Message Meaning How to Remedy Problem Responsible Party
Example(s)
11 Unknown street An error occurred while Trillium rejected the Marketing - (Leads and Incomplete Orders) Mktg (Leads)
pattern standardizing the record name/address pattern. The 1. Mktg will daily examine the records and correct any Order
format of the street was not
obvious problems or reject any obviously bad records. Mgmt (Orders)
recognized. 2. At the end of each week Mktg will print out all the Req. check first then
Attn records that reside in Error status' 1 to 20 using the IG Trillium
Admin Report. administrator
3. Mktg will give this report to a Call Center Admin
12 Invalid directional No example Trillium rejected the 4. The Call Center will attempt to contact the people on Mktg (Leads)
name/address pattern. The the list and return the list with records with one of the Order
street directions were not following results: Mgmt (Orders)
recognized. a. Could not contact check first then
b. Corrections to address provided Trillium
c. Address confirmed as correct administrator
13 Unusual or long No example Trillium rejected the 5. Mktg will then address each of the records according to Mktg (Leads)
address name/address pattern. The the results: Order
address was too long or in a. Reject Record Mgmt (Orders)
an unrecognized format.
b. Correct address and reprocess check first then
c. Give to Trillium administrator to adjust the Trillium Trillium
configuration administrator
14 No city or country No example Trillium rejected the Order Management (Web Orders) Mktg (Leads)
found name/address pattern. No 1. Order Management will daily examine the records and Order
city or country was found. correct any obvious problems, check the address via a Mgmt (Orders)
directory service or contact the customer to confirm or check first then
correct the address. Trillium
2. If the address is confirmed as correct the information is administrator
sent to the Trillium administrator to adjust the Trillium
configuration
15 Geography too No example Trillium rejected the 3. If the address will not process in time (address Mktg (Leads)
long name/address pattern. The correction does not work or Trillium reconfiguration takes Order
city/state/postal code too long) Order Management can discard the record in IG Mgmt (Orders)
information was too long. and re-create the customer manually in IP (if necessary) check first then
and then re-create the order manually in OM Trillium
NOTE: A manual re-creation of a web order in OM may administrator
require price overwrites if the Web pricing differs from JDE.
Code Short Description Detailed Error Message Meaning How to Remedy Problem Responsible Party
Example(s)
16 Corrected city No example Trillium rejected the Marketing - (Leads and Incomplete Orders) Mktg (Leads)
name too long name/address pattern. The 1. Mktg will daily examine the records and correct any Order
city name was too long, obvious problems or reject any obviously bad records. Mgmt (Orders)
even after being 2. At the end of each week Mktg will print out all the Req. check first then
standardized Attn records that reside in Error status' 1 to 20 using the IG Trillium
Admin Report. administrator
3. Mktg will give this report to a Call Center Admin
17 Conflicting No example Trillium rejected the 4. The Call Center will attempt to contact the people on Mktg (Leads)
geography types name/address pattern. The the list and return the list with records with one of the Order
city/state/postal following results:
a. Could not contact Mgmt (Orders)
code/country information is b. Corrections to address provided check first then
in conflict Trillium
c. Address confirmed as correct
administrator
18 Unable to verify No example Trillium rejected the 5. Mktg will then address each of the records according to Mktg (Leads)
city names name/address pattern. the results: Order
Trillium does not believe the a. Reject Record Mgmt (Orders)
city name specified exists. b. Correct address and reprocess check first then
c. Give to Trillium administrator to adjust the Trillium Trillium
configuration administrator
19 Unidentified line No example Trillium rejected the Order Management (Web Orders) Mktg (Leads)
name/address pattern. One 1. Order Management will daily examine the records and Order
ore more lines of data were correct any obvious problems, check the address via a Mgmt (Orders)
not recognized as name or directory service or contact the customer to confirm or check first then
address data. correct the address. Trillium
2. If the address is confirmed as correct the information is administrator
sent to the Trillium administrator to adjust the Trillium
configuration
20 Multiple street Record contains Trillium rejected the 3. If the address will not process in time (address Mktg (Leads)
names type unacceptable content name/address pattern. correction does not work or Trillium reconfiguration takes Order
More then one street too long) Order Management can discard the record in IG Mgmt (Orders)
address was found. and re-create the customer manually in IP (if necessary) check first then
and then re-create the order manually in OM Trillium
NOTE: A manual re-creation of a web order in OM may administrator
require price overwrites if the Web pricing differs from JDE.
Code Short Detailed Error Message Example(s) Meaning How to Remedy Problem Responsible
Description Party
9001 Web interface Unexpected exception attempted to During staging, communication 1. Try reprocessing the record in the I.T.
error invoke action <DFXIMEDIATRACKING> with the web imports database Admin UI.
encountered a problem
9003 File parsing No example During staging, the data in the file 1. Investigate the problem based on I.T.
error being staged did not parse the group (e.g. possible bad West file,
properly bad Convergys file, bad NCOA file, bad
Do Not Email file, or error from e-
commerce processing).
2. Restart the group in the Admin UI if
the problem has been corrected.
9004 File format error Expected row width [400] but found [401] During staging, the data in the file 1. Investigate the problem based on I.T.
on row [1] being staged did not match the the group (e.g. possible bad West file,
expected format. bad Convergys file, bad NCOA file, bad
Do Not Email file, or error from e-
commerce processing).
2. Restart the group in the Admin UI if
the problem has been corrected.
9005 No records No Message No records were found in a file 1. Try reprocessing the record in the I.T.
found in file during staging Admin UI.
9007 Internal import Unable to retrieve group/section An unanticipated error occurred 1. Try reprocessing the record in the I.T.
server error <Dig/staging> during importing Admin UI.
Code Short Detailed Error Message Example(s) Meaning How to Remedy Problem Responsible
Description Party
9008 Size of File Size of file <0927mkk.txt> changed after Indicated a file being staged was 1. If a West, Convergys, NCOA, or Do I.T.
Change staging. Before: <664286>, after: actively being modified during the Not Email file, try reprocessing the
<828120> staging process group.
9009 File IO Error No Example During staging, a file I/O condition 1. If a West, Convergys, NCOA, or Do I.T.
was encountered Not Email file, try reprocessing the
group.
9100 Too many Too many errors in a row: (last one: Reply 15 consecutive errors were 1. Investigate the problem based on I.T.
consecutive to message action <InsertCustomer> encountered in a group. Importing the group (e.g. possible bad West file,
import errors contained status <Failure> and status of the group is halted. bad Convergys file, bad NCOA file, bad
message <> Do Not Email file, or error from e-
commerce processing).
2. Restart the group in the Admin UI if
the problem has been corrected.
9101 Trillium Error Reply to message action Interaction with the Trillium data 1. Try reprocessing the record in the I.T.
<StandardizedAddress> contained status cleansing system failed Admin UI
<Failure> and status message <Address unexpected:
1. Trillium is not available, or 2. Inform a possible problem to the
failed to standardize>. Import Gateway and CRM teams for
2. When performing a Trillium
App Error Code, Desc: <,> Sys Error investigation
action a failure or error was
Code,Desc: <1000,StandardizeAddress reported, or
Service. No connection could be made 3. A logical problem occurred
because the target machine actively preventing continuation of this
refused it phase of processing, or
4. A code exception occurred in
Import Gateway.
Interaction with the E.piphany IP
9102 Epiphany IP Reply to message contained
<InsertCustomer> action status (CRM) system failed unexpectedly 1. Try reprocessing the record in the I.T.
Integration Error <Failure> and status message <>. 1. CRM was not available, or Admin UI
2. Inform a possible problem to the
Invalid data - a household XML was 2. When Performing a CRM action Import Gateway and CRM teams for
expected and was not returned. a failure or error was reported, or investigation
3. A logical problem occurred
Exception thrown while attempting to preventing continuation of this
send message phase of processing, or
4. A code exception occurred in
Import Gateway.
Code Short Detailed Error Message Example(s) Meaning How to Remedy Problem Responsible
Description Party
9103 Media Tracking Reply to message contained failure Interaction with the Media 1. Try reprocessing the record in the I.T.
Integration Error status. (action: <DFXIMEDIATRACKING> Tracking (MT) system failed Admin UI
status: <failure> status message: unexpectedly: 2. Inform a possible problem to the
<Record Not Found> 1. MT was not available, or Import Gateway and CRM teams for
2. When performing a MT action a investigation
Exception thrown while attempting to failure or error was reported, or
send message 3. A logical problem occurred
preventing continuation of this
phase of processing, or
4. A code exception occurred in
Import Gateway
9104 Order Unable to override kit price <SKU: Interaction with the Order 1. Try reprocessing the record in the Order
Management 458036> - OM response did not contain Management (OM) system failed Admin UI Management
Integration Error any KitDiscountable order lines (action: unexpectedly: 2. Inform a possible problem to the I.T.
<AddItems>) 1. OM was not available, or Import Gateway and CRM teams for
2. When performing a OM action investigation
App Error Code, Desc: a failure or error was reported, or
<UNKNOWN,Invalid Kit Configuration; no 3. A logical problem occurred
components detected for kit preventing continuation of this
phase of processing, or
investigation
Code Short Detailed Error Message Example(s) Meaning How to Remedy Problem Responsible
Description Party
9207 Insufficient The Birthdate date format is invalid: <11- The lead contained one or more 1. Correct the record in the Admin UI Marketing
Lead Info 11-1111> fields that were blank or in the and mark the record for reprocessing examines and
No First Name wrong format IT Fixes
No Postal Code
The required region is empty. (Category:
<4> SubCategory: <9207> During <3>)
9208 No Inquiry Date No example The lead did not contain an inquiry 1. Correct the record in the Admin UI Marketing
date and mark the record for reprocessing examines and
IT Fixes
9209 Invalid Lead No example A lead was not of an expected 1. Report a possible problem to the Marketing
Type type Import Gateway and E-Commerce examines and
teams for investigations. IT Fixes
9210 Insufficient No example The NCOA record contained one 1. Correct the record in the Admin UI Marketing
NCOA Info or more fields that were blank or and mark the record for reprocessing examines and
in the wrong format IT Fixes
9211 Insufficient No City The order contained one or more 1. Correct the record in the Admin UI Order
Order Info fields that were blank or in the and mark the record for reprocessing Management
wrong format examines and
IT Fixes
9212 Insufficient No example The Do Not Email record 1. Correct the record in the Admin UI Marketing
Email Info contained one or more fields that and mark the record for reprocessing examines and
were blank or in the wrong format IT Fixes
9213 Invalid Data No valid CRM translation available for The record contained one or more 1. Correct the record in the Admin UI Marketing
Form element: MLR fields that were blank or in the and mark the record for reprocessing examines and
wrong format IT Fixes
The Birthdate date format is invalid: <11-
11-1111>
No valid value found for <04> (Category:
<4> SubCategory: <9213> During: <3>)
No valid value found for <Oregon>
(Category: <4> SubCategory: <9213>
During: <3>)