|
|
|
|
| " The underlying philosophy of the FDM4 E.D.I. management system is to provide pure unattended transaction processing with your single or multiple trading partners." |
|
- All FullyAutomated!!!
All outbound E.D.I. Documents can be transmitted with the added functionality of transmitting only, printing only, or transmitting and printing. As well, audit controls have been added to prevent multiple transmissions of E.D.I. Documents.
The following is a list of E.D.I. documents that have been integrated into the FDM4 Order Entry & Purchasing modules with a short description of the functionality.
- 850/875 Outbound Purchase Orders
- 850/875 Inbound Purchase Orders
- The system validates and loads the purchase order into FDM4 order entry and checks pricing, unit of measure, and item number cross-reference. The system also allows an edit screen prior to processing.
- 810/880 Outbound Order Entry Invoices and Credit Memos
- 180 Outbound Return Authorization Request
- 180 Inbound Return Authorization Notification
- The system will transparently load the vendor's return authorization number and validate that there is a Return Authorization number issued via E.D.I.
- 860 Inbound Order Change Notice
- The system will locate the existing order, confirm the line item to be deleted or changed, add new line items, change destination, shipping date, or bill to information. When the line is changed the system validates that quantities cannot be changed lower than what was shipped.
- 869 Inbound Order Status
- The system will request a status report on outstanding purchase orders. The E.D.I. import procedure creates entries in an inquiry review screen. When these inquiries are reviewed the system will allow the response to these inquiries via the 870.
- 870 Outbound Order Status Response
- This procedure will scan the shipping records to see if goods have already been shipped. It then allows the user to add/edit delivery information.
- 855 Outbound Purchase Order Acknowledgement
- At the time of releasing an inbound purchase order (850) to order entry, the system creates the 855 flat file based on the edited 850 as was loaded to FDM4 order entry. The system will allow a full review and edit of 855 documents before being released for transmission. This will allow the assigning of multiple shipment dates and quantities per line item as well as other changes to the order header information. When in the review or edit mode, help lookups are available to assist in preparing an accurate response.
- Pro_EDI is the EDI system of choice at leading organizations such as Southwest Airlines, Consolidated Freightways, Sysco Corporation, and the U.S. Navy.
- Pro_EDI is an EDI translation and document management software system, designed to add EDI capability to existing application environments. Pro_EDI is probably the most advanced EDI integration system, for PC and UNIX systems, on the market today.
- A continuous development process, over the past five years, has resulted in an intuitive, function rich system, which addresses the complexities of integrating the EDI data stream into application environments.
- Pro_EDI is designed to achieve two fundamental objectives:
- Minimize the amount of costly custom programming that is required with other less flexible software solutions.
- Minimize the impact on present operations by calling EDI routines when the application calls for them.
- How Pro_EDI Works
- Pro_EDI works by taking flat files generated by application software and translating them into EDI documents, and translating EDI documents to flat files, which can then be processed by application software.
- This software tool is specifically designed to facilitate an integrated EDI environment. In looking at the basic data flow the Pro_EDI software operates as the EDI engine sitting between the application environment and the communications environment.
- Pro_EDI performs integrity checking on incoming documents, automatically generates functional acknowledgements to send to your trading partners, processes functional acknowledgements received from your trading partners, keeps track of control numbers, and keeps detailed audit trails of all EDI activity.
- For example, an accounts receivable module generates an application file containing invoice data for many different customers. Pro_EDI will take that interface file and create EDI invoice documents for each customer in the file, in the particular EDI format required by each customer.
- Pro_EDI will translate transaction sets of different EDI standards, versions, and implementations into any application file format, defined by you, for each type of document so they can be processed by your application software.,
- You can track documents by trading partner, interchange control numbers, group control numbers, document control numbers, or by your own user defined reference numbers, such as invoice number or PO number.
- To further enhance the integrated environment all key management reports can be generated on-line using the command line processor.
- The translator can also be run on-line, from batch or script files, or from other applications. This means you can run the translators at pre-scheduled times or on demand. This feature satisfies trading partners which require EDI transmissions to take place at pre-set times during the day as well as those trading partners who require EDI transmissions at random times during the day.
- Pro_EDI supports the ANSI X12 standards and the EDIFACT standards, including all subsets such as TDCC, WINS, VICS, AIAG, UCS, etc. Multiple releases of the standards can be maintained concurrently within the software database. Different versions of the same transaction sets can also be maintained concurrently in the database. As new versions of the standards are released they will be made available to Pro_EDI customers holding maintenance contracts.
- User Control
- Pro_EDI permits user defined application interface file (AIF) layouts, transaction sets, and mapping between the two. Many different transaction sets can be mapped into one AIF or one transaction set can be mapped into many AIFs.
|
|
|
|
|
|
