Best Of
Re: When drilling down from GL, View Transaction appears to do nothing
Thanks for sharing this info….
Re: Critical Vulnerability in Siebel IP 25.1 catalina.jar file
When you start the 25.9 installation, it will ask to run postinstalldbsetup setup which is part of installation and its mandatory to run. So that the schema changes from 25.1 to 25.9 will be applied.
Note that this is not an upgrade rather update. If you want to skip postinstalldbsetup during installation, you can use differ option which will generate schema.ddl which you need to ask your DBA to apply manually.
But you must complete postinstalldbsetup, else your application will not function properly.
Hope this clarifies your queries.
Regards,
Mallik Kalluri
Re: Critical Vulnerability in Siebel IP 25.1 catalina.jar file
If you apply a monthly update, as mentioned by my colleague Mallik, the PostInstallDBSetup is mandatory.
Furthermore, it is customer's responsibility to perform regression tests before going live on Production as any other change you would perform during your development cycle and would like to migrate to Production.
Regards,
Michael Harada
Re: Transaction Reason not showing up in new mobile responsibilities
This issue would be better served in a Service Request (SR) opened in My Oracle Support. Detailed logging and/or specific customer details may be required for resolution, and for your protection we ask that this sort of information be transmitted only via a secure SR. When creating your SR, you can reference the URL of this community post.
Re: We dont receive email from our incident rules (sort of)
Hello @Rookie_DBA,
Please use the Simulate button to see which rule is causing this. Please raise an SR with OEM Support so that we can help you out in a screenshare.
Regards,
Satya
When drilling down from GL, View Transaction appears to do nothing
This is to share some info to potentially help someone else in the future. We have version 12.2.12 and the product is General Ledger.
In Inquiry > Account, select an account and click Show Journal Details then click Drilldown. The View Journal Entry Lines form appears in a browser window.
If you click View Transaction and it seems like nothing at all happens, the issue could be that pop ups are blocked so a message such as "frmservlet.jnlp could harm your device, do you want to keep it anyway" isn't being shown. Look on the URL address bar at the top of the screen and check for a small icon after the address. Hovering over the icon shows that pop ups have been blocked. Click on the icon and choose to allow pop ups from your EBS. Click on View Transaction again. This time, the message should be shown and the user can choose to Keep the file and then the java window will open and display the transaction.
This seemed like a useful addition since some searching found posts on how to respond to the message, how to make jnlp open automatically and so on, but not one for no message appearing at all.
Re: Duplicate Supplier / Vendor Cleanup FSCM 9.2 Image 43 Tools 8.61
We have been through this exercise a few times over the years. I've seen a few things done.
Depending on if there are open transactions for the supplier (req's, PO's, contracts, items associated, Sourcing Events, RFQ's, etc.) we have requested that any open activity be closed so the vendor can be inactivated and any items where the supplier is listed as a priority be moved to the new or duplicate supplier.
I believe in those cases our AP group changes the vendor's name to do not use, use vendor xyz. At least then folks can see, if they try to use the supplier to use the supplier number we want to go forward with. I think this has been done for ages, regardless of the path forward.
Like this-
In other cases, I've seen where we make the supplier not open for ordering. This seems to allow active transactions to naturally clear up on their own, but new Req's or PO's can't be created. Although, this may take a while before that can happen. In this case, the items, if there are any should be moved to a different supplier.
There's been some conversation about allowing the supplier to be updated on the PO, but from a legal perspective, even if they are duplicates in your system that could get a little weird. We currently do not allow the supplier to be changed on a PO once it's been dispatched.
Although, there's been a case or two where we have made an exception and changed configuration to allow it- for that situation only and changed it back.
In some cases, new contracts have to be created using the supplier to move forward with. In others, it seems we have created a new contract version and changed the vendor for that version. That seems to mostly work. The idea is to make sure new req's or PO's created reference the appropriate contract.
In our situation, we also have to consider integrations to other systems. That always adds some spice to an already spicy situation. lol
Let us know if you have questions.
Happy to help! 🌶️
Re: How to copy WBS, Activities, and Relationships from 3 separate projects into one project
From any existing project, you can go next to a WBS Root or lower and go to far left until the GEAR Icon appears, then click it and select ADD WBS from existing Project… then simply choose where it is and bring it in. Use details to select what all you carry in with addition.