Task – To create a Medical Reimbursement form on SSHR screen so the employees can easily update their medical bills every month and their
manager can approve these bills and at the end of the month a process have to be run which will transfer these bills into employee’s payroll elements
so before payroll run these bill should be updated
Step 1 – Creating SIT
Login in as System Administrator -> Flexfield -> Key -> Segments
Search for Application (Human Resources) and Flexfield Title (Personal Analysis Flexfield)
Define a new row, we can call it MEDICAL_REIMBURSEMENT_KFF and the description can be Job Requests.
Next we click on "Segments" to define the form fields to be used in the application.
Field - ValueSet
=============
Employee Name LOV
Nature of Sickness LOV
Details of Sickness 30Char
Hospital Name 30Char
Date FND_STANDARD_DATE
Amount Allowed CRL_YES_NO
Amount Number
Then we save and compile.
Next, login as Global Super HRMS Manager. And look for the function "Define Special Information Type". Find the one we just created
MEDICAL_REIMBURSEMENT_KFF and check the "Enabled" and "Other" checkboxes and save.
Step 2 – Configure WorkFlow Process
Change the node attribute of HR_SIT_JSP_PRC seeded WF to Yes or Yes Dynamic
or
Copy the seeded workflow
open Workflow builder, login Open the HR item type. Under processes, find HR_SIT_JSP_PRC workflow process as a template Copy it, and paste.
When pasting, the internal name should be MEDICAL_REIMBURSEMENT_SIT_PROC_JSP_P (i.e the name of our new workflow process). The
display name can be Medical Reimbursement.
Save the workflow locally and upload it via WFLoad command
Step 3 – Define Function
After this, we go back into SysAdmin and go to Application -> Function
The function can be:
Function, User Function Name, Description
==================================
MEDICAL_REIMBURSEMENT_PROCESS., TEST Job Request Process, Special Information Types
Under the properties tab, we have:
Function, Type, Maintenance Mode, Context dependence
===========================================
MEDICAL_REIMBURSEMENT_PROCESS., SSWA jsp function , None, None
Under the Form tab we have
Parameters
==========
pAMETranType=SSHRMS&pAMEAppId=&pProcessName=
MEDICAL_REIMBURSEMENT_SIT_PROC_JSP_P&pItemType=HRSSA&pCalledFrom= MEDICAL_REIMBURSEMENT_PROCESS
&pPersonID=&pFromMenu=Y
Under the Web HTML tab, we have
HTML Call
=========
OA.jsp?akRegionCode=HR_CREATE_PROCESS_TOP_SS&akRegionApplicationId=800&OAFunc= MEDICAL_REIMBURSEMENT_PROCESS
MEDICAL_REIMBURSEMENT_SIT_PROC_JSP_P is the name of the workflow process we created earlier.
pCalledFrom and OAFunc must be the function name
save & Exit.
Step 4 – Map Function with Menu
Next is to add this function (Medical Reimbursement) to the Menu for TEST Employee Self Service.
Then we also need to open the menu "Global Self Service Functions Custom". And add our function to it as well under the function column.
Next we now navigate to our function and we have to personalize the page for it.
Step 5 – Personalize the Page
After this, we have to personalize the page:
/oracle/apps/per/selfservice/specialinformation/webui/PersonSitPG
to only show our SIT at functional level.
To do this, we will click on our new function in SSHR. But this will show all of the SIT's available which is quite a lot.
So on this page, we click on the "Personalization" link at the top.
Then from here, we find the column "Flex: Key flex for Sit" near the very bottom click the pen image to personalize the page.
Now, on the next page that shows up, find the "Segment List" column.
For this field, we enter values under the function header in the format:
STRUCTURE 1|Segment 1|Segment 2||Structure 3|Segment 7|Segment 8
So for our example we can have:
MEDICAL_REIMBURSEMENT_KFF | Employee Name | Date | Amount | Hospital Name | Details of Sickness
Step 6 – Setting up AME
The final thing to do is to setup AME rules for this workflow process:
Login as "Approvals Management Business Analyst" and create a new Rule under TEST HR
Combination, Header,
Condition - WORKFLOW_PROCESS_NAME in (HR_SIT_JSP_PRC) or (MEDICAL_REIMBURSEMENT_SIT_PROC_JSP_P) whatever you are using
Actions - Supervisory (one level up) or whatever we want it to be.
manager can approve these bills and at the end of the month a process have to be run which will transfer these bills into employee’s payroll elements
so before payroll run these bill should be updated
Step 1 – Creating SIT
Login in as System Administrator -> Flexfield -> Key -> Segments
Search for Application (Human Resources) and Flexfield Title (Personal Analysis Flexfield)
Define a new row, we can call it MEDICAL_REIMBURSEMENT_KFF and the description can be Job Requests.
Next we click on "Segments" to define the form fields to be used in the application.
Field - ValueSet
=============
Employee Name LOV
Nature of Sickness LOV
Details of Sickness 30Char
Hospital Name 30Char
Date FND_STANDARD_DATE
Amount Allowed CRL_YES_NO
Amount Number
Then we save and compile.
Next, login as Global Super HRMS Manager. And look for the function "Define Special Information Type". Find the one we just created
MEDICAL_REIMBURSEMENT_KFF and check the "Enabled" and "Other" checkboxes and save.
Step 2 – Configure WorkFlow Process
Change the node attribute of HR_SIT_JSP_PRC seeded WF to Yes or Yes Dynamic
or
Copy the seeded workflow
open Workflow builder, login Open the HR item type. Under processes, find HR_SIT_JSP_PRC workflow process as a template Copy it, and paste.
When pasting, the internal name should be MEDICAL_REIMBURSEMENT_SIT_PROC_JSP_P (i.e the name of our new workflow process). The
display name can be Medical Reimbursement.
Save the workflow locally and upload it via WFLoad command
Step 3 – Define Function
After this, we go back into SysAdmin and go to Application -> Function
The function can be:
Function, User Function Name, Description
==================================
MEDICAL_REIMBURSEMENT_PROCESS., TEST Job Request Process, Special Information Types
Under the properties tab, we have:
Function, Type, Maintenance Mode, Context dependence
===========================================
MEDICAL_REIMBURSEMENT_PROCESS., SSWA jsp function , None, None
Under the Form tab we have
Parameters
==========
pAMETranType=SSHRMS&pAMEAppId=&pProcessName=
MEDICAL_REIMBURSEMENT_SIT_PROC_JSP_P&pItemType=HRSSA&pCalledFrom= MEDICAL_REIMBURSEMENT_PROCESS
&pPersonID=&pFromMenu=Y
Under the Web HTML tab, we have
HTML Call
=========
OA.jsp?akRegionCode=HR_CREATE_PROCESS_TOP_SS&akRegionApplicationId=800&OAFunc= MEDICAL_REIMBURSEMENT_PROCESS
MEDICAL_REIMBURSEMENT_SIT_PROC_JSP_P is the name of the workflow process we created earlier.
pCalledFrom and OAFunc must be the function name
save & Exit.
Step 4 – Map Function with Menu
Next is to add this function (Medical Reimbursement) to the Menu for TEST Employee Self Service.
Then we also need to open the menu "Global Self Service Functions Custom". And add our function to it as well under the function column.
Next we now navigate to our function and we have to personalize the page for it.
Step 5 – Personalize the Page
After this, we have to personalize the page:
/oracle/apps/per/selfservice/specialinformation/webui/PersonSitPG
to only show our SIT at functional level.
To do this, we will click on our new function in SSHR. But this will show all of the SIT's available which is quite a lot.
So on this page, we click on the "Personalization" link at the top.
Then from here, we find the column "Flex: Key flex for Sit" near the very bottom click the pen image to personalize the page.
Now, on the next page that shows up, find the "Segment List" column.
For this field, we enter values under the function header in the format:
STRUCTURE 1|Segment 1|Segment 2||Structure 3|Segment 7|Segment 8
So for our example we can have:
MEDICAL_REIMBURSEMENT_KFF | Employee Name | Date | Amount | Hospital Name | Details of Sickness
Step 6 – Setting up AME
The final thing to do is to setup AME rules for this workflow process:
Login as "Approvals Management Business Analyst" and create a new Rule under TEST HR
Combination, Header,
Condition - WORKFLOW_PROCESS_NAME in (HR_SIT_JSP_PRC) or (MEDICAL_REIMBURSEMENT_SIT_PROC_JSP_P) whatever you are using
Actions - Supervisory (one level up) or whatever we want it to be.
