Transfer Transactions from Production to Costing
Use the Transfer Transactions from Maintenance to Costing scheduled process to transfer the maintenance execution transaction details and maintenance work order status updates to costing for accurate costing of the maintenance work orders.
The program reads the records in the resource transaction table.
As part of this transfer, the following are interfaced from Oracle Maintenance to costing:
- Resource transactions for the costed resources
- All the operation transactions
- Maintenance work order status updates
You can access this report from these locations:
| Location | Description |
|---|---|
|
Maintenance Management work area task panel |
The Transfer Transactions from Maintenance to Costing can be run from the task menu. |
|
Scheduled Processes work area |
You can schedule the Transfer Transactions from Maintenance process or run it at any time as an ad hoc job. |
When to Use
It is only recommended to use this process monthly after completing work orders to a closed status, preventing further updates. This process will then update the costing of the maintenance work orders.
Privileges Required
- Transfer Transactions from Maintenance to Costing ( MNT_TRANSFER_TRANSACTIONS_FROM_MAINTENANCE_TO_COSTING_PRIV)
Specifications
Use these specifications when you run the scheduled process.
| Specification | Description |
|---|---|
| Job Type | Run at any time as an ad hoc job. |
| Frequency | Typically, once a month during the month end close process. |
| Time of Day | Any time. |
| Duration | It could take a while depending on the volume of data being analyzed. |
| Compatibility | There should be only one instance of the job running at any one time. |
Parameters
You must define at least a range of work order numbers or dates to process the report.
| Parameter | Optional or Required | Description | Parameter Value | Special Combinations Required |
|---|---|---|---|---|
| Organization | Required | The organization for which work order costs will be transferred. | The Organization is selected using an LOV. | None |
| Source System | Required | The source system of the production transactions. | The Source System is selected using an LOV. | None |
Troubleshooting Information
- Once submitted, you can view the status of the process in the Scheduled Processes work area. A successfully completed process, as well as any child processes, will end in Succeeded status.
- If issues are encountered, the process or any of its subprocesses may be Warning or Error. The specific validation errors and warning messages that prevented the process from completing successfully are displayed in the error log(s).
- Any interactive warning validations are NOT performed.
- When the process is submitted, you can Resubmit, Put on Hold, Cancel Process, Release Process in the Scheduled Processes work area.