Predictive blanking of Oracle EBS MRP Modules

Predictive reduction of the Oracle EBS MRP module The definition of the predictive reduction is based on the original forecast, using the planned sales order to reduce the corresponding forecast quantity to get the current forecast. Current FORECAST = Original Forecast-Customer order. Method of forecasting the first class, which is automatically reduced when the order is planned, is the automatic reduction forecast when the sales order is planned; requires the plan manager to run in the foreground (mrp> setup > Plan manager); configuration file Mrp:consume Forecast = Yes; new sales order This type of reduction is applicable when a planned or planned sales order is changed.        Oracle recommends this method of automatic reduction, because, in this way, the reduction is only for new orders or changed orders, the old and new requirements are very clearly divided, can effectively avoid the historical orders mistakenly, excessive reduction forecast. Essence: Only records with process_status = 2 in Mrp_sales_order_updates are processed. In the second category, the reduction Plan manager has two effective forms when copying/merging/loading:

1. Foreground run (mrp> setup > Plan manager);
2. If the profile mrp:perform planning Manager Functions in Loads = Yes, it will replace the ability to perform all of the Plan manager's functions each time the copy/merge/Mount program is run.

When the plan manager is in effect (that is, the above 2 conditions satisfy at least one), a forecast reduction can be performed at the following two steps:

1. Reduction in copy/merge forecasts;
2. Flushes when the forecast is loaded into MDS.

The essence: Based on the forecast original quantity, for all orders in the Oe_order_lines_all, from the beginning of the reduction. The specific reduction logic and the first similarity.        In the third category, predictive set reduction is independent of the plan manager. Depending on the configuration file Mrp:consume fcst set summary settings, the object of the predictive set blanking may be all open order lines in Oe_order_lines_all (when set to Yes) or the order line status, take Mrp_sales_ All records in the Order_updates (when set to No).        The records captured in both cases are further limited by the demand start date on the forecast set undershoot request. Essence: After the prediction set flushes the request starts, it clears all the flushes of the current forecast set first, and then, based on the predicted original quantity, the range of requirements records determined by the configuration file Mrp:consume fcst set summary settings and request parameters, from scratch.        The specific reduction logic and the first similarity. In the process of formal use of MRP in enterprises, it is prudent to use predictive set reduction. Changing configuration file Mrp:consume FCST Set summary settings is not allowed without professional guidance. Base Set forecast set blanking options
1. The blanking box determines whether this prediction set allows for a reduction. This option is valid for all the blanking methods.         2. Exception update percentage The effect of abnormal demand is controlled by the maximum percentage of the original forecast that can be reduced by a single sales order. As an example, if you set the exception update percentage of a forecast set to 50%, add a three row forecast, and the original number of each row is 100, that means that each sales order line (LINE_ID) can have a maximum of 50 reduction per line forecast (100*50%):


3. Backward days, forward days are the number of working days that a forecast entry can be reduced from the date of the sales order schedule, behind, or forward forecast.        Non-working days are not counted.        When you define a forecast set, you can enter the number of days for backward and forward flushes, and the number of days that the forecast entry contains.        When a forecast date that exactly matches the sales order date is not found, or if the exact date is found but the quantity does not meet the sales order quantity, the reduction will first be moved behind the working day (backward) to find the predicted amount of the cut, and if the search fails, the reduction will move forward in the working day range (forward push). The following example, the forecast of the number of days and the number of days before the push is set to 5, the original forecast fell in 6 working days, the quantity is 20, if there is a sales order, the date of shipment is planned at 8th, the number of 100, the Plan manager will be 8th, 4th, 1th, 11th, 12th, the order of the number of Finally, only the forecast of number 15th is left:
Answer:
Configuration file Mrp:compute Sales order changes indicates whether or not to calculate and use the demand to perform forecast consumption and to track sales order information. The available values are as follows:

• Yes-calculates and uses sales order information.
• No-sales order information is not calculated and used.

When this profile is set to No, the new planned sales order will not be reduced as expected.        When you restore the profile options setting to Yes, the Plan manager flushes the file to "no" as all sales orders are scheduled. This configuration file controls the processing of the records that the Plan manager uses for process_status = 2 (Pending) in Mrp_so-lines-temp: Once the sales order is scheduled, it is inserted into mrp_so_lines_temp, at which point Process_status = 2 (pending); When the configuration file is set to No, the Schedule manager does not process them, records remain in the pending state, and when the configuration file is set to Yes, the Plan manager crawls the items to be processed in the mrp_so-lines-temp and inserts them into the Mrp_sales_order_ Updates and update process_status = 5 (SUCCEEDED) in temp. Mrp:consume SCST Set Summary

• Yes-order lines that have only scheduled shipping dates that meet the parameters and have not yet been shipped can be taken to reduce the forecast set.
• No-the order lines that meet the request parameters for all planned shipping dates can be taken to reduce the forecast set.

Depending on the configuration file Mrp:consume fcst set summary settings, the object of the predictive set blanking may be all open order lines in Oe_order_lines_all (when set to Yes) or the order line status, take Mrp_sales_        All records in the Orders_updates (when set to No). This configuration file is only valid for forecast set reduction and is not valid for predictive auto-flushes through the plan manager.         Mrp:old Sales orders Cutoff days old Sales order Cutoff days This profile is intended to counter the demand for orders that were updated during the unplanned suspension of the plan manager, preventing closed expired orders from continuing to reduce the forecast. The predicted reduction is directly related to the Mrp_sales_order_updates table, where the CURRENT_AVAILABE_TO_MRP label is Y or N, which determines whether the order line participates in the forecast reduction.        If I have an order, its shipping occurs during the Schedule manager pause, then after restarting the Plan manager, the order is in the Mrp_sales_order_updates table, or the status of Y (if the Plan manager continues to run, the normal order, the registration is Y, the shipment closes after N). Old Sales order Cutoff days This configuration file takes effect on orders lines that have a status of Y in this table, and avoids expired orders that have been closed and continue to make forecasts.
The steps to test the effect are as follows: Set the old Sales order Cutoff days to empty (for an infinite number of nights), close the Schedule manager, register a new order and change the confirmation, reopen the Plan manager and test the reduction, and you will still be able to reduce the forecast by the actual closed orders. Principles of the blanking logic database
The main steps are as follows:

1. Once the sales order is scheduled, the mrp_so_lines_temp is inserted, at this point process_status = 2 (Pending)
2. The Plan manager verifies that the configuration file Mrp:compute the settings for Sales Order changes, and if set to Yes, the Plan manager crawls all the pending entries in the Mrp_so_lines_temp and inserts them into the Mrp_sales_order_ Updates and update process_status = 5 (succeeded) in temp
3. Initial state of the record inserted mrp_sales_order_updates Process_status = 2 (Pending)
4. The Plan manager verifies the settings of the configuration file Mrp:consume Forecast, and if configured, the Schedule manager flushes the entries that are pending in Mrp_sales_order_updates and updates them based on the flushing record Mrp_forecast_ Updates (Forecast reduction schedule), and update process_status = 5 (succeeded) in Mrp_sales_order_updates

The principle of flushing and reducing

1. Forecast flushes are made within the forecast set, and a plan for a sales order line can simultaneously reduce the number of forecast sets that contain this item forecast entry, and a sales order line must not have a total reduction in a forecast set that is greater than the planned shipments for this order line.
2. Priority reduction for the same requirement classification. After a sales order is planned, the forecast reduction process prioritizes forecasts with the same requirements classification. If the forecast reduction process does not find predictions for the same demand classification, it will reduce the entry without the requirement classification. If the sales order does not have an associated requirement classification, the forecast consumption process attempts to first reduce the forecast entry associated with the organization's default requirements classification, and then flushes the entries that have not yet been defined for the requirement classification.
3. The forecast demand date must fall within the time period that is greater than (the order line schedule churn date-backward days), less than (order line planned shipping date + forward days) to be matched to the sales order line.

The blanking logic assumes that the predictive set FCS contains the predicted FC01 and forecast FC02, and that two predictions contain the same item A. Here's how to match a sales order line with a forecast entry when you perform a forecast reduction:

1. Sort the sales order lines that need to be reduced by the planned shipping date from small to large;
2. The forecast entries of item A in the forecast concentration are sorted from small to large according to the requirement date;
3. In the forecast entry for item A, a forecast entry of one or more lines that predicts the demand date from the planned shipment date of this sales order line;
4. If there is only one row, use this line to reduce;
5. If there is more than one line, the alphabetical order of the predicted names is sorted from small to large, and then minus.

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

Predictive blanking of Oracle EBS MRP Modules