Oracle Enterprise

Asset Management
Troubleshooting
EAM Transactions
An Oracle White Paper
March 2014

Table of Contents
1. OVERVIEW............................................................................................................................................1
2. WIP PERIOD BALANCES............................................................................................................................2
3. TABLES AFFECTED BY STUCK TRANSACTIONS...............................................................................................3
4. RESOURCE TRANSACTION PROCESSING......................................................................................................5
5. RESOURCE TRANSACTION ERRORS............................................................................................................6
6. MATERIAL TRANSACTION ERRORS......................................................................................................15

1. OVERVIEW
The objectives of this white paper are to provide an overview
of how to resolve pending or errored transaction issues in
Enterprise Asset Management. This paper will cover the
following topics :

Consider the type of transactions affected

Specify the tables involved
Look at resource transaction errors and consider the
cause, validate if there is a root cause solution and
explain how to fix these errors.
Look at material transaction errors and consider the
cause, validate if there is a root cause solution and
explain how to fix these errors.

Most of the eBusiness applications usually require the posting of

transactions to a specific entity in order to record the activity
against that entity.
For example : A work order is created for an asset. Activity
against the work order is recorded as :
- Resource transactions to record work done on a
Work Order (WO)
- Material Issue Transactions for material issued.
- Material return transactions to return materials to
Inventory.
- Completion Transactions to complete the work order.
Sometimes, these transactions fail. We will investigate the causes
and explain what to do.
Remember that a WO cannot be closed if its transactions are not
processed.
Here is a brief explanation of the main types of transaction
affected :

Resource Transaction : Is a transaction where you

automatically or manually charge labor for a defined resource
such as a person or machines to a discrete job or repetitive
schedule and it has not processed. The transaction could be
waiting to process or processing during validation has errored.

Material Transactions : This is where material is issued to a WO

manually or via move orders. Remember backflush is NOT
available in EAM. This is because EAM does not cater for
assembly pull or operation pull supply types.

Return Transaction : A manual return of component from the

WO to inventory. You may have issued too much material, for
example.

Completion Transactions : The completion of the WO. Any

required meter readings and quality results can be entered at
this stage.

Asset Move Transactions : when an asset is moved from one

organization to another.
DISCLAIMER: This document contains datafixes for
certain types of errors. These datafixes have been tried
and tested. However, datafixes should always be used
very carefully in a Test environment and it is preferable
that you seek Orac;e Support Guidance before using
these. If the datafixes cause any issues, Oracle cannot
be held liable for them.

2. WIP PERIOD BALANCES :

An important table that needs to be considered when dealing
with stuck transactions in EAM (and WIP) is the
WIP_PERIOD_BALANCES table.
A very common cause of errored/pending transactions occurs
if there are missing records in WIP_PERIOD_BALANCES table.
The creation and deletion of entries in the
WIP_PERIOD_BALANCES is governed by the following rules:
A record is deleted from WIP_PERIOD_BALANCES when :

The job status is changed to unreleased.

The period is closed and the job close date is <=

accounting period start date.

A record is inserted into WIP_PERIOD_BALANCES when

The job status is changed to released.

The period is opened and the job status (status_type

column) is one of the following:
- Released - charges allowed ( status_type = 3)
- Complete - charges allowed (4)
- Complete - no charges allowed (5)
2

- Hold - no charges allowed (6)

- Canceled - no charge allowed (7)
- Pending close (14)
- Failed close (15)

3. TABLES AFFECTED BY THE STUCK TRANSACTIONS :

Resource Transactions :

Pending transactions : These get stuck in the table

WIP_COST_TXN_INTERFACE and have
PROCESS_STATUS = 1

Running transactions: These get stuck in the table

WIP_COST_TXN_INTERFACE with PROCESS_STATUS = 2

Errored transactions get stuck in

