Claims Analysis
Total Claims: 18
Claim 1
Independent Claim
183 words
A combination software and hardware system, for managing electronic data interchange (EDI) between a sending trading partner and a receiving trading partner, the system comprising: a) receiving means for receiving data from said sending trading partner, said received data containing, selectively, standard EDI structured data and non-standard EDI data, and said non-standard EDI data having a structure substantially similar to a standard EDI data structure, and said non-standard EDI data or an identifier associated with said non-standard EDI data being corrupted before being received by the receiving means; b) compare means, coupled to said receiving means, for comparing said structure of said non-standard EDI data received to a library of standard EDI data structures, and identifying a standard EDI data structure in said library most similar to said structure of said received data; and c) data file creating means, coupled with said compare means, for creating from said received data without interactive intervention a data file having a structure definition the same as said standard EDI data structure in said library compared to be most similar to said structure of said received data.
Claim 2
Dependent Claim
183 words
A combination software and hardware system, for managing electronic data interchange (EDI) between a sending trading partner and a receiving trading partner, the system comprising: a) receiving means for receiving data from said sending trading partner, said received data containing, selectively, standard EDI structured data and non-standard EDI data, and said non-standard EDI data having a structure substantially similar to a standard EDI data structure, and said non-standard EDI data or an identifier associated with said non-standard EDI data being corrupted before being received by the receiving means; b) compare means, coupled to said receiving means, for comparing said structure of said non-standard EDI data received to a library of standard EDI data structures, and identifying a standard EDI data structure in said library most similar to said structure of said received data; and c) data file creating means, coupled with said compare means, for creating from said received data without interactive intervention a data file having a structure definition the same as said standard EDI data structure in said library compared to be most similar to said structure of said received data.
Claim 3
Dependent Claim
43 words
The system according to claim 1 wherein said non-standard received data and library of standard EDI data structures include distinguishably delimited segments of data for identifying said standard EDI data structure in said library most similar to said structure of said received data.
Claim 4
Dependent Claim
42 words
The system according to claim 2 wherein said received data is compared to said library of standard EDI data structures by means of pattern recognition of said distinguishably delimited segments of data of said received data and library of EDI data structures.
Claim 5
Dependent Claim
15 words
The system according to claim 1 further including storage means for storing said received data.
Claim 6
Dependent Claim
16 words
The system according to claim 4 wherein said data file is stored in said storage means.
Claim 7
Dependent Claim
246 words
A combination software and hardware system for managing and maintaining data received from a sending trading partner and for accessing said data by a receiving trading partner, the system comprising: a) data file creating means, for creating from said received data first and second data files, said data being, selectively, standard Electronic Data Interchange (EDI) data and non-standard EDI data, and said non-standard EDI data having a structure substantially similar to a standard EDI data structure, and said non-standard EDI data or an identifier associated with said non-standard EDT data being corrupted before being received: a1) said first data file having a pre-defined template format for managing any of said received data that conforms to said template format, said first file created from a merging of received data that conforms to said template format into data fields of said template format; and a2) said second data file for managing any of said received data that does not conform to said template format, said second file created from a transfer of said data to said second file without any template format interpretation of said received data, and appending said second file to an end of said first file, and wherein both said first and second data files are created without interactive operator intervention; and, b) access means, coupled to said first and second data file, for providing electronic access to and use of said first and second data file by any authorized user or group of users.
Claim 8
Dependent Claim
246 words
A combination software and hardware system for managing and maintaining data received from a sending trading partner and for accessing said data by a receiving trading partner, the system comprising: a) data file creating means, for creating from said received data first and second data files, said data being, selectively, standard Electronic Data Interchange (EDI) data and non-standard EDI data, and said non-standard EDI data having a structure substantially similar to a standard EDI data structure, and said non-standard EDI data or an identifier associated with said non-standard EDT data being corrupted before being received: a1) said first data file having a pre-defined template format for managing any of said received data that conforms to said template format, said first file created from a merging of received data that conforms to said template format into data fields of said template format; and a2) said second data file for managing any of said received data that does not conform to said template format, said second file created from a transfer of said data to said second file without any template format interpretation of said received data, and appending said second file to an end of said first file, and wherein both said first and second data files are created without interactive operator intervention; and, b) access means, coupled to said first and second data file, for providing electronic access to and use of said first and second data file by any authorized user or group of users.
Claim 9
Dependent Claim
34 words
The system according to claim 6 further including notification means coupled to said data file creating means, for notifying a particular user or group of users of said first and second data files created.
Claim 10
Dependent Claim
28 words
The system according to claim 6 wherein said access means includes browse means for allowing visual review of said received data in said first and second data files.
Claim 11
Dependent Claim
28 words
The system according to claim 6 wherein said access means includes modify means for allowing said received data in said first and second data files to be modified.
Claim 12
Dependent Claim
32 words
The system according to claim 6 wherein said access means includes reject means for allowing the rejection of all or part of said received data in said first and second data files.
Claim 13
Dependent Claim
32 words
The system according to claim 6 wherein said access means includes approval means for allowing the approval of all or part of said received data in said first and second data files.
Claim 14
Dependent Claim
27 words
The system according to claim 6 wherein said access means includes report means for allowing reporting of said received data in said first and second data files.
Claim 15
Independent Claim
266 words
A method of managing Electronic Data Interchange (EDI) between a sending trading partner and a receiving trading partner, comprising the steps of: a) receiving data from said sending trading partner, said received data containing, selectively, standard EDI structured data and non-standard EDI data, and said non-standard EDI data having a structure substantially similar to a standard EDI data structure, and said non-standard EDI data or an identifier associated with said non-standard EDI data being corrupted before being received; b) comparing said structure of said non-standard EDI data received to a library of standard EDI data structures, and identifying a standard EDI data structure in said library most similar to said structure of said received data; c) assigning to said received data a structure definition the same as said standard EDI data structure in said library compared to be most similar to said structure of said received data; d) creating a first data file having a predefined template format for managing any of said received data that conforms to said template format, said first file created from a merging of received data that conforms to said template format into data fields of said template format; and e) creating a second data file for managing any of said received data that does not conform to said template format, said second file created from a transfer of said data to said second file without any template format interpretation of said received data, and appending said second file to an end of said first file, and wherean both said first and second data files are created without interactive operator intervention.
Claim 16
Independent Claim
266 words
A method of managing Electronic Data Interchange (EDI) between a sending trading partner and a receiving trading partner, comprising the steps of: a) receiving data from said sending trading partner, said received data containing, selectively, standard EDI structured data and non-standard EDI data, and said non-standard EDI data having a structure substantially similar to a standard EDI data structure, and said non-standard EDI data or an identifier associated with said non-standard EDI data being corrupted before being received; b) comparing said structure of said non-standard EDI data received to a library of standard EDI data structures, and identifying a standard EDI data structure in said library most similar to said structure of said received data; c) assigning to said received data a structure definition the same as said standard EDI data structure in said library compared to be most similar to said structure of said received data; d) creating a first data file having a predefined template format for managing any of said received data that conforms to said template format, said first file created from a merging of received data that conforms to said template format into data fields of said template format; and e) creating a second data file for managing any of said received data that does not conform to said template format, said second file created from a transfer of said data to said second file without any template format interpretation of said received data, and appending said second file to an end of said first file, and wherean both said first and second data files are created without interactive operator intervention.
Claim 17
Dependent Claim
24 words
The method according to claim 13 further including notifying a particular user or group of users of said first and second data files created.
Claim 18
Dependent Claim
28 words
The method according to claim 13 further including providing access to and use of said first and second data files by any authorized user or group of users.