Data management system and method for integrating non-homogenous systems

• US 20020107699A1
• Filed: 03/16/2001
• Published: 08/08/2002
• Est. Priority Date: 02/08/2001
• Status: Abandoned Application

• Current Assignee: Covaleo Corporation
• Original Assignee: Covaleo Corporation
• Inventors: Neu, Barry, Prast, Albert, Sharley, Jonathan David, Rivera, Gustavo R., McKinney, Delbert Lee, Lems, Greg, Kelm, Kevin S.
• Application Number:
  US09/812,118
• Publication Number:
  US 20020107699A1
• Time in Patent Office: Days
• US Class Current: 705/1
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]

Abstract

A system and method for exchanging data between a supplier and a buyer through the incorporation of both parties'"'"' backend systems is disclosed. When a buyer submits an order, it is sent to a data manager. The data manager extracts the relevant data from the incoming purchase order and translates it from the buyer-native format to a neutral format. The data manager can next translate the purchase order from the neutral format to the supplier-native format and send the translated purchase order to the supplier where it generally can be directly used by the supplier'"'"'s backend system.

Claims

1. A method for facilitating an exchange of data, the method comprising:

electronically receiving a purchase order;

applying a first translation map to the purchase order to generate a neutral format of the purchase order;

identifying a destination party for the purchase order;

applying a second translation map to the generated neutral format of the purchase order to generate a destination-party-native format of the purchase order, wherein the second translation map is associated with the identified destination party; and

providing the destination-party-native format of the purchase order to the identified destination party.

2. The method of claim 1, wherein the step of electronically receiving the purchase order comprises:

receiving the purchase order from the originating party in an originating-party-native format.

3. The method of claim 1, wherein the purchase order comprises a product identifier, the method further comprising:

prior to providing the destination-party-native format of the purchase order to the identified destination party, comparing the product identifier to a list of appropriate product identifiers, wherein the list of appropriate product identifiers is associated with the identified destination party.

4. The method of claim 3, further comprising:

notifying at least one of a purchase order originating party and the destination party responsive to the product identifier not being included in the list of appropriate product identifiers.

5. The method of claim 1, wherein the purchase order comprises a quantity indicator for an ordered product, the method further comprising:

determining whether the quantity indicator complies with a quantity requirement associated with the ordered product.

6. The method of claim 1, further comprising:

verifying the validity of the received purchase order prior to providing the destination-p arty-native format of the purchase order to the identified destination party.

7. The method of claim 1, further comprising:

verifying the integrity of the received purchase order prior to providing the destination-party-native format of the purchase order to the identified destination party.

8. The method of claim 1, wherein the purchase order is a backend-generated purchase order, the method further comprising:

receiving at least an indication of a non-backend-generated purchase order originated by a buyer;

converting the at least an indication of the non-backend-generated purchase order to a buyer-native-format purchase order; and

electronically providing the buyer-native-format purchase order to the buyer.

9. The method of claim 8, wherein the receiving the at least an indication of the non-backend-generated purchase order comprises:

receiving the at least an indication of the non-backend-generated purchase order from an electronic commerce site.

10. The method of claim 9, wherein the receiving at least an indication of a non-backend-generated purchase order comprises:

receiving an order acknowledgement, wherein the order acknowledgment includes the at least an indication of the non-backend-generated purchase order.

11. The method of claim 9, wherein the receiving at least an indication of a non-backend-generated purchase order comprises:

receiving an invoice, wherein the invoice includes the at least an indication of the non-backend-generated purchase order.

12. The method of claim 8, further comprising:

identifying a executable process corresponding to the received purchase order; and

executing the identified executable process.

13. The method of claim 12, wherein the executing the identified executable process comprises:

calling a routine in a hosted application.

14. The method of claim 13, wherein the executing the identified business process comprises:

generating a response document according to the hosted application

15. The method of claim 1, further comprising:

storing the received purchase order in a central repository.

17. The method of claim 16, wherein receiving the data item comprises:

receiving at least one of a document, a binary file, an audio file, a motion picture file, and a graphical file.

18. The method of claim 16, further comprising:

verifying the integrity of the received data item.

