Abstract: Systems and methods for using account symbols instead of general ledger accounts in the accounting documents generated by the business applications running in an enterprise environment are described. A correspondence between account symbols and general ledger accounts is defined and stored in a memory of a computer system. A business application generates accounting entries using account symbols instead of general ledger accounts. The generated account messages are received at an accounting application through an inbound interface. The account symbols in the accounting entries are replaced with the corresponding general ledger accounts. Financial documents are generated at the receiving accounting application based on the financial entries.

Abstract: Systems and methods for managing multiple systems in an enterprise resource planning system are provided. In an embodiment, data identifying modules and entities using modules or systems may be collected from each system in enterprise resource planning system. The collected data may then be organized to show a usage landscape of entire enterprise resource planning system. In an embodiment, the collected data may also be merged with other organizational data, such as organizational chart data, to present the usage landscape in an intuitive manner using the organizational structure data from the organizational chart. The collected data may also be used to identify potential data inconsistencies across different systems or may be used to limit connectivity to only authorized systems or modules. In some embodiments, attributes such as attributes identifying modules and entities may be inputted into a system which then distributes the attributes to other systems.

Abstract: In the described systems and methods for information lifecycle cross-system reconciliation, a number of reconciliation indicators for a certain type of data are defined. A first set of values of the reconciliation indicators are calculated at a first computer system based on data stored in a memory of the first computer system. A second set of values of the reconciliation indicators are calculated at a second computer system based on data transferred from the first computer system. The two sets of values are received at reconciliation cockpit and stored in a reconciliation data structure. Further, the reconciliation data structure is examined to identify inconsistency between the data stored in the memory of the first computer system and the data transferred to the second computer system. If such an inconsistency is identified, the data transfer is cancelled. If inconsistency is not identified, the data transfer is confirmed.

Abstract: The disclosed are a method and a system that may automatically monitoring message traffic between computer applications and using the monitoring data to reconcile databases associated with data related to the messages. The system may include a server, a cockpit monitoring module, a database, and a client terminal. The server may host a plurality of computer applications. The plurality of computer applications may operate on data records containing data. The data in the data records may be operated on by more than one of the plurality of computer applications. The computer applications may generate messages that may be related to the operations performed on the data in the data records. The messages may include information related to data records operated on by the plurality of computer applications. For example, the messages may contain information about the operations, the data, or other information related to the data and the application.

Abstract: The disclosed are a method and a system that may automatically monitoring message traffic between computer applications and using the monitoring data to reconcile databases associated with data related to the messages. The system may include a server, a cockpit monitoring module, a database, and a client terminal. The server may host a plurality of computer applications. The plurality of computer applications may operate on data records containing data. The data in the data records may be operated on by more than one of the plurality of computer applications. The computer applications may generate messages that may be related to the operations performed on the data in the data records. The messages may include information related to data records operated on by the plurality of computer applications. For example, the messages may contain information about the operations, the data, or other information related to the data and the application.

Abstract: Systems and methods for using account symbols instead of general ledger accounts in the accounting documents generated by the business applications running in an enterprise environment are described. A correspondence between account symbols and general ledger accounts is defined and stored in a memory of a computer system. A business application generates accounting entries using account symbols instead of general ledger accounts. The generated account messages are received at an accounting application through an inbound interface. The account symbols in the accounting entries are replaced with the corresponding general ledger accounts. Financial documents are generated at the receiving accounting application based on the financial entries.

Abstract: In the described systems and methods for information lifecycle cross-system reconciliation, a number of reconciliation indicators for a certain type of data are defined. A first set of values of the reconciliation indicators are calculated at a first computer system based on data stored in a memory of the first computer system. A second set of values of the reconciliation indicators are calculated at a second computer system based on data transferred from the first computer system. The two sets of values are received at reconciliation cockpit and stored in a reconciliation data structure. Further, the reconciliation data structure is examined to identify inconsistency between the data stored in the memory of the first computer system and the data transferred to the second computer system. If such an inconsistency is identified, the data transfer is cancelled. If inconsistency is not identified, the data transfer is confirmed.

Abstract: Systems and methods for managing multiple systems in an enterprise resource planning system are provided. In an embodiment, data identifying modules and entities using modules or systems may be collected from each system in enterprise resource planning system. The collected data may then be organized to show a usage landscape of entire enterprise resource planning system. In an embodiment, the collected data may also be merged with other organizational data, such as organizational chart data, to present the usage landscape in an intuitive manner using the organizational structure data from the organizational chart. The collected data may also be used to identify potential data inconsistencies across different systems or may be used to limit connectivity to only authorized systems or modules. In some embodiments, attributes such as attributes identifying modules and entities may be inputted into a system which then distributes the attributes to other systems.

Abstract: A system and method for distributing computing operations across multiple systems in an enterprise resource planning system is provided. In an embodiment, notifications are used to exchange information updates between the systems. In an embodiment, notifications containing financial data are sent to an accounting system. The accounting system may extract the financial data from the notification, use accounting logic in the accounting system to associate the financial data with a general ledger account maintained by the accounting system, and post an accounting entry in a financial document to properly credit and/or debit the account.

Abstract: A method, system and article of manufacture for creating a worklist and organizing a cockpit to control complex processes execution. A process hierarchy is created, including a plurality of organizational levels. A worklist of a plurality of worktasks, grouped in accordance with the process hierarchy, is created. The plurality of worktasks includes both internal worktasks, to be executed on a local computer system, and external worktasks, to be executed on external computer systems. A number of worklist views are displayed, where each worklist view includes a corresponding subset of the plurality of worktasks organized in accordance with the process hierarchy. Executions of internal and external worktasks are initiated from one or more of the worklist. Further, detailed information relevant to the execution is received. The executions of the tasks are monitored on one the worklist views.