System and method utilizing a generic update module with recursive calls

• US 8,959,117 B2
• Filed: 03/15/2013
• Issued: 02/17/2015
• Est. Priority Date: 12/28/2006
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Dehn, Rene, Kaiser, Martin, Anzuinelli, Gisella Dominguez
• Primary Examiner(s): CHANNAVAJJALA, SRIRAMA T
• Application Number:
  US13/832,979
• Publication Number:
  US 20130212066A1
• Time in Patent Office: 704 Days
• Field of Search: 707618-623, 707674-679, 707702-703, 707793-796, 707802-806
• US Class Current: 707/796
• CPC Class Codes: G06F 16/00 Information retrieval; Database structures therefor; File system structures therefor
• CPC Class Codes: G06F 16/23 Updating
• CPC Class Codes: G06F 16/2308 Concurrency control transaction processing G06F9/466
• CPC Class Codes: G06F 16/2343 Locking methods, e.g. distributed locking or locking implementation details

Abstract

This disclosure provides various embodiments of software for identifying and utilizing a generic update module with recursive calls. In one aspect, the software receives packed update parameters for updating a data record in a database, unpacks the update parameters, and updates the data record in the database using the unpacked update parameters. In some implementations, the update parameters may comprise a packed long byte string. The software may update the data record by returning the unpacked update parameters to a business application for database execution.

Claims

1. A non-transitory, computer-readable medium storing computer-readable instructions executable by a computer to:

transmit packed update parameters for updating a database table in a database associated with a central data repository to an update module, wherein the update parameters are data records reflecting changes to a local instance of a data set that are used to update the database table and that are packed into a generic format independent of a particular database table structure to permit recursive calls to the update module;

recursively call the update module to process the packed update parameters;

receive reformatted update parameters for updating the database table in the database from the update module, wherein the reformatted update parameters are transmitted packed update parameters reformatted into an identified database table structure associated with the database table, and wherein the reformatted update parameters are stored in the database; and

update the database table in the database using the received reformatted update parameters.

2. The medium of claim 1, wherein the update parameters are first update parameters, the database table is a first database table, the data records are first data records, the database table structure is a first database table structure, the instructions further operable when executed to:

transmit second update parameters for updating a second database table in the database to the update module, wherein the second update parameters are second data records used to update the database table that are packed into the generic format independent of a particular database table structure;

receive the second update parameters for updating the second database table in the database from the update module, wherein the second update parameters are received in a second database table structure associated with the second database table, wherein the second database table structure is disparate from the first database table structure; and

update the second database table in the database using the received second update parameters.

3. The medium of claim 1, wherein the update parameters are first update parameters, the database table is a first database table, the data records are first data records, the database table structure is a first database table structure, the database is a first database, and the instructions further operable when executed to:

transmit second update parameters for updating a second database table in a second database to the update module, wherein the second update parameters are second data records used to update the database table that are packed into the generic format independent of a particular database table structure;

receive the second update parameters for updating the second database table in the second database from the update module, wherein the second update parameters are received in a second database table structure associated with the second database table, wherein the second database table structure is disparate from the first database table structure; and

update the second database table in the second database using the received second update parameters.

4. The medium of claim 1, wherein the update parameters comprise a long byte string.

5. The medium of claim 1, wherein the database resides in a persistent environment.

6. The medium of claim 1, wherein updating the database table comprises inserting, updating, or deleting a data record in the database table.

7. The medium of claim 1, wherein updating the database table comprises:

issuing a commit statement to the database; and

transferring the received update parameters to the database for updating within the database.

8. The medium of claim 7, wherein the commit statement is generated by a business application.