Mfg WIP Advisor Webcast 2013 1030Understanding Discrete Job ClosureUnderstanding Discrete Job ClosureUnderstanding Discrete Job ClosureUnderstanding Discrete Job ClosureUnderstanding Discrete Job ClosureUnderstanding Discrete Job ClosureUnderstanding Discrete Job ClosureUnderstanding Discrete Job ClosureUnderstanding Discrete Job Closure

1
Copyright 2013, Oracle and/or its affiliates. All rights reserved.
Oracle Advisor Webcast Program
Current schedule Archived recordings Doc ID 740966.1
Future Advisor Webcasts

Upcoming live webcasts and recent recordings: VOICE STREAMING ENABLED Teleconference Access: US & Canada: 866- 627-3315 Toll Number: +1-706-758-7972 Global Toll-Free: 1148600.1 Password: Oracle WIP WIP Webcast Calendar/Archive Doc ID 1319827.1 All Webcast Calendar/Archive Doc ID 740966.1 What advisor webcast topics do YOU want to see presented? Visit the Work In Process and Flow Manufacturing My Oracle Support Community today to let us know.
Safe Harbor Statement

The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decision. The development, release, and timing of any features or functionality described for Oracles products remains at the sole discretion of Oracle.
Oracle Advisor Webcast

Understanding Discrete Job Closure
Basem Abdelrahim
Objectives
Assist users in better understanding and troubleshooting of discrete job closure issues. Address month end issues where material or resource transactions are stuck. This, in turn, will prevent discrete job closure.
Agenda
[1] Technical Overview [2] Discrete Job Closure Flow
[3] Troubleshooting [4] Diagnostics

[5] Resources
[1] Technical Overview

Job closure process allows WIP discrete jobs to change status to Closed so that
open requirement does not appear as valid demand in the Item Supply/Demand form.
You can close several standard and non-standard discrete jobs simultaneously. You
can also close individual discrete jobs.
[1] Technical Overview (cont.)

WICDCL module (Close Discrete Jobs)
This program is called when closing discrete jobs via Form or SRS.
EAMCDCL module (Close EAM Work Orders)

This program is only used to close EAM Maintenance Work Orders. This program does not close WIP discrete jobs. This program calls the WIP concurrent request to close EAM Work Orders.
10

Benefits of Closing a Job
1. 2. 3. 4.
Closing a Job will prevent Cost Update transaction from updating items/resources in a job. Closing a Job writes off any balance remaining in wip elemental valuation accounts Closing a Job will prevent any transactions from occurring. All variances are computed at job close.
11
Costing Job Close Transactions

1.
Closing a job calculates final costs and variances. The actual close date that you specify determines the accounting period that WIP uses to recognize variances. You can back date the close to a prior open period if desired.
2.
The close process writes off the balances remaining in the WIP elemental valuation accounts to the elemental variance accounts that you defined by accounting class, leaving a zero balance remaining in the closed job.
12

Two Ways to Close Discrete Jobs
1. 2.
Close Discrete Jobs (FORM) Close Discrete Jobs (SRS)
No API/Open Interface Available

There is no 'automated way or public API to process the job closure.
13

Closing Non Standard Jobs
1.
You can manually close non standard jobs whenever you choose. The job status is set to Closed Jobs with asset type class are costed in the same way as standard jobs, and all variances are computed at job close. For jobs with expense type class, an accounting close is performed on a periodic basis.
2.
3.
14

Information associated with a job is not deleted when job is closed.
You can view information for closed discrete jobs. You also can print reports on
closed jobs and closed job values.

You can close jobs of any status except jobs that are Closed, Pending Close,
Pending Bill Load, and Pending Routing Load.

Prior to closing discrete jobs, you can review job value information using the
Discrete Job Value Report, which lists standard and non-standard asset jobs, or the Expense Job Value Report, which lists non-standard expense jobs. See: Discrete Job Value Report, page 16-18 and Expense Job Value Report, page 16-23.
15
[2] Job Closure Flow

The Close Discrete Jobs (Form) enables you to: N: Work In Process -> Discrete -> Close Discrete Job (Form)
1. 2. 3. 4. 5.
Submit and immediately process job close requests Specify a close date other than the system date Unclose discrete jobs Check and resubmit failed job close requests View discrete jobs before closing them
16
[2] Job Closure Flow (cont.)

The Close Discrete Jobs (SRS) enables you to: N: Work In Process -> Discrete -> Close Discrete Job (SRS)
1. 2. 3. 4. 5. 6.
Specify when to submit the close request (concurrent or scheduled processing) Specify a close date other than the system date Use criteria for closing jobs based on a range of accounting classes, job numbers, and dates - including release, start, and completion dates Exclude or include jobs linked to sales orders from the processing Exclude or include uncompleted jobs from the processing Exclude or include jobs with pending transactions
17

