• Eliminates Manual Entry of Customer Orders
• Eliminates Manual Generation of Customer Acknowledgements
• Minimizes Order Billing Cycle
• Eliminates the Need for Costly Pre-Printed Forms
• Eliminates Manual Entry of Customer’s Cash Receipts

This module is designed to update the DMACS system with transactions that originated from the EDI system by receiving inbound cash receipts, outbound A/R invoices, Purchase Orders, and Sales Order acknowledgments. Prior to actually transmitting outbound EDI data, the DMACS system allows the identification of customers and vendors who are to receive these outbound transactions.

At OSLabs we are dedicated in providing the highest standards of encoded business transactions for computer-to-computer interchange by utilizing the latest methods of security purposes by ensuring date integrity, confidentiality, verification of origin by delineating information for authentication, encryption, and compression.

Flow of In-Bound Transactions

EDI Transaction Sets enter the DMACS database during the load process when EDI records are converted from a work file to the data base file for use by a transaction processing program.

An Order Entry EDI batch program converts the records from a separate record for each inbound EDI transaction that applies to a customer or vendor. The work file is created as an interface from the EDI system to the DMACS system and a report is generated showing the error messages for the records that did not pass the edit process. The last page of the report, (or the only page is if there were no errors), is a summary page showing the number of records processed and the number of records converted.

These transaction processing programs select transaction sets, such as sales orders, and update the appropriate file. During this process, an error report may be generated to assist in identifying rejected transactions.

An archive program can be used to archive processed EDI records.

Flow of Outbound Transactions

Prior to transmitting outbound EDI data DMACS identifies which customer and vendors are to receive either outbound EDI transactions consisting of either

A/R invoices or purchase and sales order acknowledgments.

DMACS then stores both the customer’s (or vendor’s) EDI receiver ID and EDI sender ID on each outbound EDI record. If the receiver ID has not been defined for the customer, then the system will store the customer’s sender ID and receiver ID in an appropriate work file.

For example, if a customer is sent outbound invoices, then DMACS will create a pre-assigned EDI transaction Set ID number record (i.e., 810) for that customer number. If the same customer also receives Sales Order’s (i.e., 855), then another record will be created for that customer and transaction Set ID number 855. Similarly, if a vendor is sent outbound Purchase Order’s, then an 850 record will be created. This allows you to simply define the transaction Set ID number that applies to a vendor or customer, and the appropriate record will be stored.

For each outbound invoice that is processed, DMACS creates one invoice header record and multiple invoice line item and comment records.