ERROR MESSAGES (ORACLE)

Screen Error Messages

The following error message may appear on the screen when you execute this application:

The application was unable to <perform database action> on tables <table list>.

This error message is usually preceded by a SQL Error dialog box that shows the SQL statement that failed execution. Open a Windows text editor application such as WordPad or Notepad, and switch back to the SQL Error dialog box. Using your mouse, highlight the entire text of the SQL statement that failed execution and press Ctrl-Insert. This copies the text to the Windows Clipboard. Switch back to the text editor, left-click the mouse anywhere in the editing window, and press Shift-Insert. This pastes the SQL text from the Clipboard into the editing window. The text can now be printed and saved for use by Technical Support personnel.

Report Error Messages

There are many error messages that may occur during the validation phase of this process. These messages are listed on the Error Report. The error report lists the following information:

Error File Line — The line number (physical position, no actual line number is assigned) associated with the ASCII error file that may be produced. There may be multiple errors associated with the original input line. However, the line is written to the error file once. You can correct this error file, rename it, and process it separately.
Original Line — The line number (physical position, no actual line number is in the input file) associated with the original ASCII file being processed. There can be multiple errors associated with one original input line.
Item — The Item ID (ITEM_ID) from the input file associated with the error.
Rev — The Item Revision ID (ITEM_RVSN_ID) from the input file associated with the error.
Line Type — The Line Type associated with the error (for example, the ITM line type that populates the ITEM table). Line Type is the first field that appears on each input file line.
Value In Error — The value from the input file that is in error (the displayed value is limited to 15 characters — it can be truncated).
Error Description — Briefly describes why the value (or lack thereof) is in error. Refer to the error message descriptions in this section for additional information and possible remedies.

The less complicated of these errors have been generalized and are documented in General Report Error Messages. The more complicated errors are separated by Line Type and put into separate tables.

General Report Error Messages

The following generalized errors may occur during the validation phase of this process (??? is replaced by the column name that is in error; ?? is replaced by a numeric value that indicates the length or value limit):

Error Message	Additional Info/Remedy
??? is required.	Modify the input file to provide a valid value for the indicated column.
??? is not a valid number.	Modify the input file to provide a valid numeric value for the indicated column.
Length > ??.	Column can contain only ?? characters. Modify the input file to provide a smaller value (less than or equal to the number of characters indicated) for the indicated column.
??? is not a valid date.	Modify the input file to provide a valid date value for the indicated column. The date format is YYYY-MM-DD.
??? (Number) cannot be > ??.	Modify the input file to provide a valid numeric value less than or equal to the amount indicated for the indicated column.
??? (Number) cannot be < ??.	Modify the input file to provide a valid numeric value greater than or equal to the amount indicated for the indicated column.
??? (Number) cannot contain decimals.	The number being uploaded contains a decimal point that is not allowed for this column. Modify the input file to provide a whole number for the indicated column.
??? (Number) cannot be negative.	The number being uploaded contains a minus sign that is not allowed for this column. Modify the input file to provide a positive number for the indicated column.
Invalid ???.	The value being uploaded contains a value that is not allowed for this column. Modify the input file to provide a valid value. This message is usually (if space allows) followed by a list of the acceptable values.
Start Date cannot be > End Date.	The Start Date must fall before the End Date provided. Double check both dates to ensure they comply with this rule.
Item used in PSP. U/M cannot be changed	Required only if MRP Settings > Plan Substitute Part = ‘Y’ and Part has an existing proj. substitute part(s) or used as proj. substitute part
Item used in SPT. U/M cannot be changed	Required only if MRP Settings > Plan Substitute Part = ‘Y’ and Part has an existing substitute part(s) or used as substitute part
PSP rejected, U/M does not match	Required only if MRP Settings > Plan Substitute Part = ‘Y’ Proj substitute part’s U/M is not equal to original part’s U/M
Item used in SPT. U/M cannot be changed	Required only if MRP Settings > Plan Substitute Part = ‘Y’. Part has an existing proj. Substitute part(s) or used as. substitute part
SPT rejected, U/M does not match.	Required only if MRP Settings > Plan Substitute Part = ‘Y’ and Substitute part’s U/M is not equal to original part’s U/M
Line XX is invalid.	Conditions: Invalid line type, invalid delimiter, record do not have valid data and contains only the line type.

Item (ITM) Error Messages

The following table lists the more complicated errors associated with the ITM Line Type.

Error Message	Additional Info/Remedy
Item rejected. Bad PRT and/or IUM.	The ITM record was rejected because a PRT and/or IUM record associated with the ITM record (with the same Item ID/Item Revision ID) contained an error. Because the ITM, PRT, and IUM tables are logically linked, the ITM record could not be uploaded. Correct the associated PRT and/or IUM records.
ITM rejected, duplicate key.	Each ITM record in the input file must have a unique key (Item ID/Item Revision ID). The input file contains multiple ITM records with the same key values indicated on the report. Remove all duplicate ITM records.
Invalid Industry Class Code	Industry Class does not exist in IND_CLASS
Invalid Subcontractor Charge Type	Input file value is not “L”, “E” or “O”
Missing required UDF line	Input file is missing a UDF row for a user-defined field that is deemed Required. That is, if UDEF_LBL row exists with S_TABLE_ID = ‘ITEM’, REQD_FL = ‘Y’ and COMPANY_ID matching login company (only if ITEM_SETTINGS_CORP. ITEMS_BY_COMP_FL = Y)
Inactive item with dependent data.	Input file has ITEM.ACTIVE_FL = N, but the part is currently used in MBOM or EBOM (Assembly, or Component with Comp Type NOT ‘D’eleted), PO line (PO_LN. S_LN_STATUS_TYPE not = C, S or V), Requisition line (RQ_LN. S_RQ_STATUS_CD not = V, C or G), MO (MO_HDR. S_MO_STATUS_CD not = C or L), SO line (SO_LN. S_LN_STATUS_TYPE not = V, C or S), Inventory qty exists (INVT_WHSE_LOC.LOC_QTY > 0).
Invalid NAICS code	Value does not exist in OPP_NAICS_CODES table, or exists with SHOW_LOOKUP_FL = N

Part (PRT) Error Messages

The following table lists the more complicated errors associated with the PRT Line Type.

