Oracle® Asset Tracking: Implementation Guide Release 12
Oracle® Asset Tracking: Implementation Guide Release 12
December 2006
Oracle Asset Tracking Implementation Guide, Release 12 Part No. B25723-01 Copyright 2006, Oracle. All rights reserved. Primary Author: Stacey Tucker-Blosch The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065. The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs. The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party. Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
Contents
iii
Matching Invoice to Purchase Order...................................................................................... 2-15 Defining Invoice Quantity Tolerance..................................................................................... 2-16 Defining Oracle Projects Parameters...................................................................................... 2-16 Defining a Descriptive Flexfield for Expenditure Items........................................................2-16 Setting Up Asset Creation Grouping Methods for Project Expenditure Items..................... 2-18 Additional Oracle Projects Setup Considerations.................................................................. 2-19 Defining Oracle Assets Parameters........................................................................................ 2-20 Performing Oracle Installed Base Setup Tasks...................................................................... 2-21 Defining HZ Locations ........................................................................................................... 2-21 Associating HR and HZ Locations with Asset Locations....................................................... 2-22 Setting the Freeze Install Parameter....................................................................................... 2-22 Setting Up Internal Orders for Assets.................................................................................... 2-23 Setting Up Workflow Notification Options........................................................................... 2-23 Explaining the Open Interface Flow for Assets...................................................................... 2-23
iv
Send Us Your Comments
Oracle Asset Tracking Implementation Guide, Release 12
Part No. B25723-01
Oracle welcomes customers' comments and suggestions on the quality and usefulness of this document. Your feedback is important, and helps us to best meet your needs as a user of our products. For example: Are the implementation steps correct and complete? Did you understand the context of the procedures? Did you find any errors in the information? Does the structure of the information help you with your tasks? Do you need different information or graphics? If so, where, and in what format? Are the examples correct? Do you need more examples?
If you find any errors or have any other suggestions for improvement, then please tell us your name, the name of the company who has licensed our products, the title and part number of the documentation and the chapter, section, and page number (if available). Note: Before sending us your comments, you might like to check that you have the latest version of the document and if any concerns are already addressed. To do this, access the new Applications Release Online Documentation CD available on Oracle MetaLink and www.oracle.com. It contains the most current Documentation Library plus all documents revised or released recently. Send your comments to us using the electronic mail address: [email protected] Please give your name, address, electronic mail address, and telephone number (optional). If you need assistance with Oracle software, then please contact your support representative or Oracle Support Services. If you require training or instruction in using Oracle software, then please contact your Oracle local office and inquire about our Oracle University offerings. A list of Oracle offices is available on our Web site at www.oracle.com.
Preface
Intended Audience
Welcome to Release 12 of the Oracle Asset Tracking Implementation Guide. See Related Information Sources on page viii for more Oracle Applications product information.
Documentation Accessibility
Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/ .
vii
Structure
1 Overview of Oracle Asset Tracking 2 Implementation and Setup 3 Oracle Asset Tracking Administration 4 Oracle Asset Tracking API
Integration Repository
The Oracle Integration Repository is a compilation of information about the service endpoints exposed by the Oracle E-Business Suite of applications. It provides a complete catalog of Oracle E-Business Suite's business service interfaces. The tool lets users easily discover and deploy the appropriate business service interface for integration with any system, application, or business partner. The Oracle Integration Repository is shipped as part of the E-Business Suite. As your instance is patched, the repository is automatically updated with content appropriate for the precise revisions of interfaces in your environment.
viii
ix
1
Overview of Oracle Asset Tracking
This chapter covers the following topics: Definition of Oracle Asset Tracking Inventory Item and Asset Tracking Features of Oracle Asset Tracking Integration Points and Dependencies for Oracle Asset Tracking
warehouses, on trucks, installed in the network, or on project sites, facilitating financial transactions using physical movements of material and equipment. In addition, Oracle Asset Tracking can provide a life-cycle history of all activity for that equipment. An asset comprises a collection of items. The items may be trackable or not trackable; the tracking is carried out in Oracle Installed Base and Oracle Asset Tracking. During implementation, items are designated as trackable at the item master level in Oracle Inventory. Oracle Asset Tracking tracks the activity of the trackable items through inventory, projects, and into fixed assets. In Oracle Assets you perform the Mass Additions concurrent process to create assets. Summary of Oracle Processes that Track Internal Products and Assets The following diagram shows a summary of the Oracle application modules, and the transactions and messages associated with Oracle Asset Tracking.
Summary of Oracle Processes That Track Internal Products and Assets
For example, when a field service technician enters a report that equipment has been placed into service, the deployment system may send a message to Oracle Asset Tracking. This message updates the status of the equipment to "In Service," and gives its in-service date to Oracle Projects. The asset is now ready to be created in Oracle Assets. Messaging Architecture in Oracle Asset Tracking The messaging architecture receives requests from external publishing systems in
eXtensible Markup Language (XML) format. Based on the input requirements, the application updates the status and keeps a history of transactions for the tracking unit. Subsequently, the application publishes outgoing requests to the subscribing systems for further processing. The publishing and subscribing systems include: Installed Base, Inventory, Purchasing, Payables, Assets, Projects, Workforce Management, and other legacy systems.
2
Implementation and Setup
This chapter covers the following topics: Setup Checklist Install Required Oracle Application Modules Define Users with Responsibilities in Oracle Application Modules Define System Profile Options for Oracle Asset Tracking Define System Profile Options for All Dependent Responsibilities Define Oracle Inventory Parameters Defining Organization Parameters Defining User-Definable Transaction Types Defining Normal Items Defining Depreciable Items Associating Subinventories to Locations Defining Inventory Period Additional Oracle Inventory Setup Considerations Defining Oracle Purchasing Parameters Defining Oracle Payables Parameters Matching Invoice to Purchase Order Defining Invoice Quantity Tolerance Defining Oracle Projects Parameters Defining a Descriptive Flexfield for Expenditure Items Setting Up Asset Creation Grouping Methods for Project Expenditure Items Additional Oracle Projects Setup Considerations Defining Oracle Assets Parameters
Performing Oracle Installed Base Setup Tasks Defining HZ Locations Associating HR and HZ Locations with Asset Locations Setting the Freeze Install Parameter Setting Up Internal Orders for Assets Setting Up Workflow Notification Options Explaining the Open Interface Flow for Assets
Setup Checklist
Oracle Asset Tracking has an ability to track an item instance regardless of the location and also to perform the financial updates automatically. Users may use both the tracking and financial update functionality or just the instance tracking capability. If you are not using asset creation through Oracle Asset Tracking, then you do not have to perform the setups in Oracle Projects and Oracle Assets. The following table is a comprehensive list of all setup steps that must be completed:
Setup Steps for Oracle Asset Tracking Step Title 1. Install required Oracle application modules, page 2-3 2. Define users with required responsibilities, page 2-4 3. Define system profile options for Oracle Asset Tracking, page 2-4 4. Define system profile options for all the dependent responsibilities, page 2-5 5. Define Oracle Inventory parameters, page 2-8 6. Define Oracle Purchasing parameters, page 2-14 7. Define Oracle Payables parameters, page 2-15 8. Define Oracle Projects parameters, page 2-16 9. Define Oracle Assets parameters, page 2-20
Step Title 10. Perform Oracle Installed Base setup tasks, page 2-21 11. Set Up Internal Orders for Assets, page 2-23 12. Set Up Workflow Notification Options, page 2-23 13. Explaining the Open Interface Flow for Assets, page 2-23
Note: If you are an Oracle Installed Base user and want to limit your
You must also install the following if you are using internal sales orders for normal items: Oracle Order Management
Use a standard setup for Oracle Purchasing, Oracle Assets, Oracle General Ledger, Oracle Payables. For detailed setup information on all of these applications consult the appropriate documentation set.
Note: You must also install and set up Oracle Human Resource
Management System (HRMS). In Oracle HRMS, you must set up users with the ability to approve purchase orders. For detailed setup information on Oracle HRMS, please refer to the Oracle HRMS implementation documentation appropriate to the country where the application is being installed.
From the Navigator for the System Administrator responsibility, choose Profile and then select System. In the Profile Name field of the Find System Profile Values window, enter CSE% and click Find. In the System Profile Values window, define the profile options as follows:
2.
Oracle Asset Tracking Module Profile Option Settings Profile Name Default Value Profile Option Function Sets the file and directory of the debug log file. DBA can create own path of directory for fog file Enter Y (yes) or N (no) to control the debugging function for the message dequeuer. This option is used to set the default FA book type code for creating asset from depreciable item. The default expenditure type used when material is issued to a project. This must be set to Y if you are using Oracle Asset Tracking. Required
/sqlcom/temp/
Optional
Optional
Responsibilities Required for Profile Option Setup Oracle Application Module Oracle Inventory Oracle Purchasing Oracle Payables Oracle Projects Oracle Assets Oracle General Ledger Oracle Installed Base Oracle Asset Tracking Oracle Order Management Sample Responsibility Name Inventory Manager Purchasing Manager Payable Manager CRL 11i Projects Assets Manager General Ledger Installed Base Administrator Asset Tracking Manager Order Management Super User
names. For your installation, use the appropriate equivalent responsibility name or names set up for each Oracle application module.
The following table shows the supplementary profile options that are required to be set up. The table first shows the profile options that must be set up for each of the responsibilities listed in the preceding table. This is followed by the profile options that are required for specific responsibilities only.
Supplementary Profile Options Required for Oracle Asset Tracking Profile Options MO: Operating Unit Profile Level Responsibility Responsibilities All responsibilities in preceding table.
Responsibilities All responsibilities in preceding table. All responsibilities in preceding table. All responsibilities in preceding table. All responsibilities in preceding table. All responsibilities in preceding table. All responsibilities in preceding table. Oracle Asset Tracking Oracle Installed Base Order Management
Responsibility
Responsibility
Responsibility
Responsibility
Site, Responsibility
Responsibility
Responsibility
From the Navigator for the System Administrator responsibility, choose Profile and then select System. For each combination of responsibility and profile options in the preceding tables, perform steps 2 through 5.
2.
In the Responsibility field of the Find System Profile Values window, enter the appropriate responsibility, such as Inventory, Vision Enterprises. In the Profile Name field of the Find System Profile Values window, enter the Profile Value and click the Find button.
3.
4.
Enter the appropriate value at the Responsibility level (and Site level where required). Save.
5.
Tracking When an item is Oracle Asset Tracking trackable, any activity for that item passes a message to Oracle Asset Tracking for tracking. You perform the task of making an item trackable by both Oracle Installed Base and Oracle Asset Tracking in Oracle Inventory, as follows: When you define a master item, then, to make the item trackable, check the Track in Installed Base check box on the Service tab.
You must define the item as trackable at the master organization level only. Items become Installed Base trackable (and Asset Tracking trackable) across all organizations. Do not change this item attribute at the organization level.
Additional Tracking Considerations The Installed Base tracking attribute of an item cannot be changed when on-hand quantity is greater than zero. Attribute changes are not applied to pre-existing transactions in the Oracle Asset Tracking record. If you change the tracking attribute of an item from No to Yes, transactions that occurred before the change have no record in Oracle Asset Tracking. If you change the tracking attribute of an item from Yes to No, Oracle Asset Tracking no longer processes the pre-existing transactions. Depreciable Items Items that are trackable by Asset Tracking are defined as either normal or depreciable items. The difference between normal and depreciable items is in the way that assets can be created from the items. For a normal item, the asset is created after an item is put in service. For a depreciable item, the asset is created when an item is received, either in Oracle Inventory or Oracle Projects. For a depreciable item, you must define the item as depreciable at the master organization level only. Do not change this item attribute at the organization level. For more details, see Define Depreciable Items, page 2-13. Serial Number Control You must designate serial number control for the trackable items at the master organization level. This ensures that serial number control for an item is the same across all inventory organizations. Do not change this item attribute at the organization level. You specify serial number control in the Inventory tab. Do not change serial control for an item after transactions have been entered. Additional Serial Number Control Considerations In Oracle Inventory, you may enter a miscellaneous issue transaction to remove all on-hand inventory, change the serial control attribute, then enter a miscellaneous receipt to restore the on-hand quantities. During the process of correcting on-hand quantities, items that already have transactions are not affected. As a result records in Oracle Asset Tracking do not show the change in the serial control attribute. General Oracle Inventory Considerations In addition, follow these restriction guidelines when setting up Oracle Inventory: Define all Oracle Asset Tracking items as inventory items (Inventory tab). If the Inventory Item check box is not marked, you cannot store or move the item. Enable Inventory Asset and Costing Enabled attributes for all items in Oracle Asset Tracking (Costing tab). These attributes let you enter and maintain costs for the items.
Do not modify the Oracle Account Generator logic for deriving the depreciation expense account. The depreciation expense account is derived from the book type (corporate or tax) and the asset category. Oracle Asset Tracking assumes that the depreciation expense account remains unchanged as a result of subinventory or inter-organization transfers.
Define Organization Classifications Oracle Asset Tracking tracks those inventory items which you have defined for Asset Tracking tracking. Each module that interacts with Oracle Asset Tracking passes messages that contain specific information for all items that are marked as Asset Tracking-tracking. For these messages to be sent and received successfully, the organizations you define must have the following classifications: HR Organization Use to associate employees, such as buyers and planners, with items within the organization. Inventory Organization Use to define, maintain, transact, and have on-hand balances for item numbers. Project Expenditure/Event Organization and Project Task Owning Organization Allows Oracle Inventory to associate items assigned to project and tasks to a project clearing account, which collects the cost of that assigned material. Use to monitor the expenditures for a project and task by reviewing the account through Oracle Projects. You use capital projects to collect construction-in-process (CIP) and expensed costs for assets you are building. When you are ready to place the asset in service, you generate asset lines from the CIP costs in Oracle Projects. You can send these lines to Oracle Assets to become depreciable, fixed assets. Therefore allow entry of capital project in your organization and issue material to the Capital Projects only. You must specify any additional classifications you need for your organization.
Prerequisites
You must define your organizations when you set up Oracle Inventory before you can define the organization parameters.
In the Inventory responsibility, navigate to Setup. Select Organizations and then select Parameters. In the Organization Parameters window, click the Inventory Parameters tab and enter:
1. 2.
2.
The Move Order Timeout Period The Move Order Timeout Action
3. 4.
Click the Costing Information tab and check Project Cost Collection Enabled. Click the Other Accounts tab and enter the organization's Project Clearing Account number. Save.
5.
Inventory
Check on Project
Inventory
You do not have to use the transaction type names as shown in the table. However, you must specify the source type and action as shown and select the Project check box for each of the transaction types required for Oracle Asset Tracking.
Using the Inventory responsibility, navigate to Setup. Select Transactions and then select Types. In the Transaction Types window, click the User tab. Enter name, source type, action, and check box. Save.
2. 3. 4.
In the Inventory responsibility, navigate to Items and then select Master Items. In the Master Item window, enter the appropriate information into the header region of the window. Click the Inventory tab. Check Inventory Item. Stockable and Transactable are checked by default.
3. 4.
5. 6.
Select the Service tab and check Track in Installed Base. Enter or select information in the remaining fields of the window.
7.
Save.
In the Inventory responsibility, navigate to Items and then select Master Items. In the Master Item window, enter the appropriate information into the header region of the window. Click the Inventory tab. Check Inventory Item. Stockable and Transactable are checked by default.
3. 4.
5. 6.
Select the Service tab and check Installed Base Tracking. Choose Create Depreciable Inventory Asset from the list of values of the Asset Creation field. Enter or select information in the remaining fields of the window. Save.
7. 8.
In the Inventory responsibility, navigate to Accounting Close Cycle and then select Inventory Accounting Periods. In the Inventory Accounting Periods window, in the first Period region, enter the current period. Save.
Note: This is a standard setup step in Oracle Inventory. For more
2.
3.
This modification ensures that the project clearing account used in the organization matches the credit account generated by auto-accounting for receipt transactions.
In addition, be aware of the following restrictions when setting up Oracle Purchasing: Set the match approval level to at least three-way matching. Oracle Asset Tracking uses purchase order and invoice data to determine and adjust costs. Three-way matching ensures that the purchase order quantity, the receipt quantity, and the invoice quantity all match. You can also set the match approval level higher, to four-way matching. If your organization's default matching method is less than three-way, update the matching level setting on the purchase order itself. Assign an asset category to Asset Tracking tracking items. The asset category must not be an expense category and must belong to the same Assets book as the book used by the Profile Option CSE: FA Book Type Code. For details of setting up the profile options, see Define System Profile Options for Oracle Asset Tracking, page 2-4.
Note: For details on Oracle Purchasing setup steps, please refer to
The Accrual at Period End flow is not supported in Release 12 by Oracle Asset Tracking. It is replaced by the Receipt Accrual flow. The Subledger Architecture updates introduced in Release 12 change the way accounts are derived by the Generate Asset Lines PA process. Oracle Asset Tracking uses this purchasing item attribute to derive the asset category it uses when it creates asset records. Set control of this attribute at the master organization level so that the asset category for an item is the same across all inventory organizations.
In the Payables responsibility, navigate to Setup. Select Options and then select Financials.
2. 3.
In the Financials Options window, click the Supplier - Entry tab. Set the Invoice Match Option to Purchase Order.
In the CRL 11i Projects responsibility, navigate to Projects. Select Setup, Flexfields, Descriptive, and then Segments. In the Descriptive Flexfield Segments window, create the descriptive flexfield for the application Oracle Projects with the title Expenditure Items. Click Segments. Refer to the following table to define the five segments in the flexfield.
2.
3. 4.
Segments in the Expenditure Items Flexfield Name Item Number Window Prompt Item Number Column ATTRIBUTE6 Value Set 50 chars (no validation) 50 chars (no validation) 50 chars (no validation) 50 chars (no validation) 50 chars (no validation)
Serial Number
Serial Number
ATTRIBUTE7
Category
Category
ATTRIBUTE8
Location
Location
ATTRIBUTE9
Product Classification
Product Classification
ATTRIBUTE10
5. 6.
Select the Displayed check box for all five segments in the flexfield. Save the data you have entered, then close the Segments Summary - Global Data Elements window. Back in the Descriptive Flexfield Segments window, select the check box Freeze Flexfield Definition. Click Compile.
Note: In a subsequent step of setting up asset creation grouping
7.
8.
methods, the asset creation options GROUPING ELEMENT1, GROUPING ELEMENT2, and GROUPING ELEMENT3 correspond respectively to the columns ATTRIBUTE8, ATTRIBUTE9, AND ATTRIBUTE10 defined in the Expenditure Items descriptive flexfield. See Set Up Asset Creation Grouping Methods for Project Expenditure Items, page 2-18.
In the CRL 11i Projects responsibility, select Asset Creation. The Asset Naming Convention window appears, with the window divided into several regions, and fields in each region.
Note: The region Define Asset Description contains three fields.
2.
In the Asset Naming Convention window, use the lists of values to select the option values for each region name, as shown in the following table:
Define Asset Creation Region Name Define Asset Name Define Asset Description Option Value Task Name Grouping Element1 Grouping Element2 Task Name Grouping Element2 Grouping Element1
Location Category
must correspond with attribute 8, 9, or 10, depending on which attribute was chosen to indicate location and category in the system-level descriptive flexfield setup. See Define a Descriptive Flexfield for Expenditure Items, page 2-16.
3.
Save.
Oracle Projects Setup and Implementation in the Oracle Projects Fundamentals and Oracle Projects Implementation Guide.
Asset generation will only be done for projects with project types that have Override Asset Assignment checked. Make sure that the PO Receipt transaction/Inventory Issue to Project transaction is accounted in the Subledger Architecture. If not then run the Create Accounting SLA concurrent program in a responsibility with respect to the application context. The employee tied to the user running the Create Asset Headers in Oracle Projects Normal Items process should be listed as the Key Member in the project definition. Two function security, menu entries should be included in the menu where the Oracle Asset Tracking concurrent request Create Asset Headers in Oracle Projects Normal Items is scheduled to run (if not already defined):
Activity Management Gateway: Add Project Asset Activity Management Gateway: Add Asset Assignment
Define Group Asset and Super Group Key Flexfields Application Oracle Assets Oracle Assets Key Flexfield Group Asset Super Group Suggested Segment Values (1) City, (2) Network Element (1) Region, (2) Product Line
In addition, be aware of the following: Do not change or delete the link between the deliver-to and asset location once an asset has been created. Use the Locations form in Oracle Asset Tracking to initially link deliver-to and asset location. After this initial link is created, changing or deleting the link could corrupt the asset record. When assets are created through Oracle Asset Tracking, the asset key flexfield value is null. If you want Oracle Asset Tracking to automatically populate this value, you must customize the application. All assets must be related to an asset category. The Asset category will drive the depreciable for the asset.
The Oracle Assets book type is designated by the profile option CSE: FA Book Type Code. When you define Asset Groups you are required to define the depreciation method you will only find methods which have a calculation method of Flat Rate.
The setup steps required for Oracle Asset Tracking that are performed in Oracle Installed Base are: Define HZ Locations, page 2-21 Associate HR and HZ Locations to Asset Locations, page 2-22 Set the Freeze Install Parameter, page 2-22
Defining HZ Locations
Oracle Asset Tracking has the ability to correlate HR locations to HZ locations. HR locations are inventory locations used to receive material. HZ locations are used to deploy equipment in the field. You need to establish the link between HR locations and HZ locations in order to perform automatic financial updates when material movements occur. After you have defined asset locations, you must define HZ locations.
Prerequisites
You must have defined organizations in Oracle Inventory. You must have set up the profile options for Oracle Inventory and Oracle Assets. For details, see Define System Profile Options for All Dependent Responsibilities, page 2-4. You must have set up asset locations in Oracle Assets. For more information, see the Oracle Assets User Guide.
To define HZ locations:
1.
In the Oracle Installed Base responsibility, choose Setups and then select Maintain Locations. Enter complete address in HZ location setup window. Enter the description of the HZ location. Enter the HZ location code. Save.
2. 3. 4. 5.
Prerequisites
HR and HZ locations must be defined.
In the Oracle Installed Base responsibility, choose Setups and then select Asset Location Setup. Select location source as HR or HZ. Choose location code from the list of values. Assign Asset location. Enter active start date. You can disable the particular relationship by entering active end date. Save.
2. 3. 4. 5. 6. 7.
In the Oracle Installed Base responsibility, navigate to Setups and then select Install Parameters.
2.
Define an inventory location with all the subinventories including staging subinventory. Assign an asset location to the inventory location. This is done in the Oracle Installed Base Asset Locations window.
2.
Populate the Install Base Open Interface Instance Attributes and Asset Link Interface (CSI_I_ASSET_INTERFACE). You can do this with a PL/SQL program or by using a SQL*Loader script.
2.
3
Oracle Asset Tracking Administration
This chapter covers the following topics: Administering Oracle Asset Tracking Bypassing the Service Fulfillment Queue
Understanding the Message Dequeuer A message dequeuer is a background process that continuously polls a queue and
processes items from the queue. The message dequeuer removes messages from the message queue on a first-in, first-out (FIFO) basis. Message queues are maintained by Oracle Advanced Queueing (OAQ). For information about message queues, see the following topics in theOracle Service Fulfillment Manager Concepts and Procedures guide: Messaging in Oracle Service Fulfillment Manager Managing the System Queues
You can manage the message queues in either Oracle Service Fulfillment Manager or Oracle Number Portability. Oracle Asset Tracking uses the messaging system that is maintained in Service Delivery Platform (SDP). When you start a message queue, a controller process automatically starts the dequeuers. For more information about starting and suspending a message queue, see the following topics in the Oracle Service Fulfillment Manager Concepts and Procedures guide: Oracle SDP Start Oracle SDP Stop
Before starting the transaction make sure that the Service Fulfillment Manager queue is running. To do that, perform the following steps:
1. 2. 3.
Change the responsibility to SFM System Administrator. Navigate to Concurrent and then select Administer Manager. Make sure SFM Event Manager Queue Service is running.
This profile option indicates the processing control for transacting items. Available values for transaction items are shown in the following table:
Available Values for Transaction Items Processing Online processing Description Processes transactions while you wait, and control is returned once transaction processing is completed. Upon commit, control returns immediately to you, allowing you to processing and continue working. The transactions are executed on a periodic basis. Upon commit, Oracle Inventory spawns the concurrent process and returns control immediately to you, allowing you to continue working. Displays the concurrent request number of the concurrent process executing the transaction. Form level processing Processes transactions using the processing control option you choose for that particular type of transaction. You must also set the Oracle Inventory profile options for Inter Organization Transfer, Miscellaneous Issue and Receipt, Receive Customer Return, Return to Customer, and Transfer Between Subinventories.
Background Processing
The value you choose for this profile overrides values you set for individual transaction profiles unless you choose Form level processing. Oracle Inventory predefines a value of Immediate concurrent processing for this profile for all levels upon installation. You can update this profile at all levels. For more information please refer to the Inventory Profile Options section in the Oracle Inventory User's Guide.
4
Oracle Asset Tracking API
This chapter covers the following topics: Overview of the Oracle Asset Tracking API Oracle Asset Tracking Public Package Contents of Package CSE_DEPLOYMENT_GRP
This package contains the procedure PROCESS_TRANSACTION, which can perform the deployment transactions that are listed in the following table:
Name Install
Description The prerequisite is that you must have an instance with the operational status code In-Process/Not Used for the item you are trying to install. This procedure creates/updates the item instance with the operational status Installed, location type code from Project/Internal Site to HZ_locations. If there is an existing instance with operational status code Installed, then it updates the same or otherwise it will create a new instance.
Un-Install
The prerequisite is that you must have an instance with the operational status code Installed for the item you are trying to uninstall. This procedure updates the item instance with operational status code Not Used, location type code from HZ_locations to Project.
Put in Service
The prerequisite is that you must have an instance with the operational status code Installed for the item you are trying to put into service. This procedure creates/updates the item instance with operational status code In-Service. If there is an existing instance with operational status code In-Service, then it updates the same or otherwise it will create a new instance. This procedure creates expenditure items in the projects interface table. The installed base transaction created by this action will be used to create a project asset for Normal Items.
Description The prerequisite is that you must have an instance with the operational status code In-Service for the item you are trying to put out of service. This procedure creates/updates the item instance with operational status code Out-of-Service. If there is an existing instance with operational status code Out-of-Service, then it updates the same or otherwise it will create a new instance.
Move
The prerequisite is that you must have an instance with the operational status code Out-of-Service for the item you are trying to move. This procedure creates/updates the network location of the item instance with operational status code Out-of-Service. If there is an existing instance with operational status code Out-of-Service, network location as From Network Location, then it updates the network location with To Network Location or otherwise it will create a new instance with usage code Out-of-Service, network location as To Network Location. The installed base transaction created by this action will be used to interface move transactions to Oracle Fixed Assets.
Project Transfer
The prerequisite is that project transfer cannot be done for items that are already put in service. This procedure transfer items that are received into a project location to another project location. Item instances that are just received in to project or Installed in a location can be transferred.
Name Retirement
Description This procedure manually retires items that are capitalized. You can retire an item instance operationally (the instance is expired), or both operationally and functionally (the corresponding fixed asset is also retired from the books).
p_dest_location_tbl
cse_deployment_grp.dest_location _tbl
Yes
Parameter p_ext_attrib_values_tbl
Required Yes
Description This PL/SQL structure contains any references to extended attribute values that require an update along with the instance update. This PL/SQL structure holds the transaction action type and the transaction reference data that needed to be populated in install base transactions.
p_txn_tbl
cse_deployment_grp.transaction_t bl
Yes
The following table describes the OUT parameters associated with this API.
OUT Parameters: Parameter x_return_status Data Type VARCHAR2 Description Returns the status of the transaction: FND_API.G_RET_STS_SUCCESS - successful FND_API.G_RET_STS_ERROR - error FND_API.G_RET_STS_UNEXP_ERROR unexpected error x_error_msg VARCHAR2 The error message
Sample Code
Project Transfer
set serverout on declare l_location_type_code l_location_id l_instance_usage_code l_operational_status_code varchar2(30); number; varchar2(30); varchar2(30);
l_instance_tbl cse_deployment_grp.txn_instances_tbl; l_dest_location_tbl cse_deployment_grp.dest_location_tbl; l_ext_attrib_values_tbl cse_deployment_grp.txn_ext_attrib_values_tbl; l_txn_tbl cse_deployment_grp.transaction_tbl; l_return_status varchar2(1) := fnd_api.g_ret_sts_success; l_error_message varchar2(2000); begin l_instance_tbl(1).instance_id := 1302711;
select serial_number, lot_number, inventory_item_id, operational_status_code, location_type_code, location_id, instance_usage_code, operational_status_code into l_instance_tbl(1).serial_number, l_instance_tbl(1).lot_number, l_instance_tbl(1).inventory_item_id, l_instance_tbl(1).operational_status_code, l_location_type_code, l_location_id, l_instance_usage_code, l_operational_status_code from csi_item_instances where instance_id = l_instance_tbl(1).instance_id; IF l_location_type_code = 'PROJECT' THEN l_instance_tbl(1).last_pa_project_id l_instance_tbl(1).last_pa_project_task_id ELSE l_instance_tbl(1).last_pa_project_id l_instance_tbl(1).last_pa_project_task_id END IF; l_txn_tbl(1).transaction_id l_txn_tbl(1).transaction_date l_txn_tbl(1).source_transaction_date l_txn_tbl(1).transaction_type_id l_txn_tbl(1).txn_sub_type_id l_txn_tbl(1).source_group_ref_id l_txn_tbl(1).source_group_ref l_txn_tbl(1).source_header_ref_id l_txn_tbl(1).source_header_ref l_txn_tbl(1).transacted_by l_txn_tbl(1).transaction_quantity l_txn_tbl(1).operational_flag l_txn_tbl(1).financial_flag := := := := := := := := := := := := := := 5773; := 248906; := 5773; := 248906; fnd_api.g_miss_num; sysdate; sysdate; 152; 3; fnd_api.g_miss_num; fnd_api.g_miss_char; fnd_api.g_miss_num; fnd_api.g_miss_char; fnd_api.g_miss_num; 1; 'Y'; 'Y';
l_dest_location_tbl(1).parent_tbl_index := 1; l_dest_location_tbl(1).location_type_code := l_location_type_code; l_dest_location_tbl(1).location_id := l_location_id; l_dest_location_tbl(1).instance_usage_code := l_instance_usage_code; l_dest_location_tbl(1).operational_status_code := l_operational_status_code; IF l_location_type_code = 'PROJECT' THEN l_dest_location_tbl(1).pa_project_id l_dest_location_tbl(1).pa_project_task_id l_dest_location_tbl(1).last_pa_project_id fnd_api.g_miss_num; l_dest_location_tbl(1).last_pa_project_task_id fnd_api.g_miss_num; ELSE l_dest_location_tbl(1).last_pa_project_id l_dest_location_tbl(1).last_pa_project_task_id l_dest_location_tbl(1).pa_project_id fnd_api.g_miss_num; l_dest_location_tbl(1).pa_project_task_id fnd_api.g_miss_num; END IF; := 8093; := 249903; := := := 8093; := 249903; := :=
cse_deployment_grp.process_transaction ( p_instance_tbl => l_instance_tbl, p_dest_location_tbl => l_dest_location_tbl, p_ext_attrib_values_tbl => l_ext_attrib_values_tbl, p_txn_tbl => l_txn_tbl, x_return_status => l_return_status, x_error_msg => l_error_message); if l_return_status <> fnd_api.g_ret_sts_success then dbms_output.put_line(l_error_message); end if; end; /
Asset Retirement
set serverout on declare l_instance_tbl cse_deployment_grp.txn_instances_tbl; l_dest_location_tbl cse_deployment_grp.dest_location_tbl; l_ext_attrib_values_tbl cse_deployment_grp.txn_ext_attrib_values_tbl; l_txn_tbl cse_deployment_grp.transaction_tbl; l_return_status varchar2(1) := fnd_api.g_ret_sts_success; l_error_message varchar2(2000); begin l_instance_tbl(1).instance_id l_instance_tbl(1).asset_id := 1605848; := 108431;
select serial_number, inventory_item_id, operational_status_code into l_instance_tbl(1).serial_number, l_instance_tbl(1).inventory_item_id, l_instance_tbl(1).operational_status_code from csi_item_instances where instance_id = l_instance_tbl(1).instance_id; l_instance_tbl(1).lot_number l_instance_tbl(1).inventory_revision l_instance_tbl(1).last_pa_project_id l_instance_tbl(1).last_pa_project_task_id l_instance_tbl(1).unit_of_measure l_instance_tbl(1).active_start_date l_instance_tbl(1).active_end_date l_instance_tbl(1).instance_status_id l_txn_tbl(1).transaction_id l_txn_tbl(1).transaction_date l_txn_tbl(1).source_transaction_date l_txn_tbl(1).transaction_type_id l_txn_tbl(1).txn_sub_type_id l_txn_tbl(1).source_group_ref_id l_txn_tbl(1).source_group_ref l_txn_tbl(1).source_header_ref_id l_txn_tbl(1).source_header_ref l_txn_tbl(1).transacted_by l_txn_tbl(1).transaction_quantity l_txn_tbl(1).proceeds_of_sale l_txn_tbl(1).cost_of_removal -- use this flag to expire the item instance l_txn_tbl(1).operational_flag -- use this flag to retire the fixed asset l_txn_tbl(1).financial_flag := := := := := := := := := := := := := := := := := := := := := fnd_api.g_miss_char; fnd_api.g_miss_char; fnd_api.g_miss_num; fnd_api.g_miss_num; fnd_api.g_miss_char; fnd_api.g_miss_date; fnd_api.g_miss_date; fnd_api.g_miss_num; fnd_api.g_miss_num; sysdate; sysdate; 104; fnd_api.g_miss_num; fnd_api.g_miss_num; fnd_api.g_miss_char; fnd_api.g_miss_num; fnd_api.g_miss_char; fnd_api.g_miss_num; 1; 10; 10;
:= 'Y'; := 'Y';
cse_deployment_grp.process_transaction ( p_instance_tbl => l_instance_tbl, p_dest_location_tbl => l_dest_location_tbl, p_ext_attrib_values_tbl => l_ext_attrib_values_tbl, p_txn_tbl => l_txn_tbl, x_return_status => l_return_status, x_error_msg => l_error_message);