Mgroeneveld
Well Known Member
Dear list,
We're facing a challenging problem regarding Transfer Order's next numbering.
Setup is as follows.
2 Types of Transfer Orders:
ST - OT
S5 - O5
The ST and S5 are using seperate buckets in the Next Numbering (standard NN). The OT and O5 refer though to the same bucket in the Next Numbering.
The problem is e.g. that a ST refers to a particular OT. The OT though refers to a total different ST. Also the order lines are often linked incorrectly.
We noticed a call on the KG indicating possible locking problems with a particular version of Oracle in conjunction with JDE. Just to be sure, we changed the JDE.ini file with the solution for this locking problem. I am still a bit concerned on the next numbering issue.
Question: does anyone have a similar issue ? If so, what could be the best solution ? Maybe reserving a seperate bucket for the O5 would help ??
Thanks in advance.
Martijn Groeneveld
Working with Oneworld XE, version 1 SP20
We're facing a challenging problem regarding Transfer Order's next numbering.
Setup is as follows.
2 Types of Transfer Orders:
ST - OT
S5 - O5
The ST and S5 are using seperate buckets in the Next Numbering (standard NN). The OT and O5 refer though to the same bucket in the Next Numbering.
The problem is e.g. that a ST refers to a particular OT. The OT though refers to a total different ST. Also the order lines are often linked incorrectly.
We noticed a call on the KG indicating possible locking problems with a particular version of Oracle in conjunction with JDE. Just to be sure, we changed the JDE.ini file with the solution for this locking problem. I am still a bit concerned on the next numbering issue.
Question: does anyone have a similar issue ? If so, what could be the best solution ? Maybe reserving a seperate bucket for the O5 would help ??
Thanks in advance.
Martijn Groeneveld
Working with Oneworld XE, version 1 SP20
