hr_assignment_api update_emp_asg to update supervisor

Oracle Apps Technical

Thursday 13 march 2014, oracle hrms api – update employee assignment & supervisor adding.

3 comments:

Very much Helpful! Thanks :)

Thank you so much, very useful :-)

what if we have multiple assignment then how should we tell the api that we need supervisor on active one. becasue the active assignment flag of both assignments are Y.

hr_assignment_api.update_emp_asg

I have created the following API, but when i execute, I get the error ‘ORA-20001: The primary key specified is invalid’. I don’t know where I am going wrong. Please advise. DECLARE l_per_effective_date DATE; p_default_code_comb_id NUMBER; p_assignment_id NUMBER; l_object_version_number NUMBER; l_cagr_grade_def_id NUMBER; l_cagr_concatenated_segments VARCHAR2 (70); l_concatenated_segments VARCHAR2 (70); l_soft_coding_keyflex_id NUMBER; l_comment_id NUMBER; l_effective_start_date DATE; l_effective_end_date DATE; l_no_managers_warning BOOLEAN; l_other_manager_warning BOOLEAN; l_hourly_salaried_warning BOOLEAN; l_gsp_post_process_warning VARCHAR2 (70); p_supervisor_id NUMBER; l_location_id NUMBER; p_assignment_number VARCHAR2 (40); p_change_reason VARCHAR2 (40); l_assignment_status_type_id NUMBER (40); p_comments VARCHAR2 (40); p_date_probation_end DATE; p_frequency VARCHAR2 (40); l_internal_address_line VARCHAR2 (40); l_manager_flag VARCHAR2 (40); p_normal_hours NUMBER; l_collective_agreement_id NUMBER; l_employee_category VARCHAR2 (40); l_job_post_source_name VARCHAR2 (40); p_supervisor_assignment_id NUMBER; l_source_type VARCHAR2 (40); l_labour_union_member_flag VARCHAR2 (40); l_old_conc_segments VARCHAR2 (40); l_flex_num VARCHAR2 (40); l_organization_id NUMBER; p_validate BOOLEAN; p_datetrack_update_mode DATE; p_internal_address_line VARCHAR2 (40); p_manager_flag VARCHAR2 (40); p_perf_review_period NUMBER; p_perf_review_period_frequency VARCHAR2 (40); p_probation_period NUMBER; p_probation_unit VARCHAR2 (40); p_sal_review_period NUMBER; p_sal_review_period_frequency VARCHAR2 (40); p_set_of_books_id NUMBER; p_source_type VARCHAR2 (40); p_time_normal_finish NUMBER; p_time_normal_start NUMBER; p_bargaining_unit_code VARCHAR2 (40); p_labour_union_member_flag VARCHAR2 (40); p_hourly_salaried_code VARCHAR2 (40); p_ass_attribute_category VARCHAR2 (40); p_ass_attribute1 VARCHAR2 (40); p_ass_attribute2 VARCHAR2 (40); p_ass_attribute3 VARCHAR2 (40); p_ass_attribute4 VARCHAR2 (40); p_ass_attribute5 VARCHAR2 (40); p_ass_attribute6 VARCHAR2 (40); p_ass_attribute7 VARCHAR2 (40); p_ass_attribute8 VARCHAR2 (40); p_ass_attribute9 VARCHAR2 (40); p_ass_attribute10 VARCHAR2 (40); p_ass_attribute11 VARCHAR2 (40); p_ass_attribute12 VARCHAR2 (40); p_ass_attribute13 VARCHAR2 (40); p_ass_attribute14 VARCHAR2 (40); p_ass_attribute15 VARCHAR2 (40); p_ass_attribute16 VARCHAR2 (40); p_ass_attribute17 VARCHAR2 (40); p_ass_attribute18 VARCHAR2 (40); p_ass_attribute19 VARCHAR2 (40); p_ass_attribute20 VARCHAR2 (40); p_ass_attribute21 VARCHAR2 (40); p_ass_attribute22 VARCHAR2 (40); p_ass_attribute23 VARCHAR2 (40); p_ass_attribute24 VARCHAR2 (40); p_ass_attribute25 VARCHAR2 (40); p_ass_attribute26 VARCHAR2 (40); p_ass_attribute27 VARCHAR2 (40); p_ass_attribute28 VARCHAR2 (40); p_ass_attribute29 VARCHAR2 (40); p_ass_attribute30 VARCHAR2 (40); p_title VARCHAR2 (40); p_segment1 VARCHAR2 (40); p_segment2 VARCHAR2 (40); p_segment3 VARCHAR2 (40); p_segment4 VARCHAR2 (40); p_segment5 VARCHAR2 (40); p_segment6 VARCHAR2 (40); p_segment7 VARCHAR2 (40); p_segment8 VARCHAR2 (40); p_segment9 VARCHAR2 (40); p_segment10 VARCHAR2 (40); p_segment11 VARCHAR2 (40); p_segment12 VARCHAR2 (40); p_segment13 VARCHAR2 (40); p_segment14 VARCHAR2 (40); p_segment15 VARCHAR2 (40); p_segment16 VARCHAR2 (40); p_segment17 VARCHAR2 (40); p_segment18 VARCHAR2 (40); p_segment19 VARCHAR2 (40); p_segment20 VARCHAR2 (40); p_segment21 VARCHAR2 (40); p_segment22 VARCHAR2 (40); p_segment23 VARCHAR2 (40); p_segment24 VARCHAR2 (40); p_segment25 VARCHAR2 (40); p_segment26 VARCHAR2 (40); p_segment27 VARCHAR2 (40); p_segment28 VARCHAR2 (40); p_segment29 VARCHAR2 (40); p_segment30 VARCHAR2 (40); p_concat_segments VARCHAR2 (40); a DATE; BEGIN select effective_start_date into a from per_all_people_f where employee_number=111; l_object_version_number :=1; hr_assignment_api.update_emp_asg (p_validate => p_validate ,p_effective_date => to_date(a) ,p_datetrack_update_mode => p_datetrack_update_mode ,p_assignment_id => 103 ,p_supervisor_id => p_supervisor_id ,p_assignment_number => p_assignment_number ,p_object_version_number => l_object_version_number ,p_change_reason => p_change_reason ,p_comments => p_comments ,p_date_probation_end => p_date_probation_end ,p_default_code_comb_id => p_default_code_comb_id ,p_frequency => p_frequency ,p_internal_address_line => p_internal_address_line ,p_manager_flag => p_manager_flag ,p_normal_hours => p_normal_hours ,p_perf_review_period => p_perf_review_period ,p_perf_review_period_frequency => p_perf_review_period_frequency ,p_probation_period => p_probation_period ,p_probation_unit => p_probation_unit ,p_sal_review_period => p_sal_review_period ,p_sal_review_period_frequency => p_sal_review_period_frequency ,p_set_of_books_id => p_set_of_books_id ,p_source_type => p_source_type ,p_time_normal_finish => p_time_normal_finish ,p_time_normal_start => p_time_normal_start ,p_bargaining_unit_code => p_bargaining_unit_code ,p_labour_union_member_flag => p_labour_union_member_flag ,p_hourly_salaried_code => p_hourly_salaried_code ,p_ass_attribute_category => p_ass_attribute_category ,p_ass_attribute1 => p_ass_attribute1 ,p_ass_attribute2 => p_ass_attribute2 ,p_ass_attribute3 => p_ass_attribute3 ,p_ass_attribute4 => p_ass_attribute4 ,p_ass_attribute5 => p_ass_attribute5 ,p_ass_attribute6 => p_ass_attribute6 ,p_ass_attribute7 => p_ass_attribute7 ,p_ass_attribute8 => p_ass_attribute8 ,p_ass_attribute9 => p_ass_attribute9 ,p_ass_attribute10 => p_ass_attribute10 ,p_ass_attribute11 => p_ass_attribute11 ,p_ass_attribute12 => p_ass_attribute12 ,p_ass_attribute13 => p_ass_attribute13 ,p_ass_attribute14 => p_ass_attribute14 ,p_ass_attribute15 => p_ass_attribute15 ,p_ass_attribute16 => p_ass_attribute16 ,p_ass_attribute17 => p_ass_attribute17 ,p_ass_attribute18 => p_ass_attribute18 ,p_ass_attribute19 => p_ass_attribute19 ,p_ass_attribute20 => p_ass_attribute20 ,p_ass_attribute21 => p_ass_attribute21 ,p_ass_attribute22 => p_ass_attribute22 ,p_ass_attribute23 => p_ass_attribute23 ,p_ass_attribute24 => p_ass_attribute24 ,p_ass_attribute25 => p_ass_attribute25 ,p_ass_attribute26 => p_ass_attribute26 ,p_ass_attribute27 => p_ass_attribute27 ,p_ass_attribute28 => p_ass_attribute28 ,p_ass_attribute29 => p_ass_attribute29 ,p_ass_attribute30 => p_ass_attribute30 ,p_title => p_title ,p_segment1 => p_segment1 ,p_segment2 => p_segment2 ,p_segment3 => p_segment3 ,p_segment4 => p_segment4 ,p_segment5 => p_segment5 ,p_segment6 => p_segment6 ,p_segment7 => p_segment7 ,p_segment8 => p_segment8 ,p_segment9 => p_segment9 ,p_segment10 => p_segment10 ,p_segment11 => p_segment11 ,p_segment12 => p_segment12 ,p_segment13 => p_segment13 ,p_segment14 => p_segment14 ,p_segment15 => p_segment15 ,p_segment16 => p_segment16 ,p_segment17 => p_segment17 ,p_segment18 => p_segment18 ,p_segment19 => p_segment19 ,p_segment20 => p_segment20 ,p_segment21 => p_segment21 ,p_segment22 => p_segment22 ,p_segment23 => p_segment23 ,p_segment24 => p_segment24 ,p_segment25 => p_segment25 ,p_segment26 => p_segment26 ,p_segment27 => p_segment27 ,p_segment28 => p_segment28 ,p_segment29 => p_segment29 ,p_segment30 => p_segment30 ,p_concat_segments => p_concat_segments ,p_contract_id => hr_api.g_number ,p_establishment_id => hr_api.g_number ,p_collective_agreement_id => hr_api.g_number ,p_cagr_id_flex_num => hr_api.g_number ,p_cag_segment1 => hr_api.g_varchar2 ,p_cag_segment2 => hr_api.g_varchar2 ,p_cag_segment3 => hr_api.g_varchar2 ,p_cag_segment4 => hr_api.g_varchar2 ,p_cag_segment5 => hr_api.g_varchar2 ,p_cag_segment6 => hr_api.g_varchar2 ,p_cag_segment7 => hr_api.g_varchar2 ,p_cag_segment8 => hr_api.g_varchar2 ,p_cag_segment9 => hr_api.g_varchar2 ,p_cag_segment10 => hr_api.g_varchar2 ,p_cag_segment11 => hr_api.g_varchar2 ,p_cag_segment12 => hr_api.g_varchar2 ,p_cag_segment13 => hr_api.g_varchar2 ,p_cag_segment14 => hr_api.g_varchar2 ,p_cag_segment15 => hr_api.g_varchar2 ,p_cag_segment16 => hr_api.g_varchar2 ,p_cag_segment17 => hr_api.g_varchar2 ,p_cag_segment18 => hr_api.g_varchar2 ,p_cag_segment19 => hr_api.g_varchar2 ,p_cag_segment20 => hr_api.g_varchar2 ,p_cagr_grade_def_id => l_cagr_grade_def_id ,p_cagr_concatenated_segments => l_cagr_concatenated_segments ,p_soft_coding_keyflex_id => l_soft_coding_keyflex_id ,p_comment_id => l_comment_id ,p_effective_start_date => l_effective_start_date ,p_effective_end_date => l_effective_end_date ,p_concatenated_segments => l_concatenated_segments ,p_no_managers_warning => l_no_managers_warning ,p_other_manager_warning => l_other_manager_warning ,p_supervisor_assignment_id => p_supervisor_assignment_id ); END;

