The information in the address book:
Holds information that you might need in an EDI message, but that is not included in the original application data.
Contains information that is used to dynamically switch maps at runtime, based on data being sent and received.
Provides a method for routing data based on EDI envelopes.
Serves as the audit and control point relative to keeping track of control numbers for the last EDI messages sent and received.
Provides a cross-reference between the internal application number for a trading partner and the identifiers for that trading partner on the EDI envelope.
The address book provides the sender and receiver information that allows EDI messages to be correctly identified and exchanged. Company data provides the default sender information for outbound maps and the default receiver information for inbound maps. Trading partner data provides the default receiver information for outbound maps and the default sender information for inbound maps. Trade agreements that link trading partner to specific maps can contain additional sender and receiver information that can be used to override the default information – for that specific trading partner/map combination.
This chapter is organized into three sections—company, trading partners, and trade agreements. In ECMap, you can add a new company profile, delete a company profile, or modify a company profile. You can add a new trading partner, delete a trading partner, modify a trading partner, copy a trading partner, or copy the trading partner and trade agreement tables for a trading partner. Finally, you can create a new trade agreement linking a trading partner to a specific map, delete a trade agreement, or modify a trade agreement.
