Thursday, August 18, 2016

ORACLE HRMS FAQ's

What are the minimum classifications to create a Business Group?
(i) Business Group
(ii) GRE/Legal Entity
(iii) HR Organization

What are the Pre-Requisites for creating a Business Group?
(i) Value Sets
(ii) Key Flexfields
(iii) Location

What is the use of HR Organization?
If we want to assign the employee information to a Business Group then we need to have HR Organization classification under a Business Group.

What is People Group?
(i) It is a Flexible area for holding user-defined assignment data.
(ii) Data can be used for Grouping sets of assignment together.
(iii) People group can be used for Element eligibility.
(iv) This information is used by the Payroll Run.
(v) The data will be held in PAY_PEOPLE_GROUPS.
(vi) GROUP_NAME field holds the concatenation of Segment data.

What is the KFF structure for SIT?
Personal Analysis Flexfields.

What is the DFF structure for EIT?
(i) Extra Person Information
(ii) Assignment Extra Information
(iii) Extra Location Information
(iv) Extra Position Information
(v) Extra Job Information
(vi) Organization Developer DF

How to enable EIT?
Switch Responsibility to ‘Human Resources, Vision Enterprises’
Double click on ‘Security’
Click on ‘Information Types’
Create your own ‘Information Types’ under your ‘Responsibility Name’.

How to enable SIT?
Switch Responsibility to ‘Human Resources, Vision Enterprises’
Double click on ‘Other Definitions’
Click on ‘Special Information Types’

What is the use of Date Track?
1) It is used to maintain the record history by creating a new record when the date track mode is UPDATE and override on the existing record when the Data track mode is CORRECTION.
2) The value of the Data Track record depends on the date.
3) Tables ending with _F are date track tables.
4) To control data tracked rows, every Date Track table must include Effective_start_date & Effective_end_date.
5) The Effective_Start_Date indicates when the record inserted.
6) The Effective_End_Date indicates when the record updated or deleted.

What is the use of Object Version Number?
1) It is used to capture the latest record from the data base table.
2) When a row is inserted its number is set to 1.
3) If any updates performed on the row then the OVN is incremented.
4) Every API has the OVN parameter.
5) For create API this parameter is defined as an OUT parameter.
6) For update API this parameter is defined as an IN OUT parameter.
7) The APIs use it to check a row has been updated by another user, to prevent overwriting their changes.

What is the Element?
It is a Data Structure which is used to hold information for both Human Resources and Payroll.
In Human Resources elements may represents compensation types including Earnings such as Salary, Hourly Wages and Bonuses.
In Payroll, elements constitute all the items in the Payroll run process.

What are the Classification Priorities?
(i) Information
(ii) Non-Payroll
(iii) Earnings
(iv) Pre-Tax Deductions
(v) Tax Deductions
(vi) Employer Tax
(vii) Voluntary Deductions
(viii) In Voluntary Deductions

What the Element can represent?
Earnings --> such as Salary, Wages & Bonuses
Benefits --> such as employee stock & pension plans
Non-Payroll items --> such as Expenses
Absences from work
Voluntary and In-Voluntary deductions
Employer Taxes and other Liabilities.

What are the pre-defined Elements?
UK Payroll legislation provides many predefined elements
--Tax
--National Insurance (Employee/Employer)
--Court Orders
These Elements cannot be modified.

What are the Element Entry Concepts?
Recurring à Recurring Entries can exists over many Payroll periods
Non-Recurring à Non-Recurring Entries are valid for single Payroll period only.

What are the types of Element Entry?
There are four types
Normal Entry
Override Entry
Additional Entry
Adjustment Entry
--Additive Adjustment
--Replacement Adjustment
--Balance Adjustment

How can we add a new input value to an existing Element?
We can add an additional input values to an existing Element if the element has not been processed in a Payroll run and the Effective data is the same date of creation of the Element.

What is the use of ID_FLEX_NUM?
It is used to define the Structure Definition.
The Structure Definition is held in FND_ID_FLEX_STRUCTURES
The Structure Segment Definition is held in FND_ID_FLEX_SEGMENTS

What is the Element Link?
Links identify one or more assignment components that must be included in an employee's assignment for them to be eligible.Elements can, but they don’t have to, be linked by: Organization GroupJob PositionGrade LocationEmployment Category (i.e., Fulltime-Regular, Part-time-Regular)
Payroll Salary Basis


What is API?
Ø API is packaged procedure which can be used as an entry point into Application.
Ø The advantage of using an API is we can enter new information or alter the existing data without manual enters the information into the Application.
Ø APIs allow users to maintain HRMS information without using Oracle Application forms.

How do i use an API to upload the data?
Ø 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.

