Monday Jul 14, 2014

How To Customize Oracle Asset Tracking to Meet Specific Business Requirements

Oracle Asset Tracking (OAT) includes a number of client extention hooks that can be used to change the default logic of OAT. These client extention hooks can offer great flexibility for customers to implement their own logic to derive the attributes for a fixed asset during the asset creation/move processes in the OAT module.

Empty stubs are shipped with OAT via package CSE_ASSET_CLIENT_EXT_STUB (CSEFASTB.pls). Custom code needs to be added in a number of of stubs in order to override the default functionality.


In the document 'How To Customize Oracle Asset Tracking to Meet Specific Business Requirements' (Doc ID 1674412.1) we list the stubs that are available and what each one can be used for.  

This is a great resource for any customers who need to customize the standard functionality.  If you have any questions, remember that our experts in the MOS Install Base Community are there to help!

Monday Jun 02, 2014

How To Check If a Transaction Related to Oracle Asset Tracking Has Been Accounted in SLA

In Oracle Asset Tracking (OAT), we often see situations where a pending transaction has failed to be processed by the OAT programs. Typical situations can be:
  • a pending transaction errors with "Unable to derive accounts from sub ledger accounting for the material transaction"
  • a transaction is not picked by OAT programs.


The Create Accounting program log file will show error messages and possible corrective actions to solve the error.  But as this is usually a scheduled program, often any errors that are reported are missed by users.

To aid OAT users to identify if a transaction has failed and accounting has not been created, we have now created a SQL script which can be run for any pending transaction:

How To Check If a Transaction Related to Oracle Asset Tracking Has Been Accounted in SLA ? (Doc ID 1673414.1)
Using the script in this note, the user can pass the material transaction ID for the related transaction and the script will check if SLA accounting entries have been created for this specific transaction or not.

If the SLA accounting entries have not been created, the script will prompt the user to run Create Accounting program.  After Create Accounting has been run, the user can run the script again to confirm that accounting has been created.

Tuesday May 27, 2014

Your Feedback on Oracle Asset Tracking

Oracle Asset Tracking Development strives to improve customer satisfaction with our Oracle Asset Tracking product.  In this context, they are very interested in getting your feedback about the Oracle Asset Tracking module.

Recently, we have seen more and more customers using OAT and we would like to know for example:
  • Have you have encountered any product gaps that need to be addressed?
  • Are there business flows that do not suit your requirements?
  • What new features you want to see in the product?
Please share your feedback with us and we will discuss it with Oracle Asset Tracking Development and Product teams to improve the product.

To share your feedback either post to the dedicated thread in the MOS Install Base Community here OR add a comment to this blog post (note that the blog comment you enter won't immediately be visible in the blog).

Monday Apr 07, 2014

Asset Tracking: How to Capitalize Serialized Normal Items Through Sales Order Shipment

The Oracle Asset Tracking product supports various transactional flows to capitalize a physical asset's (item instance) cost into a fixed asset at an appropriate point of its eligibility. Depreciable items (aka Capitalize on Receipt or COR items) make the item eligible for capitalization at the point of receipt transaction whereas Normal items (aka Capitalize on Issue or COI items) make the item eligible for capitalization when the instance is put in service or when issued to a field location.

In environments such as Equipment rentals and leases, there is a need for Oracle Asset Tracking to initiate capitalization when a normal item is shipped out to the customer. As a result, the existing Loaner flow functionality in Oracle Asset Tracking module has been extended to provide an out of the box functionality to capitalize of Normal Items when they are shipped to customer locations.  This functionality is in R12.2 and in R12.1.3 via Patch 17181028:R12.CSE.B: Consolidated Patch For Oracle Asset Tracking.

In Doc ID 1623821.1 a detailed test case is described, explaining the business flow and giving the necessary application setups and step-by-step process.

If you are interested in other Oracle Asset Tracking test case examples, take a look at Doc ID 1550977.1: Master Note For Oracle Asset Tracking Test Case Documents.


Tuesday Mar 11, 2014

New Diagnostic for Oracle Asset Tracking

In January our blog entry 'Troubleshooting Asset Tracking Pending Transactions' we told you about a new note to help you resolve problems with Oracle Asset Tracking (OAT) pending transactions.  Now we're happy to announce a new diagnostic script which will do a lot of the hard work for you!  

The new Oracle Asset Tracking Pending Transactions Diagnostic Program collects information related to pending transactions in Install Base and also some generic information that can be useful for the investigation of the issue at hand. This program will collect and display information for a given Inventory Item ID (either serialized or non-serialized) and can help in identifying the problems with pending transactions for any IB Trackable item. 

The program output report has the following sections:

  •     Item Definition
  •     Inventory Material Transaction Details (MMT)
  •     Install Base Error Transaction Details
  •     Install Base Pending Transaction Details
  •     Instance History Details for Pending Transactions
  •     Instance-Asset Details for Pending Transactions
  •     Project Details
  •     Fixed Asset Details
  •     Install Base Parameters information
  •     Asset Location Mapping in Install Base
  •     Asset Book and Category Set up in FA
  •     CSE Profile Option Setups

The diagnostic toDoc ID 16168591.ol consists of a self-contained PL/SQL code package which will be executed as a concurrent program.

For more details on how to install and use this program, please refer to: Oracle Asset Tracking Pending Transactions Diagnostic Program (Doc ID 1616859.1).

About

Welcome to the EBS Support Blog where Oracle insiders share news and information about EBS products including new releases, tips and tricks, troubleshooting guides, upcoming webcasts and links to EBS Communities.

Stay Connected

Twitter

Search

Archives
« May 2015
SunMonTueWedThuFriSat
     
1
2
3
4
5
7
9
10
11
16
17
18
22
23
24
25
27
28
29
30
31
      
Today