In E-Business Suite, the Job Requisition status is not preserved as historical information in the OLTP. Therefore, as a Job Requisition status changes, for example from 'Drafted' to 'Approved' to 'Open' to 'Closed', the OLTP saves only the last status.
In Oracle Business Analytics Warehouse, the Job Requisition Open event is a significant event because several Job Requisition metrics depend on it, such as Job Requisition Open to Assessment Start Days, Job Requisition Open Since (Days), Job Requisition Age (Months), Job Requisition Opened, Job Requisition Open, Job Requisition Open (Period Begin) and so on. Therefore, you must track this event by configuring the original Job Requisition status event, which occurs on the Job Requisition start date.
This tasks configures Job Requisition 'start' events.
Optional or Mandatory
This is a mandatory task, although there are defaults set up already in the installed solution. Oracle recommends that you read this section and then decide whether the default settings meet your business needs. If not, then you must change the configuration to suit your business needs.
Applies to
This configuration is required only for E-Business Suite source applications.
Task description
In order to infer the 'start' event of a Job Requisition that can be at any state now (named 'Job Requisition Current Status' – source conformed domain), you look at the previous 'most significant' status. This is named 'Job Requisition Original Status' - a source conformed domain. In this task, you will map your 'Job Requisition Current Status' domain members to one of the possible members of the 'Job Requisition Original Status' domain.
For example, if the current status is 'Closed', then you can infer that at one point it had a status of 'Open'. Therefore, you should map the original status to 'Open' against the current status 'Closed'. However, if the current status is 'Approval Denied', then it might make sense to assume that the requisition was never opened. Therefore, you should map the original status to another value, such as 'Requested', against the current status 'Approval Denied'.
Both of the involved source conformed domains 'Job Requisition Current Status' (**) and 'Job Requisition Original Status' have members that come from the same set of values. In fact, all values of 'Job Requisition Original Status' should exist as a value in 'Job Requisition Current Status'.
(**) Before you configure 'Job Requisition Original Status' you must configure the source conformed domain 'Job Requisition Current Status'. For more information, refer to the task 'Manage Domains and Member Mappings for Recruitment Fact Group'.
The Additional Information section below gives some extra information related to this task that should help understand the concept better, in terms of how these configurations are used downstream. Also, it provides a list of installed mappings between the two source-conformed domain members related to this task.
Additional Information
In the current task, it is expected that you would configure a 'probable' and 'most significant' original status of a job requisition, given a current status, with intent to track its 'Requisition Open' event. However, by mapping the original 'status' alone does not complete the 'event' configuration. Once you map the original status, you would also need to map 'statuses' to the appropriate 'events' in a later task called 'Manage Domains and Member Mappings for Recruitment Event Type'. These two tasks together complete the configuration of requisition start events.
For example, if the 'Job Requisition Current Status' is 'Closed', it might mean that the job requisition was 'Open' on an earlier date. In this case, the 'Job Requisition Original Status' can be configured as 'Approved'. The 'Approved' status can then be mapped to RQSTN_OPEN as W_EVENT_CODE, W_SUB_STAGE_CODE, and W_STAGE_CODE at the configuration task 'Manage Domains and Member Mappings for Recruitment Event Type'. This completes the process of identifying a job requisition's 'Opened' event when the job requisition is currently 'Closed' and its previous statuses are not tracked in E-Business Suite.
Another example might go like this. If the 'Job Requisition Current Status' is 'Rejected', it might mean that this job requisition previously had a status of 'Pending' on an earlier date and was never in 'Open' status. In this case, the 'Job Requisition Original Status' can be configured as 'Pending' instead of 'Open'. The 'Pending' status can then be mapped to RQSTN_APPROVAL_PENDING as W_EVENT_CODE, W_SUB_STAGE_CODE and RQSTN_PENDING as stage code at the configuration task 'Manage Domains and Member Mappings for Recruitment Event Type'. Within Oracle Business Analytics Warehouse, this job requisition will then be treated as being never opened.
The table shows the installed mapping between the two source-conformed domain members. If this does not meet your business needs, then you will need to edit the member mappings.
| Source Member (Current Status) | Source Member Code (Current Status) | Target Member (Original Status) | Target Member Code (Original Status) |
|---|---|---|---|
|
APPROVED |
APPROVED |
APPROVED |
APPROVED |
|
CANCELLED |
CANCELLED |
PENDING |
PENDING |
|
CLOSED |
CLOSED |
APPROVED |
APPROVED |
|
HOLD |
HOLD |
APPROVED |
APPROVED |
|
OPEN |
OPEN |
APPROVED |
APPROVED |
|
PENDING |
PENDING |
APPROVED |
APPROVED |
|
REJECTED |
REJECTED |
PENDING |
PENDING |
|
RQSTN_CANCELLED |
UNAPPROVED |
PENDING |
PENDING |
|
UNDER REVIEW |
UNDER REVIEW |
PENDING |
PENDING |
Dependency
If you edit this mapping, you would need to carry out a full ETL load into Oracle Business Analytics Warehouse.