Error Message	Additional Info/Remedy
Cannot change Ord Policy (Ord To Qty).	You cannot change the Order Policy Type. There is a Part Project (PPJ) line or an existing Part Project record with a non-zero value in the Order To Quantity column. If the Order Policy Type (in the Part table) is O (Order To Point), the Order To Quantity must be zero or greater. To change the Order Policy Type to a value other than O, you must remove the dependency by changing the Order To Quantity to zero.
Cannot change Ord Policy (Reord Pt Qty).	You cannot change the Order Policy Type. There is a Part Project (PPJ) line or an existing Part Project record with a non-zero value in the Reorder Point Quantity column. The Reorder Point Quantity must be greater than zero if the Order Policy Type (in the Part table) is R (Reorder Point). To change the Order Policy Type to a value other than R (Reorder Point), you must remove the dependency by changing the Reorder Point Quantity to zero.
Min Lot Size not allowed (Order Policy).	The Minimum Lot Size Quantity cannot have a value greater than zero unless the Order Policy Type is R (Reorder Point) or M (Min/Mult Lot Size). Change the Minimum Lot Size Quantity to zero, or change the Order Policy Type to R or M.
Min/Mult Lot Size required (Ord Policy).	The Minimum Lot Size Quantity or Multiple Lot Size Quantity must be provided with a value greater than zero because the Order Policy Type is M (Min/Mult Lot Size). Change the Minimum Lot Size Quantity or Multiple Lot Size Quantity to zero (0), or change the Order Policy Type to a value other than M.
Mult Lot Size not allowed (Ord Policy).	The Multiple Lot Size Quantity cannot have a value greater than zero unless the Order Policy Type is M (Min/Mult Lot Size). Change Multiple Lot Size Quantity to zero (0), or change the Order Policy Type to M (Min/Mult Lot Size).
Pd Ord Days is required (Order Policy).	Period Order Days is required when the Order Policy Type is P (Period). You must provide a value greater than zero for Period Order Days or change the Order Policy Type to a value other than P.
Pd Ord Days not allowed (Order Policy).	Period Order Days can be greater than zero if the Order Policy Type is P (Period). You must change Period Order Days to zero (0) or change Order Policy Type to P.
PRT rejected, duplicate key.	Each PRT record in the input file must have a unique key (Part ID/Part Revision ID). The input file contains multiple PRT records with the same key values indicated on the report. Remove all duplicate PRT records.
PRT rejected, no matching Item.	There is a PRT record in the input file without a corresponding ITM record (with the same Item ID/Item Revision ID).
PRT rejected. Bad ITM.	Unless there are additional error messages for this record, it probably contains no errors. It was rejected because it is dependent on an ITM record that was rejected. Correct the errors associated with the ITM record.
Value must be B, P, R, S, T, or L.	Part Type not B (Buy With Components), P (Phantom), R (Reference), S (Standard), T (Tool) or L (MPS Planning-Only)
MPS Planning-Only part s/b Estimating.	Part Type is MPS Planning-Only (PART. S_PART_TYPE = L) and Part Status not Estimating (PART. S_STATUS_TYPE not ‘E’).
MPS Planning-Only part s/b non-inv.	Part Type is MPS Planning-Only (PART. S_PART_TYPE = L) and Part is an inventory part (PART. INVT_FL = ‘Y’).
MPS Planning-Only part s/b MPS planned.	Part Type is MPS Planning-Only (PART. S_PART_TYPE = L) and Planning Type not MPS (PART. S_PLAN_TYPE not ‘S’).
Invalid Ord Policy, Plan Type is not R	Planning Type is not equal to ‘R’eorder and Policy Type ‘Reorder Point’ or ‘Order to point.
Invalid warehouse/location combination.	Default Warehouse ID / Default Inventory Location combination provided does not exist in WHSE_LOC table.
Exceeds maximum of 999999.9999	Minimum Lot Size Qty > 999999.9999
Exceeds maximum of 999999.9999	Minimum Lot Size Qty > 999999.9999
Exceeds maximum of 999999.9999	Minimum Lot Size Qty > 999999.9999
Value must be ‘A’, ‘S’ or ‘N’.	Vendor Restriction by Part Code (Values: A = Approved, S = Assigned, N = No Restriction).
Invalid Industry Class Code	Industry Class does not exist in IND_CLASS
Inv ser/lot track N/A to backflush part.	PART.BKFLSH_FL = Y and either PART.LOT_REQD_FL = Y or PART.SERIAL_REQD_FL = Y.
Invalid Subst Part Planning Order.	Required only if MRP Settings > Plan Substitute Part = ‘Y’ and MRP_SETTINGS. USE_PART_PLAN_FL = ‘Y’. Substitute part’s status is neither of the following: ‘OP’ (Original Part Across Project), ‘OS’ (Original/Substitute Part in Project Demand First), ‘SP’ (Substitute Part Across Project), ‘SO’(Substitute /Original Part in Project Demand First)
Invalid Subcontractor Charge Type	Input file value is not “L”, “E” or “O”
CS Inv Abbrv for Make Part cannot be RM	A raw material inventory type inventory abbrev was entered as common stock invt. Abbrev for a make part
Scrap cannot exceed 0.9999.	Scrap percentage cannot exceed 99.99% (0.9999)
Invalid Part Type for BOM assembly.	Part Status = Estimating, Part Type is NOT MPS Planning-Only. Part/Rev is used as the assembly in a Released or Partially Released MBOM or EBOM.
Invalid Part Status for BOM assembly.	Part Status Type was changed from 'Released' to 'Pre-Released' and Part is used in an Assembly Part in BOM with BOM Status = Released or Partially Released (MBOM or EBOM).
Invalid Part Status for BOM component.	Part Status Type was changed from 'Released' to 'Estimating Only' or 'Pre-Released' and Part is used in an component in a MBOM or EBOM with Component Release flag = Released.
Invalid NAICS code	Value does not exist in OPP_NAICS_CODES table, or exists with SHOW_LOOKUP_FL = N

Item Unit of Measure (IUM) Error Messages

The following table lists the more complicated errors associated with the IUM Line Type.

