Registering Approval Transactions
To register approval transactions, use the Register Transactions (EOAW_TXN) component.
These topics provide an overview of the approval transaction registry and list prerequisites.
Page Name |
Definition Name |
Usage |
---|---|---|
EOAW_TXN |
Register approval transactions in the Approval Framework by creating a unique approval process identifier for each approval transaction. The transaction definition is the metadata that describes the transaction setup to the Approval Framework. |
The approval transaction registry is the interface that developers use to register a PeopleSoft application's transaction with the Approval Framework. Using the Register Transactions page, developers define how the system interacts with portions of the application that have been defined for approvals. Transactions that require approvals are candidates for being linked to the Approval Framework. Developers can use the Register Transactions page to link the components, event handler, records, and classes that they created through PeopleTools Application Designer for an application transaction (such as a job offer or employee absence request) into the approval process. The transaction definition itself is the metadata which describes the transaction make up to the Approval Framework. In some cases, you might add a transaction or make changes to a transaction. Application developers can register the main records and components that make up the transaction, then functional business analysts can select the approval transaction on which to base the approval process definition.
Delivered Approval Transaction Process IDs
PeopleSoft HCM delivers several approval transaction process identifiers that are common across applications for use with the Approval Framework. The system uses these process IDs specifically for registering delegation-related transactions with the Approval Framework so that the approval framework, which handles the requests, can communicate back and forth with the delegations framework.
When registering approval transactions with the Approval Framework on the Register Transactions page, you must specify a header record for the approval transaction. When you are configuring these process IDs in the Configure Transactions component, you can use this header record and any of the listed fields to define additional criteria for the processing of the approval transaction. You define this additional criteria on the Criteria Definition page, which is accessible through the Configure Transactions component. Fields not listed on the Register Transactions component are not available for the criteria definition.
This table lists the approval transaction process IDs that PeopleSoft HCM applications deliver:
Process ID |
Description |
---|---|
AM_Extended_Abs |
Extended Absence |
Abs Mgmt - Leave Donations |
Leave Donations |
AbsenceCancelation |
Absence Cancelation |
AbsenceManagement |
Absence Management |
Absence_Mgmt_ByDeptManager |
Absence Management By Department Manager |
Absence_Mgmt_ByPosMgmt |
Absence Management By Position Management |
Absence_Mgmt_ByPosnDeptMgr |
Absence Management By Position - Department Manager |
Absence_Mgmt_ByPosnSupervisor |
Absence Management By Position - Supervisor |
Absence_Mgmt_BySupervisorId |
Absence Management By Supervisor ID |
AddressChange |
Address Change Approval |
AdhocSalaryChange |
Adhoc Salary Change |
ApproveCompensationProposals |
Approve Compensation Proposals |
Delegation |
Defines delegation transactions for the Approval Framework. |
DelegationBatch |
Defines batch delegation transactions for the Approval Framework. |
DelegationNotifyAdmin |
Defines delegation transactions for the Approval Framework where the administrator gets notified. |
DelegationRevoke |
Defines revoked delegation transactions for the Approval Framework. |
FTPTChangeEmployee |
Full/Part Change Status in eProfile Manager |
FederalAddrChg |
Federal Address Change Transaction |
FederalFTPTChange |
Federal Full / Part Time Change |
FederalLocationChg |
Federal Employee Location Change |
FederalMarChg |
Federal Marital Status Change Transaction |
FederalNameChg |
Federal Name Change Transaction |
FederalPromoteEmployee |
Federal Employee Promotion |
FederalReassignEmployee |
Federal Employee Reassignment |
FederalRetireEmployee |
Federal Employee Retirement |
FederalRportingChg |
Federal Employee Reporting Change |
FederalSeparateEmployee |
Federal Employee Separation |
FormApproval |
Form Approval |
GPCN_Payroll_Approval |
Payroll result approval process |
GSSAdhocSalaryChange |
Guided self-service ad hoc salary change transaction |
GSSDemoteEmployee |
Guided self-service demotion Transaction |
GSSFTPTChangeEmployee |
Guided self-service change full time / part time status transaction |
GSSLocationChange |
Guided self-service location change transaction |
GSSPromoteEmployee |
Guided self-service promotion transaction |
GSSReportingChgEmployee |
Guided self-service reporting change transaction |
GSSRetireEmployee |
Guided self-service retirement transaction |
GSSTerminateEmployee |
Guided self-service termination transaction |
GSSTransferEmployee |
Guided self-service transfer transaction |
JPMNonpersonProfiles |
Non-person Profile |
JPMPersonProfiles |
Person Profile |
JobOffer |
Job Offer |
JobOpening |
Job Opening |
LocationChange |
Location change |
MaritalStatusChange |
Marital Status Change Approval |
MatrixTeam |
Matrix Team |
MilitaryRankChange |
Military Rank Change Approval |
NameChange |
Name Change Approval |
Payroll-Updatable W4 |
W4’s submitted by employees |
PerformanceManagement |
Appraisal Transaction Approval |
PromoteEmployee |
Promotion Transaction Approval |
ReportingChgEmployee |
Reporting Change Transaction Approval |
RetireEmployee |
Retire employee |
TLOvertimeRequest |
TL Overtime Request Process ID |
TLPayableTime |
TL Payable Time Process ID |
TLReportedTime |
TL Reported Time Process ID |
TerminateEmployee |
Terminate Transaction Approval |
TransferEmployee |
Transfer Transaction Approval |
BenefitsDocumentFiling |
Benefits Document Filing |
Note: Refer to the corresponding documentation in your application-specific documentation for information about delivered approval transaction process IDs that are specific to an application.
Note: Any PeopleSoft delivered approvals will already have the Approval Transaction Registry populated. No additional configuration is typically needed.
Before registering approval transactions, you must create all of the required objects in PeopleTools Application Designer.
To complete the prerequisites for defining the approval transaction registry:
Create a Transaction Handler Application class that extends an approved event handler class delivered by approval workflow.
Create notification templates for the events, which include approval and denial for header and line levels.
Create transaction data sources, as needed.
Create views on transaction tables that will serve as criteria sources.
Create a view to serve as a source for ad hoc users.
Create a view to serve as a source for approver contact information.
Note: Oracle PeopleSoft delivers Notification Composer Framework to manage the setup and administration of all notifications in one central location.
Once you have adopted the Notification Composer feature, you must use it to create new notifications and manage your existing notifications.
Notifications delivered with HCM Image 47 or later must use Notification Composer.
For more information about Notification Composer Framework, see Understanding Notification Composer.