Sap Ag

Sap Se

Matthias Tebbe

Peter Latocha

Jens Freund

Gerd Moosmann

Otfried Von Geisau

Peter Fitz

Peter J Neumayer

Stefan Kaetker

Paola Sala

Karin Brecht-Tillinger

Arnulf Schueler

Arthur Berger

Armin Schwarz

Bettina Jaeger

Joachim Kenntner

Thomas Moser

Fabian Guenther

Markus Biehler

Kai-Michael Roesner

Dieter Krisch

Peter Sieber

Ralf Klein

Thomas Meigen

Matthias Richter

Frank Schuhmacher

Tatjana Pfeifer

Andreas Bold

Philipp Suenderhauf

Marcus Philipp

Olaf Tennie

Christoph Jungkind

Jacques Duparc

Helgi Thorleifsson

Balakrishna Gottipati

Volker Paul

Guy Cases-Langhoff

Jens Ruths

Ricardo Bustamante

Horst Vaeth

Silke A H Gruber

Marc Moesges

Gertrud Beisel

Teodor Joav Bally

Stefan Kaetkep

Embodiments described herein relate to an improved technique for preemptive client application request processing based on observed use access patterns and/or models. The system includes a framework engine operable to trace sequences of requests to one or more service provider applications, including which particular client requests are likely to be followed by other particular client requests for each service. Based on the resulting traces, the framework can determine the probability of a particular request B following another particular request A. When request A is retrieved from the service provider application, and when the probability is high enough (e.g. &#x3e;50%) that request B will follow request A in the sequence of requests, the framework is operable to simulate request B in a background process and provide a response to request B from a local memory storage.

System and method for preemptive request processing

The present disclosure describes methods, systems, and computer program products providing an integrated development environment for client/server environments. One computer-implemented method includes reading a derived business application data model (BADM) associated with a business application into an integrated development environment (IDE), defining a client application data model (CADM) for a client application, defining at least one data mapping rule (DMR) to map at least data translations between the BADM and the CADM, developing the client application based upon at least the CADM, developing at least one web service based upon the BADM, CADM, and the at least one DMR, generating the client application and the at least one web service, and deploying the client application, the at least one web service, and the at least one DMR.

Integrated development environment for heterogeneous client/server environments

An application programming interface (API) consumption development environment (CDE) is integrated with an API administration component and a determination is made whether an existing API conforms to application development requirements. A desired API is defined including test data, and the desired API and test data is forwarded to an API developer as a development request. The API CDE is integrated with the API administration component. A developed API is deployed to an API provider creating an integration testing deployment, and the API administration component is notified of the integration testing deployment. The developed API is deployed to an API provider productive for productive use.

End-to end, lifecycle aware, API management

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

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.

Growing community of inventors

Walldorf, Germany

Matthias Tebbe