The app delivers specialized support for Person Special Information Types (SITs), Person Extra Information Types (EITs), and Assignment Extra Information Types. It can be configured to allow users to view, create, update and delete SIT and EIT data and it supports routing of transactions using Oracle workflow with Approvals Management (AME).
Information Types Support
SITs and EITs are commonly used throughout Oracle E-Business Suite to support a wide variety of business processes. Since they are built on a flexfield architecture, they are a useful tool for implementers wanting to model processes not supported by "out of the box" Oracle. Implementers can use a combination of Valueset validation, user hook validation, and AME rules to create custom processes with unique business rules and approval chains.
The app supports this flexible architecture by supporting:
EITs and SITs are based on a flexfield definition. The app automatically detects this definition and renders the SIT and EIT forms accordingly. Segments that are configured to be hidden will not display; segments that are marked as required will display with an asterisk (to indicate a mandatory field) and so on.
The app supports advanced flexfield features, such as cascading defaults and $FLEX$ references.
When displaying an SIT or EIT form for creating or updating a row, the app looks at the value sets that have been attached to each segment and renders each field appropriately. For example, a segment based on a Date value set will display with a date field; a segment based on a List of Values will display with a Select-single field, etc.
When SIT and EIT data is transacted, the standard Oracle HRMS APIs are called. If you have created PL/SQL-based user hooks to perform custom validation, then these will be called when the user submits their changes. Similarly, if you have created custom triggers against the Oracle Tables (not recommended by Oracle), these will also fire when the API attempts to transact the data onto the tables.
If a business rule is violated, the error will be shown within the app and the user will be required to modify their data or discard their work.
When you configure an SIT or EIT to support creating, updating, or deleting, you link it to the Base Oracle function that contains the Oracle Workflow process name and Approvals Management transaction type. This is used at run-time to invoke the right workflow. The app will automatically work out the correct approvers to route the transaction to and display the approval chain to the user. The app supports AME rules that specify multiple approvers or approver groups; the appropriate information will be shown when the transaction is submitted.
When an SIT or EIT transaction is submitted, the Oracle Workflow process is initiated as described above. Notifications are sent to users in the regular way which can then be approved via the standard Oracle worklist on the in-app worklist.