MRP MRP wizard Detail Pegging and replenishment - robinfeng/beashelp GitHub Wiki
固定和补货
Navigation: MRP > MRP Wizard > Detail: Pegging and 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
Pegging and replenishment are split into:
Warehouse Production Sales Purchase Computation type
Warehouse Field Meaning Inventory Inventory is taken into consideration Minimum Inventory If this option is activated, the minimum inventory is taken into consideration. A request due to the minimum stock is always carried out to the presence. If requirements exist in the past, then these are put into the presence after minimum stock examination has been carried out . hmtoggle_plus1 Remark At the balance calculation the minimum stock is always subtracted, thereby it is recognizable in the time line at which point the minimum stock is underrun (balance < 0). If the balance becomes negative due to future requirements, then the minimum stock has to be increased. An order is suggested if the minimum stock is underrun in the week view in presence. If a minimum stock request is active, you already have reacted too late, because goods cannot be reordered on time. Breakdown minimum inventory If this option is activated, the minimum stock requirements are broken down. An assembly is broken down into its components. In this case the requirements always date from the past. Inventory transfer request Enable to manage inventory transfer request through the MRP. Each inventory transfer request generates 2 entries in the MRP, first is similar to a sales order in the source warehouse and the second entry is like a purchase order for the target warehouse.
Production Field Meaning Production receipt hmtoggle_plus1 Consideration of planned receipt from production This option refers to balance calculation. If enabled (as default) planned good receipts from production and negative BOM items are taken into consideration. The same applies for all other kinds of inflow and outflow.
The warehouse stored in the work order or in the negative BOM is used as receipt If in configuration wizard a receipt warehouse is stored, this will be used as reference. This applies only, if some special warehouses are to be considered. See Planning scenarios - warehouse Plannings scenarios - detail - warehouse filter Configuration wizard - Posting Production issue If this option is activated, planned production issues (BOM) are taken into account. Negative BOM items are not considered. Consider blocked production orders Standard: no. Per default blocked production orders are not taken into consideration in the MRP Consider planned orders Standard: yes Planned production orders are taken into consideration in the MRP, even if they are blocked Consider production requests standard: yes. If this option is enabled, production requests are considered, which have been created by order recommendation. Breakdown subassemblies hmtoggle_plus1 How to breakdown sub-assemblies, whose requirement is not covered If subassemblies are not covered by warehouse, production or purchase order receipts, these are further broken down. Here you can select, whether peggings are grouped by day, week or month. Grouping peggings, cuts the connection to the actual pegging. hmtoggle_plus1 Example: Work order with assembly A, where the deposited bill includes assembly B In the master data material C is assigned to assembly B
A (assembly) | - B (assembly) | - C (material)
beas checks, whether there is enough stock for assembly B or if there is a scheduled receipt (requirement coverage calculation). If nothing is found, the assembly B is broken down, thereby determining the requirement for material C, though there is no production order. Here, material C is firmly linked to the pegging (production order, assembly A).
Sales Field Meaning Sales order If this option is activated, sales orders are taken into consideration under the following conditions: • Order line has not been closed • Open quantity >0 • Approved (SBO – Customer order – „Logistics“ tab, „approved“ enabled • It is an assembly or the purchase part is included in item area, defined in „Item“ • Delivery date within the period to be computed Customer order reserve invoice hmtoggle_plus1 If this option is activated, customer order reserve invoice are taken into consideration. If you deactivate these options, sales orders for which a customer order reserve invoice was created are no longer considered, because SAP closes the sales order. In this case, the requirement originator is now the customer order reserve invoice, not the customer order. In order for this to be included in the MRP as requirement originator, this option must be activated.
The sequence therefore changes in SAP from sales order -> delivery note to sales order -> invoice -> delivery note Option is disabled by default. Blanket agreement hmtoggle_plus1 Activate, to consider blanket agreements Only types “Specific” and with status “Approved” are considered.
The requirement is not included to the balance calculation, but displayed in grey. Only after a demand was called off by a sales order, the requirement is considered in balance.
If the sum of requirements of sales order linked to a specific blanket agreement is lower than quantity in the blanket agreement itself, beas creates order recommendations for the difference quantity.
Important: In the blanket agreement in row details you need to define the date or the recurring period. Also unapproved customer orders If enabled, customer orders are taken into account, which have not been approved (ordr.confirmed=‘N‘) To release: customer order - tab "logistics" – „approve“ Consider calculation hmtoggle_plus1 Considering pre-calculations in computation If this option is activated, calculations are taken into consideration. If a calculation is mapped to a customer order item, the material requirement for the customer order is not based on the master data but on the stored calculations. Calculations are always order related, i.e. the structure is always broken down completely. Replenishment elements in the inter stages are not taken into account, as well as existing stock.
Lead time is not calculated in the calculation. Requirement dates do not take into account any times for processing indicated in the calculation.
Assemblies (storage related as well as order related) are broken down completely. As assembly quantity, the same quantity is stored in production inflow and outflow. If a work order is created, the order related assemblies are not transferred to the work order.
Consider SCM hmtoggle_plus1 Determine, if SCM is considered Option visible only, if the View "BEAS_SCM_MRP" is existing. This is the case, if the View is installed for example when activating the SCM-solution.
Configuration of the View Field Type Description itemcode nvarchar(30) Item cardcode nvarchar(30) Customer scm_bo_project nvarchar(20) Project code scm_numatcard nvarchar(20) Reference to sales order number or Purchase order number scm_sal_pur nvarchar(3) Sales order (= "sal") or Purchase (="pur") Determines, dealing with a purchase or a sales order. scm_date nvarchar(20) Delivery date. Configuration: yyyy/mm/dd scm_quantity decimal(19,8) Quantity scm_bo nvarchar(25) Sales order number or Purchase order number scm_bo_pos nvarchar(10) Saler order or purchase order row
Stored entries are treated as sales orders. For further information please see SCM-Documentation. Breakdown sub-assemblies hmtoggle_plus1 Determines, whether sub-assemblies are broken down If this option is activated (Default), sub-assemblies from sales area are broken down.
Example Assembly A contain Sub-assembly B contains Material C
If the switch is enabled, following requirement is displayed: Assembly A Assembly B Material C
If the switch is enabled, following requirement is displayed: Assembly A Assembly B
In this case, Assembly B is no further broken down, Material C is not displayed as requirement.
Example of use: Disable the switch if you do not manufacture everything on your own. That means, on the moment of scheduling you decide, whether to produce or to purchase.
Further information See: Requirement coverage calculation
Purchase Field Meaning Purchase If you activate this option, purchase orders are taken into consideration. This makes consistent balance calculation possible. If this option is deactivated, this is not possible Evaluate blocked Pur.Orders If this option is activated, blocked purchase orders are taken into consideration, i.e. they are included in the balance calculation Purchase quotations show If enabled, purchase quotations are only displayed . Usually, this is not needed, because purchase quotations are also displayed in the window on the right (currently planned receipts) Purchase quotations valuate Can only be selected, if the upper option (display) is enabled. Activate this option to consider purchase quotations in balance calculation. This makes sense, if purchase quotations are used for other purposes, for example for planned receipts. Blanket agreement hmtoggle_plus1 Activate, to consider blanket agreements Only types “Specific” and with status “Approved” are considered.
The requirement is not included to the balance calculation, but displayed in grey. Only after a demand was called off by a sales order, the requirement is considered in balance.
Important: In the blanket agreement in row details you need to define the date or the recurring period. Display Draft Pur.Order If this option is activated, draft purchase orders are displayed in the MRP run. Evaluate Draft Pur.Order Can only be selected, if the upper option (display) is enabled. If this option is activated, buffered purchase orders are taken into consideration, i.e. they are included in the balance calculation. Use this, if drafted purchase orders are used for planned receipts. Recurring orders Enable, to support the SAP Business One function "recurring transactions" in MRP Purchase order reserve invoice If this option is activated, reserve order invoices are taken into consideration. This option is activated by default. Reserve invoices are displayed in MRP as long as not delivered or closed. Follow up manual returns If this option is activated, purchasing returns created without a reference to a goods receipt are displayed as a negative or positive inflow (selection). Use: If goods are returns and a replacement delivery is expected without a new purchase order being created, a manual return can be created without a reference to the goods receipt. As soon as the delivery takes place, the return is closed. Important: manual return are considered in the requirement coverage calculation. Display SCM order schedule
Only available with installed SCM Module! If only this option is selected, order schedule is displayed in gray, the calculated balance is not affected. If option is enabled, order schedule is displayed in gray, the calculated balance is not affected. See consider SCM Valuate SCM order schedule Only available with installed SCM Module! If this option is enabled, the planning run behaves just like forSAP Business One orders. Balance calculation takes into account the order schedule.See consider SCM Purchase requests If this option is activated, purchase requests and production requests are taken into consideration.
Computation type Field Meaning Sum peggings hmtoggle_plus1 Allows the summation of peggings Allows a) Compression of the data sets to the most necessary b) Reducing the calculation effort See Computation time
Detail Every pegging (forecast, order, customer order etc.) is displayed separately. This setting makes sense, if purchases are issued ordered related or if it is goods of high value. Day/week/month/sum The peggings are accumulated corresponding to chosen the time period. it does not become the pegging then in the purchase order proposal list but only this one accumulated e.g. need per day - to and quantity issued per day/week/month displayed. If no detailed declaration of the pegging or resource is necessary and one has to deal with high amounts of data, that way of accumulation is recommended. The calculation time is shortened, the view is more clear. This setting also can be done in the item master.
See Item master - Planning Calculate lead time for assembly hmtoggle_plus1 When active, the lead time is calculated Resource scheduling (MRP2) is based on lead time calculation. Therefore "Calculate lead time for assembly" must be activated if resource scheduling is required.
If enabled, lead time is calculated using the integrated capacity planning tool by means of backward scheduling on basis of the routing deposited in the item data. The calculation is carried out by means of backward scheduling simulation. Existing capacities are not taken into account. If a material is assigned to an operation sequence directly, then the start date of the operation sequence is assigned (time: start of processing) Depending on the depth of the production structure and the accuracy of the forecast, the computation can take very much time. Often it is sufficient to have a good estimate of the requirements. Disable: calculation time is shortened significantly, the item lead time serves as a reference. The function "Resources - Activate resource planning is disabled in this case automatically.
Note Lead time means production time of the assembly without consideration of sub-assemblies lead times.
Example Assembly A contains assembly B Assembly A has a lead time of 10 work days Assembly B has a lead time of 5 work days
Calculation on this case: Date of finished production for A and B = requirement date Start date A = requirement date - lead time 10 work days Start date B = requirement date - lead time 5 work days
See: calculate resources Consider link to operations hmtoggle_plus1 Consider links to routings Sales documents If this feature is active, (default), calculating the requirement date, links between operation sequence and BOM item are considered. If function is inactive, links are not considered, the calculated manufacturing start date is used always as requirement date of the BOM item. Disabling the functions accelerates the computation a little.
Production Bom item: If active, for computing the requirement date the start date of the assigned operation is used, otherwise the start time of the work order position. If this was not set, the delivery date is used.
See Computation of order recommendation date
Calculate resources Only visible, if "Calculate lead time for assemblies" has been deactivated. This gives direct access to the function "calculate resources" to calculate e.g. the complete material requirements and complete resource requirement in advance. The necessary resources (material and tools) are calculated on the basis of the the production lot size and stored accumulated. This calculation type is much faster than the upper one, it provides a good estimate.
返回 主页