You can make transactions appear version-specific using a saved transactions report and the “Drill into Transactions” option on the Versions Modeling page.
First, we need to understand how transactions work: transactions are imported into the system separately from an Actuals import. Typically, users import transactions alongside Actuals and view the transactions in the actuals version. However, transactions are not tied to any versions. They are tied to the intersection of a particular time period, account, and level.
When a user drills into transactions, it generates a predefined transaction report. By default, the transaction report uses the “Default” view for transactions, set on a version-by-version basis. You can see this by going to navigation menu>>Modeling>>Model Management>>Versions>>select a version>> “Drill into transactions”. Typically, this is set to the “Default” view, but you can change the setting to a custom transactions report.
To setup the custom transactions report, you would create a dimension or Text field to add to your transactions definition from Modeling>>Modeled Management>>Transactions. The dimension, created from Modeling>>Model Management>>Dimensions, or Text field, created from the aforementioned Transactions page, would represent the version(s) to use as a filter in a custom transactions report. You may have values such as “Actuals”, “Budget” and “Forecast”. After the dimension or Text field is created, add it to the Transactions page and save.
To set up a custom transaction report, you can go to the navigation menu>>Reports>>Create new report>>Transaction. Here, you can set up a custom transaction report with a any number of fields/columns as well as filters. You can create as many transaction reports as you need for however many versions you need to have transactions customized. Once the columns have been defined/set for the report you would like displayed in specific versions, you would go to the “Filters” button and add a filter for the previously created Versions dimension or text field. If this was created for your “Budget” version(s), you’d add a filter for “Budget”.
Save the custom transactions report and go to Modeling>>Model Management>>Versions, select a version in particular, and update the “Drill into transactions” field to the report you just created.
The next time you import transactions, you will want to include the new Versions column/field and define your transaction rows as needed by version. With the custom transaction report, you will only see the transactions you would like in the version based on the filter.