Professional Documents
Culture Documents
Asset Management
Asset Move Understanding
and Troubleshooting
Table of Contents
I. INTRODUCTION.......................................................................................................................................1
II. TECHNICAL OVERVIEW.............................................................................................................................1
III. SETUP AND PRE-REQUISITES .....................................................................................................................2
I.
Introduction
This paper describes the fundamentals of Asset Move functionality within Oracle Enterprise
Asset Management (eAM). Asset Move functionality was introduced in Release 12.1.1.
You may need to move assets from one organization (often a different location) to
another organization for different reasons, to replace a failed asset , or to borrow an
asset for a particular job or project.
II.
Technical Overview
The Asset Move Workbench enables you to transfer an asset and its child assets from one
maintenance organization to another as a single unit, and the parent child asset
relationships are preserved. Asset Move functionality can also be achieved via the
following 2 Inventory forms:
Inventory -> Transactions -> Inter-Organization Transfer
OR
Inventory -> Transactions -> Subinventory Transfer
However, the advantage of using it from EAM UI (i.e., Asset Move page) is that the
entire hierarchy can be moved as a single unit.
III.
The following setup steps are required to ensure proper asset transfer.
1) Select Intermediate Subinventory
Navigation: EAM -> Setup -> Parameters
Define an Intermediate Subinventory in eAM Parameters form in the source organization (i.e., source
org and not destination org). This intermediate subinventory is the default subinventory to
which
all the assets undergoing miscellaneous receipt transactions are received while performing the
Asset Move transfer. The Intermediate Locator value indicates the number assigned to the
expense intermediate inventory.
Note:
Only the expense subinventories associated with your organization are available for selection.
This manager will need to be enabled to allow user view transferred asset in Self Service, even
though it can be viewed in Forms. Please review DOC ID 180718.1 for more information.
The value for the parameter should read like this, the last parameter indicates the
number of threads:
SM_MSG_WAIT_TIME=10:SM_SLEEP_TIME=10:XDP_DQ_CLASS_NAME=oracle.apps.xd
p.dequeuer.core.Dequeuer:XDP_DQ_API=XNP_EVENT.PROCESS_IN_EVT:XDP_DQ_INIT_
NUM_THREADS=1
If there are no rows, let's create a shipping network for testing purposes.
First row
From: EM
To: FAC
You can add another row with FAC as origin and EM1 as destination with the same
setup
4) Setup/Implementation Considerations
The Source Org and The transfer Orgs should be in open period.
Asset Group should already be assigned to the Destination org in Item Master Form.
You should not have Production Equipment Link. In Asset Number Form: Others Tab
has Property Management Region (Fields: Location Name and Location Code). They
correspond to Property Management Link. Refer to Users Guide for clarification.
If you want to perform transfers between Expense Sub Inventories and Asset Sub
Inventories, you have to set the profile "INV: Allow Expense to Asset Transfer" to "Yes".
Only Expense Subinventories are shown in the Intermediate Subinventory LOV.
If Asset/Rebuildable is already issued out of stores then a new serial would be created
by doing a Miscellaneous Receipt Transaction if the profile INV: Restrict Receipt of
of Serials" is set to "No".
There is a demand from some customers that an Asset/Rebuild is "Issued out of stores", it
is fine to create and receive a new Serial But if the Asset/Rebuild is "Issued to Projects"
or "Issued to a Work Order", then the a new serial should not be created.
Currently Inventory does not distinguish between "Issued out of Stores" , "Issued to
Projects", "Issued to a Work Order". All it considers is the above profile Option and
performs a Receipt of Serial Based on its Value. There is an Existing ER to make
changes as above: ER # 8203382.
IV. Troubleshooting
9
There are common troubleshooting steps that come into play when debugging issues related to Asset Move,
e.g., asset cannot be viewed in the destination org after performing Asset Move.
1) If user is not able to achieve the Asset Move functionality at all for any Assets, via
Asset Move functionality, user should try performing from Inventory UIs first to see
if there is any issue from Inventory responsibility:
Inventory -> Transactions -> Inter-Organization Transfer
OR
Inventory -> Transactions -> Subinventory Transfer
2) Resubmit transactions via Inventory Transaction Open Interface form and Pending Transactions form.
a. Go to Inventory -> Transactions -> (Transactions Open Interface or Pending
Transactions).
b. Query for the asset for which Inter-org transfer is being done.
c. Get the screen shot of all the tabs and also the error explanations for further analysis by Support
3) Process stuck transactions by resubmitting the transactions from the
"Transactions Error Processing" in the Install Base Administrator responsibility. Steps are:
10
Troubleshooting (cont.)
6)
If the issue persists after performing above steps, please generate trace with
binds as follows:
a. When in the webpage, click the "Diagnostics" in the top then set Diagnostics:
Set Trace Level
b. Then set Trace with binds and waits and click save
c. Go back to reproduce the issue. Once done, disable trace and note down the
Trace ID, then
run this sql query:
SELECT value
FROM v$parameter
WHERE name = 'user_dump_dest';
Get the web service SQL*Trace related the trace ID.
Note:
If you need further clarification on creating a trace, please follow Doc ID
190685.1.
7) Generate CSI Log while re-submitting the transactions. This will help in
reviewing additional debugging messages. Steps are as follows:
11
V.
The following shows important bugs, Enhancement Requests (ERs) and Notes that addressed Asset
Move related issues. Please not that patch 14786085:R12.EAM.B is highly recommended,
since it delivers latest set of files related to Asset Move Functionality.
Issue Description
DOC ID
Patch #
ER #
Remarks
12
DOC ID
Patch #
ER #
Remarks
13
14