Forum Discussion
MCFNeil
8 years agoQrew Captain
The short answer: QB and SAP both have very robust API functionality, so basically anything you want to send back and forth is possible. Especially because you have a common denominator (job ID).
You are going to want to involve an engineer to see the complexity of the the data model, business model, and your goals to give you an accurate level of effort.
Usually you have to decide where the 'true' source of information resides, i.e. SAP or QB. Because you want to make sure the data doesn't override the real stuff with outdated information.
The long game; Most companies I know of once they get the QB app built out the right way they can get rid of SAP altogether. So it depends on what your goals are in the long run, and just plan for that.
You are going to want to involve an engineer to see the complexity of the the data model, business model, and your goals to give you an accurate level of effort.
Usually you have to decide where the 'true' source of information resides, i.e. SAP or QB. Because you want to make sure the data doesn't override the real stuff with outdated information.
The long game; Most companies I know of once they get the QB app built out the right way they can get rid of SAP altogether. So it depends on what your goals are in the long run, and just plan for that.