System and method for transferring data between databases

• US 7,512,690 B2
• Filed: 07/16/2004
• Issued: 03/31/2009
• Est. Priority Date: 07/18/2003
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Gross, Jens-Uwe, Imabayashi, Kazuya
• Primary Examiner(s): Najjar; Saleh
• Assistant Examiner(s): HUQ, FARZANA B
• Application Number:
  US10/892,377
• Publication Number:
  US 20050050116A1
• Time in Patent Office: 1,719 Days
• Field of Search: 709/203, 709/227, 709/228, 709/229, 707/2, 707/10, 707/200, 707/204, 707/3, 705/1, 705/20, 705/50, 705/67, 705/75
• US Class Current: 709/227
• CPC Class Codes: G06Q 30/08 Auctions

Abstract

A data transfer control device issues a session key identifying an application running on a user terminal. Then the device specifies a first database as a transfer destination of data input into a common data field for the first and a second database and outputs the data to an application process together with a session key. The device then inputs the data in the common data field together with the session key from the application process and updates the first database. After that, the device retrieves and outputs the data requested by the application process from the updated first database.

Claims

1. A data transfer control device for synchronizing inputs to a first and a second database having different field definitions and outputs to an application process running on a user terminal, comprising:

a session management device configured to issue a session key identifying said application process;

a value transfer destination management device configured to specify at least one receipt data field in said first database as transfer destination for data input into at least one transfer data field in said second database, wherein the at least one transfer data field to be transferred is common to the first and second databases and has a different field definition than the at least one receipt data field in said first database the specified transfer destination to said application process together with said session key;

a database management device configured to input the data input into the at least one transfer data field in said second database that is common to the first and second databases, wherein the data input is received from said application process together with said session key and updating said first database with the at least one receipt data field that is common to the first and second databases based on the specified transfer destination and based on the session key;

and a data requested processing device configured to retrieve and output the data requested by said application process from said updated first database;

wherein said session management device, when said session key is issued, inputs identifying information of said user terminal,

and said value transfer destination management device retrieves from said first database a business object linked to the identifying information of the user terminal input by said session management device and a settings form indicating whether or not to display certain fields within said business object, and then specifies said transfer destination and outputs the business object and settings form together with said session key.

2. The data transfer control device according to claim 1, wherein said value transfer destination management device specifies the transfer destination of the input data of the common data field using a URL of said first database and said session key.

3. The data transfer control device according to claim 1, wherein said database management device, when updating said first database, specifies a business object into which to input the data from said common data field, based on the session key input by said application process.

4. A data transfer control method for synchronizing inputs to a first and a second database having different field definitions and outputs to an application process running on a user terminal, comprising:

issuing a session key identifying said application process;

specifying at least on receipt data field in said first database as transfer destination for data input into at least transfer one field in said second database, wherein the at least one transfer data field to be transferred is common to said first and second databases and has a different field definition than the at least one receipt data field in said first database and outputting the specified transfer destination together with said session key to said application process;

inputting the data of said at least one transfer data field in said second database that is common to the first and second databases from said application process together with said session key to update said first database with the at least one receipt data field that is common to the first and second databases based on the specified transfer destination and based on the session key; and

retrieving and outputting the data requested by said application process from said updated first database;

when said session key is issued, inputting identifying information for said user terminal, retrieving from said first database a business object linked to the identifying information of said user terminal and a settings form indicating whether to display or not display certain fields within said business object,

specifying said transfer destination, and outputting the business object and settings form together with said session key.

5. The data transfer control method according to claim 4, wherein the transfer destination of the input data to said common data field is specified using a URL of said first database and said session key.

6. The data transfer control method according to claim 4, further comprising, when said first database is updated, specifying a business object into which to input the data from said common data field, based on the session key input from said application process.

7. A computer-readable medium on which is stored a set of instructions for synchronizing inputs to a first and a second database having different field definitions and outputting to an application process running on a user terminal, which instructions when executed perform stages comprising:

issuing a session key identifying said application process;

specifying at least one receipt data field in said first database as transfer destination for data input into at least one transfer field in said second database, wherein the at least one transfer data field to be transferred is common to said first and second databases and has a different field definition than the at least on receipt data field in said first database and outputting the specified transfer destination together with said session key to said application process;

inputting the data of said at least one transfer data field in said second database that is common to the first and second databases from said application process together with said session key to update said first database with the at least one receipt data field that is common to the first and second databases based on the specified transfer destination and based on the session key; and

retrieving and outputting the data requested by said application process from said updated first database;

wherein the performed stages further comprise;

when said session key is issued, inputting identifying information for said user terminal; and

retrieving from said first database a business object linked to the identifying information of said user terminal and a settings form indicating whether to display or not display certain fields within said business object, and then specifying said transfer destination, and outputting the business object and settings form together with said session key.

8. The computer-readable medium according to claim 7, wherein the transfer destination for the input data to said common data field is specified using a URL of said first database and said session key.

9. The computer-readable medium according to claim 7, wherein the performed stages further comprise, when said first database is updated, specifying a business object into which to input the data from said common data field, based on the session key input from said application process.