EXTENSIBLE SCHEMAS AND PARTY CONFIGURATIONS FOR EDI DOCUMENT GENERATION OR VALIDATION

• US 20080168081A1
• Filed: 01/09/2007
• Published: 07/10/2008
• Est. Priority Date: 01/09/2007
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Gaurav, Suraj, Machiraju, Surendra
• Application Number:
  US11/621,362
• Publication Number:
  US 20080168081A1
• Time in Patent Office: Days
• US Class Current: 707/102
• CPC Class Codes: G06F 40/14 Tree-structured documents parsing G06F40/205; validation G06F40/226
• CPC Class Codes: G06Q 10/067 Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

Improved systems for EDI schema generation or EDI document formation are provided based on extensible EDI schema, enhancing design time tools. Automatic schema discovery is performed based on deployed schemas for transaction sets within an EDI document. Instance generation and validation are also customizable to synchronize with per party EDI Properties enabling fine control over various choices for generation or validation processes.

Claims

1. A method for use in an electronic data interchange (EDI) communications system, comprising:

receiving information representative of at least one interchange of an EDI system including a plurality of different types of transaction sets; and

automatically discovering at least one deployed EDI schema in the EDI system that corresponds to at least one of the plurality of different types of transactions sets.

2. The method of claim 1, further including:

validating the at least one interchange based on the at least one deployed EDI schema discovered according to the discovering step.

3. The method of claim 2, wherein said validating includes validating the at least one interchange according to configuration settings specific to a party originating the at least one interchange.

4. The method of claim 2, further comprising:

inputting configuration settings specific to a party originating the at least one interchange to be used during said validating step.

5. The method of claim 1, further including:

generating a reference schema that references the at least one deployed EDI schema discovered during said discovering step.

6. The method of claim 5, further including:

authoring at least one EDI document based on the reference schema generated during said at generating step.

7. The method of claim 5, wherein said generating includes generating a reference schema that references at least one transaction set definition (TSD) deployed in the EDI system.

8. The method of claim 1, wherein said discovering includes automatically discovering at least one deployed EDI schema stored in a relational format of a relational database system.

9. A computer readable medium comprising computer executable instructions for performing the method of claim 1.

10. A computing device comprising means for performing the method of claim 1.

11. A user interface for use in connection with an electronic data interchange (EDI) communications system for communication of EDI documents between EDI parties, comprising:

a party configuration user interface component that receives a specification of at least one option specific to an EDI party of the EDI system for use when at least one of validating or generating an EDI document instance in the EDI system pertaining to the EDI party; and

a configuration application component that applies the at least one option to performing at least one of validation of EDI document instances pertaining to the EDI party or generation of EDI document instances pertaining to the EDI party.

12. The user interface of claim 11, wherein the at least one option specific to an EDI party includes an option that validates at least one interchange automatically based on at least one deployed EDI transaction set definition (TSD) in the EDI system.

13. The user interface of claim 11, wherein the at least one option specific to an EDI party includes an option that specifies definition rules for ISA segments of an EDI document associated with the EDI party.

14. The user interface of claim 11, wherein the at least one option specific to an EDI party includes an option that specifies definition rules for at least one of GS segments or ST segments of an EDI document associated with the EDI party.

15. The user interface of claim 11, wherein the at least one option specific to an EDI party includes an option that specifies the EDI party does not require validation in a defined EDI messaging context.

16. The user interface of claim 11, wherein the at least one option specific to an EDI party includes at least one of an option to perform extended validation based on deployed schema, an option to select rules concerning delimiters used within an Interchange, an option to specify acknowledgement (ACK) properties and an option to select rules pertaining to applied character sets.

17. A server object for interfacing with at least one data store that stores a plurality of electronic data interchange (EDI) transaction set definitions (TSDs), including:

an EDI document processing component that receives information representative of at least one interchange of an electronic data interchange (EDI) system including a plurality of different types of transaction sets; and

an automatic schema discovery component that automatically discovers at least one deployed TSD of the plurality of EDI TSDs that correspond to at least one of the plurality of different types of transactions sets.

18. The server object of claim 17, further including:

a validation component that validates the at least one interchange based on the at least one deployed TSD discovered by the automatic schema discovery component.

19. The server object of claim 17, further including:

a tool for generating at least one EDI document based on a reference schema that references the at least one deployed TSD discovered by the automatic schema discovery component.

20. The server object of claim 17, further including:

a party configuration component that receives settings for at least one option specific to an EDI party of the EDI system for use when at least one of validating or generating an EDI document instance in the EDI system pertaining to the EDI party.