First, give conclusions that can be used for decision-making
The integration should be preceded by a system and a catalogue of data that identifies who creates the customer, goods, orders, inventory, organizational and financial documents, who has the right to modify them and to synchronize them.
What conditions need to be identified before judgement is made?
The same question may have different answers under different business, data and project phases. It is suggested that the following conditions be checked and that the common findings on the web be incorporated into their own projects.
Suggested order of advance
First, we'll be clear about the target and the border.
System, interface and master data catalogues are produced to confirm the data ownership.
Validation Key Dependence
A high value chain road design field, event and anomaly rule are selected first.
Development of assessable outcomes
The history is used to combine the border samples, so on, retest and compensate.
Make sure you decide the next step with the real results.
Checking reconciliation differences on the online line and gradually expanding other systems.
How do you understand it in the actual business?
Once CRM has been closed, a customer and order is created to the ERP, and the ERP bank is retransmitted to the CRM. If both parties change the client code, duplicate records will occur; the process will be stable in the long term when the ERP is identified as official customer-master data, a CRM preservation map, and the business only key is used to prevent duplicate creation.
The easiest pit to step on.
Each system is directly interconnected and later forms an unmaintainable network interface
Only test normal requests, not process duplicate calls and network timeout
Field names are the same, business is the same.
How should we end up receiving and confirming?
The receipt and inspection shall cover normal, duplicate, missing, disorderly, overtime and authority anomalies, and shall reconcile logs, alarms, retests, compensation and reconciliations. The interface contract, field mapping, call limits, account numbers and the troublebook shall also be delivered.
When preparing to communicate with suppliers or internal teams, it is recommended that current processes, representative samples, existing systems, planning time and budget levels be brought. First, the unknown items are clearly marked, and then the decision is made to use diagnostics, PoC, fixed-range projects or ongoing research and development, which is usually more reliable than a direct demand for a price and duration without borders.