Professional Documents
Culture Documents
In Oracle HR,People are different from the employees. Not all the people defined are employees.
Employee information
goes into the table "hr_employees" and the people information goes into the "per_all_people_f" table,but
an employee will
be in both the hr_employees and per_all_people_f tables. Typically if there are any contacts for an
employee ,then they
will be entered as the people.
-- The below query can be tried to see if the HR product is installed or not. Interesting all the HR related
code is present in the applicaction user PER and not HR
select INIT_FUNCTION_NAME from FND_PRODUCT_INITIALIZATION
where APPLICATION_SHORT_NAME = 'PER'
and exists (select 1 from FND_PRODUCT_INIT_CONDITION C
where C.APPLICATION_SHORT_NAME = 'PER'
and C.RE_INIT_CONDITION in ('USER','RESP','APPL','NLS'))
Normally, whenever a purchase order is raised ,say,by an employee. then it will be routed thru the next
in the hierarchy.
And there are two types of hierarchies in the Oracle purchasing module. One is position approval
hierarchy and another
employee/supervisor hierarchy. This setting can be defined using the path
setup => Organization => Financials Options screen. => Human Resources tab.
If the "Use Approval Hierarchies" check box is checked, then it means that the position approval
hierarchy is used.
If the "Use Approval Hierarchies" check box is unchecked, then it means that the employee/supervisor
hierarchy is used.
Let us briefly dwell on what is the difference between these two hierarchies. In the case of position
approval hierarchy,
firstly a hierarchy of all the positions in the company are defined. for ex, Manager, Senior Manager,
Executive director
,Vice President,etc; all these positions are first defined. So if a manager raises a PO, then that document is
routed up
the hierarchy i.e it is routed to the senior manager.
In the case of employee/supervisor hierarchy, while we are defining an employee ,say ,Smith, then his
manager ,say, David, is also
specified. And a document is routed to that manager David.
INcidentally in Oracle purchasing, there are lot of document types defined. That is ,a requisition(Internal
or Purchase), planned purchase order,
standard purchase order.etc We can see these types from the path setup => Purchasing => Document
Types.
/**********************************************/
/* HR Stuff.
The profile option MO: Operating Unit will always the store the operating unit id and not the
inventory_org id
The Profile option MO:Top Operating Level stores the values of set of books, legal entity or operating
unit.
If it is SOB, user can run the report with any LE underneath that sob
if it is LE, user can run the report with any OU underneath that LE
if it is OU, user can run the report with any OU mentioned in the MO: Operating Unit profile option.
There are certain predefined oracle app reports which we can run with above mentioned reporting
levels.
Ex : Aging 4 Buckets report.*/
hr_organization_information_v
------------------------
-- Set the environment in the production environment ( fnd_client_info.set_org_context)
BEGIN
dbms_application_info.set_client_info(485);
END;
-- This query ,given a approval group, will give the approval limits.
select * from po_control_rules where control_group_id in
(select control_group_id from po_control_groups where control_group_name = 'NCE 10/CE 10')
-- This query given a job function name, will give the approval limits.(Make sure you set the correct
org_id before you check the amount limits.
select * from po_control_rules where control_group_id in
(select control_group_id from po_control_groups where control_group_id in
(select control_group_id from po_position_controls where end_date is not null and job_id in (
select job_id from per_jobs where name like 'E7-G AND A' )
)
)