RE: Anyone try PTF 3196 for R6 Yet?

[Konrad Underkofler <kdunderk@xxxxxxxxxxxxx>]

Ann,

No huge show stopping issues but lots of little things and
while researching APAR issues see changes in the COM model
in the letters that just don't make much sense. As an example
the text of the letter says fix unit of measure and the diff
of the model is in the price calculation area.

MRP is now showing missing ITMRVAL0 records on the planning
exception report (that arent missing) because of effectivity
issues (rank this one as EPDM strangeness), before R6 it
only used to inform us of missing item balance and planning
records.

Shipping date calculations on availability and acknowledgements
in COM never let you ship on Thursday with a 2 day ship lead
time. Ship calendar processing is not really working well
anywhere.

Kit pick lists and shipments went south during the migration
from R4 to R6 (NOTE to anyone that uses kits and has not
migrated yet!). Kits never did really work right on R4 so
I am looking forward to having the inventory correct.

Serial shipment entry now always goes back to warranty date
every time enter is hit instead of staying on the serial
subfile line as it did in R4. We scan numbers so this was
a big issue. And MAPICS refuses to fix it!

Green screen EPDM was not showing revision correctly.

EPDM requires a send to PDM to add an item balance record.
(I thought PDM went away with R6).

MUI needed new objects to run the EVNTROUTER under the right
user id.

And of course the usual assortment of missing records, files
etc. but I expected some of that with migration.

I did know about the RPGLE issue. It is because source change
date does not show at the object level for an ILE object. They
had to change the selective apply method to fix that but I
believe ACSAPPLY has been changed to accomplish that.

Thankfully we only use EPDM so we are insulated from alot of
the client issues. So overall we are fine, just sort of
disappointed since PTF 2624 should have been mature,
there really is no new function and enough has changed
accidentally (or been "enhanced") to make it a pain in the
posterior. But at least we are at current level!

Regards,

Konrad