Sap Ag

Sap Se

Paola Sala

Karin Brecht-Tillinger

Peter Fitz

Arnulf Schueler

Andre Wagner

Ralf Sievers

Johann Kemmer

Georg Podhajsky

Markus Biehler

Andreas Brossler

Jens Freund

Stephan Hetzer

Joachim Kenntner

Thomas Nitschke

Tao Yu

Antonia Gross

Peter J Neumayer

Arthur Berger

Armin Schwarz

Gerd Ritter

Daniel Buchmann

Gunther Stuhec

Renzo Colle

Peter Latocha

Michael Seubert

Gerd Moosmann

Otfried Von Geisau

Dietmar Nowotny

Werner Gnan

Daniel Bock

Thilo Kraehmer

Markus A Peter

Matthias Tebbe

Gregor Rieken

Toralf Grossmann

Andreas Bold

Stefan Adelmann

Matthias Schmitt

Wolfgang Nieswand

Rudolf Winkel

Christoph Lehner

Otto Makris

Stefan Elfner

Andreas F Morsch

Thomas Maag

Michael Zoeller

Robert Reiner

Jochen A Rasch

Axel Kuehl

Volker Jaeck

Benjamin Klehr

Daniela Schapler

Ruediger Radcke

Uwe Pyka

Frank Thome

Dagmar Schultze

Andreas Schneider

Pascal Hochwarth

Karsten Koetter

Corinne Kuster

Theo Zimmerman

Gabriel Alvarez

Stefan Kaetker

Robert Doerner

Zeno Rummler

Christoph Jungkind

Stefan Franke

Giovanni Deledda

Adam Kiwon

Volker Ripp

Renato Zadro

Tobias Hoppe-Boeken

Hua Wang

Joachim Gaffga

Matthias Richter

Jochen Steinbach

Gunther Liebich

Jochen Hirth

Gregor Tielsch

Andreas Poth

Ingo Pfitzner

Thomas Moser

Mario Andy Mueller

Andrea Sudbrack

Fabian Guenther

Volkmar Stegmann

Achim Heger

Martin Von Der Emde

Johannes Bechtold

Thomas Bach

Rainer Heun

Michael Picht

Andre Wachholz-Prill

Reiner Bildmayer

Stefan Kiefer

Thomas Weiler

Paul P Tanzer

Erwin Pinter

Holger Herrmann

Shane Bracher

Systems, methods and articles for determining anomalous user activity are disclosed. Data representing a transaction activity corresponding to a plurality of user transactions can be received and user transactions can be grouped according to types of user transactions. The transaction activity can be determined to be anomalous in relation to the grouped user transactions based on a predetermined parameter.

Detecting anomalous user activity

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 message-based communication arrangement, an organizational center replication request, and a payment schedule business object.

Consistent interface for message-based communication arrangement, organisational centre replication request, and payment schedule

Methods and systems consistent with the present invention provide a data processing system having a business object model reflecting the data used during a business transaction. Consistent interfaces are generated from the business object model. These interfaces are suitable for use across industries, across businesses, and across different departments within a business during a business transaction.

Consistent set of interfaces derived from a business object model

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 and apparatus, including systems and computer program products, for a services architecture design that provides enterprise services having supplier relationship 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 supplier relationship management 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 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, 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 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, a Project Processing process component, a Source of Supply Determination process component, a Due Item Processing process component, a Balance Of Foreign Payment Management process component, a Pricing Engine process component, and an Accounting Coding Block Distribution Processing process component.

A technique for exchanging messages in a computer network using a public data template and a message transfer protocol with interdependent request and confirmation messages is described. A request message includes a first data structure obtained by packing application data that requires confirmation in the public data template. A network component receiving the request message unpacks the application data and provides the unpacked application data to a confirmation process. At the same time, the unpacked application data provided to the confirmation process is repacked in the public data template to generate a second data structure. The second data structure is sent with a confirmation message via the computer network to the sender of the request message. By comparing the content of the first data structure with the content of the second data structure, inconsistencies degrading the accuracy and trustworthiness of the confirmation process may be detected.

Technique for reliable message confirmation

A system and method for the resource-saving collaborative handling of data sets in a computer network is described. The method comprises the steps of providing a data set having an initial collaborative workflow, determining if the data set satisfies a set of one or more first start conditions to trigger a random function query, providing the data set to a random function if the random function query is triggered, stochastically determining, by the random function, whether or not to assign a modified collaborative workflow to the data set, and replacing the initial workflow with the modified workflow for the data set if the random function determines to assign the modified workflow.

Processing of data sets in a computer network

A networked database includes the automatic creation of follow-on data sets from initial data sets. A dialogue routine is implemented for initiating a dialogue-type communication that includes inputting and confirming data required for creating the follow-on data sets. The database is provided with a plurality of data sets and is capable of generating and displaying a list of data sets according to user-defined criteria. For a data set in the generated list that allows for the automatic creation of a follow-on data set, a related, configurable, user-activated control element is displayed. Upon user-activation, the control element, generates a control signal for initiating the automatic creation of the follow-on data set based on data derived from the selected data set and/or any data set associated with the selected data set. The newly created follow-on data set is then associated with the selected data set.

Distributed handling of associated data sets in a computer network

Growing community of inventors

Heidelberg, Germany

Paola Sala