The Peoplesoft doc uses SYSADM as the example when creating the Owner ID in the doc, and most people follow the examples in the doc so this may be why you see SYSADM as the Owner ID, but it does not have to be SYSADM. It can be any ID you want to make up, for example P854DEV or P854PRD, etc.
For example in Oracle you can use P854DEV as the owner ID of our PeopleTools 854 dev database, and this becomes the high level qualifier of the tables.
This way I do not have to give out the SYSADM password
See Install doc Task 1-4-2, page 39
A PeopleSoft database is a set of SQL objects defined as having the same owner ID. These tables are always contained within a single Oracle database.
A PeopleSoft database includes the PeopleSoft objects and application data for one or more products in a PeopleSoft product line.
This owner ID (an Oracle user ID) may also be referred to as an Oracle schema or Oracle logical database.
Each PeopleSoft database needs its own owner. We refer to this as the PeopleSoft owner ID, which is also the PeopleSoft access ID.
To create the ID see Install doc Task 6A-10, page 171
To create the PeopleSoft database owner ID:
1. Log on to SQL*Plus, connecting as the System user.
sqlplus system/manager
2. Run the PSADMIN.SQL script.
SQLPLUS>@<PS_HOME>\scripts\nt\psadmin.sql (for Non-CDBs)
SQLPLUS>@<PS_HOME>\scripts\nt\pdb\psadmin.sql (for CDBs)
The doc numerous times show the Connect ID and Owner ID as SYSADM (see attachment), but it does not have to be this name.
The Stat code does more than READ access in the code (sometimes INSERT, UPDATE, CREATES, etc) so we need to list the Owner ID to accomplish this, but we do not need to give the users the password for this Owner ID.
Yes, you can give the users any other ID to go into Toad and just have the DBA grant READ access to all tables to that ID.