Error Message	Additional Info/Remedy
IUM rejected, duplicate key.	Each IUM record in the input file must have a unique key (Item ID/Item Revision ID /Unit of Measure Type). The input file contains multiple IUM records with the same key values indicated on the report. Remove all duplicate IUM records.
IUM rejected, no matching Item.	There is an IUM record in the input file without a corresponding ITM record (with the same Item ID/Item Revision ID).
IUM rejected. Bad ITM.	Unless there are additional error messages for this record, it probably contains no errors. It was rejected because it is dependent on an ITM record that was rejected. Correct the errors associated with the ITM record.

Item Unit of Measure Conversion (UMC) Error Messages

The following table lists the more complicated errors associated with the UMC Line Type.

Error Message	Additional Info/Remedy
UMC rejected, duplicate key.	Each UMC record in the input file must have a unique key (Item ID, Item Revision ID, From U/M, and To U/M). The input file contains multiple UMC records with the same key values indicated on the report. Remove all duplicate UMC records.
UMC rejected, no matching Item.	There is a UMC record in the input file without a corresponding ITM record (with the same Item ID/Item Revision ID).
UMC rejected. Bad ITM.	Unless there are additional error messages for this record, it probably contains no errors. It was rejected because it is dependent on an ITM record that was rejected. Correct the errors associated with the ITM record.

Item Vendor (VND) Error Messages

The following table lists the more complicated errors associated with the VND Line Type.

Error Message	Additional Info/Remedy
Already a preferred vendor for Item.	A preferred vendor has already been designated for this Item ID/Item Revision ID. Update the existing Item Vendor record to a preferred status of Y (Yes) or N (No), or change the record you are attempting to upload to a preferred status (PREF_VEND_CD) of Y or N. Only one vendor can have a P (Preferred) status.
Only one (1) preferred vendor per Item.	There is more than one VND record with a preferred vendor flag (PREF_VEND_CD) equal to P for this Item ID/Item Revision ID. Change one of the records you are attempting to upload to a preferred status of Y or N. Only one vendor can have a P (Preferred) status.
VND rejected, duplicate key.	Each VND record in the input file must have a unique key (Item ID/Item Revision ID/Vendor ID). The input file contains multiple VND records with the same key values indicated on the report. Remove all duplicate VND records.
VND rejected, no matching Item.	There is a VND record in the input file without a corresponding ITM record (with the same Item ID/Item Revision ID).
VND rejected. Bad ITM.	Unless there are additional error messages for this record, it probably contains no errors. It was rejected because it is dependent on an ITM record that was rejected. Correct the errors associated with the ITM record.

Item Cost (CST) Error Messages

The following table lists the more complicated errors associated with the CST Line Type.

Error Message	Additional Info/Remedy
CST rejected, duplicate key.	Each CST record in the input file must have a unique key (Item ID/Item Revision ID/Item Cost Type). The input file contains multiple CST records with the same key values indicated on the report. Remove all duplicate CST records.
CST rejected, no matching Item.	There is a CST record in the input file without a corresponding ITM record (with the same Item ID/Item Revision ID).
CST rejected. Bad ITM.	Unless there are additional error messages for this record, it probably contains no errors. It was rejected because it is dependent on an ITM record that was rejected. Correct the errors associated with the ITM record.

Item Project Cost (IPC) Error Messages

The following table lists the more complicated errors associated with the IPC Line Type.

Error Message	Additional Info/Remedy
IPC rejected, duplicate key.	Each IPC record in the input file must have a unique key (Item ID/Item Revision ID/Project ID/Item Cost Type). The input file contains multiple IPC records with the same key values indicated on the report. Remove all duplicate IPC records.
IPC rejected, no matching Item.	There is an IPC record in the input file without a corresponding ITM record (with the same Item ID/Item Revision ID).
IPC rejected. Bad ITM.	Unless there are additional error messages for this record, it probably contains no errors. It was rejected because it is dependent on an ITM record that was rejected. Correct the errors associated with the ITM record.

Item Lead Time (ILT) Error Messages

The following table lists the more complicated errors associated with the ILT Line Type.

Error Message	Additional Info/Remedy
ILT rejected, duplicate key.	Each ILT record in the input file must have a unique key (Item ID/Item Revision ID/Lead Time Type). The input file contains multiple ILT records with the same key values indicated on the report. Remove all duplicate ILT records.
ILT rejected, no matching Item.	There is an ILT record in the input file without a corresponding ITM record (with the same Item ID/Item Revision ID).
ILT rejected. Bad ITM.	Unless there are additional error messages for this record, it probably contains no errors. It was rejected because it is dependent on an ITM record that was rejected. Correct the errors associated with the ITM record.

Item Text (TXT) Error Messages

The following table lists the more complicated errors associated with the TXT Line Type.

Error Message	Additional Info/Remedy
TXT rejected, duplicate key.	Each TXT record in the input file must have a unique key (ITEM_ID/ITEM_RVSN_ID/TEXT_CD/TEXT_CD_RVSN_NO). The input file contains multiple TXT records with the same key values indicated on the report. Remove all duplicate TXT records.
TXT rejected, no matching Item.	There is a TXT record in the input file without a corresponding ITM record (with the same ITEM_ID/ITEM_RVSN_ID/TEXT_CD_RVSN_NO).
TXT rejected. Bad ITM.	Unless there are additional error messages for this record, it probably contains no errors. It was rejected because it is dependent on an ITM record that was rejected. Correct the errors associated with the ITM record.
Text Code/Revision invalid.	TEXT_CD/TEXT_CD_RVSN_NO combination does not exist, or exists but not for login user’s company.
Text Code/Revision invalid.	TEXT_CD/TEXT_CD_RVSN_NO combination is inactive (STD_TEXT.ACTIVE_FL = N).

Item User-Defined (UDF) Error Messages

The following table lists the more complicated errors associated with the UDF Line Type.

Error Message	Additional Info/Remedy
UDF rejected, duplicate key.	Each UDF record in the input file must have a unique key (Item ID/Item Revision ID/User-Defined Label). The input file contains multiple UDF records with the same key values indicated on the report. Remove all duplicate UDF records.
UDF rejected, no matching Item.	There is a UDF record in the input file without a corresponding ITM record (with the same Item ID/Item Revision ID).
UDF rejected, no matching UDEF Label.	No match for the User-Defined ID Label in the input file could be found. This label must be set up on the Manage Item User-Defined Labels screen in Costpoint Product Definition.
UDF rejected. Missing value.	The required data type field was not populated. The data type entered must match the data type specified on the Manage Item User-Defined Labels screen for that label.
UDF rejected. Incorrect value (either from Cases of user-defined field valid values).	The user-defined field value entered is not a valid option for this user-defined label. Check the valid values for this field on the Manage Item User-Defined Labels screen or the appropriate linked table.
UDF rejected. Bad ITM.	Unless there are additional error messages for this record, it probably contains no errors. It was rejected because it is dependent on an ITM record that was rejected. Correct the errors associated with the ITM record.

