BPM PO.Update: I want to raise an exception when the Part Class

Yahoo Archive
1
That worked. I didn't need the ClassID.
Thanks!!!!
Patty Buechler


--- In vantage@yahoogroups.com, "vantage" <vantage@...> wrote:
>
> Patty,
> Â
> I am doing this same setup however you do not need ClassID and
> ClassDescription. I and looking at the PODetail.CalcTransType and
the
> PODetail.ClassDescription fields to fire the exception. If the
line is
> purchase to job the CalcTransType will be PUR-MTL. You may want to
delete
> the BPM and recreate it to see if this fixes your problem.
> Â
> Conditions : the PODetail.CalcTranType field of the changed row is
equal to
> the "PUR-UKN" value
> and the PODetail.ClassDescription field of the changed row is equal
to the
> "" value
> Â
> Â
> Steve
> Â
> -----Original Message-----
> From: bpbuechler [mailto:pbuechler@...]
> Sent: December 04, 2008 9:30 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: BPM PO.Update: I want to raise an exception
when the
> Part Class = "" (8.03.405)
> Â
> Okay...so I took your suggestion and I kept the table for the
> conditions to ttPODetail.
>
> So now it looks like the following:
> the PODetail.CalcJobSeqType field of the changed row is equal to
> the "PUR-UKN" value
> and the PODetail.ClassID field of the changed row is equal to
the ""
> value
> or the PODetail.ClassDescription field of the changed row is equal
to
> the "" value
>
> It still does not work...Help?
> BTW...we are on 8.03.405
>
> Thanks
> Patty Buechler
>
> --- In vantage@yahoogroups.com, "Nigel Kerley" <nigel.kerley@>
> wrote:
> >
> > Hi Patty,
> >
> > I'm open to correction on this - I'm still getting to grips with
> BPMs
> > - but I don't think you can include more than one "tt" table in a
> > query or in BPM 4GL code. My understanding is than when you save
a
> > PODetail line, the ttPODetail table is cleared. So if you then
add
> a
> > Release, you're now working off the ttPORel table and you'll have
> to
> > link this table to the saved PODetail table.
> >
> > HTH,
> >
> > Nigel.
> >
> >
> >
> >
> > --- In vantage@yahoogroups.com, "bpbuechler" <pbuechler@> wrote:
> > >
> > > I have created a BPM around the PO.Update to raise an exception
> > when
> > >
> > > the PORel.TranType field of the changed row is equal to
the "PUR-
> > UKN"
> > > value and the PODetail.ClassID field of the changed row is
equal
> to
> > > the "" value or the PODetail.ClassDescription field of the
> changed
> > > row is equal to the "" value
> > >
> > > My problem is that I only want to raise the exception when
> the "Buy
> > > For" is OTHER.
> > >
> > > So I added one more condition where the ttPORel.TranType = "PUR-
> > UKN"
> > > and it still raises the exception if the "Buy For" is a Job.
> > >
> > > I see there are a couple fields in related tables
> > > (ttPODetail.CalcTranType & ttPORel.JobSeqType). So I added
those
> > too
> > > and it still didn't work as I need it to.
> > >
> > > Any thoughts/suggestions?
> > > Thanks
> > > Patty Buechler
> > >
> >
>
2
I have created a BPM around the PO.Update to raise an exception when

the PORel.TranType field of the changed row is equal to the "PUR-UKN"
value and the PODetail.ClassID field of the changed row is equal to
the "" value or the PODetail.ClassDescription field of the changed
row is equal to the "" value

My problem is that I only want to raise the exception when the "Buy
For" is OTHER.

So I added one more condition where the ttPORel.TranType = "PUR-UKN"
and it still raises the exception if the "Buy For" is a Job.

I see there are a couple fields in related tables
(ttPODetail.CalcTranType & ttPORel.JobSeqType). So I added those too
and it still didn't work as I need it to.

Any thoughts/suggestions?
Thanks
Patty Buechler
3
Hi Patty,

I'm open to correction on this - I'm still getting to grips with BPMs
- but I don't think you can include more than one "tt" table in a
query or in BPM 4GL code. My understanding is than when you save a
PODetail line, the ttPODetail table is cleared. So if you then add a
Release, you're now working off the ttPORel table and you'll have to
link this table to the saved PODetail table.

HTH,

Nigel.




