EDI Translation Software shall conform to the specific trading partner options to be discussed in the following. Transaction ID: Transaction set for every trading partner shall be defined by the translation software. This is to be done so to validate the creation of a particular EDI document between your trading partners. Any transaction set that would be found not setup correctly shall be rejected and shall not be incorporated with the applications but instead be put on a rejected pile and be subjected to a review. Group IDs: You must be allowed by the translators to set up a collection of transaction sets that can be sending and received from specified trading partners. Translator must then be instructed to only receive POs and remittance data from a certain company and that you shall only be allowed to send invoices and PO acknowledgments to them. This preference lets you annex invalid document groups that can savage you from a disadvantage situation like having your Class a client price being sent to a Class B client. Trading partners standard versions: Version control shall be allowed by having EDI Translation Software letting you map any document and classify its standards version. In the event that a trading partner conveys a document with a newer version than what you have received earlier, the software shall automatically reject the document and have it reviewed for it did not coincide to your map setup. Production or test modes: Transaction set for every trading partner shall be setup in test n10de and shall be later endorsed to production to prevent it from directly interfacing with your applications. This option is important for your translation software as this serves as your indicator to where you shall place the EDI document intended for a testing or production mailbox on an ISP or VAN. To further illustrate its importance, visualize a test mode wherein you receive a purchase order and then your software automatically integrates your PO into the application. Production and test documents shall at all times be treated distinctly. Electronic envelop contents: This contains the electronic document which is particular to an individual trading partner. The software lets you make EDI documents for every trading partner. Network IDs: Communications vehicle can be chosen differently between a specific EDI trading partner. A partner may use several ISPs or VANS requiring you then to work on various kinds of network 10 for each. Control Numbering: In order to monitor all your transactions, sequential control numbers shall be created and maintained among each trading partner. Essential EDI control numbers is vital to matching up receipt record to the control numbers. This matching process provides you a chance to check if there are any missing documents.