Alternate Part (APT) Error Messages

The following table lists the more complicated errors associated with the APT Line Type.

Error Message	Additional Info/Remedy
Already a preferred alt part for Item.	1. An existing Alternate Part for this Part ID/Part Revision ID has a Preference Flag equal to Y (Yes). Only one Alternate Part per Part ID / Part Revision ID can be preferred per company. Change existing value from Y to N or change value in input file from Y to N. 2. An existing ALT_PART for this PART_ID/PART_RVSN_ID has a PART_PREF_TYPE=Y. Only one (1) alternate part per item can be preferred if item is shared across all companies. (ITEMS_BY_COMP_FL = 'N' and PART_PREF_TYPE = ‘Y’ and ALT_PART.VEND_ID = 'NULL'). 3. An existing ALT_PART for this PART_ID/PART_RVSN_ID has a PART_PREF_TYPE = ‘Y’. Only one (1) alternate part per item can be preferred if item is shared across all companies. (ITEMS_BY_COMP_FL = 'N' and PART_PREF_TYPE = ‘Y’ and ALT_PART.VEND_ID != 'NULL').
APT rejected, duplicate key.	Each APT record in the input file must have a unique key (Part ID/Part Revision ID/Sequence Number). The input file contains multiple APT records with the same key values indicated on the report. Remove all duplicate APT records.
APT rejected, no matching Item.	There is an APT record in the input file without a corresponding ITM record (with the same Item ID/Item Revision ID).
APT rejected. Bad ITM.	Unless there are additional error messages for this record, it probably contains no errors. It was rejected because it is dependent on an ITM record that was rejected. Correct the errors associated with the ITM record.
Manuf Part ID req'd if Manuf ID entered.	A Manufacturer Part ID must be provided if a Manufacturer ID is provided. Remove the Manufacturer ID value from the input file or provide the Manufacturer Part ID.
Only 1 preferred alt part per Item.	There is more than one APT record for this with the same Item ID / Item Revision ID that has a Preference Flag equal to Y (Yes). Only one Alternate Part per Part ID/Part Revision ID can be preferred. Change one of the input records' Preferred Flag from Y to N.
Vend Part ID req'd if Vend ID entered.	A Vendor Part ID must be provided if a Vendor ID is provided. Remove the Vendor ID value from the input file or provide the Vendor Part ID.
Company mismatch between line and user.	Update to existing line – Input file ALT_PART.COMPANY_ID is Not Null and does not match user’s COMPANY_ID.
Manufacturer ID is required if Manufacturer Part ID is entered.	Manufacturer ID must be provided if Manufacturer Part ID is provided. Modify input file to remove Manufacturer Part ID value or provide the Manufacturer ID.
Vendor ID is required if Vendor Part ID is entered.	Vendor ID must be provided if Vendor Part ID is provided. Modify input file to remove Vendor Part ID value or provide the Vendor ID.

Substitute Part (SPT) Error Messages

The following table lists the more complicated errors associated with the SPT Line Type.

Error Message	Additional Info/Remedy
SPT rejected, invalid Sub Part ID.	The Substitute Part ID/Substitute Part Revision ID must exist in the PART table. Add part to the PART table or use an existing part.
SPT rejected, no matching Item.	There is an SPT record in the input file without a corresponding ITM record (with the same Item ID/Item Revision ID).
SPT rejected. Bad ITM.	Unless there are additional error messages for this record, it probably contains no errors. It was rejected because it is dependent on an ITM record that was rejected. Correct the errors associated with the ITM record.
SPT rejected. Bad substitute part.	The Part ID/Part Revision ID associated with a PRT line was rejected. It cannot be used as a substitute part. Correct bad PRT record or use an existing part.
SPT rejected, invalid status.	The Substitute Part Status is required only if on the Configure Materials Requirements Planning Settings application the Plan Substitute Part flag is Y and the Use Part Plan flag is set to Y. The Substitute Part Status must not be any of the following: U (Use-up/Interchangeable), I (Interchangeable), N (Non-interchangeable), X (Invalid Substitute)
Invalid Subst Part Planning Order.	The Substitute Part Status is required only if on the Configure Materials Requirements Planning Settings application the Plan Substitute Part flag is Y and the Use Part Plan flag is set to Y. The Substitute Part Status must not be any of the following: OP (Original Part Across Project), OS (Original/Substitute Part in Project Demand First), SP (Substitute Part Across Project), SO (Substitute /Original Part in Project Demand First).

Part Project (PPJ) Error Messages

The following table lists the more complicated errors associated with the PPJ Line Type.

Error Message	Additional Info/Remedy
Ord To Qty not allowed (Order Policy).	The Order To Quantity can have a value greater than zero if the associated (Part ID/Part Revision ID) PRT record or the existing associated PART record has an Order Policy Type equal to O (Order To Point).
PPJ rejected, duplicate key.	There is more than one PPJ input line with the same Item ID/Item Revision ID/Project ID. Only one PPJ record is allowed per Item ID/Item Revision ID/Project ID. Remove or correct duplicate record.
PPJ rejected, no matching Item.	There is a PPJ record in the input file without a corresponding ITM record (with the same Item ID/Item Revision ID).
PPJ rejected. Bad ITM.	Unless there are additional error messages for this record, it probably contains no errors. It was rejected because it is dependent on an ITM record that was rejected. Correct the errors associated with the ITM record.
Pref Inv Loc ID req'd if Whse ID entered.	The Preferred Inventory Location ID is required if a Preferred Warehouse ID is provided for a new PPJ record. Provide a Preferred Inventory Location ID or remove the Preferred Warehouse ID from the PPJ line.
Pref Whse ID req'd if Inv Loc ID entered.	The Preferred Warehouse ID is required if a Preferred Inventory Location ID is provided for a new PPJ record. Provide a Preferred Warehouse ID or remove the Preferred Inventory Location ID from the PPJ line.
Reord Pt Qty not allowed (Order Policy).	The Reorder To Quantity can have a value greater than zero if the associated (Part ID/Part Revision ID) PRT record or the existing associated PART record has an Order Policy Type equal to R (Reorder Point).

