Oracle Apps Solutions
Thursday, august 28, 2014, update employee assignment/criteria - hrms apis, 14 comments:.
![hr_assignment_api.update_emp_asg_criteria hr_assignment_api.update_emp_asg_criteria](https://www.blogger.com/img/blogger_logo_round_35.png)
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 ?
![](http://rss3.fun/777/templates/cheerup/res/banner1.gif)
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
HR Competence Element API | HR_COMPETENCE_ELEMENT_API | pecelapi.pkh | create_competence_element | Creates a competence element | Yes | WW | Yes |
update_competence_element | Updates competence element details | Yes | WW | No | |||
delete_competence_element | Deletes a competence element | Yes | WW | No | |||
update_personal_comp_element | Updates a personal competence element | Yes | WW | No | |||
HR Competences API | HR_COMPETENCES_API | pecpnapi.pkh | create_competence | Creates a competence | Yes | WW | Yes |
update_competence | Updates a competence | Yes | WW | Yes | |||
delete_competence | Deletes a competence | Yes | WW | No | |||
HR Employee API | HR_EMPLOYEE_API | peempapi.pkh | create_employee | Creates a new employee | Yes | WW | Yes |
re_hire_ex_employee | Hires an ex-employee as an employee | Yes | WW | Yes | |||
HR Location API | HR_LOCATION_API | hrlocapi.pkh | create_location | Creates locations | Yes | WW | Yes |
update_location | Updates the details of a location | Yes | WW | Yes | |||
delete_location | Deletes a location | Yes | WW | No | |||
HR Organization API | HR_ORGANIZATION_API | hrorgapi.pkh | create_organization | Creates a new organization within the scope of an existing business group | Yes | WW | Yes |
update_organization | Updates an existing organization | Yes | WW | Yes | |||
delete_organization | Deletes an organization | Yes | WW | No | |||
create_org_classification | Creates an organization classification for an existing organization | Yes | WW | Yes | |||
enable_org_classification | Enables the classification of an organization | Yes | WW | No | |||
disable_org_classification | Disables the classification of an organization | Yes | WW | No | |||
create_org_information | Creates organization information | Yes | WW | Yes | |||
create_org_manager | Creates cost center manager information | Yes | WW | No | |||
update_org_information | Updates an information type of an organization | Yes | WW | No | |||
update_org_manager | Updates an organization manager relationship | Yes | WW | No | |||
delete_org_manager | Deletes an organization manager relationship | Yes | WW | No | |||
create_business_group | Creates a business group | Yes | WW | Yes | |||
create_operating_unit | Creates a new operating unit within an existing business group | Yes | WW | No | |||
update_operating_unit | Updates a new operating unit starting with an existing business group | Yes | WW | No | |||
create_legal_entity | Creates an organization with a classification of legal entity | Yes | WW | No | |||
create_bgr_classif | Creates a new classification for an existing business group, namely operating unit and legal entity accounting | Yes | WW | No | |||
create_legal_entity_classif | Creates a legal entity classification for an existing organization and populates information type data | Yes | WW | No | |||
create_oper_unit_classif | Creates an operating unit classification for an existing organization | Yes | WW | No | |||
trans_org_name | Translates an organization name | Yes | WW | No | |||
HR Person Address API | HR_PERSON_ADDRESS_API | peaddapi.pkh | create_person_address | Creates a new address for a given person | Yes | WW | Yes |
update_person_address | Updates a particular address for a given person | Yes | WW | Yes | |||
create_job_group | Creates a job group | Yes | WW | Yes | |||
update_job_group | Updates a job group | Yes | WW | Yes | |||
delete_job_group | Deletes a job group | Yes | WW | No | |||
HR Job API | HR_JOB_API | pejobapi.pkh | create_job | Creates a job in the specified business group | Yes | WW | Yes |
HR Phone API | HR_PHONE_API | pephnapi.pkh | create_phone | Creates a phone record | Yes | WW | Yes |
update_phone | Updates the phone record for a person | Yes | WW | Yes | |||
delete_phone | Deletes a phone record | Yes | WW | No | |||
HR Position API | HR_POSITION_API | peposapi.pkh | create_position | Creates a position that is a specific occurrence of a job within an organization | Yes | WW | Yes |
update_position | Updates a position | Yes | WW | Yes | |||
delete_position | Deletes a position | Yes | WW | Yes | |||
HR Person API | HR_PERSON_API | peperapi.pkh | update_person | Updates person information | Yes | WW | Yes |
HR Assignment API | HR_ASSIGNMENT_API | peasgapi.pkh | update_emp_asg | Updates employee assignment details that do not affect entitlement to element entries | Yes | WW | Yes |
update_emp_asg_criteria | Updates attributes of an employee assignment that affects the entitlement criteria for any element entry | Yes | WW | Yes | |||
update_cwk_asg | Updates a contingent worker assignment | Yes | WW | No | |||
update_cwk_asg_criteria | Updates attributes of a contingent worker assignment that may affect the entitlement to element entries | Yes | WW | No | |||
HR Ex-Employee API | HR_EX_EMPLOYEE_API | peexeapi.pkh | actual_termination_emp | Terminates an employee | Yes | WW | Yes |
final_process_emp | Set the final process date for a terminated employee | Yes | WW | Yes | |||
HR Grade API | HR_GRADE_API | pegrdapi.pkh | create_grade | Creates a grade | Yes | WW | Yes |
update_grade | Updates a grade | Yes | WW | No | |||
delete_grade | Deletes a grade | Yes | WW | Yes | |||
HR Contingent Worker API | HR_CONTINGENT_WORKER_API | pecwkapi.pkh | create_cwk | Creates a new contingent worker | Yes | WW | No |
convert_to_cwk | Converts an existing person to a contingent worker | Yes | WW | No | |||
terminate_placement | Terminates a contingent worker | Yes | WW | No | |||
reverse_terminate_placement | Reverses a contingent worker termination | Yes | WW | No | |||
HR Rating Scales API | HR_RATING_SCALES_API | perscapi.pkh | create_rating_scale | Creates a rating scale | Yes | WW | Yes |
update_rating_scale | Updates a rating scale | Yes | WW | Yes | |||
delete_rating_scale | Deletes a rating scale | Yes | WW | No | |||
HR Rating Levels API | HR_RATING_LEVELS_API | pertlapi.pkh | create_rating_level | Creates a rating level | Yes | WW | Yes |
update_rating_level | Updates a rating level | Yes | WW | Yes | |||
delete_rating_level | Deletes a rating level | Yes | WW | No | |||
HR Qualification Type API | HR_QUALIFICATION_TYPE_API | peeqtapi.pkh | create_qualification_type | Creates a qualification type | Yes | WW | Yes |
update_qualification_type | Updates a qualification type | Yes | WW | Yes | |||
delete_qualification_type | Deletes a qualification type | Yes | WW | No | |||
HR Change Start Date API | HR_CHANGE_START_DATE_API | pehirapi.pkh | update_start_date | Changes the start date of an employee or contingent worker | Yes | WW | No |
HR Hierarchy Element API | HR_HIERARCHY_ELEMENT_API | peoseapi.pkh | create_hierarchy_element | Creates an organization hierarchy element record | Yes | WW | Yes |
update_hierarchy_element | Updates an organization hierarchy element record | Yes | WW | No | |||
delete_hierarchy_element | Deletes an organization hierarchy element | Yes | WW | No | |||
HR Position Hierarchy Element API | HR_POS_HIERARCHY_ELE_API | pepseapi.pkh | create_pos_hierarchy_ele | Creates position hierarchy elements | Yes | WW | No |
update_pos_hierarchy_ele | Updates a parent to a new child or a child to a new parent | Yes | WW | No | |||
delete_pos_hierarchy_ele | Deletes a position hierarchy element | Yes | WW | No | |||
HR Competence Outcome API | HR_COMPETENCE_OUTCOME_API | pecpoapi.pkh | create_outcome | Creates a competence outcome | Yes | WW | Yes |
update_outcome | Updates a competence outcome | Yes | WW | Yes | |||
delete_outcome | Deletes a competence outcome | Yes | WW | No |
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.
HR Employee API | HR_EMPLOYEE_API | peempapi.pkh | create_employee | None | P_VALIDATE P_HIRE_DATE P_BUSINESS_GROUP_ID P_LAST_NAME P_PREVIOUS_LAST_NAME P_MAILSTOP P_OFFICE_NUMBER P_INTERNAL_LOCATION P_CORRESPONDENCE_LANGUAGE P_KNOWN_AS P_SEX P_DATE_OF_BIRTH P_EMAIL_ADDRESS P_EMPLOYEE_NUMBER P_EXPENSE_CHECK_SEND_TO_ADDRESS P_FIRST_NAME P_MIDDLE_NAMES P_NATIONAL_IDENTIFIER P_TITLE P_ATTRIBUTE_CATEGORY P_ATTRIBUTE1-30 P_BACKGROUND_CHECK_STATUS P_BACKGROUND_DATE_CHECK P_BLOOD_TYPE P_HONORS P_LAST_MEDICAL_TEST_BY P_LAST_MEDICAL_TEST_DATE P_PERSON_TYPE_ID P_ON_MILITARY_SERVICE P_PRE_NAME_ADJUNCT P_RESUME_EXISTS P_RESUME_LAST_UPDATED P_SECOND_PASSPORT_EXISTS P_DATE_EMPLOYEE_DATA_VERIFIED P_NATIONALITY P_REGISTERED_DISABLED_FLAG P_STUDENT_STATUS P_WORK_SCHEDULE P_SUFFIX P_TOWN_OF_BIRTH P_REGION_OF_BIRTH P_COUNTRY_OF_BIRTH P_MARITAL_STATUS P_USES_TOBACCO_FLAG P_DPDNT_ADOPTION_DATE P_DPDNT_VLNTRY_SVCE_FLAG P_ORIGINAL_DATE_OF_HIRE |
re_hire_ex_employee | None | P_VALIDATE P_HIRE_DATE P_PERSON_ID P_OBJECT_VERSION_NUMBER P_REHIRE_REASON P_PERSON_TYPE_ID | |||
HR Contingent Worker API | HR_CONTINGENT_WORKER_API | pecwkapi.pkh | create_cwk | None | P_VALIDATE P_BUSINESS_GROUP_ID P_LAST_NAME P_EMAIL_ADDRESS P_NPW_NUMBER P_FIRST_NAME P_MIDDLE_NAMES P_PREVIOUS_LAST_NAME P_MAILSTOP P_TITLE P_KNOWN_AS P_START_DATE P_SEX P_DATE_OF_BIRTH P_NATIONAL_IDENTIFIER P_OFFICE_NUMBER P_INTERNAL_LOCATION P_CORRESPONDENCE_LANGUAGE P_ATTRIBUTE_CATEGORY P_ATTRIBUTE1-30 P_PERSON_TYPE_ID P_BACKGROUND_CHECK_STATUS P_BACKGROUND_DATE_CHECK P_BLOOD_TYPE P_COUNTRY_OF_BIRTH P_DPDNT_VLNTRY_SVCE_FLAG P_HONORS P_LAST_MEDICAL_TEST_DATE P_MARITAL_STATUS P_NATIONALITY P_ON_MILITARY_SERVICE P_PRE_NAME_ADJUNCT P_REGION_OF_BIRTH P_REGISTERED_DISABLED_FLAG P_RESUME_EXISTS P_RESUME_LAST_UPDATED P_TOWN_OF_BIRTH P_USES_TOBACCO_FLAG P_WORK_SCHEDULE P_SECOND_PASSPORT_EXISTS P_STUDENT_STATUS P_SUFFIX P_DPDNT_ADOPTION_DATE P_LAST_MEDICAL_TEST_BY P_EXP_CHECK_SEND_TO_ADDRESS P_DATE_EMPLOYEE_DATA_VERIFIED P_HOLD_APPLICANT_DATE_UNTIL P_ORIGINAL_DATE_OF_HIRE |
convert_to_cwk | The parameter P_EFFECTIVE_DATE must be set to the system date. The parameter P_DATETRACK_UPDATE_MODE must be set to CORRECTION. | P_VALIDATE P_EFFECTIVE_DATE P_PERSON_ID P_OBJECT_VERSION_NUMBER P_NPW_NUMBER P_PERSON_TYPE_ID P_DATETRACK_UPDATE_MODE | |||
terminate_placement | The parameter P_EFFECTIVE_DATE must be set to the system date. The parameters P_FINAL_PROCESS_DATE and P_LAST_STANDARD_DATE must be set to the same date as the parameter P_ACTUAL_TERMINATION_DATE. | P_EFFECTIVE_DATE P_VALIDATE P_FINAL_PROCESS_DATE P_LAST_STANDARD_PROCESS_DATE P_PERSON_ID P_DATE_START P_OBJECT_VERSION_NUMBER P_ACTUAL_TERMINATION_DATE P_PERSON_TYPE_ID P_ASSIGNMENT_STATUS_TYPE_ID P_TERMINATION_REASON P_ATTRIBUTE_CATEGORY P_ATTRIBUTE_1-30 | |||
reverse_terminate_placement | None | P_VALIDATE P_PERSON_ID P_ACTUAL_TERMINATION_DATE P_CLEAR_DETAILS | |||
HR Person API | HR_PERSON_API | peperapi.pkh | update_person | The parameter P_EFFECTIVE_DATEmust be set to the system date. The parameter P_DATETRACK_UPDATE_MODE must be set to CORRECTION. | P_EFFECTIVE_DATE P_DATETRACK_UPDATE_MODE P_VALIDATE P_HIRE_DATE P_BUSINESS_GROUP_ID P_LAST_NAME P_SEX P_DATE_OF_BIRTH P_EMAIL_ADDRESS P_EMPLOYEE_NUMBER P_NPW_NUMBER P_EXPENSE_CHECK_SEND_TO_ADDRESS P_TITLE P_FIRST_NAME P_MIDDLE_NAMES P_NATIONAL_IDENTIFIER P_PREVIOUS_LAST_NAME P_KNOWN_AS P_MAILSTOP P_OFFICE_NUMBER P_INTERNAL_LOCATION P_CORRESPONDENCE_LANGUAGE P_ATTRIBUTE_CATEGORY P_ATTRIBUTE1-30 P_OBJECT_VERSION_NUMBER P_PERSON_ID P_PERSON_TYPE_ID P_DATE_EMPLOYEE_DATA_VERIFIED P_MARITAL_STATUS P_NATIONALITY P_REGISTERED_DISABLED_FLAG P_BACKGROUND_CHECK_STATUS P_BACKGROUND_DATE_CHECK P_BLOOD_TYPE P_HOLD_APPLICANT_DATE_UNTIL P_HONORS P_LAST_MEDICAL_TEST_BY P_LAST_MEDICAL_TEST_DATE P_ON_MILITARY_SERVICE P_PRE_NAME_ADJUNCT P_RESUME_EXISTS P_RESUME_LAST_UPDATED P_SECOND_PASSPORT_EXISTS P_STUDENT_STATUS P_WORK_SCHEDULE P_SUFFIX P_USES_TOBACCO_FLAG P_DPDNT_ADOPTION_DATE P_DPDNT_VLNTRY_SVCE_FLAG P_ORIGINAL_DATE_OF_HIRE P_ADJUSTED_SVC_DATE P_TOWN_OF_BIRTH P_REGION_OF_BIRTH P_COUNTRY_OF_BIRTH |
HR Ex-Employee API | HR_EX_EMPLOYEE_API | peexeapi.pkh | actual_termination_emp | The parameter P_EFFECTIVE_DATE must be set to the system date. The parameter P_LAST_STANDARD_DATE must be set to the same date as the parameter P_ACTUAL_TERMINATION_DATE. | P_VALIDATE P_PERIOD_OF_SERVICE_ID P_OBJECT_VERSION_NUMBER P_ACTUAL_TERMINATION_DATE P_EFFECTIVE_DATE P_LAST_STANDARD_PROCESS_DATE P_PERSON_TYPE_ID P_ASSIGNMENT_STATUS_TYPE_ID P_LEAVING_REASON |
final_process_emp | The parameter P_FINAL_PROCESS_DATE must be set to the same date as was set for the parameter P_ACTUAL_TERMINATION_DATE in the ACTUAL_TERMINATION_EMP API. | P_FINAL_PROCESS_DATE P_VALIDATE P_PERIOD_OF_SERVICE_ID P_OBJECT_VERSION_NUMBER | |||
HR Assignment API | HR_ASSIGNMENT_API | peasgapi.pkh | update_emp_asg | The parameter P_EFFECTIVE_DATE must be set to the system date. The parameter P_DATETRACK_UPDATE_MODE must be set to CORRECTION. When you perform a correction to an employee's supervisor, the new supervisor must exist for the entire duration of the employee's assignment. If you want to assign a supervisor who does not exist for the entire duration of the assignment, then you can use the People window. | P_EFFECTIVE_DATE P_DATETRACK_UPDATE_MODE P_VALIDATE P_ASSIGNMENT_ID P_SUPERVISOR_ID P_OBJECT_VERSION_NUMBER P_ASSIGNMENT_NUMBER P_DEFAULT_CODE_COMB_ID P_SET_OF_BOOKS_ID P_ASS_ATTRIBUTE_CATEGORY P_ASS_ATTRIBUTE1-30 P_CHANGE_REASON P_FREQUENCY P_MANAGER_FLAG P_NORMAL_HOURS P_PERF_REVIEW_PERIOD P_PERF_REVIEW_PERIOD_FREQUENCY P_PROBATION_PERIOD P_PROBATION_UNIT P_PROJECTED_ASSIGNMENT_END P_SAL_REVIEW_PERIOD P_SAL_REVIEW_PERIOD_FREQUENCY P_TIME_NORMAL_FINISH P_TIME_NORMAL_START P_BARGAINING_UNIT_CODE P_LABOUR_UNION_MEMBER_FLAG P_HOURLY_SALARIED_CODE P_NOTICE_PERIOD P_NOTICE_PERIOD_UOM P_EMPLOYEE_CATEGORY P_WORK_AT_HOME P_JOB_POST_SOURCE_NAME P_SUPERVISOR_ASSIGNMENT_ID P_DATE_PROBATION_END P_INTERNAL_ADDRESS_LINE P_SOURCE_TYPE P_ESTABLISHMENT_ID P_CONCAT_SEGMENTS P_ASSIGNMENT_STATUS_TYPE_ID P_CONTRACT_ID |
update_emp_asg_criteria | The parameter P_EFFECTIVE_DATE must be set to the system date. The parameter P_DATETRACK_UPDATE_MODE must be set to CORRECTION. | P_EFFECTIVE_DATE P_DATETRACK_UPDATE_MODE P_VALIDATE P_ASSIGNMENT_ID P_OBJECT_VERSION_NUMBER P_POSITION_ID P_JOB_ID P_ORGANIZATION_ID P_LOCATION_ID P_GRADE_ID P_SEGMENT1-30 P_SUPERVISOR_ASSIGNMENT_ID P_EMPLOYMENT_CATEGORY P_ESTABLISHMENT_ID P_CONCAT_SEGMENTS P_CONTRACT_ID | |||
update_cwk_asg | The parameter P_EFFECTIVE_DATE must be set to the system date. The parameter P_DATETRACK_UPDATE_MODE must be set to CORRECTION. | P_EFFECTIVE_DATE P_DATETRACK_UPDATE_MODE P_VALIDATE P_ASSIGNMENT_ID P_OBJECT_VERSION_NUMBER P_ASSIGNMENT_NUMBER P_SUPERVISOR_ID P_TITLE P_SET_OF_BOOKS_ID P_VENDOR_ID P_VENDOR_EMPLOYEE_NUMBER P_MANAGER_FLAG P_EMPLOYMENT_CATEGORY P_ASS_ATTRIBUTE_CATEGORY P_ASS_ATTRIBUTE1-30 P_CHANGE_REASON P_ESTABLISHMENT_ID P_PROJECT_TITLE P_FREQUENCY P_INTERNAL_ADDRESS_LINE P_LABOUR_UNION_MEMBER_FLAG P_NORMAL_HOURS P_PROJECTED_ASSIGNMENT_END P_ASSIGNMENT_STATUS_TYPE_ID P_CONCAT_SEGMENTS P_SUPERVISOR_ASSIGNMENT_ID P_SOURCE_TYPE P_TIME_NORMAL_FINISH P_TIME_NORMAL_START P_ASSIGNMENT_CATEGORY P_SCL_SEGMENT1-30 | |||
HR Position API | HR_POSITION_API | peposapi.pkh | create_position | This API can use all HR Foundation parameters for (HR foundation version). | |
HR Competence Element | HR_COMPETENCE_ELEMENT_API | pecelapi.pkh | create_competence_element | The parameter P_EFFECTIVE_DATE must be set to the system date. The parameter P_TYPE must be set to PERSONAL. | P_EFFECTIVE_DATE P_TYPE P_VALIDATE P_BUSINESS_GROUP P_COMPETENCE_ID P_PROFICIENCY_LEVEL P_RATING_LEVEL P_PERSON_ID P_EFFECTIVE_DATE_FROM P_EFFECTIVE_DATE_TO P_SOURCE_OF_PROFICIENCY_LEVEL P_CERTIFICATION_DATE P_CERTIFICATION_METHOD P_NEXT_CERTIFICATION_DATE P_COMMENTS P_ATTRIBUTE_CATEGORY P_ATTRIBUTE1 – 20 P_PARTY_ID |
update_competence_element | The parameter P_EFFECTIVE_DATE must be set to the system date. | P_EFFECTIVE_DATE P_COMPETENCE_ELEMENT_ID P_OBJECT_VERSION_NUMBER P_VALIDATE P_PROFICIENCY_LEVEL P_RATING_LEVEL P_EFFECTIVE_DATE_FROM P_EFFECTIVE_DATE_TO P_SOURCE_OF_PROFICIENCY_ LEVEL P_CERTIFICATION_DATE P_CERTIFICATION_METHOD P_NEXT_CERTIFICATION_DATE P_COMMENTS P_ATTRIBUTE_CATEGORY P_ATTRIBUTE1 – 20 P_PARTY_ID | |||
delete_competence_element | None | P_COMPETENCE_ELEMENT_ID P_OBJECT_VERSION_NUMBER P_VALIDATE | |||
update_personal_comp_element | The parameter P_EFFECTIVE_DATE must be set to the system date. This API automatically maintains a historical record of the old competence profile entry if the effective date and the proficiency level have changed. The old competence profile entry is end dated and a new competence profile record is created. | P_EFFECTIVE_DATE P_COMPETENCE_ELEMENT_ID P_OBJECT_VERSION_NUMBER P_VALIDATE P_PROFICIENCY_LEVEL P_EFFECTIVE_DATE_FROM P_EFFECTIVE_DATE_TO P_SOURCE_OF_PROFICIENCY_LEVEL P_CERTIFICATION_DATE P_CERTIFICATION_METHOD P_NEXT_CERTIFICATION_DATE P_COMMENTS P_ATTRIBUTE_CATEGORY P_ATTRIBUTE1 - 20 |
Menus Available for HR Foundation Users
The Employee Self-Service Foundation responsibility offers the following menu items in the Oracle Applications Framework interface:
Employee Self-Service Foundation | - |
- | All Actions Awaiting Your Attention |
- | Personal Details |
Professional Details | - |
- | Education and Qualifications |
- | Other Professional Qualifications |
- | Competency Profile |
- | Work Preferences |
- | Resume |
The Manager Self-Service Foundation responsibility offers the following menu items in the Oracle Applications Framework interface:
Manager Self-Service Foundation | - |
- | All Actions Awaiting Your Attention |
- | Manager Actions |
Professional Details | - |
- | Education and Qualifications |
- | Other Professional Qualifications |
- | Competency Profile |
- | Work Preferences |
- | Resume |
The HR Foundation responsibility offers the following menu items in the Professional User (forms) Interface:
People | - | - | Enter personal and assignment information |
- | Enter and Maintain Employees | - | Enter employees, employee assignments, and applications |
- | Enter and Maintain Contingent Workers | - | Enter contingent workers and contingent worker assignments |
- | View Worker Assignment History | - | View assignment history for a worker |
Talent Management | - | - | Talent Management |
- | Rating Scales | - | Define general methods of measuring competencies |
- | Competencies | - | Define competencies |
-- | Schools and Colleges | - | Define name and location of training establishments |
- | Qualifications Types | - | Define, categorize, and rank qualifications |
Work Structures | - | - | Enter work structures |
- | Define Locations | - | - |
- | Organization | - | Enter organizational information |
- | - | Description | Enter information for an organization |
- | - | Organization Manager | Select and maintain organization managers |
- | - | Hierarchy | Structure organizations into hierarchies |
- | - | Global Hierarchy | Structure organizations into global hierarchies |
- | Job | - | Enter job-related information |
- | - | Description | Enter job names |
- | - | Job Group | Enter job groups |
- | Position | - | Enter position-related information |
- | - | Description | Enter position names |
- | - | Hierarchy | Structure positions into hierarchies |
- | Grade | - | Enter grade-related information |
- | - | Description | Enter grade names |
- | Other Definitions | - | - |
- | - | Application Utilities Lookups | Enter lookup types and values |
- | - | User Profile Options | Review your personal profile options |
Security | - | - | Define security restrictions |
-- | Profile | - | Define security profiles to restrict record access |
- | Global Profile | - | Define global security profiles to restrict record access |
- | Information Types Security | - | Define information types security |
Processes and Reports | - | - | - |
- | Submit Processes and Reports | - | Submit processes or run standard reports |
- | View Requests | - | View any request submitted for processing |
- | View Reports | - | View reports online |
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.
- Install App
E-Business Suite
For appeals, questions and feedback about Oracle Forums, please email [email protected] . Technical questions should be asked in the appropriate category. Thank you!
Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.
Oracle has updated its online Terms of Use and Community Guidelines and introduced a Community Integrity Policy . These changes document Community specific rules and Oracle’s content moderation practices including use of automated tools, appeals process, and Oracle’s contact details. If you object to any changes, you may request that your account be closed by contacting [email protected] . Your continued use of Oracle Communities means that you are consenting to the updated terms.
![](http://rss3.fun/777/templates/cheerup/res/banner1.gif)
HR_ASSIGNMENT_API.update_emp_asg_criteria error
![hr_assignment_api.update_emp_asg_criteria](https://objectstorage.us-phoenix-1.oraclecloud.com/p/usZakwxzsyewMRwrzramy7IpDhL0NnhNKqIsS4oCJQZlZGXvq0UNqBQXLk6rcQI4/n/axciphqpnohg/b/forums-prod-app/o/300000/static/images/default-user-avatar.png)
I am using following api HR_ASSIGNMENT_API.update_emp_asg_criteria to update job information. But its completing with below error.
Leaving: hr_assignment_api.update_emp_asg_criteria 999
Error Info:-E--Error while updating assignment criteria. Error Code: -20001. Error Message: ORA-20001: FLEX-COMBINATION HAS EXPIRED:
Please assist.
Sign Up to our social questions and Answers to ask questions, answer people’s questions, and connect with other people.
Confirm Password *
Login to our social questions & Answers to ask questions, answer people’s questions & connect with other people.
Username or email *
Forgot Password
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Sorry, you do not have permission to ask a question, You must login to ask a question.
Sorry, you do not have permission to add post.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
![Oraask Oraask Logo](https://www.oraask.com/wp-content/uploads/2020/04/oraask-white-min.png)
Oracle HRMS API to update people group in oracle
![hr_assignment_api.update_emp_asg_criteria Oracle HRMS API to update people group in oracle](https://www.oraask.com/wp-content/uploads/2019/04/Oracle-HRMS-API-to-Update-People-Group-after-min-759x485.jpg)
Introduction:
The People Group flexfields lets you add your own key information to the
Employee Assignment. You use each segment to define the different groups of employees which exist within your own enterprise.
update people group using “hr_assignment_api.update_emp_asg_criteria” API
Forms Or Pages:
![Oracle HRMS API to update people group in oracle 1 Oracle-HRMS-API-to-Update-People-Group-before](https://www.oraask.com/wp-content/uploads/2019/04/Oracle-HRMS-API-to-Update-People-Group-before-min-1024x429.jpg)
API IN/OUT Parameters :
— IN p_effective_date IN DATE Required — IN p_datetrack_update_mode IN VARCHAR2 Required — IN p_assignment_id IN NUMBER Required — IN p_validate IN BOOLEAN Required — IN p_called_from_mass_update IN BOOLEAN Required — IN p_organization_id IN NUMBER Required — IN Out p_people_group_id NUMBER — IN Out p_object_version_number NUMBER — IN Out p_special_ceiling_step_id NUMBER — Out p_group_name VARCHAR2 — Out p_effective_start_date DATE — Out p_effective_end_date DATE — Out p_org_now_no_manager_warning BOOLEAN — Out p_other_manager_warning BOOLEAN — Out p_spp_delete_warning BOOLEAN — Out p_entries_changed_warning VARCHAR2 — Out p_tax_district_changed_warning BOOLEAN — Out p_concatenated_segments BOOLEAN
API Parameters clarifications:
- @param p_effective_date Can be either the current date or a date in the future.
- @param p_datetrack_update_mode control parameter enables you to define the type of DateTrack change to be made.
- @param p_assignment_id System-generated primary key column Primary Key for “PER_ASSIGNMENTS_F”.
- @param p_validate control parameter (the default value is FALSE) to executes all validation for that business function.
- @param p_called_from_mass_update Set to TRUE if the API is called from the Mass Update Processes.
- @param p_organization_id Foreign Key for“HR_ALL_ORGANIZATION_UNITS”.
- @param p_people_group_id Foreign Key for “PAY_PEOPLE_GROUPS”.
- @param p_object_version_number 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.
- @param p_special_ceiling_step_id API sets this attribute to null on the database and the latest value is passed out of the API. If you do not want to alter this attribute, set the calling logic variable to hr_api.g_number.???
- @param p_group_name Identifies the name of an existing group in the workspace.
- @param p_effective_start_date and @param p_effective_end_date are all maintained by DateTrack. The START_DATE is the date when the first record for this person was created. The earliest EFFECTIVE_START_DATE for a person is equal to the START_DATE, so that If p_validate is false, then set to the effective end date for the created assignment. If p_validate is true, then set to null.
- @param p_org_now_no_manager_warning Set to true if this assignment is a manager, the organization is updated and there is now no manager in the previous organization. Set to false if another manager exists in the previous organization.
- @param p_other_manager_warning If set to true, then a manager existed in the organization prior to calling this API and the manager flag has been set to ‘Y’ for yes.
- @param p_spp_delete_warning Set to true when grade step and point placements are date effectively ended or purged by the update of the assignment. Both types of change occur when the Grade is changed and spinal point placements exist over the updated date range. Set to false when no grade step and point placements are affected.
- @param p_entries_changed_warning This is set to ‘Y’, if at least one element entry was altered due to the assignment change. It is set to ‘S’, if at least one salary element entry was affected (This is a more specific case than ‘Y’).
- @param p_tax_district_changed_warning Always set to False, since contingent worker assignments are not eligible to have a Payroll, therefore cannot be included in the United Kingdom processing which determines the value of this parameter.
- @param p_concatenated_segments If p_validate is false, set to Soft Coded Key Flexfield concatenated segments, if p_validate is true, set to null.
API Calling example:
Final result:.
![Oracle HRMS API to update people group in oracle 2 Oracle-HRMS-API-to-Update-People-Group-after](https://www.oraask.com/wp-content/uploads/2019/04/Oracle-HRMS-API-to-Update-People-Group-after-min-1024x443.jpg)
Hope this helpful. If you found it simple and easy to understand, we would love to provide you and your friends a simple solution for your problems. Thanks.
![Ahmed_Shmes Ahmed_Shmes](https://www.oraask.com/wp-content/uploads/2019/03/download-1-84x84.jpg)
Ahmed_Shmes
Related posts.
![hr_assignment_api.update_emp_asg_criteria API to Create User-Defined Table UDT in Oracle APPS R12](https://www.oraask.com/wp-content/uploads/2023/03/API-to-Create-User-Defined-Table-UDT-in-Oracle-APPS-R12-300x180.png)
API to Create User-Defined Table UDT in Oracle APPS R12
![hr_assignment_api.update_emp_asg_criteria API to Update Extra Information Types EIT in Oracle APPS R12](https://www.oraask.com/wp-content/uploads/2022/10/API-to-Update-Extra-Information-Types-EIT-in-Oracle-APPS-R12-300x180.png)
API to Update Extra Information Types EIT in Oracle APPS ...
![hr_assignment_api.update_emp_asg_criteria API to Create Organization Manager in Oracle APPS R12](https://www.oraask.com/wp-content/uploads/2022/09/API-to-Create-Organization-Manager-in-Oracle-APPS-300x180.png)
API to Create Organization Manager in Oracle APPS R12
![hr_assignment_api.update_emp_asg_criteria API to create a new absence type in oracle apps r12](https://www.oraask.com/wp-content/uploads/2019/05/Create-a-new-absence-type-in-oracle-apps-r12-2-300x180.png)
API to create a new absence type in oracle apps ...
Leave a comment cancel reply.
You must login to add a new comment.
Insert/edit link
Enter the destination URL
Or link to existing content
ERPstuff - Oracle EBS Community
Since 2006 by Malik Sikandar Hayat - Oracle ACE Pro
Skip to content
![hr_assignment_api.update_emp_asg_criteria hr_assignment_api.update_emp_asg_criteria](https://www.erpstuff.com/images/phpbb_ads/f535c14c6b74ce52665c19cc8aa50ca2.jpg)
- 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
Oracle Apps Technical
Thursday 13 march 2014, oracle hrms api – update employee assignment & supervisor adding.
Emp Num | Organization | GCC Group | Position | Job | Payroll | Location | Status | Salary Basis | Supervisor Number | GOSI - Employer | Process Flag | Error Message |
3 | Chief Business Support Office | No.No.Yes | Chief Business Support Officer.Chief Business Support Office | Chief Business Support Officer | EATC Payroll | Riyadh Head Office | Active Assignment | EATC Monthly Salary | 911 | Etihad Atheeb Telecommunication Company | N |
3 comments:
![hr_assignment_api.update_emp_asg_criteria hr_assignment_api.update_emp_asg_criteria](https://www.blogger.com/img/blogger_logo_round_35.png)
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.
![](http://rss3.fun/777/templates/cheerup/res/banner1.gif)
COMMENTS
How to Create a Hardcoded API to Update an Employee Assignment Using the API hr_assignment_api.update_emp_asg_criteria? (Doc ID 815007.1) Last updated on NOVEMBER 01, 2023. Applies to: Oracle Human Resources - Version 11.5.10.2 and later Information in this document applies to any platform. ...
Hi all, I am trying to update the emp assignment using the api. But i get the error, ORA-06550: line 18, column 4: PLS-00306: wrong number or types of arguments in call to 'UPDATE_EMP_ASG_CRITERIA' ORA-06550: line 18, column 4: PL/SQL: Statement ignored This is my code, what is wrong i couldnt find what is wrong in these, Please help. DECLARE l_people_group_id number; l_object_version ...
HR_ASSIGNMENT_API.UPDATE_EMP_ASG_CRITERIA API Errors with "ORA-20001: The primary key specified is invalid" (Doc ID 737145.1) Last updated on MAY 09, 2024. Applies to: Oracle Human Resources - Version 11.5.10.2 to 11.5.10.2 [Release 11.5.10] Information in this document applies to any platform. Symptoms
Steps to Reproduce: The issue can be reproduced at will with the following steps: 1. Login to SQL Developer or TOAD. 2. Call api hr_assignment_api.update_emp_asg_criteria from wrapper code
1. Select a discussion category from the picklist. 2. Enter a title that clearly identifies the subject of your question. 3. In the body, insert detailed information, including Oracle product and version.
Hi, We are using the above API to update People Group Flexfield in Core HRMS (UK). Version of Apps is 11.5.10.2 But the issue is that along with updating the People Group Flexfield it is also end-dating the Basic Pay Element on that Effective Date. any idea on what the issue could be?
In hr_assignment_api.update_emp_asg_criteria,w henever we update location ID or organization ID, we received " ERROR** Update of EMPLOYEE ASSIGN UPDATE = DateTrack Mode ORA-20001: FLEX-VALUE DOES NOT EXIST: N, VALUE,1054980, N, SEGMENT, HR_GENERALIST, N, VALUESET, " .
elsif l_mode = 'CRITERIA' then. /* This API updates attributes of the employee assignment that affect the. * entitlement criteria for any element entry. * The assignment must be an employee assignment. The assignment must exist as. * of the effective date of the change. */. hr_assignment_api.update_emp_asg_criteria.
Since we only need to update location/organization for suppliers and does not care about full HR/Payroll, my question is if hr_assignment_api.update_emp_asg_criteria can be disabled for the validations in below codes? Thank you in advance for any inputs. hr_assignment_api.update_emp_asg_criteria
Calling HR_ASSIGNMENT_API.UPDATE_EMP_ASG_CRITERIA to Upload HR Data Errors with: ORA-20001: The HR Object is Invalid (Doc ID 748679.1) Last updated on JULY 19, 2024. Applies to: Oracle Human Resources - Version 11.5.10.2 and later Information in this document applies to any platform. Symptoms
HR Assignment API: HR_ASSIGNMENT_API: peasgapi.pkh: update_emp_asg: The parameter P_EFFECTIVE_DATE must be set to the system date. The parameter P_DATETRACK_UPDATE_MODE must be set to CORRECTION. When you perform a correction to an employee's supervisor, the new supervisor must exist for the entire duration of the employee's assignment.
Hi Ralph, I am working on Oracle apps R12. I want to transfer employee data to assignment. I have already created the employees.
For appeals, questions and feedback about Oracle Forums, please email [email protected] questions should be asked in the appropriate category. Thank you!
1. Select a discussion category from the picklist. 2. Enter a title that clearly identifies the subject of your question. 3. In the body, insert detailed information, including Oracle product and version.
HR_ASSIGNMENT_API.UPDATE_EMP_ASG_CRITERIA throws ORA-20001: System Error: Procedure at Step 40 (Doc ID 1945587.1) Last updated on MAY 11, 2024. Applies to: Oracle Human Resources - Version 12.1.1 and later Information in this document applies to any platform. Symptoms. When the segment of People Group Key flexfield is not defined or not enabled ...
API Parameters clarifications: @param p_effective_date Can be either the current date or a date in the future.; @param p_datetrack_update_mode control parameter enables you to define the type of DateTrack change to be made.; @param p_assignment_id System-generated primary key column Primary Key for "PER_ASSIGNMENTS_F".; @param p_validate control parameter (the default value is FALSE) to ...
1. Select a discussion category from the picklist. 2. Enter a title that clearly identifies the subject of your question. 3. In the body, insert detailed information, including Oracle product and version.
A user asks for help with an error when updating employee assignment through an API in Oracle EBS 11i. Other users suggest checking the object version number, the assignment dates, and the primary key values.
Run the custom concurrent program to update the attribute1 of DFF on Assignment form to an employee who reports to the manager 3. The program internally calls API HR_ASSIGNMENT_API.UPDATE_EMP_ASG to update the DFF
Oracle HRMS API - Update Employee Assignment & Supervisor Adding To Update Employee Supervisor, Manager Flag, Bargaining Unit, Labour Union Member Flag, Time Card, Work Schedule, Normal Hours, Frequency, Time Normal Finish, Time Normal Start, Default Code Combination, Set of Books Id
Nov 5, 2015 8:59AM edited Nov 10, 2015 9:17AM in PL/SQL (MOSC) 4 comments Answered. i'm trying to update an employee ASSIGNMENT using. HR_ASSIGNMENT_API.UPDATE_EMP_ASG_CRITERIA (. HR_ASSIGNMENT_API.UPDATE_EMP_ASG_CRITERIA (. p_validate => FALSE.
Steps to reproduce: 1. Call hr_assignment_api.update_emp_asg_criteria with all the appropriate parameters . Cause
Understood that this API validates that the person needs to be an employee as at assignment date however in the Oracle EBS Application screen under HRMS, there are fields such as Supervisor and Probation info that can be updated manually even though the person is still an applicant, not yet an employee. Is there any HR API procedure to update ...