WIP_COST_TXN_INTERFACE with PROCESS_STATUS = 3
(errors are held in WIP_TXN_INTERFACE_ERROR table.

An important column in WIP_COST_TXN_INTERFACE is

PROCESS_PHASE. This has 2 values :

1 = Resource Validation
Processing

and 2 = Resource

If a transaction is processed successfully, it is removed

from WIP_COST_TXN_INTERFACE and posted to
WIP_TRANSACTIONS table.

WIP_DISCRETE_JOBS contains all details of the work

order except Failure_Code_Required flag

WIP_ENTITIES - Contains Job type (EAM, DISCRETE,

FLOW etc), Job/WO , Open/Close, Job/WO Name and
Description.
Entity_Type is the Work In Process entity type code and
the following is the code/meaning:

1
2
3
4
5
6
7
8

Discrete job
Repetitive assembly
Closed discrete job
Flow schedule
Lot based job
Maintenance job
Closed maintenance job
Closed lot based job

One common use of the WIP_ENTITIES table is to find the

wip_entity_id if only the job name is known. The following
query can be used:
Select wip_entity_id from wip_entities where
wip_entity_name = job name
The wip_entity_id is a commonly required value for
running certain diagnostic reports.
When you are analyzing jobs that have stuck or errored
transactions, it is recommended that you generate the
wipjob11i for the work order. This can be run for EAM
jobs also. The note to follow for producing this diagnostic
report is Note 316142.1

EAM_WORK_ORDER_DETAILS Contains
Failure_Code_Required flag, which determines whether
failure entry is required for the work order or not. Also
contains material shortage data.

Material and Completion Transactions :

Unprocessed material transactions get stuck in table

MTL_MATERIAL_TRANSACTIONS_TEMP.
Check for transaction_type_id=5, (wip transactions)
Also check for process_flag =E (error)

When transactions are processed successfully, they are

transferred to MTL_MATERIAL_TRANSACTIONS table.
4

There must be NO Uncosted Transactions for the job in

MTL_MATERIAL_TRANSACTIONS (WHERE COSTED_FLAG
IN (N, E))

BASIC QUERIES FROM THESE TABLES:

Before we look at the types of error, here are some basic
queries to search for errors:

select * from mtl_material_transactions where

costed_flag = 'E';
(material transactions)

select * from mtl_material_transactions_temp mmtt

where
transaction_source_type_id = 5 ;
(unprocessed material txns)

select * from wip_cost_txn_interface where

process_status = 1;
(pending resource transactions)

select * from wip_cost_txn_interface where

process_status = 3;
(resource transactions with
errors)

select * from wip_txn_interface_errors where

transaction_id in (select transaction_id from
wip_cost_txn_interface where process_status = 3); (the
actual errors are shown for the resource transactions.
The errors themselves are not stored in
wip_cost_txn_interface )

4. RESOURCE TRANSACTION PROCESSING

The Cost Manager (CMCTCM) processes Resource

Transactions.

This launches the Resource Cost Worker (CMCCTW) for

standard costing organizations.

It launches the Actual Cost Worker (CMCACW) for

average costing organizations.

It launches the Overhead Cost Worker (CMCOCW) to

process the transactions in the
WIP_COST_TXN_INTERFACE table.

If the error message in the Pending Resource

Transaction window is not clear, review the log file of
the Resource Cost Worker or Overhead Cost Worker
this may provide more information that could help in
resolving the error. Changing the following profile
options will create more detailed debug information in
the log file:

MRP:Debug Mode

set to Yes

CST:Cost update debug Level set to Full

5. RESOURCE TRANSACTION ERRORS
Error 1: Resource Transaction stuck in Pending status
(Process_status = 1). There is no error.
CAUSE :
Cost Manager is not active.
ROOT CAUSE SOLUTION : User Error.
FIX : Activate the Cost Manager.
Inventory > Setup > Transactions > Interface Managers
Note : Sometimes, there may not be a specific cause for the
pending transaction and they simply need to be resubmitted.
This is quite rare however.
Sometimes a script may be necessary to process the pending
transaction. The steps are:

Stop the Cost Manager.

6

Run script below to ensure that record is picked up by

Cost Manager (group and transaction id are nullified) :
Update WIP_COST_TXN_INTERFACE
Set group_id = null,
Process_status = 1,
transaction_id = null
Where wip_entity_name = <Job Name> ;

Now restart the Cost Manager and check transactions

are processed.

Error 2 : Error : No charges allowed for this

job/schedule
Resource Transaction stuck in Error status (Process_status =
3) with above error.
CAUSE :
The related job is not in a valid status. It is likely closed or in
status Complete no charges.
ROOT CAUSE SOLUTION : User Error.
FIX : If the job is closed, re-open it and set as released. If the
job is in status complete- no charges , then set to released
status or complete allow charges.
Note : You cannot re-open a closed job if the period in which it
was closed is also closed.

Error 3 : Transaction date precedes release date for

the job/schedule
Resource Transaction stuck in Error status (Process_status =
3) with above error.
CAUSE:
The transaction date precedes the released date for the job.
7

ROOT CAUSE SOLUTION : User Error.

FIX :

Go to Pending Resources Form.

Correct the transaction date to be after as same as job

release date.

Resubmit the errored resource transaction.

This error can also occur if importing timecards for

future dates. Make sure that the period is open and the
transaction dates relevant.

Error 4 : No balance exists for the appropriate period

for the job/schedule.
Other versions of same error :
- Record not found in WIP_PERIOD_BALANCE
Cause: There is no record in WIP_PERIOD_BALANCES
for the repetitive schedule or job.
- The wip entity is either not defined or does not have
a period balancing entry
CAUSE:
No record exists in the transactions period in
WIP_PERIOD_BALANCES table.
ROOT CAUSE SOLUTION :
-

Apply patch 12410248 in 11i.

Apply 8344919:R12.INV.A in 12.0.x

Apply patch 13605602:R12.INV.B in 12.1.3

Ensure latest versions of files below :

$inv/patch/115/sql/INVMOCLB.pls
$inv/forms/US/INVTTGPM.fmb ,
8

$bom/patch/115/sql/CSTPAPEB.pls
$inv/patch/115/odf/invacct.odf 120.4.12010000.2
Also check that your files are higher then those provided by
the patches below if the above patches have not resolved
the issue :

11i : Patch:5378577 ; Patch:5573584

12.0.X: Patch.8344919:R12.INV.A , Patch:
7516448:R12.EAM.A , Patch:7582553:R12.EAM.A
Patch:8647138:R12.EAM.A

FIX : APPLY DATAFIX :

1.

First Identify the affected records using the SQL below

SET LINES 180

SET PAGES 65
spool wip_missing_wpb.lst
SELECT
WDJ.WIP_ENTITY_ID,
WE.WIP_ENTITY_NAME,
decode(we.entity_type,
1, 'Discrete Job',
2, 'Repetitive Schedule',
3, 'Closed Discrete Job',
4, 'Flow/Work Order-less',
5, 'Lot Based Job',
6, 'EAM Job',
we.entity_type) entity_type ,
WDJ.ORGANIZATION_ID,
OAP.acct_period_id,
WDJ.DATE_RELEASED,
WAC.CLASS_TYPE
FROM WIP_ACCOUNTING_CLASSES WAC,
ORG_ACCT_PERIODS OAP,
WIP_DISCRETE_JOBS WDJ,
9

WIP_ENTITIES WE
WHERE WDJ.STATUS_TYPE IN (3, 4, 5, 6, 7, 14, 15)
AND WAC.CLASS_CODE = WDJ.CLASS_CODE
AND WDJ.ORGANIZATION_ID = WAC.ORGANIZATION_ID
AND OAP.ORGANIZATION_ID = WDJ.ORGANIZATION_ID
AND WDJ.WIP_ENTITY_ID = WE.WIP_ENTITY_ID
AND WDJ.ORGANIZATION_ID = WE.ORGANIZATION_ID
AND OAP.OPEN_FLAG = 'Y'
AND OAP.PERIOD_CLOSE_DATE IS NULL
AND OAP.SCHEDULE_CLOSE_DATE >=
TRUNC(NVL(WDJ.DATE_RELEASED, WDJ.CREATION_DATE) )
AND WAC.CLASS_TYPE != 2
AND NOT EXISTS
(
SELECT 'X' FROM WIP_PERIOD_BALANCES WPB
WHERE WPB.REPETITIVE_SCHEDULE_ID IS NULL
AND WPB.WIP_ENTITY_ID = WDJ.WIP_ENTITY_ID
AND WPB.ORGANIZATION_ID = WDJ.ORGANIZATION_ID
AND WPB.ACCT_PERIOD_ID = OAP.ACCT_PERIOD_ID);
spool off
2. Note: Check the output and see also if DATE_RELEASED is
populated . If not, script wip_wdj_date_released_upd.sql will
need to be in the next step 3. If the DATE_RELEASED for all the
jobs in the output is populated, then go to step 4.
3. Do this only if date_released of the affected jobs is null.
Run wip_wdj_date_released_upd.sql shown below to update
the date_released column in WDJ.
update wip_discrete_jobs wdj
set wdj.date_released = (select min(wpb.creation_date)
from wip_period_balances wpb
where wpb.wip_entity_id = &wip_entity_id)
where wdj.wip_entity_id = &wip_entity_id
and wdj.date_released is null

10

4. Create backup of WIP_PERIOD_BALANCES table

5. Stop Cost Manager
System Administrator Responsibility>Requests>query for
specific 'Cost Manager' and increase the Number of Days to
view from 7 to 1000>Find>Cancel request
6. Apply the script below to insert missing records in
WIP_PERIOD_BALANCES table :

INSERT INTO WIP_PERIOD_BALANCES

(ACCT_PERIOD_ID, WIP_ENTITY_ID,
REPETITIVE_SCHEDULE_ID, LAST_UPDATE_DATE,
LAST_UPDATED_BY, CREATION_DATE,
CREATED_BY, LAST_UPDATE_LOGIN,
ORGANIZATION_ID, CLASS_TYPE,
TL_RESOURCE_IN, TL_OVERHEAD_IN,
TL_OUTSIDE_PROCESSING_IN, PL_MATERIAL_IN,
PL_MATERIAL_OVERHEAD_IN, PL_RESOURCE_IN,
PL_OVERHEAD_IN, PL_OUTSIDE_PROCESSING_IN,
TL_MATERIAL_OUT, TL_MATERIAL_OVERHEAD_OUT,
TL_RESOURCE_OUT,
TL_OVERHEAD_OUT, TL_OUTSIDE_PROCESSING_OUT,
PL_MATERIAL_OUT, PL_MATERIAL_OVERHEAD_OUT,
PL_RESOURCE_OUT, PL_OVERHEAD_OUT,
PL_OUTSIDE_PROCESSING_OUT,
PL_MATERIAL_VAR, PL_MATERIAL_OVERHEAD_VAR,
PL_RESOURCE_VAR, PL_OUTSIDE_PROCESSING_VAR,
PL_OVERHEAD_VAR, TL_MATERIAL_VAR,
TL_MATERIAL_OVERHEAD_VAR,
TL_RESOURCE_VAR, TL_OUTSIDE_PROCESSING_VAR,
TL_OVERHEAD_VAR)
SELECT
OAP.acct_period_id, WDJ.WIP_ENTITY_ID,
NULL, SYSDATE,
0, SYSDATE,
0, 0,
WDJ.ORGANIZATION_ID, WAC.CLASS_TYPE,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
11

FROM WIP_ACCOUNTING_CLASSES WAC,

ORG_ACCT_PERIODS OAP,
WIP_DISCRETE_JOBS WDJ
WHERE WDJ.STATUS_TYPE IN (3, 4, 5, 6, 7, 14, 15)
AND WAC.CLASS_CODE = WDJ.CLASS_CODE
AND WDJ.ORGANIZATION_ID = WAC.ORGANIZATION_ID
AND OAP.ORGANIZATION_ID = WDJ.ORGANIZATION_ID
AND OAP.OPEN_FLAG = 'Y'
AND OAP.PERIOD_CLOSE_DATE IS NULL
AND OAP.SCHEDULE_CLOSE_DATE >=
TRUNC(NVL(WDJ.DATE_RELEASED, WDJ.CREATION_DATE))
AND WAC.CLASS_TYPE != 2
AND NOT EXISTS
(
SELECT 'X' FROM WIP_PERIOD_BALANCES WPB
WHERE WPB.REPETITIVE_SCHEDULE_ID IS NULL
AND WPB.WIP_ENTITY_ID = WDJ.WIP_ENTITY_ID
AND WPB.ORGANIZATION_ID = WDJ.ORGANIZATION_ID
AND WPB.ACCT_PERIOD_ID = OAP.ACCT_PERIOD_ID);
7. Run again select from step 1 which should return no records
now. If so, then issue a commit. Do not issue the commit until
the sql from step 1 returns no rows.
8. After committing the transaction, resubmit any errored
material transactions
Inventory > Transactions > Material Transactions > query for
error transactions
And also
EAM>Transactions>Pending Resource Transactions > query the
pending resource transactions. Resubmit these.
9. Launch the Cost Manager:
Inventory > Setup > Transactions > Interface Managers
10. Check if Cost Worker is spawned and transactions are
processed.

11. Carry out step 8 again if the transactions are still not
processed.
12

Error 5 : Resource Code is not valid. Please re-enter.

CAUSE :
An resource transaction is stuck with the above error.
ROOT CAUSE SOLUTION: There are two causes for this. Both
are due to incorrect setup.
- The resource has been inactivated on the Define Resource
Form.
- The resource does not exist in operation resources against
the department.
FIX :

Activate the resource by removing the end-date.

Or

Go to operation resources and change the resource

details to include the correct resource.

Stop the Cost Manager.

Run script below to ensure that record is picked up by

Cost Manager:
Update WIP_COST_TXN_INTERFACE
Set group_id = null,
Process_status = 1,
transaction_id = null
where process_status = 3 ;

Now restart the Cost Manager and check transactions

are processed.

If transactions get stuck in process_status of 2

(running), then set

process_status to 1 and process_phase to 2 using

the script and try
13

again.

Error 6 : Error : Employee Number not valid.

CAUSE :
A resource transaction is stuck with the above error because
the
employee details for the resource_id being used are missing.
ROOT CAUSE SOLUTION: Very rare no specific cause
identified.

FIX :

Check that valid employees have been identified for the

resource and they are active.

Stop the Cost Manager.

Run datafix below :

update wip_cost_txn_interface WCTI
set group_id = NULL,
transaction_id = NULL,
process_status = 1,
EMPLOYEE_ID =
( select distinct bre.person_id from
BOM_RESOURCE_EMPLOYEES bre
where bre.Resource_ID = WCTI.Resource_ID AND
bre.ORGANIZATION_ID =
WCTI.ORGANIZATION_ID and bre.instance_id =
WCTI.instance_id),
EMPLOYEE_NUM = (select distinct
paf.employee_number from
BOM_RESOURCE_EMPLOYEES BRE,
PER_ALL_PEOPLE_F PAF where BRE.person_id =
14

PAF.person_id AND BRE.Resource_ID =

WCTI.Resource_ID
AND bre.ORGANIZATION_ID =
WCTI.ORGANIZATION_ID and bre.instance_id =
WCTI.instance_id) WHERE TRANSACTION_ID in (list of
affected WCTI transactions);

Now restart the Cost Manager and check transactions

are processed.

MATERIAL TRANSACTION ERRORS

Error 1: There are uncosted transactions in
MTL_MATERIAL_TRANSACTIONS (MMT) table with
costed_flag = E (error).
CAUSE :
-

An error has occurred we will look at the specific errors.

Remember, the errors mentioned are the common ones
from EAM and not an extensive list of all error types
covering all the modules. From EAM side, these will be
enough.

When these errors have been fixed, resubmit the errored

transactions using the form.

You can use the script on the next page to resubmit the
transactions but use with care and only if you cannot
resubmit from the forms.

Remember if costed_flag is N, then Cost manager has likely

not run yet.

ROOT CAUSE SOLUTION : No solution cause is not clear.

FIX :
15

Backup the tables

Stop the Cost Manager

Fix the error

Run script below :

UPDATE MTL_MATERIAL_TRANSACTIONS
SET costed_flag='N',
error_code = NULL,
error_explanation = NULL,
transaction_group_id=NULL
WHERE organization_id= and
transaction_source_id= and
costed_flag IS NOT NULL;
Commit;

Restart the Cost Manager

Inventory > Setup > Transactions > Interface

Managers
Note : Sometimes, there may not be a specific cause for the
pending transaction and they simply need to be resubmitted.
This is very rare however.

Error 2: ERROR_CODE = CST_INVALID_WIP

ERROR_EXPLANATION= The wip entity is either not
defined or does not have a period balance entry
CAUSE
Uncosted MMT caused by missing records in
WIP_PERIOD_BALANCES
ROOT CAUSE SOLUTION : Use same patches as mentioned
before for the same error seen for resource transactions.
FIX :
Use the solution already provided for missing records in
WIP_PERIOD_BALANCES for resource transactions.
16

Error 3 : CST_INVALID_JOB_DATE
Error Explanation = The transaction date precedes the
release date of the job or schedule.
CAUSE :
The transaction date precedes the release date of the job or
schedule.
ROOT CAUSE SOLUTION : In 11.5.10 , ensure you have
applied
Patches 5184918 and 6405959. In 12.1.3, apply
13387681:R12.WIP.B

FIX :
In some cases the job has no release date and this needs to
be fixed manually by re-releasing the job from the form
(change the status to unreleased and then to release again).
In all cases, the solution is to make sure the Job has a valid
release date. In most cases, this is a user error and there is no
real root cause.
Here is how to correct the release date :

Stop the Cost Manager

Run datafix below :
update wip_discrete_jobs wdj
set wdj.date_released = (select
min(mmt.transaction_date)
from mtl_material_transactions mmt
where mmt.transaction_source_id = wdj.wip_entity_id
17

and mmt.organization_id = wdj.organization_id

and mmt.transaction_source_type_id = 5)
where wdj.wip_entity_id in
(select distinct mmt.transaction_source_id
from mtl_material_transactions mmt,
wip_entities we
where mmt.transaction_source_type_id = 5
and mmt.transaction_source_id = we.wip_entity_id
and mmt.organization_id = we.organization_id
and we.entity_type in (1, 5) -- discrete, lbj
and mmt.costed_flag = 'E'
and mmt.error_code = 'CST_INVALID_JOB_DATE') ;

Now restart the Cost Manager and check transactions are

processed.

Error 4 : Transactions are stuck in MMTT for move order.

CAUSE :
This happens when a WO is cancelled. The move order line
remains in Transact Move Order form in allocated status. Also
the corresponding lines from MMTT are not deleted.
In WIP, both these are deleted on cancelling a work order but
not in EAM.
ROOT CAUSE SOLUTION : There is an enhancement request
in place:
ER :5547252 : MOVE ORDER ALLOCATIONS NOT
REMOVED WHEN EAM WORK ORDER IS CANCELLED
FIX :
Manually delete the allocations from Transact Move Order form
by going to Tools -> Cancel Allocations.
Error 5: Item is allocated but is not picked up by
inventory manager and is not getting issued.
CAUSE : Caused by item allocation process not working
correctly. Exact reason is not known as it rarely happens.
ROOT CAUSE SOLUTION : Unknown.
18

FIX :
1. Navigate to Maintenance Super User > Stores tab
2. Here, on 'Material Issue' page, enter the Work
Order number
3. Click GO
4. You will receive the material issue lines
5. Click on 'Select' checkbox for the materials you
want to issue and check the quantity you need to
issue
6. Press on Issue button
Error 6: Unwanted allocations exist in MMTT. They
happen automatically from EAM.
CAUSE :
Items are allocated in EAM and not processed and are
pending in MMTT.
ROOT CAUSE SOLUTION : Standard functionality.
FIX :
1. EAM Parameters > Uncheck Enable Material Issue
Requests. This will stop the auto allocation functionality.
2. These transactions are not standard move orders and
cannot be removed from Transact Move Order Form.
3. To remove individual allocations :
- Navigate to Maintenance Super User > Stores tab >
Query the
Material
- Use the delete icon to delete the line for the specific
allocation.

Error 7 : Errors when trying to issue material in Stores :

Example shown below :
Material could not be issued. Please examine the errors
for each individual line
19

CAUSE : This type of error usually requires a patch. However,

it can also occur if you are trying to process more then one
rebuildable serial number on a line in one step material issue.
ROOT CAUSE SOLUTION : Standard functionality. You can only
issue one serial for a rebuildable.
FIX :
You can only issue one serial for a rebuildable. Quantity must
be one.
In most cases, this error below requires a patch. I am including
examples of cases where no patch is needed - as we are
diagnosing and actually fixing transactions only in this
whitepaper
Error 8 : Material could not be issued. Please examine
the errors for each individual line (see below example)
1. Material could not be issued. Please examine the
errors for each individual line.
2. Row 1 Error - Transaction processor error
CAUSE: This type of error usually requires a patch. I am only
including examples where the solution does NOT require a
specific patch and is caused by something else.
The above error can happen when a user is attempting to issue
a rebuildable serial number to a work order when that serial
rebuildable number has been in the hierarchy before.
ROOT CAUSE SOLUTION : Standard functionality.
FIX :
To bring the rebuild back to into inventory, complete one of the
following actions:
1- Use the Replace Rebuild functionality in eAM - Issue another
rebuild and specify the current one to be replaced. It will create
a work order for the replaced rebuild that can be completed to
subinventory.
2- Break the relationship manually and then receive the rebuild
in inventory. Do this as follows:
20

In eAM Self service, pull up the parent asset in the Assets

tab.

Select to view the configuration history for the asset. It

should show the rebuild as a child.

Update the configuration by end dating the relationship.

This in essence breaks the relationship.

Then complete a Miscellaneous Receipt transaction in

inventory to bring the item into inventory.

Error 9 : Material could not be issued. Please examine

the errors for each individual line (see below example)
1. Material could not be issued . Please examine the
errors for each individual line
2. Row 2 Error- Error: error .. in call back to WIP
wip_mtlTempProc_grpnull
CAUSE :
This type of error usually requires a patch. I am only including
examples where the solution does NOT require a specific patch
and is caused by something else.
The above error happens when a Rebuildable serial which is
erroring out already has a valid relationship with another
parent.
ROOT CAUSE SOLUTION : Standard functionality.
FIX :
End date relationship between rebuildable which is erroring out
and exising parent asset number :
-

Maintenance Super user > Assets > Select problematic

Rebuildable > View Configuration History > view Parents
> add end date to the existing relationship
Error 10 : Move Asset Error :

Move Asset Transaction Processor Error. Please check

the below table for the Errors. Results can be exported.
21

CAUSE:

SFM Concurrent Managers and "SFM Event Manager

Queue Service" not up and running

Track in Installed Base" flag, from the Master Item,

Service tab is not checked.

Or

ROOT CAUSE SOLUTION : User setup issue.

FIX :
1. Please check if the SFM Concurrent Managers is up and
running
2. Navigate to System Admin Responsibility > Concurrent >
Manager > Define Query up "SFM Event Manager Queue
Service"
2. Select "Work Shifts" Check the value set for the field
"Parameter".
3. Check whether the value XDP_DQ_INIT_NUM_THREADS is
set to "1". If not, please update it to 1.
4. Navigate to SFM System Administrator responsibility >
Administration > Queue Console
5. Select Event Manager Queue row and click on the
services button.
6. Query for "SFM Event Manager Queue Service" and check
whether Actual and Target values are set to 1
7. If they are not, please select the start button and ensure
that they are set to 1.
8. Then submit concurrent request "SFM Event Manager
Queue Service". This would process the messages which are
in ready status in the SFM queue.
To solve the second cause, check the flag "Track in Installed Base"
(N) Inventory -> Master Item -> Service tab.

22

EAM-OTL Integration
December 2013

23

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
Oracle is a registered trademark of Oracle Corporation. Various
product and service names referenced herein may be trademarks
of Oracle Corporation. All other product and service names
mentioned may be trademarks of their respective owners.
Copyright 2003 Oracle Corporation
All rights reserved.

24