Professional Documents
Culture Documents
Closing Work Orders White Paper PDF
Closing Work Orders White Paper PDF
Work Orders
Closing a work order changes the status to closed and means that no more
transactions are allowed to be posted to the work order.
Final costs and variances are calculated for the work order and posted to the
relevant GL accounts.
It should be noted that there is NO API for closing work orders. I will now look at
the above options in more detail :
This calls the EAMCDCL concurrent program. This is the same as the WIP program
but includes some prior validation relevant to EAM work orders.
2
3
a. Close Rebuild Work Orders Form :
Used for EAM rebuild work orders. The screenshot below shows this form :
Run from the WIP Responsibility and calls the WICDCL concurrent program.
4
c. Close Discrete Job Concurrent Request (WIP - WICDCL concurrent
program)
A key point to note is that the Actual Close Date is one of the parameters. This is
the date that will be specified as the date the job was closed. There must be NO
transaction dated on the job after this date or the close will fail.
5
d. Close EAM Job Concurrent Request (calls EAMCDCL concurrent program)
Navigation : (from EAM responsibility) View > Requests > Submit New Request >
Close EAM Work Orders
A key point to note is that the Actual Close Date is one of the parameters. This is
the date that will be specified as the date the job was closed. There must be NO
transaction dated on the job after this date or the close will fail.
6
2. WHAT HAPPENS WHEN A WORK ORDER IS CLOSED?
• The WO status is set to closed and NO more transactions can be posted to the
WO :
• Closing a WO calculates final costs and variances and ensures any open
requirements are not considered as demand.
• The WO close date specifies the accounting period that will be used to
recognise the variances.
• The close process writes off the balances remaining in the WIP elemental
valuation accounts to the elemental variance accounts that you defined by wip
accounting class, leaving a zero balance remaining in the closed job.
• If there is a positive balance in the job at the end of the close, here are the
accounting entries for a job close:
7
VARIANCES IN WIP:
When a WO is closed, a job close variance may be posted for the job if appropriate.
Work In Process Value Summary will have a variance if there is material that has
not yet been issued to the job prior to close. To resolve this, re-open the job and
issue the material. Material overhead associated to the material may also show a
variance until all materials are properly applied to the job.
For Resources and Overhead, the costs need to be associated for the item to a
Resource or Department which is part of the routing for item ...in other words, the
overhead cost needs to be part of the "Rolled Up Costs" in the item cost screen.
8
VARIANCES IN EAM:
The proper set up is to load the appropriate maintenance expense account into
both the valuation and variance account fields for the WIP Accounting Class.
This will result in maintenance work order expenses booking to the expense
account when incurred.
So, when setting up WIP Accounting Classes, use the same maintenance expense
account code in both the valuation and variance columns.
This will cause maintenance expenses to book to the proper GL account and
period.
In fact, EAM Work Orders copy the behavior of WIP Non-standard Expense jobs.
You can close such jobs and recognize variances for these jobs at any time. In
addition, the period close process automatically recognizes variances on all
charges incurred during the period. Therefore, open jobs have zero WIP
accounting balances at the start of a new period.
If there is a positive balance in the job at the end of the period, then here are the
accounting entries for non-standard expense jobs at period close:
In EAM, the balance is always equal with the actual cost (similar to cost incurred
from WIP perspective) as there is no cost to be relieved so the cost relieved is
always 0. This means that the entire cost of WO is a variance. This is why EAM
recommends the Valuation Accounts to be the same with Variance Accounts.
9
3. TROUBLESHOOTING THE CLOSING OF WORK ORDERS :
There are several reasons WHY work orders do not close. They are :
If the work order does not close, it will show one of the following statuses :
- PENDING CLOSE
- FAILED CLOSE
Pending Close :
Failed Close :
• 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.
If resource transactions have any errors , these need to be corrected and then
the resource transactions have to be resubmitted.
The errors can be seen under the errors tab from the View Pending
Transactions form.
Here are the table level queries to check which transactions are pending or in
error:
11
The query to look at the actual error is shown below:
Please note that there are many different types of error that need to be
corrected and the correction of these errors is not covered in this document.
Please refer to the note below:
The following causes can result in pending resource transactions (as stated
earlier, the solutions for resolving these issues is not covered in this
document and you need to follow Doc 1672312.1):
12
3.2 PENDING MOVE TRANSACTIONS
You can check any errors in the errors section in the form above. These
errors need to be corrected and then you can resubmit the transactions.
The following query can be used to check for pending or errored move
transactions:
The following query can be used to view the errors for these transactions:
13
b) There are lot-controlled components, but lot selection
method is manual.
Any errors have to be corrected and then you can resubmit the errored
transactions.
If the resubmission does not work, then an SR will be required with INV
Team
14
3.4 UNCOSTED/ERRORED MATERIAL TRANSACTIONS
It should be noted that there is usually a very simple reason for the
transactions to be uncosted – it is simply that the Cost Manager has not
yet run. The Cost Manager is scheduled to run however many times a day
a client requires. So , usually, these type of transactions will be processed
when the Cost Manager next runs.
UPDATE MTL_MATERIAL_TRANSACTIONS
SET COSTED_FLAG = 'N',
TRANSACTION_GROUP_ID = null,
ERROR_CODE = null,
ERROR_EXPLANATION = null
WHERE COSTED_FLAG = 'E';
However, in most cases, the underlying error has to be corrected and then
the above script will work. If the underlying error is not corrected, the
transaction will error out again.
15
3.5 OPEN PO OR PR AGAINST THE OSP WO
b. Reduce the job quantity of the job to equal the completed quantity.
16
3.7 UNWANTED RECORDS IN WIP_DJ_CLOSE_TEMP :
c. ERROR: APP-WIP-25190: You are not allowed to close jobs with these
statuses
d. Log of concurrent request WICDCL - Close Discrete Jobs may show the
following message:
e. Status has not changed. Another situation is when the WOs get closed
successfully but the status hasn't changed.
17
The solution for this type of issue is as follows:
update wip_discrete_jobs
set status_type = 4
where status_type in (14, 15) and date_closed is null;
commit;
b. Pending Close
You cannot unclose a job that does not have a status of Closed.
You also cannot unclose a job that was closed in a now closed
accounting period.
18
If you do not want Unclose to display in the menu, set the
parameter to No. The default for this option is Yes.
19
ClosinG Work Orders
July 2015-05-14
Author: Zar Ahmed
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.
Worldwide Inquiries:
Phone: +1.650.506.7000
Fax: +1.650.506.7200
www.oracle.com
20