RedPrairie EDI: Many Alternatives and Configuration Details
Warehousing, Your Customers, and the ASN
The warehousing and transport modules of RedPrairie’s E2e Business Process Platform™ are thorough and complex. DCS experience shows that ASN EDI processes and integration are more difficult than PO and Invoice EDI because ASN’s cannot arrive late. A Shipment Notice (ASN, 856 or DESADV) must arrive before the shipment or a chargeback may be levied.
Fortunately, RedPrairie has sound EDI capability or can readily export to your existing EDI system. This means the messages are sent promptly and the data needed for invoicing is passed to your business application. Integrating RedPrairie with an EDI package like Sterling Commerce’s Gentran:Server™, GXS’ TrustedLink™ and Biz™ products, Tie Commerce’s eVision™, and others is straight forward, but not trivial. We can help you determine if you can integrate with your existing EDI system or help determine the best fit for you.
Process automation brings immediate efficiencies. Connections to customers can be made using the native EDI system or though your existing EDI system. Each alternative has pros and cons. The native EDI system can be readily configured and data passed to the invoicing business application. Alternatively, data can be export to your existing EDI system, but customization using the RedPrairie DLx Integrator™ may be needed to ensure all key customer required fields (elements) are sent.
In addition to the Shipment Notice, users of the transport module experience greater piece of mind when all customer delivery messages and vendor shipment messages are delivered in real time. This is because the X12 Shipment Status Transaction Set 214 is now available from most truckers and parcel carriers. Time lost to check shipment statuses can be devoted to more important tasks.
Users of the RedPrairie Workforce™ suite can use the native EDI system (priced separately) or use or purchase an existing EDI and AS2 systems. Integration is a significant task, as is configuration of the native system.
EDI too often is an afterthought during the upgrade or suddenly comes up as an “on demand” project requested by a key customer that needs to be completed yesterday. In both scenarios you are forced to piece together a workable solution. This is something that you must do well to ensure best business practices are being followed, since future development is built on this foundation.
Here are the necessary deliverables you must provide:
- Identify key resources and opportunities in your Red Prairie environment.
- Develop the project plan with all of its appropriate components (including training).
- Set-up your development and test EDI systems.
- Create a comprehensive map for each key Transaction Set, such as the Inbound Purchase Order (850).
- Customize the comprehensive map for each Trading Partner.
- Set-up and test communications between between the translator and the interface.
- Set up data and transmission testing: setting AS2 or FTP over your VPN to your Trading Partners test mailbox. This is done while working closely with the firewall manager.
- Archive off the old EDI system and data.
- Set up the document types and processing rules.
- Check the address book to ensure all customer locations and their part numbers have been added.
- Set up the tables required to receive/send (UDC codes, Partner Cross-References, Partner Profiles, etc.).
- Install and test the finished maps and setup.
- Train users (Customer Service, Accounts Receivable, and more).
- Train I.T. (daily operations and mapping).
- Have help available for support if needed.
The EDI perspective is clear: RedPrairie EDI capability is robust and reliable. The key task is to maintain undisturbed production data EDI during the conversion.
Let DCS help you add more process automation by building upon your EDI foundation. Since setting up RedPrairie EDI is straight forward but not trivial, we recommend DCS Next Level™ Conversion service. Your mapping will be thorough, quick, and economical due to our many years of warehouse and transport EDI experience. Having DCS develop the first few Trading Partners and communication parameters lowers the cost of implementation, and hastens payback, and builds a solid foundation for future EDI additions.
- Most of the U.S. companies conducting X12 or EDIFACT EDI requirements are well known to us.
- Popular EDI Transaction Sets such as Inbound PO’s (850), Outbound ASN’s (856), Outbound Invoices (810), Inbound Releases (830), and Outbound PO Acknowledgements (855) have been implemented at many of our customers.
- You may also consider 3PL EDI (94x series) and Transportation EDI (21x series).
- Finally, connections using EDI INT AS2 or FTP over a VPN reduce cost by elimination of pricey Value Added Networks.
With experienced professionals, you can avoid common pitfalls and headaches when implementing RedPrairie EDI. Your first step is easy, email DCS for your free assessment.