CSO integration requests

To use your model data in a CSO sourcing event, you create one or more sourcing requests. Each sourcing request is based on the Network Optimization output of a specific scenario that you have run in the current model. You choose whether to use InterSite Flows, Customer Flows, or both to define the transportation lanes, and whether or not to differentiate lanes by product attributes. When you create a request, a set of lanes is generated based on the options you have selected.

If you want to further limit the lanes in the request, you can filter the lane data. For example, you can restrict the lanes to a particular set of states. Once the lane definition is ready, you can send it to the CSO sourcing manager as a sourcing request.

The CSO Integration feature is available if the appropriate role has been assigned to your account. If you have questions about your roles and access to the feature, contact licensing@coupa.com.

How lanes are determined

Lanes are unique based on the source, destination, and product attributes (Hazardous Goods and Temperature Class). For example, assume you have InterSite Flow records like the following (a subset of columns is displayed):

These are the associated Sites records:

These are the associated Products records:

The set of lanes produced from these InterSite Flows would be as follows (again, a subset of columns is shown):

Create a sourcing request

1. Select Integrate > CSO Integration . You see the CSO Integration page.

2. Click Requests at the top of the page.

3. Click New Request. You see the New Sourcing Request flyout.

4. Enter the Request Name. The default name is "New Request (n)", where (n) is an incrementing number.

5. Select the Scenario you want to use. Keep in mind that the scenario must have Network Optimization output populated for the sourcing request to be valid. Only standard scenarios can be run for new requests. Scenarios defined as Rapid Solve Scenarios are not available. See Working with scenarios for additional information.

6. For the Lane Type, select one or both of the checkboxes. You must have at least one of the options selected for the sourcing request to be valid. By default, both options are checked.

   • Site to Site Lanes - The InterSite Flows are used as sources for the lane data.

   • Site to Customer Lanes - The Customer Flows are used as sources for the lane data.

7. Turn on the Differentiate Products by switch if you want specific product attributes to be included in the lane definition. When this switch is on, lanes are differentiated based on one or both of the following:

   • Hazardous - Lane definitions use the value in the Hazardous Goods column in the Products table. This value is based on the product in the InterSite Flows or Customer Flows record. Lanes will be unique for each combination of the Hazardous Goods and Temperature Class values. If you have not selected the Temperature Controlled checkbox, Temperature Class will be "Standard".

   • Temperature Controlled - Lane definitions use the value in the Temperature Class column in the Products table. This value is based on the product in the InterSite Flows or Customer Flows record. Lanes will be unique for each combination of the Hazardous Goods and Temperature Class values. If you have not selected the Hazardous checkbox, Hazardous Goods will be "No".

8. Click Save. The request definition is saved and you can review the lane data that will be included in the sourcing request. The lanes reflect the process described in how lanes are determined. If you want to limit the lane data, you can filter the sourcing request.

Handling updated optimization output

When you create a sourcing request, the lane definitions are based on the Network Optimization output populated at the request creation time. If you make changes to the model, such as excluding customers, and then re-run Network Optimization, the sourcing request lane data is not automatically updated. You must either edit the existing sourcing request or create a new sourcing request to ensure the lanes reflect the current output for the selected scenario.

Editing sourcing requests

After creating a sourcing request, you can edit it to change the options that define the request. You can continue to refine the sourcing request until you send it. Once you have sent the sourcing request, it cannot be edited or deleted, and no changes can be made to this request.

Edit a sourcing request

If you have sent the sourcing request, it cannot be edited.

1. Select Integrate > Sourcing Requests . You see the Sourcing Requests page.

2. Click the edit icon for an existing sourcing request. You see the Sourcing Request Details flyout.

3. Edit any of the options that define the request. You can use edit to change the request name in addition to the other options.

4. Click Save. The request definition is saved and you can review the lane data that will be included in the sourcing request. Click the refresh icon on the sourcing request tab to update the lane data in the grid.

Duplicate a sourcing request

1. Select Integrate > Sourcing Requests . You see the Sourcing Requests page.

2. Click the duplicate icon for an existing sourcing request. You see the New Sourcing Request flyout. The default name for new request is the original name appended with "(1)".

3. Edit any of the options that define the request. You can use edit to change the request name in addition to the other options.

4. Click Save. The request definition is saved and you can review the lane data that will be included in the sourcing request.

Delete a sourcing request

If you have sent the sourcing request, it cannot be deleted.

1. Select Integrate > Sourcing Requests . You see the Sourcing Requests page.

2. Click the delete icon for an existing sourcing request. You are prompted to confirm the deletion.

3. Click OK. The sourcing request is deleted.

Search sourcing requests

You can search within the list of sourcing requests using the filter.

1. Select Integrate > Sourcing Requests . You see the Sourcing Requests page.

2. In the filter field, start typing the name you are searching for. Sourcing requests that contain the characters are displayed in the navigation pane.