WO2000023874A1 - Interface de navigation pour systeme erp - Google Patents

Interface de navigation pour systeme erp Download PDF

Info

Publication number
WO2000023874A1
WO2000023874A1 PCT/US1999/024859 US9924859W WO0023874A1 WO 2000023874 A1 WO2000023874 A1 WO 2000023874A1 US 9924859 W US9924859 W US 9924859W WO 0023874 A1 WO0023874 A1 WO 0023874A1
Authority
WO
WIPO (PCT)
Prior art keywords
document
node
sub
level
instance node
Prior art date
Application number
PCT/US1999/024859
Other languages
English (en)
Inventor
Gary W. Rush
Herman J. Kiefus
Original Assignee
Made2Manage Systems, Inc.
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Made2Manage Systems, Inc. filed Critical Made2Manage Systems, Inc.
Priority to US09/743,152 priority Critical patent/US7131069B1/en
Priority to AU11319/00A priority patent/AU1131900A/en
Publication of WO2000023874A1 publication Critical patent/WO2000023874A1/fr
Priority to US09/928,863 priority patent/US6981222B2/en
Priority to US10/910,487 priority patent/US20050240881A1/en

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0487—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser
    • G06F3/0489—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using dedicated keyboard keys or combinations thereof
    • G06F3/04895—Guidance during keyboard input operation, e.g. prompting
    • 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
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Definitions

  • the present invention relates to software interface systems, and in particular, to methods for providing quick and intuitive navigation to stored information normally available in different business documents.
  • ERP Enterprise Resource Planning
  • a business Prior to ERP software, a business would generally use different software applications to automate different functional departments of a business. For example, accounting, order entry, manufacturing, inventory and shipping departments would each use their own software systems. While these individual departments can achieve improved operational efficiency through software, the business as a whole would not realize the potential afforded by information technology because the individual software applications may not smoothly interface with each other, and there could be significant duplication of data across the individual systems.
  • ERP software With ERP software, all of the different functional applications for a business share a common database, so all data is entered only once. Moreover, there is a seamless integration of data between disparate applications, so data generated by one application can be immediately used by any other application. Due to the use of a comprehensive database, ERP systems permit enhanced analysis of a business' data.
  • ERP systems provide such comprehensive access to a business' data, they suffer from having an end user interface that is difficult to learn.
  • an ERP system is used by nearly every person in every operational department, even though each user only accesses a small portion of the data in the entire ERP system. This tends to make ERP user interfaces inherently complicated, particularly for end users that need to access information outside of the end user's normal area of expertise. For example, while a sales person may become proficient in accessing quotation or sales order information in an ERP system, if customer asks the sales person a question about the shipment or invoice for a particular order, the ERP user interface will usually make it difficult for the sales person find the information, because the user interface for shippers and invoices is likely to be unfamiliar to the sales person. Summary of the Invention
  • the present invention comprises a software system having a user-friendly navigational interface utilizing an hierarchical display of business documents based upon a dominant-subordinate relationship between the documents.
  • the documents are related through the use of keys, which define a relationship between the dominant and the subordinate documents.
  • the invention displays information related to that document.
  • the information to be displayed can be custom defined by the user.
  • each user can define a unique set of data to be displayed.
  • the invention further provides a means by which the underlying data can be easily edited from the hierarchical display.
  • the present invention also allows the creation of expressions that will alert the user to predetermined conditions.
  • the alert is displayed in conjunction with the hierarchical display of a document, but the expression may be defined by data not normally contained within the document.
  • each user can define a unique set of alerts for various documents based on conditions of particular interest to the user.
  • the present invention further comprises a visual rendering of predefined expressions describing the progress of work related to a document. This rendering may be based on data not normally contained within the given document.
  • each user can define a unique set of progress expressions for various documents based on conditions of particular interest to the user.
  • Fig. 1 is a representative excerpt of a pane showing a hierarchical arrangement of different types of business documents.
  • Fig. 2 shows a screen that may be used to specify the particular information to be displayed when a document or sub-document instance node is selected.
  • Fig. 3 shows a representative screen showing how options for displaying the hierarchical structure may be specified.
  • Fig. 4 shows an exemplary hierarchical relationships between demand business documents and subdocuments.
  • Fig. 5 shows an exemplary hierarchical relationships between supply business documents and subdocuments.
  • Fig. 6 shows an exemplary hierarchical relationships between general ledger business documents and subdocuments.
  • Fig. 7 shows a hierarchical display system in which document type nodes are displayed subordinate to a document instance node for those document types that actually exist for the particular document instance node.
  • Fig. 8 shows a pop-up box that permits an accessing screen for a particular business document (or sub-document) to be launched directly from the hierarchical tree structure.
  • Fig. 9 shows the screen of Fig. 3 with representative display parameter options and data filter options.
  • Fig. 10 is a representative data-editing screen for a customer record type business document.
  • Fig. 11 is a representative data-editing screen for part of a sales quote type business document.
  • Fig. 12 is a representative data-editing screen for the sales line item sub-document part of the sales quote type business document-editing screen of Fig. 11.
  • Fig. 13 shows representative icons that may be used to specify whether a particular Bill-of-Materials document is for a Make, Buy or Sell item.
  • Fig. 14 shows the levels of a branch in a tree structure in which both document type nodes and document instance nodes are used.
  • Fig. 15 shows the level of a branch in a tree structure in which only document type nodes and document instance nodes are used.
  • a "document” is a compilation of information commonly found in a business environment. Descriptions of specific types of documents related to an ERP setting appear below.
  • a "sub-document” is a portion of a document and comprises types of information that may appear multiple times.
  • a sales order line item may comprise a quantity, product description, unit price and extended price.
  • a sales order line item is a sub-document because it is included within a larger document, namely a sales order.
  • a "document instance node” is an entry in a hierarchical tree structure associated with an instance of a representation of a business document, which, when selected, allows information associated with the specific document to be displayed. In the preferred mode, the node is an icon with identifying information adjacent. Alternatively, the node could be in the form of Hypertext, with or without an adjacent icon.
  • the node-identifying information or hypertext displayed be sufficient to allow a user to uniquely identify the specific document.
  • a unique customer number, a unique customer name, or a unique composite of both customer number and customer name could represent a specific customer document.
  • Customer name alone may not be sufficiently unique if, for example, a business sells to two different branch offices of the same customer.
  • a "sub-document instance node" is an entry in a hierarchical tree structure that differs from a document instance node in that it is associated with a sub-document. This is useful within the context of the present invention since the line item of a document can form the bridge between two different business groups.
  • a sales force can create sales orders comprised of a list of products.
  • the manufacturing group must fill the entire order, it will be filled by fabricating the individual line items.
  • the line items function as a bridge between the sales documents and the documents associated with manufacturing the items.
  • a "document type node” is a node that is used to symbolize a class of business document types.
  • each "type” comprises a commonly used business document. Examples in an ERP setting include "Customers,” “Sales Orders,” “Job Orders” or “Accounts Payable Sub Ledger.”
  • instances of particular documents may be displayed in an immediately subordinate position to the document type node. Because, in one embodiment, the document type node is only a heading, it does not cause the display of information for a particular document.
  • the document type node is the mechanism by which all of the nodes subordinate to it can be collapsed or expanded to provide easier navigation of the hierarchical tree.
  • a "filter document type node” is a document type node that is displayed based on the evaluation of a "filter document type node expression.”
  • the filter document type node is displayed at the same level in the hierarchical tree structure as the document type node for the document instance for which the filter document type node expression was defined. Normally, the satisfaction of a filter document type node expression results in the filter document type node being displayed. While it is possible for the document instance node to only be displayed under the filter document type node and not the document type node when the filter document type node expression is satisfied, allowing the document instance to be displayed more than once in a given level allows for multiple filter document type node expressions to be defined for a given document.
  • a "filter document type node expression" is a predetermined, logical expression applied to data. It is not necessary that the data accessed to evaluate the logical expression be derived solely from the document referenced by a document instance node for which the filter document type node expression is defined. For example, a credit department manager might define a filter document type node expression for a customer document that evaluates to true if a customer's actual credit exceeds the business 's authorized credit limit for that customer, based on evaluation of accounts receivable information for the customer. In one embodiment, each user can define a set of filter document type node expressions unique to that user.
  • a "sub-document type node” is a type node that symbolizes a class of sub-document types. In one embodiment of the invention, the sub-document type node is the mechanism by which all of the nodes subordinate to it can be collapsed or expanded to provide easier navigation of the hierarchical tree.
  • a "filter sub-document type node” is a sub-document type node that is displayed based on the evaluation of a "filter sub-document type node expression.”
  • the filter sub- document type node is displayed at the same level in the hierarchical tree structure as the sub- document type node for the sub-document instance for which the filter sub-document type node expression was defined. Normally, the satisfaction of a filter sub-document type node expression results in the filter sub-document type node being displayed.
  • filter sub-document type node expression is a predetermined, logical expression applied to data. It is not necessary that the data accessed to evaluate the logical expression be derived solely from the sub-document referenced by a document instance node for which the filter document type node expression is defined.
  • a manufacturing manager might define a filter document type node expression for a job order line item that evaluates to true if a specific receiver document line item is entered.
  • each user can define a set of filter document type node expressions unique to that user.
  • a “container” refers to an array of elements wherein the elements may be, but need not be, of the same nature.
  • a container may comprise an element made up of an alphanumeric code, followed by an element comprised of no more than four numbers.
  • the container can be thought of as a bag, into which any desired data, of any form may be placed.
  • containers comprise representations of business documents and sub-documents.
  • An "entry point” is a document type that may be selected by the user as the starting point or root for a navigation tree. In one embodiment, this selection is made via the user interface, or by launching the hierarchical display from a screen in which the document is referenced, such as an editing screen.
  • a “point of interest” is a visual indicator that is displayed next to a document or sub- document instance node based on the evaluation of a "point of interest expression”. Normally, the satisfaction of a point of interest expression indicates a warning condition so as to alert the end user that further investigation is warranted.
  • a “point of interest expression” is a predetermined, logical expression applied to data.
  • the data accessed to evaluate the logical expression be derived solely from the document referenced by a document instance node next to which the resultant point of interest indicator would be displayed.
  • An end user who is a credit manager may set a point of interest expression for a customer document that evaluates to true if a customer's actual credit exceeds the business's authorized credit limit for that customer, based on evaluation of accounts receivable information for the customer.
  • a “key” is a code that can be shared by two or more containers, pursuant to which there is a one-to-one or a one-to-many relationship between the two or more containers. This is accomplished in one embodiment by utilizing the concept of "primary key” and "foreign key” which is well known in the art. For example, where one container comprises a customer document, it may have a unique key that may be a unique customer name. This could be the primary key for the customer document.
  • a quote business document may include or incorporate that unique customer name as a part of the unique quote business document identifier. However, the customer primary key comprises a foreign key when it is in the quote business document container.
  • a sales order associated with that particular customer may merely append a code such as SO-001 to the customer primary key (signifying sales order 001). While in the sales order container, the key “Joe's- SO-001" would be the primary key, while “Joe's” would be a foreign key.
  • a "pane” comprises a two or three-dimensional area displayable on a computer screen. In one embodiment, both the first and second panes are displayed in a single window in a windows-based operating system, but the panes could also be displayed in different windows.
  • a "user class” is a uniquely identifiable group of users. It is possible, but not necessary to define a user class for each unique user.
  • a “visual progress bar” is a visual representation of the evaluation of a "visual progress bar expression”.
  • the representation in the preferred embodiment is in the form of a bar graph which progresses from zero (0) to one hundred (100) per cent based upon the evaluation of the visual progress bar expression.
  • a "visual progress bar expression” is a user defined expression that evaluates to a numeric value. In one embodiment the expression is of the form x/y and evaluates to a number between 0 and 1. The expression may evaluate any data within the system.
  • a "breakpoint" is an expression that is defined by the user in conjunction with the visual progress bar expression, such that the color of the bar changes (e.g., from green to yellow to red) at predetermined values of X/Y.
  • the invention further provides a means for reversing the order of the colors, such that the bar changes (e.g., from red to yellow to green) as the expression approaches one hundred (100) per cent.
  • a "layer” is a dominant-subordinate relationship between documents or sub- documents of the same type wherein the subordinate document or sub-document represents a constituent part or step of the dominant document or sub-document.
  • a "representation of a business document” means a computer memory storing at least the minimal amount of information needed for a business document. In one embodiment the information is stored within containers. While a virtually unlimited number of permutations exist within various business settings, the minimal information for a reasonably useful system for the following documents in an ERP setting is as follows:
  • Customer a unique customer identifier. This is normally a customer number or an email address. However, this may also be a customer name. Although not required, a customer record will often include an address, phone number, contact name, and credit limit;
  • Quote a unique customer identifier, at least one quoted item, and a quoted pricing basis.
  • the word "item” in this context need not refer to a discrete unit of a particular good.
  • the pricing basis may be as generic as "market value”. Additional information which is not necessary, but which may be present in a quote includes, but is not limited to, available discounts for bulk purchases, shipping arrangements, and date of delivery information. Since there is not necessarily a contract at this point, the quoted price is an estimate of the final price;
  • Quote Item Bill of Material (BOM): a uniquely identified quote and at least one quoted item.
  • the item is a discrete unit, and the BOM is a discrete item.
  • Quote Item Routing Step at least one quoted item and at least one operation.
  • the operation may be as simple as transporting an item from place "A" on the manufacturing floor to place "B". However, this feature is particularly useful in make to order contexts where a routing step indicates a customization of a base product;
  • Sales Order a unique customer identifier, a unique sales order identifier, at least one item, and a pricing scheme.
  • a simple sales order is exemplified in an over the counter sales.
  • an over the counter sale comprises information such as a definite quantity and price, which would not be present in a sales order for "all the items which can be produced in a month.”
  • a per unit pricing scheme possibly incorporating an incentive scheme.
  • Other information which may be associated with a sales order would be a destination, a quantity, a release date, method of payment, and a need date.
  • the price and the item in a sales order are definite, as contrasted with the quoted price and quoted item of a quote. This is not to say that the final cost is definite, as the price may be on a per unit basis;
  • Sales Order Item Release a unique sales order identifier, at least one item, and an indication of time. While the indication of time might be as simple as "when available", a sales order item release is particularly useful when a customer prefers to have delivery of purchases staggered over some period of time. In this context, a sales order item release might also include a quantity of items to be released on a specific day. This arrangement allows a price to be established based on a large number of items being purchased, while not creating an excessive need for manufacturing or warehouse capacity since delivery is spread out over time. Additional information may include shipping information;
  • Sales Order Item Bill of Material (BOM): a unique sales order, and at least one item. Sales order BOMs are used to track the complete list of materials comprising the sales order item;
  • Sales Order Item Routing Step a unique sales order item and at least one operation
  • Job Order a unique job order identifier, and an item identifier.
  • Other fields which can be usefully associated with a job order include a release date, a need date, and fields to accumulate costs against the job order. Typical cost fields include material, labor, and overhead;
  • Job Order Bill of Material (BOM): a unique job order identifier, and at least one item.
  • Job Order Routing Step a unique job order identifier, at least one item, and at least one operation.
  • a shipper when used to send a product to a customer, a shipper comprises a unique customer identifier, at least one item to be shipped, and a means for determining a shipping date.
  • a shipper may be used when shipping an item to a sub-contractor.
  • the shipper comprises a unique vendor identifier, at least one item to be shipped, a purchase order identifier, and a means for determining a shipping date.
  • this document will also contain freight and shipping charges, and a carrier.
  • additional information within a shipper optionally comprises freight and shipping charges, a carrier, and the back order quantity. Other useful information may include the source of the items to be shipped.
  • Accounts Receivable (AR) Invoice a unique invoice identifier, a unique customer identifier (this may be an element of the invoice identifier), a quantity of items, a date, and an accumulation of prices for the items.
  • This document will frequently incorporate freight and shipping charges, and carry a total accumulation for items and other charges;
  • Accounts Receivable (AR) Payment a unique payment identifier, a date, an amount, and an accounts receivable invoice identifier.
  • General Ledger Account Category at least one unique general ledger account category. Typically, categories will include assets, liabilities, shareholder's equity, revenue from sales, expenses and cost of goods sold;
  • General Ledger Account a unique account identifier, and a general ledger account category
  • General Ledger Account posting a unique posting identifier, a general ledger account, and an amount
  • General Journal Entry a unique general journal entry identifier, a general journal identifier, an amount and a date;
  • Accounts Payable Sub Ledger a unique AP sub-ledger identifier, and a general journal identifier;
  • Accounts Payable (AP) Invoice unique AP invoice identifier, a unique vendor identifier, at least one item, a quantity, at least one price, and a date;
  • Accounts Payable (AP) Payment a unique payment identifier, a date, an amount, and an AP invoice identifier.
  • Accounts Receivable (AR) Sub-Ledger a unique AR sub-ledger identifier, and a general journal identifier;
  • Payroll Sub-Ledger a unique payroll sub-ledger identifier, and a general journal identifier
  • Order Costing Sub Ledger a unique order costing sub-ledger identifier, and a general journal identifier
  • Vendor a unique vendor identifier
  • Purchase Order a unique vendor identifier, a unique purchase order identifier, at least one item, and a pricing scheme;
  • Purchase Order Item Release a unique purchase order identifier, at least one item, and an indication of time;
  • Receiver a receiver identifier, a vendor identifier, at least one item, a quantity of the item(s), and a date. Some documents will include the name of the individual accepting receipt.
  • a "representation of a sub-document” means a computer memory storing at least the minimal amount of information needed for a sub-document. In one embodiment the information is stored within containers. While a virtually unlimited number of sub- documents exist within any given business setting, the minimal information for some exemplar sub-documents within an ERP setting is defined:
  • Quote Item a unique item identifier and a quote identifier, other information that may be listed includes need date and pricing information;
  • Sales Order Item a unique item identifier and a sales order identifier
  • Shipper Item a unique item identifier and a shipper identifier
  • Purchase Order Item a unique item identifier and a purchase order identifier
  • Receiver Item a unique item identifier and a receiver identifier
  • Accounts Receivable (AR) Invoice Item a unique item identifier and an invoice identifier
  • Accounts Payable (AP) Invoice Item a unique item identifier and an AP invoice identifier.
  • the present invention relates to a quick and informative interface means for presentation of, and navigation through, stored information from different business documents.
  • the invention allows a user to navigate through the information utilizing a means for displaying an hierarchical tree structure reflecting relationships between different types of business documents.
  • the present invention creates a hierarchical tree structure by defining relationships between different types of business documents as they are encountered in a typical business environment.
  • typical "types" of business documents within an ERP setting include, but are not limited to, quotes, sales orders, customers, job orders, shippers, invoices (AR and AP), BOMs, routing steps, releases, payments (AR and AP), vendors, purchase orders, receivers, GL account categories, GL accounts, GL account postings, GL entries, AP sub-ledgers, AR sub-ledgers, payroll sub- ledgers, and order costing sub-ledgers.
  • the documents may include x-ray negatives, office visit documentation, health insurance provider information, health history, and prescription drug history.
  • Other documents in the above settings and other business settings will be obvious to those skilled in the art, and are within the scope of the present invention.
  • the documents are displayed to the user, in the preferred embodiment, so as to indicate in a visual manner, the relationship that exists between the documents, as will be defined below. This is accomplished by means of levels and branches, wherein entries within a branch have the same basis, such as the same customer or the same sales order, while entries in the same level will all be of the same type, such as all customers, or all quotes.
  • the hierarchical structure is based upon a dominant-subordinate relationship between adjacent levels. This relationship means that for a given branch, a dominant entry may have one or many entries in an adjacent subordinate branch. However, an entry within a subordinate level will only have one entry in the immediately adjacent dominant level within the same branch. It is important to note that a given entry may exist on more than one branch, while not violating the above relationship. For example, with reference to Fig. 4, one may navigate from customer (level 1) to sales order (level 2) to shipper (level 3), or, from customer (level 1) to shipper (level 2). Navigation is described more fully below. Further, it is possible to have a plurality of levels between two entries of the same branch, while maintaining a dominant-subordinate relationship with respect to the two entries. For instance, in the above example, customer is dominant to shipper, regardless of whether or not one navigates through an intermediate sales order document.
  • the relationship is described as being dominant - subordinate - sub-subordinate.
  • the dominant-subordinate relationship is as defined above.
  • a dominant-subordinate relationship exists between the subordinate and sub-subordinate entry.
  • the relationship between the dominant and sub-subordinate entry would be a dominant-subordinate one.
  • the three entries can be, but need not be, in immediately adjacent levels.
  • the existence of a particular document entry is symbolized by a document instance node, which can be, but need not be, in the form of an icon. Icons associated with document instance nodes may be, but need not be, of different visual characteristics based on the type of document in conjunction with which they are used.
  • document instance nodes may be, but need not be, grouped under another icon that indicates the type of documents in the particular group. This node is defined as a document type node.
  • document type nodes may be, but need not be, an icon, having different visual characteristics based on the type of document in conjunction with which the icon is used.
  • Tree structure 1405 comprises three levels, indicated by columns 1410, 1415, and 1420.
  • Level 1415 is subordinate to level 1410 and dominant to level 1420, and level 1420 is subordinate to both level 1410 and level 1415.
  • one type node 1425 is displayed along with two instance nodes 1430 and 1435.
  • Type nodes 1440 and 1445 are displayed in subordinate level 1415.
  • Instance nodes 1450 and 1455 are of the same type, since both are shown under type node 1440, and both are related and subservient to instance node 1430.
  • Instance nodes 1430, 1450, and 1455 are all in the same branch.
  • Instance nodes 1460 and 1465 are shown under type node 1445.
  • instance nodes 1470 are shown in level 1420. Thus, instance node 1470 would be subordinate to instance nodes 1450 and 1430, but not 1455. Further, instance node 1470 is of the same branch as instance nodes 1450 and 1430, but it is not of the same branch as instance node 1455.
  • type nodes are not used in the present invention.
  • a representative tree structure for this embodiment is shown in Fig. 15, which like Fig. 14 displays three levels, 1510, 1520, and 1530.
  • the instance nodes shown in Fig. 15 have the same relationships as the instance nodes in an embodiment incorporating type nodes. Namely, instance node 1550 is subordinate to instance node 1540, and of the same branch as instance node 1540. Instance node 1560 is subordinate to both instance node 1540 and instance node 1550, and of the same branch as instance nodes 1540 and 1550. At the same time, instance node 1570 is subordinate to and of the same branch as instance node 1540, but instance node 1540 is not of the same branch as instance node 1550.
  • the user has the option of further filtering document and sub- document instances (which will be described below).
  • the user may define a specific data or group of data as a filter document type node expression or filter sub-document type node expression such that when the expression is met, the document or sub-document in which that data is resident will be shown subordinate to the filtering document type node or filter sub- document type node.
  • a customer document may be presented below a customer document type node as shown in Fig. 7.
  • filtering document type expression for any customer having an outstanding invoice greater than thirty days, and named that filter document type node "Accounts Overdue," and customer 000100 - AIR APPLICATIONS INC.
  • customer document 000100 - AIR APPLICATIONS INC. would be shown subordinate to "Customers" document type node in addition to "Accounts Overdue” filter document type node. Further, the "Accounts Overdue” filter document type node would be displayed at the same indentation as the document type node "Customers.”
  • the document or sub-document may be displayed alternatively, or redundantly. This does not violate the one-to-one or one-to-many dominant- subordinate relationship defined above in that there is only one instance being referenced. It is merely being redundantly presented to the user.
  • the document and sub-document instance nodes may, but need not, be acted upon and navigated from just as an instance node under a document or sub-document type node.
  • Instance nodes 1610 and 1620, and 1630, 1640 and 1650 are displayed subordinate to type nodes 1660 and 1670 respectively, indicating relationships defined above.
  • Instance node 1690 is likewise displayed subordinate to instance node 1610.
  • the identical tree is shown in Fig. 17, with the exception that a filter document type node expression has been defined, and instance node 1610 satisfies the logical expression. Consequently, filter document type node 1675 is displayed with instance node 1680 listed underneath.
  • the actual instance associated with instance node 1680 is the same instance that is associated with instance node 1610.
  • instance node 1680 is in all functional respects identical to instance node 1610.
  • Document instance nodes are associated with stored computer memory comprising representations of business documents. Thus, each instance node may be thought of as being associated with a specific document. Although each node has a discrete set of information associated with the node, the specific information contained within the computer memory may be, but need not be, defined as part of more than one document.
  • the displayed hierarchical tree structure of the present invention is based upon entry points.
  • An entry point is a document that the user designates as the highest-level for a tree.
  • the invention in the preferred embodiment defines a variety of potential entry points based on the normal flow of business documents in an ERP setting, the varieties of analysis that a business performs, and the specialized knowledge that can be expected within the different business groups of an enterprise. For example, in the scenario where a salesperson is visiting Customer B and Customer B has reason to know what quotes had been provided to Customer A, the salesperson would be interested in obtaining the quotes given to Customer A.
  • the invention defines a customer document as an entry point and, as will be explained more fully below, the invention provides a means for navigating from a particular customer document (entry point) to the quote documents (subordinate documents) associated with that customer.
  • While the above example shows arrival at a specific quote from a customer document entry point, it is sometimes useful to enter the system by way of another entry point while accessing the same type of document. For instance, if one is tracking sales history and desires to understand seasonal variability, it is more useful to look directly at sales order documents generally rather than being limited to those of a specific customer. Thus, it is more convenient to look directly to sales order documents, rather than navigating through customer documents, thereby avoiding the extraneous level as well as not over constraining the documents available for exploration. Finally, a sales representative would be knowledgeable as to specific quotes and sales orders. A production manager would be familiar with particular job orders. The shipping department would have special interest in shipping activity, and accounting department personnel would be interested in invoices.
  • entry points those documents, among others, are designated as entry points.
  • Other entry points or groupings of entry points will be obvious to those skilled in the art as being appropriate for specific applications, those entry points and groupings of entry points are within the scope of the present invention.
  • means for selecting a node comprises an interface of a cursor controlled by a mouse. Navigation from the entry point is then accomplished by moving the cursor to the desired node and double clicking, or by right clicking the mouse, which causes a menu to appear, and choosing an explore option. Either action may cause nodes subordinate to the selected node to alternately be expanded or collapsed. Once a subordinate node is exposed, repeating the above sequence with the desired subordinate node may further expand the branch. In one embodiment, the above operation can be performed on instance nodes subordinate to document and sub-document type nodes as well as on instances subordinate to filter document and sub-document type nodes.
  • the invention further allows navigation through certain sub-documents, using the sub- document as a bridge between documents of different types. This is useful particularly in the case of line items. For example, a single sales order comprises several line items. Each of the line items has the potential for spawning several job orders. Thus, it is less confusing to a user to differentiate job orders according to the line item they are associated with, rather than presenting all the job orders related to a sales order. Consequently, the present invention comprises representations of sub-documents, sub-document instance nodes, sub-document type nodes, and filter sub-document type nodes having the same system characteristics as representations of documents, sub-document instance nodes, sub-document type nodes, and filter document type nodes, respectively.
  • the allowed paths are displayed to the user as branches that may be alternatively investigated from a given entry point or root.
  • the entry point chosen by the user may be represented as the root level of the document tree, and is dominant to the subordinate document or sub-document, which may be navigated to directly from the root level.
  • subordinate levels are displayed as an indented list immediately below the entry point. While the branch level is in a subordinate relationship to the root level, as a given branch is explored, the branch becomes a dominant level to ensuing branches that are listed below the explored branch.
  • the branch level is in a subordinate relationship to the root level, as a given branch is explored, the branch becomes a dominant level to ensuing branches that are listed below the explored branch.
  • the top level the "root"
  • Alternate embodiments permit multiple entry points to be shown at the top level.
  • One embodiment allows multiple instance nodes for the same business document or subdocument.
  • this is allowed when an instance has a filter document type node expression defined.
  • the instance has a document instance node displayed subordinate both to the document type node as well as to the filter document type node.
  • Navigation paths in the present invention are defined by relationships between the different documents and sub-documents.
  • the means for relating documents and or sub-documents is a key.
  • a key will uniquely identify one container. This is the primary key for the container. For example, a customer container may have a primary key of 1001. If a container representing a sales order document is created which will relate to 1001, the container will incorporate customer no. 1001 as a foreign key, while being uniquely identified by its own primary key, SO2002, for example.
  • the document or subdocument to be navigated to must be of a type to which navigation is allowed as defined by the keys that relate documents to each other.
  • the container representing the subordinate document or sub-document must have, as a foreign field, the key which is present as a primary key in the dominant document or sub-document.
  • the subordinate document or sub-document must incorporate as a foreign key, any foreign key that was used in order to navigate to its immediately dominant document or sub- document.
  • container SO2002 When container SO2002 was defined, it incorporated as a foreign field the primary key of the customer who made the order, in this example, 1001. Thus the second principle is satisfied. Since only two levels are involved, the third principle is met when the second principle is met. The third principle differs from the second principle when the user further explores the branch, SO2002. For example, if the job order had been completed, and the product shipped, a shipper document, SH3003 would have been created. SH3003 would be the primary key, while 1001 and SO2002 would be foreign keys for SH3003. Thus, continuing the above example, the user would be allowed to navigate to SH3003 since navigation is allowed from a job order to a shipper, SH3003 has SO2002 as a foreign key, and SO2002 has 1001 as a foreign key.
  • the present invention also incorporates layers, such that immediately adjacent subordinate levels may, but need not, comprise component documents or layers of the dominant document.
  • a quote document comprises an automobile
  • quote item sub-documents comprise a power package and a sound package.
  • the sound package may, but need not, include a remote CD player.
  • the sub-document representing a CD player option comprises a sub-layer quote item sub-document.
  • the remote CD player routing step document would include installation of the remote unit in the trunk.
  • the running of wire from the remote unit to the local unit would be represented by a sub-layer routing step document.
  • both documents and sub-documents can be layered.
  • the present invention further comprises means for defining the information, related to the representation of a business document or subdocument, which will be displayed when a document instance node is selected. The information that is identified by the user is then displayed when the associated instance node is selected.
  • any information within the ERP system may be identified for display. While the information will predominantly comprise data from the selected document or sub-document, a user may identify information not normally associated with the document or sub-document. For example, a sales person interested in displaying information regarding outstanding sales orders for one customer, while interested only in the available credit for another customer, could identify this information for the individual customer such that as the customer documents are selected by the sales person, this information is displayed. In the preferred embodiment, the information is displayed to the user adjacent a user defined label such as, but not limited to, "Days Late".
  • each individual user defines the information according to their particular job needs, and this identification of information is stored within the system during the computer session. The information is also maintained by the system between sessions, available to be recalled whenever the user accesses the system and selects the applicable node.
  • users are grouped into user classes, sometimes referred to as "roles", that have common information needs. For example, shipping clerks may all be defined as a single user class, while the president of a company may be the sole member of a user class.
  • the unique identification of users and or groups of users and storage of user unique information are well known in the art.
  • the invention comprises a means for displaying the information so designated.
  • the means for displaying information includes but is not limited to a pane within a window.
  • the invention also allows information within the system to be evaluated, and the results displayed graphically. This is accomplished by providing points of interest and visual progress bars.
  • the point of interest in the preferred embodiment is user definable, and stored and maintained within the system.
  • the user defines a point of interest expression that is in the form of a logical expression, which resolves to true or not true.
  • the system assesses the underlying information and results are then displayed to the user by a means for displaying a point of interest.
  • the display is in the form of an icon that appears when the expression evaluates to true, and is displayed next to the instance node for which the expression is defined.
  • a visual progress bar in one embodiment, is also user definable, and stored and maintained within the system.
  • the displayed visual progress bar is also based upon an expression.
  • the expression for a visual progress bar is in the form of X/Y, and attains a maximum value of one (1).
  • the system computes a value based on the underlying information and results are then displayed to the user by a means for displaying a visual progress bar.
  • the display is in the form of a progress bar and text.
  • the present invention further comprises a means for accessing the representation of a business document that is being displayed.
  • a means for launching the accessing means is further provided.
  • the accessing means allows the user to view or edit the representation of a business document. Consequently, a user may edit the representation of a business document by right clicking on the document instance node associated with the representation of a business document.
  • editing comprises capabilities such as adding, deleting, and altering.
  • a means for limiting the nodes displayed to a user is also provided. This should not be confused with the function of filtering document and sub-document type nodes described above.
  • the means for limiting displayed nodes in the preferred embodiment comprises a filter text box, into which letters, numbers and wildcards may be placed to limit the nodes displayed by the invention, including those displayed subordinate to filter document and sub- document type nodes.
  • the invention also comprises a means for launching the navigational software which may be imbedded into the system software, such that while a user is using an interface for displaying information in a representation of a business document, the user may launch the navigational software from that interface.
  • the navigational software places a node associated with the representation of a business document that was being viewed as the root for the hierarchical tree structure.
  • Typical "types" of business documents within the ERP setting comprise, but is not limited to, quotes, sales orders, customers, job orders, shippers, invoices (AR and AP), BOMs, routing steps, releases, payments (AR and AP), vendors, purchase orders, receivers, GL account categories, GL accounts, GL account postings, GL entries, AP sub-ledgers, AR sub-ledgers, payroll sub-ledgers, and order costing sub-ledgers.
  • demand-side state machine 410 is described.
  • Customer document 415 comprises the highest-level entry point of demand-side state machine 410.
  • the usefulness of entering at customer document 415 is described above.
  • Quote 420, sales order 425, job order 430, shipper 435, and AR invoice 440 also comprise entry points for demand- side state machine 410, such that a user may navigate using these entry points as the root level of the tree. It is useful to enter at quote documents 420 in order to perform business analysis. For instance, in assessing the appropriateness of a product's price, a salesperson may want to know if an item has been quoted frequently, but rarely sold. This might indicate that the product is overpriced.
  • customer document 415 From customer document 415, direct navigation is possible to quote document 420, sales order document 425, job order document 430, shipper document 435 of demand- side state machine 410, AR invoice document 440, or AR payment document 445.
  • Customer Related Documents Moving from customer document 415 to quote document 420 is useful when a salesperson is attempting to ascertain quotes given to a particular customer as has previously been discussed. Moving from customer document 415 to sales order document 425 is useful for understanding the purchase history of a particular customer. A salesperson may use this to ascertain when the next call to a customer should be made. A salesperson may navigate from customer document 415 to job order 430 if a customer has recently had a fire and can not receive any products. The salesperson can rapidly ascertain job order documents 430, representing work in progress, under customer document 415 and put them on hold.
  • Navigation from customer document 415 to shipper document 435 of demand-side state machine 410 is useful when the customer represented by customer document 415 inquires as to the status of a shipment that is late. The user enters the system at customer document 415 and navigates to shipper document 435 of demand-side state machine 410 to determine whether the shipment is in transit or sitting on the loading dock. Similarly, if a customer inquires as to a recently delivered bill, user can enter at customer document 415 and navigate to AR invoice document 440 to ascertain the basis for the billing. The same customer perspective is useful when an issue arises as to what invoice a particular payment was applied to. The AR clerk or manager would enter at customer document 415 and navigate to AR payment document 445 to find the needed information.
  • the present invention provides a navigation path from sales order document 425 to shipper document 435 of demand-side state machine 410 so that a salesperson may ascertain the status of a specific order upon inquiry from a customer.
  • a salesperson may ascertain the status of a specific order upon inquiry from a customer.
  • the actual status of the product can be ascertained by navigating to sales order item release document 470 to determine if the item had been released for production and/or for shipping. From sales order item release document 470, navigation is allowed to either job order document 430, to determine where in production the item is, or to shipper document
  • Navigation from job order document 430 to job order BOM document 485 or job order routing step document 490 is useful in gathering information as to the status of a product which has been released for production. Should the sales person in the above example opt to navigate from sales order item release document 470 to job order document
  • Navigation from shipper document 435 of demand-side state machine 410 to shipper item sub-document 495 of demand-side state machine 410 is useful for a shipping manager who knows a shipment is supposed to go to a customer, but does not recall the specific items to be loaded. Navigation from shipper item sub-document 495 of demand-side state machine
  • AR invoice document 440 is needed when personnel in accounts receivable are attempting to reconcile a global payment from a customer that covers all or parts of several shippers.
  • AR Invoice Related Documents Many times a payment will be for less than an entire AR invoice. In these circumstances, the invention allows for navigation from AR invoice document 440 to AR invoice item sub-document 497.
  • AR payment 45 from customer 415 as described above.
  • navigation is useful, for example, from AR invoice item sub-document 497 to AR payment document 445, for accounts receivable personnel rectifying payments received against a specific AR invoice.
  • Vendor document 510 comprises the highest-level entry point for supply side state machine 505.
  • a production manager may desire to begin a tree at the vendor document level in order to if it is known that a product has been shipped to a particular sub-contractor, but the purchase order number is not known.
  • purchase order document 515, shipper document 520 of supply side state machine 505 receiver document 525 and AP invoice document 530 are provided as entry points in the preferred embodiment.
  • a salesperson receiving an inquiry as to the meaning of a specific purchase order item may be given a purchase order number as a reference and enter at purchase order document 515.
  • the same salesperson may use a number or receiver number in asking the shipping clerk whether a product is sitting on the loading dock. Therefore, the shipping clerk would enter the navigation tree at shipper document 520 of supply side state machine 505 or receiver document 525 respectively.
  • An accounts payable clerk may be given an invoice number when asked about the status of paying a vendor, thus entering the tree at AP invoice document 530. Consequently, the preferred embodiment has defined the above entry points to minimize the navigation required to obtain the desired information.
  • navigation paths through supply side state machine 505 are defined.
  • Navigation from vendor document 510 to purchase order document 515 is of use in several instances. One example is for accounts payable personnel attempting to determine the number of open orders that exist for a given vendor.
  • Navigation from vendor document 510 to shipper document 520 of supply side state machine 505 is useful for a sales person desiring information on the status of a product that has sub-contract work to be performed on the product.
  • Navigation from vendor document 510 to receiver document 525 is useful for determining if the product has returned from the sub-contractor.
  • Navigation from vendor document 510 to AP invoice document 530 is useful for a manager interested in performing a price comparison between vendors.
  • Navigation is provided from purchase order document 515 to purchase order item sub- document 535 and thence to purchase order item release document 540, which is useful for determining the status of sub-contracting work which is done in support of a contract of the type discussed under sales order item release document 470 of demand state machine 410 of Fig. 4.
  • a salesperson investigating a late delivery can ascertain whether the shipment to the sub-contractor has been released.
  • navigation from purchase order document 515 or purchase order item release document 540 to shipper 520 of supply side state machine 505 allows a salesperson to determine if the product has been shipped to the vendor for the sub-contracted work to be performed.
  • Navigation from purchase order document 515 to receiver document 525 is useful in determining if the product has been returned from the vendor.
  • Navigation from receiver document 525 to receiver item sub-document 550 is useful for ascertaining the specific items that were received from a sub-contractor. In conjunction with shipper item sub-document 545 of supply side state machine 505, this allows a complete inventory of items at a sub-contractor to be determined. Navigation from receiver item sub- document 550 to AP invoice document 530 is useful for accounts payable personnel in determining whether an invoice for a particular item has been received.
  • Navigation from AP invoice document 530 to AP invoice item sub-document 555 is useful in determining the specific items that are being billed under AP invoice document 530.
  • Navigation from AP invoice document 530 to AP payment document 560 is useful in determining the status of paying vendors for work performed.
  • GL drill-down state machine 605 is explained.
  • the highest level entry point for GL drill-down state machine 605 is GL account category document 610.
  • This entry point is provided for users who are not familiar with the various accounts in the general ledger, so as to be an aid in determining an exploration path.
  • GL drill-down state machine 605 is GL account document 615 which is useful for experienced users who know the account they are interested in.
  • navigation paths of GL drill-down state machine 605 are described.
  • Navigation from GL account category document 610 to GL account document 615 is used to begin focus on a specific GL account, such as but not limited to assets, liabilities, and shareholders' equity.
  • Navigation from GL account document 615 to GL account postings document 620 is useful for viewing cash flow within a specific account without the confusion of daily fluctuations.
  • Navigation from GL account postings document 620 to general journal entries sub-document 625 is useful in focusing on activity on a daily basis, allowing analysis of trend lines for any account in any account category.
  • Navigation from general journal entries sub-document 625 to the ledgers comprising the entry allows for increased focused on the ledgers which is useful, for example, in performing cost analysis.
  • the ledgers comprise AP sub-ledger document 630, AR sub-ledger document 635, payroll sub-ledger document 640, and order costing sub-ledger document 645.
  • the information within the aforementioned documents within this state machine comprises compiled information.
  • the relationship between the compilation information and the primary instances is captured by navigation from AP sub-ledger document 630 and AR sub-ledger document 635, to AP invoice document 650 and AR invoice document 665 respectively.
  • AP invoice document 650, AP invoice item sub-document 655, and AP payment document 660 are the same containers as AP invoice document 530, AP invoice item sub- document 555, and AP payment document 560 of Fig. 5.
  • each hierarchy level includes two nodes: a document type node, and a document instance node.
  • a document type node For example, the following table illustrates, the node type and hierarchy level numbers for a representative set of records:
  • the document type nodes are optional, as they are not necessarily needed to display information from a particular business document. Accordingly, the document type nodes may be eliminated entirely from the levels of each hierarchy. In such a system, for example, the above representative hierarchy could be displayed as follows.
  • a child business document in a hierarchy may be expanded or collapsed by, for example, double clicking on the parent business document.
  • the machines in the preferred embodiment define a set of paths and entry points that will be useful in a wide variety of applications. It will be obvious to those skilled in the art that virtually any navigational path between documents can be programmed into a system, and the present invention includes within its scope alternate entry points and or paths that may be defined for an application. The salient feature being that navigation between documents and/or sub-documents of different types is allowed.
  • Explore tab 10 contains the primary visual objects that the user interacts with when locating or reviewing information.
  • Explore tab 10 comprises the means for displaying a hierarchical tree structure shown by navigation pane 20, and the means for displaying information embodied as properties pane 30.
  • the relative sizes of the panes may be adjusted by placing the mouse cursor (not shown) between the two at or about dashed line 25 and then clicking and dragging the mouse to yield the desired proportion.
  • a list of document types is displayed in text box 41.
  • This list is limited to documents that are entry points. In the prefe ⁇ ed embodiment, sub-documents are not entry points.
  • the documents which are entry points include customer, quote, sales order, job order, shipper, AR invoice, vendor, purchase order, receiver, AP invoice, G/L account category, and G/L documents.
  • Choosing a specific document type causes text box 50 to resize, according to the selection made, and that control receives focus.
  • Text box 50 displays unique document identifiers, allowing the user to specify a particular document from which tree view control 60 is refreshed. Lookup capability is associated with this control through binocular button 70.
  • tree view control 60 which is a hierarchical tree structure of document instance and type nodes.
  • tree view control 60 is a commercially available control such as can be provided by Sheridan Software Systems, Inc. of Melville New York, which is discussed in more detail below.
  • Tree view control 60 contains the result of the cu ⁇ ent search criterion of locator 80, combo box 40, or text box 50.
  • Tree view control 60 contents are not removed until a new search criterion is specified. It is via tree view control 60 that the user navigates to related documents or sub-documents, initiates further exploration from, and receives certain visual feed back pertaining to the state of a document.
  • type nodes such as type nodes 80, 81, 82, 83, and 84
  • instance nodes such as instance nodes 90, 91, 92, 93, 94, 95, and 96.
  • type nodes 80, 82, 83, and 84 are document type nodes, which indicate that the documents listed underneath the nodes are of the same type.
  • BOM Bill of Material
  • Document instance nodes such as document instance nodes 90, 92, 93, 94, 95, and 96 identify a specific instance of a document.
  • sub-document type node 81 and sub-document instance node 91 are also shown in tree view control 60. These nodes function in the same manner as document type nodes and document instance nodes. However, the nodes are associated with subsets of a document such as the specific line items in a sales order as represented by sub-document instance node 91.
  • Fig. 8 shows explore tab 10. Cursor 805, indicated by the shaded rectangle, has been placed over job order instance node 810. By right clicking, pop-up menu 815 is displayed. Pop-up menu 815 comprises 5 actions, namely, "Go To”, “Expand”, “Collapse”, “Zoom In”, and “Zoom Out.” When selected, "Go To” causes an editing screen for the selected business document (or sub-document) to be launched directly from tree view control 60.
  • Data editing screen 1000 shown in Fig. 10, is an embodiment of a data-editing screen for a customer document.
  • Data-editing screen 1100 of Fig. 11 is an embodiment of a data-editing screen for a quote document
  • data-editing screen 1200 of Fig 12 shows an embodiment of a data- editing screen for a sales line item sub-document.
  • the "Expand” option expands one branch of the tree view. This operation is analogous to clicking on the '+' appearing to the left of the node.
  • the "Collapse” option collapses one branch of the tree view. This operation is analogous to clicking on the '-' appearing to the left of an expanded node.
  • "Zoom In” performs an exhaustive depth first exploration (explosion) from a chosen node. Rather than double clicking down a series of documents, the user can apply this operation to a node to see all related contents. This operation can expose a vast amount of information from hundreds to possibly thousands of nodes. The breadth of its execution is bound by a user-defined option (described below). "Zoom Out” is opposite the "Zoom In” operation.
  • the "Explore” option (not shown) is available on type nodes and drives the query to the next state in the state machine. This is the default double click behavior for a node.
  • job order document type nodes such as job order document type node 83
  • a document or sub-document type node will only appear as a subordinate document type node if the data base contains an instance node of the applicable type which is appropriately related to the dominant instance node.
  • the display of document type nodes 705, 710, 715, and 720 indicate that there are instance nodes subordinate to those type nodes.
  • job order document type node 725 must be explored.
  • the prefe ⁇ ed embodiment displays a subordinate job order type node such as job order type node 725 whenever demand-side state machine 410 of Fig. 4 indicates that navigation to an existent job order would be allowed.
  • job order 430 it is possible for job order 430 to be subordinate to customer 415, or sales order item release 465. Consequently, whenever a sales order item release or customer document instance node is displayed as an expanded dominant document instance node, such as document instance node 730 of Fig. 7, a job order document type node will be displayed.
  • This designed anomaly reflects the fact that a potential exists for an excessive number of job orders within a given database, necessitating an extensive search to verify no applicable job orders exist. Therefore, while display of type nodes when no associated instance node exists is avoided so as to limit the amount of spurious information displayed to the user, a system designed to await search results for job orders has the potential for unduly delaying display of search results. Consequently, the prefe ⁇ ed embodiment will display a job order type node along with the actual search results, while completing the search of the job orders within a database.
  • the invention further comprises graphics (icons) such that a user can rapidly categorize the node type or node instance. Referring to Fig. 2, various icons for document and sub document type nodes are shown.
  • icon 1305 may be used to show a BOM for an item which will be manufactured internally
  • icon 1310 may be used to indicate the item is an item which must be bought
  • icon 1315 may indicate an item which can be sold. Alternate associations are within the scope of the present invention.
  • document and sub-document type nodes appear in bold text while document and sub-document instance nodes are not in bold text. This is shown, for example, in Fig. 1 by the text for document type node 80, "Sales Orders" which appears in bold text, and the text for document instance node 90, "001004-COBY EQUIPMENT CO.” which is not in bold text.
  • POI icon 97 appears as a generalized warning symbol. The details of POI icon 97 are discussed below, but its primary purpose is normally to alert the user that a predefined condition exists.
  • view pane 30 is shown on explore tab 10.
  • Two types of objects are shown in the embodiment of Fig. 1, progress indicators and properties. Referring to Fig. 1, progress indicators are rendered in label/3D panel pair 31 while the properties values are rendered in edit box 32. These two object types are used to provide informational feedback pertaining to the 'selected' document or sub-document instance node in tree view control 60. The definition of the expressions that generate these objects is discussed below.
  • Progress indicators 33 and 34 comprise label 35 and bar graph 36. Also shown are properties values 37, 38 and 39. Each properties value comprises label 4 land expression 42. In the prefe ⁇ ed embodiment, up to twenty progress indicators and an unlimited number of properties values may be defined for each document or sub-document instance node.
  • Display components tab 200 comprises four primary controls.
  • the first primary control is drop down combo box
  • a second identifier not shown, for a given editing session is the user under whose logon the invention is being accessed. So if, for example, a consultant or other technical personnel is defining expressions for a given user, they need to be logged in as that user so that the expressions created modified are associated with that user and not the person manipulating the expression.
  • the second primary control is POI grid 220 that contains a single element, which must evaluate to a logical value. If the element evaluates to TRUE for a document or sub- document instance node of a type identified in drop down combo 210, POI icon 97 (shown on Fig. 1) will appear beside the document or sub-document instance node in tree view control 60 of explore tab 10 which is of the type identified in drop down combo 210.
  • the element may comprise a single expression, or multiple expressions for a given document or sub- document type node. Referring to Fig. 2, POI expression 230 is shown in POI grid 220. This expression, if evaluated to true, would cause POI icon 97 to be displayed.
  • POI expression 231 is also present in POI grid 220, a logical "OR" is read between the expressions such that if either POI expression 2301 or POI expression 231 evaluates to true for a given document or sub-document instance which is of the type identified in drop down combo box 210, POI icon 97 will be displayed with the document or sub-document instance node on tree view control 60.
  • the expression can, but need not, evaluate data directly associated with the document or sub-document instance node for which the expression is defined. Consequently, the expression or multiple expressions can evaluate data primarily associated with any document or sub-document, in any combination for a given POI.
  • a sales person may create an expression that evaluates to true for a specific customer document instance node when three months has elapsed since the last order placed by the customer.
  • This POI will only appear on explore tab 10 for the sales person's user logon, not, for example, on the accounts receivable clerk's explore tab 10.
  • the accounts receivable clerk may create an expression that evaluates to true for a given customer document instance node if a customer has an invoice outstanding for three months or more.
  • the third primary control is progress indicators grid 240 which comprises five elements, label 245, and expression 250, and lower bound, upper bound, and invert (not shown) which are to the right of expression 250.
  • Label 245 can contain up to twenty characters of text that will be displayed to the left of bar graph 36 on view pane 31 as label 35 of Fig. 1.
  • Expression 250 comprises the numeric expression used to render bar graph 36 as a bar progressing from left to right indicating from 0% to 100%. Expression 250 must return a value between zero and one and is typically of the form x/y.
  • Bar graph 36 is rendered in one of three colors. In the prefe ⁇ ed embodiment, this color scheme is red, yellow, and green.
  • Upper bound and lower bound serve to identify the threshold at which bar graph 36 changes from red to yellow and from yellow to green.
  • Invert (not shown) is a check box, that when checked inverts the color scheme order of bar graph 36 from red, yellow, green to green, yellow, red.
  • Up to twenty progress indicators may be identified for each document or sub-document instance node. As in the case of POIs discussed above, the progress indicators are uniquely programmable by each unique user.
  • Properties grid 270 comprises two sub-grids, specifically, label sub-grid 275 and expression sub-grid 280.
  • Entries in label sub-grid 275 such as label sub-grid entry 276 can contain up to twenty characters of text are rendered as label 41 in properties pane 30 of explore tab 10, to the left of expression 42 as shown in Fig. 1.
  • Entries in expression sub-grid 280 such as expression sub-grid entry 281identify the specific data rendered as expression 42 in properties pane 30 of explore tab 10. This expression can evaluate to any of the common data types available in commercially available systems such as FoxPro, which is available from Microsoft of Seattle, Washington.
  • the system converts entries under expression sub- grid 280 from the form "table.field" to characters.
  • An unlimited number of values may be defined for each document or sub-document instance node.
  • This feature of the present invention allows the individual user to determine the information within the document that is of the most importance to the user's function. For example, a shipping clerk selecting a customer document instance node would most likely be concerned with the address of the customer and prefe ⁇ ed shipping means. Therefore, the shipping clerk has the ability to configure the invention to present this information when the customer document instance node is selected.
  • the president of the company might be more interested in the names of the executives and the phone numbers for a customer. Therefore, the president could configure the invention to display this information when a customer document instance node is selected. Editing in each grid is effected via a right click menu. Values present in a grid can be manipulated directly.
  • the final user interface primary control that is shown on display components tab 200 comprises drop down combo box 285 and copy button 290.
  • the development of point of interest, progress indicator, and property expressions can be a time consuming task. For many applications, it is not necessary for each user will have their own, entirely distinct, set of expressions. Rather, several distinct user classes or 'profiles' will suffice.
  • Use of drop down combo box 285 and copy button 290 effects the copying of a set of expressions defined for one user to the set of expressions associated with another user.
  • the copy 'source' user is determined by making a selection from drop down combo box 285 which displays all users with any expression(s) defined. Once a selection of a user is made, pressing copy button 290 completes the process. All expressions defined for the source user will be copied to the cu ⁇ ently logged on (active) user. Any expressions previously defined for the active user are destroyed.
  • Options tab 300 comprises several user preferences and operational controls.
  • Style drop down combo box 305 is a drop down combo box that controls the display aspects of tree view control 60 of navigation pane 20 of explore tab 10. The user can set any one of seven preferences that are listed in text box 306 when style drop down combo box 305 is selected.
  • Fig. 9 shows options tab 300 with style drop down combo box 305 selected, and the seven available preferences. Referring again to Fig. 3, other user preferences are described. Indentation spinner
  • 310 is a spinner control that determines the amount of indentation (in pixels) that each subordinate level is indented from the dominant level in tree view control 60 of navigation pane 20 of explore tab 10.
  • Font Size 315 is a spinner control that determines the relative size of the text appearing in tree view control 60 of navigation pane 20 of explore tab 10.
  • Zoom Depth 320 is a spinner control that determines the maximum number of levels a 'Zoom In' operation will attempt. The zoom operation is the exhaustive exploration of a chosen node. Due to the nature of the relationships contained in the invention as embodied in the prefe ⁇ ed embodiment, the number of nodes explored during the zoom operation could easily reach into the thousands. The purpose of this control is to place a practical limit on the exhaustive search.
  • Image Size 330 is an option group that determines whether large or small graphics (icons) appear along with each node. In the prefe ⁇ ed embodiment, "Large" is the default, and the user can choose between 16x16 or 32x32 (pixel) icons.
  • Select on Hover 325 is a check box that determines whether a given node is 'selected' simply by the fact that the mouse cursor is over it. Having this setting on a high performance system is desirable as view pane 30 will be refreshed as the mouse passes over each node; allowing the user to view progress indicators for a large number of nodes with relative ease.
  • Toward the right half of options tab 300 of Fig. 3 are shown several controls for the scope of the search of documents and sub-documents.
  • these 'filters' are persistently stored by user in the prefe ⁇ ed embodiment.
  • the process of setting filters is anchored by the selection of a document type by selecting drop down combo box 333 and selecting a document type from the drop down list.
  • the selected document type is displayed in text box 334.
  • status grid 335 will refresh, illustrating the document 'Statuses' available for the selected document or sub-document type and highlighting which of the statuses are selected for display.
  • Status grid 335 is multi-select such that one, a combination, or all entries may be selected. It is important to note that these filters are placed on status grid 335 as defined by the prefe ⁇ ed embodiment, and that no other logical expression may be applied. In addition, not all documents have a status. In these cases, status grid 335 is disabled.
  • date fields 340 and 345 At the lower right hand portion of options tab 300 of Fig. 3 are shown date fields 340 and 345. These fields can be used to restrict the documents or sub- documents displayed on explore tab 10. The date fields can be used alone or in conjunction with the status filter to further restrict the records retrieved during exploration.
  • the prefe ⁇ ed embodiment of the present invention incorporates Active TreeView Control, a commercially produced tree control available from Sheridan Software Systems, Inc. of Melville New York (Sheridan). System requirements for Active TreeView Control are available from Sheridan, as are descriptions of the included files (both distributable and non- distributable). In addition to these files, the present invention incorporates several additional files to effect various elements.
  • Active TreeView Control a commercially produced tree control available from Sheridan Software Systems, Inc. of Melville New York (Sheridan).
  • System requirements for Active TreeView Control are available from Sheridan, as are descriptions of the included files (both distributable and non- distributable).
  • the present invention incorporates several additional files to effect various elements.
  • Icons associated with document type nodes and sub-document type nodes are displayed based upon the file NODEIMAGE.PRG as follows: LPARAMETERS pcDocument Type, plPlaceholder DO CASE
  • a free table is placed in the ERP's primary data directory, typically x: ⁇ ERPDATA. If this table does not become part of the ERP database, 'ERPDATA.DBC it is necessary for the data installer to appropriately place this file in the target environment.
  • the file for checking POI expressions is stored as POINTSOFINTEREST.PRG as follows: LPARAMETERS poNode, pcDocument Type
  • PROCEDURE Explorer_QTDRTGOverheadCost PROCEDURE Explorer_QTDRTGTotalCost
  • the organization of the view pane is evaluated each time a new node type is selected.
  • the number of, size, and relative location of progress indicators and the location of the 'Properties' pane are set.
  • the values of each progress indicator and properties entries are evaluated each time a new node is chosen.
  • the selection of a new node can occur either by clicking on a node or by simply hovering the mouse over a node. In the latter case, the rendering of the view pane changes in rapid fashion: as the user drags the mouse down the tree view.
  • the details of the progress to be monitored are entered into progress indicators grid 240 along with a numeric value between zero and one for the upper and lower bounds, indicating when the progress bar graph should change in color from green, to yellow, to red. If desired, the order is reversed by checking the invert box found to the far right of expression 250.
  • the information to be displayed for the customer documents in properties pane 30 of explore tab 10 can be defined by typing the desired label into label sub-grid 275, and typing the desired expression into expression sub-grid 280.
  • the pre-existing labels and expressions of another user may be copied by selecting drop down combo box 285, and selecting the user to be copied in text box 286. Copying of expressions and labels is then effected by selecting copy button 290. This process is repeated for every document and sub-document type for which a point of interest, progress indicator, or display of information is desired.
  • the user next selects options tab 300 of Fig. 3 to establish various display parameters.
  • the style of the hierarchical tree structure is set by selecting style drop down combo box 305 and highlighting the desired style in text box 306.
  • Indentation for the subordinate levels is set by selecting the appropriate button on indentation spinner 310 to change the displayed number.
  • the user sets the number of levels to be controlled by the "zoom in” and zoom out' options of pop-up menu 815 of Fig. 8.
  • Select on hover 325 is then checked to automatically refresh view pane 30 of Fig. 1 when the cursor highlights an instance node.
  • the desired document statuses to be included in the tree are then set by selecting drop down combo box 333 and selecting the desired document type in text box 334. The operation is completed by highlighting the desired statuses in status grid 335.
  • This sequence is repeated for all document and sub-document types that are desired to be shown in the hierarchical tree.
  • the tree can be further limited by placing a date limit in date fields 340 and 345.
  • the user selects explore tab 10 of Fig. 1 to navigate to the desired information.
  • the tree is created in navigation pane 20 by first selecting drop down combo box 40 of explore tab 10. This causes a list of available document types to be displayed in text box 41. Highlighting a desired document type in text box 41 causes that document type to be displayed in text box 41, and a search to be conducted for that type of document, within the constraints established on options tab 300 of Fig. 3.
  • the results of an initial search are displayed in the tree view control 60.
  • a placeholder node, corresponding to the document type identified in the drop down combo box appears as the root node as shown by document type node 80 in Fig. 1, and the result set of the search appears in tree view control 60.
  • a search parameter may be typed in text box 50.
  • This search adds only document and sub-document instance nodes for instances found to the tree. The actual instances are not retrieved the instance node is selected as is explained below.
  • This two step methodology of first searching, and later retrieving serves to balance response time for 'explore' requests between a single level search and an exhaustive search where hundreds if not thousands of records could be scanned. Referring now to Fig. 7, an initial search is performed for customer documents.
  • the co ⁇ esponding logic in the prefe ⁇ ed embodiment will add Customers document type node
  • Expansion of an instance node subordinate to customers document type node 735 will result in placeholder nodes for any document or sub-document types having an instance node under it, and a job order node regardless of any associated job order instances as explained above.
  • This is shown in Fig. 7 by sales quotes document type node 705, sales order document type node 710, job orders document type node 725, shippers document type node 715, and AR invoices document type node 720.
  • Moving the cursor over an instance node causes the invention to retrieve the particular instance of the document or sub-document associated with the selected instance node. At this point, all of the document's or sub-document's fields are available to be evaluated.
  • a function/procedure must be developed to locate the related record(s) before the evaluation can take place. Typically, these functions/procedures will return the desired value itself. A good example of this would be the 'on-hand' functions used to determine various inventory statistics for a related item.
  • Selection of the instance node causes properties pane 30 to be refreshed as a result of select on hover box 325, shown in Fig. 3, being checked.
  • the cursor highlights customer instance node 740, labels and expressions previously defined by the user in properties grid 270 of Fig. 2, for customer document types, are displayed. Further, any evaluation defined in progress indicators grid 240 of Fig 2 will be initiated, and the results displayed. A typical result is shown as label 750 and bar graph 755 in Fig. 7.
  • the expressions reflect information specific to the customer instance associated with instance node 740.
  • Modification of the actual instance is accomplished by selecting the instance, and right clicking the mouse. This causes pop up menu 815 (Fig. 8) to be displayed. Selection of the "Go To” option causes a data-editing screen for the selected instance to be displayed. For example, by selecting customer instance node 730 (Fig. 7), right clicking the mouse, and selecting the "Go To” option, data-editing screen 1000 shown in Fig. 10 is displayed.
  • text box 1105 reflects the same customer number used to identify customer instance node 745 of Fig. 7.
  • the user may select items tab 1110, causing items tab 1110 to be displayed as shown in data-editing screen 1200 of Fig. 12.
  • This is the data-editing screen for quote line item document 1205 related to quote document 1115 shown in Fig. 11.
  • the user could have drilled down to the sub- document instance node associated with quote line item document 1205, selected the sub- document instance node, and selected the "Go To" option from the pop-up menu.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Human Resources & Organizations (AREA)
  • Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • General Physics & Mathematics (AREA)
  • Economics (AREA)
  • General Engineering & Computer Science (AREA)
  • Educational Administration (AREA)
  • Game Theory and Decision Science (AREA)
  • Development Economics (AREA)
  • Human Computer Interaction (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

La présente invention porte sur un système logiciel possédant une interface de navigation conviviale utilisant un affichage (20) hiérarchique de documents commerciaux sur la base d'une relation dominant-subordonné entre les documents. Selon une réalisation, les documents sont apparentés par l'utilisation de codes qui définissent une relation entre les documents dominants (81) et subordonnés (91). Conjointement à la sélection d'un document spécifique, l'invention affiche des informations relatives à ce document qui peut être personnalisé par l'utilisateur. Selon une autre réalisation, chaque utilisateur peut définir un ensemble unique de données à afficher. L'invention porte également sur un dispositif au moyen duquel les données sous-jacentes peuvent être facilement mises en forme à partir de l'affichage (20) hiérarchique. Cette invention permet également de créer des expressions (230, 231) qui avertissent l'utilisateur de la présence d'état prédéterminés. Cet avertissement est affiché conjointement avec l'affichage (20) hiérarchique d'un document, mais l'expression (230, 231) peut être définie par des données qui ne sont normalement pas contenues dans le document. Chaque utilisateur peut définir un ensemble unique d'avertissements pour divers documents. La présente invention comprend, en outre, un rendu visuel d'expressions prédéfinies décrivant l'évolution du travail relatif à un document, et chaque utilisateur peut également définir un ensemble unique de l'évolution des expressions (250) pour divers documents sur la base de conditions d'un intérêt particulier pour l'utilisateur.
PCT/US1999/024859 1998-10-22 1999-10-22 Interface de navigation pour systeme erp WO2000023874A1 (fr)

Priority Applications (4)

Application Number Priority Date Filing Date Title
US09/743,152 US7131069B1 (en) 1998-10-22 1999-10-22 Navigational interface for ERP system
AU11319/00A AU1131900A (en) 1998-10-22 1999-10-22 Navigational interface for erp system
US09/928,863 US6981222B2 (en) 1998-10-22 2001-08-13 End-to-end transaction processing and statusing system and method
US10/910,487 US20050240881A1 (en) 1998-10-22 2004-08-03 Navigational interface for ERP system

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US10528798P 1998-10-22 1998-10-22
US60/105,287 1998-10-22
US23763199A 1999-01-26 1999-01-26
US09/237,631 1999-01-26

Related Child Applications (4)

Application Number Title Priority Date Filing Date
US09743152 A-371-Of-International 1999-10-22
US09/743,152 A-371-Of-International US7131069B1 (en) 1998-10-22 1999-10-22 Navigational interface for ERP system
US09/928,863 Continuation-In-Part US6981222B2 (en) 1998-10-22 2001-08-13 End-to-end transaction processing and statusing system and method
US10/910,487 Division US20050240881A1 (en) 1998-10-22 2004-08-03 Navigational interface for ERP system

Publications (1)

Publication Number Publication Date
WO2000023874A1 true WO2000023874A1 (fr) 2000-04-27

Family

ID=26802442

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US1999/024859 WO2000023874A1 (fr) 1998-10-22 1999-10-22 Interface de navigation pour systeme erp

Country Status (2)

Country Link
AU (1) AU1131900A (fr)
WO (1) WO2000023874A1 (fr)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1315097A1 (fr) * 2001-11-22 2003-05-28 Oracle International Corporation Système d'information orienté client
DE102004006285A1 (de) * 2004-02-09 2005-09-15 Siemens Ag Visualisierung von strukturierten Daten
US7228506B2 (en) * 2003-09-25 2007-06-05 Microsoft Corporation System and method for providing an icon overlay to indicate that processing is occurring
US8370794B2 (en) 2005-12-30 2013-02-05 Sap Ag Software model process component
US8402426B2 (en) 2005-12-30 2013-03-19 Sap Ag Architectural design for make to stock application software
US8538864B2 (en) 2006-03-30 2013-09-17 Sap Ag Providing payment software application as enterprise services
US8676617B2 (en) * 2005-12-30 2014-03-18 Sap Ag Architectural design for self-service procurement application software
US8818884B2 (en) 2008-09-18 2014-08-26 Sap Ag Architectural design for customer returns handling application software
US11514380B2 (en) 2019-07-30 2022-11-29 Oracle International Corporation Continuing interaction with ongoing transactions in ERP systems

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5801702A (en) * 1995-03-09 1998-09-01 Terrabyte Technology System and method for adding network links in a displayed hierarchy
US5923328A (en) * 1996-08-07 1999-07-13 Microsoft Corporation Method and system for displaying a hierarchical sub-tree by selection of a user interface element in a sub-tree bar control

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5801702A (en) * 1995-03-09 1998-09-01 Terrabyte Technology System and method for adding network links in a displayed hierarchy
US5923328A (en) * 1996-08-07 1999-07-13 Microsoft Corporation Method and system for displaying a hierarchical sub-tree by selection of a user interface element in a sub-tree bar control

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"MANAGING YOUR MONEY FOR WINDOWS", USER'S GUIDE MECA SOFTWARE, XX, XX, 1 January 1994 (1994-01-01), XX, pages 01 - 61, XP002923275 *
"The Windows Sources catalog", GALE GROUP COMPUTING, vol. 1, no. 8, September 1993 (1993-09-01), BUYERS GUIDE *
DATABASE GALE GROUP [online] XP002934906, accession no. Dialog Database accession no. 01614372 *

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1315097A1 (fr) * 2001-11-22 2003-05-28 Oracle International Corporation Système d'information orienté client
US7228506B2 (en) * 2003-09-25 2007-06-05 Microsoft Corporation System and method for providing an icon overlay to indicate that processing is occurring
DE102004006285A1 (de) * 2004-02-09 2005-09-15 Siemens Ag Visualisierung von strukturierten Daten
US8370794B2 (en) 2005-12-30 2013-02-05 Sap Ag Software model process component
US8402426B2 (en) 2005-12-30 2013-03-19 Sap Ag Architectural design for make to stock application software
US8676617B2 (en) * 2005-12-30 2014-03-18 Sap Ag Architectural design for self-service procurement application software
US8538864B2 (en) 2006-03-30 2013-09-17 Sap Ag Providing payment software application as enterprise services
US8818884B2 (en) 2008-09-18 2014-08-26 Sap Ag Architectural design for customer returns handling application software
US11514380B2 (en) 2019-07-30 2022-11-29 Oracle International Corporation Continuing interaction with ongoing transactions in ERP systems

Also Published As

Publication number Publication date
AU1131900A (en) 2000-05-08

Similar Documents

Publication Publication Date Title
US7131069B1 (en) Navigational interface for ERP system
US7240077B1 (en) Web site content change management
US8069093B2 (en) Website user account linking
US6628307B1 (en) User interface for internet application
US7900151B2 (en) Maintaining individual object data
US8069096B1 (en) Multi-constituent attribution of a vendor's product catalog
US20030115207A1 (en) Hierarchical hybrid OLAP analytics generators
US20030061225A1 (en) Hierarchical hybrid OLAP scenario management system
US20110126123A1 (en) Systems and methods for managing to-do list task items via a computer network
US20050091263A1 (en) Systems and methods for representing and editing multi-dimensional data
US5890132A (en) Associating a physical application to a business operation
US20080004981A1 (en) Online marketplace management system with automated pricing tool
EP1693793A1 (fr) Système de gestion de propriété industrielle
US20040039629A1 (en) Web based method and system for managing and transferring business information
US20060282342A1 (en) Image-based inventory tracking and reports
US20030061246A1 (en) Hierarchical hybrid online analytical processing services system
AU6906700A (en) Livestock inventory and materials system with interactive graphical user interface
WO2000023874A1 (fr) Interface de navigation pour systeme erp
US6892357B2 (en) Logistics management method and system
US20040148309A1 (en) Customer fields
US20030061226A1 (en) Data loader for handling imperfect data and supporting multiple servers and data sources
EP1087303A2 (fr) Procédé et appareil pour générer des pages Web avec des informations affichées dans un carroussel
US8234174B1 (en) Method and apparatus for creating custom advertisements
US20080033947A1 (en) Rating system and method of monitoring ratings
US20070118446A1 (en) System and method for managing relationships in a procurement transaction

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref country code: AU

Ref document number: 2000 11319

Kind code of ref document: A

Format of ref document f/p: F

AK Designated states

Kind code of ref document: A1

Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
WWE Wipo information: entry into national phase

Ref document number: 09743152

Country of ref document: US

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase