Académique Documents
Professionnel Documents
Culture Documents
Block Planning is the planning or pre-assignment of resource capacities for products with specific attributes, with the purpose of using the capacities more rationally. The attributes are described using characteristics from the SAP system.
In block planning, you define blocks on a resource that have a specific duration and attributes, for example, a duration of 2 days per block on which you manufacture products in various alloys of the same alloy group. A block is defined as a period of time, in which a resource processes one or more activities with the same attributes. The attributes are represented by CDP characteristics. The maintenance of block definition is done in the master data of the resource
Block schedule: /SAPAPO/CDPS0 with double-click on block Extended block schedule: /SAPAPO/CDPS0 with heuristic Extended Block
SAP_CDPBP_01:
Plan blocks
Rescheduling of activities on block-planned resources if block attributes have been changed.
SAP_CDPBP_02:
SAP_CDPBP_03:
SAP_CDPBP_04:
TLA6
TLA7
ITS8-9
Explanation: The block is defining a time period on a resource where only activities with specified characteristics can be scheduled. The block is defining as well wether it is fixed (no new orders); where the activities are to be scheduled (block border) and whether a block can be overbooked (%) The actual maintenance job of blocks can be done out of the Planning Board (/n/SAPAPO/CDPSC0) or from the resource master (/n/SAPAPO/RES01) Switch to tab Intervals
Choose line where you want to change and press reference cycle Specify
to insert a
when to insert cycle How many times to insert Whether existing blocks are to
be overwritten Downtimes to be considered
Press
to insert
You can maintain the block schedule from the resource master and set additional fields of the blocks from there. But it is recommended to use the planning board for this daily maintenance Press and define to display all fields
If you set this indicator, the system schedules component and operation dates on the block limits as follows: Input and output component of operations in the block The requirements date for the input components is scheduled to the start of the block, while the receipt date of the output components is scheduled to the end of the block. Use the consumption type At Activity End for receipt components and At Activity Start for requirements components; do not use any offsets as the system will adjust the dates accordingly at the block limits. System behavior may become unpredictable. The predecessor and successor operations of operations in the block The predecessor operations end at the start of the block at the latest, while the successor operations start at the end of the block at the earliest. The minimum intervals in the relationships of the predecessor and successor relationships for operations in the block refer to the start or end of the block. Use end-start relationships between the operations as the system will adjust the dates at the block limits accordingly. System behavior may become unpredictable. Dependencies Scheduling at block limits can be overwritten by the setting Schedule Operation on Block Limits in the strategy profile. Input or output components with continuous consumption are not scheduled to block limits; the same applies to the minimum or maximum offsets in relationships. The system will only schedule at block limits if the relevant activity lies in a compatible block. If the activity only partially lies in a compatible block, then the compatibility at the start of the block is valid for relationships to successor activities and requirements components, and the compatibility at the end of the block is valid for the predecessor activities and receipt components. This indicator cannot be set at the first or last block on the resource. If required, add additional blocks at the beginning or end if you want to use scheduling at block limits. If you delete blocks, the indicator might be set for the first or last block. The system ignores this setting, however.
The activities will not be planned in this block if the activities are scheduled again in a fixed block.
No additional activities will be planned in this block. Block Is Protected If you have set the protection indicator for a block, you cannot change the properties of that block on the maintenance screen. NOT used by I2P
If you set this indicator, the system considers the temporal tolerance that you have defined for the blocks. With block tolerance, the system can schedule an operation in the block in such a way that the operation extends beyond the block limit in the planning direction. A prerequisite is that depending on the planning direction - the start or end date of the operation lies within the block limit, and the operation does not extend further than the tolerance beyond the block limit. NOT USED
Block schedule
Overview Material stages Capacity Planning Scheduling Conversion Reporting
Block schedule (double-click on block in planning board) Block maintenance heuristic (mark resource in Planning Board and
choose Enhanced Block Maintenance Heurisitic
Mark resource
Maintenance mode 1: How to enter change - either Time Equivalent (e.g. # melts) Sequence
Maintenance mode 2: If a block is enlarged either shrink subsequent block or move subsequent blocks
Enter changed block size here (in unit defined in Maintenance mode) Insert Block Delete Block Insert Reference Cycle
Block schedule
Overview Material stages Capacity Planning Scheduling Conversion Reporting
When a block setup is changed the orders are not automatically rescheduled. You need to run a schedule heuristic E.g. within planning board mark resource, choose Deallocate and choose Function Heuristics Schedule Operations