--- In vantage@yahoogroups.com, "bpbuechler" <pbuechler@...> wrote:
>
> I have created a BPM around the PO.Update to raise an exception
when
>
> the PORel.TranType field of the changed row is equal to the "PUR-
UKN"
> value and the PODetail.ClassID field of the changed row is equal to
> the "" value or the PODetail.ClassDescription field of the changed
> row is equal to the "" value
>
> My problem is that I only want to raise the exception when the "Buy
> For" is OTHER.
>
> So I added one more condition where the ttPORel.TranType = "PUR-
UKN"
> and it still raises the exception if the "Buy For" is a Job.
>
> I see there are a couple fields in related tables
> (ttPODetail.CalcTranType & ttPORel.JobSeqType). So I added those
too
> and it still didn't work as I need it to.
>
> Any thoughts/suggestions?
> Thanks
> Patty Buechler
>
4
Okay...so I took your suggestion and I kept the table for the
conditions to ttPODetail.

So now it looks like the following:
the PODetail.CalcJobSeqType field of the changed row is equal to
the "PUR-UKN" value
and the PODetail.ClassID field of the changed row is equal to the ""
value
or the PODetail.ClassDescription field of the changed row is equal to
the "" value

It still does not work...Help?
BTW...we are on 8.03.405

Thanks
Patty Buechler

--- In vantage@yahoogroups.com, "Nigel Kerley" <nigel.kerley@...>
wrote:
>
> Hi Patty,
>
> I'm open to correction on this - I'm still getting to grips with
BPMs
> - but I don't think you can include more than one "tt" table in a
> query or in BPM 4GL code. My understanding is than when you save a
> PODetail line, the ttPODetail table is cleared. So if you then add
a
> Release, you're now working off the ttPORel table and you'll have
to
> link this table to the saved PODetail table.
>
> HTH,
>
> Nigel.
>
>
>
>
> --- In vantage@yahoogroups.com, "bpbuechler" <pbuechler@> wrote:
> >
> > I have created a BPM around the PO.Update to raise an exception
> when
> >
> > the PORel.TranType field of the changed row is equal to the "PUR-
> UKN"
> > value and the PODetail.ClassID field of the changed row is equal
to
> > the "" value or the PODetail.ClassDescription field of the
changed
> > row is equal to the "" value
> >
> > My problem is that I only want to raise the exception when
the "Buy
> > For" is OTHER.
> >
> > So I added one more condition where the ttPORel.TranType = "PUR-
> UKN"
> > and it still raises the exception if the "Buy For" is a Job.
> >
> > I see there are a couple fields in related tables
> > (ttPODetail.CalcTranType & ttPORel.JobSeqType). So I added those
> too
> > and it still didn't work as I need it to.
> >
> > Any thoughts/suggestions?
> > Thanks
> > Patty Buechler
> >
>
5
Hi Patty,

I was trying something similar recently: I wanted to raise an
exception if the user didn't change the GL Chart from the default. I
tried every way I could this of to raise the exception on the PORel
table and the PODetail table. I couldn't get anything to work.

In the end, I cheated! I created the BPM as a pre-processing
directive on the PO.ChangeApproveSwitch and added a condition "number
of rows in the (below) query is not less than 1".

The query I used is: "for each ttPOHeader where
(ttPOHeader.RowMod='A' or ttPOHeader.RowMod='U') and
ttPOHeader.ApprovalStatus = 'U' , each PORel where PORel.Company =
ttPOHeader.Company and PORel.PONum = ttPOHeader.PONum and
PORel.ExpChart = '8202'".

Yes, this waits until the user is finished entering and therefore
could have a number of "wrong" lines, but it works!

You could try something similar with a query like:
"for each ttPOHeader where (ttPOHeader.RowMod='A' or
ttPOHeader.RowMod='U') and ttPOHeader.ApprovalStatus = 'U' , each
PODetail where PODetail.Company = ttPOHeader.Company and
PODetail.PONum = ttPOHeader.PONum and PODetail.CalcJobSeqType = 'PUR-
UKN' and PODetail.ClassID=''".


Nigel.

