Ansicht
Dokumentation

Bucket-Oriented Capacity Check in the CTP Process (New) ( RELNSCM410_APO_PPDS_CTP )

rdisp/max_wprun_time - Maximum work process run time   ABAP Short Reference  
This documentation is copyright by SAP AG.

Short text

Bucket-Oriented Capacity Check in the CTP Process (New)

Use

In SAP SCM 4.1, the CTP process has been enhanced by the bucket-oriented capacity check. This check, based on the PP/DS bucket capacity, is now the standard procedure in the CTP process from SCM 4.1 which the system uses to execute the capacity availability check and the capacity reservation for important resources (bottleneck resources).

Up until SAP SCM 4.0, you could only execute a time-exact scheduling for the sales orders on the basis of the time-continuous capacity of a resource using the strategy Find gap. This process has the following disadvantages:

• When scheduling on the basis of the time-continuous capacity of a resource, gaps of various sizes arise that cannot be used by other orders.

• When using sequence-dependent setup activities, the orders may be scheduled in an unsuitable sequence due to the random receipt of the orders. This means that too much capacity is wasted on setup activities and the result is a poor utilization of capacity.

• Using the time-exact CTP check over several production levels is also problematic. The fragmented loads of the resources increase with each level checked and cause an increase in the lead time of the orders. The delivery date calculated by the CTP check may lie so far in the future that it is no longer realistic.

To avoid these disadvantages, in SAP SCM 4.1 the bucket-oriented capacity check has been implemented in PP/DS. The main aim of the bucket-oriented capacity check is the improvement of the capacity load by avoiding a fragmented capacity load utilization. The system achieves this by checking and reserving the available capacity per period (Bucket). A bucket can be one day or a week, for example. Due to the period-oriented capacity check, the system can schedule many more orders as it tries to use up the capacity of a bucket completely (for example, one day of 8 hours).

Advantages of the Bucket-Oriented Capacity Check in the CTP Process

• The system calculates feasible delivery dates and creates the planned orders with a relatively high capacity load utilization.

• Due to the simplified capacity check and scheduling process, the system can create the planned orders very quickly in the CTP process. The sales employee can give binding confirmations independently of the production planner.

• Several resources can be scheduled finitely in a CTP check without the lead time increasing unnecessarily.

Prerequisites

• You can only execute the bucket-oriented capacity check for the following resource types:

• Single-activity resource

• Single-mixed resource

• Multiactivity resource (created dimension-free)

• Multimixed resource (created dimension-free)

• The resource to be checked must have the following settings:

• You have set the indicator Finite Scheduling in the tab page General Data.

• You have defined the parameters for the time-continuous capacity.

• In the tab page PP/DS Bucket Cap., you have maintained the parameters for the PP/DS bucket capacity:

Bucket Definition

Bucket Schema

Bucket Factor

Finite Capacity

• Using the function key Bucket Capacity, you can display the capacity profiles, for example, capacity per bucket in hours.

• The resource to be checked must be assigned as the primary resource in a PPM or in a PDS and the Calendar Resource indicator must be set.

Using the Check Plans function key in the resource maintenance, you can check whether you have made these settings for a certain resource. You can also carry out the same check using the model consistency check.

• For the CTP check, you use the Standard strategy profile SAP_BCTP or your own strategy profile with the same settings.

Procedure of the Bucket-Oriented Capacity Check in the CTP Process

1. Create sales order

In the CTP process, you execute an ATP check in SAP APO for the newly received sales order. If the requested quantity of the product cannot be confirmed for the desired date, the system accesses production planning and detailed scheduling. The requirement is trasferred to PP/DS.

1. Create temporary planned orders

In PP/DS, the system executes a source of supply determination, a planned order explosion and scheduling. When scheduling the planned order, the system starts from the desired date and schedules in a backwards direction. Depending on the lot size, the system creates temporary planned orders.

1. Execute bucket-oriented capacity check

The system starts from the desired date of the order and checks in a backwards direction to see whether sufficient bucket capacity is available for the operation. In this process, the system takes account of the constraints, such as, the relationships or desired date of the order, for example. If sufficient capacity is available in the required bucket, it is reserved for the operation. At the same time, the operation is scheduled infinitely on the time-continuous capacity. Then the system can calculate the availability date of the planned order and calculate a confirmation date.

If not enough bucket capacity is available for the desired date, the system searches in a backward scheduling direction for free capacity. If this is not successful, the system switchs to a forward scheduling direction to search for free capacity.

1. Save sales order

You save the sales order. In SAP APO, the temporary planned order is replaced by a planned order that is assigned to the account of the sales order.

1. Execute detailed scheduling

No time-exact production plan is created in the bucket-oriented capacity check in the CTP process. That is, the operations of the orders may overlap on the resources.

If you require a time-continuous production plan (with exact production dates), you then have to execute detailed scheduling.

Limitations

• The bucket-finite capacity check is a rough capacity check. The resulting requirements and availability dates are therefore only exact per bucket. The bucket-oriented capacity check does not create a finite production plan. If you want a finite production plan, you have to execute Detailed Scheduling later.

• The sequence-dependent setup activities are only considered in the capacity check in the form of average setup times or capacity reductions. If the average setup duration lies below the setup duration calculated in the setup optimization, it is possible that the dates cannot be respected.

• You should not use the bucket-oriented capacity check in CTP if the capacity requirements of the setup activities represent a high proportion of the total capacity requirements. In this case, block planning may provide the better alternative.

Effects on Existing Data

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

To execute the bucket-oriented capacity check, the standard strategy profile SAP_BCTP has been added in SCM 4.1. Check the strategy profile in the IMG activity Maintaining Strategy Profiles and create your own strategy profile with the same settings.

Further Information

Release Information: Enhancements to Resource Maintenance

Release Information: Bucket-Oriented Block Planning (Changed)

Consultant Note: xxxxxx

BAL_S_LOG - Application Log: Log header data   General Material Data  
This documentation is copyright by SAP AG.

Length: 10623 Date: 20240520 Time: 224127     sap01-206 ( 174 ms )