Connect ERP data with your eCoC workflow

Start with one vehicle family. Identify the source of the VIN, production status, type approval, variant, version and technical values. A value imported from ERP still needs an agreed owner and a rule for resolving conflicting information.

• Map source fields to the required vehicle record.
• Identify approval data maintained outside ERP.
• Agree how missing or changed values reach the responsible team.

Illustrative data, not a customer record: an ERP CSV export contains production record DEMO-001, its VIN, build status and variant, but no approval extension. The proposed mapping returns a missing approval-reference finding to the homologation data owner. The owner checks the approved source and supplies a corrected record; that version is reviewed again before XML preparation. This is a scoping example, not a documented API response or an available connector.

• Source: an anonymised ERP production export, with approval data supplied by homologation.
• Feedback: record DEMO-001, missing approval extension, responsible team: homologation.
• Next action: correct the source, repeat the agreed checks and retain the reviewed version.

Use a representative vehicle, an incomplete input, an interrupted exchange and a correction to assess the proposed workflow. Record the expected outcome and owner for each case. Extend to further vehicle families or automation only after the initial scope is verified.

• State the vehicle family, expected volume and source systems.
• Include repeat transfers and correction scenarios.
• Agree acceptance criteria and responsibility for later changes.