Show TOC

Process documentationProduction Scheduling for Resource Networks Locate this document in the navigation structure

 

Resource networks simplify the modeling of resource restrictions for consecutive operations or orders. For process industries in particular, certain production restrictions often apply. For example, if an operation takes place on a resource such as a reactor or blend vessel, then only a limited set of successor resources (such as storage tanks for intermediates or finished bulk products or filling lines) can be used for the successor operation.

With resource networks, you can model existing production constraints more precisely, with the objective of creating a finite and technically feasible production schedule. Resource networks also reduce the combinatorial complexity of mode coupling as an alternative way of modeling resource connections and availability.

Resource networks are intended to define allowed physical connections between resources. They basically represent pipes or other means of transport to move products produced by one resource to another resource where it is consumed. A product flow in this application is a real product flow, meaning that it may not necessarily be a product known within the system (PEGID) that is transported, but may be an intermediate product that exists between the operations or phases within an order.

The business process Production Scheduling with Resource Networks contains the following processes:

  • Definition of resource networks

  • PP/DS (Production Planning and Detailed Scheduling) optimization run with resource network constraints

  • Manual rescheduling (resource networks within orders)

Prerequisites

  • The complete planning environment exists.

  • The corresponding master data exists (without the resource networks-related data).

  • The strategy profiles exist.

  • The detailed scheduling planning board profile exists.

  • The optimization profile exists.

  • The alert profile exists.

  • The settings for data transfer between SAP ERP and SAP SCM are maintained.

  • Customer order or demand forecast requirements exist either in the SAP ERP system (to be transferred using CIF), or in the SAP SCM system.

Process

The business process runs as follows:

  1. Define resource networks (SAP SCM):

    Resource networks are defined as separate business objects by a unique identifier and a description, and are assigned to a model. Planners can define a resource in more than one resource network for optimum flexibility. The resource definition can be used to link several resource networks with each other and to build complex networks from simpler ones.

  2. Assign resource network to location product master (SAP SCM):

    The resource network is linked through its unique name to the location product master in SAP SCM, along with a resource network strategy which determines whether the resource network constraint will considered or not. For more information, see Requirement (Demand) Data.

  3. Infinite Planning (MRP, SAP SCM) (Optional):

    The planning run in SAP SCM PP generates the planned orders for finished products based on the sales orders and demands. Depending on the planning strategy settings, planned orders can be created for secondary demands through bill of materials (BOM) explosions.

    Resource capacity is considered as infinite. For more information, see Production Planning Run.

  4. Finite scheduling with PP/DS optimization (SAP SCM):

    During optimization, the system carries out finite scheduling to achieve a feasible production plan. You can optimize the production dates and the resource allocation for operations based on criteria you define in the optimization profile. For more information, see Optimization.

  5. Check alerts for resource network violations:

    Resource network violations are signaled by alerts. The alert monitor is configurable and can display a wide range of PP/DS-specific alerts, such as for capacity, date, and quantity problems. In a PP/DS alert profile, you can specify both the alert types that can be displayed as well as the threshold value for the priority of the alerts (error, warning, or information), depending on the seriousness of the problem. For example, for a day's delay, the alert monitor can be configured to trigger an error alert, and for an hour's delay, an info alert.

    You can display or hide the Alert Monitor as required. A list of order-related alerts is also integrated in the order processing view.

    For more information, see Display of Alerts.

  6. Manually resolve resource network issues:

    Interactive Planning should normally be carried out only for critical items that require a Management by Exception process, which should be developed based on relevant alerts.

    The interactive Detailed Scheduling Planning Board is the recommended tool in SAP SCM for resolving any remaining schedule issues by manual dragging and dropping of activities within a time grid or from one resource to another. This allows eliminating resource network violations (detected by the alert monitor) or using alternative resources from the same network, which may present better options for the specific exceptional situation.

    For more information, see Scheduling with the Detailed Schedule Planning Board.

  7. Transfer planned and process orders to SAP ERP:

    You can control when orders that you have created or changed in SAP APO are transferred to the connected SAP ERP system. By making specific transfers, you can reduce the load on the interface between the SAP APO system and the SAP ERP system.

    You can link the transfer of planned orders or purchase requisitions with automatic order opening in the SAP ERP system.

  8. Process planned/process orders (SAP ERP):

    When a planned or process order is changed in SAP ERP, such as when a planned order is converted to a process order that is transferred back to SAP SCM, the original product storage definition is retained in the order in SAP APO.