Thanks to the International Oracle User Council, we have an implementer’s view of the Fusion Roadmap. The roadmap is interactive, and each aspect of the roadmap leads to specific content for that area.
02 January 2013
25 December 2012
To Delete Work Orders in Oracle EAM
The Oracle EAM is based on WIP and Inventory modules, So Period Closing is used on
EAM organizations.
EAM Work Orders can be purged by using "Purge Discrete Jobs" feature. But this program will purge only WOs which are closed in already closed periods. (there are some validations which are not allowing purging of active work orders or WOs which are not in closed periods) Also you will have to run Inventory Transactions Purge program before being able to run WIP Purge.
There is no special program to purge only EAM Work Orders nor EAM Work Requests. Also it is not recommended to delete them from header tables (like wip_entities, wip_discrete_jobs or wip_eam_work_requests) as the records are related with records from detail or transaction tables by foreign keys.
In EAM, closing a period or closing an EAM Work Order act in same way: the costs incurred until that time are relieved by variance accounts. In either way, the costs can be pushed to GL. After that, as the WOs and related WRs are not necessary in the system, they could be deleted but at that time, all the material transactions and the resource transactions (and other transactions like capitalization or billing) will remain orphan and they could result in mismatch in reports and errors on user interfaces.
So purging this info from the system is not an easy task and also not recommended by Oracle
(version 11.5.10)
EAM Work Orders can be purged by using "Purge Discrete Jobs" feature. But this program will purge only WOs which are closed in already closed periods. (there are some validations which are not allowing purging of active work orders or WOs which are not in closed periods) Also you will have to run Inventory Transactions Purge program before being able to run WIP Purge.
There is no special program to purge only EAM Work Orders nor EAM Work Requests. Also it is not recommended to delete them from header tables (like wip_entities, wip_discrete_jobs or wip_eam_work_requests) as the records are related with records from detail or transaction tables by foreign keys.
In EAM, closing a period or closing an EAM Work Order act in same way: the costs incurred until that time are relieved by variance accounts. In either way, the costs can be pushed to GL. After that, as the WOs and related WRs are not necessary in the system, they could be deleted but at that time, all the material transactions and the resource transactions (and other transactions like capitalization or billing) will remain orphan and they could result in mismatch in reports and errors on user interfaces.
So purging this info from the system is not an easy task and also not recommended by Oracle
(version 11.5.10)
'Period Close Variance' Entries From Oracle EAM to GL
The term 'Variance' in both 'Job/Period Close Variance' and 'Work
Order Cost details screen - Variance' is causing the confusion. While the former
is used in an accounting sense the latter is merely a term used in the cost view
of the work order.
The Job Close variance and the Period close variance cause the maintenance expenses incurred on the work order to be passed on from the WO Valuation account to the Variance account. If these two accounts were set up to be the same in the WIP Accounting class, (which is the case that you have and also the recommended modelling specially for Average cost type), then the above postings are merely symbolic in the sense that the same account is debited and credited. The debit to the WO Valuation account during the actual EAM material or labor transaction would be the point at which this maintenance expense is first recognized in the P&L. Subsequent variance posting will have no impact.
The Variance observed in the Work Order Cost details page is just a cost view of the difference between the Estimated Cost and Actual Cost of the work orders. This gives an idea to the maintenance planner and execution team as to the extent of costs incurred in actual compared to the estimated cost.
EAM WO Cost Estimation is not impacting the accounting once the period is closed. (In fact, once the period is closed, nothing from EAM can do adjustments into GL)
If you want to schedule the Work Order Cost Estimate Processor then you will have to schedule the Estimation based on your needs. Are the users checking the WO costs daily? then you should schedule daily.
But, there is no impact on the accounting if the
The Job Close variance and the Period close variance cause the maintenance expenses incurred on the work order to be passed on from the WO Valuation account to the Variance account. If these two accounts were set up to be the same in the WIP Accounting class, (which is the case that you have and also the recommended modelling specially for Average cost type), then the above postings are merely symbolic in the sense that the same account is debited and credited. The debit to the WO Valuation account during the actual EAM material or labor transaction would be the point at which this maintenance expense is first recognized in the P&L. Subsequent variance posting will have no impact.
The Variance observed in the Work Order Cost details page is just a cost view of the difference between the Estimated Cost and Actual Cost of the work orders. This gives an idea to the maintenance planner and execution team as to the extent of costs incurred in actual compared to the estimated cost.
EAM WO Cost Estimation is not impacting the accounting once the period is closed. (In fact, once the period is closed, nothing from EAM can do adjustments into GL)
If you want to schedule the Work Order Cost Estimate Processor then you will have to schedule the Estimation based on your needs. Are the users checking the WO costs daily? then you should schedule daily.
But, there is no impact on the accounting if the
Reconcile the Oracle EAM and Payroll to avoid duplicate entries in GL
Oracle EAM is not designed to automatically reconcile with payroll entries. Customer
needs to setup the accounts used in resource absorption account (resource
definition form) and WIP valuation account for resource (WIP Accounting class)
appropriately to achieve the desired results.
A recommendation that we provide to the customer base independent of the topic being discussed here is that the WIP valuation account and WIP variance account in the WIP Accounting class be set the same. In the context of these possibilities/recommendation, please see the below 3 cases
Case-1 :
If the resource absorption accounts are set the same WIP valuation accounts for resource cost element, then debit and credit will be to the same account and there is no net value posted in GL due to resource charging in eAM. However the cost of resources required /actually used in a eAM work order will be displayed as cost views in Estimated cost view and Actual Cost view. In this approach, you are accounting all payroll related expense through the Payroll module only and eAM just provides a view of the resource costs expended on the work order.
Case-2 :
If the resource absorption account is set the same as the payroll debit side account, then this has the net effect of consuming the payroll expense when maintenance expense is incurred due to utilization of the maintenance resources. So your financial statements would then reflect payroll expenses to the extent of non-maintenance related resources(people) and the maintenance expenses bucket would show all maintenance costs – both items used and resources used.
Case-3:
A third practice that customers employ is to have 3 separate accounts involved in the resource transaction process:
A recommendation that we provide to the customer base independent of the topic being discussed here is that the WIP valuation account and WIP variance account in the WIP Accounting class be set the same. In the context of these possibilities/recommendation, please see the below 3 cases
Case-1 :
If the resource absorption accounts are set the same WIP valuation accounts for resource cost element, then debit and credit will be to the same account and there is no net value posted in GL due to resource charging in eAM. However the cost of resources required /actually used in a eAM work order will be displayed as cost views in Estimated cost view and Actual Cost view. In this approach, you are accounting all payroll related expense through the Payroll module only and eAM just provides a view of the resource costs expended on the work order.
Case-2 :
If the resource absorption account is set the same as the payroll debit side account, then this has the net effect of consuming the payroll expense when maintenance expense is incurred due to utilization of the maintenance resources. So your financial statements would then reflect payroll expenses to the extent of non-maintenance related resources(people) and the maintenance expenses bucket would show all maintenance costs – both items used and resources used.
Case-3:
A third practice that customers employ is to have 3 separate accounts involved in the resource transaction process:
No iPhone/Android Application For Oracle eAM, But there is a " Wireless Maintenance Workbench "
There is no "Oracle EAM eBS app for iPhone/Android" software available till version R12.1.3, Oracle has not provided such software to
customers.
However, there is application called "Oracle Wireless Maintenance". This responsibility is a html eBS EAM responsibility and it can be used from mobile devices in on-line mode. The only requirement is that the mobile device to have internet browsing capability This is not requiring any software to be installed on client (mobile) device. However, if you have a VPN secured server, the mobile device must have this capacity to connect via VPN.
Note: Oracle features and applications may have been modified and empowered by third party software providers BUT this modified software is not supported by Oracle.
SETUP required for Wireless Maintenance Workbench
A. Sysadmin Setup:
1. Go to System Administrator >Security>Responsibility>Define, Set the "Wireless Maintenance User Workbench" as a Self Service Web Application instead of mobile application and Set Data group Application to Enterprise Asset Management instead of Manufacturing.
2. Go to System Administrator > Application > Function and query for Function = EAM_WL_MUWB_HOME (User Function Name should be defaulted to MUWB Home Page) and Go to properties tab and make sure that type = "SSWA jsp function"
3. Go to System Administrator > Security > User > Define, Query for your user and make sure there is a valid employee is populated in the Person field.
B. EAM setup:
6. EAM Organization must be assigned to the Responsibility 'Wireless Maintenance User Workbench' through the Organization Access form in Inventory
7. The Login User Employee should have some work order operation assignments (the normal MUWB data):
a. EAM => Setup => Routing =>
However, there is application called "Oracle Wireless Maintenance". This responsibility is a html eBS EAM responsibility and it can be used from mobile devices in on-line mode. The only requirement is that the mobile device to have internet browsing capability This is not requiring any software to be installed on client (mobile) device. However, if you have a VPN secured server, the mobile device must have this capacity to connect via VPN.
Note: Oracle features and applications may have been modified and empowered by third party software providers BUT this modified software is not supported by Oracle.
SETUP required for Wireless Maintenance Workbench
A. Sysadmin Setup:
1. Go to System Administrator >Security>Responsibility>Define, Set the "Wireless Maintenance User Workbench" as a Self Service Web Application instead of mobile application and Set Data group Application to Enterprise Asset Management instead of Manufacturing.
2. Go to System Administrator > Application > Function and query for Function = EAM_WL_MUWB_HOME (User Function Name should be defaulted to MUWB Home Page) and Go to properties tab and make sure that type = "SSWA jsp function"
3. Go to System Administrator > Security > User > Define, Query for your user and make sure there is a valid employee is populated in the Person field.
B. EAM setup:
6. EAM Organization must be assigned to the Responsibility 'Wireless Maintenance User Workbench' through the Organization Access form in Inventory
7. The Login User Employee should have some work order operation assignments (the normal MUWB data):
a. EAM => Setup => Routing =>
Subscribe to:
Posts (Atom)