DECLARE l_per_effective_date DATE; p_default_code_comb_id NUMBER; p_assignment_id NUMBER; l_object_version_number NUMBER; l_cagr_grade_def_id NUMBER; l_cagr_concatenated_segments VARCHAR2 (70); l_concatenated_segments VARCHAR2 (70); l_soft_coding_keyflex_id NUMBER; l_comment_id NUMBER; l_effective_start_date DATE; l_effective_end_date DATE; l_no_managers_warning BOOLEAN; l_other_manager_warning BOOLEAN; l_hourly_salaried_warning BOOLEAN; l_gsp_post_process_warning VARCHAR2 (70); p_supervisor_id NUMBER; l_location_id NUMBER; p_assignment_number VARCHAR2 (40); p_change_reason VARCHAR2 (40); l_assignment_status_type_id NUMBER (40); p_comments VARCHAR2 (40); p_date_probation_end DATE; p_frequency VARCHAR2 (40); l_internal_address_line VARCHAR2 (40); l_manager_flag VARCHAR2 (40); p_normal_hours NUMBER; l_collective_agreement_id NUMBER; l_employee_category VARCHAR2 (40); l_job_post_source_name VARCHAR2 (40); p_supervisor_assignment_id NUMBER; l_source_type VARCHAR2 (40); l_labour_union_member_flag VARCHAR2 (40); l_old_conc_segments VARCHAR2 (40); l_flex_num VARCHAR2 (40); l_organization_id NUMBER; p_validate BOOLEAN; p_datetrack_update_mode DATE; p_internal_address_line VARCHAR2 (40); p_manager_flag VARCHAR2 (40); p_perf_review_period NUMBER; p_perf_review_period_frequency VARCHAR2 (40); p_probation_period NUMBER; p_probation_unit VARCHAR2 (40); p_sal_review_period NUMBER; p_sal_review_period_frequency VARCHAR2 (40); p_set_of_books_id NUMBER; p_source_type VARCHAR2 (40); p_time_normal_finish NUMBER; p_time_normal_start NUMBER; p_bargaining_unit_code VARCHAR2 (40); p_labour_union_member_flag VARCHAR2 (40); p_hourly_salaried_code VARCHAR2 (40); p_ass_attribute_category VARCHAR2 (40); p_ass_attribute1 VARCHAR2 (40); p_ass_attribute2 VARCHAR2 (40); p_ass_attribute3 VARCHAR2 (40); p_ass_attribute4 VARCHAR2 (40); p_ass_attribute5 VARCHAR2 (40); p_ass_attribute6 VARCHAR2 (40); p_ass_attribute7 VARCHAR2 (40); p_ass_attribute8 VARCHAR2 (40); p_ass_attribute9 VARCHAR2 (40); p_ass_attribute10 VARCHAR2 (40); p_ass_attribute11 VARCHAR2 (40); p_ass_attribute12 VARCHAR2 (40); p_ass_attribute13 VARCHAR2 (40); p_ass_attribute14 VARCHAR2 (40); p_ass_attribute15 VARCHAR2 (40); p_ass_attribute16 VARCHAR2 (40); p_ass_attribute17 VARCHAR2 (40); p_ass_attribute18 VARCHAR2 (40); p_ass_attribute19 VARCHAR2 (40); p_ass_attribute20 VARCHAR2 (40); p_ass_attribute21 VARCHAR2 (40); p_ass_attribute22 VARCHAR2 (40); p_ass_attribute23 VARCHAR2 (40); p_ass_attribute24 VARCHAR2 (40); p_ass_attribute25 VARCHAR2 (40); p_ass_attribute26 VARCHAR2 (40); p_ass_attribute27 VARCHAR2 (40); p_ass_attribute28 VARCHAR2 (40); p_ass_attribute29 VARCHAR2 (40); p_ass_attribute30 VARCHAR2 (40); p_title VARCHAR2 (40); p_segment1 VARCHAR2 (40); p_segment2 VARCHAR2 (40); p_segment3 VARCHAR2 (40); p_segment4 VARCHAR2 (40); p_segment5 VARCHAR2 (40); p_segment6 VARCHAR2 (40); p_segment7 VARCHAR2 (40); p_segment8 VARCHAR2 (40); p_segment9 VARCHAR2 (40); p_segment10 VARCHAR2 (40); p_segment11 VARCHAR2 (40); p_segment12 VARCHAR2 (40); p_segment13 VARCHAR2 (40); p_segment14 VARCHAR2 (40); p_segment15 VARCHAR2 (40); p_segment16 VARCHAR2 (40); p_segment17 VARCHAR2 (40); p_segment18 VARCHAR2 (40); p_segment19 VARCHAR2 (40); p_segment20 VARCHAR2 (40); p_segment21 VARCHAR2 (40); p_segment22 VARCHAR2 (40); p_segment23 VARCHAR2 (40); p_segment24 VARCHAR2 (40); p_segment25 VARCHAR2 (40); p_segment26 VARCHAR2 (40); p_segment27 VARCHAR2 (40); p_segment28 VARCHAR2 (40); p_segment29 VARCHAR2 (40); p_segment30 VARCHAR2 (40); p_concat_segments VARCHAR2 (40); a DATE; BEGIN

