Sap Ag

Sap Se

Peter Latocha

Jens Freund

Gerd Moosmann

Stefan Kaetker

Otfried Von Geisau

Matthias Tebbe

Peter Fitz

Peter J Neumayer

Michael Seubert

Werner Gnan

Fabian Guenther

Paola Sala

Dirk Wodtke

Karin Brecht-Tillinger

Jian Xu

Philipp Suenderhauf

Arnulf Schueler

Andrew Y Ng

Andreas Bold

Dieter Krisch

Arthur Berger

Vincent L Mendicino

Yingjiong He

Miro Vins

Chinmaya Sarangi

Neil Srivatsan

Ralf Klein

Armin Schwarz

Bettina Jaeger

Matthias Richter

Stephan Hetzer

Jochen Hirth

Joachim Kenntner

Daniel Bock

Thomas Moser

Markus Biehler

Kai-Michael Roesner

Peter Sieber

Guy Cases-Langhoff

Jochen Steinbach

Bernd Schmitt

Michael Meyringer

Markus A Peter

Martin J Wilmes

Andreas Poth

Berthold Wocher

Achim Clemens

Frank Schuhmacher

Ami Heitner

Marcus Philipp

Christian Haas

Hamid Moghaddam

Alexander Koegler

Reiner Bildmayer

Christoph Jungkind

Devasena Rajamohan

Shai Alfandary

Steffen Hartig

Matthias Schwarz

Olivier M Dreidemy

Sebastian Pulkowski

Volker Faisst

Jacques Duparc

Thorsten Kulick

Jan Penning

Joachim Barnbeck

Attila Orban

Jochen Wickel

Tim Gaiser

Helgi Thorleifsson

Peter Meuer

Uwe Mayer

Andre Doerfler

Edwin Himmelsbach

Andreas Sandner

Jens Ruths

Sabine Montnacher

Volker Paul

Bernhard Kohlhaas

Shanmuga Priya Vijayarajendran

Gertrud Beisel

Stefan Kaetkep

Ricardo Bustamante

Horst Vaeth

Silke A H Gruber

Marc Moesges

A business object model, which reflects data that is used during a given business transaction, is utilized to generate interfaces. This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction. In some operations, software creates, updates, or otherwise processes information related to a feed event, a feed event document, and/or a feed event type business object.

Consistent interface for feed event, feed event document and feed event type

A business object model, which reflects data that is used during a given business transaction, is utilized to generate interfaces. This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction. In some operations, software creates, updates, or otherwise processes information related to a user feed administrator, a user feed event link and/or a user feed settings business object.

Consistent interface for user feed administrator, user feed event link and user feed settings

A business object model, which reflects data that is used during a given business transaction, is utilized to generate interfaces. This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction. In some operations, software creates, updates, or otherwise processes information related to a feed collaboration group and/or a feed event subscription business object.

Consistent interface for feed collaboration group and feed event subscription

A business object model, which reflects data that is used during a given business transaction, is utilized to generate interfaces. This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction. In some operations, software creates, updates, or otherwise processes information related to a flag and/or a tag business object.

Consistent interface for flag and tag

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 apparatuses, including computer program products, for implementing a software architecture design for a software application implementing personnel events functionality. 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 personnel administration process component, a payroll processing process component, an expense and reimbursement management process component, a time and labor process component, a compensation management process component, an employee payroll administration process component, and numerous country-specific employer regulatory compliance process components.

Architectural design for personnel events application software

Methods and apparatus, including systems and computer program products, for a service architecture design that provides enterprise services having human capital management 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 human capital management software application as enterprise services

Methods and apparatus, including systems and computer program products, for a service architecture design that provides enterprise services having payroll 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 payroll software application as enterprise services

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 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

Growing community of inventors

Malsch, Germany

Peter Latocha