CONSISTENT INTERFACE FOR OPPORTUNITY

• US 20140006546A1
• Filed: 06/28/2012
• Published: 01/02/2014
• Est. Priority Date: 06/28/2012
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Pfitzner, Ingo, Bender, Thorsten, Zimmermann, Sascha, Wocher, Berthold, Naundorf, Stephan, Wolf, Markus, Yang, Guang, Kreindlina, Olga, Buecheler, Torsten, Mazur, Stefan, Scheuch, Carsten
• Granted Patent: US 9,246,869 B2
• Time in Patent Office: Days
• US Class Current: 709/217
• CPC Class Codes: G06Q 10/067 Enterprise or organisation modelling
• CPC Class Codes: G06Q 30/00 Commerce
• CPC Class Codes: H04L 51/063 Content adaptation, e.g. replacement of unsuitable content
• CPC Class Codes: H04L 51/56 Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]

Abstract

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 an opportunity business object.

Claims

1. A computer readable medium including program code for providing a message-based interface for exchanging opportunity data, the medium comprising:

program code for receiving via a message-based interface exposing at least one service as defined in a service registry and from a heterogeneous application executing in an environment of computer systems providing message-based services, a first message for requesting replication of opportunity data, including business transaction information and identification of parties involved in a prospective business transaction, the first message including a message package hierarchically organized as;

an opportunity replication request message entity; and

an opportunity package including an opportunity entity, wherein the opportunity entity includes an identifier, a processing type code and a process status valid since date; and

wherein the opportunity entity includes a status entity from a status package; and

program code for sending a second message to the heterogeneous application responsive to the first message.

2. The computer readable medium of claim 1, wherein the opportunity entity further includes at least one of the following:

a prospect party entity from a prospect party package, at least one competitor party entity from a competitor party package, at least one sales employee party entity from a sales employee party package, an employee responsible entity from an employee responsible party, a sales unit party entity from a sales unit party package, at least one party entity from a party package, a sales cycle entity from a sales cycle package, a sales forecast entity from a sales forecast package, a sales and service business area entity from a sales and service business area package, at least one business transaction document reference entity from a business transaction document reference package, an attachment folder entity from an attachment folder package, a text collection entity from a text collection package, and at least one item entity from an item package.

3. The computer readable medium of claim 1, wherein the opportunity entity further includes at least one of the following:

system administrative data, a name, a priority code, a group code, an origin type code, a result reason code, and a change ordinal number value.

4. A distributed system operating in a landscape of computer systems providing message-based services defined in a service registry, the system comprising:

a graphical user interface comprising computer readable instructions, embedded on tangible media, for requesting replication of opportunity data, including business transaction information and identification of parties involved in a prospective business transaction, the instructions using a request;

a first memory storing a user interface controller for processing the request and involving a message including a message package hierarchically organized as;

an opportunity replication request message entity; and

an opportunity package including an opportunity entity, wherein the opportunity entity includes an identifier, a processing type code and a process status valid since date; and

wherein the opportunity entity includes a status entity from a status package; and

a second memory, remote from the graphical user interface, storing a plurality of service interfaces, wherein one of the service interfaces is operable to process the message via the service interface.

5. The distributed system of claim 4, wherein the first memory is remote from the graphical user interface.

6. The distributed system of claim 4, wherein the first memory is remote from the second memory.