Configure the SIT in standard Oracle
If you haven't already, you will need to configure the SIT in standard Oracle before you can deploy the SIT in the app. This means you need to have:
- Configured the SIT structure and segments
- Ensure the flexfield structure is frozen
- Enable the SIT (*HRMS Manager: Other Definitions: Special Information Types) by ensuring both Enabled and Other are checked
- Test it in the standard Oracle PUI form to make sure it works
- Create a Base Oracle function that contains the workflow process name (eg, pProcessName=HR_SIT_JSP_PRC) and AME Transaction type parameters (eg, pAMETranType=SSHRMS&pAMEAppId=800). This is typically a copy of HR_SIT_SS with its parameters modified, eg, XXX_HR_SIT_SS.
Create an SIT page
Decide on a suitable page to house your new SIT. You don't need to create one page per SIT; often it's better to group related functionalities together on a single page. For example, you might add an SIT to a Personal information page, or to a Profile page. You may choose to add your SIT to an already-existing page.
To learn how to create pages, please see Pages.
The page must use the {PERSON_ID} Object Id format and xxas_per_pkg.per_and_primary_asg_ctx Object Id handler.
Create an SIT view formula
Copy the XXAS_EMP_PERSONSIT_TEMPL_FF formula and name it appropriately. We recommend the format XXX_BK_<TITLE>_VIEW, eg, XXX_BK_BUSINESS_TRIP_VIEW.
Ensure you date-track back when creating the Fast Formula and use the formula type Applaud HR Assignment.
Create a flexible SIT block
Create a flexible block with the following properties:
Property | Value |
---|---|
Security type | Role and data |
Object | Applaud HR Assignment |
Layout | LIST if multi-row or FORM if a single row |
Data source | Applaud HR Person SIT |
Order by | As per requirements. Eg, CREATION_DATE DESC |
View formula | As created earlier, eg, XXX_BK_BUSINESS_TRIP_VIEW. |
Read-only | Checked if this is a read-only SIT, or unchecked if it's editable |
Form | Person SIT (/public/xxas/emp/view/personsit.xml) Not required if it's read-only. |
Form handler | xxas_person_sit_pkg Not required if it's read-only. |
Base Oracle function | The function you created in your Oracle setup, eg, XXX_HR_SIT_SS. |
Special information type | The SIT structure name, eg, XXX_BUSINESS_TRIP |
Define access control for the SIT
To allow the block itself to be visible, create a Grant:
- Navigate to Grants: Add
- Choose the role that should see the block
- Choose the Object Ids against whom the block should be visible
To allow SIT rows to be visible inside the block, create a Data source grant:
- Navigate to Data source grants: Add
- Choose the role that should have access to SIT rows
- Choose Create a new one under Object Ids
- Specify the instance set title and predicate to limit the rows. For example: &TABLE_ALIAS.person_id = fnd_global.employee_id AND &TABLE_ALIAS.id_flex_structure_code = 'XXX_BUSINESS_TRIP'
To allow a new SIT row to be created, create an Add row grant:
- Navigate to Grants to add a row: Add
- Choose the role that should have access to create a row
- Choose the Object Ids against whom the role can create a row
To allow updating and deleting of a row, edit the Update_Allowed and Delete_Allowed outputs of your view Fast Formula. See Defining the view formula.