Consistent Interface for Project and Sales Order

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 a request to derive an intercompany settlement project task, 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 intercompany settlement project task request message entity;
• and
• a project task package including at least one project task entity, wherein each project task entity includes an object node sender technical identifier (ID);
• 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.

A computer readable medium including program code for providing a message-based interface for exchanging information about projects, 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 a notification about a customer project and assignments of project tasks to customer transaction document items, the first message including a message package hierarchically organized as:
• a project and customer transaction document assignment notification message entity;
• and
• a project package including a project entity, wherein the project entity includes a universally unique identifier, a project identifier (ID), a language code, a responsible company ID, a responsible cost centre ID, an intercompany settlement indicator, a main business process variant type code, a project life cycle status code, and a task blocking status code;
• and
• program code for sending a second message to the heterogeneous application responsive to the first message.

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 a notification about a customer project and assignments of project tasks to customer transaction document items, 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:
• a project and customer transaction document assignment notification message entity;
• and
• a project package including a project entity, wherein the project entity includes a universally unique identifier, a project identifier (ID), a language code, a responsible company ID, a responsible cost centre ID, an intercompany settlement indicator, a main business process variant type code, a project life cycle status code, and a task blocking status code;
• 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.

A computer readable medium including program code for providing a message-based interface for exchanging information about projects, 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 a request to create a customer project based on a sales order, the first message including a message package hierarchically organized as:
• a sales order project create request sync message entity;
• and
• a sales order package including a sales order entity, wherein the sales order entity includes a universally unique identifier (UUID) and an identifier (ID), wherein the sales order entity further includes a buyer party entity, a create project action elements entity and at least one item entity from the sales order package, wherein the buyer party entity includes a party UUID, a party type code and a party internal ID, wherein the create project action elements entity includes a project responsible employee ID, a project responsible cost centre ID and a project creation method code, and wherein each item entity includes a UUID, an ID and a customer project invoicing method code;
• and
• program code for sending a second message to the heterogeneous application responsive to the first message.

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 a request to create a customer project based on a sales order, 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:
• a sales order project create request sync message entity;
• and
• a sales order package including a sales order entity, wherein the sales order entity includes a universally unique identifier (UUID) and an identifier (ID), wherein the sales order entity further includes a buyer party entity, a create project action elements entity and at least one item entity from the sales order package, wherein the buyer party entity includes a party UUID, a party type code and a party internal ID, wherein the create project action elements entity includes a project responsible employee ID, a project responsible cost centre ID and a project creation method code, and wherein each item entity includes a UUID, an ID and a customer project invoicing method code;
• 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.