--- In vantage@yahoogroups.com, "bpbuechler" <pbuechler@...> wrote:
>
> Okay...so I took your suggestion and I kept the table for the
> conditions to ttPODetail.
>
> So now it looks like the following:
> the PODetail.CalcJobSeqType field of the changed row is equal to
> the "PUR-UKN" value
> and the PODetail.ClassID field of the changed row is equal to the
""
> value
> or the PODetail.ClassDescription field of the changed row is equal
to
> the "" value
>
> It still does not work...Help?
> BTW...we are on 8.03.405
>
> Thanks
> Patty Buechler
>
> --- In vantage@yahoogroups.com, "Nigel Kerley" <nigel.kerley@>
> wrote:
> >
> > Hi Patty,
> >
> > I'm open to correction on this - I'm still getting to grips with
> BPMs
> > - but I don't think you can include more than one "tt" table in a
> > query or in BPM 4GL code. My understanding is than when you save
a
> > PODetail line, the ttPODetail table is cleared. So if you then
add
> a
> > Release, you're now working off the ttPORel table and you'll have
> to
> > link this table to the saved PODetail table.
> >
> > HTH,
> >
> > Nigel.
> >
> >
> >
> >
> > --- In vantage@yahoogroups.com, "bpbuechler" <pbuechler@> wrote:
> > >
> > > I have created a BPM around the PO.Update to raise an exception
> > when
> > >
> > > the PORel.TranType field of the changed row is equal to the
"PUR-
> > UKN"
> > > value and the PODetail.ClassID field of the changed row is
equal
> to
> > > the "" value or the PODetail.ClassDescription field of the
> changed
> > > row is equal to the "" value
> > >
> > > My problem is that I only want to raise the exception when
> the "Buy
> > > For" is OTHER.
> > >
> > > So I added one more condition where the ttPORel.TranType = "PUR-
> > UKN"
> > > and it still raises the exception if the "Buy For" is a Job.
> > >
> > > I see there are a couple fields in related tables
> > > (ttPODetail.CalcTranType & ttPORel.JobSeqType). So I added
those
> > too
> > > and it still didn't work as I need it to.
> > >
> > > Any thoughts/suggestions?
> > > Thanks
> > > Patty Buechler
> > >
> >
>
6
Patty,
Â
I am doing this same setup however you do not need ClassID and
ClassDescription. I and looking at the PODetail.CalcTransType and the
PODetail.ClassDescription fields to fire the exception. If the line is
purchase to job the CalcTransType will be PUR-MTL. You may want to delete
the BPM and recreate it to see if this fixes your problem.
Â
Conditions : the PODetail.CalcTranType field of the changed row is equal to
the "PUR-UKN" value
and the PODetail.ClassDescription field of the changed row is equal to the
"" value
Â
Â
Steve
Â
-----Original Message-----
From: bpbuechler [mailto:pbuechler@...]
Sent: December 04, 2008 9:30 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: BPM PO.Update: I want to raise an exception when the
Part Class = "" (8.03.405)
Â
Okay...so I took your suggestion and I kept the table for the
conditions to ttPODetail.

So now it looks like the following:
the PODetail.CalcJobSeqType field of the changed row is equal to
the "PUR-UKN" value
and the PODetail.ClassID field of the changed row is equal to the ""
value
or the PODetail.ClassDescription field of the changed row is equal to
the "" value

It still does not work...Help?
BTW...we are on 8.03.405

Thanks
Patty Buechler

--- In vantage@yahoogroups.com, "Nigel Kerley" <nigel.kerley@...>
wrote:
>
> Hi Patty,
>
> I'm open to correction on this - I'm still getting to grips with
BPMs
> - but I don't think you can include more than one "tt" table in a
> query or in BPM 4GL code. My understanding is than when you save a
> PODetail line, the ttPODetail table is cleared. So if you then add
a
> Release, you're now working off the ttPORel table and you'll have
to
> link this table to the saved PODetail table.
>
> HTH,
>
> Nigel.
>
>
>
>
> --- In vantage@yahoogroups.com, "bpbuechler" <pbuechler@> wrote:
> >
> > I have created a BPM around the PO.Update to raise an exception
> when
> >
> > the PORel.TranType field of the changed row is equal to the "PUR-
> UKN"
> > value and the PODetail.ClassID field of the changed row is equal
to
> > the "" value or the PODetail.ClassDescription field of the
changed
> > row is equal to the "" value
> >
> > My problem is that I only want to raise the exception when
the "Buy
> > For" is OTHER.
> >
> > So I added one more condition where the ttPORel.TranType = "PUR-
> UKN"
> > and it still raises the exception if the "Buy For" is a Job.
> >
> > I see there are a couple fields in related tables
> > (ttPODetail.CalcTranType & ttPORel.JobSeqType). So I added those
> too
> > and it still didn't work as I need it to.
> >
> > Any thoughts/suggestions?
> > Thanks
> > Patty Buechler
> >
>