Pretransformation Rules
Use a pretransformation rule to populate an order attribute or set its default value before Order Management transforms the source order.
Example Usage |
Description |
---|---|
Populate an attribute on a fulfillment line. |
Assume your sales order includes the Request Date attribute, and you must display it on fulfillment lines, but only for the AS54888 desktop computer. Here's your rule.
|
Populate an attribute so you can use it in a transformation rule. |
Assume your sales order includes the AS54888, you must convert its size from centimeters to inches, then display it on the fulfillment line. Here's your rule.
|
Order Management runs pretransformation rules each time the Order Entry Specialist modifies the sales order.
Learn how to use a pretransformation rule to set default values. For details, see Set Default Values for Other Attributes on Sales Orders.
Set Transaction Type Before You Transform
You can run a pretransformation rule only on some events, such as when you select the business unit, customer, or order type, or when you add an order line.
Also, pretransformation and posttransformation rules might not run when you create a sales order through a web service, REST API, or file-based data import.
If you must set the transaction type before you transform, and if you must set it when an event happens that doesn't start a pretransformation rule, or if you create a sales order through a web service, REST API, or file-based data import, then don't use a transformation rule to set the attribute values. Use an order management extension instead. Read the Set the Billing Transaction Type According to Order Type subtopic. For details, see Extend Order Headers.
If you're returning a sales order, then you must set the transaction type to Credit Memo.
For details and examples, go to REST API for Oracle Supply Chain Management Cloud, expand Order Management, then click Sales Orders for Order Hub.