Typical transformation rule scenarios

Core requirements

• Configure multiple rules for one transformation route.
• Copy and adapt existing rules.
• Trace related documents and write execution data back.
• Map source and target Record Types.
• Close source documents automatically after completion.
• Split one document by detail attributes or merge details from multiple documents. Merging is planned.

Scenario 1: Automatically split and push an approved Purchase Requisition

Scenario description

1. A department submits one Purchase Requisition for computers from Supplier A and monitors from Supplier B.
2. The requisition is approved.
3. The system splits it into two Purchase Orders based on the Supplier field.

Recommended configuration

• Transform Purchase Requisition to Purchase Order.
• Map both master objects and their detail objects.
• Use Supplier as the split dimension.
• Trigger the push from a Workflow post-action after approval.

Scenario 2: Merge documents with reference creation

Scenario description

1. Departments submit multiple Purchase Requisitions.
2. At month-end, a buyer creates a Purchase Order and clicks Create by Reference.
3. The buyer selects requisitions awaiting procurement.
4. The system merges detail lines with the same material category and requested delivery date.

Recommended configuration

• Pull Purchase Requisition data into a Purchase Order through Create by Reference.
• Associate the action with the transformation rule.
• Merge when Material Category and Requested Delivery Date match.

Related topics

• Object transformation rule overview
• Configure transformation rules