l_object_version_number :=3; l_per_effective_date :=sysdate; l_effective_start_date :=sysdate-1; l_effective_end_date :=sysdate;

hr_assignment_api.update_emp_asg (p_validate => false ,p_effective_date => l_per_effective_date ,p_datetrack_update_mode => ‘CORRECTION’ ,p_assignment_id => 165 ,p_supervisor_id => p_supervisor_id ,p_assignment_number => p_assignment_number ,p_object_version_number => l_object_version_number ,p_change_reason => p_change_reason ,p_comments => p_comments ,p_date_probation_end => p_date_probation_end ,p_default_code_comb_id => p_default_code_comb_id ,p_frequency => p_frequency ,p_internal_address_line => p_internal_address_line ,p_manager_flag => p_manager_flag ,p_normal_hours => p_normal_hours ,p_perf_review_period => p_perf_review_period ,p_perf_review_period_frequency => p_perf_review_period_frequency ,p_probation_period => p_probation_period ,p_probation_unit => p_probation_unit ,p_sal_review_period => p_sal_review_period ,p_sal_review_period_frequency => p_sal_review_period_frequency ,p_set_of_books_id => p_set_of_books_id ,p_source_type => p_source_type ,p_time_normal_finish => p_time_normal_finish ,p_time_normal_start => p_time_normal_start ,p_bargaining_unit_code => p_bargaining_unit_code ,p_labour_union_member_flag => p_labour_union_member_flag ,p_hourly_salaried_code => p_hourly_salaried_code /* ,p_ass_attribute_category => p_ass_attribute_category ,p_ass_attribute1 => p_ass_attribute1 ,p_ass_attribute2 => p_ass_attribute2 ,p_ass_attribute3 => p_ass_attribute3 ,p_ass_attribute4 => p_ass_attribute4 ,p_ass_attribute5 => p_ass_attribute5 ,p_ass_attribute6 => p_ass_attribute6 ,p_ass_attribute7 => p_ass_attribute7 ,p_ass_attribute8 => p_ass_attribute8 ,p_ass_attribute9 => p_ass_attribute9 ,p_ass_attribute10 => p_ass_attribute10 ,p_ass_attribute11 => p_ass_attribute11 ,p_ass_attribute12 => p_ass_attribute12 ,p_ass_attribute13 => p_ass_attribute13 ,p_ass_attribute14 => p_ass_attribute14 ,p_ass_attribute15 => p_ass_attribute15 ,p_ass_attribute16 => p_ass_attribute16 ,p_ass_attribute17 => p_ass_attribute17 ,p_ass_attribute18 => p_ass_attribute18 ,p_ass_attribute19 => p_ass_attribute19 ,p_ass_attribute20 => p_ass_attribute20 ,p_ass_attribute21 => p_ass_attribute21 ,p_ass_attribute22 => p_ass_attribute22 ,p_ass_attribute23 => p_ass_attribute23 ,p_ass_attribute24 => p_ass_attribute24 ,p_ass_attribute25 => p_ass_attribute25 ,p_ass_attribute26 => p_ass_attribute26 ,p_ass_attribute27 => p_ass_attribute27 ,p_ass_attribute28 => p_ass_attribute28 ,p_ass_attribute29 => p_ass_attribute29 ,p_ass_attribute30 => p_ass_attribute30 ,p_title => p_title ,p_segment1 => p_segment1 ,p_segment2 => p_segment2 ,p_segment3 => p_segment3 ,p_segment4 => p_segment4 ,p_segment5 => p_segment5 ,p_segment6 => p_segment6 ,p_segment7 => p_segment7 ,p_segment8 => p_segment8 ,p_segment9 => p_segment9 ,p_segment10 => p_segment10 ,p_segment11 => p_segment11 ,p_segment12 => p_segment12 ,p_segment13 => p_segment13 ,p_segment14 => p_segment14 ,p_segment15 => p_segment15 ,p_segment16 => p_segment16 ,p_segment17 => p_segment17 ,p_segment18 => p_segment18 ,p_segment19 => p_segment19 ,p_segment20 => p_segment20 ,p_segment21 => p_segment21 ,p_segment22 => p_segment22 ,p_segment23 => p_segment23 ,p_segment24 => p_segment24 ,p_segment25 => p_segment25 ,p_segment26 => p_segment26 ,p_segment27 => p_segment27 ,p_segment28 => p_segment28 ,p_segment29 => p_segment29 ,p_segment30 => p_segment30 ,p_concat_segments => p_concat_segments ,p_contract_id => hr_api.g_number ,p_establishment_id => hr_api.g_number ,p_collective_agreement_id => hr_api.g_number ,p_cagr_id_flex_num => hr_api.g_number ,p_cag_segment1 => hr_api.g_varchar2 ,p_cag_segment2 => hr_api.g_varchar2 ,p_cag_segment3 => hr_api.g_varchar2 ,p_cag_segment4 => hr_api.g_varchar2 ,p_cag_segment5 => hr_api.g_varchar2 ,p_cag_segment6 => hr_api.g_varchar2 ,p_cag_segment7 => hr_api.g_varchar2 ,p_cag_segment8 => hr_api.g_varchar2 ,p_cag_segment9 => hr_api.g_varchar2 ,p_cag_segment10 => hr_api.g_varchar2 ,p_cag_segment11 => hr_api.g_varchar2 ,p_cag_segment12 => hr_api.g_varchar2 ,p_cag_segment13 => hr_api.g_varchar2 ,p_cag_segment14 => hr_api.g_varchar2 ,p_cag_segment15 => hr_api.g_varchar2 ,p_cag_segment16 => hr_api.g_varchar2 ,p_cag_segment17 => hr_api.g_varchar2 ,p_cag_segment18 => hr_api.g_varchar2 ,p_cag_segment19 => hr_api.g_varchar2 ,p_cag_segment20 => hr_api.g_varchar2 ,p_cagr_grade_def_id => l_cagr_grade_def_id ,p_cagr_concatenated_segments => l_cagr_concatenated_segments */ ,p_soft_coding_keyflex_id => l_soft_coding_keyflex_id ,p_comment_id => l_comment_id ,p_effective_start_date => l_effective_start_date ,p_effective_end_date => l_effective_end_date ,p_concatenated_segments => l_concatenated_segments ,p_no_managers_warning => l_no_managers_warning ,p_other_manager_warning => l_other_manager_warning ,p_supervisor_assignment_id => p_supervisor_assignment_id );

