System, method and computer program product for EDI-to-EDI translations

• US 20080294645A1
• Filed: 05/22/2007
• Published: 11/27/2008
• Est. Priority Date: 05/22/2007
• Status: Active Grant

• Current Assignee: Sybase Incorporated (SAP SE)
• Original Assignee: Sybase Incorporated (SAP SE)
• Inventors: Leibowitz, Eric, Nilson, Eric
• Granted Patent: US 9,002,870 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database

Abstract

Systems, methods and computer program products for mapping an inbound EDI (Electronic Data Interchange) transaction to one or more outputs are described herein. An embodiment operates by receiving an inbound EDI transaction, and translating the inbound EDI transaction to any combination of EDI outbound transactions and non-EDI outbound transactions. Such translation is performed according to a map file, which is generated as follows. The inbound and any outbound EDI transactions are defined, and templates of the inbound and outbound EDI transactions are also defined. Then, mappings between the template of the inbound EDI transaction and the templates of the outbound EDI transactions are defined. A mapping between the inbound EDI transaction and application data may also be defined, where the application data may include a text file, a XML file, and/or a table of a database. Rules relating to or governing the mapping of the inbound EDI transaction to outputs may also be created. These definitions, mappings and rules are stored in the map file.

Claims

1. A method of mapping an inbound EDT transaction to one or more outputs, comprising:

receiving said inbound EDT transaction; and

translating said inbound EDT transaction to any combination of EDT outbound transactions and non-EDI outputs, wherein said translating step is performed according to a map file.

2. The method of claim 1, further comprising:

defining said inbound EDT transaction;

defining any outbound EDT transactions;

defining a template of said inbound EDT transaction;

defining templates of said outbound EDT transactions; and

defining a mapping between said template of said inbound EDT transaction and said templates of said outbound EDT transactions;

wherein said transaction, template and mapping definitions are stored in said map file.

3. The method of claim 2, further comprising:

defining a mapping between said inbound EDT transaction and application data.

4. The method of claim 3, wherein said application data comprises at least one of a text file, a XML file, and a table of a database.

5. The method of claim 3, further comprising:

creating rules relating to or governing mapping of said inbound EDT transaction to outputs.

6. A system for mapping an inbound EDT transaction to one or more outputs, comprising:

means for receiving said inbound EDT transaction; and

means for translating according to a map file said inbound EDI transaction to any combination of EDI outbound transactions and non-EDI outputs.

7. The system of claim 6, further comprising:

means for defining said inbound EDI transaction;

means for defining any outbound EDI transactions;

means for defining a template of said inbound EDI transaction;

means for defining templates of said outbound EDI transactions; and

means for defining a mapping between said template of said inbound EDI transaction and said templates of said outbound EDI transactions;

wherein said transaction, template and mapping definitions are stored in said map file.

8. The system of claim 7, further comprising:

means for defining a mapping between said inbound EDI transaction and application data.

9. The system of claim 8, wherein said application data comprises at least one of a text file, a XML file, and a table of a database.

10. The system of claim 8, further comprising:

means for creating rules relating to or governing mapping of said inbound EDI transaction to outputs.

11. A computer program product comprising a computer useable medium having control logic stored therein, said control logic when executed by a computer causing said computer to map an inbound EDI transaction to one or more outputs, said control logic comprising:

means for causing a computer to receive said inbound EDI transaction; and

means for causing a computer to translate according to a map file said inbound EDI transaction to any combination of EDI outbound transactions and non-EDI outbound transactions.

12. The computer program product of claim 11, said control logic further comprising:

means for causing a computer to define said inbound EDI transaction;

means for causing a computer to define any outbound EDI transactions;

means for causing a computer to define a template of said inbound EDI transaction;

means for causing a computer to define templates of said outbound EDI transactions; and

means for causing a computer to define a mapping between said template of said inbound EDI transaction and said templates of said outbound EDI transactions;

wherein said transaction, template and mapping definitions are stored in said map file.

13. The computer program product of claim 12, said control logic further comprising:

means for causing a computer to define a mapping between said inbound EDI transaction and application data.

14. The computer program product of claim 13, wherein said application data comprises at least one of a text file, a XML file, and a table of a database.

15. The computer program product of claim 13, said control logic further comprising:

means for causing a computer to create rules relating to or governing mapping of said inbound EDI transaction to outputs.