My Oracle Support Banner

Person Data Removal Tool (PDRT) - Difference in Status Value Returned, When Check Constraints API "EBS_DRT_UTILS.ENTITY_CHECK_CONSTRAINTS" is Called From Back-end (DB) and When Called From PDRT Application Page (Doc ID 2897113.1)

Last updated on SEPTEMBER 19, 2022

Applies to:

Oracle Human Resources - Version 12.2.10 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
-----------------------------------

Observed that, there is difference in status value returned when the "Check Constraint" program is executed from Back-end (Data Base) using Application Program Interface (API) and when called from PDRT application page.

                     When program is called from API, status gets updated as "Check Constraint", but when the same is done from application, status gets updated as "No Constraint".

EXPECTED BEHAVIOR
-----------------------------

Expect that, there should be no difference in status value returned when the "Check Constraint" program is executed from Back-end (Data Base) using Application Program Interface (API) as well as when called from PDRT application page.

STEPS
-----------------------

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

1. Login using "HRMS Manager" Responsibility.

2. Navigate to Function "Person Data Removal".

3. In the launched page, click on"Add FND" or "Add HR" or "Add TCA" button.

4. In the launched page, search and select the person record which needs to be removed and clcik on "Add", this will add the person to the Removal list.

5. Now select that person record from the removal list and in the "action" List Of Values (LOV), select "Check Constraint" and click on "Go" button.

6. The check constraint concurrent program is called and once it is completed, we can see the status getting updated as "No Constraint".

7. Now when the same program is called for this person from back-end using API script given below, the status returned is "Check Constraint".

8. So observe that, there is a difference of status getting returned for the "check constraint" concurrent program when called from API and when called from application.
  

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.