UNABLE TO CLOSE EAM WORK ORDERS WHEN RUNNING CONCURRENT PROGRAM EAMCDCL FROM API (Doc ID 1057154.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Enterprise Asset Management - Version 12.0.4 to 12.0.6 [Release 12]
Information in this document applies to any platform.

Symptoms

On : 12.0.4 version, Work Execution

We are unable to Close a EAM Workorder when the concurrent program EAMCDCL is submitted through fnd_request.submit_request standard API. The Program is running successfully and actually creating the necessary reports but unable to change the WorkOrder status from Completed to Closed.
The instance that we have having this problem is RODEV and is a new QA environment instance.

Expect it to work

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

SELECT wip_dj_close_temp_s.NEXTVAL INTO v_group_id FROM DUAL;


2.

MERGE INTO wip_dj_close_temp a
USING (SELECT rec_c_wo_close.wip_entity_id AS wip_entity_id,
rec_c_wo_close.organization_id AS organization_id,
rec_c_wo_close.wip_entity_name AS wip_entity_name,
primary_item_id AS primary_item_id,
rec_c_wo_close.report_type AS status_type,
SYSDATE AS actual_close_date,
v_group_id AS GROUP_ID
FROM mi2k_vw_orcl_wo
WHERE wip_entity_name = rec_c_wo_close.wip_entity_name
AND organization_id = rec_c_wo_close.organization_id) b
ON ( a.wip_entity_name = b.wip_entity_name
AND a.organization_id = b.organization_id)
WHEN NOT MATCHED THEN
INSERT (wip_entity_id, organization_id, wip_entity_name,
primary_item_id, status_type, actual_close_date, GROUP_ID)
VALUES (b.wip_entity_id, b.organization_id, b.wip_entity_name,
b.primary_item_id, b.status_type, b.actual_close_date,
b.GROUP_ID)
WHEN MATCHED THEN
UPDATE
SET a.actual_close_date = b.actual_close_date,
a.GROUP_ID = b.GROUP_ID;


3.

COMMIT;


4.

v_request_id :=
fnd_request.submit_request ('EAM',
'EAMCDCL',
'',
TO_CHAR (SYSDATE, 'YYYY/MM/DD HH24:MI'),
FALSE,
TO_CHAR (rec_c_wo_close.organization_id),
'',
'',
'',
'',
'',
'',
'',
'',
'',
'',
'',
'',
TO_CHAR (v_group_id),
TO_CHAR (v_select_jobs),
'',
'',
'',
3,
'',
CHR (0),
'',
'',
'',
'',
'',
'',
'',
'',
'',
'',
'',
'',
'',
'',
'',
'',
'',
'',
'',
'',
'',
'',
'',
'',
'',
'',
'',
'',
'');

Changes

Upgraded to 12.0.6 from 12.0.4

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms