Sap Ag

Sap Se

Uwe E Fischer

Daniel Buchmann

Olivier Ficatier

Jochen Hoenig

Oliver Scheerer

Guillaume Duchene

Bernhard P Waldscheck

Wolfgang Kalthoff

Gordon Muehl

Franz Weber

Michael Demuth

Robert Lang

Ebru Polat

Paresh Deshpande

Lutz Rosenpflanzer

Christoph Lenschow

Cristina Ferro

Axel Haury

Jochen Schmitt

Bernhard Suchanek

Alexandra Suchanek, Legal Representative

Daniela Heep

Klaus Stadlthanner

Andreas Muecklich

Biju Jatheendran

Markus Breiter

Jochen Hönig

Alexandra Suchanek

The present disclosure describes methods, systems, and computer program products for integrating authorizations. One computer-implemented method includes: reading enterprise data warehouse (EDW) authorizations for a user from an authorization database in response to a query generated by the user for EDW data; responsive to a determination that the user is assigned to an environment, reading environment authorizations from a business planning and consolidation (BPC) system; enhancing the EDW authorizations for the user with the environment authorizations read from the BPC system to create a new authorization set; reading a user-based data access profile (DAP) from the BPC; and intersecting the new authorization set with the DAP to create an overall user authorization set.

Integration of centralized and local authorizations for multi-dimensional data

A data warehouse incorporates processing for creating, managing, and otherwise maintaining master data. The data warehouse may communicate with a master data manager to obtain services for handling master data. A surrogate master data identifier may be defined by the data warehouse to reference the master data, thereby decoupling any modifications of the master data identifier that may be made by the master data manager. The data warehouse may export the master data to an application system, and conversely import master data from an application system.

Master data management in a data warehouse/data mart

Embodiments implement data and meta data versioning in order to adapt reported data ('actuals') for planning purposes. A versioning engine receives from an operative system (e.g. ERP system), root variants. These root variants may comprise existing actual data and corresponding underlying corporate meta data. Based upon user input, the versioning engine creates from these root variants, additional variants of the data and/or meta data. A new data variant may be based upon the original corporate meta data unchanged (e.g. for projecting existing product lines). A data variant may alternatively be based upon a new meta data variant reflecting changes to the original corporate meta data (e.g. for adopting an entirely new product line). By effectively depicting relationships between actual data and plan data, and between that data and its underlying meta data, versioning allows a user to visualize evolution of actual data into plan data for forecasting purposes.

Data and meta data variants extending actual data for planning

Processing proposed changes to data includes notifying a server of a proposed change to master data, receiving, from the server, an indication as to whether there is a concurrent change to the master data, where the concurrent change corresponds to a change to the master data in addition to the proposed change, and deciding whether to make the proposed change or to abort the change.

Processing proposed changes to data

Memory stores data for access by a computer program that is capable of being executed on a data processing system. A data structure is stored in the memory, which includes information resident in a database used by the computer program. The information includes payload data made up of data objects, process data for a process associated with the data objects, and a header that includes technical data for transmitting the data structure.

Process data for a data packet

A directory includes information about various systems (e.g., applications, processes, tasks, objects, services) and data, and may include data ownership information. The directory may define existing systems, corresponding locations by address, and corresponding semantic names. The directory may also specify the role of each system, e.g., a consumer or provider role. The directory may also define a scope of data a provider system can provide. As such, the directory may also include information about whether and how such data is being replicated. When a user requests data, a service may, based on the directory, determine and select an appropriate provider system for the data. The service may further create a subscription process to provide the user a local cache of the requested data. With such directory information, a service can provide data access services that integrate subscription processes.

Services for data access based on a data ownership directory in distributed system landscapes

A request is received to initiate an operation (e.g., a query, etc.) on a view on a business object type. Such a request contains data characterizing the view which in turn characterizes a plurality of hierarchically arranged elements. Such elements characterized are associated with elements characterized by one or more business objects types. Thereafter, the operation is performed on the elements of the two or more business objects types. Responsive results of the operation responsive are mapped to the elements of the virtual business object type. After such mapping occurs, a message is generated that contains the results of the request in a structure compatible with the view.

