Master data changes with accountable approval
AMODIT manages requests to create or update customer, supplier, dual-role business partner and item master records. It routes each section to the responsible people, checks completeness and approval, and can pass approved records to a target system.
Connect the data, owners and approval path
Several teams may contribute
Creating or changing a master record can require input from different teams. A section may need correction before the request is complete, approved and ready to move into the target system.
One controlled AMODIT request
The workflow assigns sections by responsibility, supports parallel input and follows the appropriate route. Case, task, error and audit views show progress from the initial request to an approved master record.
From request to an approved master record
This is an implementation pattern: master-data creation and update workflows connect AMODIT with the customer’s systems. The customer selects record types, data scope, roles, and approval rules.
1. Create or change request
The case identifies whether the request concerns a customer, supplier, an entity acting in both roles or an item master record, and whether a new record or an update is required.
2. Capture the required data
The form collects the information needed for the selected record type. Registry data can be retrieved when it forms part of the agreed workflow.
3. Route sections to their owners
The route and responsibility template determine who completes and reviews each part of the request.
4. Work in parallel and return corrections
Selected sections can be completed in parallel. An incomplete section can return to the right owner while the overall case remains visible.
5. Check completeness and approve
The workflow checks the required information before the request completes and follows the defined approval step.
6. Send and track synchronization
An approved record can be sent to the target system through an API. The workflow can record synchronization status, support a correction and retry the transfer.
One source, consistent data across workflows
How shared reference data is used depends on the agreed system of record, the data owner and the integration scope.
Agreed system of record
People, business partner, organizational unit and category data can come from an agreed system of record. Keeping that source current helps reduce inconsistent entries across workflows.
Accountable data owner
For each data domain, the workflow identifies who maintains it and where a change intended for other workflows is entered.
Context-specific choices
Selection lists can be limited to values relevant to the case, so users work with the appropriate data for that workflow.
Controlled distribution
Once approved, current values can be passed to specified workflows or systems according to the agreed direction and integration scope.
Tell us which master records are in scope, who contributes the data and how changes are approved. We can map the form, routes, completeness checks and any transfer of approved data to the target system.
Describe the master records, participating roles and approval path in scope. We will discuss how AMODIT can structure the workflow.
Master data management workflow FAQ
1Which master records can the workflow cover?
The implementation pattern covers customer, supplier, dual-role business-partner, and item master records. The customer selects the final catalog and how it integrates with source systems.
2Can one workflow handle both record creation and updates?
Yes. A central request can distinguish a new master record from a change to existing data and then follow the appropriate route.
3Can several teams complete sections in parallel?
Yes. Sections can be divided by responsibility and completed in parallel, with a selected section returned for correction when needed.
4How does the workflow control completeness?
Required sections and fields are checked before approval. Task and error views identify the items that still need input or correction.
5Can approved records be sent to another system?
Yes. The integration sends approved records through an API, records synchronization status, and retries the exchange after a correction. The customer defines the target system and data scope.
6What can serve as the master data source?
The source is defined as part of the workflow and integration design. It can be an agreed register, while AMODIT uses the relevant data in the process and manages the change request. The design also assigns data ownership and the update location.
7How are updates shared with other workflows?
The design first defines the update location and data owner. Approved values can then be passed to specified workflows or systems when this is covered by the agreed integration. The method and status depend on the available interfaces.