Published at: 2026-09-17
Object change management overview
Configure object changes to create change records when users revise business documents. You can compare versions and trace approvals.
Business value
Contracts often change during procurement and sales fulfillment. Object change management provides these benefits:
- Standardized changes: Use change orders to update documents and prevent direct changes to source documents.
- Detailed audit trail: The system records changed fields and compares version differences.
- Stronger approval control: Changes update the source document only after approval.
Core concepts
| Concept | Definition | Related objects |
|---|---|---|
| Source object | The original business document with object changes enabled. | Contracts, Sales Orders |
| Change order | An automatically generated object that stores changes to a source object. | Contract Change Orders, Sales Order Change Orders |
| Change log | A technical log of versions, changes, and old and new field values. | Change order object, source object |
Use case
Your company signs a supplementary agreement during procurement contract fulfillment. The original contract must then be updated.
After object changes are enabled, users click Change instead of editing the contract directly. They update the amount or terms and submit the change order for approval. After approval, the system updates the original contract, creates a new version, and shows the differences in change history.
Features
Change order object
A change order records specific changes and provides version difference analysis. The current release supports only Contracts and Sales Orders.
Record and write back changes
You can add, edit, or delete object content in a change order. After approval, the system writes the changes back and increments the source record version.
Difference analysis
The change log records each version and its changes. Users can compare field values before and after a change.