Total Pageviews

Search This Blog

Tuesday, January 11, 2011

Batch Element Entry (BEE)

Batch Element Entry (BEE) enables payroll to enter batches of element entries, validate that the entries are correct and then transfer the entries to the employee’s element entries.

Batch Element Entry also provides the following functionality:

*  Batch Header identifies the batch and determines what happens if any of the batch lines duplicate existing element entries.
*  Batch Lines enable payroll to create batches by Element with the relevant Input Values for processing in payroll.  Defaults can be initiated for faster data entry.
*  BEE provides the ability to validate batches prior to submitting.  This feature enables payroll to identify incorrect employee assignment numbers, elements that are not eligible for employees, etc.
*  Provides the ability to use Control Totals to help validate the batch
*  Messages that indicate if batches are out of balance with control totals, in valid employee assignment numbers, etc.
*  BEE Spreadsheet Interface - Enables the loading of payroll data from various sources into BEE using the delivered BEE Spreadsheet Interface tool.  Please refer to the Spreadsheet Interface section for more information on using the Spreadsheet Interface.

"Team Work" More We Less Me.
           Sameer Patil

Monday, January 10, 2011

Procedure to Create Competency.

Procedure to Create Competency.
    1. Select the New button in the Find window.
    2. Enter a name and description for the competence.
    3. Enter the dates between which the competence is valid. You must enter a From date but you can leave the To date blank. If you enter a To date, ensure that it is wide enough to cover any competence elements you may need to create.

Entering a Rating Scale

    5. Click the Scale radio button to use a rating scale to measure the competence against.
    6. If you set up a default rating scale, it displays automatically for this competence, otherwise select one from the list. You can delete the defaulted rating scale and select another one, if required.
    7. Select the Levels box if you want to check the proficiency levels for that rating scale, otherwise go straight to Entering Competence Details.

Entering Proficiency Levels

    8. Click the Levels radio button to enter proficiency levels and behavioral indicators for the competence.
    9. Select the Levels button and enter the first proficiency level and description. For example, enter 0 in the Level field and No Skill in the Name field.
    10. Enter the behavioral indicator for that level, for example, 'No knowledge/expertise of scaffolding'. You can enter up to 2000 characters for each behavioral indicator.

Entering Competence Details

    12. Select the main method of evaluating the competence, for example, written examination or observation.
    13. Enter how often you need to evaluate the competence. For example, enter 5 if you have to evaluate the competence every 5 years.
    14. Select the measure to identify how often you need to evaluate the competence. For example, select Year if you evaluate the competence every 5 years.
    If you click this box, when you or another user later indicates that a person possesses this competence (using the Competence Profile), you must enter the certification method and date.
    16. Save your changes.

Querying a Competence Using the Find Competencies Window

When you navigate to the Competencies window, the Find Competencies window automatically displays in front of it.

To query a competence using the Find Competence window:

    1. Do one or both of the following:
    • Enter a full or partial query on the competence name.
    2. Choose the Find button.
    Oracle Human Resources displays the competence for you to check.



"Team Work" More We Less Me.
           Sameer Patil

Wednesday, January 5, 2011

Object Version Number (OVN) in API

 Object Version Number (OVN) is a column in a database table. It is used to track multiple changes to a record. When a new row is inserted, the OVN is set to 1. As updates are performed on the row through the Forms, the OVN is incremented. The OVN is transferred with a queried row. If an update is attempted when the change is saved to the table, the current OVN is compared with the value being passed back from the transaction. If the two are the same, the update can be committed to the table. If the two are different, the update is rejected and flagged with an error. The transaction must be re-queried, and the update made again to the more current version of the row.

APIs and Forms use OVNs similarly. Every published API has the p_object version_number control parameter.

For Create APIs, this parameter is defined as an OUT parameter: the API assigns the object version number to 1 for row inserts. For Update APIs, the parameter is defined as IN OUT, and is mandatory in the API call.

The current value 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, the error HR_7155_OBJECT_LOCKED is raised. The information can be re-queried for a more current version.




You can use the following query to determine the OVN to pass in your API call:

select max(ovn) from (table name)  where person_id/assignment_id etc=(some value)





Thanks and Regards
Sameer S Patil
"Team Work" More We Less Me.