Hi IL,
Many companies import transactions for transaction matching so it is definitely not an uncommon thing to do.
Reasons not to do it for reporting that I can think of are:
- Is there a better method of reporting on the transactions that doesn't require importing them to OneStream
- you could instead display an external report using drill through functionality
- Is it possible/practical to report on the transactions on a OS page with them stored externally (usually amount of transactions and time to run report dictate this)
- Consider your storage limits (typically these are pretty large these days)
- Can you can get all the transactions into the environment at the required frequency
In regards to displaying table data to users, Version 9 will be your best friend here. You can now report on data in tables as if they were cubes using Dynamic Cube Services. There is some good content on v9 and DCS in Navigator. Also some links below.
Dynamic Cube Services - an Introduction | OneStream Community
https://documentation.onestream.com/1375907/Content/Design%20and%20Reference/Financial%20Model%20Guides/Dynamic-Cube-Services/Overview.html
You can set up drill through to data in a table prior to v9 and you can also show table data in the Excel add-in using Table Views.