Project Substitute Part (PSP) Error Messages

The following table lists the more complicated errors associated with the PSP Line Type.

Error Message	Additional Info/Remedy
PSP rejected, invalid Part Project ID.	A Part Project record must exist or a PPJ record must be included in the input file for the Part ID/Part Revision ID / Project ID. Provide a PPJ record.
PSP rejected, invalid Sub Part ID.	No PART record exists for the Part ID/Part Revision ID. Provide a PRT record or use another Part ID/Part Revision ID.
PSP rejected, no matching Item.	There is a PSP record in the input file without a corresponding ITM record (with the same Item ID/Item Revision ID).
PSP rejected. Bad Part Project record.	The PPJ record in input file for the Part ID/Part Revision ID / Project ID was rejected. Correct the PPJ record.
PSP rejected. Bad substitute part.	The PRT record in input file for the Part ID/Part Revision ID was rejected. Correct the PRT record or use another Part ID/Part Revision ID.
Usage Seq No must be unique.	The Usage Sequence Number must be unique for each Part ID/Part Revision ID/Project ID. Provide a unique Usage Sequence Number.
PSP rejected, invalid status.	The Plan Substitute Part Status is required only if on the Configure Materials Requirements Planning Settings application the Plan Substitute Part flag is Y and the Use Part Plan flag is set to Y. The Project Substitute Part Status must not be any of the following: U (Use-up/Interchangeable), I (Interchangeable), N (Non-interchangeable), X (Invalid Substitute)

Item Product (PRD) Error Messages

The following table lists the more complicated errors associated with the PRD Line Type.

Error Message	Additional Info/Remedy
PRD rejected, no matching Item.	There is a PRD record in the input file without a corresponding ITM record (with the same Item ID/Item Revision ID).
PRD rejected. Bad ITM.	Unless there are additional error messages for this record, it probably contains no errors. It was rejected because it is dependent on an ITM record that was rejected. Correct the errors associated with the ITM record.
Invalid MPS Planning Part	If MPS Plan Part is not null and Part/Rev combination does not exist.
Inactive MPS Planning Part	If MPS Plan Part is not null and Part/Rev combination is not active.
Pre-release MPS Planning Part	If MPS Plan Part is not null and Part/Rev status is Pre-Release.

Product Price Catalog (PPC) Error Messages

The following table lists the more complicated errors associated with the PPC Line Type.

Error Message	Additional Info/Remedy
COGS Pct Rt not allowed (COGS Calc Cd).	The Cost of Sales Percentage Rate can be greater than zero if the Cost of Sales Calculation Code is P (Percentage). Remove the value or set the Cost of Sales Calculation Code to P.
PPC rejected, invalid Item Product.	There is no existing Item Product table or pending PRD record for this Item ID/Item Revision ID. Provide a PRD line for the Item ID/Item Revision ID.
PPC rejected, no matching Item.	There is a PPC record in the input file without a corresponding ITM record (with the same Item ID/Item Revision ID).
PPC rejected, no PCS line provided.	You must provide a Product Cost Schedule (PCS) line for the Item ID/Item Revision ID/Price Catalog Code because the Cost of Sales Calculation Code is C (Cost Schedule). Provide a PCS line or change the value of the Cost of Sales Calculation Code to P (Percentage).
PPC rejected, no PPS line provided.	Provide a Product Price Schedule (PPS) line for the Item ID/Item Revision ID/Price Catalog Code.
PPC rejected, no PWS line provided.	You must provide a Product Warranty Cost Schedule (PWS) line for the Item ID/Item Revision ID/Price Catalog Code because the Warranty Cost Calculation Code is C (Cost Schedule). Provide a PWS line or change the value of the Warranty Cost Calculation Code to P (Percentage).
PPC rejected, PCS line is not allowed.	You cannot insert a Product Cost Schedule (PCS) line for the Item ID/Item Revision ID/Price Catalog Code because the Cost of Sales Calculation Code is not C (Cost Schedule). Remove the PCS line or change the value of the Cost of Sales Calculation Code to C.
PPC rejected, PWS line is not allowed.	You cannot insert a Product Warranty Cost Schedule (PWS) line for the Item ID/Item Revision ID ID/Price Catalog Code because the Warranty Cost Calculation Code is not C (Cost Schedule). Remove the PWS line or change the value of the Warranty Cost Calculation Code to C.
PPC rejected. Bad Item Product.	The pending Item Product (PRD) record for this Item ID/Item Revision ID was rejected. Provide a valid PRD line for the Item ID/Item Revision ID. Unless additional errors are indicated, this PPC line contains no errors.
PPC rejected. Bad ITM.	Unless there are additional error messages for this record, it probably contains no errors. It was rejected because it is dependent on an ITM record that was rejected. Correct the errors associated with the ITM record.
PPC rejected. Bad PCS record.	The pending Product Cost Schedule (PCS) record for this Item ID/Item Revision ID/Price Catalog Code was rejected. Provide a valid PCS line for the Item ID/Item Revision ID/Price Catalog Code. Unless additional errors are indicated, this PPC line contains no errors.
PPC rejected. Bad PPS record.	The pending Product Price Schedule (PPS) record for this Item ID/Item Revision ID/Price Catalog Code was rejected. Provide a valid PPS line for the Item ID/Item Revision ID/Price Catalog Code. Unless additional errors are indicated, this PPC line contains no errors.
PPC rejected. Bad PWS record.	The pending Product Warranty Cost Schedule (PWS) record for this Item ID/Item Revision ID/Price Catalog Code was rejected. Provide a valid PWS line for the Item ID/Item Revision ID/Price Catalog Code. Unless additional errors are indicated, this PPC line contains no errors.
WARR Pct Rt not allowed (Warr Calc Cd).	The Warranty Percentage Rate can be greater than zero if the Warranty Cost Calculation Code is P. Remove value or set the Warranty Cost Calculation Code to P.
PPC rejected, invalid Price Catalog	This Price Catalog does not exist in PRICE_CATLG table.

Product Price Schedule (PPS) Error Messages

The following table lists the more complicated errors associated with the PPS Line Type.

