# US 2012/0084257 A1 · Master data management versioning

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2012/0084257 A1
- Document ID: US20120084257A1
- Status: Published application
- Kind: A1
- Application number: 13/250,740
- Filed: 2011-09-30
- Published: 2012-04-05
- Earliest claimed: 2010-09-30
- Assignees: Teradata US, Inc.
- Inventors: NEELESH V. BANSODE; THOMAS K. RYAN; LATESH PANT; VIVEK SHANDILYA; NITIN PRATAP JAIN; SHASHANK SHEKHAR
- Web page: https://patentgrep.com/patent/US20120084257A1

## CPC

- G06F 16/219: {Managing data history or versioning (querying versioned data G06F16/2474; querying temporal data G06F16/2477)}
- G06F 16/2329: {using versioning}
- G06F 16/2393: {Updating materialised views}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

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.

## Claims

### Claim 1

A computer-implemented method for maintaining versions of structured views of data in a computer system, comprising:
(a) executing a relational database management system (RDBMS) that stores master data in the computer system in one or more master RDBMS tables, wherein:
(i) the master data is hierarchical in nature; and
(ii) hierarchy metadata for the master data is stored in the RDBMS tables;
(b) maintaining, as part of a process and framework, a series of business rules and process workflows to manage the master data;
(c) creating one or more version tables in the RDBMS that correspond to each of the one or more master RDBMS tables, wherein each of the one or more version tables further comprises an attribute denoting version information;
(d) defining one or more versions of the master data by replicating the master data and hierarchy metadata stored in the master RDBMS tables into the corresponding one or more version tables; and
(e) utilizing the one or more version tables to graphically visualize, manage, and manipulate the one or more versions of the master data.

### Claim 2 (depends on 1)

The method of claim 1, wherein the replicating of the master data is performed in a version staging area.

### Claim 3 (depends on 1)

The method of claim 1, wherein the attribute denoting version information forms a part of a primary key in each of the one or more version tables.

### Claim 4 (depends on 1)

The method of claim 1, wherein the one or more version tables utilize a partitioning concept to optimize a retrieval and deletion of version data.

### Claim 5 (depends on 1)

The method of claim 1, further comprising editing one of the one or more versions of the master data using the hierarchy metadata stored in the one or more version tables.

### Claim 6

An apparatus for maintaining versions of structured views of data in a computer system, comprising:
(a) a relational database management system (RDBMS) executing in the computer system;
(b) a master data management system configured to maintain, as part of a process and framework, a series of business rules and process workflows to manage master data that resides in one or more tables in the RDBMS, wherein:
(i) the master data is hierarchical in nature;
(ii) hierarchy metadata for the master data is stored in the RDBMS tables;
(iii) the master data management system creates one or more version tables in the RDBMS that correspond to each of the one or more master RDBMS tables, wherein each of the one or more version tables further comprises an attribute denoting version information; and
(iv) the master data management system defines one or more versions of the master data by replicating the master data and hierarchy metadata stored in the master RDBMS tables into the corresponding one or more version tables; and
(c) a hierarchy viewer configured to utilize the one or more version tables to graphically visualize, manage, and manipulate the one or more versions of the master data.

### Claim 7 (depends on 6)

The apparatus of claim 6, wherein the replicating of the master data is performed in a version staging area.

### Claim 8 (depends on 6)

The apparatus of claim 6, wherein the attribute denoting version information forms a part of a primary key in each of the one or more version tables.

### Claim 9 (depends on 6)

The apparatus of claim 6, wherein the one or more version tables utilize a partitioning concept to optimize a retrieval and deletion of version data.

### Claim 10 (depends on 6)

The apparatus of claim 6, further comprising editing one of the one or more versions of the master data using the hierarchy metadata stored in the one or more version tables.

### Claim 11

An article of manufacture comprising a program storage device readable by a computer, tangibly embodying at least one program of instructions executable by the computer to perform method steps of maintaining versions of structured views of data in a computer system, the method steps comprising:
(a) executing a relational database management system (RDBMS) that stores master data in the computer system in one or more master RDBMS tables, wherein:
(i) the master data is hierarchical in nature; and
(ii) hierarchy metadata for the master data is stored in the RDBMS tables;
(b) maintaining, as part of a process and framework, a series of business rules and process workflows to manage the master data;
(c) creating one or more version tables in the RDBMS that correspond to each of the one or more master RDBMS tables, wherein each of the one or more version tables further comprises an attribute denoting version information;
(d) defining one or more versions of the master data by replicating the master data and hierarchy metadata stored in the master RDBMS tables into the corresponding one or more version tables; and
(e) utilizing the one or more version tables to graphically visualize, manage, and manipulate the one or more versions of the master data.

### Claim 12 (depends on 11)

The article of manufacture of claim 11, wherein the replicating of the master data is performed in a version staging area.

### Claim 13 (depends on 11)

The article of manufacture of claim 11, wherein the attribute denoting version information forms a part of a primary key in each of the one or more version tables.

### Claim 14 (depends on 11)

The article of manufacture of claim 11, wherein the one or more version tables utilize a partitioning concept to optimize a retrieval and deletion of version data.

### Claim 15 (depends on 11)

The article of manufacture of claim 11, further comprising editing one of the one or more versions of the master data using the hierarchy metadata stored in the one or more version tables.
