Best Of
Re: Is the TAX UPDATE 25-C's target posting date changed to October 17?
Hello,
I am checking with Development on the date. I will update this community once they respond back to me.
Regards,
Re: Security on User Preferences Tables in PeopleSoft Query
Hi Wendy
The security measures implemented on these tables are part of the standard security model in PeopleSoft to protect sensitive user data and maintain data integrity. These tables often contain personal preferences and settings that are specific to individual users, such as interface customization, default values, and system behavior. Restricting direct access to these tables helps prevent unauthorized modifications and ensures that users can securely manage their own preferences.
The security framework in PeopleSoft allows for granular control over access rights, ensuring that only authorized users or roles can view and modify specific data. While it may add an extra layer of complexity when comparing preferences across users, this is a necessary safeguard to protect user privacy and maintain the system's overall security.
If you need to analyze user preferences for a specific purpose, I recommend exploring the following options:
Utilize PeopleSoft's built-in reporting tools: PeopleSoft provides various reporting functionalities that allow administrators to generate reports on user preferences without directly querying the tables. These reports can be designed to aggregate and present data while respecting the security settings. The User Preferences report (FIN0006) to display information that includes a listing of the preferences that are defined for each user.
Create custom queries. You would need to work with your PeopleSoft Administrator to gain the necessary permissions but then you could create your own PeopleSoft Queries without touching any of the data.
While I understand that removing security from these tables might simplify certain tasks, it is essential to balance convenience with data security and privacy. PeopleSoft's security model is designed to be flexible and customizable, allowing organizations to adapt it to their specific needs while maintaining a robust security posture.
DaveT
Re: how to grant table from database to another database
Hello 12305688,
is "the other database" an Oracle database as well? And do you mean "select data from any table / view" or "select data from some given table(s) only"? (and do you mean "only SELECT" or "do whatever you want (SELECT INSERT UPDATE DELETE, ALTER TABLE, DROP PROCEDURE, …)" or something else?
As a senior IT guy (more than 10 years in the forums) you know that details are important… Please clarify your needs, and specify also the Oracle version(s) used…
As "starting point" I will make some assumptions and illustrate with a simple case.
Requirement: user ABC in a database B needs to read the data of a table DEF.THIS_TABLE in a database A.
Solution: in database B, create a private database link for ABC, pointing to GHI@A; in database A, create a user GHI with just enough privileges (create session + read on DEF.THIS_TABLE). Now in database B, connected as user ABC, I can do: SELECT … FROM def.this_table@mylink WHERE …
Maybe this is enough to reply to your question, maybe you have some more complexity and don't know what to do, then provide more details.
HTH,
Bruno Vroman.
P.S.: note that you can very easily modify your display name to something more human-friendly then user123…; just have a look at , it takes two minutes.
Re: how to grant table from database to another database
Access the Table via the Database Link:
To allow a user in another database to SELECT from a schema (let's say schema_name.username) in your database, you typically use database links and object grants in Oracle.
- On the target database (the one from which you'll be running queries), create a database link to the source database.
CREATE DATABASE LINK example_link
CONNECT TO username IDENTIFIED BY password
USING 'tns_service_name'; - Grant SELECT Privileges
On the source database (where schema.username exists), grant SELECT privileges on the desired tables or views.
GRANT SELECT ON schema.table_name TO username;
- Access the Table via the Database Link
SELECT * FROM schema.table_name@EXAMPLE_LINK;
Re: Two PO's released by the Plan with Same Need by Date on same creation date.
Hi @User_ID376 ,
It is not possible to ascertain the exact reason why two rows are released once the planned orders are released and the plan is re-run. All the details related to the previous planned orders are re-written.
Having said that, these kind of issues happen due to PTF or movement of planned orders due to constraints. In the above scenarios, though the planned orders are originally created at different dates, they might be moved to same date and got released.
The only way to ascertain the cause is to review the plan output on the very same day when the planned orders are released (or before the plan is re-run).
Hope the above helps!
Best Regards,
Mohan Balaji
Re: About statistics on PDB$SEED before upgrade
Yes and if you do, don't forget to mention the answer to the core question of this thread, whether or not you should open the Seed container in write mode. And, if you even can. I think you shouldn't because Seed is Seed … But then you must have a look why this is wrong as it is. Maybe it is just a trailing action because of some earlier upgrade ?
Mr. C
Re: Concurrent Program PRC: Transaction Import
Hi Gene,
You should enter the entire value displayed in the Name field (i.e. '340-HUMAN RESOURCES').
The validation on the organization_name field is: Must be a valid organization in
PER_ORGANIZATION_UNITS.NAME
Thank you!
Sherry
Re: How to pull P6 baseline project activities details from P6 using rest api
@Michael Hilferty-Oracle and @DavidCumming : Thanks for reply and your efforts in looking into this, our current P6 version is 25.4 and its Cloud.
Also, I have found the way to pull this information from rest API and is as below:
From Project End Point, pull below fields:
Name,Id,ObjectId,CurrentBaselineProjectObjectId
And then in Activity End Points, pull requested information with Activity id i.e. , Early Start, Early Finish etc. and pass the filter for ProjectObjectId with value "CurrentBaselineProjectObjectId" received from Project EndPoint.