Error Message	Additional Info/Remedy
From Qty must be .0001 > prev To Qty.	The From Quantity value conflicts with an existing Product Price Schedule row or another pending PPS line for the Item ID/Item Revision ID/Price Catalog Code/ Start Date/End Date. If you want to have additional lines for the same Item ID/Item Revision ID/ Price Catalog Code/ Start Date/End Date, the From Quantity must be .0001 greater than the existing/pending To Quantity. There must be no overlapping and no gaps in the quantity values. For example, if you want one entry that covers From Quantity .0001 through To Quantity 4.9999, the next entry must have a From Quantity of 5.000 (.0001 greater than 4.9999).
Must have .0001 From Qty.	Each PPS line for the Item ID/Item Revision ID/ Price Catalog Code/ Start Date/End Date must have a From Quantity = .0001. That is the default if no value is provided in the input file.
Must have 9(10).9999 To Qty.	Each PPS line for the Item ID/Item Revision ID/ Price Catalog Code/ Start Date/End Date must have a To Quantity = 9999999999.9999. That is the default if no value is provided in the input file.
No matching Prod Price Catalog record.	There is a PPS record in the input file without a corresponding PPC record (with the same Item ID/Item Revision ID/Price Catalog Code).
PPS rejected, no matching Item.	There is a PPS record in the input file without a corresponding ITM record (with the same Item ID/Item Revision ID).
PPS rejected. Bad ITM.	Unless there are additional error messages for this record, it probably contains no errors. It was rejected because it is dependent on an ITM record that was rejected. Correct the errors associated with the ITM record.
PPS rejected. Bad PPC record.	The corresponding Product Price Catalog (PPC) record (with the same Item ID/Item Revision ID/Price Catalog Code) contains errors. Unless there are additional error messages for this record, it probably contains no errors. It was rejected because it is dependent on a PPC record that was rejected. Correct the errors associated with the PPC record.
Start Dt must be day after prev End Dt.	The Start Date value conflicts with an existing Product Price Schedule row or another pending PPS line for the Item ID/Item Revision ID/Price Catalog Code/Start Date/End Date. If you want to have additional lines for the same Item ID/Item Revision ID/ Price Catalog Code/ Start Date/End Date, the Start Date must be one day later than the existing/pending End Date. There must be no overlapping and no gaps in the date values. For example, if you want one entry that covers Start Date 2003-01-01 through End Date 2003-06-30, the next entry must have a Start Date of 2003-07-01 (one day later than 2003-06-30).

Product Cost Schedule (PCS) Error Messages

The following table lists the more complicated errors associated with the PCS Line Type.

Error Message	Additional Info/Remedy
From Qty must be .0001 > prev To Qty.	The From Quantity value conflicts with an existing Product Cost Schedule row or another pending PCS line for the Item ID/Item Revision ID/Price Catalog Code/ Start Date/End Date. If you want to have additional lines for the same Item ID/Item Revision ID/ Price Catalog Code/Start Date/End Date, the From Quantity must be .0001 greater than the existing/pending To Quantity. There must be no overlapping and no gaps in the quantity values. For example, if you want one entry that covers From Quantity .0001 through To Quantity 4.9999, the next entry must have a From Quantity of 5.000 (.0001 greater than 4.9999).
Must have .0001 From Qty.	Each PCS line for the Item ID/Item Revision ID/ Price Catalog Code/Start Date/End Date must have a From Quantity = .0001. That is the default if no value is provided in the input file.
Must have 9(10).9999 To Qty.	Each PCS line for the Item ID/Item Revision ID/ Price Catalog Code/Start Date/End Date must have a To Quantity = 9999999999.9999. That is the default if no value is provided in the input file.
No matching Prod Price Catalog record.	There is a PCS record in the input file without a corresponding PPC record (same Item ID/Item Revision ID/Price Catalog Code).
No PPC record with S_COGS_CALC_CD = P.	The corresponding Product Price Catalog (PPC) record (with the same Item ID/Item Revision ID/Price Catalog Code) does not have P for the Cost of Sales Calculation Code value. Remove the PCS record or change the corresponding PPC line with the Cost of Sales Calculation Code value to P.
PCS rejected, no matching Item.	There is a PCS record in the input file without a corresponding ITM record (with the same Item ID/Item Revision ID).
PCS rejected. Bad ITM.	Unless there are additional error messages for this record, it probably contains no errors. It was rejected because it is dependent on an ITM record that was rejected. Correct the errors associated with the ITM record.
PCS rejected. Bad PPC record.	Unless there are additional error messages for this record, it probably contains no errors. It was rejected because it is dependent on a Product Price Catalog (PPC) record that was rejected. Correct the errors associated with the PPC record.
Start Dt must be day after prev End Dt.	The Start Date value conflicts with an existing Product Cost Schedule row or another pending PCS line for the Item ID/Item Revision ID/Price Catalog Code/ Start Date/End Date. If you want to have additional lines for the same Item ID/Item Revision ID/Price Catalog Code/ Start Date/End Date, the Start Date must be one day later than the existing/pending End Date. There must be no overlapping and no gaps in the date values. For example, if you want one entry that covers Start Date 2003-01-01 through End Date 2003-06-30, the next entry must have a Start Date of 2003-07-01 (one day later than 2003-06-30).

Product Warranty Cost Schedule (PWS) Error Messages

The following table lists the more complicated errors associated with the PWS Line Type.

Error Message	Additional Info/Remedy
No matching Prod Price Catalog record.	There is a PWS record in the input file without a corresponding Product Price Catalog (PPC) record (with the same Item ID/Item Revision ID/Price Catalog Code).
No PPC record with S_WARR_CST_CALC_CD = "P."	The corresponding PPC record (with the same Item ID/Item Revision ID/Price Catalog Code) does not have P for the Warranty Cost Calculation to Code value. Remove the PWS record or change the corresponding PPC line Warranty Cost Calculation to Code value to P.
PWS rejected, no matching Item.	There is a PWS record in the input file without a corresponding ITM record (with the same Item ID/Item Revision ID).
PWS rejected. Bad ITM.	Unless there are additional error messages for this record, it probably contains no errors. It was rejected because it is dependent on an ITM record that was rejected. Correct the errors associated with the ITM record.
PWS rejected. Bad PPC record.	Unless there are additional error messages for this record, it probably contains no errors. It was rejected because it is dependent on a Product Price Catalog (PPC) record that was rejected. Correct the errors associated with the PPC record.
Start Dt must be day after prev End Dt.	The Start Date value conflicts with an existing Product Warranty Cost Schedule row or another pending PWS line for the Item ID/Item Revision ID/Price Catalog Code/Start Date/ End Date. If you want to have additional lines for the same Item ID/Item Revision ID/Price Catalog Code/Start Date /End Date, the Start Date must be one day later than the existing/pending End Date. There must be no overlapping and no gaps in the date values. For example, if you want one entry that covers Start Date 2003-01-01 through End Date 2003-06-30, the next entry must have a Start Date of 2003-07-01 (one day later than 2003-06-30).

