32 planning run

14
SAP AG R Planning R un © SAP AG TAMM10 4.0B 32-1

Upload: lymacsauok

Post on 10-Nov-2015

218 views

Category:

Documents


3 download

DESCRIPTION

Planning Run

TRANSCRIPT

You can carry out the planning run as a total planning run for one specific plant. With this procedure, all the materials that are relevant for planning are planned. It includes BOM explosion for BOM materials.

The total planning run can be carried out online or in the background processing mode.

You can carry out the planning run as single-item planning. In this case, the planning run is carried out for one particular material either single or multi-level. In single-item, single-level planning, the system only plans the BOM level of the selected material. In single-item, multi-level planning, the system plans the level of the selected material plus all the lower BOM levels.

The planning file contains entries for all the materials relevant to planning, provided that MRP is activated for the plant.

The planning file controls the planning run and the scope of the planning.

When a change relevant to planning (for example, creation of a purchase order) occurs, a change indicator is set in the planning file for the respective entry (file entry NETCH). When a change relevant to planning occurs withing the planning horizon, another change indicator is set (file entry NETPL).

In Customizing, you can define the planning horizon as a plant parameter or as a MRP group parameter.

Changes relevant to planning can be:

Changes involving stocks, provided they change the stock/requirements situation of the material

The addition of purchase requisitions, purchase orders, planned orders, sales requirements, forecast requirements, dependent requirements or reservations.

Changes to fields relevant to planning of these goods receipts or issues or of the material master record,

The deletion of goods receipts or goods issues.

The low-level code is the lowest level that a material appears on in any bill of materials.

The low-level code controls the planning sequence: first, the low-level code 0 materials are planned, then, the low-level code 1 materials are planned, and so on.

Requirements planning can be carried out for various numbers of materials. The planning run type controls the scope of the materials to be planned. The planning run type is specified by the field processing key in the entry screen.

The following types of MRP runs are possible:

Regenerative planning (processing key NEUPL): The system plans all materials which are included in the planning file irrespective of all indicators.

Net change planning (processing key NETCH): The system only plans those materials which are provided with the change indicator NETCH.

Net change planning in the short-term planning horizon (processing key NETPL): The system only plans those materials provided with the change indicator NETPL.

On completion of the planning run, the appropriate indicator is automatically deletetd in the planning file:

The system deletes the total change indicator and the net change indicator for a regenerative planning run and a net change planning run.

The system only deletes the net change planning indicator for a net change planning run in the planning horizon.

In order to accelerate planning, it can be limited to a certain planning horizon. Only those requirements that are within the planning horizon are covered by receipts.

Note: Due to the progress of time, requirements can occur in the planning horizon that have not yet been covered by receipts. If no other changes relevant to planning occur, these requirements will only be covered during the next planning run over the entire time frame. This is why this kind of planning run should be carried out on a regular basis.

In Customizing, the planning horizon is defined as a plant or MRP group parameter.

The creation indicator controls the creation of planned orders or purchase requisitions, schedule lines, and MRP lists.

By entering the creation indicator for purchase requisitions in the entry screen of the planning run, you can control whether the system should directly create purchase requisitions or planned orders first.

If a schedule line exists for a material and the source list contains an entry relevant for planning, schedule lines can also be created directly via materials planning. This is controlled by the creation indicator for schedule lines in the entry screen of the planning run.

You can save the planning results in the form of MRP lists. The creation indicator for MRP lists controls whether the system should always create an MRP list for all planned materials or whether it should create an MRP list for certain materials depending on the exception message.

In total planning, the creation indicator in the entry screen is used for planning if no other plant or MRP group parameters have been maintained for the material.

Plant parameters are control parameters for material requirements planning which are defined in Customizing for each plant.

The MRP group is an organizational object which is used to allocate certain control parameters for MRP to a group of materials. If your company requires more detailed control of the planning for each plant and you want to allocate control parameters to certain material groups that are different from the plant definition, you can maintain MRP groups and MRP group parameters in Customizing.

You can allocate the MRP group in the material master record.

If an MRP group was allocated to a material type, it will default in the material master record.

In total planning, the system checks for each material whether the material was allocated a MRP group:

If no MRP group is allocated to the material, it is planned using plant parameters.

If a MRP group is allocated to the material, it is planned using MRP group parameters.

In single-item planning, the parameters entered in the entry screen are always used for planning.

SAP AGTAMM10 4.0B32-11