Abstract: A method and system are disclosed for modeling a relational database. The method comprises the steps of defining a set of data tables to accommodate any number of levels of a business hierarchy and using these tables as a generic data model to handle various levels of requirements of the business hierarchy. This set of tables include a first control table, a second table containing hierarchy nodes in a flattened format, a third table storing unique hierarchy node names, and a fourth table describing the hierarchy nodes in one or more languages. For example, this business hierarchy may be a commodity hierarchy, a geography hierarchy and a client organization hierarchy. Also, in the preferred embodiment, no new tables are needed when a new hierarchy is introduced, and the generic data model supports different numbers of reporting levels from one hierarchy to the next hierarchy.

Abstract: A method, system and program product for classifying data elements into different levels of a business hierarchy. The method includes identifying data elements to be classified into one or more levels of a business hierarchy, selecting a first logic decision tree for evaluating the data elements identified for classification into the hierarchy and executing the first tree for recursively evaluating each data element identified until the first tree has been traversed. Further, the method includes dynamically creating configurable anchor point classifications for the data elements evaluated through the first tree and assigning a respective anchor point classification to each data element evaluated, such that, a respective anchor point classification assigned to a data element evaluated links the data element to a lowest level of the hierarchy, and where the anchor point classification conveys classification information as to each higher level of the hierarchy that the data element belongs to.

Abstract: A method, system and program product for classifying data elements into different levels of a business hierarchy. The method includes identifying data elements to be classified into one or more levels of a business hierarchy, selecting a first logic decision tree for evaluating the data elements identified for classification into the hierarchy and executing the first tree for recursively evaluating each data element identified until the first tree has been traversed. Further, the method includes dynamically creating configurable anchor point classifications for the data elements evaluated through the first tree and assigning a respective anchor point classification to each data element evaluated, such that, a respective anchor point classification assigned to a data element evaluated links the data element to a lowest level of the hierarchy, and where the anchor point classification conveys classification information as to each higher level of the hierarchy that the data element belongs to.

Abstract: A method and system are disclosed for modeling a relational database. The method comprises the steps of defining a set of data tables to accommodate any number of levels of a business hierarchy and using these tables as a generic data model to handle various levels of requirements of the business hierarchy. This set of tables include a first control table, a second table containing hierarchy nodes in a flattened format, a third table storing unique hierarchy node names, and a fourth table describing the hierarchy nodes in one or more languages. For example, this business hierarchy may be a commodity hierarchy, a geography hierarchy and a client organization hierarchy. Also, in the preferred embodiment, no new tables are needed when a new hierarchy is introduced, and the generic data model supports different numbers of reporting levels from one hierarchy to the next hierarchy.

Abstract: A hybird Notes/DB2 environment provides a requisition catalog on the Web. Client browsers are connected to a GWA infrastructure including a first network dispatcher and a virtual cluster of Domino.Go servers. The network dispatcher sprays out browser requests among configured .nsf servers in virtual server cluster. Communications from this virtual server cluster are, in turn, dispatched by a second network dispatcher servers in a Domino cluster. External objects, primarily for a GUI, are served in a .dfs and include graphic files, Java files, HTML images and net.data macros. The catalog is built from supplier provided flat files. A front end is provided for business logic and validation, as also is a relation database backend. HTML forms are populated using relational database agents. A role table is used for controlling access both to Notes code and DB2 data. Large amounts of data is quickly transferred using an intermediate agent and window.