Optimization Functions for Process Industry 
The optimization process is enhanced by several functions that can be applied in the process industry.
Container Planning
You can now also use optimization to carry out container planning. You set up container planning in the Consider Storage Properties field in the optimization profile. Optimization can take the following settings from the resource into account:
Maximum Stock Level
Set Remaining Fill Level to Zero
Allow Multiple Products
Container resource-based pegging is also considered based on the product master setting; for more information, see Maintaining Settings in Product Master Data.
Product storage definition master data is considered for the optimization process.
For more information on restrictions, see SAP Note 1171154.
Optimization with Resource Networks
Resource networks are considered by the optimization process. You can use the Consider Resource Networks field in the optimization profile to specify whether resource networks must be taken into account within an order or between orders, or in both cases.
Note
The Self-Reference indicator in the resource network master data is not considered by the optimization process. Since this indicator is always set for optimization, the sequence of operations on the same resource is always allowed.
Order Creation
Optimization can now create new orders and adjust or delete existing ones. You make the settings for these functions on the Order Creation tab screen in the optimization profile. For more information on restrictions, see SAP Note 1155421.
Integration
Dependencies and Restrictions in Optimization
The current functionality is designed for buffer processes between different production stages as well as simple mixing scenarios. The functionality in the optimizer cannot be used for reactor processes or chemical conversions (reactions) in container resources.
Master data attributes of container resources, such as minimum fill level or replenishment level, are not considered.
Each order should use any container resource only once. Each violation of this rule can result in violations of the maximum fill level.
Deallocation of late operations is not compatible with container resource planning as the deallocated operations can cause missing amounts in the storage balance. Such a deallocation is automatically disabled if you activate the container resource planning. Deallocation on the right horizon and due to validity periods is still possible, but with resulting storage violations in the last postprocessing step, when operations are shifted backward and deallocated.
Dependencies between orders: Any dependencies between orders besides pegging have a big impact on the container planning in performance and quality of the solution. Shelf life and maximum earliness are automatically disabled during the optimization run. You must avoid any external constraints, fixing of sequences, or prioritizations in your storage scenarios.
The decomposition is automatically deactivated if you activate the planning of storages.
Lot sizes: Lot sizes that are too large cause infeasibilities in the container planning. The optimizer tries to reduce such infeasibilities. To achieve good planning quality, the lot sizes should match with the storage capacities. One possible solution for this is the creation of orders with the optimizer.
Campaign planning: Container planning cannot be combined with campaign optimization on bottleneck resources. If there are already existing campaigns that should be considered together with storage constraints, the optimizer tries to achieve the uninterruptedness of campaigns but cannot guarantee it. Interruption of campaigns is not reported during optimization.
Selection of resources and horizons: If you plan a container resource, the optimizer must have the orders that produce into storage and orders that consume from storage inside the optimization problem. No other valid solution is possible.
Continuous material flow is not supported in connection with container resource planning. All continuous material flows affecting container resources are handled as discrete for optimization.
Time-dependent storage definitions or time-dependent storage usage parts of PPMs are not supported.
For detailed information and additional restrictions, see SAP Note 1171154.