In this Document

APPLIES TO:

GOAL

1. Possible reasons for Resource Transactions to go to Pending with action plan to process them.

2. Common Errors while performing Resource Transactions with action plan to process them.

SOLUTION

Transactions in Pending Resource Transactions Form are generally of two kinds:
1. Unprocessed (process_status = 1 in WCTI)
2. Errored (process_status = 3 in WCTI)

Some of the common reasons why resource transactions remain unprocessed

1. Cost Manager is not active.

Solution:

Navigate to Inventory -- SetUp -- Transactions -- Interface Managers

See if the Cost Manager is Inactive. If yes, then launch the Cost Manager.

To launch the Cost Manager, Keep the cursor on 'Cost Manager' and Go to  Tools -- Launch Manager  and submit the Request. Once the Request Completes, it will invoke Cost Workers and process the records.

2. Any one transaction in error in either wip_cost_txn_interface or mtl_material_transactions table. (Only for Average Costing)

Solution:

This is a very common issue when using Average Costing. Any error during the cost processing of a material or resource transaction for a particular organization flags the transaction as erred and prevents the cost processing of other transactions in that particular organization.

You can use the below scripts to find out the errored transactions:

If any of the first two queries return rows, the subsequent transactions will not be picked up by the Actual Cost Worker. Only after the errored transaction is processed, the rest of the pending Resource and Material Transacitons will get processed.

3. For Flow Schedules or Work Orderless Complettions, completion transaction in MMT is already costed

Solution:

If there are records in WCTI for Flow Schedules or WOLC for which the corresponding Completion transactions in MMT are costed, then cost manager will not pick up these records. These records become orphaned records.

This issue is seen in 11.5.8 and 11.5.9.  This issue is fixed in file cmlctw.lpc in executable CMCCTW at $BOM_TOP/bin as 115.10.1159.4. If you are on 11.5.8 or 11.5.9, then following the readme text, apply Patch 3309813  to fix the root cause.

NOTE: This Patch Is NOT Applicable For Those Customers Who Are On Release 11.5.8 And Have Applied The Patch 3504721

For existing orphaned records, log an SR with Oracle Support to get confirmation to delete them after confirming that the corresponding record in MMT has been processed and do a manual adjustment in GL.

Reason why resource transactions go in Error is due to some failed validation.

The key steps to resolving erred transactions are:
1. Locate the transaction.
2. Find the error message to determine what is preventing the transaction from processing.
3. Resolve the error.
4. Resubmit the pending record.

Some of the common errors while performing Resource Transactions along with possible causes and action plan to process them

Error 1: No charges allowed for this job/schedule

Possible Causes: 

These will be transactions where the job is not in Released or Completed status. You can perform transactions only against jobs which have status of Released or Complete. 
This issue mainly occurs for OSP jobs when a OSP item is received against a Closed Job with a charge type of PO Move or PO Receipt for that corresponding OSP Resource. You can verify it by checking the source_code in WIP_COST_TXN_INTERFACE. It will show as 'RCV' 
Another cause of this is data being inserted into WIP_COST_TXN_INTERFACE for a job that is not in Released or Complete status and then trying to process it. 

Solution: 

Check the status of the corresponding job. Change the status of the job to either Released or Complete. If the job is closed, then unclose the job. Then resubmit the transaction. However, if the period in which the job is closed is also closed, then you cannot unclose the job and hence cannot process these transactions. 
In this case, you need to delete these transactions from the pending resource transactions form. 
Resubmit the transactions through forms only. 
To prevent this issue, please make sure that no receipt is done against a job that is closed.

Error 2: Transaction date precedes release date for the job/schedule

Possible Causes:

You would have entered a transaction date that precedes the release date for your job or schedule. The transaction date for any WIP transaction must always be greater than the Released date of the work order.

Solution:

Change the transaction date of that errored transaction in the pending resource transactions form and then resubmit. Resubmit the transactions through forms only.

Error 3: No balance exists for the appropriate period for the job/schedule

Possible Causes:

This error occurs if here is no record in WIP_PERIOD_BALANCES for the corresponding repetitive schedule or job in that accounting period for which transactions are errored.

Solution:

Follow the Note 1080033.6 to create the missing WPB records. Run the script cm276916.sql out of Note 1080033.6 if this error is for discrete jobs. Otherwise run the script cm325424.sql if the errors are for repetitive schedules. Then resubmit the transactions through forms.

REFERENCES