How AceMapper handles N/A, N/R, U/K

When validating an application, AceMapper handles U/K and N/A values in the VCdb the same way. (U/K stands for Unknown - the attribute has not been researched yet. N/A stands for Not Available - researched, but no information available at this time). If the VCdb has U/K or N/A and the application has a value such as VTEC, the application will be considered valid and the attribute will appear on the application (it will not be changed to a note).

N/R stands for Not Required. The attribute was researched and is known to not exist. For example, a non-VTEC engine doesn’t have an Engine Version so N/R is used. In the case of the Honda Civic engines, the N/R really means non-VTEC. If the application has VTEC and the VCdb has N/R, the application is invalid.

When an attribute is excepted (e.g. Exc. VTEC), U/K, N/A, and N/R are handled the same way. The except can’t be translated to individual attributes without putting U/K, N/A or N/R on the application. That’s not allowed, so the excepted attribute is converted to a note. For example, if the application has Exc. VTEC and the VCdb has N/R, N/A or U/K, Exc. VTEC will appear as a note on the application.