For partners that build or integrate commercially available applications and service solutions with the Oracle Cloud Platform
For partners that provide implementation or managed services around Oracle Cloud Applications
All,
We received the 19B update into our DEV/TEST environment over the weekend and started testing on Monday. We uncovered an issue with general journals. Now, when we upload them via spreadsheet, they don't route for approval, and no email notifications are sent out. We have an SR open, but nothing from Oracle yet. Has anyone else encountered this?
We checked the journal source settings and nothing has changed there. It works fine if you create the journal through the UI, but almost all of our journals are uploaded through excel.
Thanks,
Jason
Comment
Hi Jason-We didnt see any issue in this in 19B
Thanks!
Karthik
Average Rating:



2 ratings
|
Sign in to rate this
Jason,
We are getting a similar issue after implementing 19B to Test on 5/3/19. When uploading from the spreadsheet and selecting "Submit Journal Import and Posting" from the Submission Options, the journal does not route for approval. The user must still navigate to the journal under Manage Journals and route it manually. The approval process works correctly after manually completing this step.
Previously, after selecting this option during the upload, the journal would automatically route.
I've created an SR and will update when I get a solution. Please do the same.
Thanks,
Dan
Average Rating:



3 ratings
|
Sign in to rate this
Jason and Dan, please share the outcome of your SRs. I'm sure there are many of us interested. Thanks, Wendy
Average Rating:



1 rating
|
Sign in to rate this
Thanks for posting this. We have a 5/31 fiscal year end. I'm not looking forward to this being an issue in June.
It's not listed in the Known Issues note - Oracle Financials Cloud Functional Known Issues - Release 19B (Doc ID 2523036.1)
Average Rating:



2 ratings
|
Sign in to rate this
All,
Update on our end. We are seeing the issue exactly how Dan described it. We walked Oracle Support through the process in both 19B and 19A (Test vs Prod) today to prove it's not working as it was. They are forwarding to development and will update our SR when they have more to report. I'll update this post when I know more.
Thanks,
Jason
Average Rating:



3 ratings
|
Sign in to rate this
Hi Jason/Dan- Yes just tested in Non-PROD were 19B applied and this is an issue.The Journals are not routing to the approver when upload through Spreadsheet.We need to manually push this
I need to raise the SR
Thanks!
Karthik
Average Rating:



2 ratings
|
Sign in to rate this
What's the Bug # so I can follow this?
Average Rating:



2 ratings
|
Sign in to rate this
Update today from Oracle. This has been classified as a bug, # 29754451
Here is their proposed work around: You can schedule an AutoPost program for Journal Source "Spreadsheet". This AutoPost will pick these batches and request for approval and posting. The user will not have to manually post these batches each time.
I tested this and it appears to work. We have a number of batches in the system that I think we'll need to clean up before running in production, and it will slow down the batch approval process, as approvers won't see until the scheduled process runs.
Jason
Average Rating:



3 ratings
|
Sign in to rate this
I have 3 separate SRs going on with Oracle regarding Journal Approval post 19A upgrade (2 are with Development). Need to open one more, it seems for 19B :(
Average Rating:



1 rating
|
Sign in to rate this
Update from Oracle: They are giving patch fix for GL Approval issue in our environments on 5/24 for Non-Prod & 5/31 for Prod
Thanks!
Karthik
Average Rating:



3 ratings
|
Sign in to rate this
Has the patch resolved the issue?
Average Rating:



1 rating
|
Sign in to rate this
Patch will get apply only by 5/24.Will keep you post the results
Average Rating:



1 rating
|
Sign in to rate this
Sorry, will ask next week. Misread the date.
Average Rating:



1 rating
|
Sign in to rate this
Patch was applied in our non-production and is working fine now.The Journals are routing automatically to the approver now
PROD Patch by 5/31.
Thanks!
Karthik
Be the first to rate this
|
Sign in to rate this
We have the same issue. I will be following.
Be the first to rate this
|
Sign in to rate this
Just opened a SR. Here's the response from Support.
"...Also, this resolution is specific to approval rules defined in BPM and having custom stages and/or participants.
If you have observed that the custom stages/participants and corresponding rules are missing after upgrade, the issue has been resolved via bug 29396947.
- Issue will be fixed in : 1901 March 8th CWB, April monthly
Alternate solution
If there are very few rules and stages that are missing after the upgrade, oracle recommends that you redefine the rules Manually, in BPM.
If there are many and complex rules and custom stages, please engage the support to get further assistance.
Please refer the KM- Custom Stages and Participants missing in approval rules, after upgrade ( Doc ID 2516110.1 ) "
Be the first to rate this
|
Sign in to rate this
I opened an SR as well.
Has anybody been able to get the link to this bug 29396947 to work? If so, can you share the correct link?
Be the first to rate this
|
Sign in to rate this
https://support.oracle.com/epmos/faces/PatchDetail?requestId=22793149&_afrLoop=491850157287046&patchId=29396947&_afrWindowMode=0&_adf.ctrl-state=r3gkm88b0_418
Thanks!
Karthik
Be the first to rate this
|
Sign in to rate this
We asked for the patch to be applied in non-prod on 5/24 and in prod 5/31, Oracle has come back with a 6/7 date, but we have a 5/31 year-end.
Be the first to rate this
|
Sign in to rate this
Hi All
Patch was applied in our non-production and is working fine now.The Journals are routing automatically to the approver now
PROD Patch by 5/31.
Thanks!
Karthik
Average Rating:



1 rating
|
Sign in to rate this