Breakdown replenishment

MRP > MRP Wizard > MRP scenario planning > Detail > Breakdown replenishment

Top  Previous  Next
Expand/Collapse Toggles

Breakdown replenishment

Peggings cause another requirement in the case of assemblies. If there is a resource (work order, goods issue by order, etc.) for this assembly, its requirement can be covered and therefore it is not broken down further. You can configure which resources should be considered. If you activate all possibilities, the net breakdown is performed; if nothing is activated, the gross breakdown is performed.

See: requirement coverage calculation

 

hmtoggle_plus1Example:

For net breakdown:

Order A consists of 100 item B

Inventory in warehouse 50 item B

Each item B consists of 5 item C

Requirement for item B: 100, but balance only 50

Requirement for item C: 250

 

For gross breakdown:

Order A consists of 100 item B

Inventory in warehouse 50 item B

Each item B consists of 5 item C

Requirement for item B: 100, but balance only 50

Requirement for item C: 500

PATH: MRP > MRP Wizard > Select a scenario > click the Edit button > Detail tab.

MRP_detail_Breakdown_repl

Window system_option_struktur.psr

 

Field

Description

Consider order multiples

Affects the minimum purchase quantity and the order multiple of an assembly. See Item master – Planning data

Minimum order quantity is always considered.

 

Affects the function requirement coverage calculation only. Only material and the sub-assemblies of the assembly which has order multiples are affected.

 

If a subsequent requirement originator is covered by order multiple of the predecessor, the subsequent pegging gets the same order proposal date.

See Example 3.

Note: Sub-assemblies and material requirement are combined in this case. In the Origin of requirement  function the requirement coverage is displayed in a note.

See Requirement coverage calculation

 

Example 1:

Assembly A (order multiple = 50)

    Assembly B ( = BOM of Assembly B, not order related)

 

Sales order 1 for "Assembly A" 30 pcs

Arising requirement:

"Assembly A" from sales order 1 = 30 pcs

"Assembly B" from sales order 1 = 30 pcs

 

Example 2:

Sales order 1 for "Assembly A" 30  pcs

Sales order 2 for "Assembly A" 5 pcs

Arising requirement:

"Assembly A" from sales order 1 = 30 pcs

"Assembly A" from sales order 2 = 5 pcs

"Assembly B" Total 35 pcs

The entry "Assembly B" is a sum, it can cover two sales orders because of the order multiple.

 

Example 3: Order proposal date

Assembly A, Minimum order quantity  is10, no stock, cycle time is 1 day.

Forecast 7. January: 4 pieces, order proposal: 6. January

Forecast 8. January: 4 pieces, order proposal: 6. January

Forecast 9. January: 4 pieces, order proposal: 8. January

 

Forecast 7: temporary 10 pieces are produced until January 6th. Forecast 8 is completely covered and Forecast 9 partly. From Forecasts 9, 2 pieces remain. More needs to be produced, accordingly a new date is calculated and displayed.

 

Note: refers to versions from beas9.1-004-058

 

Example 4:

With minimum order quantity and without order multiple:

Assembly A (Minimum order quantity = 50)

    Assembly B ( = BOM of Assembly B, not order related)

 

Sales order 1 for "Assembly A" 30  pcs

Sales order 2 for "Assembly A" 5 pcs

Arising requirement:

"Assembly A" from sales order 1 = 30 pcs

"Assembly A" from sales order 2 = 5 pcs

"Assembly B" Total 35 pcs

 

Example 5:

With minimum order quantity and without order multiple:

Sales order 1 for "Assembly A" 30  pcs

Sales order 2 for "Assembly A" 5 pcs

Arising requirement:

"Assembly A" from sales order 1 = 50 pcs

"Assembly A" from sales order 2 = 5 pcs

"Assembly B" from sales order 1= 50 pcs

"Assembly B" from sales order 2 = 5 pcs

 

No summary, because Assembly "B" is produced with minimum order quantity of 50 and covers sales order 1.

 

The date is also considered. For additional information, see Requirement coverage calculation

 

Attention: MRP2 - Resource planning: Summarized values are displayed as a forecast.

 

Consider goods receipt from production

Production receipts are taken into account if they are available at the requirement date. See Requirement coverage calculation.

Consideration of inflow in future

Number of days between the planned outflow and the planned receipt. Default setting is 999, which means that if the planned receipt is within 999 calendar days after the requirement day, it is taken into account.

Important: This flag only applies to items where "Breakdown" is different from "Order-related" items. Item breakdown.

See Requirement coverage calculation.

Production receipt reservation consider

Take into account receipt reservations only, order assignments are ignored. Only used for order-related items are affected.

Disabled: There is a 1 to 1 link between customer order and work order,  reservations are ignored.

Enabled: Order assignment is ignored, only receipt reservationsare considered.

Include warehouse stock

Inventory is taken into consideration for sub-assemblies.

Consider goods receipt from PO

Planned purchase receipts are taken into account, if they are available at the requirement date. Buffered and blocked purchase orders are not considered.

Demands for Purchase order and Production

If active, requests for purchase and production are considered. This option is displayed only, if Pegging and replenishment > Purchase > Purchase order and Details > Purchase > Request are activated.


Help URL: https://help.beascloud.com/beas202102/index.html?mrp_setup_aufloesung.htm