Sie sind auf Seite 1von 13

Fundamentals of Asset Move Functionality

Prepared by
Oracle Support
August 1, 2013

Table of Contents

Introduction ... 1
Technical Overview ... 1
Setup and Pre-requisites .. 2
Troubleshooting . 8
Important Fixes and Notes ....... 9

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.

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.

The following entities will also move with the asset:


Activities: if the Activity Definition is assigned to the destination organization. If
not, you will need to use the Activity Workbench to assign an activity to the new organization.
PM schedules
Meters
Failure history and setup
These entities do not move with the asset:
Work orders
Routing
Cost history
Collection plans

Setup and Pre-requisites


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.

Why Intermedia Subinventory is needed ? Its a subinventory needed for autocreation of the misc
receipt to bring onhand needed for the transfer. This is mentioned in Oracle Enterprise Asset
Management User's Guide Release 12.1 - Section Using the Asset Move Workbench, page 20-33:
EAM performs a miscellaneous receipt of an asset if there is no quantity available in the expense
subinventory. This process does not track the quantity for the asset. These miscellaneous receipts are
done at zero cost, and are placed in an expense intermediate subinventory.
2

2) Enable Service Fulfillment Manager (SFM) Event Manager Queue Service


- Responsibility: SFM System Administrator
- Navigation: Administration -> Queue Console

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.

- Click on the Services button

- Check the 'SFM Event Manager Queue Service' is having 'Actual' and 'Target'
values set to 1 and 1.

- To ensure that only one SFM thread is run. Please check as follows.
System Admin Responsibility > Concurrent > Manager > Define
Query up SFM Event Manager Queue Service

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.xdp.
dequeuer.core.Dequeuer:XDP_DQ_API=XNP_EVENT.PROCESS_IN_EVT:XDP_DQ_INIT_NU
M_THREADS=1

5
3) Set up a Shipping Network
Navigation: Inventory -> Setup -> Organizations -> Shipping Networks

Click on Find button to see if a shipping network already exists.


If there are no rows, let's create a shipping network for testing purposes.

First row:

From: EM1

To: FAC

Transfer Type: Direct

Elemental Visibility Enabled: Checked (checkbox next to FOB LOV)

Set the accounts in primary and secondary accounts

Save.

(You can add another row with FAC as origin and EM1 as destination with the same setup)

6
4) Important Notes
a. Asset Routes cannot be moved.
b. The Source Org and The transfer Orgs should be in open period.
c. The Asset Group should be transactable.
d. The Asset (Or Rebuild) Group should already be assigned to the Destination org in
the Item Master Form.
e. Asset should not have Property Manager Link. In Asset Number Form: Location Tab

has
Production Organization and Equipment Details. This value corresponds to Production
Equipment Link.
f. Transfer Type should be Direct, not Intransit.
g. 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. You may refer to user guide for further clarification.
h. If a user wants to perform transfers between Expense Sub Inventories and Asset Sub
Inventories, They
have to set the profile option "INV: Allow Expense to Asset Transfer" to "Yes".
i. If the Asset has no On Hand Quantity, a Misc Receipt Transaction is performed in
background into the
Intermediate Subinventory that was defined in the EAM Parameters.
j. Only Expense Subinventories are shown in the Intermediate Subinventory LOV.
So one has to set the below profile Option "INV: Allow Expense to Asset Transfer"
to "Yes".
Otherwise, the Asset Transfers will not be allowed to Destination Subinventory
from the
Intermediate Sub Inventory if the Destination Subinventory is an Asset
Subinventory.
k. If an Asset/Rebuildable is already issued out of stores then a new serial would be
created by doing a
Miscellaneous Receipt Transaction if the Profile option "INV: Restrict Receipt of
Serials" is set to "No".
If user wants to Stop that then the profile Option should be set to "Yes".

l. 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.
m. 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.
m. If An Asset is defined in a production Org (Example M1 is production Org
maintained by EM1) and
there is no on hand Quantity on that serial and user wants to transfer this to
other Maintenance Org,
say FAC, then a Misc Receipt Transaction is triggered in EM1 and then a transfer
happens from EM1
to FAC.
n. If An Asset is defined in a production Org (Example M1 is production Org
maintained by EM1) and
there is on hand Quantity then a transfer happens from M1 to FAC directly.
7

