Common compliance scenarios and responses

This section describes common compliance errors and their responses. Although the descriptions represent typical error scenarios, the list is not all inclusive, and you may encounter different errors for which you should contact your Sybase technical representative.

**Table 4-1: Map error scenario 1**
Description	Map response
When NM101 NE IL is in loop 2100A, the map reports: Segment not found The map should report on the specific error; for example, NM101 in loop must equal IL.	The logic that the map follows will not get to the mapping for the NM1 in which loop 2100A is defined because the qualifier is not an IL (a valid value). Therefore, the map produces a generic error message.

**Table 4-2: Map error scenario 2**
Description	Map response
In the 837I map, an Invalid Error on REF Loop 2010AA processes the second REF at the incorrect level.	The 837I Implementation Guide contains errors, where the same code for both REF segment definitions and the REF segments in this instance are defined one after the other. Therefore, there is no logical way to determine which REF is correct.

**Table 4-3: Map error scenario 3**
Description	Map response
In the 834 map, the map reports no errors on N1 qualifiers in Loop 1000. Instead, the user sees the following message: Not found in master segment table Flow points have element qualifiers. Therefore, if the qualifier is wrong, it does not move to the N1 level; thus, the map reports no specific error.	The logic that the map follows will not get to the mapping for the NM1 in which loop 2100A is defined because the qualifier is not an IL (a valid value). Therefore, the map produces a generic error message.