Send Notifications from Order Management to Other Systems

Set up Order Management to send a notification to a system that resides outside of Order Management.

Summary of the Steps

Add the connector.
Manage business event trigger points.
Set the notification frequency.

Learn how to do the set up. For details, see Guidelines for Integrating Order Management and Use Integration Cloud Service with Order Management.

Follow these guidelines:

Use a connector only to connect to an application that resides outside of Oracle.
Don't use a connector to connect to Integration Cloud Service.
Make sure the value that you specify in the Connector URL attribute references a resource that's up and running, and that you correctly format the URL.

Following these guidelines will help to make sure you don't degrade performance.

This topic uses example values. You might need different values, depending on your business requirements.

Add the Connector

Add the connector that Order Management uses to communicate with your system.

In the Setup and Maintenance work area, go to the task.
- Offering: Order Management
- Functional Area: Orders
- Task: Manage External Interface Web Service Details

On the Manage Connector Details page, click Actions > Add Row, then set the values.

Attribute	Value
Target System	Select the system that must receive the notification. This system subscribes to the business event.
Connector Name	Enter text that describes the purpose of the connector. For example, to indicate that you use this connector to send notifications to a legacy system, enter `LEG_Notification`.
Connector URL	Specify an endpoint URL. The URL is the address of the web service that you deploy on a system that resides outside of Oracle Order Management. Order Management will call this web service, and the web service must accept the payload that Order Management sends. Make sure the web service uses this WSDL: `https://server:port/soa-infra/services/default/DooTaskExternalInterfaceVirtualPartnersComposite/businesseventsconnetor_client_ep?WSDL`
User Name	Enter the user name that the system requires.
Password	Enter the password that the system requires.

Manage Business Event Trigger Points

Manage the business event trigger points that determine when to communicate business events to your system.

In the Setup and Maintenance work area, go to the task.
- Offering: Order Management
- Functional Area: Orders
- Task: Manage Business Event Trigger Points
On the Manage Business Event Trigger Points page, select a trigger point.

At run time, if the sales order reaches the trigger point you specify, then Order Management calls the web service you select in the Connector URL attribute. The web service then sends details of the business event to the system. For example, to send a notification when a fulfillment line closes, select the Fulfillment Line Closed trigger point.
Click Actions > Add Row.

Some trigger points include the Associated Connectors tab in the details area. If this tab displays, then click it to add the connector.

Set the values.

Attribute	Value
Connector Name	Select the connector you added earlier in this topic.
Override Default Visibility	Select one. Contains a check mark. Send a notification about each sales order even if the system that receives the notification doesn't have any knowledge about the sales order. Doesn't contain a check mark. If the system doesn't have any knowledge about the sales order, then don't send the notification about the sales order. Here's an example. Assume your implementation includes Source System 1 and Source System 2, and that each of these systems can send a source order to Order Management. Assume Source System 2 has no knowledge of source orders that originate in Source System 1, and that you don't want to notify Source System 2 when an event happens that's associated with a source order that originates in Source System 1. If Override Default Visibility doesn't contain a check mark, then Order Management won't call the connector for Source System 2, and Source System 2 won't receive the notification.

Attribute

Value

Connector Name

Select the connector you added earlier in this topic.

Override Default Visibility

Select one.

Contains a check mark. Send a notification about each sales order even if the system that receives the notification doesn't have any knowledge about the sales order.
Doesn't contain a check mark. If the system doesn't have any knowledge about the sales order, then don't send the notification about the sales order.

Here's an example.

Assume your implementation includes Source System 1 and Source System 2, and that each of these systems can send a source order to Order Management.
Assume Source System 2 has no knowledge of source orders that originate in Source System 1, and that you don't want to notify Source System 2 when an event happens that's associated with a source order that originates in Source System 1.
If Override Default Visibility doesn't contain a check mark, then Order Management won't call the connector for Source System 2, and Source System 2 won't receive the notification.

Optional. Repeat step 3 and step 4.

You can associate the same connector with more than one business event, as necessary.
Optional. Repeat step 2 through 5 for each trigger point you must administer.
Click Save and Close.

Set the Notification Frequency

Use the Notify Frequency parameter to specify how frequently Order Management sends notifications. For details, see Manage Order Management Parameters.