Hi Ralph, I am working on Oracle apps R12. I want to transfer employee data to assignment. I have already created the employees.

Could you provide a bit more information such as the RDBMS you are writing this for?

Respectfully, Ralph D. Wilson II Senior Programmer Analyst Information Technology Department 9311 San Pedro Suite 600 San Antonio TX 78216 (800) 527-0066 x7368 (210) 321-7368 (direct) [email protected] “Make everything as simple as possible, but not simpler.” Albert Einstein.

“Narmin Khatri via database-development-l”

Related Topics

Oracle HR Foundation

Oracle HR Foundation provides a restricted set of responsibilities and database objects to carry out selected HR tasks. Users of non-HRMS applications, for example, Oracle Projects, often use the Oracle HR Foundation responsibility to gain access to HR functionality.

For information on the database objects and menus available in HR Foundation, see:

APIs Available for Foundation Users

Menus Available for Foundation Users

Requirements

What is hr foundation.

HR Foundation is a responsibility available for bundling with specified Oracle Applications. In order to further applications integration, Oracle HR has delivered a responsibility which groups together a set of Forms which can be used by other Oracle Applications. This functionality delivers more processes than the current Shared HR facility, and so makes more shared processes available for use. Examples include competency management.

Working with HR Foundation

Apis available for hr foundation users.

