Cume 14

[sally_earnest]

I am advising anyone preparing to upgrade to Cume 14 to go to the Knowledge Garden and look at the SARS on Cume 14 coming out in Cume 15. We had major problems with FASTR reports, Equipment Maintenance, AP, and GL. I would recommend skipping the Cume 14 Upgrade and wait for Cume 15. I would be interested in comments from anyone else that has installed Cume 14.

 

[esolch]

We upgraded to CUM 14 in August 2003. We have had a few minor issues come up. Things like in A/P the GUI did not function like it did for Voucher Entry in CUM 11 (they opened a SAR on that one). Some FASTR headings did not print, and we had to correct the print sequencing. Not show stoppers by any means. Since then, its been very smooth. I am guessing that when/if the real issues develop will be when we run the W2's and 1099's in January, after year end close. We have not had any problems with G/L.

 

[tpayne]

One of the main issues we have right now with cum 14 is Future Commits.
We are getting Sales Orders entered daily that are going into a Future
Committed state.
We then have to run the Repost Future Commits program to clear this.
Can't see anything on the KG.
Wondering if anyone else had issues with this?




Best Regards
Tony Payne - Senior Analyst/Programmer
Aker By Maax, Plymouth, Indiana
--------------------
4+ yrs JDE World Financials / Manufacturing
V5R2 / A7.3 cum14

 

[mgerritt]

Re: RE: Cume 14

Don't know if this is the same thing you are seeing, but... We are CUM 13. We are getting future commits too. Looks like when a blanket is released, ands the date for the shipment is over 30 days in the future. Haven't had much chance t really look at this yet. Are your porblems with orders with request dates 30+ days out? Blanket releases are the only time we would see this type fo time frame.

 

[tpayne]

RE: RE: Cume 14

Hi Marc,
No - ours are just ordinary orders with shipment dates within the next 2
weeks.
The system seems to randomly select lines and set them as future committed -
there doesn't appear to be any pattern to it as far as we can see. This is
happening during order entry, since when the user finishes entering an order
and goes to print it, some of the lines are already missing. They can also
tell because the line value is not set during order entry.
We went directly from cum 11 to cum 14, so it could be a cum 13 issue.
Hopefully we can resolve this soon. Seems strange that this would come in
way after the Y2K changes!




Best Regards
Tony Payne - Senior Analyst/Programmer
Aker By Maax, Plymouth, Indiana
--------------------
4+ yrs JDE World Financials / Manufacturing
V5R2 / A7.3 cum14

 

[nanda_raote]

A further question - has anyone tried the EDI enhancements in cum 14 to the inbound PO messages using P471411?

Thanks
Nanda