Product Warranty Cost Schedule (PWS) Error Messages

These are 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).