Close Requirements
1.
In the Close Discrete Jobs (Form), you cannot close a job that has pending material, resource, or move transactions including those that the concurrent manager has not processed. You also cannot close a job that has uncosted material transactions. If you attempt to close a job for which pending or uncosted transactions exist, the close process fails and the job status changes to Failed Close. When a job with outside processing operations is changed to complete, closed, or canceled status - an informational warning message displays if open purchase orders or requisitions exist for any of the operations. Changing a job status to completed, closed, or canceled is prevented if open reservations exist.
2.
3.
4.
18

Close Requirements (cont.)
5.
If you attempt one of these transactions for a job linked to a sales order, an error message displays. You have two options in order to continue:
a. b.
Unlink the sales order reserved to this job Reduce the job quantity of the job to equal the completed quantity
6. 7.
If you close a job for an MPS-planned item with a quantity complete different from the quantity originally scheduled, the MPS for the actual quantity is automatically updated. In Oracle Warehouse Management organizations, open move orders for a job are cancelled when the job is closed. However, you must perform an unload task transaction to delete material requirement and move order record.
19

Unclose Requirements
1. 2. 3. 4. 5.
You cannot unclose a job that does not have a status of Closed. You cannot unclose a job that is linked to a sales order. You also cannot unclose a job that was closed in a now closed accounting period. The form function parameter WIP_WIPDJMDF_CLOSE enables the Unclose option in the Tools menu. See Figure 1. If you do not want Unclose to display in the menu, set the parameter to No. The default for this option is Yes. See Figure 2.
20

N: Work In Process -> Discrete Jobs -> Close Discrete Jobs (Form)
Figure 1
21 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

N: System Administrator -> Application -> Function
Figure 2
22 Copyright 2013, Oracle and/or its affiliates. All rights reserved.

To Re-open Closed Jobs
1. 2.
From the queried jobs displayed, select which jobs to reopen. When you reopen a job, it reverts to its pre-close status.

For example, reopening a job that had a pre-close status of Complete changes its status from Closed back to Complete. See: Work In Process Users Guide - Discrete Job Statuses, page 12-6.
3. 4.
Choose Unclose from the Tools menu to submit the request. When you choose Unclose, job statuses are immediately changed to their pre-close status.
23
[3] Troubleshooting
Check for Stuck Records via Application or SQL*PLUS: ** At the Application Level:
1.
Pending Transactions form N: Inventory -> Transactions -> Pending Transactions Resubmit errored transactions if any exists under Error tab.
2.
Pending Move Transactions form N: Work In Process -> Move Transactions -> Pending Move Transactions Resubmit errored transactions if any exists under Error button
24
[3] Troubleshooting (cont.)
** At the Application Level:

3.
Pending Resource Transactions form N: Work In Process -> Resource Transactions -> Pending Resource Transactions Resubmit errored transactions if any exists under Error button
4.
View Material Transactions form N: Work In Process -> Material Transactions -> View Material Transactions Resubmit errored transactions if any exists under Tools -> Submit All
25

Check if records are stuck in any of the following tables: ** At the Table Level:
1.
Pending Material Transactions: select * from mtl_material_transactions_temp where transaction_source_type_id = 5;
2.
Uncosted Material Transactions: select * from MTL_MATERIAL_TRANSACTIONS where costed_flag in ('N','E') where transaction_source_type_id = 5;
3.
Pending or Errored Move Transactions: select * from WIP_MOVE_TXN_INTERFACE where process_status in (1,3);
26

** At the Table Level:
4.
Pending or Errored Resource Transactions: select * from WIP_COST_TXN_INTERFACE where process_status in (1,3); Error Associated with Resource Transactions: select * from WIP_TXN_INTERFACE_ERRORS where TRANSACTION_ID in (select TRANSACTION_ID from WIP_COST_TXN_INTERFACE where process_status= 3)
5.
6.
Error Associated with Move Transactions: select * from WIP_TXN_INTERFACE_ERRORS where TRANSACTION_ID in (select TRANSACTION_ID from WIP_MOVE_TXN_INTERFACE where process_status= 3)
27

Note: To identify wip_entity_id which is system generated for discrete job name or number, you can run this query: select wip_entity_id from wip_entities where wip_entity_name like xyz; -- Value xyz represents the job name or number
28

7.
Unwanted Records in wip_dj_close_temp In some cases, the concurrent process is interrupted or terminated. This, in turn, causes records to get stranded in WIP_DJ_CLOSE_TEMP. If records in this table have status of 'Pending Close', no close routines have been called and committed.
a. b.
Create backup tables for from wip_dj_close_temp and wip_discrete_jobs. Datafix to set all the jobs with Pending Close or Failed Closed to Complete status:
q q
delete wip_dj_close_temp where 1=1; update wip_discrete_jobs set status_type = 4 where status_type in (14, 15) and date_closed is null; commit;
q c.
29
Resubmit the jobs for closure.

