jimmymac
Reputable Poster
A while back we upgraded our OneWorld XE to SP23 on the A400 and had major problems. We quickly had to roll back to SP22. We have custom C programs which serve as an interface between a legacy RPG/JAVA system to One World XE. These C programs call the OneWorld Work Order and Purchase Order MBFs to update and create Work orders and Purchase Orders.
Beginning after we installed SP23, the C program that calls the PO BeginDoc returned with an error code. We only get that the function failed, not why unfortunately. But in the jdedebuglog we see very strange things. For example, the function Verify Approval Route Code was being called and failing. However we do not use Approval Route Codes and the version of P4310 that we reference in the calls has a blank for the option which means to not edit route codes. It seems to be doing it anyway and other similar things are occuring that indicate the the values we are passing to the MBFs and the data that the MBFs are receiving are somehow different or corrupted. Note that when we run the same test in a SP22 environment, everything passes and the logs show among other things that the Approval Route Code is not called, which is correct. It has been suggested that in SP23 JDE introduced unicode and our C programs may need to be converted to be unicode capable to work. However, it was my understanding that unicode wasn't introduced until 8.9 and shouldn't have any effect on XE.
Oracle/JDE has been zero help and we seem to be on our own.
Any thoughts about the unicode recommendation or any other ideas would be appreciated.
Thanks.
Beginning after we installed SP23, the C program that calls the PO BeginDoc returned with an error code. We only get that the function failed, not why unfortunately. But in the jdedebuglog we see very strange things. For example, the function Verify Approval Route Code was being called and failing. However we do not use Approval Route Codes and the version of P4310 that we reference in the calls has a blank for the option which means to not edit route codes. It seems to be doing it anyway and other similar things are occuring that indicate the the values we are passing to the MBFs and the data that the MBFs are receiving are somehow different or corrupted. Note that when we run the same test in a SP22 environment, everything passes and the logs show among other things that the Approval Route Code is not called, which is correct. It has been suggested that in SP23 JDE introduced unicode and our C programs may need to be converted to be unicode capable to work. However, it was my understanding that unicode wasn't introduced until 8.9 and shouldn't have any effect on XE.
Oracle/JDE has been zero help and we seem to be on our own.
Any thoughts about the unicode recommendation or any other ideas would be appreciated.
Thanks.