JMast
Reputable Poster
Hello All,
We upgraded from SQL 2000 SP23_K to SQL 2005 SP_ZA1 in February. I posted earlier about a issue we are seeing in SO Entry. I am not interested in rehashing that in this post, but I will give you some background for the real question.
The failure is on the Customer Master MBF when it pulls open invoices for the Sold To for a credit check. It is particularly odd since it only seems to be affecting one customer and only about 10% of their orders. The only other similar error is occasional failures of R42118 which allocates material to Sales Orders. Our focus has been on the SO issue since that is most disruptive. I started the case with the Service Pack group who flipped it to the Distribution group. Oracle has an ESU on the Customer Master MBF proposed as the solution.
My colleagues here are having a hard time comprehending how a significant upgrade in performance at the service pack and DB levels could cause a failure in an MBF that did not change.
So, the question to the experts: Does this often happen in JDE where a problem is created by a technical upgrade and the fix is to the application code? Any high level explanation why?
One reason this is so important is that this system is very stable but really has not been maintained from an ESU point of view, so applying the small ESU proposed by Oracle will require baseline ESUs in the Distribution module requiring much testing and redoing of some mods.
Thanks for any insight,
Jer
We upgraded from SQL 2000 SP23_K to SQL 2005 SP_ZA1 in February. I posted earlier about a issue we are seeing in SO Entry. I am not interested in rehashing that in this post, but I will give you some background for the real question.
The failure is on the Customer Master MBF when it pulls open invoices for the Sold To for a credit check. It is particularly odd since it only seems to be affecting one customer and only about 10% of their orders. The only other similar error is occasional failures of R42118 which allocates material to Sales Orders. Our focus has been on the SO issue since that is most disruptive. I started the case with the Service Pack group who flipped it to the Distribution group. Oracle has an ESU on the Customer Master MBF proposed as the solution.
My colleagues here are having a hard time comprehending how a significant upgrade in performance at the service pack and DB levels could cause a failure in an MBF that did not change.
So, the question to the experts: Does this often happen in JDE where a problem is created by a technical upgrade and the fix is to the application code? Any high level explanation why?
One reason this is so important is that this system is very stable but really has not been maintained from an ESU point of view, so applying the small ESU proposed by Oracle will require baseline ESUs in the Distribution module requiring much testing and redoing of some mods.
Thanks for any insight,
Jer