Using INF for input pipe cost fields
You can use INF as a value for an input pipe on cost fields to prevent records with failed mappings from being used when the model is run. When the Input Pipe populates the cost with INF, the policy or lane will not be used during expansion and optimization.
You can use INF for input pipes on cost fields such as:
- Variable Transportation Cost on the Transportation Policies table – If INF is the result of the lookup, then the Transportation Policy is treated as if its Status is set to Exclude when the model is run.
- Unit Sourcing Cost on the Site Sourcing Policies and Customer Sourcing Policies tables – If INF is the result of the lookup, then the Sourcing Policy is treated as if its Status is set to Exclude when the model is run.
- Unit Production Cost field on the Production Policies table – If INF is the result of the lookup, then the Production Policy is treated as if its Status is set to Exclude when the model is run.
Last modified: Wednesday May 15, 2024