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. You can now print the text and save it for use by Technical Support personnel.
There are several 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 PT2 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 the "General Report Error Messages" section. Errors associated with the PT2 Line Type are outlined in the "Part (PT2) Error Messages" section.
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. |
The following table lists errors associated specifically with processing the PT2 Line Type.
Error Message |
Additional Info/Remedy |
Cannot change Ord Policy (Ord To Qty). |
The Order Policy Type cannot be changed. There is an existing Part Project record with a non-zero value in the Order To Quantity column. 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). |
The Order Policy Type cannot be changed. There is 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 a value greater than zero, 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 the Multiple Lot Size Quantity to zero, 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 or change the Order Policy Type to P. |
PT2 rejected, duplicate key. |
Each PT2 record in the input file must have a unique key (Part ID/Part Revision ID). The input file contains multiple PT2 records with the same key values indicated on the report. Remove all duplicate PT2 records. |