Dependency handling for configuration transport

Patent metadata

Field	Value
Publication number	US-11567808-B2
Application number	US-201916712386-A
Country	US
Kind code	B2
Filing date	Dec 12, 2019
Priority date	Dec 12, 2019
Publication date	Jan 31, 2023
Grant date	Jan 31, 2023

Abstract

Systems and methods include reception of an indication of a first data object to transmit from a first database tenant to a second database tenant, the first data object comprising user configuration settings metadata of a database application and associated with a first data object type, determination of whether a dependent data object may be associated with a data object of the first data object type, determination, if it is determined that a dependent data object may be associated with a data object of the first data object type, of whether a dependent object is dependent on the first data object, and automatic determination, if it is determined that a dependent object is dependent on the first data object, to transmit the dependent object from the first database tenant to the second database tenant.

First claim

What is claimed is:

1. A system comprising:
a memory storing processor-executable process steps;
a processing unit to execute the processor-executable process steps to cause the system to:
receive an indication of a first data object of a first database tenant to add to a transport request to transmit the first data object from the first database tenant to a second database tenant, the first data object being associated with a first entity type and comprising configuration settings of a database application;
determine, based on a registry entry for the first entity type associated with the first data object, whether the first entity type of associated with the first data object is permitted, whether optional or mandatory, to be associated with a dependent object of the first database tenant;
in an event it is determined that the first entity type of the first data object is permitted to be associated with a dependent object, determine a first dependent object associated with the first data object;
determine whether the first dependent object associated with the first data object is one of a mandatory dependent of the first data object and an optional dependent of the first data object;
automatically add, in the instance the first dependent object is determined to be a mandatory dependent of the first data object, to the transport request in addition to the first data object, the first dependent object to transmit from the first database tenant to the second database tenant.

2. A system according to claim 1 , the processing unit to execute the processor-executable process steps to cause the system to:
present an indicator of the first dependent object;
receive an instruction to present a data object on which the first dependent object is dependent;
in response to the instruction, present an indicator of the first dependent object.

3. A system according to claim 1 , the processing unit to execute the processor-executable process steps to cause the system to:
in an event it is determined that a first entity type of the first dependent object is permitted to be associated with a dependent object, determine a second dependent object associated with the first dependent object.

4. A system according to claim 1 ,
wherein determination of the first dependent object associated with the first data object comprises querying of a first provider associated with the first entity type.

5. A system according to claim 4 , the processing unit to execute the processor-executable process steps to cause the system to:
receive an indication of a second data object to add to a transport request to transmit the second data object from the first database tenant to the second database tenant, the second data object being associated with a second entity type and comprising configuration settings of the database application;
determine whether the second entity type of the second data object is permitted to be associated with a dependent object based on the second entity type;
in an event it is determined that a second entity type of the second data object is permitted to be associated with a dependent object, determine a second dependent object associated with the second data object by querying a second provider associated with the second entity type.

6. A system according to claim 1 , the processing unit to execute the processor-executable process steps to cause the system to:
determine one or more other dependent objects associated with the first data object;
receive a selection of one or more of one or more other dependent objects; and
add to the transport request, the selected other dependent objects to transmit from the first database tenant to the second database tenant.

7. A system according to claim 6 , wherein determination of whether a first entity type of the first data object is permitted to be associated with a dependent object is based on the first entity type,
wherein determination of the first dependent object associated with the first data object comprises querying of a first provider associated with the first entity type, and
wherein determination of the one or more other dependent objects comprises querying of the first provider.

8. A computer-implemented method comprising:
receiving an indication of a first data object of a first database tenant to add to a transport request to transmit the first data object from a first database tenant to a second database tenant, the first data object being associated with a first entity type and comprising user configuration settings metadata of a database application and associated with a first data object type;
determining, based on a registry entry for the first entity type associated with the first data object, whether the first entity type associated with the first data object is permitted, whether optional or mandatory, to be associated with a data object of the first database tenant;
in an event it is determined that the first entity type of the first data object is permitted to be associated with a data dependent object, determining a first dependent object associated with the first data object;
determining whether the first dependent object associated with the first data object is one of a mandatory dependent of the first data object and an optional dependent of the first data object; and

in an event it is determined that the first dependent object is a mandatory dependent of the first data object, automatically add to the transport request, in addition to the first data object, the first dependent object to transmit from the first database tenant to the second database tenant.

9. A method according to claim 8 , further comprising:
presenting an indicator of the first dependent object;
receiving an instruction to present a data object on which the first dependent object is dependent;
in response to the instruction, presenting an indicator of the first dependent object.

10. A method according to claim 8 , further comprising:
in an event it is determined that a first entity type of the first dependent object is permitted to be associated with a dependent object, determining a second dependent object associated with the first dependent object.

11. A method according to claim 8 ,
wherein the determination of the dependent object comprises querying of a first provider associated with the first entity type.

12. A method according to claim 11 , further comprising:
receiving an indication of a second data object to add to a transport request to transmit the second data object from the first database tenant to the second database tenant, the second data object comprising user configuration settings metadata of a database application and being associated with a second data entity type;
determining whether a dependent data object is permitted to be associated with a data object of the second data entity type;
in an event it is determined that a dependent data object is permitted to be associated with a data object of the second data entity type, determining whether a dependent object is dependent on the second data object; and
in an event it is determined that a second dependent object is dependent on the second data object, automatically determining to transmit the second dependent object from the first database tenant to the second database tenant.

13. A method according to claim 8 , further comprising:
determining one or more other dependent objects;
receiving a selection of one or more of one or more other dependent objects; and
adding to the transport request to transmit the selected other dependent objects from the first database tenant to the second database tenant.

Assignees

• Sap Se

Inventors

• Gera Gaurav Loknath
• Steiert Martin
• Keller Martina
• Kumar Sameer
• Gieselmann Thomas
• Schaude Horst

Classifications

• G06F16/2282

  Tablespace storage structures; Management thereof · CPC title

• G06F9/5077 Primary

  Logical partitioning of resources; Management or configuration of virtualized resources (specific details on emulation or internal functioning of virtual machines G06F9/455) · CPC title

• G06F16/213

  with details for schema evolution support · CPC title

• G06F16/27

  Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor · CPC title

• G06F16/21 Primary

  Design, administration or maintenance of databases · CPC title