Application Programmatic Interfaces (APIs) are a logical grouping of all external process routines. The Oracle HRMS API strategy delivers a set of PL/SQL packages procedures and functions that provide an open interface to the database.

Oracle® Integration Repository, an integral part of Oracle E-Business Suite, is a compilation of information about the numerous interface endpoints exposed by Oracle applications. The full list of public APIs and the purpose of each API is available in the integration repository. See: Oracle Integration Repository Overview, Oracle Integration Repository User Guide . For information on how to access and use Oracle Integration Repository, see: Accessing Oracle Integration Repository, Oracle Integration Repository User Guide

For information on how to call APIs, see the technical essay APIs in Oracle HRMS

This topic lists APIs supported for HR Foundation. HR Foundation users can only use restricted parameters in some APIs. See: APIs to Which Restrictions Apply for HR Foundation

List of APIs Supported for HR Foundation

The following table shows the APIs delivered with Oracle HR Foundation.

Important: Legislation WW = All Legislations

APIs to Which Restrictions Apply for HR Foundation

The following table includes APIs with a list of restricted parameters that you can use for each API. For APIs that are not part of this restricted list, you use all parameters.

Menus Available for HR Foundation Users

The Employee Self-Service Foundation responsibility offers the following menu items in the Oracle Applications Framework interface:

