Ansicht
Dokumentation

Container Control / MRP: Separate Goods Receipt ( RELNPP_KAB_30F_SEPWE )

Addresses (Business Address Services)   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Container Control / MRP: Separate Goods Receipt

Description

In the replenishment strategy, "Container control / MRP", the system automatically sets the indicator, Separate GR for in-house production and external procurement in the standard. This means that the goods receipt and the setting of the container to FULL must be carried out in two separate steps. This is necessary as, in this type of replenishment control, no relationship exists between a kanban and a replenishment element created in the planning run.

From release 3.0D, the indicator Separate GR can be switched off in two cases as a relationship can be established between the kanban and the replenishment element via the control cycle:

• In-house production with strategy 0004 (container control / MRP)

Repetitive manufucturing is used and the production version for which a run schedule header exits is recorded in the control cycle.

• External procurement with strategy 0006 (container control / MRP)

Scheduling agreements are used and the scheduling agreement is recorded in the control cycle. Note that this scheduling agreement can have no KANBAN indicator.

If, in these two cases, the indicator Separate GR is switched off, then the system automatically posts a goods receipt for the run schedule header / scheduling agreement when setting the kanban to FULL. If, however, you post a goods receipt for the RS header / scheduling agreement manually, the system does not set a kanban to FULL in the background. Therefore, you should avoid posting goods receipts manually in this procedure or you should limit it to posting differences.

Example

In external procurement, the procedure is as follows:

A scheduling agreement exists with the vendor for the material. Schedule lines are created for this scheduling agreement in the planning run that provide the vendor with an overview. You have arranged with the vendor that no delivery is made for these schedule lines. Instead, the vendor waits until the quantity is released by KANBAN.

If a kanban is set to EMPTY, the system does not create a schedule line, nor does it create a purchase order. Instead, it only records information on the quantity and date in the form of a kanban.

Here, kanbans can be reprinted, for example, and a fax may be sent to the vendor. Or, the vendor may deliver in certain cycle and collect the new EMPTY kanbans when delivering the goods.

If the kanban is set to FULL, the system automatically posts a goods receipt for the scheduling agreement for the kanban quantity. That is, the oldest schedule line is reduced by the goods receipt quantity.

Damage caused to data by errors

Software/hardware requirements

Installation information

Effects on System Administration

Effects on Customizing

Effect on batch input

Changes to the Interface

Changes in procedure

Procedure for removing dataset errors

Dependent functions

Planning

Further notes

PERFORM Short Reference   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 3592 Date: 20240604 Time: 071141     sap01-206 ( 73 ms )