peterbruce
Legendary Poster
JDEList,
I recently encountered a problem where the data selection for UBE version was apparently overwritten on the enterprise server. After some investigation, I found that this was the case.
When a UBE version is run on the server from a client (not triggered on the server itself by a scheduler - JDE or other), the data selection for the version is overwritten.
This what happened: I ran a UBE version from a client and changed the data selection at the time of running the version. Report came out as I expected. Then the same UBE version was run by a scheduler on the server. I had expected it to use the original data selection, but it used the changed data selection that I had used when I ran it. I then looked at the data selection from a client and it was unchanged (note: to change the data selection on a version permanently you need to check it out in OMW, change it, and check it back in, then install it). I than ran it without changing it and it was as expected. I then manually ran the UBE version on the server (using runube) and it was as expected - it had changed back to the original data selection.
I monitored the tam files - the rdaspec.ddb and rdaspec.xdb in the spec directory - and they were indeed updated.
This is different behaviour to what happens if a UBE version is run locally - when the data selection is changed when submitting the UBE version loaclly it is not changed permanently, only for that run.
I was not aware that the behaviour on the server was different to that on a client and I am guessing that I am not alone in this, so here is a "heads up". This appears to be operating as designed and is probably the same for other JDE versions.
My installation config is:
Oracle JD Edwards EnterpriseOne,
E8.11sp1 8.97.2.1, ES Sun, Oracle DB 9207, Websphere 6 Win2K3.
I recently encountered a problem where the data selection for UBE version was apparently overwritten on the enterprise server. After some investigation, I found that this was the case.
When a UBE version is run on the server from a client (not triggered on the server itself by a scheduler - JDE or other), the data selection for the version is overwritten.
This what happened: I ran a UBE version from a client and changed the data selection at the time of running the version. Report came out as I expected. Then the same UBE version was run by a scheduler on the server. I had expected it to use the original data selection, but it used the changed data selection that I had used when I ran it. I then looked at the data selection from a client and it was unchanged (note: to change the data selection on a version permanently you need to check it out in OMW, change it, and check it back in, then install it). I than ran it without changing it and it was as expected. I then manually ran the UBE version on the server (using runube) and it was as expected - it had changed back to the original data selection.
I monitored the tam files - the rdaspec.ddb and rdaspec.xdb in the spec directory - and they were indeed updated.
This is different behaviour to what happens if a UBE version is run locally - when the data selection is changed when submitting the UBE version loaclly it is not changed permanently, only for that run.
I was not aware that the behaviour on the server was different to that on a client and I am guessing that I am not alone in this, so here is a "heads up". This appears to be operating as designed and is probably the same for other JDE versions.
My installation config is:
Oracle JD Edwards EnterpriseOne,
E8.11sp1 8.97.2.1, ES Sun, Oracle DB 9207, Websphere 6 Win2K3.