Since my information so far is that only the Release 1 creation is buried so deep, I can use a more conventional method to set it on additional release... but so far in my testing this morning that isn't happening.
I could always take out the 'ComXRef.Key3 = "1"' line to make it apply to any release.
I don't know a whole lot about actual programming, and to me this seems like a dangerous way to go about things... I'd like to limit its use if possible.
Thanks!
Ernie Lowell
Diba Industries
I could always take out the 'ComXRef.Key3 = "1"' line to make it apply to any release.
I don't know a whole lot about actual programming, and to me this seems like a dangerous way to go about things... I'd like to limit its use if possible.
Thanks!
Ernie Lowell
Diba Industries
--- In vantage@yahoogroups.com, Miguel Santillan <msantillan@...> wrote:
>
> What happens if you have two releases.
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Elizabeth
> Sent: Friday, August 02, 2013 5:53 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: PO Suggestion Logic Guru Wanted
>
>
>
> Thank you all for the help!
>
> We mostly use PO Suggestions to create new PO lines (MRP runs every night), so written a Data Directive BPM on the PODetail table to automatically lock the qty on all new PO lines thusly:
>
> Condition: where ttPODetail.RowMod = 'A'
> Action:
>
> for each ttPODetail no-lock.
>
> CREATE ComXRef.
> Assign ComXRef.Company = 'DI'
> ComXRef.File = 'PORel_Mapping'
> ComXRef.Key1 = string(ttPODetail.PONUM)
> ComXRef.Key2 = string(ttPODetail.POLine)
> ComXRef.Key3 = "1"
> ComXRef.foreignKey1 = 'no'
> ComXRef.ForeignKey2 = 'Yes'.
>
> end.
>
> In the test environment, it appears to work swimmingly (enabling the Lock Qty checkbox on PORelease 1) both for manually created PO lines as well as those coming from Generate PO Suggestions.
>
> Am I actively seeking problems by using such a blunt instrument as CREATE this way?
>
> Thanks again for your help,
>
> Ernie Lowell
> Diba Industries
>
> --- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>, "bw2868bond" <bwalker@<mailto:bwalker@>> wrote:
> >
> > COMXref table
> >
> > COMxref.file = "PORel_Mapping"
> > COMxref.Key1 = string(ttporel.PONum)
> > COMxref.Key2 = string(ttporel.POLine)
> > COMxref.Key3 = string(ttporel.PORelNum)
> > COMxref.foreignKey1 = "No" */ Lock Date
> > COMxref.foreignKey2 = "Yes" */Lock Qty
> >
> >
> > --- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>, "Elizabeth" <gracefulthreads@> wrote:
> > >
> > > After finding that in the manual and going over the Lock Qty with my purchasing crew, I'm now using the DMT to set that enabled on all open PO Releases.
> > >
> > > So far go good...
> > >
> > > but then I went to see about creating a BPM to set it automatically when the PO "approved" status changes to true... THERE IS NO POREL.LOCKQTY FIELD IN THE DATABASE! There's also no LockDate field.
> > >
> > > It's there in the DMT, and the client Field Help shows it there in big bold black and blue.
> > >
> > > I guess this is why they pay us the big bucks.
> > >
> > > Also in the field help, the "external" checkbox is enabled. Does this mean it's stored somewhere else?
> > >
> > > Is there another, more sinister way to enable it automagically?
> > >
> > > Ernie Lowell
> > > Diba Industries
> > >
> > > --- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>, "Richard Sirow" <rick@> wrote:
> > > >
> > > > Ernie,
> > > >
> > > >
> > > >
> > > > I check the Lock Qty checkbox (on the Release Detail tab in PO Entry) to
> > > > stop this annoying problem on vendors where this happens. A BPM could
> > > > probably be written to do this, as it is a pain going through every release
> > > > in a PO.
> > > >
> > > >
> > > >
> > > > Richard L. Sirow, President
> > > >
> > > > Independent Components Corp.
> > > >
> > > > www.iccparts.com<http://www.iccparts.com>
> > > >
> > > > rick@
> > > >
> > > >
> > > >
> > > > From: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf Of
> > > > Elizabeth
> > > > Sent: Thursday, August 01, 2013 12:20 PM
> > > > To: vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
> > > > Subject: [Vantage] PO Suggestion Logic Guru Wanted
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > I've read the MRP Tech Ref manual (what an edge-of-the-seat page-turner THAT
> > > > was), and I don't understand the logic to New vs Change PO Suggestions (I am
> > > > assuming there is some logic, but I'm willing to be convinced there isn't).
> > > >
> > > > Days of Supply: should group suggestions within that range together to
> > > > reduce the total number of suggestions.
> > > >
> > > > Min/Max OnHand: When you go below the min, place an order. If Reorder to Max
> > > > enabled, buy enough to get to Max. If not, get to more than min.
> > > >
> > > > These two don't seem to play together very reliably. If there is a PO
> > > > already in the system that is due OUTSIDE the Days of Supply range, we get a
> > > > Change suggestion to reduce, and then a New suggestion to order more now. My
> > > > purchasing guys are going crazy on that... shouldn't the Change suggestion
> > > > just say to move it in?
> > > >
> > > > There's more, but my brain already hurts.
> > > >
> > > > Ernie Lowell
> > > > Diba Industries
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > [Non-text portions of this message have been removed]
> > > >
> > >
> >
>
>
>
> [Non-text portions of this message have been removed]
>