Best Of
Re: HR_DRPT_BLD and PS_HR_DIRECT_REP_5. Employee with Terminated manager will report to the next person
Universally, are you simply reassigning all active employees to another supervisor before the supervisor it termed? Common practice in JOB is to look at the supervisor being termed, and if that person has people assigned to them, before the term record is entered, the employees affected are reassigned to another person, and then the supervisor is termed clean. You also need to see if there are any approvals in the mix, and reassign the task as well before the supervisor term row is entered.
All this is because you do not have Position Management, and if you did, then the empty supervisor box will automatically up the task the that supervisors Reports To as long as the Org Chart is all connected top to bottom.
Before Jane 2 was Termed, John should have been reassigned to an active new manager.
Good luck, and let us know how this was resolved. Have a great day.
David L
DHLuding
Re: HR_DRPT_BLD and PS_HR_DIRECT_REP_5. Employee with Terminated manager will report to the next person
Hi TJR,
It depends on the reporting on those employees.
Access type 5 combines Position Reporting and Supervisor Reporting. Position
Reporting is by job. So, if someone has 2 jobs and one is inactivated, that reporting will be removed from the table when someone else takes that position. That row in PS_HR_DIRECT_REP_5 is used for drilling down to indirect reports but skipped when getting supervisor.
Supervisor reporting is to a person, so if the person is still active in any position the direct reports still report to them.
So, if you want people reporting to a person no matter what job is active use the supervisor id in Job. If you want them to stop reporting when the manager's job is inactivated, you should use position reporting.
As far as using the table directly, the table is used for drilling down and getting supervisor. These 2 functions are very different, so the methods are the best way to access the data. You will need to review the methods to make sure they get the correct information if your query the table directly.
Thanks,
Bhuvana
Reported Bug: JMSReceiver Connections to Queue Leave Open Connections in Status CLOSE_WAIT
A handle leak occurs in named subsystems interacting with local internal Tomcat when sending outbound messages, causing connections to be dropped on the Java side. However, the libcurl library keeps these connections alive, resulting in sockets stuck in CLOSE_WAIT state. This was identified to be a bug affecting Siebel versions 25.1 and later. The bug will be fixed in Siebel update 25.6. Doc ID 3088287.1. https://bit.ly/4ls2NiH
#SiebelCRM #Integrations
Re: F4311: Blank PDPN (Period Number) and PDFY (Fiscal Year)
Thank you for the explanation, Mahesh
Re: Project billing module.
Hi,
The accounting related to project billing are mentioned in the documentation:
> Accounting Transactions for Revenue, Invoices, and Advances
Thank you,
Christine
How to Disable Push Notifications on PeopleTools 8.61
This new document explains how to disable Push Notifications on PeopleTools 8.61.
Re: AP_INVOICES_PKG.GET_APPROVAL_STATUS package extremely slow
First, I would mention the possibility of performance issues related to running Gather Schema Statistics. Since performance seems to be degrading over time, it might be possible that you need to run Gather Schema Statistics, even in test instances, to get the best performance. This has resolved many performance issues for us.
What method are you using to do the report? That could have an impact as well.
Are you filtering the data any or are you returning all rows?
On which release are you? We are on 12.2 and I ran your query as-is in our test instance. With 5,743,834 rows, it returned data within seconds. A solution could be somewhat related to whether you are on 12.2 or an earlier release. As another quick test, I modified the query to return only those which were not APPROVED, ensuring all rows would be read. It returned 42,143 rows in about 45 minutes. So depending upon whether you are filtering the data by anything and how many rows you have, it could take quite some time.
Finally, consider this Note, which provides various methods to find different Status': What are the Invoice Statuses in the Invoice Workbench? How can you Query the Statuses from SQL? (Doc ID 2507071.1)
I hope this helps answer your question.
DGray
Re: PS Query Drilling URL - Attachment URL to URL which is a FTP site, NOT a database table
Oracle Support responded with a Bug request.
This is a big wet blanket to our Tools 8.53 upgrade benefits , if others are interested please log a case and reference the bug to raise its priority.
Bug 19429388 : FILE ATTACHMENTS HELD ON FTP SERVER ARE NOT SUPPORTED FOR DRILLURL ON PSQUERY
PS Query Drilling URL - Attachment URL to URL which is a FTP site, NOT a database table
Is it possible to use a FTP type URL in a drilling URL in a PS Query? The only way I've had it work and actually produce the document in the FTP site/folder is to use an Query - Drilling URL - Attachment URL- URL Type = External URL. If I set the URL Type to Internal URL, I get the error message "URL Identifier {URL Name} in request is not of record type".
The problem with using the External URL as the URL Type is that the URL definition contains the user name and password in it. When you perform an "inspect element" in the Chrome browser, you can see that the User Name and Password is available for anyone to see. The user name and password will also appear in the browser tab if the target document is not found in the URL site (FTP URL).
I was hoping I could abstract the user name and password with the URL Properties, but I don't seem to be able to get the Query Drilling URL to do anything with the PS URL Properties.
A Drilling URL - Attachment URL - URL Type = Internal URL to a document stored in a URL that is a FILEDB type URL works nicely and only shows the URL reference and the document name reference in the resulting HTML.


