Replenishment Using Run Schedule Quantities (SAP Library

Replenishment Using Run Schedule Quantities

Use

You use this function when you produce the necessary material yourself, using repetitive manufacturing. As soon as a kanban is set to EMPTY the system creates run schedule quantities for this material, for example planned orders for repetitive manufacturing, and this triggers production.

Prerequisites

You have entered a repetitive manufacturing profile for the material in the material master, that guarantees billing with cost collector.

You have created a production version for the material in the material master record.

You have created a cost collector.

In this process the system posts the costs incurred in production to the cost collector. To determine the cost collector see Product Cost Collectors .

You have placed an appropriate replenishment strategy in the control cycle:

In addition, you can use the standard replenishment strategy 0002, which you cannot, however, use in combination with material requirements planning. Here, you must exclude the MRP storage location.
You can also use replenishment strategy 0005. With this strategy you can combine KANBAN with MRP. Planned orders, which are created using MRP, are reduced on creating run schedule quantities by emptying a kanban. In the replenishment strategy you determine which planned orders are reduced, until which time planned orders are included in the reduction and whether, in the case of a cancellation of a run schedule quantity, another planned order is created.

The advantage of this process is that you have the option of a preview, you can plan components and you have current data available for the kanban calculation.

You have entered the production version in your control cycle under In-house production. In this way the system immediately creates run schedule quantities; it assigns the planned order directly to the line entered in the production version.

Actions

You set a kanban to EMPTY.

The system creates a run schedule quantity.

If you have chosen replenishment strategy 005, then the system also reduces the planned orders, which have been created by MRP.

The kanban or the information is transported by the demand source to the supply source. If necessary, the card is reprinted at the supply source or it is attached to the kanban.

The supply source receives the information on all the empty containers by means of the kanban or via the kanban board.

After the container has been filled by the supply source, you have three options:

The supply source backflushes the replenished quantity. The goods receipt for the material produced, the goods issue for the components and the deletion of the run schedule quantity are all automatically combined with the KANBAN backflush function in repetitive manufacturing (from the repetitive manufacturing menu under Backflush ® KANBAN backflush). In this backflush transaction, you can also branch into the component processing screen where you can change component materials or quantities. When you save the backflush, the system automatically sets the status to FULL.

Also read the section Posting Goods Receipt for KANBAN Materials.

The demand source sets the container to FULL. Then the system automatically backflushes the current data of the run schedule quantity. Backflush includes: GR for the replenished material, GI for the components and deletion of run schedule quantity.

Note

If you manually change the component list of the run schedule quantity (in order to change component quantities for example), the system automatically carries out the backflush with the changed run schedule quantity data when the kanban is set to FULL.

Note

If the status is set to FULL or the backflush transaction is posted without component processing, the system explodes the current BOM. If you want to change components, then you must use the backflushing function or you can manually change the run schedule quantity. In so doing, you access the component screen.

Caution

In the replenishment strategy you can determine whether and in what way planned orders are created again, if the user cancels the emptying of a kanban.