The Manager Self-Service Foundation responsibility offers the following menu items in the Oracle Applications Framework interface:

The HR Foundation responsibility offers the following menu items in the Professional User (forms) Interface:

Windows for HR Foundation Users

Enter person.

Use the Enter Person window to enter, maintain, and view basic personal information and addresses for employees and external contacts. For your employees, you can also enter work assignment information, which includes organization, job, position, work location, and supervisor's name.

Note: In Oracle Learning Management this window is called the Enter Person window.

The following Oracle applications use this form:

Engineering

Project Accounting

Training: You can use this form to enter training resources.

Work in Process: You must enter an employee if you want to define and charge an employee rate to a job or repetitive schedule.

Entering a New Employee

Recording employment termination and rehiring ex-employees.

Resource Creation, Oracle Learning Management User Guide

Viewing Person Information

Use the Enter Person window to enter and maintain basic personal information, addresses, and work assignment details for your employees.

The system warns you if you enter two people with the same name and birth date.

Note: You cannot use this form if Oracle Human Resources is installed at your site. You must use the HR People window, which maintains a datetracked history of any changes you make to employee records.

Prerequisites

Select your employee number generation method in the Financial Options window.

To enter a new employee

Enter the employee's name. Only the last name is required.

If your enterprise uses manual employee number entry, enter an employee number and national identifying number (such as Social Security Number in the US).

If your enterprise uses automatic number generation, enter a national identifying number only. The employee number automatically displays when you save your entries in this window.

Enter the employee's hire date in the first of the Employment Dates fields. This must be on or before today's date.

In the Email field, you can enter an email user ID.

In the Mail field, select Home or Office to indicate the employee's preferred mail address. For example, Oracle Payables mails employee expense checks to this address.

Save your work and choose More... to enter additional information.

Choose Address to enter address information.

Choose Assignment to enter work assignment and supervisor information.

Entering Addresses

You can enter as many addresses as necessary for each employee in the Address region of the Person Information window.

Set up any address types you want to use (such as home or office) as Lookups for the Lookup Type ADDRESS_TYPE.

To enter an address

Select a national address style.

A window opens with the address format for the country you select.

Enter your address information in this window and choose OK.

This returns you to the Address window.

Select an address type, such as home, or weekend, or office.

You can check Primary for the address you are creating, to identify the employee's main address. By default, the first address you enter is the Primary address.

Only one address at any time can be a person's Primary address.

Additional Information: Default address styles are predefined for many countries. You can create address styles for other countries

Note: See: Oracle HRMS Technical Reference Manual

Entering Employee Work Assignments

You enter information about an employee's work assignments in the Assignment tabbed region.

If you want to assign the employee to an organization, job, or position, you must define these work structures first.

See: Creating an Organization, Oracle HRMS Enterprise and Workforce Management Guide

See: Defining Jobs, Oracle HRMS Enterprise and Workforce Management Guide

See: Defining Positions, Oracle HRMS Enterprise and Workforce Management Guide

Enter the work address of the assignment in the Location window.

See: Setting Up Locations, Oracle HRMS Enterprise and Workforce Management Guide

Set up your Accounting key flexfield.

To enter a new assignment

Select the organization to which you want to assign the employee. The default organization is the Business Group.

If a location is defined for this organization, it also appears as a default.

Select the job, position, and supervisor for the employee's assignment.

The employee's supervisor is the default next approver for all purchasing documents if the Use Approval Hierarchies check box in the Financial Options window is checked.

The Ledger field displays the ledger for your installation. The Default Expense Account field displays the concatenated description of the Account.

In some applications, you can select another flexfield structure that the employee's expenses should debit. Oracle Payables uses this information to generate expense reports for your employees.

