When a Self Service HRMS user creates any data from the screens, such data goes and resides in some temporary tables. This data is retained within the temporary tables until the transaction is Completed. A transaction in this example gets completed when Holiday Rejection complaint is either Rejected or Approved. These temporary table names begin with name HR_API%. In reality, the data entered by the user is either stored within just one table i.e. HR_API_TRANSACTIONS or within HR_API_TRANSACTION_VALUES. When the data is stored in just the HR_API_TRANSACTIONS then the entire data entered by the user is captured in a CLOB column. This feature was introduced couple of years ago, whereby for performance reasons the temporary data is captured in a clob column named HR_API_TRANSACTIONS within HR_API_TRANSACTIONS. This CLOB column contains XML contents. By now, you might have the following questions
In this article we will undertake a simple example for AME customization in iRecruitment. This example pertains to Vacancy creation process in iRecruitment.
In the last three AME articles we learnt
1. Basics of AME
2. How SSHR is attached to HRSSA Workflow and AME
3. How to create FND User for AME with necessary RBAC
Assign AME Roles and Responsibilities
1. Navigate to User Management Responsibility->Users and search for the user to whom you wish to grant AME roles. (Can navigate from any user which has Security Administrator Role or from SYSADMIN user).
Oracle Self Service Human Resources (SSHR) is all driven by a single workflow. The name of this workflow is HR and its short code is HRSSA. The workflow is kicked off as soon as any business activity is initiated in Self Service HRMS. This workflow can be customised to initiate AME for the generation of approval lists.
Let’s take approvals of Competencies for example. As standard when employees enter their Competencies, they don’t need approval. As a Professional Services consultancy, we need changes to Competencies approved so Line Managers are aware of their employee’s skill sets. As soon as you open the Competency Profile screen the HRSSA workflow is fired up.
When user clicks on SSHR Menu Item, the name of the workflow process is passed as a parameter to the form function. Therefore, the sequence of events are
- User clicks on a menu in SSHR responsibility
- Form Function attached to Menu is invoked.
- This Form Function invokes AK Region HR_CREATE_PROCESS_TOP_SS [See Web HTML of Form Function HR_PERINFO_SS]
In this article you will understand the basic concept of AME. This article will lay the foundation of some of the AME examples in iRecruitment and SSHR that will be covered.
What is AME?
AME by definition is a Approval Management Engine that Builds a list of approvers for a specific transaction using business rules. However in simple words, AME is a “IF THEN….ELSE….END IF” condition – wrapped into an API.
That’s exactly what AME is. It is a IF THEN ELSE CONDITION wrapped up into a lets say Function Call to produce a list of approvers. The complexities are taken care of by the Approval Management Engine itself. However this “IF CONDITION” definition holds true when talking about the simplest possible definition of AME. Therefore if you can understand “IF Condition”, then you can understand AME. Further to that, if you know how to write IF Conditions and how to write SQL, then you will be able to implement most of the AME Business requirements with ease. Lets have a look into IF CONDITION from another perspective.
· Eligibility/Rate Factors
- Benefits Group BEN_BENFTS_GRP
- Derived Factors BEN_COMP_LVL_FCTR
- Postal/Zip BEN_PSTL_ZIP_RNG_F
- Service Areas BEN_SVC_AREA_F