Step 1: Find the API for which HOOK has
to write.
There are mainly two tables:
1)HR_API_HOOKS
2)HR_API_MODULES
Note:For
understanding types of hook search in oracle metalink.
Step
2: Create A PL/SQL Procedure which fits
requirements.
Step
3: Now Register created procedure into Required Hook:
API for Registering User
Hook:
.
HR_API_HOOK_CALL_API.CREATE_API_HOOK_CALL
.
HR_API_HOOK_CALL_API.UPDATE_API_HOOK_CALL
.
HR_API_HOOK_CALL_API.DELETE_API_HOOK_CALL
Step
4: Once Hook registered. We need to run the Pre Processors which will taken
care by DBA.
Step
5: Once done with all above steps verify the status of user hook in the table
called:
HR_API_HOOK_CALLS
===========================================================
APIs With User Hooks
In
Release 11, Oracle HRMS has supplemented the core product API functionality by
the addition of API user hooks. These are locations in the HRMS APIs where
additional customer specific logic can be executed.
When
the API processing reaches a user hook, core product processing stops and any
customer specific logic for that event is executed. Then, if no errors occur,
the main API processing resumes.
You
can use such extra logic to add functionality not supplied directly by Oracle
Applications. This could include business events such as the following:
validating
particular customer data: For example, you could limit grade step promotions to
a maximum of one step.
maintaining
additional data in your own user defined tables: This could include specialised
information about employees not held in database tables supplied by Oracle
HRMS.
detecting
that a particular business event has occurred: If the event was an employee
termination process, for example, this could be made to send a message to your
security database disabling the employee's security pass.
Attention:
You should not manually edit the API source code files supplied by Oracle If
you do modify these codes, Oracle Applications will be unable to support the
product, and upgrades may not be possible. Oracle Applications only supports
direct calls to the published APIs. Direct calls to any other server-side package
procedures or functions that are written as part of the Oracle HRMS
Applications suite are not supported.
List of APIs
The
following APIs support all the API event points (before process; after process)
:
applicant assignment
offer_apl_asg
update_apl_asg
contact
relationship
create_contact_relationship
delete_contact_relationship
employee
actual_termination_emp
final_process_emp
create_employee
employee
assignment
activate_emp_asg
suspend_emp_asg
final_process_emp_asg
update_emp_asg
actual_termination_emp_asg
employee
assignment criteria
update_emp_asg_criteria
grade
rate value
create_grade_rate_value
update_grade_rate_value
delete_grade_rate_value
job
requirement
create_job_requirement
mass
moves
mass_moves
pay
scale value
create_pay_scale_value
update_pay_scale_value
delete_pay_scale_value
person
address
create_person_address
update_person_address
personal
payment method
create_personal_payment_method
update_personal_payment_method
position
create_position
update_position
position
requirement
create_position_requirement
secondary
applicant assignment
create_secondary_apl_asg
secondary
employee assignment
create_secondary_emp_asg
Row Handlers
The
Row Handlers on the following tables support all the Row Handler event points (after
insert; after update; after delete) :
PER_ADDRESSES
PER_ALL_PEOPLE_F
PER_ALL_ASSIGNMENTS_F
PAY_PERSONAL_PAYMENT_METHODS_F
PER_POSITIONS
PER_APPLICATIONS
PER_CONTACT_RELATIONSHIPS
No comments:
Post a Comment