To obtain list of the jobs which are in Pending Close status: select wip_entity_name Job_Number, wip_entity_id Job_id from wip_entities where wip_entity_id in (select wip_entity_id from wip_discrete_jobs where status_type = 14); To obtain list of the jobs which are in Failed Close status select wip_entity_name Job_Number, wip_entity_id Job_id from wip_entities where wip_entity_id in (select wip_entity_id from wip_discrete_jobs where status_type = 15);
30

Resubmit jobs with a Pending Close or Failed Close status, where there are no pending transactions.
1. 2. 3. 4.
Responsibility: Work In Process Navigation: Discrete -> Close Discrete Jobs (Form) Query a discrete job with stats Pending Close Go to Tools -> Check Requests 1
You can use the Check Requests option from the Tools menu to manually resubmit jobs that have failed to close and have a Pending Close status. Resubmitting a job with Check Request sets the job's status back to its original status. Resubmitting jobs that have Pending Close statuses because the process has not yet concluded does not interrupt the close process.
31

If Job has Date Closed in a period which is closed then there is nothing to do further.
1. 2.
No data fix can be provided. The two options are to re-open the closed jobs which would require re-opening the closed inventory periods OR create new jobs for the remaining quantity of the jobs that were closed. If you wish to re-open the Inventory period to allow you re-open the jobs, refer to the following note: Re-Open a Closed Inventory Accounting Period (Doc ID 472631.1)
3.
32

If the Inventory period is still open then following steps can be done.
1. 2. 3.
Go to WIP > Discrete > Close Discrete Jobs (Form) Query the problematic closed job(s) Menu > Tools > Unclose
33

Error APP-WIP-25309 ** When the error APP-WIP-25309: There is an open Requisition or Purchase Order attached to this job/schedule occurs when closing a discrete job, there could be several possible reasons: PO/Requisition Incorrect Status The associated PO/Requisition must be in status Finally Closed to enable jobs to close successfully. 2. Undelivered PO Quantity POs must be delivered to the shopfloor. Users need to perform transactions of type 'Deliver' from Receiving Transactions form.
1.
34

Error APP-WIP-25309 (cont.)
3.
Code Issue If jobs cannot be closed even though the associated Purchase Order is closed, this could be a bug in the pertinent file (e.g. wicdcl.opp). Data Corruption Example: If cancel_flag = NULL in PO_REQUISITION_LINES_ALL. Purchase requisition status (cancel_flag) shows as NULL where this should be cancelled instead. Please log an SR to obtain a data fix.
4.
35
[4] Diagnostics
WIP Diagnostic wipjob11i (see Doc ID 1476250.1) ** This is SQL script that captures the job information from various tables. The output will be named after the wip_entity_id and will be called <wip_entity_id>.lst . The script takes job_name (wip_entity_name) and job_id (wip_entity_id) as inputs and generates a report. ** WIP Diagnostic wipjob11i shows important information to diagnose job closure data, such as: 1. Discrete Job Status 2. Pending or errorred transactions 3. Resource and material records
36
[4] Diagnostics (cont.)

The collector script wipjob11i is part of R12 and can be run via the Application ** Instructions for running the collector scripts are in the following documents: Doc ID 732341.1: Work Order Collector Script Doc ID 732343.1: Flow Collector script Doc ID 732342.1: Repetitive Collector script
37

Output of Diagnostics: Apps Check for Work in Process & Inventory ** Diagnostic: Apps Check Concurrent Request This can be run from either Order Management or Purchasing Responsibility
Use View / Requests / Submit a new request Then type Diag and hit to bring up the report parameter Up to 5 Applications can be entered into this request.
38

WIP Debug Log for Close Discrete Job concurrent program while closing jobs ** Steps to obtain WIP Debug log are:
1. 2. 3. 4. 5. 6. 7.
FND: Debug Log Filename = (Make sure this is null) FND: Debug Log Enabled = Yes FND: Debug Log Level = Statement FND: Debug Log Module = WIP% Remember: select max(log_sequence) from fnd_log_messages; Now do the test case Get the log by: select * from fnd_log_messages where log_sequence > &max_log_sequence; --get this from Step 5..
39

Generating Trace and Detailed Log
1. 2. 3. 4.
Enable profile option MRP: DEBUG to YES Enable the level 12 trace with waits and binds for the Job Close Concurrent program Provide the unsorted trace as well as the tkprof Also, provide the log file of the concurrent program
Note:
For guidelines on generating level 12 trace files see DOC ID 726039.1. If using this method, ensure that the concurrent program definition does not have the trace option checked. Also be sure to log out of the application before running tkprof to ensure that all the information is dumped to the trace file.
40
[5] Resources

