Sap Se

Makesh Balasubramanian

Tejram Jagannath Sonwane

Shiva Prasad Nayak

Ashwin Vijayendra

Pradeep Panda

Poornesh Bharathipura Sharma

Ashudeep Reshi

Sudhansu Mohanty

Indeevar Reddy Aduri

Venkatram Vundavalli

Joseph Ashok Kumar

Rishul Matta

Sai Harish Balantrapu

Akhila Rao

Nanda Hiregowdar

Methods and system are disclosed that improve a user experience to develop a data model. In one aspect, an entity model extensible markup language (EDMX) file is received by an integrated development environment (IDE). The contents of the EDMX file including elements, attributes and attribute values are displayed via a text editor of the IDE. Based on an input received to modify the attributes or the attribute values via the text editor, the graphical model may be instantiated to generate and display the modified attributes or attribute values in an ER editor. Based on an input received to modify the attributes or the attribute values on the ER editor, a text editor model may be instantiated to display the modified attributes or the attribute values in the text editor. The IDE improves the user experience to model and develop data models.

Integrated development environment with multiple editors

Embodiments relate to converting data object(s) from a multi-source database environment into a single-source database environment. Such a conversion may be desirable to increase performance and/or reduce consumption of processing resources. An engine is configured to receive a multi-source database universe from a repository. The engine analyzes that universe to identify details thereof for conversion, e.g., connections, tables, views, alias tables, etc. A new single-source connection is registered, and then the single-source universe is re-generated through a universe conversion algorithm, an automatic function mapping algorithm, and a query generation algorithm. Embodiments avoid labor intensive manual re-creation of the universe, and may be implemented as an automatic conversion wizard also updating dependent report queries per new single-source query patterns. Particular embodiments converting from multi-source database environment available from SAP AG, may utilize a Software Design Kit (SDK) to create a migration plug-in as part of an Information Design Tool (IDT).

Converting data objects from multi- to single-source database environment

The present disclosure describes methods, systems, and computer program products for providing a web-based integrated development environment (IDE) solution hosted on a cloud environment. One computer-implemented method includes receiving an entity data model extensible markup language (XML) (EDMX) model, receiving an indication of user input from a user input device, providing auto completion suggestions based on received user input, determining whether the provided auto completion selections are acceptable, and determining whether the ECMX model is complete and in a logical state.

Adaptive, context-aware, model-based suggestions

Embodiments relate to converting data object(s) from a single-source database environment into a multi-source database environment. An engine is configured to receive a single-source database universe from a repository. The engine analyzes that universe to identify details thereof for conversion, including but not limited to connections, tables, views, alias tables, etc. A new multi-source connection is registered, and then the multi-source universe is re-generated through a universe conversion algorithm, an automatic function mapping algorithm, and a query generation algorithm. Embodiments avoid labor intensive manual re-creation of the universe, and may be implemented as an automatic conversion wizard also updating dependent report queries per new multi-source query patterns. Particular embodiments converting a single-source database environment available from SAP AG, may utilize a Software Design Kit (SDK) to create a migration plug-in as part of an Information Design Tool (IDT).

Converting data objects from single- to multi-source database environment

Embodiments relate to reporting data of project artifacts in a multi-source universe database environment. In embodiments, an analytics module is configured to receive as input, data in target tables of a data federator. With reference to a file, the analytics module creates a federated table in a federator layer of an Information Design Tool (IDT) in a multi-source universe database environment. The federator layer may also include data source references, objects, and mapping rules. This migration process allows the IDT to preserve with the federated tables, previously created mapping rules defining the complex logical relationship between the target tables and the underlying database data. These mapping rules are used in creating project-based reports of the federated table data in the multi-source database universe environment. In this manner, data can be migrated to a multi-source database universe, while conserving previous effort to define logical relationships between federated data and the database.

Migrating federated data to multi-source universe database environment

A semantic layer (universe), which is created on a source database (DB), is migrated to a target DB. The migration includes pre-migration steps, actual migration and post-migration steps. The pre-migration steps prepare the target DB for the actual migration by configuring the target DB and determining the differences between the source DB and the target DB. During the actual migration, data, tables and views are migrated to the target DB conforming to the target database structure, functions and configuration. A new universe is created on the target database and all consumers of the source universe such as created reports are changed to refer to the new universe.

Growing community of inventors

Bengaluru, India

Makesh Balasubramanian