On inbound map checkpoints

Table 1-15 lists the format, cause, and solution (if applicable) for the ECMap messages related to inbound map checkpoints, in numeric order by message number.

**Table 1-15: ECMap messages related to inbound map checkpoints**
Message	Cause	Solution
`(7022) OK: Output Files Checkpoint < > at < > < >`	Cause:
`(7023) OK: EDI OUT File < > Chkpt < > at < >`	Information only. Advises that checkpoint has been set.
`(7024) ERROR: Invalid Date Assignment`	Moving date from one field to another field using an invalid operation.	Modify rule to perform operation.
`(7025) ERROR: < > Control Count Mismatch < > vs < >`	Control counts on the GE do not match the GS.	Bad EDI data. Inform sender.
`(7026) ERROR: < > Reference Mismatch: < > vs < >`	Control counts on the GE do not match the GS.	Bad EDI data. Inform sender.
`(7031) ERROR: Non-Numeric < > Control Count: < >`	Control counts are not numeric for the SE Segment	Bad EDI data. Inform sender.
`(7034) ERROR: Missing < > Control Count: < >`	Control counts are missing for the SE Segment	Bad EDI data. Inform sender
`(7037) FATAL: Rule <rule number> L < > MemVar File Name > 256`	Performed an operation on a file where a defined memory variable is a file name and the size of the memory variable file name is greater than 256 characters.	Modify extended file name to meet the maximum limit imposed.
`(7038) ERROR: No Open File: <file name>`	Occurs when a file management rule has been issued to close a file that is not opened.	Modify file management rule.
`(7039) TRACE: < > < > < >`	A generic trace message that occurs when Verbose Trace is on.
`(7040) FATAL: Nested Perform Limit Exceeded`	Runtime program has a limit of 50 nested rules. This message can occur when a rule calls itself within a nested rule.	Modify perform rule.