oracle供应商新建默认中国,求助：R12建立供应商的问题

在Metalink帮你查的：

--------------------------------

TIP:  Click help for a detailed explanation of this page.

Bookmark Go to End

Subject:  Error 'ORA-20001: Only one pending Concurrent Request is allowed for ARHDQMSS at any given time' While Updating Employee's Assignment in Poland Legislation

Doc ID:  762547.1 Type:  PROBLEM

Modified Date :  21-JAN-2009 Status:  MODERATED

In this Document

Symptoms

Cause

Solution

References

--------------------------------------------------------------------------------

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.

Applies to:

Oracle Human Resources - Version: 12.0.4

This problem can occur on any platform.

Symptoms

-- Problem Statement:

On 12.0 in Test:

When attempting to hr_assignment_api.update_emp_asg the following error occurs:

ERROR

-ORA-20001: Only one pending Concurrent Request is allowed for ARHDQMSS at any given time

-- Steps To Reproduce:

The issue can be reproduced at will with the following steps:

1. HZ: Ignore Concurrent Request limit for DQM Synchronization set to Y

2. DQM Synchronization Method set to Automatic

3. Run API Call to create employee and update assignment

Cause

Default values for the Soft Coded KeyFlexfield segments are set to hr_api.g_varchar2 in API

hr_assignment_api.update_emp_asg.

When PL assignment is updated through API hr_assignment_api.update_emp_asg, and if the values of

mandatory PL segments are not passed, they are defaulted.

The PER_PL_ASSIGNMENT API checks that the value for these segments must not be explicitly set to

NULL, i.e NULL must not be passed for mandatory segments when updating the assignment. But it

doesn't check the value of those segments in the database if its defaulted.

As a result, one was able to update the PL assignment, if mandatory args/segments were not passed.

Additional check to pass the notice period units must be added when the notice_period, notice

period date and notice period end date are passed.

Also Contract Category (Segment3) cannot be changed once set. But the API is allowing the change it.

This issue has been fixed in the file peplasgp.pkb in version 120.9.12000000.6

You have file peplasgp.pkb 120.9.12000000.4 which is lower than this fixed version.

This is explained in the following bug:

Bug 7554037: HR: ERROR WHILE UPDATING EMPLOYEE'S ASSIGNMENT ORA-20001: ONLY ONE PENDING

Solution

-- To implement the solution, please execute the following steps::

1. Download and review the readme and pre-requisites for Patch 7554037.

2. Ensure that you have taken a backup of your system before applying the recommended patch.

3. Apply the patch in a test environment.

4. Confirm the following file versions:

peplasgp.pkb 120.9.12000000.6

You can use the commands like the following:

strings -a $PER_TOP/patch/115/sql/peplasgp.pkb |grep '$Header'

5. Retest the issue.

6. Migrate the solution as appropriate to other environments.

References

Bug 7554037 - HR: ERROR WHILE UPDATING EMPLOYEE'S ASSIGNMENT ORA-20001: ONLY ONE PENDING

Note 465993.1 - How does the DQM Real Time (Automatic) Synchronization work for R12?

Keywords

12.0.4 ; API ; SYNCHRONIZATION ; EMPLOYEE~ASSIGNMENT ;