Maximum receipts constraint on Routes In
New upper bound on receipts at a location by transportation method is now available for Supply Chain Optimization. It allows users to specify a capacity constraint on incoming (unloading) docks for each location by transport method.
In SCP 20.8 the TRANSPORTATION_DOCK entity in SCV has been introduced to model the SCO Routes Out class. In this release, the same SCV entity is used to support the SCO Routes In class, including the new maximum receipts constraint in this class.
The default Supply Chain Optimization Planning Engine definition (SP_SCO) has been extended in a previous version, and activated now with supporting configuration in SCV and Planning Engine SP SCO.
- Classes:
- Transfers, Routes, Routes In, Locations and Money
- Optimization "Solver"
- Variables
- Workflows
- Queries
See Change_log.html, accessible from the SCO Planning Engine documentation in the standard content for additional details on the changes to SCO for this feature.
- SP_V_ROUTE_IN_CALENDAR, using SM_TRANSPORTATION_DOCK_BUCKETS as source
- SP_V_ROUTES_IN, using SC_TRANSPORTATION_DOCK as source
- New class property app default: APSCO_BASE_Profile_Routes In_max_receipts_tu
- New class property app default: APSCO_BASE_Profile_Routes In_max_receipts_discrete
- New class property app default: APSCO_BASE_Profile_Routes In_vehicle_capacity
- SCO - SP_V_ROUTES_IN
- SCO - SP_V_ROUTE_IN_CALENDAR
- SP - SCV - SCO - Import Route In Calendar
- SP - SCV - SCO - Import Routes In
- SCV - SCO Import Transactional Data
- SCO_Routes In Chart
- SCO_Routes InTP
- SCO_Routes In
- SCO_Routes In Grid
- SCO_4TransportResource
- SCO_4Transport_Plan_Review
You are not required to have a new role or privilege access to use this feature.