Oracle HRMS Interview Questions

1. What is interface and conversion and what interface you developed explain complete process along with error handling part.
2. API name and table for element entry
3. How to do conversion process.
4. Inbound interface name and outbounf interface name that you worked on.
5. AOL basics like tables for value set and types of value sets and table for indepdent VS.
6. Pragmatic autonomous transaction.
7. SQL function for string
8. Cascading Decode statement.
9. Bulk collect with limit syntax and limitation .
10. The largest component you have ever worked on explain that.
11. Unix basics command for file access.
12. XML publisher reports registration steps.
13. Trigger
14. All base tables name for Oracle HRMS
15. Workflow tables.
16. Hint in SQL
17. Public and private API in Oracle
18. Ref cursor and usage of that.
19. Collection type variables.
20. Count(*) will generate no data found exception or not if conditions don’t match in where clause.
21. How to generate XML file from PLSQL package.
22. How to migrate template from one instance to other.
23. How to skip records from ctl file.
24. What will be status after awaiting for shipping in o2c.
25. How to submit request set from back end.
26. Profile objective creation and order of precedence at different level.
27. Ddl dml and command for SQL.
28. Max number of the columns in oracle tables?
29. Total attributes in table atnd what is Global attribute.
30. Total segments in table kff enabled table.
31. Total size of any object in oracle database .
32. What is AuthID in create or replace. Package.
33. Difference between procedure and Function.
34. INOUT parameters what is the purpose of nocopy with that?
35. What is lookups and what all are the tables for the same.
36. If emp is terminated then what will be the current employer flag in per_all_peope_f table.
37. When to use NOCOPY parameters in parameters.
38. What is basic difference between conversion process and open Interfaces.



When a Self Service HRMS user creates any data from the screens, such data goes and resides in some temporary tables. This data is retained within the temporary tables until the transaction is Completed. A transaction in this example gets completed when Holiday Rejection complaint is either Rejected or Approved. These temporary table names begin with name HR_API%. In reality, the data entered by the user is either stored within just one table i.e. HR_API_TRANSACTIONS or within HR_API_TRANSACTION_VALUES. When the data is stored in just the HR_API_TRANSACTIONS then the entire data entered by the user is captured in a CLOB column. This feature was introduced couple of years ago, whereby for performance reasons the temporary data is captured in a clob column named HR_API_TRANSACTIONS within HR_API_TRANSACTIONS. This CLOB column contains XML contents. By now, you might have the following questions 

Continue reading →

Using AME to Approve an Activity in Self Service HRMS

Oracle Self Service Human Resources (SSHR) is all driven by a single workflow. The name of this workflow is HR and its short code is HRSSA. The workflow is kicked off as soon as any business activity is initiated in Self Service HRMS. This workflow can be customised to initiate AME for the generation of approval lists.

Let’s take approvals of Competencies for example. As standard when employees enter their Competencies, they don’t need approval. As a Professional Services consultancy, we need changes to Competencies approved so Line Managers are aware of their employee’s skill sets. As soon as you open the Competency Profile screen the HRSSA workflow is fired up.

Continue reading →



How does Oracle know which workflow process to initiate when a user enters “Person Information” screen in SSHR

When user clicks on SSHR Menu Item, the name of the workflow process is passed as a parameter to the form function. Therefore, the sequence of events are
  • User clicks on a menu in SSHR responsibility
  • Form Function attached to Menu is invoked.
  • This Form Function invokes AK Region HR_CREATE_PROCESS_TOP_SS [See Web HTML of Form Function HR_PERINFO_SS]

Continue reading →

AME(Approval Management Engine) Part 1


In this article you will understand the basic concept of AME. This article will lay the foundation of some of the AME examples in iRecruitment and SSHR that will be covered.

What is AME?
AME by definition is a Approval Management Engine that Builds a list of approvers for a specific transaction using business rules. However in simple words, AME is a “IF THEN….ELSE….END IF” condition – wrapped into an API.
That’s exactly what AME is. It is a IF THEN ELSE CONDITION wrapped up into a lets say Function Call to produce a list of approvers. The complexities are taken care of by the Approval Management Engine itself. However this “IF CONDITION” definition holds true when talking about the simplest possible definition of AME. Therefore if you can understand “IF Condition”, then you can understand AME. Further to that, if you know how to write IF Conditions and how to write SQL, then you will be able to implement most of the AME Business requirements with ease. Lets have a look into IF CONDITION from another perspective.

Continue reading →