19. The method of claim 16, further comprising:

verifying the validity of the data item prior to providing the third format of the data item to the identified destination party.

20. The method of claim 19, wherein the verifying comprises:

determining if the data item complies with a data item standard associated with the destination party.

21. The method of claim 19, wherein the verifying comprises:

determining if the data item complies with a standard associated with a data-item-originating party.

22. The method of claim 16, further comprising:

extracting an originating party identifier and a data type from the received data item.

23. The method of claim 22, further comprising:

storing the second format of the translated data item according to the originating party identifier and the data type.

24. The method of claim 16, further comprising:

identifying a process corresponding to the received data item; and

executing the identified process.

25. The method of claim 24, wherein the step of executing the identified process comprises:

calling a routine in a hosted application

27. The system of claim 26, wherein the data item comprises a product identifier and wherein the plurality of instructions are further configured to cause the at least a first processor to:

compare the product identifier to a list of appropriate product identifiers, wherein the list of appropriate product identifiers is associated with the identified destination party.

28. The system of claim 27, wherein the plurality of instructions are further configured to cause the at least a first processor to:

notify at least one of a data item originating party and the destination party responsive to the product identifier not being included in the list of appropriate product identifiers.

29. The system of claim 27, wherein the data item comprises a quantity indicator for an ordered product and wherein the plurality of instructions are further configured to cause the at least a first processor to:

determine whether the quantity indicator complies with a quantity requirement associated with the ordered product.

30. The system of claim 26, wherein the plurality of instructions are further configured to cause the at least a first processor to:

verify the validity of the data item prior to providing the destination-party-native format of the data item to the identified destination party.

31. The system of claim 26, wherein the plurality of instructions are further configured to cause the at least a first processor to:

identify an executable process corresponding to the received data item; and

execute the identified executable process.

32. The system of claim 31, wherein the plurality of instructions are configured to cause the at least the first processor to execute the identified executable process by:

calling a routine in a hosted application.

16. A method for facilitating an exchange of data, the method comprising:

electronically receiving a data item, wherein the data item is in a first format;

converting the data item from the first format to a second format;

identifying a destination party for the data item;

converting the data item from the second format to a third format, wherein the third format is associated with the identified destination party; and

providing the third format of the data item to the identified destination party.

26. A system for facilitating an exchange of data, the system comprising:

at least a first processor;

at least a first storage device connected to the at least a first processor; and

a plurality of instructions stored on the at least a first storage device, the plurality of instructions configured to cause the at least a first processor to;

translate a received data item to a neutral format of the data item;

identify a destination party for the data item;

translate the generated neutral format of the data item to a destination-party-native format of the data item; and

provide the destination-party-native format of the data item to the identified destination party.

33. A system for facilitating an exchange of data, the system comprising:

a format map storage device configured to store a plurality of translation format maps;

a translation module in communication with the format map storage device, the translation module configured to receive a data item, translate the data item to a neutral format according to a first of the plurality of translation format maps, and translate the neutral format of the data item to a destination-party-specific format according to a second of the plurality of translation format maps; and

a document data base in communication with the translation module, the document database configured to store the neutral format of the data item.

34. The system of claim 33, further comprising:

a workflow coordinator configured to initiate processing of the received data item.

35. The system of claim 34, further comprising:

a product information database configured to store product information; and

a verification module in communication with the workflow coordinator and the product information database;

wherein the verification module is configured to compare product information included with the received data item and product information stored in the product information database.

36. The system of claim 33, further comprising:

a document viewing module; and

a style sheet storage device in communication with the document viewing module, the style sheet storage device configured to store a plurality of style sheets;

wherein the document viewing module is configured to graphically render the received data item according to a first of the plurality of style sheets.

37. The system of claim 33, further comprising:

a first edge adapter for communicating with a first client in a first client-native method;

a second edge adapter for communicating with a second client in a second client-native method; and

an internal adapter coupled to the first edge adapter and the second edge adapter, the internal adapter configured to communicate with the first edge adapter according to the first client-native method and to communicate with the second edge adapter according to the second client-native method.

38. The system of claim 37 wherein the internal adapter is further configured to communicate with the translation module according to an internal method.