This section provides the information you need when configuring your own functions. It tells you how self service functions are defined in the Forms user interface, and lists each menu function parameter, together with the parameter use.
For more information on configuring functions see Guidelines for Configuring SSHR Functions.
The function type for all SSHR functions is SSWA JSP FUNCTION (JSP). The Context Dependence is Responsibility. The Maintenance Mode Support is not relevant to self-service functions. These values should be copied into your own functions.
A function Web HTML call has the following format:
OA.jsp?akRegionCode=HR_CREATE_PROCESS_TOP_SS&akRegionApplictionID=800&OAFunc=HR_CHANGE_JOB_SS
where the Web HTML call parameters listed in the Forms user interface are separated by "&".
All functions that end in "_SS" (but not those ending in "_MGR_SS") use the following parameters, which are described in greater detail below:
pAMETranType=SSHRMS
pAMEAppId=800
pProcessName=WORKFLOW_PROCESS_NAME
pItemType=HRSSA
pCalledFrom=EDA_FUNCTION_NAME
pEffectiveDate=
The following table describes all available menu function parameters:
Note: References to "_SS" functions exclude "_MGR_SS" functions.
| Parameter | Description |
|---|---|
| OAFunc=<function>_SS | Add this parameter to all the self service _SS functions, providing your own function name. This parameter enables you to do personalization for a specified <function>_SS level. |
| pAMEAppId=800 | Add this parameter to all the _SS functions that contain pAMETranType=SSHRMS to specify the application Id for the transaction type. |
| pAMETranType=SSHRMS | Add this parameter to all functions that use AME to process approvals. The parameter provides the transaction type name of SSHRMS. If you define your own transaction type provide that transaction type name here. |
| pCalledFrom=EDA_FUNCTION_NAME | Add this parameter to all the _SS functions that are launched through workflow. It indicates which function calls the current function. Replace EDA_FUNCTION_NAME with the corresponding _SS function name. |
| pDestination=HR_ACTIONS_SS | Add this parameter to the _MGR_SS functions if the workflow process attached to this function can navigate through the Actions page. |
| pEffectiveDate= | Add this parameter to the _SS function if this function needs the effective date field to be displayed in the actions screen. No value should be set. |
| pFlowName=<processname> | Use this parameter for functions that require special processing. The process names are "COBRA Registration", "Benefits Registration" & "New Hire". |
| pGroupName=<documentgroupshortname> | Use this parameter to provide the Document Group short name for a PDF merge |
| pItemType=HRSSA | Add this parameter to all the _SS and _MGR_SS functions to provide the Item Type. |
| pManagerEnabled=N | Add this parameter to _MGR _SS functions if managers are not allowed to select themselves in the hierarchy tree; the Action icon for the logged-in manager will be disabled. |
| pMode=<value> | Add this parameter to your manager or personal action functions with the value of LMDA for manager action functions and EDA for personal action functions. |
| pPayRate=Y | Use this parameter to validate pay rate related transactions. If this parameter is set to Yes, then only SSHR performs pay rate validations. |
| pProcessName=WORKFLOW_PROCESS_NAME | Add this parameter to all the _SS functions that are launched through workflow. Replace WORKFLOW_PROCESS_NAME with the corresponding workflow process name, for example HR_PERSONAL_INFO_JSP_PRC . |
| pSalChange=Y | This parameter indicates that the process is purely a Salary Change process and does not include Assignment Pages. An appropriate message will be presented on the Effective Date page. If this parameter is absent it defaults to 'N', which indicates that the process includes Assignment related pages. |
| addBreadCrumb=Y | Add this parameter to MGR_SS functions or Enter Process functions if you want to display a navigation link, or breadcrumb, on the page. |
| pEnableTerms=Y | This parameter enables users to include ex-employees (terminated employees) in a person search. This parameter is enabled for selected Manager and Professional functions with a default setting of Y. |
| pRehireReco=Y | When managers search for ex-employees to rehire them using the Applicant Hire and Rehire function, by default the search result displays ex-employees whose rehire is recommended and whose rehire is not recommended. Add this parameter to the Applicant Hire Mgr (HR_APPL_HIRE_MGR_SS) function to display only ex-employees whose rehire is recommended. See: Applicant Hire and Rehire |
| pNtfFyiDetails=Y | Add this parameter to _SS functions to enable notification recipients to view transaction changes on the FYI Notification page after transactions are either approved or rejected. If this parameter is set to Y, then the FYI Notification page displays a Details region with the Proposed column and a Supporting Documents region. If any attachments are added to a transaction's Review page, then these attachments appear as a link on the FYI Notification page. For example, after a manager approves a leave of absence transaction, the recipient who receives the FYI notification can view the absence details that have been approved. The recipient need not navigate to the relevant self-service pages in the application to understand the changes that have been approved. The FYI notifications retrieve information from the transaction table and not from the base table. Therefor if transaction data is dependent on base table and base table data is deleted, then relevant data is not displayed in FYI notifications. Note: If you set this parameter, it is recommended that you schedule the Complete Defunct Workflow process to run with "AC" (Approval Complete ) status to delete completed transactions. For example, you can delete completed transactions that are about 15 or 20 days earlier than the current date. |
| &pQkFn=Y | Add this parameter to the self-service functions to hide the Effective Date page in the self-service transactions flow. For information on how to use this parameter, see: Control the Display of the Effective Date, Review, and Confirmation Pages for Self-Service Transactions |
| &pBpRv=Y | Add this parameter to the self-service functions to hide the Review page in the self-service transactions flow. If this parameter to hide the Review page is set to Y, then for the last page in the relevant process, the 'Last Page in Flow' attribute must be set to Yes using Oracle Workflow Builder. This indicates that the specific page is the last page in the transaction and the Review page is not available. Another Node attribute "Approval Required Flag" must be set for the same last page node to decide whether "Approvals" are required for that functionality or not. Note: Note that if either &pQkFn or &pBpRv parameter is set to Y, then the Confirmation page is automatically hidden. If you plan to hide the Review page and approvals are required for the function, then it is not possible to view the list of reviewers or track the approval process. Also, any additional functionality available on the Review page such as adding comments, viewing list of approvers, or adding attachments to transactions will not be available. For information on how to use this parameter, see: Control the Display of the Effective Date, Review, and Confirmation Pages for Self-Service Transactions |