Abstract: A system receives database tables from a plurality of computer systems. Each of the database tables is associated with a particular computer system. Each particular computer system is associated with a particular schema. The database tables are stored in a computer storage device according to the particular schema of the computer system with which each database table is associated. Database views are created and stored. Each of the views is associated with a particular schema. A configuration table according to the particular schemas of each of the computer systems is generated. The configuration table is displayed on a display device. A selection of one or more schemas is received from the display on the computer display device. The database view from one of the selected database schemas is used as a template to generate a view for all of the selected schemas.

Abstract: Database content provisioning includes a broad base shipment as an initial release of database content. The database content may then be incrementally enriched with specific enhancements, which may be delivered as updates. Shipping variants for delivering upgrades include delta installations, and in some embodiments, may include full installations. Changes to an existing database object in activated database content may be treated as a new database object, and may include a reference to the existing database object. The user is notified of the new database object, but the new database object is otherwise not activated, thus ensuring stability of the activated database content.

Abstract: Various embodiments include at least one or systems, methods, and software providing abilities to automatically generate a test plan that mitigates risk involved in testing less than an entirety of a software system following modification. Some embodiments operate to allow a user to influence the scope of an optimized test plan while also reducing a number of tests and test execution effort involved. Such embodiments may identify portions of the software system to test and portions of the software system that will not be tested in a manner that reduces a total testing effort involved. Reductions in testing effort are performed in generation of the test plan in view of testing preferences which are utilized not only to reduce the total effort in executing a test plan, but also does so to optimize the test plan.

Abstract: A system, computer readable medium, and method for automatically testing computer objects affected by an update package. The exemplary method may compare computer objects/instances in an update package with those of the installed version of the computer application. A set of computer objects that have changed in the update package as compared to the installed version may be generated. The changes to each of the computer objects in the set of changed objects may be analyzed to determine if an automated test is related to the changed object. If an object has a related automated test assigned to it, the object may be placed in a separate list for testing. The automated tests of the changed objects in the separate list may be organized into a test plan. The automated tests may be executed according to the test plan. The system may have servers and computer processors to implement the method.

Abstract: A computer system includes a first database system that includes a plurality of tables, and a second database system that includes a subset of the tables in the first database system. The system identifies a plurality of reports that are currently generated using the second database system. The system also identifies a plurality of reports that are not currently generated using the second database system, but that are capable of being generated using the second database system, and displays a list of these reports on a computer display device. In an embodiment, the system further replicates one or more tables that are required for generation of additional reports from the first database system to the second database system.

Abstract: Embodiments of the present invention may provide “undo” (e.g., rollback) features, along with data management simplification features, to an update package model of software suite development/evolution. New functions, which may have disruption effects for customers, may be installed into the core configuration data with inactive switches. Upon activation, a switch status may change, and a query filter may use the activated function (e.g., as associated with the switch ID). Original functions may be maintained, giving the user the ability to deactivate an activated function, and thereby reverting the system back to the prior configuration status.

Abstract: A tailored add-on component for a released software product having internal and released development objects. The released development objects are designed for external use, such as end-user customization. The internal development objects are designed for use within the released software product, with no access from outside components. The tailored add-on component adds a functional application that makes calls to both released and internal objects. Access to internal objects is made while maintaining stability by confining internal object calls to a single adaptation component within the add-on, while also implementing an interface for the objects of the software product that are used by the add-on. The interface includes a function to freeze objects that are in the interface, and a set of automatic test components to identify changes in the objects that are in the interface.

Abstract: In an example embodiment, a delivery unit comprises a plurality of objects. The delivery unit is encapsulated within a transport container for delivery to an entity for installation. As new versions of the objects are created by modifying the source code, the modified versions of objects are included in the delivery unit along with unmodified versions of the remaining objects of the delivery unit. The modified versions of the objects are marked for installation, while the unmodified versions are not marked for installation. Upon installation, the objects marked for installation are extracted from the delivery unit while the objects not marked for installation are discarded. The extracted objects are then installed, thus updating any previous versions of the objects, while unmodified objects are not installed. In one representative embodiment, objects are procedures of a database system, which may be organized hierarchically into folders.

Abstract: In an example embodiment, a tri-state variable associated with a table in a database indicates whether the table is automatically sorted at runtime or left unsorted. The value of the tri-state variable also indicates whether code associated with the table assumes the table will be sorted at runtime. In a situation where two parties have code that utilize the table, when the first ensures its code to no longer assumes the table will be sorted, they may set the value of the tri-state variable from automatic sorting enforced to automatic sorting recommended. In this state the table will still be automatically sorted at runtime. When the second ensures its code no longer assumes the table will be sorted, they may set the value of the tri-state variable from automatic sorting recommended to no automatic sort at which time the table is left unsorted.

