Re: Cumulative Sh15127 - 6717

I'v no idea on the root cause or solution, but here is a free hint while you
are waiting for a solution:
    a trigger on IMHIST can help you avoiding the SQL and continuing your
business as if the bug isn't there.

Kris

----- Original Message ----- 
From: "Ann Neal" <aneal@xxxxxxxxxxxxxxxxxx>
To: "MAPICS ERP System Discussion" <mapics-l@xxxxxxxxxxxx>
Sent: Monday, October 24, 2005 10:07 PM
Subject: [MAPICS-L] Cumulative Sh15127 - 6717


> List,
>
> Since applying Sh15127, IFM 3way manual match is requiring the field VNDNR
> in the IMHIST record to be populated.  We have queried RP & RD
transactions
> in IMHIST back to January and this field is blank for scanned receive
> transactions.  We populate TRDATA with RP or RD information and the
purchase
> order gets updated.  The Ujobs also call the programs to create the IMHIST
> record(s).
>
> What we are trying to decide is this a PMC problem - should IMHIST have
the
> vendor info written to it; or should IFM 3way match not need the vendor
info
> as prior to Sh15127?  At present Infor support has closed BOTH tickets
> saying the fix should be in the other application.
>
> Has anyone else encountered this problem?  We are running an SQL statement
> manually a couple times per day to update VNDNR in IMHIST just to be able
to
> do business.
>
> thanks,
> Ann
> LeTourneau, Inc.
>
> _______________________________________________
> This is the MAPICS ERP System Discussion (MAPICS-L) mailing list
> To post a message email: MAPICS-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/mapics-l
> or email: MAPICS-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/mapics-l.
>
>