Troubleshooting
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:
a. Go to Install Base Administrator-> Transactions Error processing form
b. Select the record and re-submit from the Tools menu
4) Make sure that the SFM manager is up and running. This can be verified by the
following action plan:
a. Resp: SFM System Administrator -> Administration -> Queue Console -> Click on
"Services" Button

b. Ensure that for "SFM Event Manager Queue Service" Actual and Target values
should be '1'
5) Go to responsibility: SFM System Administrator ->Concurrent -> Define Manager ->
Query For "SFM Event Manager Queue Service"
a. Click on "Work Shifts" button.
b. In the Parameter field, ensure that the string ends with
'XDP_DQ_INIT_NUM_THREADS=1' which
makes the number of XDP threads being processed as 1 at a time. If it ends with
'2', the asset move
transactions error out.
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 go to
SELECT value
FROM v$parameter
WHERE name = 'user_dump_dest';
Get the web service SQL*Trace related the trace ID.
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:
a. Set profile "CSI: Debug Level" = 10
b. Set profile 'CSI Log File Name' to test
c. Perform the test case (i.e., asset transfer transaction).
d. Upload log file 'test-counter.log' generated in directory specified in profile 'CSI
Log File Path'
Note: Refer to DOC ID 239627.1 for more clarification on how to obtain the log.
8

Important Fixes and ERs


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

After asset move is done, asset can no


longer be searched in the source org.

1557049.1 15959864:R12.EAM.B

Code issue that was fixed. Patch is


released.

Transaction Processor Error When Doing


An Inter Org Transfer Of Asset

1096126.1

Setup issue described in the note.

Unable To Perform Internal Receipt


Transaction For Eam Asset Transfer

1388753.1 10139440:R12.EAM.B

Code issue that was fixed. Patch is


released.

Exception Error Page Encountered When


Moving An Asset

1323965.1 12319034:R12.EAM.B

Code issue that was fixed. Patch is


released.

Assets from level-2 onwards are


transferred even though asset at level-1 is
end dated in a given hierarchy

13723024:R12.EAM.B

Code issue that was fixed. Patch is


released.

EAM ASSET TRANSFER API NOT


WORKING FOR TRANSACTION TYPE
OTHER THAN MISC. RECEIPT

14048769:R12.EAM.B

Code issue that was fixed. Patch is


released.

In EAM, Inter Org In-transit Asset


transfers are failing from Maintenance
Super User Responsibility After Setting
Profile 'INV: Create RCV Shipments in
Bulk' to "Yes"

14786085:R12.EAM.B

Code issue that was fixed. Patch is


released.

In Maintenance Super User Responsibility


while attempting Asset Move, error was
seen in inventory interface tables with
message 'Invalid Transaction UOM'.

9012795:R12.EAM.B

Code issue that was fixed. Patch is


released.

When performing an Asset Move Transfer


for a newly defined asset that has no
onhand Quantity against it, there is a
mismatch in the date for the
miscellaneous receipt transaction and
actual date of asset move transfer

9571785:R12.EAM.B

Code issue that was fixed. Patch is


released.

When Performing Asset Move From One


Organization To Another, Destination
Organization field is not enabled

1565334.1

Setup issue described in the note.

Asset Move Process Did Not Successfully 1380129.1


Bring Activity With Asset During InterOrg Asset Move Process

Stuck records for the asset move


transactions which halted the asset
move process.

Important Fixes and ERs (cont.)


Issue Description

DOC ID

Patch #

ER #

Remarks

UNABLE TO MOVE ASSET TO


SUBINVENTORY WHERE LOCATOR
CONTROL IS DYNAMIC

6853615 This ER is under review and has not


been approved for future
implementation as of yet.

EAM ASSET MOVED AND ABLE TO


ISSUE MATERLIAL TO WORK
ORDER IN ORIGINAL ORG

14796140

When the profile option


"INV:Restrict Receipt of
Serials" is set to "No", The
receipt of serials into
inventory through transactions
such as
Miscellaneous receipt, PO
receipt should exclude the
serial numbers that are issued
out of inventory through the
following transactions:
- Issue to Field location
- Issue to projects
- Sales order shipment

8203382 This ER is under review and has not


been approved for future
implementation as of yet.

10

Das könnte Ihnen auch gefallen