Professional Documents
Culture Documents
Asset
Tracking
setup
overview
Brief overview on how to setup asset tracking to generate your
Installed base customer assets resulting sales order fulfillment
The testing disclaimer in the TM block on the last page (highlighted in yellow) is provided
by the FCC. It must appear in the TM block for all pre-release, pre-GA products. Be sure to
remove the yellow highlighting before publishing. When the product becomes GA, update
your collateral by removing the disclaimer from the TM block. If your product is already GA,
delete the disclaimer from the TM block.
Important: If your product is not GA, then you cannot include any regulatory compliance
information in the white paper. Regulatory compliance information may be included for GA
products only if you have completed all required safety and emissions testing, and you
have received the certificates issued by the testing organization.
Navigation Details:
You can specify one of three values in the Asset Tracking attribute: Not Tracked,
Customer Asset, or Full Lifecycle:
• Not tracked
Means that the product is never tracked as an installed base asset. You can’t
create assets for an item that is not tracked by any means: User interface, file-
based data import, or even the REST service.
Means that the product tracking as an installed base asset starts only when the
item is fulfilled or shipped to a customer. Asset tracking stops when the product
is returned to inventory.
• Full Lifecycle
For serialized items, it means that an asset is created as soon as the product is
received in inventory. This applies regardless of the receipt source, whether it’s
an inventory receipt, work order completion receipt, or a purchased order
receipt. Beyond this point, every move of the products is tracked and reflected
in the asset.
For nonserialized items, it means that an asset relationship is created when the
product is consumed as part of a serialized tracked product during a serialized
work order. In other words, an asset is created for the consumed product and
will become an asset component of the top product asset going forward, as
explained for the serialized products. However, for nonserialized items, asset
creation at inventory receipt and further tracking does not take place.
Inventory
Perform needed setup for inventory, manufacturing, and shipping of the products and components.
Manufacturing
Define your work definitions as needed for the manufacturing of the product. As stated earlier the
work definition must be enabled for serialized production for asset lifecycle tracking.
Order Management
Perform needed setup for order management in general like sourcing order promising for the sold
products
In the full lifecycle tracking scenarios, the assets are created during inventory and manufacturing
processes, and they need to be updated by order management when the order is fulfilled. Order
management brings the account, charge details, and other sales order details information into the
asset. For this update to occur, the DOO_ManageAsset task must be made part of the sales order
orchestration process. Examples of steps to perform are provided in the next section.
Outbound Process
The example is based on modifying a copy of the seeded DOO_OrderFulfillmentGenericProcess
orchestration process independently of other process or modifications you must build.
3. Search for the Manage Orchestration Process Definitions task and open it.
5. Edit it, and insert the Asset Management task after the Merge in the step definition tab
ATTRIBUTE VALUE
Step Number Unique value – It should be between the value for Merge
Task and Create Invoice task
Step Name Any unique, user friendly name (for example Asset
Management)
Task DOO_AssetManagement
7. Go to the Orchestration Process Status Values tab and insert two new rows
ATTRIBUTE VALUE
Repeat the step to add value for Status value Not Applicable with expression value as NOT APPLICABLE
ATTRIBUTE VALUE
Repeat the step to add value for Status value Not Applicable with expression value as NOT APPLICABLE
12. Go to the Actions menu and select Validate. A Validated check mark will appear beside the
orchestration process name
14. Go to the Actions menu and select Deploy –The process will be deployed (details can be confirmed in
the EM – Once the process is confirmed in the EM UI as deployed it can be used to execute the forward flow)
Inbound Process
The example is based on a modification of generic return process built for the purpose, detailed might vary
depending on what process you need to build.
3. Search for the Manage Orchestration Process Definitions task and open it
4. Search for the order return orchestration process you need to tailor
5. Edit it, and insert new step after the Wait for Receipt in the step definition tab
ATTRIBUTE VALUE
Step Number Unique value – It should be between the value for Merge
Task and Create Invoice task
Step Name Any unique, user friendly name (for example Asset
Management)
Task DOO_AssetManagement
7. Go to the Orchestration Process Status Values tab and insert a new row
ATTRIBUTE VALUE
ATTRIBUTE VALUE
12. Click on Actions and select “Validate” – a “Validated” check mark should appear beside the
orchestration process name
13. Click on Actions and select “Release” – orchestration process status should be changed from “New”
to ‘Released’
14. Click on Actions and select “Deploy” –The process should be deployed (details can be confirmed in
the EM – Once the process is confirmed in the EM UI as deployed it can be used to execute the forward flow)
Steps
4. Below are examples of the outbound & inbound fulfillment process selection rule based on the asset
tracked value in the fulfillment order line
7. Check if there is a EIL routing rule defined for the Asset Management Task. If not, define a rule
exactly like below.
CONCLUSION
If you follow the guidance provided in this white paper, you can successfully set up your products to generate
your Installed Base customer assets resulting from sales order fulfillment.
Worldwide Headquarters
500 Oracle Parkway, Redwood Shores, CA 94065 USA
Worldwide Inquiries
TELE + 1.650.506.7000 + 1.800.ORACLE1
FAX + 1.650.506.7200
oracle.com
CONNECT W ITH US
Call +1.800.ORACLE1 or visit oracle.com. Outside North America, find your local office at oracle.com/contact.
Copyright © 2019, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the
contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other
warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are
formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any
means, electronic or mechanical, for any purpose, without our prior written permission. This device has not been authorized as
required by the rules of the Federal Communications Commission. This device is not, and may not be, offered for sale or lease, or
sold or leased, until authorization is obtained. (THIS FCC DISLAIMER MAY NOT BE REQUIRED. SEE DISCLAIMER SECTION ON
PAGE 2 FOR INSTRUCTIONS.)
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective
owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and
are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are
trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0919
White Paper Title
July 2019
Author: Bernard Ladent
Contributing Authors: Briestly Manesh