Healthy transaction sizing on Accounting Hub implementations
Blog: Oracle BPM
Source system transactions come in different shapes and sizes on Accounting Hub implementations – from single line transactions to huge transactions having thousands of lines each. Transaction size is a common concern in pass-through implementations when source system data is in the form of pre-accounted debit and credit balances. Volume (rather than size) is typically a concern in event based implementations when source systems are passing raw transaction data.