On-request views of business object types

Embodiments consistent with the invention provide a computer-implemented method for providing a cross-system log in a distributed computer system environment having multiple computer systems. The method comprises electronically receiving data in a first system, the data including cross-system characteristics of a cross-system activity originating from a second computing system, electronically storing the data, electronically receiving a request to access the data, and electronically providing the requested data.

Cross-system log in a distributed system environment

Software and content used by the software are developed on a first computer system for use on a second computer system. Transferable forms of the developed software and content that may be used by the second computer system are created. The transferable form of the developed software is made available for transfer to the second computer system. The transferable form of the developed content is transferred to a content server that makes a transferable form of content used by software running on the second computer system available for receipt by the second computer system. The transferable form of the developed software from the first computer system and the transferable form of the content from the content server are received at the second computer system. The received software and content are translated into usable forms of the software and content that may be used by the second computer system.

Common transport logistics for software and content

A first device transmits messages to a second device. The first device keeps track of messages that have already been transmitted from the first device to the second device, experiences an interruption in transmission of messages at the first device, and resumes the transmission from the first device following the interruption. Resuming the transmission includes transmitting only messages that have not already been completely transmitted from the first device to the second device.

Data transmission process

Methods and apparatus, including computer program products, are provided for processing messages including structured data, such as objects and business objects. The method may include a receiver inhibiting processing of a first message including a first object referencing a second object, when the receiver of the first message does not include key mapping information for the second object. The receiver may then receive key mapping information determined for the second object, when a second message, received at the receiver, includes the second object without references to another dependent object. The mapping information may be representative of a location of the second object. The receiver may then automatically resume processing of the first message, when the key mapping information is received. Related apparatus, systems, methods, and articles are also described.

Active sequencing

Correcting errors in data objects includes executing a main process to process the data objects, detecting an error in a first data object via the main process, sending, to an error correcting process, the data object and information associated with the error, and instantiating an instance of the error correcting process to attempt to correct the error. The error correcting process is implemented using substantially a same environment as the main process. The main process continues to execute during and after sending the data object and the information to the error correcting process and while the error correcting process attempts to correct the error.

Error handling process

The subject matter disclosed herein provides methods and apparatus, including computer program products, for determining keys for use with data structures, such as objects, business objects, view business objects, and the like. In one aspect, there is provided a computer-implemented method. The method may include determining a first key of a view business object node by combining one or more keys of the business object nodes used to form the view business object node, the first key used to identify the view business object node when the view business object node is a root node. The method may also include determining, when the view business object node has a parent node, a second key of the view business object node by combining the first key and at least one key of the parent node, the second key used to identify the view business object node. Next, the method may store at least one of the first key and the second key to identify the view business object node during a query or a retrieve operation associated with a database. Related apparatus, systems, methods, and articles are also described.

Key management and high performance runtime for view business objects

A system to compare process sizes is described. In one example embodiment, the system comprises memory and one or more processing devices. The memory may be configured to store executable instructions. The one or more processing devices may be configured to execute the instructions. The instructions may cause the one or more processing devices to generate a first process that corresponds to an activity, generate data objects that correspond to the elements associated with the activity, and identify a number of data objects associated with the first process. The one or more processing devices may further obtain a reference size for the first process based on the number of data objects and compare the reference size for the first process with the reference size for another process.

Comparing process sizes

Change-driven replication includes determining in a first replication data included in a collection of business master data by performing an explosion of the collection of business master data and transmitting the data to be replicated from a central data system to one or more target data systems, determining which data included in the collection of business master data has changed since the first replication by exploding only the changed data, replicating only the changed data in a second replication, and transmitting the changed data from the central data system to at least one of the target data systems.

Growing community of inventors

Karlsruhe, Germany

Uwe E Fischer