Editorial draft available to read. Factual and language review is pending. Examples are illustrative.
Decision and scope
Start with business objects and decisions rather than a connector name. List orders, items, stock balances and statuses. For each exchanged field define its owning system, stable identifier, unit, refresh interval and write permissions. Document how delayed updates, unknown references and rejected changes are handled.
Illustrative example
Illustrative example: the ERP owns the official production order while a portal presents progress. The portal submits proposed updates with unique request identifiers. The ERP accepts or rejects each proposal and returns an attributable result. Retrying the same request must not create a second inventory movement or a duplicate completion record.
Acceptance check
Test creation, changes and cancellations in a separate environment. Reconcile counts and quantities after an interruption. Accept the integration when every field has an owner and operational errors can be resolved without invisible manual edits.
Key takeaways
- Accept the integration when every field has an owner and operational errors can be resolved without invisible manual edits.