On running the EDI product as an adapter

Table 1-16 lists the format, cause, and solution (if applicable) for the ECMap messages related to running the EDI adapter, in numeric order by message number.

**Table 1-16: ECMap messages related to running the EDI adapter**
Message	Cause	Solution
`(8000) ERROR: ADK does not support %s data type of %s field`	The specified field is an unsupported data type for use with NDO metadata. Currently, the only unsupported field type is Packed Decimal, F_Comp3.	For an unsupported field type, assigned a supported field type in another record. Then use that record for the NDO.
`(8001) ERROR: Put NDO object into NDO queue failed`	The internal queue fails to hold another NDO object.	System error. Call the vendor.
`(8002) ERROR: Incompleted NDO structure parent node missing Transaction Abort.`	The current record placed in the NDO data tree is does not have its specified parent already in the NDO tree.	Correct the map so that the NDO_WRITE command of a parent record is always performed before using NDO_WRITE for a child record.
`(8003) ERROR: Cannot find record %s’s parent %s in data tree, skip this node.`	When reading a NDO Data tree, this message occurs if the parent child relationships in the data tree do not match the parent child relationships defined in the map.	Check that the repository schema matches the parent child relationship described in the map.
`(8004) ERROR: < field name > field has invalid date < date value >.`	Date format of <date value> is invalid.	Check input data field and data type of this <field name>
`(8050) ERROR: Does not support %s type of %s field.`	When reading the NDO data tree, the node data type trying to be read is not a supported conversion type. Currently, conversion is not supported for DT_VoidPTR and DT_Binary.	Do not use DT_VoidPtr or DT_Binary as field type for NDO data trees that are to be read by the EDI Adapter.
`(8051) ERROR: <Schema name> does not match <filename>.`	The schema name of the NDO Data Tree Being read from a Queue must match the schema name defined in the map. Note in the map the schema name is the file name.	Schema name of either the map or the NDO data tree must be changed so that both are identical.
`(8052) ERROR: Record %s undefined in map file, skip all leaf nodes.`	A container node name does not match any record name in the map	Correct either the NDO schema or the map. All container NDO node names should be defined as a record in the map.
`(8053) ERROR: <Field name> undefined in record <record name> in the map file.`	When reading an NDO data tree, the field name of one of the nodes is not matched by a map field name in the map.	Redefine map or schema so that all field names in the schema matches a field name in the map.
`(9000) ERROR: NCPDP switch does not match TP lookup switch`	A TP lookup is used that does not support the inbound type (Batch or Telecom) selected.