Teradata Us, Inc.

Teradota Us, Inc.

Terodata Us, Inc.

Thomas Kevin Ryan

Brian Jay Wasserman

Neelesh Bansode

George Robert Hood

Linette Draper

Carl Lewis Christofferson

Santosh Kumar Singh

Paul M Cereghini

Paul H Phibbs

Latesh Pant

Karen A Papierniak

Shashank Shekhar

Mike Chiufang Hsiao

Vivek Shandilya

Gordon Brooks

Arvind Kumar

Nitin Jain

Ankit Khare

Judy Bayer

Enrico Galimberti

Achal Patel

Yabing Bi

Anand Louis

Richard C Schwarz

Sang Y Yum

Gordon Douglas Brooks, Jr

Madhavi Chandrashekar

Techniques for cross referencing data are presented. A first database object and a second database object are linked together. The linkage is automatically cross referenced to a third database object. Access to any of the database objects can be achieved via any of the remaining database objects and vice versa. Additionally, the link and cross reference can be visualized and visually manipulated and modified.

Techniques for cross referencing data

A method, system, apparatus, and article of manufacture provides the ability to visualize master data management (MDM) data as part of a MDM workflow user interface (UI) in a computer system. MDM data resides in one or more tables of a relational database management system. An MDM system maintains, as part of a process and framework, a first process workflow to manage relationship data. The relationship data is data required to manage an association of one piece of MDM data to another piece of MDM data. A first process workflow provides a UI node that contains a link to a file that describes UI components to display when the first process workflow is executed. A first component of the UI component identifies an Adobe&#x2122; Flex&#x2122; based UI component. The Adobe&#x2122; Flex&#x2122; based UI component enables the representation and viewing of the MDM data in a hierarchy.

Workflow integration with Adobe&#x2122; Flex&#x2122; user interface

Techniques for data integration are provided. Source attributes for source data are interactively mapped to target attributes for target data. Rules define how records from the source data are merged, selected, and for duplication detection. The mappings and rules are recorded as a profile for the source data and processed against the source data to transform the source attributes to the target attributes.

Techniques for data integration

Techniques for managing data relationships are presented. A database element from a first database table is linked with a database element of a second database table via a Graphical User Interface as directed by a user. The link establishes a data relationship having attributes and properties. The relationship along with the attributes and properties are graphically presented to the user for inspection and analysis.

Techniques for managing data relationships

A method, system, apparatus, and article of manufacture is configured to expose a database asset as a web service. A relational database management system (RDBMS) that stores information is executed in a computer system. As part of a process and framework, a series of business rules and process workflows are maintained that manage data that resides in RDBMS tables. A rule is created that contains an application programming interface definition with predefined input and output for exposing the database asset as the web service. The rule is exposed as the web service. The web service is used to invoke a database operation based on the database asset, and to output a result.

Master data management database asset as a web service

A method, system, apparatus, and article of manufacture provide the ability to maintain multiple versions of structured views of data in a computer system. A relational database management system (RDBMS) is executed that stores master data in the computer system in master RDBMS tables. The master data is hierarchical in nature and hierarchy metadata for the master data is stored in the RDBMS tables. As part of a process and framework, a series of business rules and process workflows are maintained to manage the master data. Version tables are created in the RDBMS that correspond to each of the master RDBMS tables. Each of the version tables includes an attribute denoting version information. Versions of the master data are defined by replicating the master data and hierarchy metadata into the corresponding version tables. The version tables are used to graphically visualize, manage, and manipulate the versions of the master data.

Master data management versioning

Graphical User Interfaces for custom lists and labels are provided. A database includes fields that define views when processed by an application server on behalf of a user. At least one view permits the user to supply criteria for custom defining lists or sets of labels, which are also retrieved from the database by the application server.

Graphical user interfaces for custom lists and labels

Techniques for data store list generation and management are provided. A user supplies criteria for a list via a graphical user interface tool. The criteria are used to generate a query, and the query when executed against a data store produces results representing the list. The list may then be used for a variety of purposes.

