Sap Ag

Sap Se

Jens Freund

Gerd Moosmann

Peter Latocha

Stefan Kaetker

Otfried Von Geisau

Stephan Hetzer

Jochen Steinbach

Jochen Hirth

Matthias Tebbe

Peter Fitz

Peter J Neumayer

Paola Sala

Joachim Kenntner

Andreas Poth

Martin J Wilmes

Renzo Colle

Daniel Bock

Karin Brecht-Tillinger

Achim Clemens

Arnulf Schueler

Frank Wagner

Dieter Krisch

Arthur Berger

Achim Heger

Reiner Bildmayer

Ralf Klein

Armin Schwarz

Bettina Jaeger

Frank Brunswig

Markus Biehler

Kai-Michael Roesner

Andreas Bettin

Wolfgang Barheine

Shai Alfandary

Jochen Wickel

Stefan A Baeuerle

Joachim Fitzer

Gerd Ritter

Guenter Pecht-Seibert

Thomas Fiedler

Baré Said

Thomas Schneider

Gunther Liebich

Reiner P Hammerich

Wolfgang M Koch

Dietmar Nowotny

Adam Polly

Bernd Schmitt

Bernhard Lokowandt

Michael Meyringer

Markus A Peter

Ingo Pfitzner

Thomas Moser

Berthold Wocher

Ami Heitner

Georg Podhajsky

Thomas Nitschke

Tao Yu

Stefan J Moeller

Klaus-Peter Lang

Volkmar Stegmann

Klaus Reinelt

Stefan Adelmann

Andrea Sudbrack

Fabian Guenther

Michael Hartel

Christian Haas

Martin Von Der Emde

Irena Kull

Peter Sieber

Hamid Moghaddam

Alexander Koegler

Thomas Bach

Christoph Jungkind

Michael Picht

Thomas Gross-Boelting

Rainer Heun

Andre Wachholz-Prill

Steffen Hartig

Thomas Reiss

Christian Baeck

Holger Herrmann

Olivier M Dreidemy

Sebastian Pulkowski

Thomas Friedrich

Thorsten Kulick

Nir Pachter

Volker Faisst

Matthias Schwarz

Jacques Duparc

Yuval Morad

Uta Prigge

Cordula Ude

Joachim Barnbeck

Attila Orban

Katja Kasteleiner

Christoph Engler

Sedat Gueler

Sergio Rozenszajn

Helgi Thorleifsson

A computer-implemented system may include an application platform comprising a platform model of a plurality of business objects, each of the business objects comprising a model of data and associated logic, and a public solution model comprising a subset of the platform model. The system may also include a business application, wherein a data model and access logic of the business application are defined based on the public solution model, and wherein the application platform is to provide services to the business application based on the data model, the access logic and the platform model.

Public solution model in an enterprise service architecture

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

Methods, systems, and apparatus, including computer program products, for implementing a software architecture design for a software application implementing service request and order management. 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 Outbound Delivery process component, a Site Logistics Processing process component, a Confirmation and Inventory process component, a Customer Requirement Processing process component, a Supply and Demand Matching process component, a Logistics Execution Control process component, a Service Request Processing process component, a Customer Quote Processing process component, a Service Order Processing process component, a Service Contract process component, and a Service Confirmation Processing process component.

Architectural design for service request and order management application software

Methods and apparatus, including computer program products, to realize a software model are described. A plurality of process components characterizing software implementing a respective and distinct business process is defined, and each of the process components defining a respective service interface for interacting with other process components. The plurality of process components is divided into multiple deployment units, wherein each deployment unit characterizes independently operable software, and each process component is entirely included in exactly one deployment unit. Context independent interactions are defined among the plurality of process components.

Software modeling

Methods, systems, and apparatus, including computer program products, for implementing a software architecture design for a software application implementing ad-hoc goods movement. 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 an Accounting process component that records the relevant business transactions for valuation and profitability analysis; an Inventory Processing process component that handles the management of inventory and the recording of inventory changes and may provide services to maintain current stock, handling unit content, logistics operating unit content, and allocation content; a Site Logistics Processing process component that handles the preparation, physical execution, and confirmation of logistics processes within a site; and a Supply and Demand Matching process component that combines the tasks necessary to ensure that sufficient material receipt elements exist to cover material demand while taking available capacity into account.

Architectural design for ad-hoc goods movement software

Methods and apparatus, including computer program products, to realize a business scenario are described. A plurality of process components and context independent interactions among the process components are defined. Each of the process components characterizes software implementing a respective and distinct process. In addition, each of the process components defines at least one respective service interface for interacting with business objects associated with other process components, and all communication and interaction between process components taking place through the respective interfaces of the process components.

Software model integration scenarios

Methods and apparatus, including computer program products, for defining a software model business object are described. A plurality of business objects and interactions between these business objects are defined. Each business object is operable to encapsulate business data and can be associated with exactly one process component. Each of the process components characterizes software implementing a respective and distinct process and defines a respective at least one service interface for communicating and interacting with business objects in other process components. Moreover, all communication and interaction between process components takes place through the respective interfaces of the process components. Additionally, the interactions among business objects in different deployment units occur solely via the process component interfaces.

Software model business objects

Methods, systems, and apparatus, including computer program products, for implementing a software architecture design for a software application implementing a make to stock process. 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; a Production process component; a Site Logistics process component; a Confirmation and Inventory process component; a Customer Requirement Processing process component; a Demand Forecast Processing process component; a Supply and Demand Matching process component; a Production Trigger and Response process component; an In-house Requirement Processing process component; a Sales Scheduling Agreement Processing process component; and a Demand Planning process component.

Architectural design for make to stock application software

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 operations, each being implemented for a respective process component. The process components include an Inbound Delivery Processing process component, a Site Logistics Processing process component, an Inventory Processing 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

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.

Methods and apparatus, including computer program products, for defining one of a plurality of process components. At least one inbound operation initiated by an external process component to read or modify data encapsulated in a business object solely associated with the process component is defined. Additionally at least one outbound operation to read or modify data encapsulated in a business object solely associated with an external process component is defined. Each of the process components characterizes software implementing a respective and distinct process, and each of the process components defines a respective at least one service interface for communicating and interacting with other process components. In addition, all communication and interaction between process components takes place through the respective interfaces of the process components.

Software model process component

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 and apparatus, including systems and computer program products, for a services architecture design that provides enterprise services having supply chain control 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.

Computer readable medium for implementing supply chain control using service-oriented methodology

Growing community of inventors

Heidelberg, Germany

Jens Freund