Model building configuration

A new home for the Coupa Supply Chain documentation

Starting with Supply Chain 42, our documentation will be located on Coupa Compass. The help here will continue to be accessible for the foreseeable future, but will no longer be updated. If you need a Compass user account, contact your company’s Designated Support Contact (DSC).

You can access new and updated Supply Chain documentation in the following location on Compass:

https://compass.coupa.com/en-us/products/supply-chain-design-and-planning

Model building configuration

Reusable model configurations let you tailor data selection as needed for your supply chain design study. Within the configuration you determine:

the name for your model recipe
the source for your Customer Orders
the location types to be used for Customer and Production nodes

Values that are required for a valid model recipe are flagged with *.

Set up recipe configuration

Click the Configuration node for the current recipe definition.
Enter the Model Recipe Name. Provide a name that is unique for the Decision Data Model (DDM) you are using.
Optionally provide a Description with details about the model recipe you are creating. You can enter up to 256 characters for the description. Text below the Description indicates how many characters are remaining.
Click Next or click the Customer Orders node.
Select the Transactions that determine the source of transactional data. For the current Network Optimization and Greenfield Analysis models, this data will populate the Customer Orders table in the target model. The source of transactional data is one of:
- Orders Full
- Shipments Full
- Demand Forecast
- Orders Full + Demand Forecast - records from both DDM tables that fall within the model horizon will be used to create Customer Orders.
- Shipments Full + Demand Forecast - records from both DDM tables that fall within the model horizon will be used to create Customer Orders.
  
  The Notes column in Customer Orders in your model is populated with either "historic" or "forecast" to identify the source of the order data.
Click Next or click the Location Types node.
For Customer Location Type, select one or more location types that represent the demand nodes in your model. These are the location types that demand products.
- You must select at least one location type.
- Location types you select as production location types are not available for use as customer location types.
- Any location types not selected as customer location types are considered sites.
  
  If you have already added scope filters or advanced aggregation to Customers or Sites, you cannot add or remove a Customer Location Type value without those filter and aggregation settings being discarded.
For Production Location Type, select one or more location types that represent the production nodes in your model. These are the location types that produce products. When you are generating policies from one of the DDM sources, the location type(s) you select determine which sites can be used in Production Policies.
- You must select at least one location type.
- Location types you select as production location types are not available for use as customer location types.
Your recipe now has all required fields. You can click Save to save the configuration information and continue editing the recipe definition.
If you are not filtering, aggregating, or adding policies to your data and the recipe definition is complete, click Save and Close to save the current configuration information and close the recipe. If any required fields are not populated or there are other issues with required data, the associated nodes are highlighted in red and validation warnings are displayed. Complete the required fields, then click Save and Close. The recipe is saved and is displayed in the table of model recipes.

When the information on the Configuration node is valid and you click Next, note the following:

The Scope, Aggregation, and Policies & Constraints nodes are now enabled, and you can proceed with additional recipe definition as needed. If you are not adding Scope, Aggregation or Policies & Constraints definitions to the recipe, you can use the configured recipe to build models.

Cancel the recipe definition

On any of the nodes in the recipe definition, click Cancel or click the X at the top right of the page. You are warned that the recipe will be closed and will not be saved.
Click Discard to close the recipe without saving the definition, or click Save to save and close the recipe.