Enter a location for the assignment.

Updating Employee Assignments Over Time

Project Accounting users can select the Assignment History region to view and update employee assignments over time.

The date fields in this region display the start and end dates of the assignment.

In the New Assignment region, you can insert a change to the assignment, as from a particular start date. The Assignment History region shows one row for every change to the organization, job, location, manager, or billing title of the assignment. Each row is valid between the dates shown at the bottom of the Assignment History region.

To insert a change to an assignment

Query the assignment you want to change in the Assignment History alternative region of the Person Information window.

In the New Assignment region, enter the start date of the change.

The other fields in this region display the values that are valid at this date.

Update any of the values in the New Assignment region, and save your changes.

To record employment termination

Query the employee in the Enter Person window.

Enter a termination date in the second of the Employment Dates fields, and save.

To cancel a termination

Clear the termination date in the second of the Employment Dates fields, and save.

To rehire an ex-employee

Query the ex-employee in the Enter Person window.

Change the value of the first date within the Employment Dates fields to the new hire date.

Click tab. This action must clear the termination date in the second of the Employment Dates fields.

Save the changes.

You can use the Enter Person window to view information about a person or about groups of employees or other people.

To find selected people

If the Find People window does not open automatically, choose Find from the Query menu.

You can enter any combination of the following criteria:

a person's name or employee number

a national identifying number (such as social security number)

work location

Choose the Find button to run the query.

Choose Next Record from the Go menu to see each person retrieved by the query.

Defining a Position (non-HRMS users)

You use the Position window to define positions within your organizations and to add them to position hierarchies. You can also enter the skills that position holders require and the grades to which they can be assigned. You can enter position evaluation scores, if you have set up a position evaluation system.

To define a position

Enter a start date early enough to handle any historical information you want to enter. You can also enter an end date, but ensure it is before the end date of all the valid grades for the position.

Tip: Consider using a fixed date as a default for your initial setup, for example, 01-JAN-1901. This will simplify your data-entry.

Enter a unique name for the position.

If there is more than one segment in the Position Name flexfield, a window opens when you enter the Name field. You must enter a unique combination of segments in this window.

Select the organization and job for this position. They must have a start date on or before the start date of this position.

Note: You cannot change the organization or job once you have saved the definition.

You can set up several positions that have the same job in the same organization. Each position name must be unique.

Optionally, select a status for the position. If the status is Valid or blank, employees can be assigned to the position. If the status is Invalid or any other status defined at your site, employees cannot be assigned to the position.

Location and Standard Conditions default from the organization, but you can override the defaults.

If there is a probation period for this position, you can enter its length in the Probation Period tabbed region.

In the Absence tabbed region, select Yes in the Replacement Required field if you want users to be warned that they should enter the name of a replacement when they enter an absence for a holder of this position. You can do this for positions where it is essential that a person is in charge at all times.

You can select the position that should be held by the person to cover as relief in case of absence.

In the Planned Successor tabbed region, you can select the position from which a successor will move to fill this position.

Save your position.

If you want to add the position to one or more position hierarchies, choose the Reporting To button. Select a hierarchy and the name of the position to which this position reports.

Choose the Evaluation button to enter evaluation information and an overall evaluation score for the position.

See: Entering Evaluation Information, Oracle HRMS Enterprise and Workforce Management Guide .

Choose the Requirements button to enter position requirements, such as required qualifications or valid experience, to help you match people to roles.

See: Entering Job and Position Requirements, Oracle HRMS Enterprise and Workforce Management Guide

Note: You use the Competence Requirements window to enter competencies if you are following the competence approach.

Choose the Valid Grades button to enter the grades to which position holders can be assigned.

See: Entering Valid Grades for Jobs or Positions, Oracle HRMS Enterprise and Workforce Management Guide

Choose the Occupancy button to view all those people who have held a selected position or who are applying for it, and the dates of their occupancy. This information could be relevant for selecting people with the necessary skills for similar positions.

See: Viewing Position Occupancy, Oracle HRMS Enterprise and Workforce Management Guide

