PO Print Report

PO.Update Method
PreProcess Condition:

the ttPOHeader.ReadyToPrint field has been changed from false to true
and number of rows in the 'OrderDate Less Than Today' query is not less than 1

OrderDate Less Than Today Query:

for each ttPOHeader where ttPOHeader.RowMod = 'U' and ttPOHeader.OrderDate < Today

Action:

set the POHeader.PrintAs field of the updated row to the "C" value

This will not work for POs modified the same day they were created.....

--- In vantage@yahoogroups.com, "Brian W. Spolarich " <bspolarich@...> wrote:
>
> Can you describe your BPM? ;-)
>
> --
> Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix / Picometrix
> Â Â Â Â bspolarich@... ~ 734-864-5618 ~ www.advancedphotonix.com
>
>
> -----Original Message-----
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of bw2868bond
> Sent: Wednesday, September 02, 2009 11:26 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: PO Print Report
>
> --- In vantage@yahoogroups.com, Robert Brown <robertb_versa@> wrote:
> >
> > I think Brian is right. I don't think the printing BO methods are exposed to leverage for this.
> >
> > However (depending upon what version you are running, as the versions we've been on: 305-405a have all had SIGNIFICANT changes to BO methods & what native table field actually get updated on certain events for PO Entry... clearly a work in process!), - PO Entry does keep internal track of whether a PO should be "printed as New" versus "Change order printed" (or something to that effect).
> >
>
>
> Somewhere between 8.00.811 and 8.03.405 the automatic change of print as new to print as change order was 'removed' I logged a support call and was told this is working as designed - even though support confirmed it worked in one version but not the other. I cobbed together a BPM that simulates the desired effect for us......
>
> We never used 8.03.3xx
>
>
>
> ------------------------------------
>
> Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have already linked your email address to a yahoo id to enable access. )
> (1) To access the Files Section of our Yahoo!Group for Report Builder and Crystal Reports and other 'goodies', please goto: http://groups.yahoo.com/group/vantage/files/.
> (2) To search through old msg's goto: http://groups.yahoo.com/group/vantage/messages
> (3) To view links to Vendors that provide Vantage services goto: http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
>
I'm looking to create a report that will show what PO's have not been
printed. I know for Jobs there is the travelerslastprinted field, which
works great for jobs. Does anyone know what field I could use to show
PO's that have not printed?



Thanks,



Travis Late

ERP Project Manager

M-B Companies, Inc

1200 Park Street

Chilton, WI 53014

Phone: 920-898-1560 Ext.152

Cell: 920-960-0062

Email: tlate@... <mailto:tlate@...>





[Non-text portions of this message have been removed]
I'm doubtful you'll be able to do this. The printing functions in Vantage don't have BO method hooks associated with them, so there's no way to do something like a Post-Processing BPM directive that updates POHeader.Date01 with the last printed date.

-bws

--
Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix / Picometrix
    bspolarich@... ~ 734-864-5618 ~ www.advancedphotonix.com


-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Late, Travis
Sent: Tuesday, September 01, 2009 9:47 AM
To: vantage@yahoogroups.com
Subject: [Vantage] PO Print Report

I'm looking to create a report that will show what PO's have not been
printed. I know for Jobs there is the travelerslastprinted field, which
works great for jobs. Does anyone know what field I could use to show
PO's that have not printed?
I think Brian is right. I don't think the printing BO methods are exposed to leverage for this.

However (depending upon what version you are running, as the versions we've been on: 305-405a have all had SIGNIFICANT changes to BO methods & what native table field actually get updated on certain events for PO Entry... clearly a work in process!), - PO Entry does keep internal track of whether a PO should be "printed as New" versus "Change order printed" (or something to that effect).

Sounds like you want to ID approved POs still set to 'print as new'... You may (or should I say "will") find the native app table views don't directly correlate to the tables in the data dictionary (which seems to be the annoying norm for apps more often than not) - but studying the native views in the app (in customization mode data tools) and comparing to the data dictionary of likely sources of those views (which might include the Xref table) - as well as some mind numbing full trace log reviews - might reveal the critical fields (or perhaps a BO method you can trap that updates them) that you could then either write a BAQ report directly against (or indirectly use in a BPM or customization to do what Brian suggests - populate a 'last print date' upon change in true/false value of one or both of those fields - then write your BAQ against that 'last print date' field you add to the app.).

Rob Brown




________________________________
From: Brian W. Spolarich <bspolarich@...>
To: vantage@yahoogroups.com
Sent: Tuesday, September 1, 2009 10:05:20 AM
Subject: RE: [Vantage] PO Print Report


I'm doubtful you'll be able to do this. The printing functions in Vantage don't have BO method hooks associated with them, so there's no way to do something like a Post-Processing BPM directive that updates POHeader.Date01 with the last printed date.

-bws

--
Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix / Picometrix
bspolarich@advanced photonix. com ~ 734-864-5618 ~ www.advancedphotoni x.com

-----Original Message-----
From: vantage@yahoogroups .com [mailto:vantage@yahoogroups .com] On Behalf Of Late, Travis
Sent: Tuesday, September 01, 2009 9:47 AM
To: vantage@yahoogroups .com
Subject: [Vantage] PO Print Report

I'm looking to create a report that will show what PO's have not been
printed. I know for Jobs there is the travelerslastprinte d field, which
works great for jobs. Does anyone know what field I could use to show
PO's that have not printed?







[Non-text portions of this message have been removed]
--- In vantage@yahoogroups.com, Robert Brown <robertb_versa@...> wrote:
>
> I think Brian is right. I don't think the printing BO methods are exposed to leverage for this.
>
> However (depending upon what version you are running, as the versions we've been on: 305-405a have all had SIGNIFICANT changes to BO methods & what native table field actually get updated on certain events for PO Entry... clearly a work in process!), - PO Entry does keep internal track of whether a PO should be "printed as New" versus "Change order printed" (or something to that effect).
>


Somewhere between 8.00.811 and 8.03.405 the automatic change of print as new to print as change order was 'removed' I logged a support call and was told this is working as designed - even though support confirmed it worked in one version but not the other. I cobbed together a BPM that simulates the desired effect for us......

We never used 8.03.3xx
Can you describe your BPM? ;-)

--
Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix / Picometrix
    bspolarich@... ~ 734-864-5618 ~ www.advancedphotonix.com


-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of bw2868bond
Sent: Wednesday, September 02, 2009 11:26 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: PO Print Report

--- In vantage@yahoogroups.com, Robert Brown <robertb_versa@...> wrote:
>
> I think Brian is right. I don't think the printing BO methods are exposed to leverage for this.
>
> However (depending upon what version you are running, as the versions we've been on: 305-405a have all had SIGNIFICANT changes to BO methods & what native table field actually get updated on certain events for PO Entry... clearly a work in process!), - PO Entry does keep internal track of whether a PO should be "printed as New" versus "Change order printed" (or something to that effect).
>


Somewhere between 8.00.811 and 8.03.405 the automatic change of print as new to print as change order was 'removed' I logged a support call and was told this is working as designed - even though support confirmed it worked in one version but not the other. I cobbed together a BPM that simulates the desired effect for us......

We never used 8.03.3xx



------------------------------------

Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and Crystal Reports and other 'goodies', please goto: http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto: http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto: http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links