Abstract: Embodiments of methods and systems for database viewing, create a copy of a vendor view in a customer view layer that is present between an interface layer and the database layer. In certain embodiments this copy of the vendor view may contain no customer specific logic, simply serving as a 1:1 projection in the customer view allowing the vendor to track customer access to particular vendor views. According to some embodiments, the copy of the vendor view may be changed to create a modification view. Changes are applied to the modification view only, leaving the original vendor view unchanged with a link to the stored modification copy. This link can be used to adjust the modification copy whenever a hot fix or a new version of the ‘modified’ database content is installed to the customer system. Embodiments may support consumer extensions to the vendor views and/or to the database itself.

Abstract: A tailored add-on component for a released software product having internal and released development objects. The released development objects are designed for external use, such as end-user customization. The internal development objects are designed for use within the released software product, with no access from outside components. The tailored add-on component adds a functional application that makes calls to both released and internal objects. Access to internal objects is made while maintaining stability by confining internal object calls to a single adaptation component within the add-on, while also implementing an interface for the objects of the software product that are used by the add-on. The interface includes a function to freeze objects that are in the interface, and a set of automatic test components to identify changes in the objects that are in the interface.

Abstract: A computer-implemented method for selecting one or more functions for display is provided. The selection may be performed via an implementation guide that is a hierarchy comprising nodes. A node may represent one function. The method may comprise retrieving a first list of switches in response to selection of a function, extracting one or more switches from the first list such that the extracted switches include function switches and/or conflict switches, determining whether each of the extracted switch is an active conflict switch and, if yes, adding the active conflict switch to a second list of switches. After removing all switches from the first list or having added all of them to the second list, the method processes the second list to determine which functions can be executed on the processor without conflicts and presenting a function GUI element representing a function determined to be executable without conflicts.

Abstract: The invention may provide “undo” (e.g., rollback) features, along with data management simplification features, to an update package model of software suite development/evolution. New functions, which may have disruption effects for customers, may be installed into the core configuration data with inactive switches. Upon activation, a switch status may change, and a query filter may use the activated function (e.g., as associated with the switch ID). Original functions may be maintained, giving the user the ability to deactivate an activated function, and thereby reverting the system back to the prior configuration status.

Abstract: This disclosure includes a method, a system and a computer readable medium. The method includes receiving a data model configured to model data in a first database schema in a database system, using the received data model to generate a first data view of a first instance of the first database schema in the database system, including referencing, using a first view variant, one or more data tables including the first instance of the first database schema to generate the first data view, and using the received data model to generate a second data view of a second instance of the first database schema in the database system, including referencing, using a second view variant, one or more data tables including the second instance of the first database schema to generate the second data view.

Abstract: A method includes identifying a table over a conventional database used by an application, creating a view of the table equivalent to the identified table in an in-memory database, and calling the view with a same call as used for the identified table such that calling the view via the application provides a same result as would have been obtained from the same call to the table in the conventional database.

Abstract: A data model may be designed based views of a pre-existing data model. Metadata associated with the pre-existing data model may be presented to the user to support the user's design effort. The metadata may inform and otherwise guide the user's design choices to reduce the likelihood of inconsistencies between the new data model and the pre-existing data model. The metadata may also be used to identify and warn the user of potential inconsistencies between the new data model and the pre-existing data model.

Abstract: A data model specific to a database schema is received in a database system. The received data model may be applied to a first instance of the database schema to generate a data view of the first database schema. The received data model may be applied to a second instance of the database schema to generate a second data view of the second database schema.

Abstract: Schema mapping is provided at several levels of granularity to generate views from a data model. The schema mapping allows for the database tables referenced among the data views contained in the data model to come from a collection of several physical schemas, even though the data model may comprise a single authoring schema.

Abstract: Various embodiments include at least one or systems, methods, and software providing abilities to automatically generate a test plan that mitigates risk involved in testing less than an entirety of a software system following modification. Some embodiments operate to allow a user to influence the scope of an optimized test plan while also reducing a number of tests and test execution effort involved. Such embodiments may identify portions of the software system to test and portions of the software system that will not be tested in a manner that reduces a total testing effort involved. Reductions in testing effort are performed in generation of the test plan in view of testing preferences which are utilized not only to reduce the total effort in executing a test plan, but also does so to optimize the test plan.

Abstract: Database content provisioning includes a broad base shipment as an initial release of database content. The database content may then be incrementally enriched with specific enhancements, which may be delivered as updates. Shipping variants for delivering upgrades include delta installations, and in some embodiments, may include full installations. Changes to an existing database object in activated database content may be treated as a new database object, and may include a reference to the existing database object. The user is notified of the new database object, but the new database object is otherwise not activated, thus ensuring stability of the activated database content.