Is Apogee ERP right for your business?

Apogee ERP is a great fit for many businesses. Find out if it's the right choice for you! Are you looking for a Apogee ERP demo, technical support, product or pricing information or to simply to compare Apogee ERP with competitive options? Quickly get answers and the information you need.

Integrated business-to-business commerce needs to manage effectively massive transactions for each business partner, exactly like your business partner wants. Transmit purchase orders, picking/packing slips and invoices electronically to your customers and suppliers easily. Convert invoices from your suppliers into Accounts Payable vouchers, and purchase orders into quotations or sales orders without having to rekey them. The Electronic Data Interchange (EDI) module provides these capabilities and more. Using the standard X12 protocol, the EDI module is a user definable tool to map those often changing standards without the need for outside technical assistance. Whether you need to best manage volume of transactions from any client or want to simply reduce the paper flow and errors in your sales and purchasing cycle, this application will return many times the benefit of its acquisition.



  • Supports ANSI X.12 standards.
  • Does not require the use of a third-party translator.
  • Multi-company and Multi-division support.

Trading Partner Setup

  • Unlimited number of trading partners.
  • Generating and receiving options for EDI data is maintained by trading partner. Options for a particular transaction set are also controlled by trading partner.
  • Control numbers are maintained by trading partner/transaction set combination.

Transaction Set Mapping

  • Support for all versions and industry subsets of the ANSI X.12 standard is provided. Default transaction set mappings for all versions supported are also provided.
  • Segment mapping can be done for all trading partners, or for a specific trading partner.
  • You can define which database fields are to be used when generating EDI transaction sets, and can specify the field to use when assigning elements from incoming transaction sets.
  • Qualifiers entered are validated against the EDI qualifier dictionary.
  • An open-ended translation facility exists to convert data from incoming or outgoing transaction sets. This allows you to specify the “correct” EDI abbreviation for things such as unit of measure and currency codes.
  • Segment information can be generated or processed for specific countries only.
  • Formulas are used to specify the values to be placed in generated transaction sets, as well as allowing you to manipulate incoming EDI data before assigning it to a database field.
  • Utilities are provided to copy system transaction set mappings to trading partners, and to copy a trading partner’s transaction set mappings to other trading partners.

Supported EDI Transactions

  • Purchase order (850) and PO change (860).
  • Purchase order acknowledgement (855).
  • Picking/packing slip (advanced shipping notice) (856).
  • Invoice (810).
  • Text meassage (864).
  • EDI transaction acknowledgement (997).
  • Order acknowledgement (832)