Challenge Overview
The client for this project has an existing system called the Apex Journal Facility. This application provides users with the ability to submit requests for changes to the Essbase application (Hyperion Essbase 9.3). The application also provides an approval and tracking process for the submitted journal requests.
The existing Journal Facility application is Notes based. The goal for this project is to create a new, web-based application to replace the existing, Notes-based Apex Journal Facility application.
The new Journal Facility application will allow users to create and submit journals. A journal is a request from a financial planner to adjust an existing data entry or to create a new entry into the financial planning system to be reflected in the business unit's budget / plan for the coming year.
The application will support the ability to create one of three journal types: a 1 to 1 Journal, a 1 to X Journal, or an Exception Journal. Users will validate their journal entries against the valid member lists. If errors are found, they will need to correct them before either saving the journal as a draft or submitting it for approval.
The new system will also support the ability to import journal data from the Masterlist Interlock DB.
This module will implement the back end services, entities and exceptions. The services will use JPA to manage database data.
This module will also support the ability to import journal data from the Masterlist Interlock DB.
This component provides the services in “Services Part 1 Class Diagram” and their implementations.
Final Submission Guidelines
N/A