How do i identify the Package name and version of the API?
SELECT text
FROM all_source
WHERE name like ‘HR_EMPLOYEE_API%’
AND text LIKE ‘%Header%’;

Where can i find information on an API and its parameters?
Review the package header file for the particular API file (.pkh).

What is Object version number and how do I assign values for it in an API?
Ø 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.

When the HR_7155_OBJECT_LOCKED raised?
The current value of object_version_number must be passed in the API call and it is compared to the version on the row in the table. If the versions are different then the HR_7155_OBJECT_LOCKED is raised.

What is the p_validate control parameter?
Every API has a p_validate control parameter.
When the parameter is set to FALSE then all the business function validation is performed.
If every thing is validated then row can be inserted/updated/deleted.
If p_validate is set to TRUE then only the actual operation is validated.
A savepoint is issued at the start of the call and a rollback is done at the end of the call.
Can I use an API on an application table on which an event-based alert is defined?
Ø 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.

What is the difference between an API and a publicly callable API?
Ø An API is an alternative entry for data to be insert/update/delete from the application.
Ø The Oracle HRMS
Ø Publicly callable APIs engage in validation in the same manner as the forms do with in the application.
Ø Validation is performed in terms of data integrity, insuring that data relationship exist properly between related tables.
Ø Validation is also performed against business functionality as the application form would enforce it.
Ø Therefore, only publicly callable APIs should be used to insert/update and delete data from the application.

What is User Acceptance Testing?
User Acceptance Testing is often the final step before rolling out the application.
Usually the end users who will be using the applications test the application before ‘accepting’ the application.
This type of testing gives the end users the confidence that the application being delivered to them meets their requirements.
This testing also helps nail bugs related to usability of the application.

User Acceptance Testing – Prerequisites:
Before the User Acceptance testing can be done the application is fully developed.
Various levels of testing (Unit, Integration and System) are already completed before User Acceptance Testing is done. As various levels of testing have been completed most of the technical bugs have already been fixed before UAT.

User Acceptance Testing – What to Test?
To ensure an effective User Acceptance Testing Test cases are created.
These Test cases can be created using various use cases identified during the Requirements definition stage.
The Test cases ensure proper coverage of all the scenarios during testing.

During this type of testing the specific focus is the exact real world usage of the application. The Testing is done in an environment that simulates the production environment.
The Test cases are written using real world scenarios for the application

User Acceptance Testing – How to Test?
The user acceptance testing is usually a black box type of testing. In other words, the focus is on the functionality and the usability of the application rather than the technical aspects. It is generally assumed that the application would have already undergone Unit, Integration and System Level Testing.

However, it is useful if the User acceptance Testing is carried out in an environment that closely resembles the real world or production environment.

The steps taken for User Acceptance Testing typically involve one or more of the following:
1) User Acceptance Test (UAT) Planning
2) Designing UA Test Cases
3) Selecting a Team that would execute the (UAT) Test Cases
4) Executing Test Cases
5) Documenting the Defects found during UAT
6) Resolving the issues/Bug Fixing
7) Sign Off

User Acceptance Test (UAT) Planning:
As always the Planning Process is the most important of all the steps. This affects the effectiveness of the Testing Process. The Planning process outlines the User Acceptance Testing Strategy. It also describes the key focus areas, entry and exit criteria.

Designing UA Test Cases:
The User Acceptance Test Cases help the Test Execution Team to test the application thoroughly. This also helps ensure that the UA Testing provides sufficient coverage of all the scenarios.
The Use Cases created during the Requirements definition phase may be used as inputs for creating Test Cases. The inputs from Business Analysts and Subject Matter Experts are also used for creating.
Each User Acceptance Test Case describes in a simple language the precise steps to be taken to test something.
The Business Analysts and the Project Team review the User Acceptance Test Cases.

Selecting a Team that would execute the (UAT) Test Cases:
Selecting a Team that would execute the UAT Test Cases is an important step.
The UAT Team is generally a good representation of the real world end users.
The Team thus comprises of the actual end users who will be using the application.

Executing Test Cases:
The Testing Team executes the Test Cases and may additional perform random Tests relevant to them

Documenting the Defects found during UAT:
The Team logs their comments and any defects or issues found during testing.

Resolving the issues/Bug Fixing:
The issues/defects found during Testing are discussed with the Project Team, Subject Matter Experts and Business Analysts. The issues are resolved as per the mutual consensus and to the satisfaction of the end users.

Sign Off:
Upon successful completion of the User Acceptance Testing and resolution of the issues the team generally indicates the acceptance of the application. This step is important in commercial software sales. Once the User “Accept” the Software delivered they indicate that the software meets their requirements.

The users now confident of the software solution delivered and the vendor can be paid for the same. 

No comments:

Post a Comment

Best Blogger TipsGet Flower Effect