Sap Ag

Silke Massmann

Otfried Von Geisau

Michael Meyringer

Andreas Huppert

Ralph Rillig

Klaus Herter

Archim Heimann

Dieter Krisch

Christian Fuhlbruegge

Volker Faisst

Steffen Springborn

Thomas Kretz

Karlheinz Agsteiner

Andre Doerfler

Arno Mielke

Alexander Stefan Adam

Dorothea Martin

Katharina Sorge

Ulrich Spinola

Werner Sottong

Generation of an engineering change case is initiated by associating an identified problem for a product with an engineering change case template. The engineering change case can include a plurality of structured folders that can be populated with content characterizing the identified problem as well as proposed solutions to the identified problem with each folder being assignable to one or more users and having associated deliverables for such users. The various users populate the folders with content associated with the deliverables with at least a portion of the deliverables being delegable and requiring completion in a sequential order. Thereafter, generation of the engineering case can be finalized when an indication is received that all deliverables requiring approval have been completed. Otherwise, the engineering change case can be canceled. Related apparatus, systems, techniques and articles are also described.

Collaborative environment to assess, design, and implement product changes

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

Growing community of inventors

Heidelberg, Germany

Silke Massmann