IP Library › Granted Patent US 12,475,087
Granted Patent B2
US 12,475,087 · App. 18/609,319 · Granted Nov 18, 2025

Deployment of configuration data in parallel to active test usage

Inventors: Wulf Kruempelmann (Altlussheim, DE); Dominik Ofenloch (Lampertheim, DE)
Assignee: SAP SE
G06F16/213G06F16/2282G06F16/2358G06F16/252
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,475,087
App. No.
18/609,319
Granted
Nov 18, 2025
Kind
B2
Abstract

One or more applications access a first set of database tables via a first projection view mapping from a first name to a second name. At a given point in time, the one or more applications may detect an indication of a modification operation targeting the first set of database tables. In response to detecting the indication of the modification operation, the one or more applications may create a second set of database tables for storing results of the modification operation. In response to detecting a completion of the modification operation, the first projection view may be remapped from the first name to a third name, where the third name is associated with the second set of database tables. Then, the one or more applications may access the second set of database tables via the first projection view mapping from the first name to the third name.

Claims (38)

1 . A computer-implemented method comprising:

accessing, by a first application, a first set of database tables via a first projection view mapping from a first name to a second name;

detecting an indication of a modification operation targeting the first set of database tables;

creating a second set of database tables for storing results of the modification operation, wherein the second set of database tables are a modified version of the first set of database tables;

responsive to detecting a completion of the modification operation:

remapping the first projection view from the first name to a third name, wherein the third name is associated with the second set of database tables; and

accessing, by the first application, the second set of database tables via the first projection view mapping from the first name to the third name.

2 . The computer-implemented method of claim 1 , wherein accesses targeting the first set of tables subsequent to the completion of the modification operation are redirected to the second set of tables.

3 . The computer-implemented method of claim 1 , further comprising continuing to enable access to the first set of database tables via the first projection view mapping from the first name to the second name while the modification operation is ongoing.

4 . The computer-implemented method of claim 3 , further comprising generating a second projection view mapping from the first name to the third name.

5 . The computer-implemented method of claim 4 , further comprising accessing, by a second application, the second set of tables via the second projection view mapping from the first name to the third name for performing the modification operation.

6 . The computer-implemented method of claim 5 , wherein accesses by the first application to the first set of database tables via the first projection view mapping from the first name to the second name occur in parallel with accesses by the second application to the second set of tables via the second projection view mapping from the first name to the third name for performing the modification operation.

7 . The computer-implemented method of claim 1 , wherein the modification operation is a lifecycle management operation.

8 . The computer-implemented method of claim 1 , further comprising generating a database trigger to cause changes made to the first set of database tables to also be made to the second set of database tables while the modification operation is ongoing.

9 . The computer-implemented method of claim 1 , wherein the third name is generated by prepending a MOD prefix to the second name.

10 . A system comprising:

at least one processor; and

at least one memory storing instructions that, when executed by the at least one processor, cause operations comprising:

accessing a first set of database tables via a first projection view mapping from a first name to a second name;

detecting an indication of a modification operation targeting the first set of database tables;

creating a second set of database tables for storing results of the modification operation, wherein the second set of database tables are a modified version of the first set of database tables;

responsive to detecting a completion of the modification operation:

remapping the first projection view from the first name to a third name, wherein the third name is associated with the second set of database tables; and

accessing the second set of database tables via the first projection view mapping from the first name to the third name.

11 . The system of claim 10 , wherein accesses targeting the first set of tables subsequent to the completion of the modification operation are redirected to the second set of tables.

12 . The system of claim 10 , wherein the operations further comprise continuing to enable access to the first set of database tables via the first projection view mapping from the first name to the second name while the modification operation is ongoing.

13 . The system of claim 12 , wherein the operations further comprise generating a second projection view mapping from the first name to the third name.

14 . The system of claim 13 , wherein the operations further comprise accessing the second set of tables via the second projection view mapping from the first name to the third name for performing the modification operation.

15 . The system of claim 14 , wherein accesses by a first application to the first set of database tables via the first projection view mapping from the first name to the second name occur in parallel with accesses by a second application to the second set of tables via the second projection view mapping from the first name to the third name for performing the modification operation.

16 . The system of claim 10 , wherein the modification operation is a lifecycle management operation.

17 . The system of claim 10 , wherein the third name is generated by prepending a MOD prefix to the second name.

18 . A non-transitory computer readable medium storing instructions, which when executed by at least one data processor, cause operations comprising:

accessing, by a first application, a first set of database tables via a first projection view mapping from a first name to a second name;

detecting an indication of a modification operation targeting the first set of database tables;

creating a second set of database tables for storing results of the modification operation, wherein the second set of database tables are a modified version of the first set of database tables;

responsive to detecting a completion of the modification operation:

remapping the first projection view from the first name to a third name, wherein the third name is associated with the second set of database tables; and

accessing, by the first application, the second set of database tables via the first projection view mapping from the first name to the third name.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 19, 2024
From: KRUEMPELMANN, WULF; OFENLOCH, DOMINIK
To: SAP SE
Reel/Frame 066824/0560 →
Continuity (1)
Related Publication 20250298778A1 · Sep 25, 2025
References Cited (16)
US 10789220B2 · Mayer · 2020 [cited by examiner]
US 10891273B2 · Mayer · 2021 [cited by examiner]
US 10936624B2 · Kruempelmann · 2021 [cited by examiner]
US 11416509B2 · Patel · 2022 [cited by examiner]
US 12038907B1 · Gosain · 2024 [cited by examiner]
US 20040177063A1 · Weber · 2004 [cited by examiner]
US 20180137010A1 · Mayer · 2018 [cited by examiner]
US 20180137145A1 · Mayer · 2018 [cited by examiner]
US 20180285390A1 · Mayer · 2018 [cited by examiner]
US 20190050213A1 · Schanafelt · 2019 [cited by examiner]
US 20190377820A1 · Kruempelmann · 2019 [cited by examiner]
US 20200349176A1 · Daimler · 2020 [cited by examiner]
US 20250139066A1 · Eberlein · 2025 [cited by examiner]
US 20250209742A1 · Richwagen · 2025 [cited by examiner]
Preserving mapping consistency under schema changes (Year: 2004). [cited by examiner]
Map Projections (Year: 2014). [cited by examiner]