Project CLIN (CLN) Error Messages

The following table lists the more complicated errors associated with the CLN Line Type.

Error Message	Additional Info/Remedy
CLN rejected, duplicate key.	Each CLN record in the input file must have a unique key (Project ID/CLIN ID). The input file contains multiple CLN records with the same key values indicated on the report. Remove all duplicate CLN records.

PCP Error Messages

The following table lists the more complicated errors associated with the PCP Line Type.

Error Message	Additional Info/Remedy
COGS Pct Rt not allowed (COGS Calc Cd).	The Cost of Sales Percentage Rate cannot be greater than 0 unless Cost of Sales Percentage Rate = P. Remove the value or set the Cost of Sales Percentage Rate to P.
PCP rejected, CCS line is not allowed.	A CLIN Cost Schedule (CCS) line cannot be inserted for the Item ID/Item Revision ID/Project ID/CLIN ID because the Cost of Sales Calculation Code is not C (Cost Schedule). Remove the CCS line or change the value of the Cost of Sales Calculation Code to C.
PCP rejected, CWS line is not allowed.	A CLIN Warranty Cost Schedule (CWS) line cannot be inserted for the Item ID/Item Revision ID/Project ID/CLIN ID because the Warranty Cost Calculation Code is not C (Cost Schedule). Remove the CWS line or change the value of the Warranty Cost Calculation Code to C.
PCP rejected, duplicate key.	Each PCP record in the input file must have a unique key (Item ID/Item Revision ID/Project ID/CLIN ID). The input file contains multiple PCP records with the same key values indicated on the report. Remove all duplicate PCP records.
PCP rejected, invalid Item Product.	There is no existing Item Product or pending PRD record for this Item ID/Item Revision ID. Provide a PRD line for the Item ID/Item Revision ID.
PCP rejected, invalid Project CLIN.	There is no existing Project CLIN or pending CLN record for this Project ID/CLIN ID. Provide a CLN line for the Project ID/CLIN ID.
PCP rejected, no CCS line provided.	A CLIN Cost Schedule (CCS) line must be provided for the Item ID/Item Revision ID/Project ID/CLIN ID because the Cost of Sales Calculation Code is C (Cost Schedule). Provide a CCS line or change the value of the Cost of Sales Calculation Code to P (Percentage).
PCP rejected, no CPS line provided.	Provide a CLIN Price Schedule (CPS) line for the Item ID/Item Revision ID/Project ID/CLIN ID.
PCP rejected, no CWS line provided.	A CLIN Warranty Cost Schedule (CWS) line must be provided for the Item ID/Item Revision ID/Project ID/CLIN ID because the Warranty Cost Calculation Code is C (Cost Schedule). Provide a CWS line or change the value of the Warranty Cost Calculation Code to P (Percentage).
PCP rejected, no matching Item.	There is a PCP record in the input file without a corresponding ITM record (same Item ID/Item Revision ID).
PCP rejected. Bad CCS record.	The pending CLIN Cost Schedule (CCS) record for this Item ID/Item Revision ID/Project ID/CLIN ID was rejected. Provide a valid CCS line for the Item ID/Item Revision ID/Project ID/CLIN ID. Unless there are additional errors indicated, this PCP line contains no errors.
PCP rejected. Bad CLN record.	The pending Project CLIN (CLN) record for this Project ID/CLIN ID was rejected. Provide a valid PRD line for the Project ID/CLIN ID. Unless there are additional errors indicated, this PCP line contains no errors.
PCP rejected. Bad CPS record.	The pending CLIN Price Schedule (CPS) record for this Item ID/Item Revision ID/Project ID/CLIN ID was rejected. Provide a valid CPS line for the Item ID/Item Revision ID/Project ID/CLIN ID. Unless there are additional errors indicated, this PCP line contains no errors.
PCP rejected. Bad CWS record.	The pending CLIN Warranty Cost Schedule (CWS) record for this Item ID/Item Revision ID/Project ID/CLIN ID was rejected. Provide a valid CWS line for the Item ID/Item Revision ID/Project ID/CLIN ID. Unless there are additional errors indicated, this PCP line contains no errors.
PCP rejected. Bad Item Product.	The pending Item Product (PRD) record for this Item ID/Item Revision ID was rejected. Provide a valid PRD line for the Item ID/Item Revision ID. Unless there are additional errors indicated, this PCP line contains no errors.
PCP rejected. Bad ITM.	Unless there are additional error messages for this record, it probably contains no errors. It was rejected because it is dependent on an ITM record that was rejected. Correct the errors associated with the ITM record.
WARR Pct Rt not allowed (Warr Calc Cd).	The Warranty Percentage Rate cannot be greater than 0 unless Warranty Cost Percentage Rate = P. Remove value or set Warranty Cost Percentage Rate = P.

CLIN Price Schedule (CPS) Error Messages

The following table lists the more complicated errors associated with the CPS Line Type.

