Oracle Cloud Computing

Oracle’s E-Business Suite or EnterpriseOne users may be considering moving from local servers to cloud computing. This entails a review of every process, which includes connections to customers, vendors, and transporters. The exchange of large, complex documents such as Purchase Orders will continue as before; using both classical EDI (X12 or EDIFACT) and standardized XML (GS1 or OAGi). These processes must continue without disruption to highly visible Trading Partners.

Here is a comparison of an existing to the potential process. It is for an outbound document; a similar process in reverse occurs for an Inbound document. The process to send an invoice is:

1. Close the order, which triggers the creation of an invoice.
2. The data in the invoice table (header and detail records) are extracted from their table using the EDI Gateway (a module of E-BS or E1).
3. The extraction creates a positional file and the EDI system is alerted.
4. The EDI system converts the file to an X12 Invoice 810 variable position and length file.  Then the AS2, FTPS, or SFTP utility is alerted.
5. The AS2 utility, working with the firewall, transmits the EDI file through the Internet to the customer.
6. The customer confirms receipt of the Invoice (Functional Acknowledgement, 997).

When the instance of E-BS or E1 exists in your cloud, then the EDI system must also be located in the cloud. The processes are in steps 1 through 4 are the same. In step 5, the EDI system alerts the cloud provider a file ready; the prime difference is the IP address is different.  (Changing this is not difficult for a Trading Partner.)

Some have considered renting a “managed service” instead of moving their EDI system to the cloud. In this configuration steps 4 and 5 change. The problem that manage service providers avoid or down play is that configuration of the EDI Gateway, which is labor intensive, must continue to be done by you. The managed service (EDI network) only adapts for the differences customers require in their invoice, such as the code for a UPC number or a GTIN number. A typical invoice has about 75 fields and about 5 look-ups, which must be accurately communicated to the service bureau. This is a daunting task.

Check out our easy-to-use E-Business Suite Tip Sheet that shows you each module and its corresponding transaction set can readily be automated as standard and accepted by your Trading Partner.

*As an Oracle Gold Partner, DCS will be attending Oracle OpenWorld 2013 from September 22-26 in San Francisco, CA at booth number 3421.

Are you considering moving E-BS or E1 to the cloud? What are your concerns about cloud based supply chain document exchanges? If you have done this, please tell us your tips and traps you encountered.

Follow @DCSEDI