1. The loader does not use any of the below conditions when searching the list of values or where the HR_ALL_POSITIONS_F table is used as a part of the query.
- DECODE(HR_SECURITY.VIEW_ALL,
'Y','TRUE',
HR_SECURITY.SHOW_RECORD('PER_ALL_POSITIONS',PSF.POSITION_ID)
)='TRUE'
- DECODE(HR_SECURITY.VIEW_ALL,
'Y','TRUE',
HR_SECURITY.SHOW_RECORD('HR_ALL_ORGANIZATION_UNITS',PSF.ORGANIZATION_ID)
)='TRUE'
- DECODE(HR_GENERAL.GET_XBG_PROFILE,
'Y',PSF.BUSINESS_GROUP_ID,
HR_GENERAL.GET_BUSINESS_GROUP_ID) =PSF.BUSINESS_GROUP_ID
Where, PSF is HR_ALL_POSITIONS_F Oracle table.
2. On the Oracle form under ‘Position Reporting To’ section, the Hierarchy search shows only those lists of values that are not yet assigned to the position. In the loader we cannot implement the same functionality. Instead, the loader shows all the Hierarchy including the Hierarchy that may have already been assigned. It is the loader limitation that cannot hide the assigned hierarchies in the list of values.
3. Due to supported Oracle API limitation, Valid Grade section has only ‘Create’ upload action available.
4. The Oracle form restricts user from creating or updating the Occupancy detail (via Others… > Occupancy). The same rule is applied to the loader. The Occupancy section in the loader is read-only.
