Nick,
For the 2nd worrisome part - consider applying a pretty healthy "Reschedule Out Time (days) Delta" to all of your MRP parts. (Found in Part Entry on Plant/Detail subtab.)
If you put (say) 15 in this field, you won't be pestered with 'push out' messages unless the supply order is coming in MORE than 15 days earlier than the demand date MRP associates it with.
You can assign these delta's by Part Class (if you use multiple part classes) - so expensive stuff (that could hurt your inventory turns and cash flow) can be assigned a smaller "out" delta than cheap stuff.
VERY dumb of Vantage not to let this be mass inherited by ABC codes - as that is what most people are used to dealing with....
Part Class is a Vantage oddity that we are finding has little practical use as every potential use we've considered ends up being at cross purposes to another equally compelling potential use.
I don't recall if the 'days' are company calendar working days (10 working days beign two normal weeks) or pure calendar days (14 days being two weeks).
The "in" delta has its uses too to reduce noise. For parts that you truly by order for order you probably couldn't tolerate having a part (Job or PO scheduled receipt) coming in even 1 day late to the required date.
However, for high repetive use parts that you keep in inventory (by setting some appropriate Min O/H and/or Safety Stock), this is a field that can allow you to dip into safety stock (and/or go below Min for however many days you feel is acceptable before becoming dangerous) without resulting in a cascade of daily changing (because of the high repetitive new demand nature of the part's activity patterns) "pull in" suggestions.
Example: If your Min and/or Safety is intended to try and keep a part lead time and activity calculated one month typical use inventory buffer available, you're likely getting clobbered daily by messages to constantly incrementally pull in jobs/POs by a day or two each day to stay above your set time phase based Min/Safety Qty.
If you set that "In" delta to say, two weeks, you can dip into the Min/Safety (which is what you are stocking it for anyway!) pretty significantly before your planner/buyers will start getting expedite messages.
The majority of other systems I've used didn't have any MRP timing fudge factor delta capabilities. The few that did only had a single value that applied to both In and Out acceptable deltas (and in the real world, effective In and Out acceptable deltas are almost never the same number fo days).
It's one of a handful of Vantage features that I applaud them for... Even though MRP is one of the dumbest concepts I've ever seen (too simple for the real world), at least this helps deaden its inherent non-vaue-added messaging jitters.
I would DEFINITELY experiment with deltas... I don't recall if they really worked on 305 - but I know they do on 405a! (Thank goodness!)
Rob
For the 2nd worrisome part - consider applying a pretty healthy "Reschedule Out Time (days) Delta" to all of your MRP parts. (Found in Part Entry on Plant/Detail subtab.)
If you put (say) 15 in this field, you won't be pestered with 'push out' messages unless the supply order is coming in MORE than 15 days earlier than the demand date MRP associates it with.
You can assign these delta's by Part Class (if you use multiple part classes) - so expensive stuff (that could hurt your inventory turns and cash flow) can be assigned a smaller "out" delta than cheap stuff.
VERY dumb of Vantage not to let this be mass inherited by ABC codes - as that is what most people are used to dealing with....
Part Class is a Vantage oddity that we are finding has little practical use as every potential use we've considered ends up being at cross purposes to another equally compelling potential use.
I don't recall if the 'days' are company calendar working days (10 working days beign two normal weeks) or pure calendar days (14 days being two weeks).
The "in" delta has its uses too to reduce noise. For parts that you truly by order for order you probably couldn't tolerate having a part (Job or PO scheduled receipt) coming in even 1 day late to the required date.
However, for high repetive use parts that you keep in inventory (by setting some appropriate Min O/H and/or Safety Stock), this is a field that can allow you to dip into safety stock (and/or go below Min for however many days you feel is acceptable before becoming dangerous) without resulting in a cascade of daily changing (because of the high repetitive new demand nature of the part's activity patterns) "pull in" suggestions.
Example: If your Min and/or Safety is intended to try and keep a part lead time and activity calculated one month typical use inventory buffer available, you're likely getting clobbered daily by messages to constantly incrementally pull in jobs/POs by a day or two each day to stay above your set time phase based Min/Safety Qty.
If you set that "In" delta to say, two weeks, you can dip into the Min/Safety (which is what you are stocking it for anyway!) pretty significantly before your planner/buyers will start getting expedite messages.
The majority of other systems I've used didn't have any MRP timing fudge factor delta capabilities. The few that did only had a single value that applied to both In and Out acceptable deltas (and in the real world, effective In and Out acceptable deltas are almost never the same number fo days).
It's one of a handful of Vantage features that I applaud them for... Even though MRP is one of the dumbest concepts I've ever seen (too simple for the real world), at least this helps deaden its inherent non-vaue-added messaging jitters.
I would DEFINITELY experiment with deltas... I don't recall if they really worked on 305 - but I know they do on 405a! (Thank goodness!)
Rob
--- On Wed, 1/28/09, nmtaylor1969 <n.taylor@...> wrote:
From: nmtaylor1969 <n.taylor@...>
Subject: [Vantage] Re: 8.03 Time Phase "Leadtime" source for scheduled PO receipts
To: vantage@yahoogroups.com
Date: Wednesday, January 28, 2009, 1:20 AM
Hi Rob,
The first paragraph makes sense, and appears to be an improvement
over our functionality.
The second is rather more of a worry however. We still spend far to
much time playing "chase the suggestion" and this can only serve to
produce yet more suggestion noise.
As always, its down to very careful management of the system by the
planners if disaster and chaos are to be avoided! :o(
Thanks,
Nick
--- In vantage@yahoogroups .com, Robert Brown <robertb_versa@ ...>
wrote:
>
> Nick,
>
> Very fuzzy today & can't recall if I answered your purch part MRP
question...
>
> I can't speak to 305 (just too brief a time on it) but on 403-405
MRP uses the MRP lead time offset when suggesting new POs UNLESS you
have specified a default vendor in PartPlant AND the part-vendor has
been set up with a supplier price list record that contains a
different vendor specific lead time. This is for New PO suggestions.
>
> Once you have a PO out there (that MRP will bother you to death
daily to pull in/push out, increase/decrease each release qty as
demand conditions change daily) lead time is no longer part of the
change suggestion logic. Unless you lock a line/release date and/or
qty it assumes you can move the date at will.
>
> Make sense?
>
> Rob
>
> --- On Tue, 1/27/09, nmtaylor1969 <n.taylor@.. .> wrote:
> From: nmtaylor1969 <n.taylor@.. .>
> Subject: [Vantage] Re: 8.03 Time Phase "Leadtime" source for
scheduled PO receipts
> To: vantage@yahoogroups .com
> Date: Tuesday, January 27, 2009, 12:53 AM
>
>
>
>
>
>
>
>
>
>
>
> It sounds like you have better functionality than us
Rob...!
>
>
>
> Do you know if the MRP lead time has any effect on purchased
>
> materials... ?
>
>
>
> I can't see what this actually does...? Obviously I am losing the
>
> plot...!
>
>
>
> Thanks,
>
>
>
> Nick
>
>
>
> --- In vantage@yahoogroups .com, Robert Brown <robertb_versa@ ...>
>
> wrote:
>
> >
>
> > Nick,
>
> >
>
> > You jogged my memory of our very brief initial pilot time on 305
&
>
> I found an old screen print of time phase that does indeed show the
>
> L/T column devoid of any values (except for initial o/h).
>
> >
>
> > On 405(a) the column is populated and some trial & error testing
in
>
> an offline db seems to indicate the value (for POs) comes from the
>
> supplier price list (if one exists) for the PO line.
>
> >
>
> > Changing that supplier price list value AFTER the line is created
>
> doesn't change the resulting time phase displayed L/T - so I
presume
>
> it is indeed imbedded in the PO (but for the life of me I can't
find
>
> a PO related table field that holds the info - not uncommon as I
>
> suspect there are a LOT of unpublished PO related table fields
based
>
> on PO behavior & significant BO method behavior changes that
occurred
>
> between 305 & 403 - and then again between 404 & 405).
>
> >
>
> > ...Thanks for trying!
>
> >
>
> > I guess I shouldn't count on it as being consistent as, for all I
>
> know, behavior will change when we eventually upgrade to 407.
>
> >
>
> > Rob
>
> >
>
> > --- On Mon, 1/26/09, nmtaylor1969 <n.taylor@ .> wrote:
>
> >
>
> > From: nmtaylor1969 <n.taylor@ .>
>
> > Subject: [Vantage] Re: 8.03 Time Phase "Leadtime" source for
>
> scheduled PO receipts
>
> > To: vantage@yahoogroups .com
>
> > Date: Monday, January 26, 2009, 3:05 AM
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > Rob,
>
> >
>
> > I am confused by the contents of this field. As you know I can
>
> > extract my entire time phase via service connect and subsequently
>
> > interrogate it, and I dont see any evidence to suggest that it
>
> picks
>
> > up a lead time from the supplier price list data or anywhere for
>
> that
>
> > matter. In 8.03.305 this field sets the "order by" date in the
>
> buyer
>
> > workbench, and appears to do nothing else. The time phase then
>
> shows
>
> > the MRP lead time in the lead time field at the top of the time
>
> phase
>
> > screen, but the lead field itself shows as 0.
>
> >
>
> > Actually, the lead field is 0 for my entire time phase other then
>
> one
>
> > entry!!! I dont understand.. ..????
>
> >
>
> > Regards,
>
> >
>
> > Nick
>
> >
>
> > --- In vantage@yahoogroups .com, Robert Brown
<robertb_versa@ ...>
>
> > wrote:
>
> > >
>
> > > Time Phase displays a L/T for scheduled receipts.
>
> > >
>
> > > The data dictionary explains (hopefully accurately) where this
>
> L/T
>
> > comes from for o/h inventory and Jobs (scheduled receipts and
>
> > requirements) .
>
> > >
>
> > > It does NOT explain at all where it comes from for open
Scheduled
>
> > PO receipts.
>
> > >
>
> > > It appears to me that is coming from the specific PO line
(likely
>
> > captured from the appropriate supplier price list in effect @ the
>
> > time of PO line creation - and if no supplier price list exists -
>
> > from the PartPlant MRP LT) - but none of the public tables
related
>
> to
>
> > POs seem to have a field associated with a captured L/T.
>
> > >
>
> > > Does anyone out there have any definitive insight as to where
>
> this
>
> > comes from for POs (and, if it is a PO 'imbedded' & constant
value
>
> > captured at the time of line creation, if there IS a public
>
> > table/field where the value is held)?
>
> > >
>
> > > Any insight would be appreciated.
>
> > >
>
> > > Thanks
>
> > >
>
> > > Rob Brown
>
> > >
>
> >
>