A major milestone in every Hyperion Planning project is the day that you get your first web form to accept input. Listed below, are some of the many different settings that will prevent a web form from accepting data input (we'll assume a bottoms up planning unit type here):
- Security: has the id being used been provisioned for write access to the Hyperion Planning application
- Account attempting to write to: is the account level 0, a stored account (not dynamic calc)
- stored members of all dimensions: are you attempting to write to a dynamic member (scenario, product, entity, etc.)
- Point of view criteria: are all the dimensions referenced in the web form level 0, check the page header and all the drop downs
- planning unit started: has the planning unit (year, scenario, version) been opened for input
- year: is the year part of a planning unit that has been started?
- security on entities: does the entity on the form allow for write access? (make sure the inherited security is correct, if you have read @idescendants of entity, then you will not be able to write)
- security on accounts: do the accounts on the form allow for write access?
- security on any other dimensions: are any other dimensions with security enabled set for write access?
- user id: does this id have write access to the dimensions that have security enabled?
- web form: is the read only check box checked to force the web form to be read only?
- refresh with security filters: have you recently refreshed the Hyperion Planning application with security filters checked ?
At the start of every Hyperion Planning project, is the first time you get a web form to accept data entry into a cell. What modifications need to happen in order for a web form to accept data entry?
