Teradata Us, Inc.

Neelesh Bansode

Thomas Kevin Ryan

Carl Lewis Christofferson

Santosh Kumar Singh

Latesh Pant

Brian Jay Wasserman

Shashank Shekhar

Vivek Shandilya

Arvind Kumar

Nitin Jain

Ankit Khare

Achal Patel

Anand Louis

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

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.

Growing community of inventors

Bengaluru, India

Neelesh Bansode