Oracle International Corporation

Fang Liu

Shailesh Kumar

David Battaglia

John Clark, Jr

Bhagat V Nainani

Khanderao Kand

Rajesh Bhatia

Bhanu Prakash Ayyadevara

John Meyerle

A computer-readable medium, computer-implemented method, and financial close management system are provided that manage a schedule. A schedule is a core object of the financial close management system, and is an expression of a template. Managing a schedule can include creating a new schedule, modifying an existing schedule, deleting an existing schedule, duplicating an existing schedule, validating an existing schedule, creating a template from an existing schedule, setting a status of an existing schedule, and importing and exporting an existing schedule. In addition, managing a schedule can include defining task type parameters that can be set during scheduling and setting task parameters of a schedule at a schedule level rather than a task level.

Managing schedules in a financial close management system

A computer-readable medium, computer-implemented method, and financial close management system are provided that includes a integration framework that allows an end user to leverage services or interfaces from external applications as part of a business process, such as a financial close process, of a financial close management system. The integration framework can integrate a task that requires the user to interact with a user interface of an external application (identified as an 'end user task') with the financial close management system. The integration framework can also integrate a task that runs without any user interaction required, and that interacts with a web service of an external application (identified as a 'system automated task') with the financial close management system.

Integration of applications with a financial close management system

An extensible process design provides an ability to dynamically inject changes into a running process instance, such as a BPEL instance. Using a combination of BPEL, rules and events, processes can be designed to allow flexibility in terms of adding new activities, removing or skipping activities and adding dependent activities. These changes do not require redeployment of the orchestration process and can affect the behavior of in-flight process instances. The extensible process design includes a main orchestration process, a set of task execution processes and a set of generic trigger processes. The design also includes a set of rules evaluated during execution of the tasks of the orchestration process. The design can further include three types of events: an initiate process event, a pre-task execution event and a post-task execution event. These events and rules can be used to alter the behavior of the main orchestration process at runtime.

Event driven change injection and dynamic extensions to a business process execution language process

Growing community of inventors

Dracut, MA, United States of America

Fang Liu