US 2014/0006257 A1 · Consistent Interface for Payment Order, Payment Order Processing Statement and Product Valuation Data

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 a payment order, a payment order processing statement, and a product valuation data business object.

Claims15

Dependent claims

A computer readable medium including program code for providing a message-based interface for exchanging information about groups of payment orders, 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 to maintain the data of a captured business transaction concerning payment orders, the first message including a message package hierarchically organized as:
a payment order bundle maintain request sync message entity;
and
a payment order package including at least one payment order entity, wherein each payment order entity includes a company identifier (ID), a cash location ID, a receipt date, a receipt ID and an accounting transaction date;
and
program code for sending a second message to the heterogeneous application responsive to the first message.

3 more elements

A non-transitory computer readable medium including program code for providing a message-based interface for exchanging information about payment order processing, the medium comprising:

program code for receiving a first message via a message-based interface derived from a common business object model, where the common business object model includes business objects having relationships that enable derivation of message-based interfaces and message packages, the message-based interface exposing at least one service as defined in a service registry, the first message received from a heterogeneous application executing in an environment of computer systems providing message-based services, the first message for providing a notification to a payment processing entity of a processing status of payments initiated from a bank or a clearing house, the first message including a first message package derived from the common business object model, the first message package hierarchically organized in memory based on the common business object model, the first message package including:
a payment order processing statement notification message entity;
and
a payment order processing statement notification package, wherein the payment order processing statement notification package includes at least one payment order processing statement notification entity, wherein each payment order processing statement notification entity includes an incoming company payment file register file universally unique identifier (UUID), a type code, a format code, an item total number value, a date, and at least one payment order processing statement item entity, and wherein each payment order processing statement item entity includes a type code and a payment reference;
program code for processing the first message according to the hierarchical organization of the first message package, where processing the first message includes unpacking the first message package based on the first message package's structure and the first message package's derivation from the common business object model, wherein the particular structure of the first message package is used at least in part to identify the purpose of the first message;
and
program code for sending a second message to the heterogeneous application responsive to the first message, where the second message includes a second message package derived from the common business object model to provide consistent semantics with the first message package.

4 more elements

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

at least one processor operable to execute computer readable instructions embodied on non-transitory media;
a graphical user interface executable by the at least one processor and comprising computer readable instructions, embedded on non-transitory media, for providing a notification a payment processing entity of a processing status of payments initiated from a bank or a clearing house, the instructions using a request;
a first memory storing a user interface controller executable by the at least one processor for processing the request and involving a message including a first message package derived from a common business object model, where the common business object model includes business objects having relationships that enable derivation of message-based service interfaces and message packages, the first message package hierarchically organized based on the common business object model, the hierarchical organization of the first message package including:
a payment order processing statement notification message entity;
and
a payment order processing statement notification package, wherein the payment order processing statement notification package includes at least one payment order processing statement notification entity, wherein each payment order processing statement notification entity includes an incoming company payment file register file universally unique identifier (UUID), a type code, a format code, an item total number value, a date, and at least one payment order processing statement item entity, and wherein each payment order processing statement item entity includes a type code and a payment reference;
and
a second memory, remote from the graphical user interface, storing a plurality of service interfaces executable by the at least one processor and derived from the common business object model to provide consistent semantics with messages derived from the common business object model, wherein one of the service interfaces is operable to process the message via the service interface according to the hierarchical organization of the first message package, where processing the message includes unpacking the first message package based on the first message package's structure and the first message package's derivation from the common business object model, wherein the particular structure of the first message package is used at least in part to identify the purpose of the message.

5 more elements

Dependencies are inferred from the claim text.

Consistent Interface for Payment Order, Payment Order Processing Statement and Product Valuation Data

Life of this patent

Consistent Interface for Payment Order, Payment Order Processing Statement and Product Valuation Data

Life of this patent

Abstract

Claims15