CA1323107C - Method and apparatus for electronic data interchange - Google Patents
Method and apparatus for electronic data interchangeInfo
- Publication number
- CA1323107C CA1323107C CA000615490A CA615490A CA1323107C CA 1323107 C CA1323107 C CA 1323107C CA 000615490 A CA000615490 A CA 000615490A CA 615490 A CA615490 A CA 615490A CA 1323107 C CA1323107 C CA 1323107C
- Authority
- CA
- Canada
- Prior art keywords
- data
- overlay
- dst
- format
- transaction
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Lifetime
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/103—Formatting, i.e. changing of presentation of documents
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/12—Use of codes for handling textual entities
- G06F40/151—Transformation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/12—Use of codes for handling textual entities
- G06F40/151—Transformation
- G06F40/157—Transformation using dictionaries or tables
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/166—Editing, e.g. inserting or deleting
- G06F40/186—Templates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
Abstract
METHOD AND APPARATUS FOR ELECTRONIC DATA INTERCHANGE
ABSTRACT OF THE DISCLOSURE
A programmable machine system and method for using same to perform electronic data interchange among a variety of trading partners. The machine is programmed so that it can define, enter and translate business transaction data in a variety of different dictionary-structured formats thereby providing the user with flexibility without requiring reprogramming of the machine.
ABSTRACT OF THE DISCLOSURE
A programmable machine system and method for using same to perform electronic data interchange among a variety of trading partners. The machine is programmed so that it can define, enter and translate business transaction data in a variety of different dictionary-structured formats thereby providing the user with flexibility without requiring reprogramming of the machine.
Description
BACKGROVND
1. Technical Field This invention relates to programmable machine systems, and more particularly, to methods and apparatus for defining the formats of business transactions for the purposes of entering, outputting, printing and translating data which normally will be transmitted and received among trading partners.
1. Technical Field This invention relates to programmable machine systems, and more particularly, to methods and apparatus for defining the formats of business transactions for the purposes of entering, outputting, printing and translating data which normally will be transmitted and received among trading partners.
2. Discussion .~ - ~
Traditionally, business transactions among trading partners: have been documented primarily on paper thereby : ~ ' ', ~, - .
resulting the self-evident problems associated with the storage and transmittal of a large number of physical documents. In an attempt to overcome these problems, the trend has been to use electronic data interchange (EDI) to transmit and receive various business transactions among trading partners. Examples of such transactions include Releases, Advance Ship Notices, Purchase Orders, Purchase Order Acknowledyements, Requests for Quotes, Quotes, Invoices and Bank Remittances. Thus, instead of documenting these transactions on paper~ the data are transmitted electronically (typically via a modem or digital data line connection) between computer systems operated by each trading partner.
There may or may not be involved a third party service to receive, store, and ~orward these electronic business transactions.
In order to permit the translation and use of documents exchanged between the computer systems, there must be established some type of standards for the definition of transactions. Such standards that have been implemented include ANSI ASC X12 (set up by the American National ~tandards Institute), EDIACT (Electronic Data Interchange for Administration, Commerce and Transport) and TDCC
(Transportation Data Coordinating Committee) formats. These ; formats utilize element, segment and transaction dictionaries.
; ~ These dictionaries are extremely flexible in that they have only a few mandatory requirements and a wide variety of ~ options. Thus, a particular trading partner can specifically : :
~, 1~23101 tailo~ a business transaction such as an Invoice to its own needs while still being within the standard format.
For purposes of this invention, the term "dictionary-defined" transaction format is a format which has been agreed upon by a standard's organization which may be comprised of a group of trading partners, agencies, countries, departments within an organization, etc. that use a three-tiered dictionary concept. The 3 tiers are as follows:
1) Tier 1 is the definition and identification of individual, unit data items known as elements.
Examples of~elements are date, date qualifiers, ~uantity, items number etc. An element consists of a datum having an assigned fixed data length or variable data length.
2) Tier 2 is the definition of records known as segments which are uniquely identified and consist of particular groupings of elements in a particular organization for the ultimate purpose of defining a part of a transaction.
Preferably, but not necessarily, the grouping of elements in a particular segment should have some logical relationship. Some elements may be required and others may be optional within a particular segment.
Traditionally, business transactions among trading partners: have been documented primarily on paper thereby : ~ ' ', ~, - .
resulting the self-evident problems associated with the storage and transmittal of a large number of physical documents. In an attempt to overcome these problems, the trend has been to use electronic data interchange (EDI) to transmit and receive various business transactions among trading partners. Examples of such transactions include Releases, Advance Ship Notices, Purchase Orders, Purchase Order Acknowledyements, Requests for Quotes, Quotes, Invoices and Bank Remittances. Thus, instead of documenting these transactions on paper~ the data are transmitted electronically (typically via a modem or digital data line connection) between computer systems operated by each trading partner.
There may or may not be involved a third party service to receive, store, and ~orward these electronic business transactions.
In order to permit the translation and use of documents exchanged between the computer systems, there must be established some type of standards for the definition of transactions. Such standards that have been implemented include ANSI ASC X12 (set up by the American National ~tandards Institute), EDIACT (Electronic Data Interchange for Administration, Commerce and Transport) and TDCC
(Transportation Data Coordinating Committee) formats. These ; formats utilize element, segment and transaction dictionaries.
; ~ These dictionaries are extremely flexible in that they have only a few mandatory requirements and a wide variety of ~ options. Thus, a particular trading partner can specifically : :
~, 1~23101 tailo~ a business transaction such as an Invoice to its own needs while still being within the standard format.
For purposes of this invention, the term "dictionary-defined" transaction format is a format which has been agreed upon by a standard's organization which may be comprised of a group of trading partners, agencies, countries, departments within an organization, etc. that use a three-tiered dictionary concept. The 3 tiers are as follows:
1) Tier 1 is the definition and identification of individual, unit data items known as elements.
Examples of~elements are date, date qualifiers, ~uantity, items number etc. An element consists of a datum having an assigned fixed data length or variable data length.
2) Tier 2 is the definition of records known as segments which are uniquely identified and consist of particular groupings of elements in a particular organization for the ultimate purpose of defining a part of a transaction.
Preferably, but not necessarily, the grouping of elements in a particular segment should have some logical relationship. Some elements may be required and others may be optional within a particular segment.
3) Tier 3 is the complete and full definition of transactions which are uniquely identified.
Transactions are defined in terms of their segments in a particular order. Some segments may be required and others may be optional in a particular transaction definition. Also, groups and subgroups of segments within a transaction may be further defined to indicate multiple repetitions or iterations of the group and/or subgroup (loops).
The flexibility provided by dictionary-defined transactions unfortunately also causes some real-world problems. In practice, larger trading partners are individually tailoring the information required in each of their transactions so that, while they do meet the 1 3 ~ 7 dictior,ary-defined format, the completed transacti~n formats chosen by each are quite different. Thus, if one tradiny partner wants to do business via EDI with a variety of other trading partners, at least one of the trading partners must be capable of configuring and utilizing its computer system so that it can meet all of the reyuirements dictated by thè other trading partners. For purposes of this invention, the term "dictionary-structured" transaction format is one that meets or approximates the guidelines of a dictionary~defined format but is individually tailored by a given trading partner.
Thus, a "dictionary-structured" transaction format may be the same as, may be different from, may deviate from, may be a subset of, or may be a superset of that format specified by the "dictionary-defined" format guidelines.
There are several software programs for use with electronic data exchange currently on the market. They include:
o EDI*PC Tm (General Electric Corporation; Rockville, MD) o TELINKTm (EDI, Inc.; Hanover, MD) o METRO * TranslatorTm (Metro.Mark Int~grated System, Inc.; Roslyn, NY) However, prior to the present invention, they are believed to have had the following drawbacks:
o They attempt to produce trading partner specific transactions through a combination of operator selective input with a generalized format covering multiple trading partners.
o They cannot produce exacting dictionary-structured transaction formats and "other part" formatting to ~3`~3~
the specific trading partner requirements as is done by the present invention.
SUMMARY OF THE INVENTION
The present invention enahles a trading partner to define the formats of a dictionary-structured business transaction which provide the basis for the subsequent entry and translation of business transaction data for transmission among a variety of other trading partners. All this can be -accomplished without requiring programming changes to the user's machine system.
The programmable machine system according to the preferred embodiment of the present invention includes an input means for defining a dictionary-structured transaction format that has a plurality of elements in a particular organization. Provision is made for selecting a particular system component such as a printer, screen or the like which is typically not well suited for using the dictionary-structured format to interface with a human operator. An overlay generator generates an overlay that includes a second format associated with the selected system component. The second format has elements or fields that are related to the ` elements in the dictlonary-structured format. The overlay generator also generates a mapping between the related elements of the two formats. Data that are entered in the second format are translated into the dictionary-structured format so that they can be later transmitted in that format to :
a trading partner. Also, data received in a :
.
. . . . .
d~ctionary-structured format from a trading partner can be translated into the second format.
BRIEF DESCRIPTION OF THE DRAWINGS
The various advantages to 1he present invention will become apparent to those skilled i.n the art upon readiny the following specification and by reference to the drawings in which:
Figure 1 is a schematic diagram illustrating programmable machine systems of two trading partners utilizing the present invention;
Figure 2 is a high level flowchart illustrating the major steps performed by the programmable machine system in carrying out certain aspects of the invention;
Figure 3 ~A-B) is a flowchart of how the system builds a particular overlay and mapping therefor;
Figure 4(A-C) is a pseudocode flow diagram of how an overlay is used programmatically for data entry and subsequent translation into a dictionary-structured transaction;
Figure 5(A-B) is a pseudocode flow diagram of how an overlay is used programmatically for translating : dictionary-structured transactions into formatted printed output;
Figure 6(A-B) is a pseudocode flow diagram of how an overlay is used programmatically for translating transactions from dictionary-structured formats into formats composed of fixed-field,~fixed-length records contained in a file;
~ 6 :~
.
~ 323 1 07 Figure 6(c ) is a pseudocode flow diagram of how an overlay is used programmatically for translating transactions from formats composed of fixed-field, fixed-length records contained in a file into dictionary-structured formats;
Figure 7 is a diagram showing the relationship among the three tiers (element, segment, transaction) of dictionary-defined transaction and dictionary-structured transactions;
Figure 8 is a submenu which shows how the overlay generator is accessed and how the three-tier dictionary of dictionary-defined transactions is accessed;
Figure 9 is the main menu which shows how data entry and file translation, which require overlays, are invoXed;
Figure lOA is a representation of a screen which is used to identify a data entry overlay;
Figure lOB is a representation of a screen which is used to add and delete segments used in an overlay;
Figure lOC is a representation of a screen which is used to define or change the attributes of a segment used in a particular overlay;
Figure lOD is a representation of a screen which is used to add and delete elemén~s used in a particular overlay;
Figures lOE and lOF are a representation of screens which are used to define or change the attributes of an element used in a particular overlay;
Figure lOG iS a representation of a screen which is used to define or change the overall data entry screen attributes :
' used ~y the Overlay Generator when it builds the data entry screen associated with a particular data entry overlay;
Figure loH is a representation of a screen which shows the actual physical appearance of a data entry screen;
Figure 11 is a pictorial representation of the types of overlays presently produced by th:is overlay generator;
Figure 12 is a matrix representation of the relationship of the elements in a data entry overlay to the coordinate position of their associated fields on a data entry screen;
and Figure 13 is a representation of the elements on a data entry overlay to their position in the transmission data stream in dictionary-structured format.
DESCRIPTION OF THE PREFERRED EMBODIMENT
Figure 1 illustrates a communication network for performing electronic data interchange between the programmable machine systems 10 and 12 of various trading partners. In order to simplify the description of the present invention and to provide a concise description of the best mode for practicing this invention, it will be described in connection with a specific example utilizing programmable machine system 12. Howe~er, it should be understood at the outset that this invention can be used by different computer equipment and implementsd in different software languages.
Assume that the machine system IO belongs to a large customer and that machine syst m 1~ belongs to a vendor of .
. ., .
I 323 1 ~7 that customer. The customer will often dictate the dicti~nary-structured transaction format that all of its vendors must use. One of its primary features is that the present invention permits the vendor's computer system to define, Pnter and translate business transaction data for transmission not only to just one customer but also to other customers which may and usually have dif~erent dictionary-structured transaction formak requirements.
The basic system con~iguration includes an IBM~
microcomputer such ~s an IBM~ XT, AT, PS/2 or any IBM~
compatible microcomputer that uses an MS-~OS operating syste~
and which can accommoda~e the boards and devices of the following system components. The processor 1~ communicates with a fixed hard disk 16 of 10 megabyte~ or more as well as with floppy disk drive(s) 18. A terminal including a keyboard and display screen 22 provides a user interface with input/o~tput capabilities. A printer ~4 with parallel interface is employed ~or providing hard copy. Finally, a modem 26 is u~ed to pr~vide bidirec~ional communication between processors of the various trading partners.
The processor 14 operates under the instructions of an application program which i~ typlcally contained on a hard disk and entered into ~he internal memory 28 of ~he processor in a conventional manner via disk drive 18. The application program of the specific embodiment of this invention was written in the COBOL language and compiled by a compiler commercially available under the trademark "Professional : 9 , ', ~ .
. ' ' , . .
3 ~ Q I
COBOL", supplied by Microfocus, 2463 E. Bashore R~ad, Palo Alto, California.
The application program contains various modules as illustrated in Figure 1. These modules are periodically loaded into the processor 14 depending upon which functions the user desires to perform as indicated by his comrnands entered into the keyboard 20. The present invention is particularly concerned with the module which will b~ referred to as the "Overlay Generator".
The overlay generator module is used for a variety of purposes. Figure 4(A-C) describes how an overlay is used to enter data via the keyboard 20 and later to translate it into a dictionary-structured transaction ready for transmission to a trading partner. Figure 5(A-B) describes how an overlay is used for translating dictionary-structured transaction data (e.g., received from a trading partner via modem 26) into formatted printed output for use on the printer 24. This capa~ility is useful for viewing or printing the transaction in a more user friendly format since the data, as received, are in a format that is not very understandable by ordinary human opexators. Figure 6(A-B) describes how an overlay is used to translate dictionary-structured transaction data into formats composed of fixed-field, fixed-length records contained in a file. This capability is useful for presenting the data ln a consistent, fixed format that can be more easily processed by other application programs. Figure 6(C
~' . ''. ~ '. :''' '' ' . ' "
~ : ........ :. . . - , . .
. ' ' . . ' " '' ' ' .,: ' ' . ' . ' : ' , ' ' ' d~scribes how fixed-field, fixed-length records contained in such a file can be translated into a dictionary-structured transaction format ready for transmission to a trading partner or for other purposes. The foregoing text will concentrate on describing how one particular overlay is generated and used for entering data which are stored on hard disk 16. Once the data are stored in a dictionary-structured format using the overlay, it can be used in a variety of manners as described in connection with Figures 5 and 6 above. In addition, it can be transmitted to the trading partner via modem 26. Likewise, transaction information recei~ed via modem 26 from a trading partner can be stored in hard disk 16, with the overlay generator module being capable of translating it into more user-friendly form such as mapping the data entries onto appropriate pixel positions or fields on display 22. Thus, while the foregoing description will focus in on a specific example, it should be understood that the present invention has a much broader applicability.
The hard disk 16 is used primarily for both storing computer application programs and records or files of data that can be accessed by the processor 14. The stored data include the dictionaries corresponding to the tier 1, tier 2 and tier 3 structure for a dictionary-deined transaction as discussed above. Figure 7 illustrates the conceptual relationship between the information in the transaction, segment and element dictionaries. The element dictionary, beirg the most basic, includes an identification code (e.g., , .
~1323107 354), a title ("e.g., "Number of I.ine Items"), data type (e.g., "N0"), and the minimum and maximum data field lengths (e.g., "1" and "4", respectively). The segment dictionary includes an identification code and one or more functionally related elements positioned in a defined sequence. The identification code CTT in Figure 7 thus de~ines a seyment utilizing element numbers 354, 347, etc. in that order. Also included is the designator (M or O) which indicates whether or not the element is required (mandatory) or optional in this segment. The transaction dictionary stored on disk 16 includes an identification code for each transaction (e.g., "850" denotes a Purchase Order transaction), and one or more functionally related segments in a defined sequence. Also included is a designator which indicates whether or not the segment is required (mandatory) or optional in this transaction. The transaction dictionary would contain both the mandatory and optional segments for each transaction.
In practice, a trading partner will decide what information it will require for particular transactions and typically provide each of its trading partners with a manual (implementation gulde) which sets forth the chosen dictionary-structured format. Thus, the first task is to appropriately ~configure the trading partner's system 12 so that it can accommodate the demands dictated by others for performing electronic data interchange therewith.
Upon starting up the system, the screen 22 will display the main menu set forth in Figure 9. By selecting the option ' ' :
, ' ' ' . ' .
~32~1~7 labeled "Maintain System and Security Files" the menu of Figure 8 will be displayed. Pursuant to the present invention, an overlay is first generated for each selected system component (also sometimes referred to as the "other part"). A system component can be any device (e.g. printer, screen, disk, etc.) where information is preferably communicated in a more desirable user~friendly or application-friendly format than the dictionary-structured format. In Figure 8, overlays can be generated by entering one of the options 6~through 9. Option 6 is associated with the display 22 and keyboard 20 for purposes of entering data.
Option 7 is associated with the printer 24 whereas options 8 and 9 enable other system components to provide certain desirable conversions of data listings.
A data entry overlay for subsequent use for data entry onto hard disk 16 via keyboard 20 and display 22 may be constructed so as to be very specific and to minimize keyboard input. This is accomplished by: selecting only the segments and elements required; using reserved words to call up data ~such as address) from other files and to define data edits;
designating element values as constants/ formulae, or defaults; changing the length of the element; changing the element name; and positioning the data field represented by that element on the display 22.
The first step in this process is to enter Option 6 (Figure 8) and proceed to define the overlay by entering an Overlay Code and a Transaction Type Code in the spaces , provided in the screen of Figure lOA. The Transaction Type Code typically is that of the corresponding dictionary-defined transaction. Examples of ANSI ASC X12 Transaction Type Codes are: Invoice = 810, P.O. = 850. The Overlay Code normally designates a particular tradiny partner. Thus, the screen of Figure 10A illustrates that a Purchase Order (for krading partner DUl) has been entered.
Segments are now added or deleted to each overlay using the manipulation capabilities of the Overlay Generatox module.
The screen format shown in Figure 10B is for a given Overlay (DUl:850~ which is accessed when a given transaction is defined and entered in the screen of Figure 10A. The software automatically fetches those mandatory segments from the stored dictionary for the given transaction and displays them on the screen. Then, the user is given the opportunity to modify this basic set of segments. The segments which make up the dictionary-structured transaction are identified by their Segment IDs in Figure 10B which are the same as those assigned to the corresponding dictionary-defined transaction.
The user can edit this screen as desired to select the segments, and "Occurs" and "Loops". Some segments are repeated multiple times at their specific location in the transaction. "Occurs'l refers to the maximum number of times a segment is permitted to appear at that location. Within transactions, specific groups of logically related segments occur repetitively. The repetition of a group is referred to as a "loop".
t~23~7 The attributes of each segment can be further modified to the exact requirements of the desired dictionary-structured transaction using the manipulation capabilities of the Overlay Generator using the screen format shown in Figure 10C by entering the appropriate line number in Figure 10B associated with the segment that is desired to be modified. These further attributes are as follows:
SEGMENT
NAME A field for the name of the particular segment.
REQUIREMENT
CODE O - Optional. The segment does not need to be used.
M = Mandatory. This segment must be used in the Transaction.
F = Floating.
MAXIMUM USE The maximum allowable number of times this segment may be used at this location in the transaction. The number enclosed in the parenthesis is the dictionary-defined number allowed for the maximum use but is not a limiting factor.
TYPICAL USE This is the number of times the elements in this segment are to appear as a table on the data entry screen. This field is only relevant if the "Maximum Use'l is greater than one, and all the elements will fit one line on a screen.
POSITION OF
SEGMENT THAT
ENDS LOOP If this segment is the first segment of a loop, this field indicates the last segment in the loop. If this segment does not start a loop, this value must be zero.
MAXIMUM
LOOPS If this segment is the first segment of a loop, this is the maximum number of times it can complete the loop. The number in this field must be zero if there is no loop.
HL LEVEL (Hierarchical Level) allows you to depict, ~lexibly, the relationships among HL segments.
T~is field shows, relatively, where this HL
falls in relationship to others defined. For e~ample,~ the Shipment HL may be designated :::
::
:
, 1 :~23 1 Q7 level 171", the Order HL may be designated le~el "3", and the Item ~IL may be designated "6".
The fields labeled "SEGMENT POSITION" refers to the ordinal position that the segment being defined holds within this rendition of this transaction. The field labeled IISEGMENT
CODE" refers to the segment ID, the 2-to-3 characters which identifies the segment.
The elements within each segment now can be added or deleted using the manipulation capabilities of the Overlay Generator usiny the screen format shown in Figurs lOD. The elements for each segment which make up the dictionary-structured transaction are identified by their relative position within segment. (Note that elements 4 ~ 5 have been deleted in the previous step) The attributes of each element can be modified to the exact requirements of the desired dictionary-structured transaction using the screen format shown in Figure lOE which is accessed by entering the appropriate sequence number in Figure lOD. As with the segments, the fields labeled "ELEMENT
POSITION" and "ELEMENT CODE" refer to each element's position within that segment and its dictionary-defined code. The modifiable attributes are as follows:
LEMENT CODE This is the code of the element that belongs in this sequential position of the segment being defined.
DESCRIPTION Free-Form Description.
DATA TYPE Defines the type of data the element must contain. Codes are:
AN Alphanumeric ID Identifier (Must be specific code as defined by ANSI) .
132;~1~7 NN Fixed Decimal Mumeric DT Date TM Time (24 hour clock HHMM format) R Floating Decimal Point Numeric REQUIREMENT
CODE Mandatory, optional, or conditional.
MINIMUM
LENGTH Minimum number of characters the element must contain. If the Element Type is "N" or "R", this count does not include the sign or decimal point.
MAXIMUM
LENGTH Maximum number of characters the element can contain. If the E:Lement Type is "N" or "R", this count does not include the sign or decimal point.
DEFAULT
CODE BLANK "Default Value" is not used.
D Default. When the data entry screen is used, the contents of the "Default Value" field will be displayed to be accepted or overr.idden.
C Constant. The element and its related value will not be displayed on the data entry screen. When the data are transmitted, this element will be sent with whatever information is indicated in the "Default Value"
field. If the Requirement Code is "CF" or "CP", this element will be transmitted only if the paired element (the following element if "CF" and previous element if "CP") exists.
F Formula. Use the formula in the field "Default Value". This element will not appear on the data entry screen.
HEADINGS Vp to three lines of title for this element.
This is how ~he element will be labeled on the data entry screen.
DASHES A Y or N switch to indicate whether to display a line of dashes between the title lines and the data for this element.
~3~3107 The user uses the manipulative capabilities until all of the element attributes have been defined as desired. It should be appreciated that the present invention enables the user to precisely define what information is yoing to be included in a particular transaction. Unlike prior art approaches which "hard code" a set format for one particular trading partner or a group of trading partners, the present invention permits a user to define a unique transaction format for one or more trading partners, store it, and then use the same equipment without further program modifications to define a totally different transaction format for a different trading partner. Once a transaction format has been defined in accordance with the process just described, the user exits back through to the screen in Figure 10B.
In addition to setting these very specific parameters already mentioned, the user can set some overall transaction parameters for doing the mapping to the data entry screen. To this end, the screen of Figure 10G is accessed by the user by entering Option "T" in the screen of Figure 10B. The screen of Figure 10G contains various fields where the user can enter information to build default attributes of the data entry screen. These attributes are outlined as follows:
OLUMN WIDTH This ~ield can set up the data entry screen in columns. Each element placed on the screen will start in a position that is an even increment of the "Column Width". ~or example, if the "Column Width" is 10, then the elements on the data entr~ screen will start on positions:
10,20,30,40,50,....only. Most typically this is set to 1 to allow mapping in any area of the screen.
MINIMUM GAP
BETWEEN
FIELDS This sets the minimum number of spaces between each element on a data entry screen.
REVERSE VIDEO
ON ENTRY
~Y/N) y = When an element is filled in on the data entry screen, it will have a white background and the characters will he black.
N = Black background with white characters.
DEFAULT
LINE
SPACING Number of blank lines between an element and the first heading of the next element down.
MANDATORY
FIELD
CHARACTER The character that will appear just before a keyed area on a data entry screen when both the segment and the element are mandatory. (This field may be left blank).
DASHES (Y/N) Dashes are dotted lines just under a heading.
The dashes indicate the maximum size of the element.
Y = The dashes will appear.
N = The dashes will not appear. Dashes are not necessary for data entry if you are using reverse video which also shows field size.
CONTINUATION
CHARACTER If a segment has a typical use of 2 or more and the entire segm~nt will fit on one line of the screen, a table will be generated on the screen for the element in this segment. The Continuation Character will appear before the first element in each row of the table after the first row. The character that is to be displayed, to denote multiple tabl~ entries of the same data ~without replacing the heading).
OVERLAY
DESCRIPTION ~his is where identification of the trading partner and transaction are assigned to the overlay~
Exiting from scr~een 10G to screen 10B again, the next step is to select the "B" (build) option to have the system . , .
13~31~7 complece the first attempt at mapping of the dictionary-structured data to the (in this case) daka entry screen. Exiting from this screen (lOB) now brings up a manipulation screen like that shown in lOH.
Figure lOH shows the actua:L, physical appearance of a data entry screen and the software allowed spatial adjustment of displayed fields and titles for the data field of each element designated to receive keyed input. If further tailoring of the display screen is desired, the user can use this screen (lOH) to~physically move the displayed fields to other areas of the screen thereby changing the mapping or can bring up any of the previously described screens to make additions, deletions, or title changes.
After a field on the data entry screen is repositioned, the overlay generator module adjusts the formatting of the data entry screen and the mapping between the data entry fields and the elements in the dictionary-structured format.
At this point in time the transaction format information is stored in a file on hard disk 16. This file contains a series of elements in the appropriate order for that transaction format. The file also contains identification information for each element, its position and its length. The file also contains a coordinate which is associated with the related field in the other system component or "other part" which will be described. A simplified representation of the overlay file is set forth in Figure 11 where overlays for three different transactions are pictorially represented. The overlay for transaction format DU1:850 consists of ordered segments BEG, Nl, etc. and their associated ele~ents. The elements are in the specified order and each element has the following information: its dictionary-defined identification code, its position within the segment, its field length, and its mapping coordinates. For example, the third element in the segment BEG is code number 324 and the adjacent identifier (03) signifies that it is the third position in that segment. A
typical number for its length would be 10. The mapping coordinate (X5, Y2) ~efines where the field for that element appears on the data entry screen. The definition of the location for each field is discussed in connection with "building" the screen. The overlay generator module operates in a similar manner to generate the other overlays pictorially represented in Figure 11.
Assume that during the screen building process, the user located the fields in the character positions shown in Figure 12 which represents a simplified data entry screen. The overlay generator, during the mapping process, would locate the character position of the first element in the transaction format file and insert those mapping coordinates (X5, Y2) in the appropriate field in the data entry overlay. The other elements likewise contain their respective mapping coordinates. If the user decides to rebuild a new screen, the elements in the transaction format file remain in their same order but the mapping coordinates will change to correspond to their new location on the screen. The overlays for the other ~ '' .
~23~Q7 system components (e.y., printer) are arranged in similar fashion but contain mapping coordinates which are associated with that particular device. The flow chart of Figure 3 describes in more detail how the machine system huilds the data entry overlay.
Figure 4 describes in detail how this overlay can now be used to enter and translate data for transmission to a trading partner. Briefly, data (e.g., price) associated with a given element (e.g., E212~ are entered into the related ~ields on screen 22 by the user via keyboard 20. The entered data and the element mapping coordinate are stored in an intermediate file. The data are each associated with a mappiny coordinate for each associated element. Before it is time to actually transmit the data, a software module instructs the CPU 14 to read each element from the pertinent overlay, along with its associated mapping coordinate. Software uses this mapping coordinate as a pointer to the intermediate file where is fetches the data having a corresponding mapping coordinate.
Thus, data D2 would be placed in the sixth position since it is associated with the sixth element E323 of the dictionary-structured format. This reordering sequence continues until the data are all arranged in the appropriate sequence. Then, they can be transmitted to the trading partners in dictionary-structured format.
In view of the foregoing, it should be appreciated that the present invention provides the user with a tremendous amount of flexibility without requiring a change in the software. Thus, it is not necessary to rewrite the software every time a new trading partner dictates a different dictionary-structured transacti.on format. Various other advantages of the present invention will become apparent to those skilled in the art after having the benefit ~f a study of the specification, drawings, ~nd following claim~.
.
' ~ ~ ,
Transactions are defined in terms of their segments in a particular order. Some segments may be required and others may be optional in a particular transaction definition. Also, groups and subgroups of segments within a transaction may be further defined to indicate multiple repetitions or iterations of the group and/or subgroup (loops).
The flexibility provided by dictionary-defined transactions unfortunately also causes some real-world problems. In practice, larger trading partners are individually tailoring the information required in each of their transactions so that, while they do meet the 1 3 ~ 7 dictior,ary-defined format, the completed transacti~n formats chosen by each are quite different. Thus, if one tradiny partner wants to do business via EDI with a variety of other trading partners, at least one of the trading partners must be capable of configuring and utilizing its computer system so that it can meet all of the reyuirements dictated by thè other trading partners. For purposes of this invention, the term "dictionary-structured" transaction format is one that meets or approximates the guidelines of a dictionary~defined format but is individually tailored by a given trading partner.
Thus, a "dictionary-structured" transaction format may be the same as, may be different from, may deviate from, may be a subset of, or may be a superset of that format specified by the "dictionary-defined" format guidelines.
There are several software programs for use with electronic data exchange currently on the market. They include:
o EDI*PC Tm (General Electric Corporation; Rockville, MD) o TELINKTm (EDI, Inc.; Hanover, MD) o METRO * TranslatorTm (Metro.Mark Int~grated System, Inc.; Roslyn, NY) However, prior to the present invention, they are believed to have had the following drawbacks:
o They attempt to produce trading partner specific transactions through a combination of operator selective input with a generalized format covering multiple trading partners.
o They cannot produce exacting dictionary-structured transaction formats and "other part" formatting to ~3`~3~
the specific trading partner requirements as is done by the present invention.
SUMMARY OF THE INVENTION
The present invention enahles a trading partner to define the formats of a dictionary-structured business transaction which provide the basis for the subsequent entry and translation of business transaction data for transmission among a variety of other trading partners. All this can be -accomplished without requiring programming changes to the user's machine system.
The programmable machine system according to the preferred embodiment of the present invention includes an input means for defining a dictionary-structured transaction format that has a plurality of elements in a particular organization. Provision is made for selecting a particular system component such as a printer, screen or the like which is typically not well suited for using the dictionary-structured format to interface with a human operator. An overlay generator generates an overlay that includes a second format associated with the selected system component. The second format has elements or fields that are related to the ` elements in the dictlonary-structured format. The overlay generator also generates a mapping between the related elements of the two formats. Data that are entered in the second format are translated into the dictionary-structured format so that they can be later transmitted in that format to :
a trading partner. Also, data received in a :
.
. . . . .
d~ctionary-structured format from a trading partner can be translated into the second format.
BRIEF DESCRIPTION OF THE DRAWINGS
The various advantages to 1he present invention will become apparent to those skilled i.n the art upon readiny the following specification and by reference to the drawings in which:
Figure 1 is a schematic diagram illustrating programmable machine systems of two trading partners utilizing the present invention;
Figure 2 is a high level flowchart illustrating the major steps performed by the programmable machine system in carrying out certain aspects of the invention;
Figure 3 ~A-B) is a flowchart of how the system builds a particular overlay and mapping therefor;
Figure 4(A-C) is a pseudocode flow diagram of how an overlay is used programmatically for data entry and subsequent translation into a dictionary-structured transaction;
Figure 5(A-B) is a pseudocode flow diagram of how an overlay is used programmatically for translating : dictionary-structured transactions into formatted printed output;
Figure 6(A-B) is a pseudocode flow diagram of how an overlay is used programmatically for translating transactions from dictionary-structured formats into formats composed of fixed-field,~fixed-length records contained in a file;
~ 6 :~
.
~ 323 1 07 Figure 6(c ) is a pseudocode flow diagram of how an overlay is used programmatically for translating transactions from formats composed of fixed-field, fixed-length records contained in a file into dictionary-structured formats;
Figure 7 is a diagram showing the relationship among the three tiers (element, segment, transaction) of dictionary-defined transaction and dictionary-structured transactions;
Figure 8 is a submenu which shows how the overlay generator is accessed and how the three-tier dictionary of dictionary-defined transactions is accessed;
Figure 9 is the main menu which shows how data entry and file translation, which require overlays, are invoXed;
Figure lOA is a representation of a screen which is used to identify a data entry overlay;
Figure lOB is a representation of a screen which is used to add and delete segments used in an overlay;
Figure lOC is a representation of a screen which is used to define or change the attributes of a segment used in a particular overlay;
Figure lOD is a representation of a screen which is used to add and delete elemén~s used in a particular overlay;
Figures lOE and lOF are a representation of screens which are used to define or change the attributes of an element used in a particular overlay;
Figure lOG iS a representation of a screen which is used to define or change the overall data entry screen attributes :
' used ~y the Overlay Generator when it builds the data entry screen associated with a particular data entry overlay;
Figure loH is a representation of a screen which shows the actual physical appearance of a data entry screen;
Figure 11 is a pictorial representation of the types of overlays presently produced by th:is overlay generator;
Figure 12 is a matrix representation of the relationship of the elements in a data entry overlay to the coordinate position of their associated fields on a data entry screen;
and Figure 13 is a representation of the elements on a data entry overlay to their position in the transmission data stream in dictionary-structured format.
DESCRIPTION OF THE PREFERRED EMBODIMENT
Figure 1 illustrates a communication network for performing electronic data interchange between the programmable machine systems 10 and 12 of various trading partners. In order to simplify the description of the present invention and to provide a concise description of the best mode for practicing this invention, it will be described in connection with a specific example utilizing programmable machine system 12. Howe~er, it should be understood at the outset that this invention can be used by different computer equipment and implementsd in different software languages.
Assume that the machine system IO belongs to a large customer and that machine syst m 1~ belongs to a vendor of .
. ., .
I 323 1 ~7 that customer. The customer will often dictate the dicti~nary-structured transaction format that all of its vendors must use. One of its primary features is that the present invention permits the vendor's computer system to define, Pnter and translate business transaction data for transmission not only to just one customer but also to other customers which may and usually have dif~erent dictionary-structured transaction formak requirements.
The basic system con~iguration includes an IBM~
microcomputer such ~s an IBM~ XT, AT, PS/2 or any IBM~
compatible microcomputer that uses an MS-~OS operating syste~
and which can accommoda~e the boards and devices of the following system components. The processor 1~ communicates with a fixed hard disk 16 of 10 megabyte~ or more as well as with floppy disk drive(s) 18. A terminal including a keyboard and display screen 22 provides a user interface with input/o~tput capabilities. A printer ~4 with parallel interface is employed ~or providing hard copy. Finally, a modem 26 is u~ed to pr~vide bidirec~ional communication between processors of the various trading partners.
The processor 14 operates under the instructions of an application program which i~ typlcally contained on a hard disk and entered into ~he internal memory 28 of ~he processor in a conventional manner via disk drive 18. The application program of the specific embodiment of this invention was written in the COBOL language and compiled by a compiler commercially available under the trademark "Professional : 9 , ', ~ .
. ' ' , . .
3 ~ Q I
COBOL", supplied by Microfocus, 2463 E. Bashore R~ad, Palo Alto, California.
The application program contains various modules as illustrated in Figure 1. These modules are periodically loaded into the processor 14 depending upon which functions the user desires to perform as indicated by his comrnands entered into the keyboard 20. The present invention is particularly concerned with the module which will b~ referred to as the "Overlay Generator".
The overlay generator module is used for a variety of purposes. Figure 4(A-C) describes how an overlay is used to enter data via the keyboard 20 and later to translate it into a dictionary-structured transaction ready for transmission to a trading partner. Figure 5(A-B) describes how an overlay is used for translating dictionary-structured transaction data (e.g., received from a trading partner via modem 26) into formatted printed output for use on the printer 24. This capa~ility is useful for viewing or printing the transaction in a more user friendly format since the data, as received, are in a format that is not very understandable by ordinary human opexators. Figure 6(A-B) describes how an overlay is used to translate dictionary-structured transaction data into formats composed of fixed-field, fixed-length records contained in a file. This capability is useful for presenting the data ln a consistent, fixed format that can be more easily processed by other application programs. Figure 6(C
~' . ''. ~ '. :''' '' ' . ' "
~ : ........ :. . . - , . .
. ' ' . . ' " '' ' ' .,: ' ' . ' . ' : ' , ' ' ' d~scribes how fixed-field, fixed-length records contained in such a file can be translated into a dictionary-structured transaction format ready for transmission to a trading partner or for other purposes. The foregoing text will concentrate on describing how one particular overlay is generated and used for entering data which are stored on hard disk 16. Once the data are stored in a dictionary-structured format using the overlay, it can be used in a variety of manners as described in connection with Figures 5 and 6 above. In addition, it can be transmitted to the trading partner via modem 26. Likewise, transaction information recei~ed via modem 26 from a trading partner can be stored in hard disk 16, with the overlay generator module being capable of translating it into more user-friendly form such as mapping the data entries onto appropriate pixel positions or fields on display 22. Thus, while the foregoing description will focus in on a specific example, it should be understood that the present invention has a much broader applicability.
The hard disk 16 is used primarily for both storing computer application programs and records or files of data that can be accessed by the processor 14. The stored data include the dictionaries corresponding to the tier 1, tier 2 and tier 3 structure for a dictionary-deined transaction as discussed above. Figure 7 illustrates the conceptual relationship between the information in the transaction, segment and element dictionaries. The element dictionary, beirg the most basic, includes an identification code (e.g., , .
~1323107 354), a title ("e.g., "Number of I.ine Items"), data type (e.g., "N0"), and the minimum and maximum data field lengths (e.g., "1" and "4", respectively). The segment dictionary includes an identification code and one or more functionally related elements positioned in a defined sequence. The identification code CTT in Figure 7 thus de~ines a seyment utilizing element numbers 354, 347, etc. in that order. Also included is the designator (M or O) which indicates whether or not the element is required (mandatory) or optional in this segment. The transaction dictionary stored on disk 16 includes an identification code for each transaction (e.g., "850" denotes a Purchase Order transaction), and one or more functionally related segments in a defined sequence. Also included is a designator which indicates whether or not the segment is required (mandatory) or optional in this transaction. The transaction dictionary would contain both the mandatory and optional segments for each transaction.
In practice, a trading partner will decide what information it will require for particular transactions and typically provide each of its trading partners with a manual (implementation gulde) which sets forth the chosen dictionary-structured format. Thus, the first task is to appropriately ~configure the trading partner's system 12 so that it can accommodate the demands dictated by others for performing electronic data interchange therewith.
Upon starting up the system, the screen 22 will display the main menu set forth in Figure 9. By selecting the option ' ' :
, ' ' ' . ' .
~32~1~7 labeled "Maintain System and Security Files" the menu of Figure 8 will be displayed. Pursuant to the present invention, an overlay is first generated for each selected system component (also sometimes referred to as the "other part"). A system component can be any device (e.g. printer, screen, disk, etc.) where information is preferably communicated in a more desirable user~friendly or application-friendly format than the dictionary-structured format. In Figure 8, overlays can be generated by entering one of the options 6~through 9. Option 6 is associated with the display 22 and keyboard 20 for purposes of entering data.
Option 7 is associated with the printer 24 whereas options 8 and 9 enable other system components to provide certain desirable conversions of data listings.
A data entry overlay for subsequent use for data entry onto hard disk 16 via keyboard 20 and display 22 may be constructed so as to be very specific and to minimize keyboard input. This is accomplished by: selecting only the segments and elements required; using reserved words to call up data ~such as address) from other files and to define data edits;
designating element values as constants/ formulae, or defaults; changing the length of the element; changing the element name; and positioning the data field represented by that element on the display 22.
The first step in this process is to enter Option 6 (Figure 8) and proceed to define the overlay by entering an Overlay Code and a Transaction Type Code in the spaces , provided in the screen of Figure lOA. The Transaction Type Code typically is that of the corresponding dictionary-defined transaction. Examples of ANSI ASC X12 Transaction Type Codes are: Invoice = 810, P.O. = 850. The Overlay Code normally designates a particular tradiny partner. Thus, the screen of Figure 10A illustrates that a Purchase Order (for krading partner DUl) has been entered.
Segments are now added or deleted to each overlay using the manipulation capabilities of the Overlay Generatox module.
The screen format shown in Figure 10B is for a given Overlay (DUl:850~ which is accessed when a given transaction is defined and entered in the screen of Figure 10A. The software automatically fetches those mandatory segments from the stored dictionary for the given transaction and displays them on the screen. Then, the user is given the opportunity to modify this basic set of segments. The segments which make up the dictionary-structured transaction are identified by their Segment IDs in Figure 10B which are the same as those assigned to the corresponding dictionary-defined transaction.
The user can edit this screen as desired to select the segments, and "Occurs" and "Loops". Some segments are repeated multiple times at their specific location in the transaction. "Occurs'l refers to the maximum number of times a segment is permitted to appear at that location. Within transactions, specific groups of logically related segments occur repetitively. The repetition of a group is referred to as a "loop".
t~23~7 The attributes of each segment can be further modified to the exact requirements of the desired dictionary-structured transaction using the manipulation capabilities of the Overlay Generator using the screen format shown in Figure 10C by entering the appropriate line number in Figure 10B associated with the segment that is desired to be modified. These further attributes are as follows:
SEGMENT
NAME A field for the name of the particular segment.
REQUIREMENT
CODE O - Optional. The segment does not need to be used.
M = Mandatory. This segment must be used in the Transaction.
F = Floating.
MAXIMUM USE The maximum allowable number of times this segment may be used at this location in the transaction. The number enclosed in the parenthesis is the dictionary-defined number allowed for the maximum use but is not a limiting factor.
TYPICAL USE This is the number of times the elements in this segment are to appear as a table on the data entry screen. This field is only relevant if the "Maximum Use'l is greater than one, and all the elements will fit one line on a screen.
POSITION OF
SEGMENT THAT
ENDS LOOP If this segment is the first segment of a loop, this field indicates the last segment in the loop. If this segment does not start a loop, this value must be zero.
MAXIMUM
LOOPS If this segment is the first segment of a loop, this is the maximum number of times it can complete the loop. The number in this field must be zero if there is no loop.
HL LEVEL (Hierarchical Level) allows you to depict, ~lexibly, the relationships among HL segments.
T~is field shows, relatively, where this HL
falls in relationship to others defined. For e~ample,~ the Shipment HL may be designated :::
::
:
, 1 :~23 1 Q7 level 171", the Order HL may be designated le~el "3", and the Item ~IL may be designated "6".
The fields labeled "SEGMENT POSITION" refers to the ordinal position that the segment being defined holds within this rendition of this transaction. The field labeled IISEGMENT
CODE" refers to the segment ID, the 2-to-3 characters which identifies the segment.
The elements within each segment now can be added or deleted using the manipulation capabilities of the Overlay Generator usiny the screen format shown in Figurs lOD. The elements for each segment which make up the dictionary-structured transaction are identified by their relative position within segment. (Note that elements 4 ~ 5 have been deleted in the previous step) The attributes of each element can be modified to the exact requirements of the desired dictionary-structured transaction using the screen format shown in Figure lOE which is accessed by entering the appropriate sequence number in Figure lOD. As with the segments, the fields labeled "ELEMENT
POSITION" and "ELEMENT CODE" refer to each element's position within that segment and its dictionary-defined code. The modifiable attributes are as follows:
LEMENT CODE This is the code of the element that belongs in this sequential position of the segment being defined.
DESCRIPTION Free-Form Description.
DATA TYPE Defines the type of data the element must contain. Codes are:
AN Alphanumeric ID Identifier (Must be specific code as defined by ANSI) .
132;~1~7 NN Fixed Decimal Mumeric DT Date TM Time (24 hour clock HHMM format) R Floating Decimal Point Numeric REQUIREMENT
CODE Mandatory, optional, or conditional.
MINIMUM
LENGTH Minimum number of characters the element must contain. If the Element Type is "N" or "R", this count does not include the sign or decimal point.
MAXIMUM
LENGTH Maximum number of characters the element can contain. If the E:Lement Type is "N" or "R", this count does not include the sign or decimal point.
DEFAULT
CODE BLANK "Default Value" is not used.
D Default. When the data entry screen is used, the contents of the "Default Value" field will be displayed to be accepted or overr.idden.
C Constant. The element and its related value will not be displayed on the data entry screen. When the data are transmitted, this element will be sent with whatever information is indicated in the "Default Value"
field. If the Requirement Code is "CF" or "CP", this element will be transmitted only if the paired element (the following element if "CF" and previous element if "CP") exists.
F Formula. Use the formula in the field "Default Value". This element will not appear on the data entry screen.
HEADINGS Vp to three lines of title for this element.
This is how ~he element will be labeled on the data entry screen.
DASHES A Y or N switch to indicate whether to display a line of dashes between the title lines and the data for this element.
~3~3107 The user uses the manipulative capabilities until all of the element attributes have been defined as desired. It should be appreciated that the present invention enables the user to precisely define what information is yoing to be included in a particular transaction. Unlike prior art approaches which "hard code" a set format for one particular trading partner or a group of trading partners, the present invention permits a user to define a unique transaction format for one or more trading partners, store it, and then use the same equipment without further program modifications to define a totally different transaction format for a different trading partner. Once a transaction format has been defined in accordance with the process just described, the user exits back through to the screen in Figure 10B.
In addition to setting these very specific parameters already mentioned, the user can set some overall transaction parameters for doing the mapping to the data entry screen. To this end, the screen of Figure 10G is accessed by the user by entering Option "T" in the screen of Figure 10B. The screen of Figure 10G contains various fields where the user can enter information to build default attributes of the data entry screen. These attributes are outlined as follows:
OLUMN WIDTH This ~ield can set up the data entry screen in columns. Each element placed on the screen will start in a position that is an even increment of the "Column Width". ~or example, if the "Column Width" is 10, then the elements on the data entr~ screen will start on positions:
10,20,30,40,50,....only. Most typically this is set to 1 to allow mapping in any area of the screen.
MINIMUM GAP
BETWEEN
FIELDS This sets the minimum number of spaces between each element on a data entry screen.
REVERSE VIDEO
ON ENTRY
~Y/N) y = When an element is filled in on the data entry screen, it will have a white background and the characters will he black.
N = Black background with white characters.
DEFAULT
LINE
SPACING Number of blank lines between an element and the first heading of the next element down.
MANDATORY
FIELD
CHARACTER The character that will appear just before a keyed area on a data entry screen when both the segment and the element are mandatory. (This field may be left blank).
DASHES (Y/N) Dashes are dotted lines just under a heading.
The dashes indicate the maximum size of the element.
Y = The dashes will appear.
N = The dashes will not appear. Dashes are not necessary for data entry if you are using reverse video which also shows field size.
CONTINUATION
CHARACTER If a segment has a typical use of 2 or more and the entire segm~nt will fit on one line of the screen, a table will be generated on the screen for the element in this segment. The Continuation Character will appear before the first element in each row of the table after the first row. The character that is to be displayed, to denote multiple tabl~ entries of the same data ~without replacing the heading).
OVERLAY
DESCRIPTION ~his is where identification of the trading partner and transaction are assigned to the overlay~
Exiting from scr~een 10G to screen 10B again, the next step is to select the "B" (build) option to have the system . , .
13~31~7 complece the first attempt at mapping of the dictionary-structured data to the (in this case) daka entry screen. Exiting from this screen (lOB) now brings up a manipulation screen like that shown in lOH.
Figure lOH shows the actua:L, physical appearance of a data entry screen and the software allowed spatial adjustment of displayed fields and titles for the data field of each element designated to receive keyed input. If further tailoring of the display screen is desired, the user can use this screen (lOH) to~physically move the displayed fields to other areas of the screen thereby changing the mapping or can bring up any of the previously described screens to make additions, deletions, or title changes.
After a field on the data entry screen is repositioned, the overlay generator module adjusts the formatting of the data entry screen and the mapping between the data entry fields and the elements in the dictionary-structured format.
At this point in time the transaction format information is stored in a file on hard disk 16. This file contains a series of elements in the appropriate order for that transaction format. The file also contains identification information for each element, its position and its length. The file also contains a coordinate which is associated with the related field in the other system component or "other part" which will be described. A simplified representation of the overlay file is set forth in Figure 11 where overlays for three different transactions are pictorially represented. The overlay for transaction format DU1:850 consists of ordered segments BEG, Nl, etc. and their associated ele~ents. The elements are in the specified order and each element has the following information: its dictionary-defined identification code, its position within the segment, its field length, and its mapping coordinates. For example, the third element in the segment BEG is code number 324 and the adjacent identifier (03) signifies that it is the third position in that segment. A
typical number for its length would be 10. The mapping coordinate (X5, Y2) ~efines where the field for that element appears on the data entry screen. The definition of the location for each field is discussed in connection with "building" the screen. The overlay generator module operates in a similar manner to generate the other overlays pictorially represented in Figure 11.
Assume that during the screen building process, the user located the fields in the character positions shown in Figure 12 which represents a simplified data entry screen. The overlay generator, during the mapping process, would locate the character position of the first element in the transaction format file and insert those mapping coordinates (X5, Y2) in the appropriate field in the data entry overlay. The other elements likewise contain their respective mapping coordinates. If the user decides to rebuild a new screen, the elements in the transaction format file remain in their same order but the mapping coordinates will change to correspond to their new location on the screen. The overlays for the other ~ '' .
~23~Q7 system components (e.y., printer) are arranged in similar fashion but contain mapping coordinates which are associated with that particular device. The flow chart of Figure 3 describes in more detail how the machine system huilds the data entry overlay.
Figure 4 describes in detail how this overlay can now be used to enter and translate data for transmission to a trading partner. Briefly, data (e.g., price) associated with a given element (e.g., E212~ are entered into the related ~ields on screen 22 by the user via keyboard 20. The entered data and the element mapping coordinate are stored in an intermediate file. The data are each associated with a mappiny coordinate for each associated element. Before it is time to actually transmit the data, a software module instructs the CPU 14 to read each element from the pertinent overlay, along with its associated mapping coordinate. Software uses this mapping coordinate as a pointer to the intermediate file where is fetches the data having a corresponding mapping coordinate.
Thus, data D2 would be placed in the sixth position since it is associated with the sixth element E323 of the dictionary-structured format. This reordering sequence continues until the data are all arranged in the appropriate sequence. Then, they can be transmitted to the trading partners in dictionary-structured format.
In view of the foregoing, it should be appreciated that the present invention provides the user with a tremendous amount of flexibility without requiring a change in the software. Thus, it is not necessary to rewrite the software every time a new trading partner dictates a different dictionary-structured transacti.on format. Various other advantages of the present invention will become apparent to those skilled in the art after having the benefit ~f a study of the specification, drawings, ~nd following claim~.
.
' ~ ~ ,
Claims (48)
1. A programmable machine system for operating on business transaction data in different dictionary-structured transaction formats, said machine system including a plurality of components including a keyboard, screen, processor, and memory, said machine system comprising:
first means for defining an overlay for each dictionary-structured format, each overlay having an ordered sequence of elements and mapping coordinates of given elements to related fields of a given system component;
second means, using a selected overlay, for translating the data in the dictionary-structured format into a different format for use on the selected system component;
and whereby the same programmable machine can operate on different dictionary-structured transaction formats without software modification.
first means for defining an overlay for each dictionary-structured format, each overlay having an ordered sequence of elements and mapping coordinates of given elements to related fields of a given system component;
second means, using a selected overlay, for translating the data in the dictionary-structured format into a different format for use on the selected system component;
and whereby the same programmable machine can operate on different dictionary-structured transaction formats without software modification.
2. The system of Claim 1 wherein said memory contains information associated with segments and elements of a given transaction, and wherein said first means comprises:
means for displaying on the screen those segments that are mandatory for a given transaction;
means, accessible to the user, for modifying the number, order and attributes of the segments and elements for a given transaction;
means for selecting a given system component having a plurality of fields, some of which are associated with certain elements;
means for tailoring the system component by moving the fields to different locations within the system component;
and wherein said programmable machine automatically updates the mapping coordinates of the elements associated with the moved fields.
means for displaying on the screen those segments that are mandatory for a given transaction;
means, accessible to the user, for modifying the number, order and attributes of the segments and elements for a given transaction;
means for selecting a given system component having a plurality of fields, some of which are associated with certain elements;
means for tailoring the system component by moving the fields to different locations within the system component;
and wherein said programmable machine automatically updates the mapping coordinates of the elements associated with the moved fields.
3. The system of Claim 2 wherein said system component is a data entry screen and wherein said machine further comprises:
means for placing data entered onto the screen through the keyboard into the appropriate ordered position for its associated element in the dictionary-structured transaction format.
means for placing data entered onto the screen through the keyboard into the appropriate ordered position for its associated element in the dictionary-structured transaction format.
4. The system of Claim 3 which further comprises means for transmitting the translated data in the dictionary-structured transaction format to a trading partner.
5. A programmable machine system having a plurality of components for defining, entering, and translating business transaction data for transmitting said data among a variety of trading partners, said system comprising:
a) input means for defining a dictionary-structured transaction format having a plurality of elements in a particular organization;
b) selector means for selecting a given system component;
c) overlay generator means cooperating with the input means and selector means for generating an overlay associated with the selected system component, said overlay being used to define a second format having positionable parts in the system component that are related to the elements in the dictionary-structured transaction format, the overlay also containing a mapping between the location of such parts in the selected system components to its associated element in the dictionary-structured format;
d) translating means for translating data entered in the second format into said dictionary-structured format;
and e) transmitting means for transmitting the translated data in the dictionary-structured transaction format to a trading partner.
a) input means for defining a dictionary-structured transaction format having a plurality of elements in a particular organization;
b) selector means for selecting a given system component;
c) overlay generator means cooperating with the input means and selector means for generating an overlay associated with the selected system component, said overlay being used to define a second format having positionable parts in the system component that are related to the elements in the dictionary-structured transaction format, the overlay also containing a mapping between the location of such parts in the selected system components to its associated element in the dictionary-structured format;
d) translating means for translating data entered in the second format into said dictionary-structured format;
and e) transmitting means for transmitting the translated data in the dictionary-structured transaction format to a trading partner.
6. The system of Claim 5 which further comprises memory means containing:
a) an element dictionary including an identification code for a datum defining each element and certain parameters therefore;
b) a segment dictionary including an identification code for each segment which is defined by a group of elements in a particular order;
c) a transaction dictionary including an identification code for each transaction defined by a plurality of segments in a particular order; and d) wherein the system includes means for selecting information from said dictionaries so as to create a plurality of different dictionary-structured transaction formats, with the overlay generator means being used to create second formats for the selected system component and a mapping to each transaction format that is created.
a) an element dictionary including an identification code for a datum defining each element and certain parameters therefore;
b) a segment dictionary including an identification code for each segment which is defined by a group of elements in a particular order;
c) a transaction dictionary including an identification code for each transaction defined by a plurality of segments in a particular order; and d) wherein the system includes means for selecting information from said dictionaries so as to create a plurality of different dictionary-structured transaction formats, with the overlay generator means being used to create second formats for the selected system component and a mapping to each transaction format that is created.
7. The system of Claim 6 wherein the selected system component is a display screen;
said system using a selected overlay to position certain characters on the screen that are associated with a given element together with data entry fields therefore; and wherein a keyboard is used to enter data into the data entry field on the screen; and said machine translating the entered data into the dictionary-structured format.
said system using a selected overlay to position certain characters on the screen that are associated with a given element together with data entry fields therefore; and wherein a keyboard is used to enter data into the data entry field on the screen; and said machine translating the entered data into the dictionary-structured format.
8. The system of Claim 6 wherein the selected component is a printer used to print data in a user-friendly format, said overlay being used by the translating means to translate the printed data from the dictionary-structured format.
9. The system of Claim 6 wherein said memory is a disk memory, with said overlay being used by the translating means to translate data into a fixed-format for storage on the disk from the dictionary-structured format.
10. The system of Claim 6 wherein said selected system component is a disk memory, with said overlay being used by said translating means to translate data in a fixed-field format into a dictionary-structured format.
11. A method of using a programmable machine to perform electronic data interchange among trading partners, at least two of the trading partners employing different dictionary-defined transaction formats, said programmable machine including a plurality of system components including a keyboard, screen, central processing unit (CPU), and memory, said method comprising:
a) entering a transaction code into the keyboard for a given trading partner;
b) displaying segments for the transaction code on the screen;
c) creating a data entry overlay that includes information stored on the disk which contains an ordered sequence of elements in a dictionary-structured format and mapping coordinates to the position on the screen where associated data fields relating to each element are located;
d) moving the data entry fields on the screen to generate a desired screen format, with the mapping coordinates to the associated elements in the overlay being updated accordingly;
e) entering data into the data entry fields;
f) using the data entry overlay to translate the entered data into the appropriate order for the defined dictionary-structured transaction format; and g) transmitting the data in the dictionary-structured transaction format to a trading partner.
a) entering a transaction code into the keyboard for a given trading partner;
b) displaying segments for the transaction code on the screen;
c) creating a data entry overlay that includes information stored on the disk which contains an ordered sequence of elements in a dictionary-structured format and mapping coordinates to the position on the screen where associated data fields relating to each element are located;
d) moving the data entry fields on the screen to generate a desired screen format, with the mapping coordinates to the associated elements in the overlay being updated accordingly;
e) entering data into the data entry fields;
f) using the data entry overlay to translate the entered data into the appropriate order for the defined dictionary-structured transaction format; and g) transmitting the data in the dictionary-structured transaction format to a trading partner.
12. The method of Claim 11 which further comprises:
storing an element dictionary in the memory, said element dictionary including an identification code for a datum defining each element and certain parameters therefor;
storing a segment dictionary in the memory, said segment dictionary including an identification code for each segment which is defined by a group of elements in a particular order; and storing a transaction dictionary in the memory, said transaction dictionary including an identification code for each transaction which is defined by a plurality of segments in a particular order; and wherein said machine automatically displays mandatory segments for each transaction code on the screen.
storing an element dictionary in the memory, said element dictionary including an identification code for a datum defining each element and certain parameters therefor;
storing a segment dictionary in the memory, said segment dictionary including an identification code for each segment which is defined by a group of elements in a particular order; and storing a transaction dictionary in the memory, said transaction dictionary including an identification code for each transaction which is defined by a plurality of segments in a particular order; and wherein said machine automatically displays mandatory segments for each transaction code on the screen.
13. The method of Claim 12 which further comprises:
modifying the displayed segments to thereby specifically tailor the transaction format as desired.
modifying the displayed segments to thereby specifically tailor the transaction format as desired.
14. The method of Claim 13 which further comprises:
performing steps a - e for different trading partners, whereby the machine can be used to define, enter and translate business transaction data for transmitting said data among a variety of trading partners even though they each use different dictionary-structured transaction formats.
performing steps a - e for different trading partners, whereby the machine can be used to define, enter and translate business transaction data for transmitting said data among a variety of trading partners even though they each use different dictionary-structured transaction formats.
15. A programmable machine system for operating on business transaction data in first and second dictionary-structured transaction (DST) formats, the machine system having a plurality of system components, the machine system comprising:
first means for defining a first overlay for the first DST format, and a second overlay for the second DST
format, with each such overlay having an ordered sequence of elements and mapping coordinates of given elements to related fields of a selected one of the system components; and second means, using the first overlay, for translating data in the first DST format into a different format for use with the selected one of the system components, and using the second overlay, for translating data in the second DST format into the different format for use with the selected one of the system components;
whereby the same programmable machine system and the selected system components is operated on data in different DST formats without reprogramming applications software to accommodate such different DST formats.
first means for defining a first overlay for the first DST format, and a second overlay for the second DST
format, with each such overlay having an ordered sequence of elements and mapping coordinates of given elements to related fields of a selected one of the system components; and second means, using the first overlay, for translating data in the first DST format into a different format for use with the selected one of the system components, and using the second overlay, for translating data in the second DST format into the different format for use with the selected one of the system components;
whereby the same programmable machine system and the selected system components is operated on data in different DST formats without reprogramming applications software to accommodate such different DST formats.
16. The machined system of claim 15 in which the system components includes at least a data entry screen device and a mass memory device, and wherein:
the first means defines different overlays for use with the data entry screen device and the mass memory device.
the first means defines different overlays for use with the data entry screen device and the mass memory device.
17. The machine system of claim 15, wherein two of the selected system components are a data entry screen and a keyboard for entering data, and the machine system further comprises:
means, for placing data entered onto the screen through the keyboard into the appropriate ordered position for its associated element in a DST format.
means, for placing data entered onto the screen through the keyboard into the appropriate ordered position for its associated element in a DST format.
18. The system of claim 15 in which the system components include a memory device and wherein the memory device contains information associated with segments and elements of a given transaction, and wherein the first means comprises:
means for displaying to a user those segments that are mandatory for a given transaction; and means, accessible to the user, for modifying the number, order and attributes of the segments and elements for a given transaction.
means for displaying to a user those segments that are mandatory for a given transaction; and means, accessible to the user, for modifying the number, order and attributes of the segments and elements for a given transaction.
19. The system of claim 15, in which a plurality of the system components each have a plurality of different locations for data therein, and the system further comprises:
means for selecting a given system component having a plurality of fields at various different locations, some of which are associated with certain elements;
means for tailoring a given system component by moving selected one of such fields to different locations within the system component; and means for automatically updating mapping coordinates of the elements associated with the moved fields.
means for selecting a given system component having a plurality of fields at various different locations, some of which are associated with certain elements;
means for tailoring a given system component by moving selected one of such fields to different locations within the system component; and means for automatically updating mapping coordinates of the elements associated with the moved fields.
20. A programmable machine system having a plurality of components for defining, entering, and translating business transaction data to be transmitted among trading partners, the system comprising:
input means for defining a dictionary-structured transaction (DST) format having a plurality of elements arranged in a particular organization;
means for selecting a given system components;
means, cooperating with the input means and means for selecting, for generating overlay means associated with the selected system component, the overlay means being for defining a second format having positionable parts associated within locations in the selected system component that are related to the elements in the DST format, the overlay means also containing mapping means for correlating the locations of such parts in the selected system component to associated elements in the DST format; and means for translating data entered in the second format into the DST format.
input means for defining a dictionary-structured transaction (DST) format having a plurality of elements arranged in a particular organization;
means for selecting a given system components;
means, cooperating with the input means and means for selecting, for generating overlay means associated with the selected system component, the overlay means being for defining a second format having positionable parts associated within locations in the selected system component that are related to the elements in the DST format, the overlay means also containing mapping means for correlating the locations of such parts in the selected system component to associated elements in the DST format; and means for translating data entered in the second format into the DST format.
21. The system of claim 20, which further comprises:
means for transmitting data translated into the DST
format to a trading partner.
means for transmitting data translated into the DST
format to a trading partner.
22. The system of claim 20 which further comprises:
programmed memory means containing:
(a) an element dictionary including an identification code for each datum defining an element;
(b) a segment dictionary including an identification code for each segment defined by a group of elements in a particular order; and (c) a transaction dictionary including an identification code for each transaction defined by a plurality of segments in a particular order.
programmed memory means containing:
(a) an element dictionary including an identification code for each datum defining an element;
(b) a segment dictionary including an identification code for each segment defined by a group of elements in a particular order; and (c) a transaction dictionary including an identification code for each transaction defined by a plurality of segments in a particular order.
23. The system of claim 22, which further comprises:
means for selecting information from the dictionaries in order to create different DST formats.
means for selecting information from the dictionaries in order to create different DST formats.
24. A method of using a programmable machine including a mass memory, keyboard, data entry screen and central processing unit (CPU) to enter electronic business data in first and second different dictionary-structured transaction (DST) formats into a machine in preparation for interchange of such data among trading partners, said method comprising the steps of:
(a) loading, from mass memory into the CPU, a first DST overlay associated with the first DST format;
(b) entering data via the keyboard associated with given elements of the first DST format into related fields shown on the screen;
(c) under the control of the CPU and using the first DST overlay, storing data entered during step (b) in an intermediate file;
(d) loading, from mass memory into the CPU, a second DST overlay associated with the second DST format;
(e) entering data via the keyboard associated with given elements of the second DST format into related fields shown on the screen; and (f) under the control of the CPU and using the second DST overlay, storing data entered during (e) in an intermediate file.
(a) loading, from mass memory into the CPU, a first DST overlay associated with the first DST format;
(b) entering data via the keyboard associated with given elements of the first DST format into related fields shown on the screen;
(c) under the control of the CPU and using the first DST overlay, storing data entered during step (b) in an intermediate file;
(d) loading, from mass memory into the CPU, a second DST overlay associated with the second DST format;
(e) entering data via the keyboard associated with given elements of the second DST format into related fields shown on the screen; and (f) under the control of the CPU and using the second DST overlay, storing data entered during (e) in an intermediate file.
25. The method of claim 24, further comprising the step of:
(g) under the control of the CPU and using at least one DST overlay, fetching data entered during steps (b) and (e) from one or more intermediate files in preparation for transmission of such data to a trading partner.
(g) under the control of the CPU and using at least one DST overlay, fetching data entered during steps (b) and (e) from one or more intermediate files in preparation for transmission of such data to a trading partner.
26. The method of claim 24, further comprising the step of:
(g) creating the first and second DST overlays, with each such overlay containing information about the ordered sequence of elements in its DST format and mapping coordinates to positions on the screen where associated data fields relating to each element are located.
(g) creating the first and second DST overlays, with each such overlay containing information about the ordered sequence of elements in its DST format and mapping coordinates to positions on the screen where associated data fields relating to each element are located.
27. The method of claim 26, further comprising the steps of:
(h) moving the data entry fields associated with the first DST overlay on the screen to generate a desired screen format, and (i) updating mapping coordinates of the associated elements in the first DST overlay accordingly.
(h) moving the data entry fields associated with the first DST overlay on the screen to generate a desired screen format, and (i) updating mapping coordinates of the associated elements in the first DST overlay accordingly.
28. In a programmable machine system, including a keyboard, a display screen, a processor and at least one mass memory device, for operating on business transaction data in different dictionary-structured transaction (DST) formats, a method of translating data organized in first and second DST
formats to a file format composed of fixed-field, fixed-length records, comprising the steps of:
(a) interactively using the keyboard, display screen and processor to define, without manually coding a computer program, a first DST overlay including mapping coordinates;
(b) formatting at least one segment of data in the first DST format into the fixed file format by moving elements of the data about in accordance with mapping coordinates contained in the first DST overlay;
(c) storing the data formatted in step (b) in a fixed file in a mass memory device;
(d) interactively using the keyboard, display screen and processor to define, without manually coding a computer program, a second DST overlay including mapping coordinates;
(e) formatting at least one segment of data in the second DST format into the fixed file format by moving elements of the data about in accordance with mapping coordinates contained in the second DST overlay; and (f) storing the data formatted in step (e) in a fixed file in a mass memory device.
formats to a file format composed of fixed-field, fixed-length records, comprising the steps of:
(a) interactively using the keyboard, display screen and processor to define, without manually coding a computer program, a first DST overlay including mapping coordinates;
(b) formatting at least one segment of data in the first DST format into the fixed file format by moving elements of the data about in accordance with mapping coordinates contained in the first DST overlay;
(c) storing the data formatted in step (b) in a fixed file in a mass memory device;
(d) interactively using the keyboard, display screen and processor to define, without manually coding a computer program, a second DST overlay including mapping coordinates;
(e) formatting at least one segment of data in the second DST format into the fixed file format by moving elements of the data about in accordance with mapping coordinates contained in the second DST overlay; and (f) storing the data formatted in step (e) in a fixed file in a mass memory device.
29. The method of claim 28, further comprising the steps of:
storing the first and second DST overlays in a mass memory device for later use;
loading the first DST overlay from the mass memory device into the processor when needed for use; and loading the second DST overlay into the processor from the mass memory in to the processor when needed for use.
storing the first and second DST overlays in a mass memory device for later use;
loading the first DST overlay from the mass memory device into the processor when needed for use; and loading the second DST overlay into the processor from the mass memory in to the processor when needed for use.
30. The method of claim 28, wherein in the formatting steps (b) and (e) each include the substeps of:
(1) finding a position where current element data corresponding to a specific element in the DST format are to be placed;
(2) determining whether such current element data would overlay a value already loaded into a flat image work file;
(3) writing the flat image work file if in substep (2) it is determined that the current element data would overlay a value already loaded into the flat image work file.
(1) finding a position where current element data corresponding to a specific element in the DST format are to be placed;
(2) determining whether such current element data would overlay a value already loaded into a flat image work file;
(3) writing the flat image work file if in substep (2) it is determined that the current element data would overlay a value already loaded into the flat image work file.
31. In a programmable machine system, including a manual input means, a display screen, processor and a mass memory device, for operating on business transaction data in different dictionary-structured transaction (DST) formats, a method of translating data organized in a fixed file format composed of fixed-field, fixed-length records into a first and second (DST) formats, the method comprising the steps of:
(a) interactively using the manual input means, display screen and processor to define, without manually coding a computer program, a first DST overlay including mapping coordinates;
(b) formatting at least one segment of data in the fixed file format into the first DST format by moving elements of the data about in accordance with mapping coordinates contained in the first DST overlay;
(c) storing the data formatted in step (b) in a DST
file in a mass memory device;
(d) interactively using the manual input means, display screen and processor to define, without manually coding a computer program, a second DST overlay including mapping coordinates;
(e) formatting at least one segment of data in the fixed file format into the second DST format by moving elements of the data about in accordance with mapping coordinates contained in the second DST overlay; and (f) storing the data formatted in step (e) in a DST
file in a mass memory device.
(a) interactively using the manual input means, display screen and processor to define, without manually coding a computer program, a first DST overlay including mapping coordinates;
(b) formatting at least one segment of data in the fixed file format into the first DST format by moving elements of the data about in accordance with mapping coordinates contained in the first DST overlay;
(c) storing the data formatted in step (b) in a DST
file in a mass memory device;
(d) interactively using the manual input means, display screen and processor to define, without manually coding a computer program, a second DST overlay including mapping coordinates;
(e) formatting at least one segment of data in the fixed file format into the second DST format by moving elements of the data about in accordance with mapping coordinates contained in the second DST overlay; and (f) storing the data formatted in step (e) in a DST
file in a mass memory device.
32. The method of claim 31, further comprising the steps of:
storing the first and second overlays in a mass memory device for later use;
loading the first DST overlay from the mass memory device into the processor when needed for use; and loading the second DST overlay into the processor from the mass memory into the processor when needed for use.
storing the first and second overlays in a mass memory device for later use;
loading the first DST overlay from the mass memory device into the processor when needed for use; and loading the second DST overlay into the processor from the mass memory into the processor when needed for use.
33. The method of claim 32, wherein the formatting steps (b) and (e) each include the substeps of:
using a flat file image work file to temporarily store data; and periodically writing data from the image work file to a mass memory device.
using a flat file image work file to temporarily store data; and periodically writing data from the image work file to a mass memory device.
34. The method of claim 31, wherein the storing steps (c) and (f) each include the substep of writing transaction, group and interchange trailers to the fixed file at the end of at least the last segment of formatted data being stored in the DST file.
35. The method of claim 31, wherein the formatting steps each include the substeps of:
locating current segments and elements in the DST
overlay being used in the formatting step;
determining whether a current element is a constant or a formula;
if the current element is a constant moving the constant value to a corresponding flat element; and if the current element is a formula moving a calculated formula value to a corresponding flat element.
locating current segments and elements in the DST
overlay being used in the formatting step;
determining whether a current element is a constant or a formula;
if the current element is a constant moving the constant value to a corresponding flat element; and if the current element is a formula moving a calculated formula value to a corresponding flat element.
36. In a programmable machine system for operating on business transaction data in different dictionary-structured transaction (DST) formats, said machine system including a plurality of system components including manual input means, a display screen, processor, and memory; a method of creating a data entry overlay to help minimize manual input of data comprising the steps of:
interactively using the manual input means, display screen, processor and memory to define, without manually coding a computer program, a basic data entry DST overlay having an ordered sequence of elements and mapping coordinates of given elements to related fields of the display screen by specifying an overlay code and a transaction type code; and customizing the basic data entry overlay thus defined by modifying at least one of the characteristics provided in the basic data entry overlay.
interactively using the manual input means, display screen, processor and memory to define, without manually coding a computer program, a basic data entry DST overlay having an ordered sequence of elements and mapping coordinates of given elements to related fields of the display screen by specifying an overlay code and a transaction type code; and customizing the basic data entry overlay thus defined by modifying at least one of the characteristics provided in the basic data entry overlay.
37. The method of claim 36, wherein the customizing step includes modifying at least one of the elements provided in the data entry overlay.
38. The method of claim 36, wherein the customizing step includes specifying overall transaction parameters for mapping data entered via the manual input means to the display screen.
39. The method of claim 38, wherein the overall transaction parameters being specified include at least two parameters elected from the group of screen parameters consisting of column width, minimum gap between elements on the display screen, reverse video selection, default line spacing, and mandatory field characters adjacent selected fields.
40. The method of claim 38, wherein the overall transaction parameters being specified include visual effects on the screen to indicate maximum allowable sizes of corresponding elements, and overlay description fields where identification of a trading partner and transaction are placed on the screen.
41. The method of claim 36, wherein the customizing step includes tailoring the appearance of the screen by moving at least two fields to different locations on the display screen.
42. The method of claim 36, in which the DST overlay includes a plurality of segments with each segment having one or more functionally related elements in a defined sequence, and wherein the customizing step includes modifying at least one of the segments.
43. The method of claim 42, wherein the customizing step includes the substeps of:
(a) selecting desired segments out of those segments displayed on the display screen;
(b) specifying a maximum number of times a specific selected segment is permitted to appear specific location on the screen; and (c) specifying whether particular groups of logically related segments will occur repetitively.
(a) selecting desired segments out of those segments displayed on the display screen;
(b) specifying a maximum number of times a specific selected segment is permitted to appear specific location on the screen; and (c) specifying whether particular groups of logically related segments will occur repetitively.
44. The method of claim 42, in which each segment has a name, and wherein the customizing step includes the substeps of:
(a) changing a segment name; and (b) specifying beginning and ending segments of a group of logically related segments that occur repetitively,
(a) changing a segment name; and (b) specifying beginning and ending segments of a group of logically related segments that occur repetitively,
45. The method of claim 43, wherein the customizing step includes the substeps of:
(a) adding elements within a first segment of the basic data entry DST overlay; and (b) deleting elements within a second segment of the basic data entry DST overlay.
(a) adding elements within a first segment of the basic data entry DST overlay; and (b) deleting elements within a second segment of the basic data entry DST overlay.
46. The method of claim 43, wherein the customizing step includes specifying attributes of elements within at least one segment of the basic data entry DST overlay.
47. The method of claim 46, wherein specifying attributes of elements within segments is accomplished at least in part by using the manual input means to enter particular selections of attributes for selected elements displayed upon the display screen.
48. The method of claim 46, wherein the attributes specified include at least two attributes selected from the group of attributes consisting of element codes, data types, requirement codes, number of characters, and default codes.
Priority Applications (7)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US07/190,147 US4951196A (en) | 1988-05-04 | 1988-05-04 | Method and apparatus for electronic data interchange |
| CA000615490A CA1323107C (en) | 1988-05-04 | 1989-09-29 | Method and apparatus for electronic data interchange |
| AU60257/90A AU630218B2 (en) | 1988-05-04 | 1990-08-07 | Method and apparatus for electronic data interchange |
| EP90115944A EP0471867B1 (en) | 1988-05-04 | 1990-08-20 | Method and apparatus for electronic data interchange |
| DE69026252T DE69026252T2 (en) | 1988-05-04 | 1990-08-20 | Method and device for electronic data exchange |
| DE199090115944T DE471867T1 (en) | 1988-05-04 | 1990-08-20 | METHOD AND DEVICE FOR ELECTRONIC DATA EXCHANGE. |
| ES90115944T ES2034931T3 (en) | 1988-05-04 | 1990-08-20 | METHOD AND APPARATUS FOR THE EXCHANGE OF ELECTRONIC DATA. |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US07/190,147 US4951196A (en) | 1988-05-04 | 1988-05-04 | Method and apparatus for electronic data interchange |
| CA000615490A CA1323107C (en) | 1988-05-04 | 1989-09-29 | Method and apparatus for electronic data interchange |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA1323107C true CA1323107C (en) | 1993-10-12 |
Family
ID=25673219
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA000615490A Expired - Lifetime CA1323107C (en) | 1988-05-04 | 1989-09-29 | Method and apparatus for electronic data interchange |
Country Status (6)
| Country | Link |
|---|---|
| US (1) | US4951196A (en) |
| EP (1) | EP0471867B1 (en) |
| AU (1) | AU630218B2 (en) |
| CA (1) | CA1323107C (en) |
| DE (2) | DE471867T1 (en) |
| ES (1) | ES2034931T3 (en) |
Families Citing this family (160)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5381555A (en) * | 1987-05-18 | 1995-01-10 | The Larches Corporation | Method for designation of data in a data bank and extraction of data for use in a computer program |
| US4951196A (en) * | 1988-05-04 | 1990-08-21 | Supply Tech, Inc. | Method and apparatus for electronic data interchange |
| US5214779A (en) * | 1988-06-30 | 1993-05-25 | International Business Machines Corporation | Variable construct representation embedded in data stream which references definition for dynamically generating data used in processing the data stream |
| US5410675A (en) * | 1989-08-21 | 1995-04-25 | Lisa M. Shreve | Method of conforming input data to an output data structure and engine for accomplishing same |
| US5251314A (en) * | 1990-06-07 | 1993-10-05 | International Business Machines Corporation | System for converting from one document type to a plurality of document types allowing accurate reversal therefrom using tables containing indications regarding non-transformable elements |
| US5202977A (en) * | 1990-07-13 | 1993-04-13 | Premenos Corp. | Edi translation system using plurality of communication processes and de-enveloping procedure corresponding to transmitted communication process |
| EP0507717A2 (en) * | 1991-04-01 | 1992-10-07 | International Business Machines Corporation | Method and apparatus for interchange of customization characteristics of formatted business data |
| WO1992018939A1 (en) * | 1991-04-19 | 1992-10-29 | Meiji Milk Products Co., Ltd. | Sale quantity characteristics classification system and supplementary ordering system |
| US5367664A (en) * | 1991-08-30 | 1994-11-22 | Magill James W | Electronic document interchange test facility |
| US5504891A (en) * | 1991-10-17 | 1996-04-02 | Ricoh Company, Ltd. | Method and apparatus for format conversion of a hierarchically structured page description language document |
| US5506985A (en) * | 1991-10-17 | 1996-04-09 | Ricoh Company, Ltd. | Method and apparatus for format conversion of a hierarchically structured page description language document |
| US5363489A (en) * | 1991-12-30 | 1994-11-08 | At&T Bell Laboratories | Auxiliary circuit for complementing the signaling of incompatible protocol systems |
| US6006199A (en) * | 1991-12-31 | 1999-12-21 | International Business Machines Corporation | Method and system for automated payment within a computer integrated manufacturing system |
| CA2093094C (en) * | 1992-04-06 | 2000-07-11 | Addison M. Fischer | Method and apparatus for creating, supporting, and using travelling programs |
| US5557780A (en) * | 1992-04-30 | 1996-09-17 | Micron Technology, Inc. | Electronic data interchange system for managing non-standard data |
| AU4237293A (en) * | 1992-05-08 | 1993-12-13 | Release Management Systems (Rms) | Data interchange system |
| JPH08509824A (en) * | 1993-02-26 | 1996-10-15 | タリジェント インコーポレイテッド | Collaborative work system |
| US20030185356A1 (en) | 1993-03-12 | 2003-10-02 | Telebuyer, Llc | Commercial product telephonic routing system with mobile wireless and video vending capability |
| US6323894B1 (en) | 1993-03-12 | 2001-11-27 | Telebuyer, Llc | Commercial product routing system with video vending capability |
| US7019770B1 (en) | 1993-03-12 | 2006-03-28 | Telebuyer, Llc | Videophone system for scrutiny monitoring with computer control |
| US5495284A (en) | 1993-03-12 | 1996-02-27 | Katz; Ronald A. | Scheduling and processing system for telephone video communication |
| US5644778A (en) | 1993-11-02 | 1997-07-01 | Athena Of North America, Inc. | Medical transaction system |
| DE69432114T2 (en) * | 1993-11-24 | 2003-10-30 | Canon Kk | System for identifying and processing forms |
| US5509071A (en) * | 1994-04-01 | 1996-04-16 | Microelectronics And Computer Technology Corporation | Electronic proof of receipt |
| US5638519A (en) * | 1994-05-20 | 1997-06-10 | Haluska; John E. | Electronic method and system for controlling and tracking information related to business transactions |
| US5745759A (en) * | 1994-10-14 | 1998-04-28 | Qnx Software Systems, Ltd. | Window kernel |
| US6397262B1 (en) | 1994-10-14 | 2002-05-28 | Qnx Software Systems, Ltd. | Window kernel |
| US8588729B2 (en) * | 1994-11-21 | 2013-11-19 | Bgc Partners, Inc. | Method for retrieving data stored in a database |
| US6876309B1 (en) * | 1994-11-21 | 2005-04-05 | Espeed, Inc. | Bond trading system |
| US5608874A (en) * | 1994-12-02 | 1997-03-04 | Autoentry Online, Inc. | System and method for automatic data file format translation and transmission having advanced features |
| US5715397A (en) * | 1994-12-02 | 1998-02-03 | Autoentry Online, Inc. | System and method for data transfer and processing having intelligent selection of processing routing and advanced routing features |
| AU706649B2 (en) | 1995-05-08 | 1999-06-17 | Cranberry Properties, Llc | Rules based electronic message management system |
| US6889194B1 (en) * | 1995-06-01 | 2005-05-03 | United Parcel Service Of America, Inc. | Method and system for preparing an electronic record for shipping a parcel |
| WO1997024679A1 (en) * | 1995-12-27 | 1997-07-10 | Tele-Communications, Inc. | Billing statement rendering system and method |
| US5761650A (en) * | 1995-12-29 | 1998-06-02 | Csg Systems, Inc. | Billing system and method |
| US5893076A (en) * | 1996-01-16 | 1999-04-06 | Sterling Commerce, Inc. | Supplier driven commerce transaction processing system and methodology |
| US5878419A (en) * | 1996-01-19 | 1999-03-02 | Novell, Inc. | Method for creating a relational description of a formatted transaction |
| US5758126A (en) * | 1996-03-19 | 1998-05-26 | Sterling Commerce, Inc. | Customizable bidirectional EDI translation system |
| JP3786708B2 (en) * | 1996-06-18 | 2006-06-14 | クランベリー、プロパティーズ、リミテッド、ライアビリティー、カンパニー | Voice, facsimile and e-mail integrated message system |
| US5794234A (en) * | 1996-08-14 | 1998-08-11 | The Ec Company | Method and system for providing electronic commerce between incompatible data processing systems |
| US5995939A (en) * | 1996-10-15 | 1999-11-30 | Cymedix Lynx Corporation | Automated networked service request and fulfillment system and method |
| US6502191B1 (en) * | 1997-02-14 | 2002-12-31 | Tumbleweed Communications Corp. | Method and system for binary data firewall delivery |
| US5905974A (en) * | 1996-12-13 | 1999-05-18 | Cantor Fitzgerald Securities | Automated auction protocol processor |
| US6850907B2 (en) | 1996-12-13 | 2005-02-01 | Cantor Fitzgerald, L.P. | Automated price improvement protocol processor |
| US5911776A (en) * | 1996-12-18 | 1999-06-15 | Unisys Corporation | Automatic format conversion system and publishing methodology for multi-user network |
| US6606603B1 (en) | 1997-04-28 | 2003-08-12 | Ariba, Inc. | Method and apparatus for ordering items using electronic catalogs |
| US7117165B1 (en) | 1997-04-28 | 2006-10-03 | Ariba, Inc. | Operating resource management system |
| JPH10307881A (en) * | 1997-05-08 | 1998-11-17 | Fujitsu Ltd | Electronic transaction device and computer-readable storage medium recording control program for executing format conversion by electronic transaction |
| US6023700A (en) * | 1997-06-17 | 2000-02-08 | Cranberry Properties, Llc | Electronic mail distribution system for integrated electronic communication |
| US6235176B1 (en) * | 1997-09-23 | 2001-05-22 | Mb Schoen & Associates | Computer apparatus and method for defined contribution and profit sharing pension and disability plan |
| US20030167220A1 (en) * | 1997-09-23 | 2003-09-04 | Schoen Matthew B. | Computer apparatus and method for illustrating, issuing, and managing disability coverage for retirement plans with individual accounts |
| US5970475A (en) * | 1997-10-10 | 1999-10-19 | Intelisys Electronic Commerce, Llc | Electronic procurement system and method for trading partners |
| US6078891A (en) * | 1997-11-24 | 2000-06-20 | Riordan; John | Method and system for collecting and processing marketing data |
| US6330617B1 (en) | 1998-02-27 | 2001-12-11 | Sabre Inc | System, method and computer program product for data conversion in a computer network |
| US6104999A (en) * | 1998-04-06 | 2000-08-15 | Ameritech Corporation | Transaction sets for automated electronic ordering of telecommunications products and services |
| US6137873A (en) * | 1998-04-06 | 2000-10-24 | Ameritech Corporation | Automatic electronic telecommunications order translation and processing |
| US6249578B1 (en) | 1998-04-06 | 2001-06-19 | Ameritech Corporation | Interactive electronic ordering for telecommunications products and services |
| US7113913B1 (en) * | 1998-06-10 | 2006-09-26 | Corporate Compensation Plans, Inc. Of Connecticut | Method and system for providing insurance protection against loss of retirement accumulations in a tax favored defined contribution plan in the event of a participant's disability |
| WO2000043903A1 (en) * | 1999-01-22 | 2000-07-27 | Stephen Ross Corkill | Method and system of performing electronic data interchange |
| US6772180B1 (en) | 1999-01-22 | 2004-08-03 | International Business Machines Corporation | Data representation schema translation through shared examples |
| US6539360B1 (en) | 1999-02-05 | 2003-03-25 | United Parcel Service Of America, Inc. | Special handling processing in a package transportation system |
| WO2000046683A2 (en) * | 1999-02-08 | 2000-08-10 | Sabre Inc. | Apparatus and method for data conversion in a computer network |
| US7392214B1 (en) * | 1999-04-30 | 2008-06-24 | Bgc Partners, Inc. | Systems and methods for trading |
| US6408303B1 (en) | 1999-07-06 | 2002-06-18 | Healthcare Transaction Processors, Inc. | System and method for automated building of a trading partner profile |
| US6947903B1 (en) * | 1999-08-06 | 2005-09-20 | Elcommerce.Com.Inc. | Method and system for monitoring a supply-chain |
| EP1093072A1 (en) * | 1999-10-16 | 2001-04-18 | Rolf-Georg Brockmans | Method for retrievable archiving of individual items of a cumulative transaction |
| US6876991B1 (en) | 1999-11-08 | 2005-04-05 | Collaborative Decision Platforms, Llc. | System, method and computer program product for a collaborative decision platform |
| EP1107152A3 (en) | 1999-12-03 | 2007-08-29 | Citibank, N.A. | Method and system for managing communication of information |
| US7051071B2 (en) * | 2000-02-16 | 2006-05-23 | Bea Systems, Inc. | Workflow integration system for enterprise wide electronic collaboration |
| US6834312B2 (en) | 2000-05-02 | 2004-12-21 | Cadopener.Com 11C | Method and apparatus for delivery of data over a network |
| US20040073617A1 (en) | 2000-06-19 | 2004-04-15 | Milliken Walter Clark | Hash-based systems and methods for detecting and preventing transmission of unwanted e-mail |
| US20050229003A1 (en) | 2004-04-09 | 2005-10-13 | Miles Paschini | System and method for distributing personal identification numbers over a computer network |
| US20020013722A1 (en) * | 2000-07-27 | 2002-01-31 | Kanaga Samantha J. | Enhanced document escrow service |
| US7899690B1 (en) | 2000-08-18 | 2011-03-01 | The Crawford Group, Inc. | Extended web enabled business to business computer system for rental vehicle services |
| US7275038B1 (en) * | 2000-08-18 | 2007-09-25 | The Crawford Group, Inc. | Web enabled business to business operating system for rental car services |
| US8600783B2 (en) | 2000-08-18 | 2013-12-03 | The Crawford Group, Inc. | Business to business computer system for communicating and processing rental car reservations using web services |
| US7487110B2 (en) * | 2001-01-30 | 2009-02-03 | International Business Machines Corporation | Automotive information communication exchange system, method, and program product |
| US6886011B2 (en) | 2001-02-02 | 2005-04-26 | Datalign, Inc. | Good and service description system and method |
| US9912722B2 (en) | 2001-04-02 | 2018-03-06 | Irving S. Rappaport | Method and system for facilitating the integration of a plurality of dissimilar systems |
| US7143190B2 (en) * | 2001-04-02 | 2006-11-28 | Irving S. Rappaport | Method and system for remotely facilitating the integration of a plurality of dissimilar systems |
| US20020165975A1 (en) * | 2001-05-07 | 2002-11-07 | Michael Abbott | Dynamic mapping of communication protocols |
| US7392217B2 (en) | 2001-05-09 | 2008-06-24 | Bgc Partners, Inc. | Systems and methods for controlling traders from manipulating electronic trading markets |
| US20030023492A1 (en) * | 2001-06-20 | 2003-01-30 | John Riordan | Method and system for collecting and processing marketing data |
| US8332502B1 (en) | 2001-08-15 | 2012-12-11 | Metavante Corporation | Business to business network management event detection and response system and method |
| US6886018B1 (en) | 2001-10-05 | 2005-04-26 | Metavante Corporation | Data processing technique for formatting data files that are subjected to a high volume of changes |
| US7386478B2 (en) | 2001-10-15 | 2008-06-10 | Sun Microsystems, Inc. | Dynamic criteria based line-grouping mechanism and method for purchase order generation |
| US7337132B2 (en) * | 2001-10-17 | 2008-02-26 | Sun Microsystems, Inc. | Customizable two step mapping of extensible markup language data in an e-procurement system and method |
| US7644014B2 (en) | 2001-10-17 | 2010-01-05 | Sun Microsystems, Inc. | Document exchange framework for automated extensible markup language data in an e-procurement system and method |
| US7458098B2 (en) * | 2002-03-08 | 2008-11-25 | Secure Computing Corporation | Systems and methods for enhancing electronic communication security |
| US20060015942A1 (en) | 2002-03-08 | 2006-01-19 | Ciphertrust, Inc. | Systems and methods for classification of messaging entities |
| US7124438B2 (en) * | 2002-03-08 | 2006-10-17 | Ciphertrust, Inc. | Systems and methods for anomaly detection in patterns of monitored communications |
| US7870203B2 (en) | 2002-03-08 | 2011-01-11 | Mcafee, Inc. | Methods and systems for exposing messaging reputation to an end user |
| US7903549B2 (en) | 2002-03-08 | 2011-03-08 | Secure Computing Corporation | Content-based policy compliance systems and methods |
| US6941467B2 (en) | 2002-03-08 | 2005-09-06 | Ciphertrust, Inc. | Systems and methods for adaptive message interrogation through multiple queues |
| US8578480B2 (en) | 2002-03-08 | 2013-11-05 | Mcafee, Inc. | Systems and methods for identifying potentially malicious messages |
| US8132250B2 (en) | 2002-03-08 | 2012-03-06 | Mcafee, Inc. | Message profiling systems and methods |
| US7694128B2 (en) | 2002-03-08 | 2010-04-06 | Mcafee, Inc. | Systems and methods for secure communication delivery |
| US8561167B2 (en) | 2002-03-08 | 2013-10-15 | Mcafee, Inc. | Web reputation scoring |
| US20030172291A1 (en) | 2002-03-08 | 2003-09-11 | Paul Judge | Systems and methods for automated whitelisting in monitored communications |
| US7693947B2 (en) | 2002-03-08 | 2010-04-06 | Mcafee, Inc. | Systems and methods for graphically displaying messaging traffic |
| US7350698B2 (en) * | 2002-03-15 | 2008-04-01 | Sun Microsystems, Inc. | Line item approval processing in an electronic purchasing system and method |
| US20040039612A1 (en) | 2002-06-14 | 2004-02-26 | Neil Fitzgerald | Method and apparatus for customer direct on-line reservation of rental vehicles |
| US8108231B2 (en) | 2002-06-14 | 2012-01-31 | The Crawford Group, Inc. | Method and apparatus for improved customer direct on-line reservation of rental vehicles |
| EP2428872A1 (en) | 2002-10-31 | 2012-03-14 | eSpeed, Inc. | Keyboard for trading system |
| GB2395036A (en) | 2002-10-31 | 2004-05-12 | Espeed Inc | Trading interface using keyboard |
| US10205721B2 (en) | 2002-12-10 | 2019-02-12 | Ewi Holdings, Inc. | System and method for distributing personal identification numbers over a computer network |
| US7131578B2 (en) | 2003-05-28 | 2006-11-07 | Ewi Holdings, Inc. | System and method for electronic prepaid account replenishment |
| US20050102156A1 (en) * | 2003-11-07 | 2005-05-12 | Ebl Technology Holdings, Ltd. | System and method for managing information in a group participant purchasing environment |
| US8131625B2 (en) | 2003-11-17 | 2012-03-06 | Bgc Partners, Inc. | Customizable trading display of market data |
| US8131626B2 (en) | 2003-11-17 | 2012-03-06 | Bgc Partners, Inc. | Customizable trading display of market data |
| US7280644B2 (en) | 2004-12-07 | 2007-10-09 | Ewi Holdings, Inc. | Transaction processing platform for faciliating electronic distribution of plural prepaid services |
| US11475436B2 (en) | 2010-01-08 | 2022-10-18 | Blackhawk Network, Inc. | System and method for providing a security code |
| US11599873B2 (en) | 2010-01-08 | 2023-03-07 | Blackhawk Network, Inc. | Systems and methods for proxy card and/or wallet redemption card transactions |
| US7676407B2 (en) * | 2004-04-26 | 2010-03-09 | General Electric Company | Method and apparatus for account payable matching for an online purchasing system |
| US7283067B2 (en) * | 2004-05-10 | 2007-10-16 | Espeed, Inc. | Fully configurable trading keyboard |
| US8635690B2 (en) | 2004-11-05 | 2014-01-21 | Mcafee, Inc. | Reputation based message processing |
| EP1717747A1 (en) | 2005-03-24 | 2006-11-02 | eSPEED, Inc. | Systems and methods for protecting against erroneous price entries in the electronic trading of financial and other instruments |
| US7937480B2 (en) | 2005-06-02 | 2011-05-03 | Mcafee, Inc. | Aggregation of reputation data |
| US7650353B2 (en) * | 2005-12-16 | 2010-01-19 | Microsoft Corporation | XML specification for electronic data interchange (EDI) |
| US7447707B2 (en) * | 2005-12-16 | 2008-11-04 | Microsoft Corporation | Automatic schema discovery for electronic data interchange (EDI) at runtime |
| US7599944B2 (en) * | 2005-12-16 | 2009-10-06 | Microsoft Corporation | Electronic data interchange (EDI) schema simplification interface |
| US7647500B2 (en) * | 2005-12-16 | 2010-01-12 | Microsoft Corporation | Synchronous validation and acknowledgment of electronic data interchange (EDI) |
| US8229832B2 (en) | 2006-01-09 | 2012-07-24 | Bgc Partners, Inc. | Systems and methods for establishing first on the follow trading priority in electronic trading systems |
| US7620645B2 (en) * | 2006-02-24 | 2009-11-17 | Microsoft Corporation | Scalable algorithm for sharing EDI schemas |
| US7984373B2 (en) * | 2006-02-24 | 2011-07-19 | Microsoft Corporation | EDI instance based transaction set definition |
| US7703099B2 (en) * | 2006-02-24 | 2010-04-20 | Microsoft Corporation | Scalable transformation and configuration of EDI interchanges |
| US7685208B2 (en) * | 2006-02-24 | 2010-03-23 | Microsoft Corporation | XML payload specification for modeling EDI schemas |
| US8156148B2 (en) * | 2006-02-24 | 2012-04-10 | Microsoft Corporation | Scalable algorithm for sharing EDI schemas |
| US8271309B2 (en) | 2006-03-16 | 2012-09-18 | The Crawford Group, Inc. | Method and system for providing and administering online rental vehicle reservation booking services |
| US10296895B2 (en) | 2010-01-08 | 2019-05-21 | Blackhawk Network, Inc. | System for processing, activating and redeeming value added prepaid cards |
| US20080126385A1 (en) * | 2006-09-19 | 2008-05-29 | Microsoft Corporation | Intelligent batching of electronic data interchange messages |
| US20080071806A1 (en) * | 2006-09-20 | 2008-03-20 | Microsoft Corporation | Difference analysis for electronic data interchange (edi) data dictionary |
| US8161078B2 (en) * | 2006-09-20 | 2012-04-17 | Microsoft Corporation | Electronic data interchange (EDI) data dictionary management and versioning system |
| US20080126386A1 (en) * | 2006-09-20 | 2008-05-29 | Microsoft Corporation | Translation of electronic data interchange messages to extensible markup language representation(s) |
| US8108767B2 (en) * | 2006-09-20 | 2012-01-31 | Microsoft Corporation | Electronic data interchange transaction set definition based instance editing |
| EP2070026A4 (en) | 2006-10-06 | 2012-01-18 | Crawford Group Inc | Method and system for communicating vehicle repair information to a business-to-business rental vehicle reservation management computer system |
| US20080168081A1 (en) * | 2007-01-09 | 2008-07-10 | Microsoft Corporation | Extensible schemas and party configurations for edi document generation or validation |
| US20080168109A1 (en) * | 2007-01-09 | 2008-07-10 | Microsoft Corporation | Automatic map updating based on schema changes |
| US8763114B2 (en) | 2007-01-24 | 2014-06-24 | Mcafee, Inc. | Detecting image spam |
| US8214497B2 (en) | 2007-01-24 | 2012-07-03 | Mcafee, Inc. | Multi-dimensional reputation scoring |
| US8179798B2 (en) | 2007-01-24 | 2012-05-15 | Mcafee, Inc. | Reputation based connection throttling |
| US7779156B2 (en) | 2007-01-24 | 2010-08-17 | Mcafee, Inc. | Reputation based load balancing |
| US7949716B2 (en) | 2007-01-24 | 2011-05-24 | Mcafee, Inc. | Correlation and analysis of entity attributes |
| US8185930B2 (en) | 2007-11-06 | 2012-05-22 | Mcafee, Inc. | Adjusting filter or classification control settings |
| US8045458B2 (en) | 2007-11-08 | 2011-10-25 | Mcafee, Inc. | Prioritizing network traffic |
| US9286335B1 (en) | 2008-01-16 | 2016-03-15 | TransThought, LLC | Performing abstraction and/or integration of information |
| US8346785B1 (en) | 2008-01-16 | 2013-01-01 | TransThought, LLC | Performing abstraction and/or integration of information |
| US8160975B2 (en) | 2008-01-25 | 2012-04-17 | Mcafee, Inc. | Granular support vector machine with random granularity |
| US8589503B2 (en) | 2008-04-04 | 2013-11-19 | Mcafee, Inc. | Prioritizing network traffic |
| US20100023352A1 (en) * | 2008-07-23 | 2010-01-28 | The Crawford Group, Inc. | System and Method for Improved Information Sharing by Repair Facilities for Managing Rental Vehicle Reservations |
| CA2786264A1 (en) | 2010-01-08 | 2011-07-14 | Blackhawk Network, Inc. | A system for processing, activating and redeeming value added prepaid cards |
| US10037526B2 (en) * | 2010-01-08 | 2018-07-31 | Blackhawk Network, Inc. | System for payment via electronic wallet |
| US8621638B2 (en) | 2010-05-14 | 2013-12-31 | Mcafee, Inc. | Systems and methods for classification of messaging entities |
| KR101903963B1 (en) | 2010-08-27 | 2018-10-05 | 블랙호크 네트워크, 아이엔씨. | Prepaid card with savings feature |
| US8837683B2 (en) | 2010-10-10 | 2014-09-16 | Medsign International Corporation | Critical health information profile and emergency communication system |
| US9122877B2 (en) | 2011-03-21 | 2015-09-01 | Mcafee, Inc. | System and method for malware and network reputation correlation |
| US11042870B2 (en) | 2012-04-04 | 2021-06-22 | Blackhawk Network, Inc. | System and method for using intelligent codes to add a stored-value card to an electronic wallet |
| US8931043B2 (en) | 2012-04-10 | 2015-01-06 | Mcafee Inc. | System and method for determining and using local reputations of users and hosts to protect information in a network environment |
| EP2923325A4 (en) | 2012-11-20 | 2016-08-17 | Blackhawk Network Inc | System and method for using intelligent codes in conjunction with stored-value cards |
| US11349755B2 (en) | 2020-07-21 | 2022-05-31 | Bank Of America Corporation | Routing data between computing entities using electronic data interchange |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US4205371A (en) * | 1975-11-03 | 1980-05-27 | Honeywell Information Systems Inc. | Data base conversion system |
| JPS5992654A (en) * | 1982-11-09 | 1984-05-28 | インタ−ナショナル ビジネス マシ−ンズ コ−ポレ−ション | Electronic document distributing system |
| JPS60218142A (en) * | 1984-04-13 | 1985-10-31 | Hitachi Ltd | Dynamic format conversion system of data |
| US4680705A (en) * | 1985-09-13 | 1987-07-14 | International Business Machines Corporation | Automatic data restructurer |
| US4951196A (en) * | 1988-05-04 | 1990-08-21 | Supply Tech, Inc. | Method and apparatus for electronic data interchange |
-
1988
- 1988-05-04 US US07/190,147 patent/US4951196A/en not_active Expired - Fee Related
-
1989
- 1989-09-29 CA CA000615490A patent/CA1323107C/en not_active Expired - Lifetime
-
1990
- 1990-08-07 AU AU60257/90A patent/AU630218B2/en not_active Ceased
- 1990-08-20 DE DE199090115944T patent/DE471867T1/en active Pending
- 1990-08-20 ES ES90115944T patent/ES2034931T3/en not_active Expired - Lifetime
- 1990-08-20 DE DE69026252T patent/DE69026252T2/en not_active Expired - Fee Related
- 1990-08-20 EP EP90115944A patent/EP0471867B1/en not_active Expired - Lifetime
Also Published As
| Publication number | Publication date |
|---|---|
| AU6025790A (en) | 1992-04-16 |
| DE69026252T2 (en) | 1996-11-28 |
| DE69026252D1 (en) | 1996-05-02 |
| EP0471867A1 (en) | 1992-02-26 |
| ES2034931T3 (en) | 1996-08-01 |
| US4951196A (en) | 1990-08-21 |
| DE471867T1 (en) | 1993-02-04 |
| EP0471867B1 (en) | 1996-03-27 |
| ES2034931T1 (en) | 1993-04-16 |
| AU630218B2 (en) | 1992-10-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA1323107C (en) | Method and apparatus for electronic data interchange | |
| US5617528A (en) | Method and apparatus for interactively creating a card which includes video and cardholder information | |
| US5664182A (en) | Persistent storage of report objects | |
| US5490243A (en) | Data processing system for multi-platform print control and electronic data fill | |
| US4845634A (en) | Product information network system | |
| US4933880A (en) | Method for dynamically processing non-text components in compound documents | |
| EP1926050B1 (en) | Methods and apparatuses for generating composite images | |
| CA2573796C (en) | Improved unique identification labeling method and system | |
| US20010012008A1 (en) | Apparatus and method for managing schedule, and computer-readable storage medium storing schedule management program | |
| JP3487644B2 (en) | Graphical user interface creation device | |
| US6161116A (en) | Ideogrammatic character editor method and apparatus | |
| JP3376254B2 (en) | Display device, display control method, and recording medium | |
| JP2509982B2 (en) | Guidance screen control method | |
| JPH0731646B2 (en) | Electronic data exchange apparatus and method | |
| Fisher et al. | Acquisitions module | |
| JPS6142072A (en) | Data input/output terminal equipment | |
| Teran et al. | XVISION: a comprehensive software system for image processing research, education, and applications | |
| JP3632988B2 (en) | Item data processing device | |
| Omer et al. | DOMESTIC: a minicomputer based information storage and retrieval system | |
| JPH0330184B2 (en) | ||
| Huang et al. | Business graphics interface to databases | |
| JPH08171380A (en) | External character verification method and sub-mission system | |
| JPS622348A (en) | Date data input system | |
| JPH0554046A (en) | Device for preparing parts table and purchase specification | |
| Hardgrave et al. | DESIGN OF INFORMATION SYSTEMS USING SCENARIO-DRIVENTECHNIQUES |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| MKEX | Expiry |
Effective date: 20101012 |