2022
The proposed data flow is demonstrated in the latter section including the Business-Case, Data-Flow, Architecture in detail .
The first section of the solution explained the very first Business Case .
{*}Customer Integration:*The customer integration dataflow constitutes of retrieving data on nightly basis from QuickBooks and integrating it with FTP and file using Inventiv specs on .FIL as file extension. The integration data-flow will always extract all Customers and move to Inventiv FTP system. The scheduler job consists of the following
? QuickBooks Customer with its respective attributes are retrieved and converted to a tabbed de-limited files with .FIL as its extension
? The files generated will be moved/over-written to a specific folder under inventive FTP system with the folder bearing the naming convention, “latest<cust_id>” as customer.fil
*Item Integration: *The Item integration dataflow constitutes of retrieving data on nightly basis from QuickBooks and integrating it with FTP and file using Inventiv specs on .FIL as file extension. The integration data-flow will always extract all items and move to Inventiv FTP system. The scheduler job consists of the following
? QuickBooks Item with its respective attributes are retrieved and converted to a tabbed de-limited files with .FIL as its extension
? The files converted is integrated to a specific folder under inventive FTP system with the folder bearing the naming convention, “latest<cust_id>” as item.fil
Invoice Integration:
The Invoice Object dataflow will be unidirectional with transfer of data from QuickBooks into inventive FTP to a specified file path with the Invoice transaction file bearing a .FIL as its extension. Integration is invoked overnight at specified interval of time by the scheduler mechanism built inside DBSync platform. The data-flow will be uni-directional and incremental in nature with transfer of data into Inventiv FTP.
Proposed Data-Flow Between QB To Inventiv FTP |
|