Thanks Nathan,
That certaily got me started in the right direction. Currently I have the following code on a PreProcess BPM
For each orderdtl, each ttorderdtl where ttorderdtl.Company = orderdtl.Company
and ttorderdtl.ordernum = orderdtl.ordernum no-lock.
Define variable cTemp as Character no-undo.
Assign cTemp = 'Before: ' + String(orderdtl.sellingquantity) + ' After: ' +
String(ttorderdtl.sellingquantity).
{lib\PublishInfoMsg.i &InfoMsg = "cTemp"}.
end.
This displays the results I'm looking for in the message box, but it displays both sets of numbers. It will display the first set of before and after, which is the numbers before the change, and then displays the numbers after the change. I cannot seem to find the reason for this?
Thanks
That certaily got me started in the right direction. Currently I have the following code on a PreProcess BPM
For each orderdtl, each ttorderdtl where ttorderdtl.Company = orderdtl.Company
and ttorderdtl.ordernum = orderdtl.ordernum no-lock.
Define variable cTemp as Character no-undo.
Assign cTemp = 'Before: ' + String(orderdtl.sellingquantity) + ' After: ' +
String(ttorderdtl.sellingquantity).
{lib\PublishInfoMsg.i &InfoMsg = "cTemp"}.
end.
This displays the results I'm looking for in the message box, but it displays both sets of numbers. It will display the first set of before and after, which is the numbers before the change, and then displays the numbers after the change. I cannot seem to find the reason for this?
Thanks
--- In vantage@yahoogroups.com, "Nathan" <bonner.n@...> wrote:
>
> Robert,
>
> Play with the following on your BPM and you will likely figure out where you can pick up the 'before' and 'after' values that you are looking for:
>
> PREPROCESS 4GL:
>
> For each ttUD09, each UD09 where ttUD09.Company = UD09.Company and ttUD09.Key1 = UD09.Key1 and ttUD09.Key2 = UD09.Key2 and ttUD09.Key3 = UD09.Key3 and ttUD09.Key4 = UD09.Key4 and ttUD09.Key5 = UD09.Key5 no-lock.
>
> Define variable cTemp as Character no-undo.
>
> Assign cTemp = 'Before: ' + String(UD09.Number01) + ' After: ' + String(ttUD09.Number01).
> {lib\PublishInfoMsg.i &InfoMsg = "cTemp"}.
>
> End.
>
> POSTPROCESS 4GL:
>
> Define Variable cTemp as Character no-undo.
>
> {lib\PublishInfoMsg.i &InfoMsg = "cTemp"}.
>
> I think you will find what you're looking for this way and should be able to display the 'cTemp' or whatever variable name you use in the body of your automatic email.
>
> By the way, I put up a post earlier this week on how to send emails a little more dynamically using 4GL within a BPM. This may be of interest to you for your current project.
>
> NB
>
> --- In vantage@yahoogroups.com, "Rob Bucek" <rbucek@> wrote:
> >
> > Have your BPM do the preprocess and a 4GL alert attachment do the
> > 'post'.
> >
> >
> >
> > Rob Bucek
> >
> > Manufacturing Engineer
> >
> > PH: (715) 284-5376 ext 3111
> >
> > FAX: (715)284-4084
> >
> > <http://www.dsmfg.com/>
> >
> > (Click the logo to view our site) <http://www.dsmfg.com/>
> >
> >
> >
> >
> >
> > From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> > Of Bob Schnable
> > Sent: Friday, December 11, 2009 11:43 AM
> > To: vantage@yahoogroups.com
> > Subject: [Vantage] Change in Quantity BPM
> >
> >
> >
> >
> >
> > Hello All,
> >
> > I currently have 2 BPM's running to alert people by e-mail when there is
> > a change in price or change in quantity on existing sales orders. When
> > there is a change, a preprocessing BPM invokes a post processing to send
> > the email. My issue is that we need both the pre and post numbers in the
> > email. I can obviously send out 2 emails, one with the pre-update
> > quantity or price and one with the post. I'm looking to send it out in
> > one e-mail. Is there a simple idea I'm missing, because I've come to the
> > conclusion that I'll have to write a small 4GL script. Thanks in advance
> > for the help!
> >
> > Robert Schnable
> >
> > IT Applications and Business Support Associate
> >
> > 440-543-8157
> >
> > 440-543-4582 Fax
> >
> > [Non-text portions of this message have been removed]
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>