Choose the Work Choices button to enter work choices that can affect an employee's, applicant's, contractor's, or ex-employee's capacity to be deployed within your enterprise (or a customer's).

See: Entering Work Choices for a Job or Position, Oracle HRMS Enterprise and Workforce Management Guide

Choose the Survey Mapping button to link salary survey lines to your position.

See: Mapping Salary Survey Lines, Oracle HRMS Compensation and Benefits Management Guide

Choose the Extra Information button to enter any additional information required by your enterprise.

See: Entering Extra Information, Oracle HRMS Configuring, Reporting, and System Administration Guide .

Entering and Maintaining Contingent Worker Information (HR Foundation)

Note: This information is for HR Foundation users only.

This template has no DateTrack support. If you enter a contingent worker with a future start date, the record disappears when you save it. You can retrieve the record in the Find window if you set the effective date to the relevant contingent worker's start date.

Use the Enter and Maintain Contingent Workers template.

To enter or maintain contingent worker information

To create a new contingent worker, click the New icon. To update an existing contingent worker, select the contingent worker in the People Management Data Organizer and click Show Details.

On the Personal tab, enter or update the contingent worker's name information.

Click the Communication tab to enter or update home or work contact details.

Click the Assignment tab to enter or update information about the contingent worker's supplier, assignment, or work structures.

Note: If you use Oracle Services Procurement to provide purchase order information, you cannot alter assignment or supplier information obtained from the purchase order or purchase order line. However, you can select a different purchase order or purchase order line.

Save your work.

Scripting on this page enhances content navigation, but does not change the content in any way.

Oracle Apps Solutions

Thursday, august 28, 2014, update employee assignment/criteria - hrms apis, 14 comments:.

Please, I have ran series of API for assignments criteria for newly created employees, but not working what could be the problem?

Hi, I hope you are passing all the mandatory parameters, what error you are getting?

I entered all the mandatory fields for this API: hr_assignment_api.update_emp_asg_criteria only, or do i need to also run hr_assignment_api.update_emp_asg. The assignment_id, is it the person type are they referring to here or ASSIGNMENT_ID in the assignment table The procedure will completed successfully and committed but when i checked it in the front end,it has not effect. Please, Help.

If you are updating only criteria, no need to call update_emp_asg. assignment_id is the assignment_id. Is it an employee or contingent worker? are you committing it after the API call? provide me your anonymous API calling block here.

The API is more than what I can paste here, this page is complaining of 4,096 characters. if you can send me your mail

When, try to debug the script, it gives me this error: Error report - ORA-20001: The primary key specified is invalid Cause: The primary key values specified are invalid and do not exist in the schema. Action: Check the primary key values before attempting to carry out the operation again. ORA-06512: at "APPS.HR_ASSIGNMENT_API", line 16095 ORA-06512: at line 30

Why trying to make further research i got this error: Error report - ORA-20001: The primary key specified is invalid Cause: The primary key values specified are invalid and do not exist in the schema. Action: Check the primary key values before attempting to carry out the operation again. ORA-06512: at "APPS.HR_ASSIGNMENT_API", line 16095 ORA-06512: at line 30

You will get an email option on clicking on my profile name. In between please double check the datatype of all the parameters.

I have sent you a mail. Thank you.

Ademola - Not sure, if the issue is resolved for you. If this is not yet resolved and you're facing this issue in the database, please follow the below steps. To implement the solution, please execute the following steps: 1. Set NLS_LANG to 'US' or ‘AMERICAN’ in TOAD/SQL Developer: a. For SQL Developer: 1. Select Tools > Preferences > Database > NLS Parameters 2. Update to have Language = AMERICAN and Territory = AMERICA b. For TOAD: 1. Access NLS Parameters, from the Database menu 2. Select Administer| -> NLS Parameters 3. Set the NLS_LANGUAGE to ‘AMERICAN’ 2. Retest the issue. 3. Migrate the solution as appropriate to other environments.

Hi The issue is with the out parameter l_asg_object_version_number not being passed correctly. Its is a bug on this API. Select the object_version_number from assignment table for the assignment ID and pass it to the API. Kamlesh

Thanks for your blog!!. Keep updating JAVA Development Services HR Pay Roll Software SAP Software Services Hotel Billing Software Web Design Company Hospital Management Software

Hi, I'm getting error while calling hr_assignment_api.update_emp_asg_criteria API. Error: -ORA-20001: FLEX-DUPLICATE CCID: N, CCID Thanks, Ankush.

Hi Ankush1818, Were you able to solve the Error: -ORA-20001: FLEX-DUPLICATE CCID: N, CCID ?

• Install App

SQL & PL/SQL

For appeals, questions and feedback about Oracle Forums, please email [email protected] . Please ask technical questions in the appropriate category. Thank you!

Updting Emp Details via API - Assignment_id - says its null but it cant be!

HR Assignment API error - Supervisor not valid for duration of the assignment

Sanchita Sarkar

Thanks, Sanchita

Tuesday, September 4, 2012

Hr employee supervisor update api.

No comments:

Post a comment.

ERPstuff - Oracle EBS Community

You love we care since 2006 by Malik Sikandar Hayat.

Skip to content

• Unanswered topics
• Active topics
• Home Forums Oracle Applications (EBS) R12 & 11i HCM (Human Capital Management)

Hr_Assignment_Api.update_emp_asg_criteria ERROR

Post by m_muzamil_khan » Sun Aug 08, 2010 7:16 am

Post by ERP_GURU » Mon Aug 09, 2010 11:44 pm

Post by m_muzamil_khan » Tue Aug 10, 2010 1:06 am

Post by ERP_GURU » Tue Aug 10, 2010 12:05 pm

Post by eng_ahmad_2007 » Mon Sep 06, 2010 6:23 pm

Return to “HCM (Human Capital Management)”

Who is online

Users browsing this forum: No registered users and 0 guests

• Home Forums
• All times are UTC
• Delete cookies

Powered by phpBB ® Forum Software © phpBB Limited

Privacy | Terms