Server

 

Data Entry

 

Data entry is accomplished from directly within Microsoft Excel.

 

myObjectiveOLAP can be set to allow data-entry immediately if a user has been given access to the data either explicitly or via role-profile.   Alternatively data-entry can be set to go to a hierarchical approval queue to be explicitly authorised by a users manager.

 

Once a change is submitted myObjectiveOLAP records:

 

 what changed?

           who changed it?

                   when was it changed?

                       what was it before the change?

 

myObjectiveOLAP can be asked to reverse out a data submission, or set the system to a specific date & time.

 

Once data is submitted, myObjectiveOLAP will process the data via MPM and then process any Processes or Workflows associated with the data being changed.   Processes are scoped by default ensuring only the minimum amount of work is required to show the impact of the change.

 

myObjectiveOLAP also allows structures such as:

 

• Dimension Values
• Hierarchies
• Models
• Attributes

 

To be maintained and created via similar data-entry forms  from directly within Microsoft Excel greatly easing the time and cost surrounding making changes to your application.

 

User Management

 

User management is simplified within myObjectiveOLAP.   Users can be created quickly and easily and assigned roles and responsibilities.

 

User access can easily be scoped ensuring that only data meant to be viewed is available to a given role, responsibility or user.

 

Data can be scoped on the Cube, Dimension or Dimension Value enabling fine-grained security.   Data security can be further enhanced by allowing users Read, or Read Write access based on a similar fine-grained security model.

 

Security within the OLAP model is enabled by utilising standard Oracle technologies such as PERMIT.

 

The security model does not just apply to data stored within the Analytic Workspace based application component, but also persists within the relational data store which is often used to store transactional information.

 

In order to protect data stored as part of the application within the relation data-store myObjectiveOLAP leverages the power of  Oracle Virtual Private Database (VPD), this enables us to control access beyond the table or view down to the Row and Column.  This enables us to mirror the access irrespective of where the data is stored.

 

 

 

Legacy Compatibility

 

myObjectiveOLAP has its roots in helping customers running legacy applications such as Oracle Financial Analyzer (OFA), Oracle Sales Analyzer (OSA) and custom Oracle Express Server applications upgrade and maximise their return on investment.  To this end myObjectiveOLAP is compatible with the heritage customisation and extension supported in these older applications.

 

Custom Code

 

With myObjectiveOLAP your considerable investment in the local-code (ofalc etc..) databases can be transitioned with very, very few changes.   In fact with the exception of some light-touch changes around the way the filesystem is handled almost no changes are required.   Where changes are required, for example with the remove of the Express command to list files in a directory, a new myObjectiveOLAP function is provided to offer the same functionality.

 

Customers who made use of the OFA API which is not available within Oracle+OLAP can quickly adapt their code to make use of a similar myObjectiveOLAP API.

 

We know many customers extended both OFA via the hooks menu; and via custom programs typically constructed as Excel Addins.  myObjectiveOLAP supports a fully featured API which will enable you to quickly meet the same result.

 

Data & Structures

 

Data from legacy applications can easily be migrated to myObjectiveOLAP.  Just export your data from your old applications datafiles via eif (Express Interchange File) and import into myObjectiveOLAP.

 

Upgrade scripts will query the meta-data in the heritage catalogs such as FD, MD, HI, etc. and will automatically convert them to the myObjectiveOLAP standard form.

 

Reasons to Upgrade to myObjectiveOLAP

  & Oracle OLAP

 

myObjectiveOLAP is a strong upgrade route for any customers using Oracle Express Server based applications.

The following is designed to give you a quick guide to the key reasons to choose myObjectiveOLAP on Oracle.

 

Oracle+OLAP

 

• Oracle+OLAP is Express, but with 10 years of enhancements.
• Oracle+OLAP works with modern Operating Systems enabling you to retire legacy ageing hardware, expensive support contracts & eradicate your replacement parts risk.
• Oracle+OLAP is Oracle, with Express Server you had to build custom solutions for recovery & backup (RMAN); failover (RAC & Gird) and security.  All of this is now part of the database.
• Memory management is much improved, and greater amounts of memory can be assigned for aggregation.
• OLAP now benefits from the robust nature of the Oracle database.  No more daily bouncing of Express to clear memory leaks.
• Data is available to standard SQL clients such as OBIEE, Applications Express.

 

myObjectiveOLAP

 

• Migration from your Express Server to myObjectiveOLAP Server is designed to be easy and quick
• Administration, your Administrators will be able to support myObjectiveOLAP with minimum retraining.  Reducing cost of upgrading and impact on your business.
• Windows and Office myObjectiveOLAP is supported from Windows XP to Windows 8; and Office 2003 to Office 2013.
• myObjectiveOLAP is built on standards.  We've utilised products within the Oracle database such as VPD, DBMS Scheduler, File Watchers and OLAP_TABLE to bring to you a high performance, strong and robust application.

 

We're so confident you'll like what you see, just ask us to do a quick proof-of-concept migration.