1. Implementing Order Management
  2. Guidelines for Sending the Response from Your Order Fulfillment System

Guidelines for Sending the Response from Your Order Fulfillment System

The connector sends a request to your order fulfillment system, then the fulfillment system sends a response. You can use services in the response to communicate status updates from your fulfillment system to Order Management.

Service

Go Here for Details

FulfillmentResponse Service

Web Services That You Can Use to Integrate Order Management

Order Fulfillment Response Service

Use Integration Cloud Service with Order Management

Identify Hosts and Ports

Identify the hosts and ports that you will use to access your payloads. Go to the Setup and Maintenance work area, then click Tasks > Review Topology. For details, see Identify Hosts and Ports for Order Management.

the Review Topology page.

For example:

  • If you use Oracle Application Development Framework (ADF), then use the host and port for FSCMServices.

  • If you use Oracle Service-Oriented Architecture (SOA), then use the host and port for FASOA (Oracle Applications, Service-Oriented Architecture).

Set Up Payload for FulfillmentResponse Service

If you use Service-Oriented Architecture, then set up the payload for the FulfillmentResponse service.

Payload for FulfillmentResponse Service.

The payload that your fulfillment system sends must include these attributes.

<ns2:FulfillLineId>Id_number</ns2:FulfillLineId>
            <ns2:SourceOrderSystem>system_name</ns2:SourceOrderSystem>

For example:

<ns2:FulfillLineId>300100072403436</ns2:FulfillLineId>
<ns2:SourceOrderSystem>GPR</ns2:SourceOrderSystem>

where

  • 300100072403436 is the fulfillment line Id.

  • GPR is the source order system. Order Management typically uses the phrase source order to refer to an order that resides in an upstream order capture system. However, in this instance, SourceOrderSystem means any system that provides input details to FulfillmentResponse.

As an option, you can also send other attributes, such as ShippedQuantity, according to your business requirements.

Order Management needs SourceOrderSystem so it can get the user name, password, and Keystore Recipient Alias from the Manage Connector Details page and use them when it sends a reply to your order fulfillment system. It uses SourceOrderSystem to search the list of connectors on the Manage Connector Details page. It searches the list in alphanumeric order, and selects the first connector it finds where the value in the Target System attribute matches the value in SourceOrderSystem. Make sure you add your connectors and name them so Order Management uses the one you need.

Assume SourceOrderSystem contains OrderCapture1, and the Manage Connector Details page contains three connectors.

Target System

Connector Name

User Name

Password

Keystore Recipient Alias

OrderCapture1

My Connector A

Administrator1

******

-

OrderCapture2

My Connector B

Administrator2

******

-

OrderCapture1

My Connector C

Administrator3

******

-

Order Management will use the Administrator1 user, password, and Keystore Recipient Alias from the row for My Connector A.

For details about how to use your payload, see Connect Order Management to Your Fulfillment System.

If you create your own task type, then you must use a slightly different payload. For details, see Create Your Own Task Type.

Set Up Payload for Order Fulfillment Response Service

If you use Application Development Framework, then set up the payload for the Order Fulfillment Response service.

payload for service Order Fulfillment Response.

The payload that your fulfillment system sends must include these attributes.

<com:IntegrationContextCode>context_code</com.IntegrationContextCode>
<com:FulfillmentSystem/>
<com:FulfillLineIdentifier>numeric_value</com:FulfillLineIdentifier>
            <com:TaskInstanceStatusCode>status_code</com:TaskInstanceStatusCode>

For example:

<com:IntegrationContextCode>DOO_TransportationPlanning</com.IntegrationContextCode>
<com:FulfillmentSystem/> 
<com:FulfillLineIdentifier>3001000071295736</com:FulfillLineIdentifier>
<com:TaskInstanceStatusCode>DOO_TP_DELIVERED</com:TaskInstanceStatusCode>

where

  • DOO_TransportationPlanning is the IntegrationContextCode.

  • 3001000071295736 is the FulfillLineIdentifier.

  • DOO_TP_DELIVERED is the TaskInstanceStatusCode.

Set Up Payload for Extensible Flexfield

You integrate an extensible flexfield with your fulfillment system the same way you integrate it during order import. The only difference is that instead of modifying the XSD file that you use during order import, you modify the XSD file that you use when you integrate with your fulfillment system. For details, see the section that describes how to integrate with web services during order import in Guidelines for Setting Up Extensible Flexfields in Order Management.

Related Topics