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.

Here is the SQL that you can run against you database to list out all the roles and the permission lists attached to those roles.

SELECT A.ROLENAME, A.DESCR, A.DESCRLONG, B.CLASSID, C.CLASSDEFNDESC
FROM PSROLEDEFN A,
  PSROLECLASS B,
  PSCLASSDEFN C
WHERE A.ROLENAME = B.ROLENAME
  AND B.CLASSID = C.CLASSID

Hi Rosemary,

We have used Data Archive Manager for PSHUP table transactions in past, you can follow below listed steps and implement PSArchive job.

Similarly you need to setup run control id for a Delete (from base table) job, create psquery, select archive number and schedule right after archive run control id. This job will delete data set based on archived data number.

so while scheduling make sure to update archive number input in delete job using Post AE or Pre AE customization to get updated for identifying next archive number. This is the important logic to make sure we schedule these jobs.

 Create History Table:

• Duplicate PSHUP_TXNS in Application Designer, name it PSHUP_TXNS_H.
• Add PSARCHIVE_SBR subrecord as first field.
• Build table with indexes.

 Define Archive Object:

• Go to PeopleTools > Data Archive Manager > Manage Archive Objects.
• Create object (e.g., HUP_TXNS), set PSHUP_TXNS as base, PSHUP_TXNS_H as history.
• Include related child tables if applicable.
• Save.

 Create Archive Query:

• In Query Manager, create ARCHIVE_PSHUP_TXNS (Archive type, Public).
• Select PSHUP_TXNS, add criteria (e.g., PROCESS_DT < :1).
• Save and test.

 Create Archive Template:

• Go to PeopleTools > Data Archive Manager > Manage Archive Templates.
• Create template (e.g., HUPTXNS, max 8 chars).
• Link archive object (HUP_TXNS) and query (ARCHIVE_PSHUP_TXNS).
• Save.

 Run Archive Job:

• Go to PeopleTools > Data Archive Manager > Archive Data to History.
• Create job, select template (HUPTXNS).
• Choose Selection (copy) or Delete (copy and delete).
• Set commit intervals, enter bind parameters (e.g., date).
• Submit via Process Scheduler.

 Verify Results:

• Query PSHUP_TXNS_H to confirm archived data.
• Check row counts against archive query results.
• Review audit log in Data Archive Manager > Audit Archiving.

 Restore Data (Optional):

• Create restore query (e.g., RESTORE_PSHUP_TXNS) for PSHUP_TXNS_H.
• Update template with restore query.
• Run restore job via Archive Data to History.

 Best Practices:

• Archive old data (e.g., >5 years for compliance).
• Use small batches, schedule off-peak.
• Test in non-production first.
• Check compatibility during upgrades.

Thanks,

Kiran.

Rosemary - Please refer below post in case if you are in higher PUM version.

Paysheet Update Enhancement - how we are using it — oracle-mosc

-Velu

Please see PeopleBooks > Administration Tools > Data Management > Using PeopleSoft Data Archive Manager

https://docs.oracle.com/cd/F86650_01/pt859pbr5/eng/pt/tadm/UnderstandingPeopleSoftDataArchiveManager-077a9f.html