This chapter discusses how to:
Review LDAP directory data.
View PeopleSoft Directory Interface reports.
Manage transaction audit history.
This section discusses how to:
Run a directory audit.
Run a directory search.
Page Name |
Object Name |
Navigation |
Usage |
Directory Audit |
EO_RUNCTL_DS_AUDIT |
Enterprise Components, Directory Interface, Run Directory Audit |
Run the Directory Audit process. |
Directory Search |
EO_DSSRCHDIRECTORY |
Enterprise Components, Directory Interface, Search Directory |
Define search parameters to query the directory. The page saves the search parameters for future use. |
Access the Directory Audit page.
Use the Directory Audit process to ensure that your directory database has the same data as your PeopleSoft database. The Directory Audit process compares the data in the directory to the data in the PeopleSoft database identified in the selected map and creates an LDAP Data Interchange Format (LDIF) file containing any discrepancies using PeopleSoft as the authority. You can then use the LDIF file to update the directory.
Note. For HRMS customers only, there is an alternative process named DSMAPINPUT FullSync Audit that you can use in place of the Directory Audit process. This new process does not replace the Directory Audit process; it is provided as an alternative to audit the data if performance becomes an issue.
See PeopleSoft Enterprise HRMS Application Fundamentals PeopleBook
Map Name |
Select the name of the map that the audit should be run against. |
Access the Directory Search page.
Use the Directory Search page to define search parameters to query the directory and view the results. Search results are displayed on the Search Results page as they appear in the directory.
Search Name |
Enter the search name. The system saves the search parameters that you enter on this page and stores them under this name for future use. |
Directory Search Parameters
Search Base |
Select the directory entry that is the search base for this search. The search base is the entry in the directory information tree at which the search begins querying. |
Search Scope |
Select from: Base: The query searches only the value in the Search Base field. One: The query searches only the entries one level down from the value in the Search Base field. Sub: The query searches the value in the Search Base field and all entries beneath it. |
Build Filter
Use the fields in the Build Filter group box to create an attribute-specific filter. For example, if you want data on a single person, enter the attribute name Person, the operation =, and enter the person’s name in the Value field. You can construct multiple filters.
( ) |
Use parentheses to separate filter statements. |
Attribute Name |
Enter the name of the attribute whose data you want to filter. |
Operation |
Select an operator to determine how to filter the data. |
Value |
Select a value to compare against when filtering. |
And/Or |
Select from:
|
Search Filter |
You can narrow the search (for example, instruct the system to search for all attributes but one) by entering a search filter. Enter the search filter using standard LDAP protocol. You can specify one or more attributes to search for. To search all attributes, enter an asterisk ( * ). For more information about the LDAP protocol, see your directory documentation. |
Search Attributes
Directory Attribute |
Select the attributes to search for. Leave this field blank to search all attributes. |
This section discusses how to:
View the directory audit report.
View the business interlink status report.
Page Name |
Object Name |
Navigation |
Usage |
Directory Audit Report |
EO_RUN_DS_AUD_RPT |
Enterprise Components, Directory Interface, Audit Report |
Generate the Directory Audit report. |
Directory BI Status Report |
EO_RUN_DS_BI_RPT |
Enterprise Components, Directory Interface, Bus Interlink Status Report |
Generate the Directory BI Status report. |
Access the Directory Audit Report page.
The Directory Audit SQR report (EO_DS001) locates and reports discrepancies between the PeopleSoft database and your directory. Before you can run the Directory Audit report, run the Directory Audit process. The Directory Audit process populates a comparison record containing the data that differs between the PeopleSoft database and the directory and creates an LDIF file with this data that can be used to update the directory. The Directory Audit report is based on this record, so you can verify what will be updated in the directory if you apply the LDIF file.
The report generates the following errors:
The distinguished name is not found in the directory.
The distinguished name is not found in PeopleSoft.
The attribute is in PeopleSoft but not in the directory.
The attribute is in the directory but not in PeopleSoft.
The value is in PeopleSoft but not in the directory.
The value is in the directory but not in PeopleSoft.
Access the Directory BI Status Report page.
If you selected an output type of Business Interlinks when setting up maps to associate PeopleSoft fields to directory attributes, the system uses PeopleSoft Business Interlinks to modify the directory. If errors are produced as a result of the interlinks, the system writes the errors to an error record. The Business Interlink Status SQR report (EO_DS002) retrieves and presents the data contained in this error record.
Delete History Error Rows for MAP |
Select to delete historical error rows for this map after reporting them. The PS_EO_BILOAD_ERR record retains error data for this map until you run the report with this check box selected. |
Run |
Click Run to run the report using PeopleSoft Process Scheduler. |
See Also
Enterprise PeopleTools 8.48 PeopleBook: PeopleSoft Process Scheduler
This section discusses how to:
Run a transaction history report.
Search for a transaction history.
Purge transaction history.
Page Name |
Object Name |
Navigation |
Usage |
Transaction History Report |
EODS_RUN_AUDIT |
Enterprise Components, Directory Interface, Audit History, Run Report |
Generate a transaction history report. |
Transaction History Inquiry |
EODS_AUDIT_HIS_IN |
Enterprise Components, Directory Interface, Audit History, Transaction Inquiry |
Search for a transaction history. |
Purge Transaction History |
EODS_RUN_ADT_PURGE |
Enterprise Components, Directory Interface, Audit History, Purge Transactions |
Purge audit history data. |
Access the Transaction History Report page.
Map Name |
Select a Directory Entry Map name. |
User ID |
Select the user ID. |
Status |
Select the status of the transaction. Valid values are Successful or No Success. |
Output Type |
Select the type of output. Valid values are File Format or Business Interlink. |
Transaction Type |
Select a type of transaction. Valid values are Add, Delete, and Update. |
Directory Attribute |
Select the attribute of the entry being defined that will contain all the members of this entry. This attribute must be valid for the current entry in the directory. The employees that satisfy the entry membership rules of this entry are added under this entry as a new value of this attribute. Because of this, there will be as many attribute values as there are employees satisfying the entry membership rules. If this field is left blank, the application uses member as a default attribute name. |
Access the Transaction History Inquiry page.
Use the Transaction History Inquiry page to run a query that displays in the browser rather than create a report that runs using Process Scheduler.
Map Name |
Select a Directory Entry Map name. |
User ID |
Select the user ID. |
Status |
Select the status of the transaction. Valid values are Successful or No Success. |
Output Type |
Select the type of output. Valid values are File Format or Business Interlink. |
Transaction Type |
Select a type of transaction. Valid values are Add, Delete, and Update. |
Directory Attribute |
Select the attribute of the entry being defined that will contain all the members of this entry. This attribute must be valid for the current entry in the directory. The employees that satisfy the entry membership rules of this entry are added under this entry as a new value of this attribute. Because of this, there will be as many attribute values as there are employees satisfying the entry membership rules. If this field is left blank, the application uses member as a default attribute name. |
Transaction Information Tab
The Transaction Information tab displays information about the transaction including the map name, the status, output type, and transaction type.
Attributes Tab
The Attributes tab displays information about the transaction including what directory audit action was performed, the type of directory attribute, and the attribute value.
DN Details Tab
The DN Details tab displays the distinguished name of the transaction.
Access the Purge Transaction History page.
Use the Purge Transaction History page to purge audit history data based on the date range that you enter in the run control page.