MRP MRP wizard Detail Breakdown replenishment - robinfeng/beashelp GitHub Wiki
展开补货
Navigation: MRP > MRP Wizard > Detail: Breakdown replenishment No contents entries on this page Contents Material requirement planning MRP wizard Planning scenarios Detail Pegging and replenishment Breakdown replenishment Inventory Forecast Resources Computation View Authorizations
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 with this and therefore it is not broken down further. You can configure here 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_plus1 Example: 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
Field Meaning Consider order multiples hmtoggle_plus1 Determines, whether at breakdown of assemblies, order multiples are to be considered
Affects minimum purchase quantity and order multiple of an assembly.See Item master - Planning data
Minimum order quantity is always considered
Affects only the function requirement coverage calculation Only material is affected and the sub-assemblies of the assembly which has order multiples.
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 function "Origin of requirement" using a note the requirement coverage s displayed. 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 10, no stock, cycle time 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, 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, 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
Consider goods receipt from production Production receipts are taken into account, if there are available at the requirement date.See Requirement coverage calculation Consideration of inflow in future Number of days between planned outflow and planned receipt. Default setting: 999. That means, if the planned receipt is within 999 calendar days after the requirement day, it will be taken into account. See Requirement coverage calculation Consider production receipt reservations? Only order related items affected. Deactivate: There is only a 1:1-linkage between customer order and work order, reservations are ignored. Activated: order assignment is ignored, only receipt reservations are considered Include warehouse stock Inventory is taken into consideration. Consider goods receipt from PO Planned purchase receipts are taken into account, if there are available at the requirement date. Buffered and blocked purchase orders are not considered. Consider requests for purchase and production hmtoggle_plus1 Consider purchase and production requests If active, requests for purchase and production are considered. This option is displayed only, if "Pegging and replenishment" - "Purchase" - "Purchase order" was activated. To consider this switch, additionally, under "Details - Purchase - Request" are required to be activated.
返回 主页