ERP Configuration Change: Approval, Test, Release and Rollback
Control parameters, workflows, access, interfaces and jobs through standard, normal and emergency change paths.
Learning objective
Make every production change traceable, verifiable and reversible.
Roles
Project leads, business owners, IT, security, key users, consultants and audit
Prerequisites
- Production changes retain approval and evidence.
- Failure rolls back within target.
- Business validation passes after release.
Completion checks
- Production changes retain approval and evidence.
- Failure rolls back within target.
- Business validation passes after release.
Common errors
- Testing directly in production.
- Rollback means only restore backup.
- No review after emergency.
Thailand project note
Thai projects require multilingual materials, THB/foreign currency, Asia/Bangkok time, segregation and retention; regulated tax, customs, BOI and statutory accounting need qualified Thai review.
Related modules
Steps
- 01
Record purpose, business impact, configuration objects, dependencies and risk.
- 02
Separate standard, normal and emergency changes; emergency never removes retrospective review.
- 03
Implement in isolation and retain before/after, test data, result and version.
- 04
Obtain business, technical and where needed security approval.
- 05
Schedule the window, notify users, back up configuration and define rollback trigger and owner.
- 06
After release validate technical state, critical transactions and reconciliation.
- 07
Maintain a calendar and collision check; analyse failed and emergency trends.
Implementation notes
- Production changes retain approval and evidence.
- Failure rolls back within target.
References
- YonSuite 客户成功服务 ↗用友 · Accessed: 2026-08-21 · Applicable version: 公开培训、巡检、实施与运行支持范围
- YonSuite Global Customer Success Services ↗用友 · Accessed: 2026-08-21 · Applicable version: 公开连续性、支持与客户成功服务范围