Technical Interview Questions and Answers :: Oracle Apps HRMS

• 
  
  API package contains many procedures to insert/update/delete the application data.
  
  


• 
  
  The API is not executed on its own, the API must be called or executed by other pl/sql program.
  
  


• 
  
  The API package should never be modified for custom use, if modified Oracle will not be able to support them.
  
  


• 
  
  None of the HRMS APIs issue commit, the calling module should manage the commit of the transaction.
  
  

• Object Version number is an assigned number to a row in a database table.


• When a new row inserted its number is set to 1


• If any updates performed on the row then the Object version number is incremented.


• Every API has the p_object_version_number control parameters.


• For create APIs this parameter is defined as an OUT parameter the API assigns the Object version number to be 1 for row inserts.


• For update APIs the parameter is defined as IN OUT, for update API the object version number is mandatory.

• No, if an event-based alert defined on an application table then the API will give error.


• To run API the alert has to be disabled and re-enabled after the API has been executed.

• 
  
  Normal Entry
  
  


• 
  
  Override Entry
  
  


• 
  
  Additional Entry
  
  


• 
  
  Adjustment Entry
  
  
  
  
  
  • Additive Adjustment
  
  
  • Replacement Adjustment
  
  
  • Balance Adjustment
  
  
  
  

1. per_all_people_f: This table will provide us the very basic information about the employee. The very data from the first screen we see when we open the "People -> Enter and Maintain" form goes into this table.
2. per_all_assignments_f: This table will store all the information which is been entered in the employee assignment form.
3. per_addresses: This table will store all the information which is been entered in the employee address form.
4. per_pay_proposals: This table will store all the information which is been entered in the employee salary form.
5. per_person_types_tl: This table is used to find the type of the employee. This table is linked with the per_all_people_f with the person_type_id to find out the type of person.
6. per_jobs_tl: This table will contain the various types of JOBS in oracle. This table is been linked with the per_all_assignments_f table to retrieve the correct job name from the employee.
7. per_grades_tl: This table will contain the various types of GRADES in oracle. This table is been linked with the per_all_assignments_f table to retrieve the correct grade name from the employee.
8. hr_locations_all: This table will contain the various LOCATIONS in oracle. This table is been linked with the per_all_assignments_f table to retrieve the correct location name from the employee.
9. pay_all_payrolls_f: This table will contain the various types of PAYROLLS in oracle. This table is been linked with the per_all_assignments_f table to retrieve the correct payroll name from the employee.
10. per_pay_bases: This table will contain the various types of PAY BASES in oracle. This table is been linked with the per_all_assignments_f table to retrieve the correct pay basis name from the employee.
11. per_assignment_status_types_tl: This table will contain the various types of assignment types in oracle. The assignment types generally would be "Active Assignment" etc. This table is been linked with the per_all_assignments_f table to retrieve the correct job name from the employee.
12. per_person_type_usages_f: This table will store the correct person type of the particluar employee. We should never depend on the person type present in the per_all_people_f table. Instead, we need to link the person_id with this table and get the correct person type.

Every update in the Table, we will save the change in the form of a Record to provide the facility to find the information at any point of time.
These tables are post fixed by _F