Thanks Scott, Jacopo.
I agree with Scott and Si. Be it with these secas or with the MRP, a
requirement should be created when ATP + requirements goes below minimum
stock.
Scott Gray escribió:
> Thanks for the info Jacopo,
>
> My personal preference would be if ATP + requirements goes below minim
Thanks for the info Jacopo,
My personal preference would be if ATP + requirements goes below minimum
then create another requirement
Regards
Scott
On 28/06/07, Jacopo Cappellato <[EMAIL PROTECTED]> wrote:
I think that the last comment on that issue (by Si Chen) perfectly
summarize our differe
I think that the last comment on that issue (by Si Chen) perfectly
summarize our different vision on this subject:
Si: "Jacopo, I just noticed I recommended the opposite of what you
mentioned! The reason is because PRODRQM_STOCK_ATP only creates
requirements the first time a product's ATP fall
Scott,
I think that all is caused by a different vision Si and I have on this
subject... Si is more oriented on the last approach, I guess.
For some details you can have a look at:
https://issues.apache.org/jira/browse/OFBIZ-653
but I'm sure there is another Jira issue around.
Jacopo
Scot
Hi Jacopo
I have to agree the last one doesn't make any sense to me, do you know why
we've kept it?
Regards
Scott
On 28/06/07, Jacopo Cappellato <[EMAIL PROTECTED]> wrote:
Very quickly:
PRODQM_STOCK_ATP: when ATP quantity goes down the
ProductFacility.minimumStock --> a requirement is create
Very quickly:
PRODQM_STOCK_ATP: when ATP quantity goes down the
ProductFacility.minimumStock --> a requirement is created
PRODQM_STOCK_QOH: when QOH quantity goes down the
ProductFacility.minimumStock --> a requirement is created
The PRODQM_ATP has a different approach:
when ATP quantity g
What is the difference between these scheduling types?
Thanks,
--
Daniel
