Consistent Interface for Financial Accounting View of Cost Object Expense List and Financials View of Contract
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 financial accounting view of cost object expense list and a financials view of contract business object.
1 . A computer readable medium including program code for providing a message-based interface for exchanging information about financial accounting view of cost object expense lists, 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 notifying of an accounting view of a cost object expense list, including elements and characteristics of a cost object expense list that are relevant to revenue recognition in order to realize revenues for expense document items and in profitability reporting, the first message including a message package hierarchically organized as:
a financial accounting view of cost object expense list notification message entity; and
a financial accounting view of cost object expense list package including a financial accounting view of cost object expense list entity, wherein the financial accounting view of cost object expense list entity includes a universally unique identifier (UUID), a cost object reference, and a company UUID; 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 financial accounting view of cost object expense list entity further includes at least one expense document item.
3 . 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 notifying of an accounting view of a cost object expense list, including elements and characteristics of a cost object expense list that are relevant to revenue recognition in order to realize revenues for expense document items and in profitability reporting, 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 financial accounting view of cost object expense list notification message entity; and
a financial accounting view of cost object expense list package including a financial accounting view of cost object expense list entity, wherein the financial accounting view of cost object expense list entity includes a universally unique identifier (UUID), a cost object reference, and a company UUID; 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.
4 . The distributed system of claim 3 , wherein the first memory is remote from the graphical user interface.
5 . The distributed system of claim 3 , wherein the first memory is remote from the second memory.
6 . A computer readable medium including program code for providing a message-based interface for exchanging financials view of contract information, 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 notifying of a financials view of contract, including information required by processes in financials, the first message including a message package hierarchically organized as:
a financials view of contract notification message entity; and
a financials view of contract package including a financials view of contract entity, wherein the financials view of contract entity includes a universally unique identifier (UUID), a contract reference, a type code, a company UUID, a business partner UUID, a party role category code, and a key; and
program code for sending a second message to the heterogeneous application responsive to the first message.
7 . The computer readable medium of claim 6 , wherein the financials view of contract entity further includes at least one of the following: a subtype code, a company identifier (ID), a business partner internal ID, an account determination debtor group code, an account determination creditor group code, a description, system administrative data, a status, a last dunning UUID, a last dunning date, a last dunning level value, a dunning blocking note, a dunning blocking expiration date, a dunning blocking expiration date, a dunning blocking reason code, a dunning blocked indicator, and a payment agreement UUID.
8 . 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 notifying of a financials view of contract, including information required by processes in financials, 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 financials view of contract notification message entity; and
a financials view of contract package including a financials view of contract entity, wherein the financials view of contract entity includes a universally unique identifier (UUID), a contract reference, a type code, a company UUID, a business partner UUID, a party role category code, and a key; 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.
9 . The distributed system of claim 8 , wherein the first memory is remote from the graphical user interface.
10 . The distributed system of claim 8 , wherein the first memory is remote from the second memory.