www.usps.com. Home  |  Help
 
Common File Transfer Errors

When Mail.dat files are transmitted, file transfer errors may occur. Some of the most common file transfer errors are listed here with guidelines for fixing them. For more help with Mail.dat files, please contact IDEAlliance.


Blank Mandatory Fields

Error message

WARNING: [Date] [Time] ERROR: In "file name" mandatory field "field name" (Row #: Position [start] #_[stop] #) is blank.

Explanation

A mandatory field in the reported file contains no data. In the error message, Row # refers to the record number within the failed file that is missing data. Position [start] #_[stop] # refers to the position (i.e., field) within the row that is missing data.

Fix

Enter the required field listed in the error message.



Invalid Data in Mandatory Fields

Error message

WARNING: [Date] [Time] ERROR: In "file name" mandatory field "field name" (Row #: Position [start] #_[stop] #) contains invalid data.

Explanation

A mandatory field in the reported file contains invalid data. In the error message, Row # refers to the record number within the failed file that is missing data. Position [start] #_[stop] # refers to the position (i.e., field) within the row that contains invalid data.

Fix

Refer to mail.dat to ensure that all fields contain relevant data.



Invalid Data in Optional Fields

Error message

WARNING: [Date] [Time] ERROR: In "file name" optional field "field name" (Row #: Position [start] #_[stop] #) contains invalid data.

Explanation

An optional field in the reported file contains invalid data. In the error message, Row # refers to the record number within the failed file that is missing data. Position [start] #_[stop] # refers to the position (i.e., field) within the row that contains invalid data.

Fix

Refer to mail.dat to ensure that all fields contain relevant data.



Two Fields Contain Incompatible Data

Error message

WARNING: [Date] [Time] ERROR: In "file name" the "field name" (Row #: Position [start] #_[stop] #) and "field name" (Row #: Position [start] #_[stop] #) fields contain incompatible data.

Explanation

The fields in the reported file contain incompatible data. This occurs when reported information between related fields is incompatible. In the error message, Row # refers to the record numbers within the failed files that are incompatible.

Fix

Refer to mail.dat to see expected data for each field. Check own data for incompatibilities.



Two Fields Contain Data Where Only One Should

Error message

WARNING: [Date] [Time] ERROR: In "file name" field "field name" (Row #: Position [start] #_[stop] #) should be mutually exclusive to the "USPS Pub Number" (Row #: Position [start] #_[stop] #) field, but both fields contain data.

Explanation

The referenced fields both contain data. In this particular type of mailing, one or the other field may contain data, but not both. In the error message, Row # refers to the record numbers within the failed file that contain data. You must remove data from one of the fields in order to submit this file.

Fix

Refer to mail.dat to see expected data for each field. Check own data for incompatibilities.



Two Fields Are Blank Where At Least One Should Contain Data

Error message

WARNING: [Date] [Time] ERROR: In "file name" either the "field name" (Row #: Position [start] #_[stop] #) field or the "field name" (Row #: Position [start] #_[stop] #) field should be filled, but both fields are blank.

Explanation

Neither field referenced contains data. In this mailing, one of these fields must contain data, but both are blank. In the error message, Row # refers to the record numbers within the failed files that are missing data. You must supply the data for one of these fields in order to submit this file.

Fix

Refer to mail.dat to see expected data for each field. Check own data for incompatibilities.



Incorrect Record Length

Error message

WARNING: [Date] [Time] ERROR: In "file name" length of "record #" is incorrect.

Explanation

A record of incorrect length was found in one of the Mail.dat files.

Fix

Refer to mail.dat to see expected record length for each field. Check own data for incompatibilities.



Incorrect Reference

Error message

WARNING: 01-Aug-01 6:10 PM: ERROR:In "c:\maildat\ABCD1234.csm"Row #2, the CONTAINER_ID and the SIBLING_CONTAINER_REF_ID fields cannot contain the same values.

Explanation

A container that references itself.

Fix

Ensure that the values in the CONTAINER_ID field and the SIBLING_CONTAINER_REF_ID are different.



Related Fields are not Related

Error message

WARNING: 01-Aug-01 6:19 PM: ERROR: In "c:\maildat\ABCD1234.mpu"The CO_PALLETIZATION_CODE field in Record #1 cannot be blank,since the corresponding WSR record is present.

Explanation

If the Walk Sequence (.wsr) file is used in the Mail.dat transfer, then the Co-Palletization Code field in the Mail Piece Unit (.mpu) record must be present.

Fix

Ensure that the existence of a Walk Sequence (.wsr) file makes the Co-Palletization Code field in the Mail Piece Unit (.mpu) record mandatory.



Duplicate Key

Error message

WARNING: 27-Jun-01 3:33 PM: ERROR:In "c:\maildat\ABCD1234.csm"The Key fields of record #5 are duplicated within this file.

Explanation

The key fields in a record are found to be the same in another record.

Fix

Ensure that duplicate keys do not exist in any of the Key fields.



Invalid Key

Error message

WARNING: 01-Aug-01 7:02 PM: ERROR:In "c:\maildat\ABCD1234.cqt" the corresponding Key fields of record #766 do not match with a CSM record in this job.

Explanation

The key fields in a child record do not correspond to a parent record.

Fix

Ensure that child records match with their corresponding parent records.



Missing File/Record (Can not be found)

Error message

WARNING: 01-Aug-01 7:02 PM: ERROR: In file "c:\maildat\ABCD1234.mpu" Record #3, the RATE_CATEGORY field is set to 'A', but no corresponding WSR record is present.

Explanation

A rate category claims saturation walk sequence; therefore, we would expect to see a Walk Sequence Record.

Fix

Ensure that Walk Sequence Record exists when rate category claims saturation walk sequence.



Count Mismatch

Error message

WARNING: 01-Aug-01 6:16 PM: ERROR: The 'CSM' record count '49' as indicated in the "c:\maildat\ABCD1234.hdr"file do not match the actual number of record(s) '51' found in the "c:\maildat\ABCD1234.csm" file.

Explanation

The Header record count does not match the actual record count.

Fix

Check the header record count to ensure it matches with the actual record count.



Reference to Non-Existing Record

Error message

WARNING: 27-Jun-01 3:44 PM: ERROR: In "c:\maildat\ABCD1234.csm" The following Sibling Container Reference ID(s) do not correspond to any original CSM record(s) in this file. Sibling Container Ref ID: 000101Sibling Container Ref ID: 000100

Explanation

Reference is made to a file that does not exist.

Fix

Check that all required files exist in mail.dat.



Key Violation

Error message

WARNING: 02-Aug-01 1:12 PM: ERROR: In "c:\maildat\ABCD1234.mcr" the corresponding key fields of the following MCR record do not match with any MPU record(s) in this job. JOB_ID: 'ABCD1234', COMPONENT_ID: 'S3S3 ', SEGMENT_ID: 'S3 ', MPU_ID: 'S4 '. The following MPU record(s) do not contain any corresponding MCR record(s): Job_id: '00004230', Segment_id: 'S3 ', MPU_id: 'S3 '

Explanation

In this case, there could be error messages for all corresponding files in a relationship: Mailpiece Unit, Component, and the MPU/C Relationship records.

Fix

Check that all key records in th MCR record correspond to a job in th MPU record.



Missing Required Field

Error message

WARNING: 02-Aug-01 4:20 PM: ERROR: There must be at least one or more MCR record(s) present in file "d:\00-1jobs\copy of 00004230\dmti5813.mcr" for every MPU record found in file "d:\00-1jobs\copy of 00004230\dmti5813.mpu".The following MPU record(s) do not contain any corresponding MCR record(s): Job_id: '00004230', Segment_id: 'S3 ', MPU_id: 'S3 '

Explanation

The relationship between the mailpiece unit records and the component records must be defined with the mpu/c relationship record.

Fix

Ensure that all realtionship are defined between MPU records and component records.


MPU Weight Source

Error message

WARNING: 17-Oct-00 2:55 PM: ERROR: In "filename.mpu" mandatory field "MPU_WEIGHT_SOURCE" (Row #1:position 66_66) is blank.

Fix

In the Mailpiece Unit record, the MPU Weight Source field is required and must contain one of the following alpha characters:

A = Agent real-time
C = Calculated formula
L = Logical implied from rate
P = Postal Clerk


Permit Number and USPS Publication Number

Error message

WARNING: 17-Oct-00 2:55 PM: ERROR: In "filename.cpt" either the "PERMIT_NUM" (Row #1:position 91_98) field or the "USPS_PUB_NUM" (Row #1:position 84_90) field should be filled, but both fields are blank.

Fix

A Permit number or USPS Publication number is required in the Component Record of each Mail.dat file.


Postage Payment Option

Error message

WARNING: 17-Oct-00 2:55 PM: ERROR: In "c:\filename.cpt" mandatory field "POSTG_PAYMENT_OPT" (Row #1:position 131_131) is blank.

Fix

In the Component record, the Postage Payment Option field is required and must contain one of the following alpha characters:

C = CPP
D = Debit
V = PVDS
T = CAPS
0 = Other
B = Billing


Component Weight Source

Error message

WARNING: 17-Oct-00 2:55 PM: ERROR: In "c:\filename.cpt" mandatory field "COMP_WEIGHT_SOURCE" (Row #1:position 53_53) is blank.

Fix

In the Component record, the Component Weight Source is a required field and must contain one of the following alpha characters:

A = Agent real-time
C = Calculated formula
L = Logical implied from rate
P = Postal Clerk


Zone/Destination Entry

Error message

WARNING: 20-Oct-00 1:34 PM: ERROR: In "c:\filename.cqt" the "3_5_DIGIT_REC" (Row #111:position 20_20), and the "ZONE_DEST_ENTRY" (Row #111:position 31_31) fields contain incompatible data.

Fix

In the Container Quantity record, if the entry in the Zone Destination Entry field is a "D" or an "L" there must be five-digit ZIP in the 3 Digit/5 Digit field.


DUNS Number Mail Facility

Error message

WARNING: 9-Mar-01 10:47 AM: ERROR: In "c:\filename.cpt" mandatory field "DUNS_NUM_MAIL_FACILITY" (Row #9:position 179_193) is blank.

Fix

The Dunn and Bradstreet number for the mailer's facility must be entered into position 179-193 in the Component record. This field is required for use with PostalOne!.

Skip navigation links and go to page end.
POSTAL INSPECTORS   Preserving the Trust POSTAL INSPECTORS
Preserving the Trust