Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 13

Action for Closing WIP Jobs in ‘Failed Close’ Status

There are various reason for which the Jobs get stuck in Failed Close status while trying to close the Job.

To view pending transactions and conditions for a job:

Navigate through Discrete JobsClose Discrete Jobs(Form)Query the JobGo To ToolsPending Actions:

If a restriction exists, the check boxes indicating the type of restrictions is marked. An explanation of each restrictive
condition follows:

 Material Transactions: Components have been issued to the job and there are records in the
WIP_REQUIREMENTS_OPERATIONS table. We can view information about issues material in the
Material Requirements.
 Uncosted Material Transactions: There are uncosted transaction records in the
MTL_MATERIAL_TRANSACTIONS table.

 Pending Material Transactions: There are unprocessed material transaction records in the
MTL_MATERIAL_TRANSACTIONS_TEMP table.

 Resource Transactions: Resources have been charged and there are records in the
WIP_OPERATIONS_RESOURCES table.

 Pending Resource Transactions: There are pending resource and overhead transaction records in the
WIP_COST_TXN_INTERFACE table.

 Pending Move Transactions: There are pending move transaction records in the
WIP_MOVE_TXN_INTERFACE table.

 PO Requisitions: There are purchase requisitions in the PO_REQUISITION_LINES table.

 Pending PO Requisitions: There are unprocessed records in the PO_REQUISITION_ INTERFACE table.
This document will cover the Jobs for which there are Pending Move/Resource Transactions in error state.

1. Deleting error records in WIP_MOVE_TXN_INTERFACE Table.


 Create Back up Table for the error out records in WIP_MOVE_TXN_INTERFACE Table.
 Delete Interface error out records through Backend or front end.
 Supported Queries.

2. Taking Back up and count of Failed Close Jobs between Date Range
 Count of Jobs between 01-Oct-2017 to 31-Mar-2018 in different status.

STATUS_TYPE STATUS_MEANING COUNT


1 Unreleased 210
6 On Hold 28
4 Complete 5680
3 Released 3524
7 Cancelled 15232
12 Closed 135163
15 Failed Close 6384

Query Used:

 Total Jobs Details in Failed Close Status.

Targeted Jobs for


Closure.xlsx

Query Used.

3. Delete Pending Resource records in error from Interface from Front end.
4. Close Discrete Jobs in Failed Close status for each Organization of given Date Range:

Note :The Parameter is as per the records in the Jobs in the Target Jobs Sheet.

A. Close Discrete Jobs (P07):


Organization : P07

Class : FCOE,MCOE,NFCOE

From Job Start Date : 01-APR-2017

To Job Start Date : 31-OCT-2019

Status : Failed Close


B. Close Discrete Jobs (P08):

Organization : P08

Class : P08_STD

From Job Start Date : 01-APR-2017

To Job Start Date : 31-OCT-2019

Status : Failed Close


C. Close Discrete Jobs (P12):

Organization : P12

Class : LA

From Job Start Date : 01-APR-2017

To Job Start Date : 31-OCT-2019

Status : Failed Close


D. Close Discrete Jobs (P19):

Organization : P19

Class : MCOE

From Job Start Date : 01-APR-2017

To Job Start Date : 31-OCT-2019

Status : Failed Close


E. Close Discrete Jobs (P21):

Organization : P21

Class : P21_STD

From Job Start Date : 01-APR-2017

To Job Start Date : 31-OCT-2019

Status : Failed Close


F. Close Discrete Jobs (P20):

Organization : P20

Class : POWER

From Job Start Date : 01-APR-2017

To Job Start Date : 31-OCT-2019

Status : Failed Close


5. Post Job Closure Count(Only Failed Jobs should be targeted rest count should remain intact(Except Closed
Jobs)):

STATUS_TYPE STATUS_MEANING COUNT


1 Unreleased 210
6 On Hold 28
4 Complete 5699
3 Released 3504
7 Cancelled 15233
12 Closed 141537
15 Failed Close 10

6. Detail of the Jobs Closed and Failed Close.


Job Closure
Details.xlsx

Job Failed Closed due to Pending Transactions:

Below queries to check the same:

--Get the WIP_ENTITY_ID for the job that failed to close


SELECT wip_entity_name, wip_entity_id, organization_id
FROM apps.wip_entities
WHERE wip_entity_name = '4520650'
AND organization_id = 816;

--Pending Move Transactions


SELECT count(*)
FROM apps.WIP_MOVE_TXN_INTERFACE
WHERE ORGANIZATION_ID = 816
AND WIP_ENTITY_ID = 5716025; -- use WIP_ENTITY_ID from query #1

--Pending Resource Transactions


SELECT count(*)
FROM apps.WIP_COST_TXN_INTERFACE
WHERE ORGANIZATION_ID = 816
AND WIP_ENTITY_ID = 5716025; -- use WIP_ENTITY_ID from query #1

--Pending Material Transactions


SELECT *--count(*)
FROM apps.MTL_MATERIAL_TRANSACTIONS_TEMP MMTT
WHERE ORGANIZATION_ID = 816
AND TRANSACTION_SOURCE_TYPE_ID = 5
AND TRANSACTION_SOURCE_ID NOT IN
(SELECT TXN_SOURCE_ID
FROM apps.MTL_TXN_REQUEST_LINES
WHERE TXN_SOURCE_ID = MMTT.TRANSACTION_SOURCE_ID
AND ORGANIZATION_ID = MMTT.ORGANIZATION_ID
AND LINE_STATUS = 9)
AND TRANSACTION_SOURCE_ID = 5716025; -- use WIP_ENTITY_ID from query #1 --
MOVE_ORDER_LINE_ID = 107946341

Select * from apps.mtl_system_items_b


where inventory_item_id = '8365080' and ORGANIZATION_ID = 816; -- segment1 = '151X1222STSP01'

Select * from apps.mtl_txn_request_lines


where LINE_ID = 107946341;

---- Uncosted Transactions


SELECT count(*)
FROM apps.MTL_MATERIAL_TRANSACTIONS
WHERE COSTED_FLAG IN ('N','E')
AND TRANSACTION_SOURCE_TYPE_ID = 5
AND ORGANIZATION_ID = 816
AND TRANSACTION_SOURCE_ID = 5716025; -- use WIP_ENTITY_ID from query #1

SELECT count(*)
FROM apps.WIP_OPERATION_YIELDS
WHERE ORGANIZATION_ID = 816
AND STATUS IN (1, 3)
AND WIP_ENTITY_ID = 5716025; -- use WIP_ENTITY_ID from query #1

-- Pending LPN Drop Transactions


SELECT count(*)
FROM apps.WIP_LPN_COMPLETIONS WLC,
apps.WMS_LICENSE_PLATE_NUMBERS LPN
WHERE WLC.ORGANIZATION_ID = 816
AND WLC.LPN_ID = LPN.LPN_ID
AND LPN.LPN_CONTEXT = 2
AND WIP_ENTITY_ID = 5716025; -- use WIP_ENTITY_ID from query #1

You might also like