Abstract: Techniques and solutions are provided for metadata-driven data maintenance. One or more data object queries are obtained from one or more data object frameworks. One or more sets of data objects are received based on the one or more data object queries. One or more data object nets are built based on the one or more sets of data objects and the one or more data object frameworks and respectively associated with one or more processes. The one or more data object nets and their associated processes are analyzed. Data object maintenance is performed on the data objects of the one or more data object nets based on the analysis of the one or more data object nets and their associated processes.

Abstract: Techniques and solutions are provided for metadata-driven data maintenance. One or more data object queries are obtained from one or more data object frameworks. One or more sets of data objects are received based on the one or more data object queries. One or more data object nets are built based on the one or more sets of data objects and the one or more data object frameworks and respectively associated with one or more processes. The one or more data object nets and their associated processes are analyzed. Data object maintenance is performed on the data objects of the one or more data object nets based on the analysis of the one or more data object nets and their associated processes.

Abstract: Systems, methods and articles for determining anomalous user activity are disclosed. Data representing a transaction activity corresponding to a plurality of user transactions can be received and user transactions can be grouped according to types of user transactions. The transaction activity can be determined to be anomalous in relation to the grouped user transactions based on a predetermined parameter.

Abstract: Embodiments of the present invention may provide a system for asynchronous data verification processing. The processing may include receiving input data for verification. The processing may parse the input data into synchronous and asynchronous data verification tasks. The synchronous data verification tasks may include linking the input data to information stored in the system. The synchronous data verification tasks may further include checking the input data for typographical errors. The asynchronous data verification tasks may include comparing the input data to the linked system data, determining one or more differences between the input data and the linked system data that may be present, and reporting the differences to a user of the system.

Abstract: Methods and apparatus, including systems and computer program products, for a services architecture design that provides enterprise services having supplier relationship 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.

Abstract: Methods and apparatus, including systems and computer program products, for a services architecture design that provides enterprise services having supplier relationship 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.

Abstract: Methods and apparatus, including systems and computer program products, for a services architecture design that provides enterprise services having supplier relationship 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.

Abstract: In some aspects, a system and method include receipt of a text file representation of an invoice associated with a supplier, receipt, from a database, of an invoice term associated with the supplier, determination, by a processor, of whether the invoice term is in the text file representation of the invoice. If is determined that the invoice term is in the text file representation of the invoice, an anchor term associated with the invoice term is determined. The invoice term and the anchor term are stored in a record associated with the supplier.

Abstract: Systems, methods and articles for determining anomalous user activity are disclosed. Data representing a transaction activity corresponding to a plurality of user transactions can be received and user transactions can be grouped according to types of user transactions. The transaction activity can be determined to be anomalous in relation to the grouped user transactions based on a predetermined parameter.

Abstract: Methods and apparatus, including systems and computer program products, for a services architecture design that provides enterprise services having supplier relationship 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.

Abstract: The disclosure provides a system, method, and software for facilitating invoice exception management. Particularly, this disclosure describes systems, method, and software for facilitating invoice exception management. The software comprises computer readable instructions. When executed, the software is operable to receive an invoice into a distributed business application. The software can identify an exception to the invoice. If an exception to the invoice is identified, the software automatically presents resolution options for the identified exception to a user via an invoice center interface.

Abstract: Methods and apparatus, including systems and computer program products, for a services architecture design that provides enterprise services having supplier relationship 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.

Abstract: A method includes selecting a set of transaction records from an accounting function, selecting a set of transaction records from a logical deployment unit, and checking the set of transaction records from the accounting function against the set of transaction records from a logical deployment unit, wherein the accounting function is separate from the logical deployment unit. A system includes a logical deployment unit, an accounting component separate from the logical deployment unit, a messaging system for sending messages from the logical deployment unit to the accounting component, and a checking mechanism.