A specialty chemical products company created an ASO reporting cube in ePBCS. This application housed detailed data that rolled up to a GL account. The problem was the source didn’t always tie to the GL due to restatements, GL entries, and manual corrections. Since they wanted the data to match to the book of record, but still have the level of reporting at the detailed level, they wanted to load data from both systems, calculate the variance, and store that variance so users would see the difference between the two sources. Read more
One thing that I have spent a lot of time on is making calculations independent of forms so that they can be used on any form. For example, rather than hard coding a script to look at a form with one column header and one row header, I am now building things to be dynamic so that the POV, the rows, and columns all are read dynamically and identifying the edited cells is independent of the source it is looking at. This will be a multi-post article because there is a lot to cover. Read more
Often times, there is a need to lock cells from a user outside of the traditional dimensional security methods. Maybe you don’t want to add dimensional security to accounts so your data push allows users to push data to another cube. Or, maybe there is more complicated logic to identify who can and who can’t edit a cell. The logic to do with is very simple. Read more
Data forms that have rules on them run when a user saves a form, regardless of whether the form has edited data. Sometimes this is by design, to let a user run a calculation. But, most of the time, it is an accident. There is no reason to use system resources and have the user wait for a calculation to finish when it doesn’t need to be executed. Read more