Sap Ag

Sap Se

Otfried Von Geisau

Jens Freund

Peter Latocha

Gerd Moosmann

Stefan Kaetker

Matthias Tebbe

Peter Fitz

Peter J Neumayer

Dieter Krisch

Paola Sala

Karin Brecht-Tillinger

Michael Meyringer

Arnulf Schueler

Arthur Berger

Ralf Klein

Armin Schwarz

Volker Faisst

Bettina Jaeger

Silke Massmann

Joachim Kenntner

Andreas Huppert

Markus Biehler

Kai-Michael Roesner

Ralph Rillig

Frank Brunswig

Juergen Sattler

Bernhard Thimmel

Klaus Herter

Jens Lemcke

Thomas Schneider

Adam Polly

Bernd Schmitt

Daniel Bock

Archim Heimann

Thomas Moser

Andreas Friesen

Fabian Guenther

Michael Hartel

Marcel Kassner

Christian Fuhlbruegge

Peter Sieber

Christoph Jungkind

Benjamin Braun

Jacques Duparc

Bettina Laugwitz

Marco Pistore

Steffen Springborn

Brit Panzer

Piergiorgio Bertoli

Helgi Thorleifsson

Vytas Cirpus

Karlheinz Agsteiner

Andre Doerfler

Arno Mielke

Alexander Stefan Adam

Thomas Kretz

Edwin Himmelsbach

Thomas Salvador

Stefan Kaetkep

Ulrich Spinola

Werner Sottong

Dorothea Martin

Katharina Sorge

Thomas Gros-Bölting

Gertrud Beisel

Systems, methods, and computer media for implementing a process map navigation tool are provided herein. A process map provides a graphical user interface that represents a process. Icons represent process components or steps and are related using flow connectors to indicate an ordered relationship between the process components. Users can click on an icon and either initiate the corresponding process component or launch a menu of tasks relevant to the step. The icons can also include indicators to provide workflow information.

Process map navigation tool

Methods, systems, and computer-readable storage media for evaluating a validity of an extended status and action management (SAM) schema. In some implementations, actions include receiving the extended SAM schema, the extended SAM schema being stored as a computer-readable document in memory and being an extension of a core SAM schema, providing one or more goals, each goal representing an intention of the core SAM schema, the one or more goals being provided in a computer-readable document stored in memory and comprising one or more primary goals that each express an intention of a process underlying the core SAM schema, and processing the one or more goals using a computer-executable model checking tool for evaluating the validity of the extended SAM schema.

Checking compatibility of extended and core SAM schemas based on complex goals

Methods, systems, and apparatus, including computer program products, for implementing a software architecture design for a software application implementing time recording. 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 Project Processing component that is responsible for structuring, planning, and executing measures or projects, a Time and Labor Management process component that supports the definition of employees' planned working time as well as the recording or the actual working times and absences, an Accounting process component that records relevant business transactions, and a Goods and Service Acknowledgement process component that includes the Goods and Service Acknowledgement business object, which is a document that states the recipient's obligation to pay the supplier for goods received or services rendered.

Architectural design for time recording application software

Methods, systems, and apparatus, including computer program products, for implementing a software architecture design for a software application implementing self-service procurement used to procure goods and services 'ad hoc' by requests from within an organization. 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 an Accounting process component, an Internal Request Processing process component, a Purchase Request Processing process component, a Purchase Order Processing process component, a Goods and Service Acknowledgement process component, a Supplier Invoice Processing process component, a Payment Processing process component, an RFQ Processing process component, and a Due Item Processing process component.

Architectural design for self-service procurement application software

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

Methods, systems, and apparatus, including computer program products, for implementing a software architecture design for a software application implementing service procurement. 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 Project Processing process component; a Purchase Request Processing process component; a Purchase Order Processing process component; a Purchasing Contract process component; a Goods and Service Acknowledgement process component; a Supplier Invoice Processing process component; an RFQ Processing process component that; and a Time and Labor Management process component.

Architectural design for service procurement application software

Methods, systems, and apparatus, including computer program products, for implementing a software architecture design for a software application implementing plan-driven procurement. 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 an Inbound Delivery Processing process component, a Material Inspection Processing process component, a Site Logistics Processing process component, a Confirmation and Inventory process component, a Purchase Request Processing process component, a Purchase Order Processing process component, a Purchasing Contract process component, a Supplier Invoice Processing process component, a Demand Forecast Processing process component, a Supply and Demand Matching process component, an External Procurement Trigger and Response process component, and a Logistics Execution Control process component.

Architectural design for plan-driven procurement application software

A computer-implemented system may include one or more storage devices storing first metadata defining an instance of a first metaobject, second metadata defining an instance of a solution supplement metaobject, wherein the second metadata comprises annotations to the first metadata, and wherein the first metaobject and the solution supplement metaobject are instances of a meta-metaobject. Also stored is executable program code of a service to determine merged metadata based on the first metadata and the annotations to the first metadata. A processor is included to execute the executable program code.

Solution-specific business object view

Methods, systems, and apparatus, including computer program products, for implementing a software architecture design for a software application implementing time recording. The application is structured as multiple process components interacting with each other through service interfaces, and multiple service operations, each being implemented for a respective process component. The process components include a Project Processing process component that supports the management of projects, a Time and Labor Management process component that supports the management of employees timekeeping and work planning, an Accounting process component that records relevant business transactions, a payroll processing process component that supports the execution and monitoring of payroll processes, and a Goods and Service Acknowledgement process component that receives a confirmation from an employee of goods received or services rendered.

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

Methods, systems, and apparatus, including computer program products, for implementing a software architecture design for a software application implementing the selling of project-based services are disclosed. The application is structured as multiple process components interacting with each other through service interfaces, and multiple service operations, each being implemented for a respective process component. The process components include a Project Processing process component that supports the management of projects, a Supplier Invoice Processing process component that manages supplier invoices, an Accounting process component that records relevant business transactions, a Customer Invoice Processing process component that manages customer invoices, and a Goods and Service Acknowledgement process component that receives a confirmation from an employee of goods received or services rendered.

Architectural design for selling project-based services application software

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

Sinsheim, Germany

Otfried Von Geisau