Actions That You Can Set When Routing Requests to Fulfillment Systems
Use actions in your routing rules to specify how to route each request to your fulfillment system.
For details about:
-
Where you set actions in the routing rule, see Manage Routing Rules.
-
How to specify actions in the payload that the Fulfillment Order service uses, see Task Services.
Here are the actions that you can use.
Action |
Description |
Value |
Attribute to Use in Payload |
Data Type to Use in Payload |
---|---|---|---|---|
Override Compensation Pattern |
Override the compensation pattern that the orchestration process specifies. Use this action only for your own custom fulfillment task. Don't use it for a predefined fulfillment task because predefined tasks already have a compensation pattern. |
|
COMPENSATION_PATTERN |
String |
Override Operation |
Override an operation. Order Management uses operations, such as Create, Update, Process, and so on. Your fulfillment system might not recognize these operations. Use this action to specify an operation that your fulfillment system recognizes. Use this action only with task types that you create. Don't use it with predefined task types. |
Text or alphanumeric value. |
MODIFIED_OPERATION |
String |
Prepare Result |
Don't use this action or the ResultKey and ResultValue parameters that it uses. They are for Oracle internal only. |
Not applicable |
Not applicable |
Not applicable |
Resolve Cross-Reference for Customer |
Specify whether to use a cross-reference. If your fulfillment system uses the same attribute values that Order Management uses, then set this action to No because a cross-reference is useful only when these values are different. For details, see Create Cross-References in Order Management. |
|
RESOLVE_XREF_FOR_CUSTOMERINFO |
String |
Set Acknowledgement Timeout |
Amount of time to wait before exiting out of an implicit wait during an interaction with your fulfillment system or with an Oracle Application. Don't use this action with tasks that involve inventory management, shipping, or accounts receivable. |
Use a numeric value for days, hours, minutes, or seconds. For example, 10 minutes. |
ACK_TIMEOUT_PERIOD |
Number |
Set Connector Name |
Connector name that the web service uses to communicate details to your fulfillment system. This name helps Order Management route the message to the web service URL that this connector references. For details about how to set up a connector so you can specify it in this action, see Manage Connector Details Between Order Management and Your Fulfillment System. |
You can use these predefined connectors:
|
SERVICE_NAME |
String |
Set Interaction Interface Type |
Format to use when Order Management interacts with your fulfillment system. |
|
InterfaceType |
String |
Set Maximum Lines to Aggregate and Send |
For details, see Aggregate Requests That Order Management Sends to Your Fulfillment System. |
Not applicable |
AGGREGATOR_MAX_FLINES |
Number |
Set Maximum Time to Wait Before Enabling Abort |
Order Management sends a request to your fulfillment system or to some other Oracle Application, and then waits to receive a reply. The reply typically arrives within a few seconds. Starting with Update 21C, use the Set Maximum Time to Wait Before Enabling Abort parameter instead of Set Maximum Time to Wait Before Allowing Cancel. Use this action to specify how long to wait for the reply and avoid a situation where Order Management goes into a perpetual wait state because of a problem that happens during the transaction, such as the network going down. Here are the wait times that Set Acknowledgement Timeout sets, by default.
Don't use this action with tasks that involve inventory management, shipping, or accounts receivable. |
Use a numeric value to express time of day, such as days, hours, minutes, or seconds. |
ABORT_ENABLE_PERIOD |
Number |
Set Maximum Time to Wait Before Aggregation |
Starting with update 21C, use Set Maximum Time to Wait Before Aggregation instead of Set Maximum Time To Wait Before Sending. For details, see Aggregate Requests That Order Management Sends to Your Fulfillment System. |
Not applicable |
AGGREGATOR_MAX_TIMEOUT |
Number |
Note
-
Don't use the Set a Value operation in the DO clause.
-
You must use the Connector Name action and the Interface Type action. All other actions are optional.
-
You can use any action when you integrate with an application that isn't an Oracle application. You can also use the Set Acknowledgement Timeout action or the Set Maximum Time to Wait Before Allowing Cancel action when you integrate with some other Oracle application.