Self Service HRMS and AME
- Category: Self Service HRMS and AME
- Created: 29 September 2009
- Written by Anil Passi
As seen in the previous article, the custom AOL function named XXFOCUSTHREAD_SIT_COMPL_FUNC instantiates a Workflow process named
The relationship between the AOL Function and HRSSA workflow is explained in the picture as shown below.
If you recollect, the WF Process name entered in our AOL definition for function XXFOCUSTHREAD_SIT_COMPL_FUNC was HR_SIT_JSP_PRC
This matches the short name of the WF Process "Change Special Information" as shown below
In the previous article you learnt the steps to create a self service HRMS data entry screen using Special Information Types, i.e SIT. This screens leverages OA Framework, however this was achieved without writing any program.
It must be noted that the data entered in this screen is applied to the base tables directly. This is because, by default, the data entered in Special Information Types is not routed via AME Approval. It is important to understand the HRMS Self Service Workflow concepts before we take a dive into AME integration with Self Service HRMS.
Therefore in this article, we will concentrate on the integration of Self Service HRMS workflow with overall Self Service processes in Oracle HRMS. Understanding of this workflow and HR_API_TRANSACTIONS is a pre-requisite before proceeding with AME config for SSHR.
I will try to address the following questions in this context
1. What is the purpose of this workflow in Self Service HRMS
2. How does this workflow dictate the navigation of the user to a specific OA Framework page.
3. How does this workflow control whether AME will be invoked
Firstly, what is the purpose of this workflow in Self Service HRMS ?
There is a historic reason for usage of Workflow named HRSSA in Self Service HRMS. Self Service HRMS product development was done slightly ahead of OA Framework. In the early days of Self Service HRMS, OA Framework did not exist in its current form, and therefore PL/SQL web Cartridges were used for developing the initial set of pages in SSHR. Thereafter AK Developer was used to configure the components of the pages in SSHR. However, Self Service HRMS team was looking for a framework that could give State Management for the data in Web Application. OA Framework was not quite ready by then, therefore Oracle Workflow was hooked onto the Self Service HRMS screens to manage user sessions. Given that workflow instance is persistent in the database tables, therefore the HRMS team was able to leverage the persistency offered by Oracle Workflow for managing the state of Web Pages in Self Service HRMS.
The powerpoint presentation in this link will give you a good idea about how OA Framework evolved in eBusiness Suite.
What is the name of this workflow?
select name, DISPLAY_NAME from wf_item_types_vl where
These screenshots below are from HRSSA Workflow as opened from Workflow Builder, for WF Process named "Change Special Information". This WF Process was attached to the AOL function definition in previous article[Part2]
If you double click on activity "SIT 4.0" in the workflow builder[shown in above picture] and navigate to Node Attributes tab[shown in image below], you will notice that this Workflow Activity calls a JSP page. The page in reality is an OA Framework page. The mapping between the "jsp page name" and the actual "OA Framework page" exists in $PER_TOP/mds/regionMap.xml. regionMap.xml is used to map the legacy[pre-OAF] page name with the OA Framework page name. This mapping file is loaded to the MDS tables during the patching/installation process.
The image below shows the contents of $PER_TOP/mds/regionMap.xml. This file contains the mapping between the "JSP page name in WF Activity" and the OA Framework Page name.
In this article, you learnt how the workflow is integrated within SSHR.
In the next article, we will see the integration points of this Workflow with AME.