Oracle Work in Process User's Guide, Release 12, Section Discrete Job Close Oracle Cost Management Users Guide, Release 12, Section Job Close Costing Information Center : Using Oracle Work In Process (Doc ID 1417745.2) Work In Process - Discrete / Lot Based Job Data Collection Script (Doc ID 1476250.1) Discrete Job or EAM Work Order remain stuck in Pending Close Status (Doc ID 158674.1) Closing WIP Jobs Causes (WICDCL - Close Discrete Jobs) Causes WIP_PO_NOT_DELIVERED Message (Doc ID 1352980.1)
41
[5] Resources (cont.)
Closing 'Failed Close' Discrete Jobs Using the Application (Not A Data Fix). Try this first (Doc ID 422245.1) WIP Close Discrete Job Program (WICDCL) Ends In "Error" Status (Doc ID 1394986.1) WIP Jobs Are Closed But Need To Perform Further Transactions Against Them (Doc ID 1302257.1) How to Close Outside Processing (OSP) Discrete Jobs (Doc ID 1279878.1) How To Get Level 12 Trace And FND Debug File For Concurrent Programs (Doc ID 726039.1)
42
Summary
What we covered today
[1] Technical Overview [2] Discrete Job Closure Flow [3] Troubleshooting [4] Diagnostics [5] Resources
43
To ask a question on the phone line, select *1 on your phone. To ask a question online, use the Q&A area at the top. Your question will be read aloud in the order received. Question can also be asked on the My Oracle Support Communities
Questions & Answers

q
44
Top Articles and Community Links

Work In Process Information Center [ID 1417725.2]. Work In Process & Flow Manufacturing Advisor Webcast Calendar And Archive [ID 1319827.1] All Advisor Webcasts [ID 1455888.1]. Continue the Discussion on the Work In Process & Flow Manufacturing My Oracle Support Community.
45
Learn More
Available References and Resources to Get Proactive
About Oracle Support Best Practices www.oracle.com/goto/proactivesupport Get Proactive in My Oracle Support https://support. oracle.com | Doc ID: 432.1 Get Proactive Blog https://blogs.oracle.com/getproactive/ Ask the Get Proactive Team [email protected]
46
My Oracle Support Community

Collaborate with a large network of your industry peers, support professionals, and Oracle experts to exchange information, ask questions & get answers. Visit the My Oracle Support Community now!! 1. 2. 3. Log into My Oracle Support. Select the Community tab. Start typing the community name in the Find a Community Quick Find field.
47
Advisor Webcast Program

Register for upcoming live advisor webcasts. Access past webcast recordings and presentation material. Continue the discussion on a specific webcast topic. Let us know what topics you would like presented in the communities or in the post webcast survey. Doc Id 740966.1
48
To ask a question on the phone line, select *1 on your phone. To ask a question online, use the Q&A area at the top. Your question will be read aloud in the order received. Question can also be asked on the My Oracle Support Communities
Questions & Answers

q
49
THANK YOU
50
51

Uploaded by

Copyright:

Available Formats

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Uploaded by

Copyright:

Available Formats

1

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Oracle Advisor Webcast Program

Current schedule Archived recordings Doc ID 740966.1

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Future Advisor Webcasts

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Safe Harbor Statement

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Oracle Advisor Webcast

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

[1] Technical Overview [2] Discrete Job Closure Flow

[3] Troubleshooting [4] Diagnostics

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

[1] Technical Overview

can also close individual discrete jobs.

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

[1] Technical Overview (cont.)

EAMCDCL module (Close EAM Work Orders)

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

[1] Technical Overview (cont.)

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

[1] Technical Overview (cont.)

Costing Job Close Transactions

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

[1] Technical Overview (cont.)

Close Discrete Jobs (FORM) Close Discrete Jobs (SRS)

No API/Open Interface Available

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

[1] Technical Overview (cont.)

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

[1] Technical Overview (cont.)

closed jobs and closed job values.

Pending Bill Load, and Pending Routing Load.

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

[2] Job Closure Flow

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

[2] Job Closure Flow (cont.)

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

[2] Job Closure Flow (cont.)

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

[2] Job Closure Flow (cont.)

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

[2] Job Closure Flow (cont.)

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

[2] Job Closure Flow (cont.)

[2] Job Closure Flow (cont.)

[2] Job Closure Flow (cont.)

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

[3] Troubleshooting (cont.)

** At the Application Level:

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

[3] Troubleshooting (cont.)

Pending Material Transactions: select * from mtl_material_transactions_temp where transaction_source_type_id = 5;

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

[3] Troubleshooting (cont.)

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

[3] Troubleshooting (cont.)

Copyright 2013, Oracle and/or its affiliates. All rights reserved.

[3] Troubleshooting (cont.)

Resubmit the jobs for closure.

Copyright 2013, Oracle and/or its affiliates. All rights reserved.