On trading partners

These messages are generated due to invalid or mismatched Trading Partner numbers or fields.

Table 1-12 lists the format, cause, and solution (if applicable) for the ECMap messages related to trading partners, in numeric order by message number.

**Table 1-12: ECMap messages related to trading partners**
Message	Cause	Solution
`(5000) OK: executed ABORT_TRANS command for Trading Partner <internal trading partner number>`	A run time map message that is written to the error log. It indicates that the map transaction for the displayed Trading Partner number was aborted by the execution of an ABORT Transaction map rule.	If an error in compliance maps, this error also appears. Solve the earlier fatal errors listed before this message.
`(5001) ERROR: aborting- database Customer has no record for Trading Partner <internal trading partner number>`	An outbound run time map message that is written to the error log along with other detailed information to identify the exact cause of the message. It indicates that the outbound transaction for the displayed Trading Partner was aborted because the Trading Partner definition database, Customer, has no entry for the displayed Trading Partner number.	Either modify this Trading Partner number, or correct the user data file that contains the invalid Trading Partner number.
`(5002) ERROR: aborting- database <trade agreement database> Table <transaction code> has no Trading Partner <internal trading partner number>`	These are outbound run time map messages that are written to the error log along with other detailed information to identify the exact cause of the message. It indicates that the outbound transaction for the displayed Trading Partner was aborted because the Trading Partner definition database, TRADSTAT, has no entry for the displayed Trading Partner number and transaction set or Map Table code.	Either define this Trading Partner number and transaction set by using the Trading Partner menu option, or correct the user data file that contains the invalid Trading Partner number.
`(5004) ERROR: Trading Partner not made current`	An outbound run time map message that is written to the error log along with other detailed information to identify the exact cause of the message. It indicates that the Master Outbound Map Flow record has not been defined with a Trading Partner field. This error is not expected to happen since the Map Flow and map generation options check for this error condition.	Use the User File or Map Flow options to include the Trading Partner field and regenerate the map.
`(5006) ERROR: Trading Partner ID- <internal trading partner number> match not found`	A run time map message that is written to the error log along with other detailed information to identify the exact cause of the message. It indicates that the displayed Trading Partner was not found in the Trading Partner definition databases. This could be due to invalid Trading Partner data or because the displayed Trading Partner has not been defined with the Trading Partner menu option.	Either define this Trading Partner number by using the Trading Partner menu option, or correct the user data file or X12 transaction file that contains the invalid Trading Partner number.
`(5007) ERROR: Trading Partner is blank`	An outbound run time map message that is written to the error log along with other detailed information to identify the exact cause of the message. It indicates that the Trading Partner user data file record was read and the Trading Partner field was blank.	Correct the user data file record to include a valid Trading Partner.
`(5019) TRACE: Trading partner: <internal trading partner number> New Transaction <transaction code>`	Cause:
`(5020) TRACE: New Trading Partner: <trading partner name>`	Found a new trading partner in the data for an inbound or outbound map.
`(5021) TRACE: Changed Trading Partner: <trading partner name>`	This message usually appears after 5020. The trading partner is now different than earlier.
`(5022) TRACE: Map change for Trading Partner <trading partner name> Map: <map name>`	This message usually appears after 5020. The map is now different than earlier.
`(5023) TRACE: Tradstat found for Tptnr <trading partner name> Trans <transaction code> Vers <version number> TstInd <test indicator value> Agency <agency> Release <release>, Overlay < >`	These informational messages occur when Verbose Trace is on. They report that a new Trading Partner has been encountered during the mapping process.
`(5024) FATAL: Trading Partner Database Structure Needs To Be Updated`	The map you ran has a previous version of the ODBC trading partner from an earlier version.	Open Map Properties. Reselect DSN and select OK and that updates your trading partner database.
`(5025) FATAL: Map uses Repeat Elements but ISA_TYPE < 00402`	Cause:	Solution: