My Oracle Support Banner

Close Discrete Jobs Takes Long Time (Doc ID 2424274.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Work in Process - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

Actual Behavior
When closing discrete jobs, following sql statement takes long time.

SELECT WIP_ENTITY_NAME
FROM
WIP_DJ_CLOSE_TEMP WDCT WHERE WDCT.GROUP_ID = :B2 AND WDCT.ORGANIZATION_ID =
:B1 AND EXISTS (SELECT '1' FROM PO_RELEASES_ALL PR, PO_HEADERS_ALL PH,
PO_DISTRIBUTIONS_ALL PD, PO_LINE_LOCATIONS_ALL PL WHERE PD.WIP_ENTITY_ID =
WDCT.WIP_ENTITY_ID AND PD.DESTINATION_ORGANIZATION_ID = :B1 AND
PD.PO_LINE_ID IS NOT NULL AND PD.LINE_LOCATION_ID IS NOT NULL AND
PH.PO_HEADER_ID = PD.PO_HEADER_ID AND PL.PO_HEADER_ID = PD.PO_HEADER_ID AND
PL.LINE_LOCATION_ID = PD.LINE_LOCATION_ID AND PR.PO_RELEASE_ID (+) =
PD.PO_RELEASE_ID AND (PL.CANCEL_FLAG IS NULL OR PL.CANCEL_FLAG = 'N') AND
(PL.QUANTITY_RECEIVED<(PL.QUANTITY-PL.QUANTITY_CANCELLED)) AND
NVL(PL.CLOSED_CODE,'OPEN') <> 'FINALLY CLOSED' ) OR EXISTS (SELECT '1' FROM
PO_REQUISITION_LINES_ALL PRL WHERE PRL.WIP_ENTITY_ID = WDCT.WIP_ENTITY_ID
AND PRL.DESTINATION_ORGANIZATION_ID = :B1 AND NVL(PRL.CANCEL_FLAG, 'N') =
'N' AND PRL.LINE_LOCATION_ID IS NULL AND NVL(PRL.CLOSED_CODE,'OPEN') <>
'FINALLY CLOSED' ) OR EXISTS (SELECT '1' FROM PO_REQUISITIONS_INTERFACE_ALL
PRI WHERE PRI.WIP_ENTITY_ID = WDCT.WIP_ENTITY_ID AND
PRI.DESTINATION_ORGANIZATION_ID = :B1 )

Expected Behavior
No performance issue

Steps to Reproduce

  1. Run Close Discrete Jobs.

Changes

 

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
Changes
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.