0018053: Suggested Work Requirement not generated by MRP

Openbravo Issue Tracking System - Openbravo ERP

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0018053

Openbravo ERP

06. Material requirement planning (MRP)

public

2011-07-21 12:44

2015-05-13 13:41

Reporter

andreaferaco

Assigned To

mirurita

Priority

normal

Severity

major

Reproducibility

always

Status

closed

Resolution

duplicate

Platform

OS Version

Professional Appliance

Product Version

Target Version

Fixed in Version

Merge Request Status

Review Assigned To

OBNetwork customer

Web browser

Mozilla Firefox

Modules

Core

Support ticket

Regression level

Regression date

Regression introduced in release

Regression introduced by commit

Triggers an Emergency Pack

Summary

0018053: Suggested Work Requirement not generated by MRP

Description

When MRP is processed for a product configured with a minimum stock, the application does not suggest any work requirement to re-establish minimum stock.

Steps To Reproduce

1) Create a product P flagged as "production" and linked to a process plan.
2) Set minimum stock for this product P to 25 units
3) From manufacturing plan window run the process "Process Manufacturing Plan"
4) When the process is completed just two records are inserted in the table MRP_RUN_PRODUCTIONLINE:
|A|Minimum Stock|-25
|A|Stock|0
No suggested work requirement records have been created. Actually it was expected at least a third record:
|A|Suggested Work Requirement|25
5) We have noticed that if the "Process Manufacturing Plan" is executed a second time without deleting existing records in MRP_RUN_PRODUCTIONLINE, the application correctly creates the records for the suggested work requirements.

The application behaviour after the second execution is consistent with the expected behaviour, however this behaviour was expected immediately after the first execution.

We analysed the code and realised that the stored procedure "mrp_run_initialize" inserts in MRP_RUN_PRODUCTIONLINE just the lines of stock (ST) and minimum stock (MS) having the flag "isexploded" = 'Y'.
Because of this condition, the stored procedure "mrp_run_explode", invoked after "mrp_run_initialize", excludes those records, and therefore it does not generate any Suggested Work Requirement because of the Minimum Stock.

When the procedure is run the second time, the stored procedure "mrp_production_run" executes this SQL statement before invoking the other procedures:

UPDATE MRP_RUN_PRODUCTIONLINE SET isexploded = 'N' WHERE MRP_RUN_PRODUCTION_ID = v_Record_ID AND qty <0 AND INOUTTRXTYPE <> 'WR';

You can see that it sets to N the flag isexploded, therefore even if "mrp_run_initialize" skips the product P because already created in the table MRP_RUN_PRODUCTIONLINE, however the "mrp_run_explode" takes it into account and correctly generates the Suggested Work Requirement.

We tried to modify the "mrp_run_initialize" so to take the record related to minimum stock (MS) at the first execution, but the procedure raises an exception (it tries to fill a null value in the planneddate field).

Proposed Solution

Additional Information