Error Message	Additional Info/Remedy
CPS rejected, no matching Item.	There is a CPS record in the input file without a corresponding ITM record (same Item ID/Item Revision ID).
CPS rejected. Bad ITM.	Unless there are additional error messages for this record, it probably contains no errors. It was rejected because it is dependent on an ITM record that was rejected. Correct the errors associated with the ITM record.
CPS rejected. Bad PCP record.	Unless there are additional error messages for this record, it probably contains no errors. It was rejected because it is dependent on a Project CLIN Product (PCP) record that was rejected. Correct the errors associated with the PCP record.
From Qty must be .0001 > prev To Qty.	The From Quantity value conflicts with an existing CLIN Price Schedule row or another pending CPS line for the Item ID/Item Revision ID/Project ID/CLIN ID/ Start Date/End Date. If you want to have additional lines for the same Item ID/Item Revision ID/Project ID/ CLIN ID/Start Date/End Date, the From Quantity must be .0001 greater than the existing/pending To Quantity. There must be no overlapping and no gaps in the quantity values. For example, if you want one entry that covers From Quantity .0001 through To Quantity 4.9999, the next entry must have a From Quantity of 5.000 (.0001 greater than 4.9999).
Must have .0001 From Qty.	Each CPS line for the Item ID/Item Revision ID/ Project ID/CLIN ID/Start Date/End Date must have a From Quantity = .0001. That is the default if no value is provided in the input file.
Must have 9(10).9999 To Qty.	Each CPS line for the Item ID/Item Revision ID/ Project ID/CLIN ID/Start Date/End Date must have a To Quantity = 9999999999.9999. That is the default if no value is provided in the input file.
No matching PROJ CLIN record.	There is a CPS record in the input file without a corresponding CLN record (same Project ID/CLIN ID).
Start Dt must be day after prev End Dt.	The Start Date value conflicts with an existing CLIN Price Schedule row or another pending CPS line for the Item ID/Item Revision ID/Project ID/CLIN ID/Project ID/ Start Date/End Date. If you want to have additional lines for the same Item ID/Item Revision ID/Project ID/ CLIN ID/Project ID/Start Date/End Date, the Start Date must be one day later than the existing/pending End Date. There must be no overlapping and no gaps in the date values. For example, if you want one entry that covers Start Date 2003-01-01 through End Date 2003-06-30, the next entry must have a Start Date of 2003-07-01 (one day later than 2003-06-30).

CLIN Cost Schedule (CCS) Error Messages

The following table lists the more complicated errors associated with the CCS Line Type.

Error Message	Additional Info/Remedy
CCS rejected, no matching Item.	There is a CCS record in the input file without a corresponding ITM record (same Item ID/Item Revision ID).
CCS rejected. Bad ITM.	Unless there are additional error messages for this record, it probably contains no errors. It was rejected because it is dependent on an ITM record that was rejected. Correct the errors associated with the ITM record.
CCS rejected. Bad PCP record.	Unless there are additional error messages for this record, it probably contains no errors. It was rejected because it is dependent on a Project CLIN Product (PCP) record that was rejected. Correct the errors associated with the PCP record.
From Qty must be .0001 > prev To Qty.	The From Quantity value conflicts with an existing CLIN Cost Schedule row or another pending CCS line for the Item ID/Item Revision ID/Project ID/CLIN ID/ Start Date/End Date. If you want to have additional lines for the same Item ID/Item Revision ID/Project ID/ CLIN ID/Start Date/End Date, the From Quantity must be .0001 greater than the existing/pending To Quantity. There must be no overlapping and no gaps in the quantity values. For example, if you want one entry that covers From Quantity .0001 through To Quantity 4.9999, the next entry must have a From Quantity of 5.000 (.0001 greater than 4.9999).
Must have .0001 From Qty.	Each CCS line for the Item ID/Item Revision ID/Project ID/ CLIN ID/Start Date/End Date must have a From Quantity = .0001. That is the default if no value is provided in the input file.
Must have 9(10).9999 To Qty.	Each CCS line for the Item ID/Item Revision ID/Project ID/ CLIN ID/Start Date/End Date must have a To Quantity = 9999999999.9999. That is the default if no value is provided in the input file.
No matching PCP record.	There is a CCS record in the input file without a corresponding Project CLIN Product (PCP) record (with the same Item ID/Item Revision ID/Project ID/CLIN ID).
No PCP record with S_COGS_CALC_CD = P.	The corresponding PCP record (with the same Item ID/Item Revision ID/Project ID/CLIN ID) does not have P for the Cost of Sales Calculation Code. Remove the PWS record or change the corresponding PCP line Cost of Sales Calculation Code to P.
Start Dt must be day after prev End Dt.	The Start Date value conflicts with an existing CLIN Cost Schedule row or another pending CCS line for the Item ID/Item Revision ID/Project ID/CLIN ID/Project ID/ Start Date/End Date. If you want to have additional lines for the same Item ID/Item Revision ID/Project ID/ CLIN ID/Project ID/Start Date/End Date, the Start Date must be one day later than the existing/pending End Date. There must be no overlapping and no gaps in the date values. For example, if you want one entry that covers Start Date 2003-01-01 through End Date 2003-06-30, the next entry must have a Start Date of 2003-07-01 (one day later than 2003-06-30).

CLIN Warranty Cost Schedule (CWS) Error Messages

The following table lists the more complicated errors associated with the CWS Line Type.

Error Message	Additional Info/Remedy
CWS rejected, no matching Item.	There is a CWS record in the input file without a corresponding ITM record (same Item ID/Item Revision ID).
CWS rejected. Bad ITM.	Unless there are additional error messages for this record, it probably contains no errors. It was rejected because it is dependent on an ITM record that was rejected. Correct the errors associated with the ITM record.
CWS rejected. Bad PCP record.	Unless there are additional error messages for this record, it probably contains no errors. It was rejected because it is dependent on a Project CLIN Product (PCP) record that was rejected. Correct the errors associated with the PCP record.
No matching PCP record.	There is a CWS record in the input file without a corresponding Project CLIN Product (PCP) record (with the same Item ID/Item Revision ID/Project ID/CLIN ID).
No PCP with S_WARR_CST_CALC_CD=P.	The corresponding PCP record (with the same Item ID/Item Revision ID /Project ID/CLIN ID) does not have P for the Warranty Cost Calculation Code. Remove the CWS record or change the corresponding PCP line Warranty Cost Calculation Code to P.
Start Dt must be day after prev End Dt.	The Start Date value conflicts with an existing CLIN Warranty Cost Schedule row or another pending CWS line for the Item ID/Item Revision ID/Project ID/ CLIN ID/Project ID/Start Date/End Date. If you want to have additional lines for the same Item ID/Item Revision ID/Project ID/CLIN ID/Project ID/Start Date/End Date, the Start Date must be one day later than the existing/pending End Date. There must be no overlapping and no gaps in the date values. For example, if you want one entry that covers Start Date 2003-01-01 through End Date 2003-06-30, the next entry must have a Start Date of 2003-07-01 (one day later than 2003-06-30).