Using Transaction Monitor

HR professionals, managers, and workers can use the Transaction Monitor page to track
and view details of the self-service transactions. As the list of all self-service transactions
is available on a single-page, users can efficiently track the status of their transactions.
Users can track transactions using the following status values and view their details.
• Pending Approval
• Complete
• Defer
•Error

Set SSHR Termination\

Perform Business Transactions when Person Type Changes Exist at a Future Date
You can perform the following personnel actions even if person type changes exist for a
person's record at a future date:
• Hire
• Terminate
• Rehire
• Reverse Terminate
See: Performing Business Transactions when Person Type Changes Exist at a Future
Date, Oracle HRMS Workforce Sourcing, Deployment, and Talent Management Guide

Future-Dated Changes
When the application encounters a pending change to the manager's selected person's record,
effective subsequent to the current action's effective date, the future-dated change poses a
potential conflict with the current action. You can manage these potential conflicts by setting the
profile option, HR:Manage Self Service Actions When Future-Dated Changes Exist, to one of
the values below:
• Allow Approval (Notify HR Rep) After completing the chain of approval, a notification of the
transaction will be sent to an HR Representative who can review the change, then apply the
necessary changes to the database manually. You must define a role based on the predefined type
HR Representative, and assign it to each HR manager you want to receive the notification. The
first HR manager to act on the notification and apply manual changes does so on behalf of all HR
Representatives.
• Stop with an Error The manager will be forced to choose an Effective Date subsequent to the
future-dated change.
Important: If you enable the system profile HR:Manage Self Service Actions When Future-
Dated Changes Exist by setting it to Allow Approval (Notify HR Rep), Oracle highly
recommends that you also enable HR:Refresh Self Service Actions with Data from Intervening
Actions. Otherwise you should disable HR:Refresh Self Service Actions with Data from
Intervening Actions.
Note: A system administrator or other implementer of Self-Service Benefits can access the
Change Session Date menu option for testing future dated enrollments. You should remove this
menu item in your production environment so that benefits participants do not alter their
enrollment date. To remove the Change Session Date item from the menu, query the
BEN_SELF_SERVICE_BENEFITS menu option in the Menus window and delete the Change
Session Date menu entry.

Managing Dates in SSHR

Effective Dates

When a user initiates an action the application prompts the user for an effective date.
The user can elect for the changes to take place as soon as final approval is made. Or
the user can supply an effective date. The application checks the hire date and tells the
user to select a later date. The application also informs the user of any pending
changes to that person's record.

The application validates the entry to make sure the data is correct using specific
criteria. The following checks are carried out in a chained process:

 hire_date

Checks that the effective date entered is later than the hire date. If it is not, an
error will be issued and the user will be unable to continue.

 termination_date

Checks that the effective date entered is earlier than the termination date. If it is
not, an error will be issued and the user will be unable to continue.

 pending_workflow

Checks if there are changes pending in the workflow tables for the selected
person.

If there are pending changes, the user will be unable to continue with the action
unless the profile option HR:Allow Concurrent Self Service Actions is set to Yes.

 future_assignment

Checks if there are any future assignment changes with respect to the effective
date entered.
  insert_mode

Issues a warning (alert) only if the effective date of the assignment is less than a
future-dated change.

To configure the outcome of the above checks, see Handling Concurrent

Transactions below.

Handling Concurrent Transactions

The application supports multiple simultaneous actions on the same employee or

worker. To activate this feature you need to set the system profile option HR:Allow
Concurrent Self Service Actions to Yes.

Enabling concurrent transactions can give rise to potential data conflicts from either
intervening actions or actions dated in the future. Two profile options enable you to
control the potentially conflicting data: HR:Refresh Self Service Actions With Data From
Intervening Actions, and HR:Manage Self Service Actions When Future-Dated Changes
Exist.

Intervening Actions

If someone approves an action on an employee or worker while a manager is

performing a transaction on the same employee or worker, and the effective date of the
approved action is prior to the current action's effective date, then a potential conflict
exists. The system profile, HR:Refresh Self Service Actions With Data From Intervening
Actions, enables you to deal with this potential conflict.

 If you set the system profile to Yes, the application displays a warning message
listing the attributes that have been changed by the prior approved action. A
refresh of the current data will occur. The manager will then be able to proceed
with the transaction.
 If you set the system profile to No, the application displays a warning with the
following message: "The database contains future-dated changes to this person's
record. Your current setup does not allow you to complete this action. Contact
your system administrator." The current transaction will fail.

Future-Dated Changes

When the application encounters a pending change to the manager's selected person's
record, effective subsequent to the current action's effective date, the future-dated
change poses a potential conflict with the current action. You can manage these
potential conflicts by setting the profile option, HR:Manage Self Service Actions When
Future-Dated Changes Exist, to one of the values below:
  Allow Approval (Notify HR Rep)

After completing the chain of approval, a notification of the transaction will be

sent to an HR Representative who can review the change, then apply the
necessary changes to the database manually.

You must define a role based on the predefined type HR Representative, and
assign it to each HR manager you want to receive the notification. The first HR
manager to act on the notification and apply manual changes does so on behalf
of all HR Representatives.

 Stop with an Error

The manager will be forced to choose an Effective Date subsequent to the

future-dated change.

Important: If you enable the system profile HR:Manage Self Service Actions When
Future-Dated Changes Exist by setting it to Allow Approval (Notify HR Rep), Oracle
highly recommends that you also enable HR:Refresh Self Service Actions with Data from
Intervening Actions. Otherwise you should disable HR:Refresh Self Service Actions with
Data from Intervening Actions.

Deleting a pending transaction in SSHR

Oracle has provided a profile option to allow deletion of pending transaction in SSHR(including absence).
HR:Enable Initiator to Delete a Pending-Approval Transaction
I needed to do this when the client requested for one of the transactions to be deleted, as the transaction
went to an inactive approver.

When you set this profile option to Yes at any one of the levels: site, application, responsibility (Manager
Self-Service and Employee Self-Service) or at the user level, the Delete icon is enabled on the following
pages:

 All Actions Awaiting your Attention (Employee Self-Service responsibility)

 Personal Actions (Employee Self-Service responsibility)
 All Actions Awaiting your Attention (Manager Self-Service responsibility)
 Manager Actions (Manager Self-Service responsibility)

Initiators can view the transactions in the Pending Approval stage and delete the transactions prior to
approval.
When an initiator deletes a transaction that is pending approval, Oracle SSHR performs the following
actions:

 Closes all the notifications associated with the transaction from the worklist and All actions
Awaiting Your Attention region.
 Removes the transactions with the Pending-Approval stage from the initiator's list of actions.
 Deletes the transaction from the HR_API_TRANSACTIONS table.
reference: 
https://oracle.pomeroy.com/OA_HTML/help?navId=2&navSetId=iHelp&locale=en&vtTopicFile=iHelp/
HelpServlet/US/PER/%40sdelpent