Data store list generation and management

A Value Analyzer system is a data-driven computer-facilitated financial model that provides accurate and consistent profitability calculations using account, product and event attributes stored in a relational database managed by a relational database management system (RDBMS). Profitability calculations are performed in the computer by applying one or more rules to the account, product and event attributes accessed from the database, wherein the profitability calculations include setup, generation and execution of structured query language (SQL) statements by the RDBMS. The present invention also monitors the profitability calculations by monitoring the setup, generation and execution of the SQL statements by the RDBMS, in order to provide bypass, logging, user restartability, or status (BLURS) functions for the profitability calculations.

Application code generation and execution with bypass, logging, user restartability and status functionality

A method, apparatus, and article of manufacture provide the ability to deploy a data management application to a target computer system. Metadata for a master data management (MDM) application is stored in a deployment database. The metadata is representative of business rules and process workflows that manage business data from multiple sources and a model definition for a model for a central business database. Configuration settings for the MDM application are stored in the deployment database. The metadata and configuration settings are retrieved from the deployment database. Installation instructions of the MDM application are confirmed based on input into a graphical user interface. The master data management application is installed on the target computer system based on the installation instructions, metadata, and configuration settings.

Deployment manager for master data management

A method, apparatus, and article of manufacture is configured to define a structured view of data in a computer system. A relational database management system (RDBMS) stores information in the computer system. As part of a process and framework, a series of business rules and process workflows that manage data (that is hierarchical in nature) that resides in one or more RDBMS tables are maintained. User input is accepted that defines a hierarchical structure that is projected onto the data. The hierarchical structure is stored as metadata in the RDBMS. The hierarchical structure is utilized to graphically visualize, manage, and manipulate the data.

Hierarchy manager for master data management

Techniques are presented for query generation, population, and management. Queries are generically defined with metadata. The metadata identifies specific queries and specific parameters associated with a given query. When a query instance is desired, parameter values are dynamically acquired and used to populate portions of the metadata associated with a desired query. The query instance may then be executed as desired.

Techniques for query generation, population, and management

A data warehouse system and application which analyzes historical sales and product data contained within a data warehouse to determine the best product prices across a set of products for a retailer. The application analyzes historical sales and product data contained in a database to determine an opportunity score for multiple products sold by a retailer, the opportunity score indicating potential benefit to said business from changing the pricing of a product; and analyzes historical sales data contained in the database to determine an ability to change score for each product, the ability to change score indicating potential risk of lost sales for the retailer from changing the pricing of a product. Results of the analyses are displayed in a scatter plot graph with the graph axes being the opportunity scores and ability to change scores, respectively. Each product is represented by a point in the scatter plot, the coordinates of the point being the opportunity score and the ability to change score associated with the represented product. The scatter plot graph can be divided into quadrants, wherein products having favorable opportunity scores and favorable ability to change scores are displayed together in one the four quadrants.

Opportunity matrix for use with methods and systems for determining optimal pricing of retail products

A method, apparatus, and article of manufacture provide the ability to import a first data model into a meta-data representation in one or more computers. An import wizard or graphical user interface is invoked and guides a user through a process of importing the first data model into the meta-data representation. A source is selected that specifies database connectivity information of a source database containing the first data model. A schema is selected from the selected source, from which tables will be imported into the meta-data representation. A list of all table names within the selected schema is retrieved and displayed. Tables are selected from the list of all table names to import into the meta-data representation. Table information, for all of the selected tables, is populated into the meta-data representation.

Open model ingestion for master data management

Techniques are presented for managing fraud information. Metadata defines user profiles, security levels, fraud cases, and presentation information. One or more queries or reports are processed against disparate data store tables and the results are aggregated into a repository. The repository is also defined by the metadata. Furthermore, operations associated with sharing, viewing, and accessing the results from the repository is defined and controlled by the metadata. In an embodiment, portions of the metadata may be viewed and navigated in a hierarchical and graphical formatted presentation.

Growing community of inventors

Valley Center, CA, United States of America

Thomas Kevin Ryan