Sap Ag

Michael Meyringer

Frank Brunswig

Otfried Von Geisau

Andreas Huppert

Bernd Schmitt

Daniel Bock

Dirk Henrich

Dieter Krisch

Ralf Klein

Volker Faisst

Silke Massmann

Ralph Rillig

Edwin Himmelsbach

Udo Peter Klein

Bare Said

Gerd Ritter

Jens Freund

Peter Latocha

Matthias Richter

Guenter Pecht-Seibert

Horst Schaude

Baré Said

Thomas Gauweiler

Stefan Kaetker

Gerd Moosmann

Tim Kornmann

Rene Gross

Frank Renkes

Gunther Liebich

Adam Polly

Michael Neumann

Michael Conrad

Georg Dopf

Toralf Grossmann

Dirk Stumpf

Matthias Schmitt

Jens Kisker

Ingo Bruss

Kai-Michael Roesner

Udo Laub

Andreas F Morsch

Peter Von Zimmermann

Andreas Reccius

Ralf Dinkel

Markus Klein

Juergen Kind

Ralf Helmut Philipp

Thomas Schachner

Andreas Neumann

Michael Hohendorf

Otfried Geisau

Michael Bauer

Silke Storch

Frank Damaschke

Tim Gaiser

Martin Schorr

Torsten Bachmann

Florian Rehfeld

Michael Sylvester

Manfred Hirsch

Ashwin Reddy Yeddula

Andrea Roesinger

Gerald Paetzold

Joachim Puteick

Martin Rogge

Hendrik Geipel

Klaus Bahr

Holger Handel

Rainer Soltek

Andrea Pluemper

Kai-Uwe Pielka

Stefan Miller

Local dependency metadata can be collected from local metadata repositories of a plurality of development systems in a layered development system landscape, and a global where-used list that includes intra-layer and inter-layer dependencies between development entities in a layered development system landscape can be created, for example by aggregating the collected local dependency data. A usage metric quantifying how frequently each development entity is depended upon by other development entities in the layered development system landscape can be assigned to each development entity in the layered development system landscape. A measure of a relative effect of a change to one of the development entities on other development entities in the layered development system landscape can be promoted.

Impact analysis and adoption planning based on global where-used lists

A computer-implemented system may include reception, from a user interface client application, of a user interface request conforming to a user interface component model, translation of the user interface request from the user interface component model to a business object model, execution of interactions associated with the translated request with a backend service layer, the interactions conforming to the business object model, determination of business object node changes and business object property changes conforming to the business object model and corresponding to the interactions, translation of the business object node changes and the business object property changes to user interface data changes and user interface event property changes conforming to the user interface component model, and provision of the user interface data changes and user interface event property changes to the user interface client.

Separation and interlinkage of UI model and service layer model

Methods and apparatus, including systems and computer program products, for a services architecture design that provides enterprise services having accounting functionality at the level of an enterprise application. The design includes a set of service operations, process components, and optionally deployment units. Suitable business objects are also described.

Providing accounting software application as enterprise services

Methods and apparatus, including systems and computer program products, for a services architecture design that provides enterprise services having foundation layer functionality at the level of an enterprise application. The design includes a set of service operations, process components, and optionally deployment units. Suitable business objects are also described.

Foundation layer for services based enterprise software architecture

Methods, systems, and apparatus, including computer program products, for implementing a software architecture design for a software application implementing an internal projects application useful for planning and executing internal projects and measures, including network scheduling, resource staffing, cost estimation and management, time confirmation, and progress monitoring. The application is structured as multiple process components interacting with each other through service interfaces, and multiple service interface operations, each being implemented for a respective process component. The process components include a Costing process component that maintains project cost estimates; an Accounting process component that records relevant business transactions; a Project Processing process component that structures, plans and executes simple, short-term measures and complex projects; and a Time and Labor Management process component that supports the definition of employees' planned working times as well as the recording of the actual working times and absences and their evaluation.

Architectural design for internal projects application software

Systems, methods, computer program code, and means are provided for processing retrieve requests received in a business software system. Pursuant to some embodiments, a retrieve request is processed by identifying that the requested node is a retrieve transformation node, determining that the node relates to one of a currently selected business object and a secondary business object, and retrieving the node data from one of a persistence buffer and a secondary buffer based on the determining.

Performance optimized retrieve transformation nodes

This disclosure involves back-end field control of layered software. For example, a method for providing back-end field control of an interface can comprise receiving a request to update one or more attributes of a business object, where the request is associated with a first software layer. The method then identifies one or more additional software layers associated with the business object and determines whether the request can update to the one or more attributes violate settings of the one or more attributes associated with the one or more additional software layers.

Back-end field control for multiple software layers

This disclosure involves dynamic business object properties for Enterprise Service Architecture (ESA) or other Service Oriented Architecture (SOA) architectures. For example, a method for dynamically modifying an interface in a SOA can comprise receiving a request for an interface associated with a business object, where the interface includes a plurality of fields configured to receive information from a client. The method can further identify current values of one or more attributes associated with the business object and dynamically modify at least one of the fields of the interface based, at least in part, on one or more of the current values.

Dynamic business object properties for SOA architectures

A method and system for allowing a rollback within a multi-object system infrastructure are provided. In embodiments, a rollback to a state of a software business object is effected. A sync point manager maintains, for example, a list of sync points and their respective associated identifiers and relationship data. When under sync point protection, i.e., a sync point is set, each subsequent object, when created, is requested to prepare a buffer associated with the specific sync point, so that if an error occurs, a request to rollback to the state associated with the sync point is effectable. Multiple sync points may be kept track of by the sync point manager. In further embodiments, the sync points may be associated with a variety of different types of objects.

System and method for business object sync-point and rollback framework

Computer-implemented methods and computer program products implement techniques for representing a project in a web application. The techniques include generating, through a Web server, a description of a project in HTML code, creating a graphic display of at least a portion of the project in the form of a chart in a browser, receiving user input manipulating the HTML element in the graphic display of the chart, and dynamically updating the graphic display of the chart in response to the user input with a plurality of instructions that manipulate the document object model of the browser. The browser includes a document object model and the chart includes a graphic representation of an HTML element.

Interactive and web-based Gantt Chart

Growing community of inventors

Rauenberg, Germany

Michael Meyringer