F3102.CPAT doubled after R31802A

jhsiao520123

Active Member
Dear Lists,
We just went live on 9.2 (TR9.2.0) however suffered the situation when scheduled R31802A runs in final mode, some work orders F3102.CPAT doubled than F3102.OPAT. Have checked the Oracle Support there does the indicate the bug, however not pretty fit our situation.
We are pretty straightforward the SBF activity where is 07 standard cost, and there are no scraps. But some work orders F3102.CPAT doubled and some are not after R31802A runs. Support said when R31802A runs the work order twice this can happen but how do I know why the R31802A will run over certain orders twice?
We set the R31802A with the single thread which is no other programs run at he same time. Could someone help how this can happen to our urgent situation? Thanks lot!

Regards,
John
 
This was a really ugly couple of bugs that affected not just CPAT but other values as well I believe.
It affected 9.0, 9.1, and 9.2

Oracle offered no fix to the data that I'm aware of - we had to manually identify and fix a couple thousand work orders.

Objects affected were B3101630, B3104170, and B3104180.

Good Luck
 
Hi Larry,
Have you ever found the true cause of this problem? This happens to us so randomly and some times the R31802A runs with OK results, some times couple WOs doubled with all cost components (not just A1) on F3102. I am not good at tools and would you have any suggestions can avoid this as possible? (Like run with small number of WO on R31802A? Or anything else?) Thanks very much!
 
Here is the reply from Oracle:
Could you please check with your CNC and confirm with us if you have the Bug 22909722 - R31802A DOUBLES CPAT applied at your side?
If not, Bug 22909722 - R31802A DOUBLES CPAT is available for download under Baseline ESU JN13444 (having Special Instructions too), dependent upon Baseline ESUs JN11543 and JN10604.

Please note that the Baseline ESUs JN11543 and JN10604 need to be installed prior of taking the required Baseline ESU JN13444.
Once you applied all the ESUs, please do a full package update and deploy and then have the issue retested.

Regards,
John
 
What I remember is that it only triggered if one of the work orders being processed had an error or a specific type of error. Every Work Order following the WO that had an error in that run had the CPAT issue (Amt doubled, etc).
 
Back
Top