Excel reporting package for the Financial Consolidation model
Provide an Excel template for collection of separate financial statements for one entity and in one reporting period. Add a self-service interface for end users to upload separate financial statements using this template.
Storage, input screens and import interface for data by operating segments, geographical areas and other custom dimensions in the Finanical Consolidation model
The database should be extended by a storage of data in local charts of accounts by operating segments, geographical areas and other custom dimensions. Data should be captured from input screens.
Storage, input screens and import interface for trial balances in the Financial Consolidation model
The database should be extended by a storage of trial balances in local charts of accounts. Data should be either imported from a file in a standard format or/or captured from input screens. The input screens should cover values for ledger account...
Designed web reports for master data maintenance to the Finanical Consolidation model
Provide designed web reports to add, inspect, modify and remove master data items such as legal entities, scopes, accounts, transaction types, currencies, etc.
Only stop the services when no Integrator job is running
We have implemented on our own systems that the restart of the services, which is carried out during the backup, only takes place when an ETL job is no longer running. This is also necessary for the cloud.
When configuring a SAML single-sign-on connection in Excel, the login information is cached. In order to logout of the SAML connection there is no other possibility than check the option "Delete cache when closing Excel" in "Options>Modeler opt...
In Jedox Web, it can become very difficult to keep track of all the cubes recently created in a database and those you may need to be referenced in rules. In the past, I have created separate databases to address this, however, the references in r...
There's often a significant number of databases present in a Jedox environment, with possible several people working on them and several usecases. To allow keeping track of what specific databases are used for, who works on them etc., it would be ...
Basically expose in the macro engine all what is possible to do in a spreadsheet: - create / rename / delete / hide / show sheet - insert / delete columns/rows - you name it