This chapter covers the following topics:
This topic group provides process-oriented, task-based procedures for using the application to perform essential business tasks.
Use the Submit Request window to request one of the following reports and concurrent processes in Oracle Asset Tracking:
When you request a report, Oracle Asset Tracking assigns a number to your request, runs the request, and stores the report. Use this procedure to view the report that you requested.
You must request a report and save the request ID number.
To view request results
Using the Asset Tracking Super User responsibility, navigate to Request and then select View.
In the Find window, click Specific Request, and enter the ID number of the report that you wish to view.
Click Find to retrieve the record.
Click View Output to see the report online.
If the report was completed with errors, then choose View Log to see a list of the errors that were encountered when your request was processed.
To print the report, in the Menu Bar choose Tools and then select Reprint.
Enter the number of copies to print, the printer, and the print style.
Save.
Use this procedure to generate a list of items that have been issued to projects but have never been placed in service.
To request an assumed loss rate report
Using the Asset Tracking Super User responsibility, navigate to Request and then select Run.
Choose to run a single report.
In the Name field, choose Assumed Loss Rate Report.
Choose either Detail or Summary report type.
The Detail type displays all individual transactions that meet your criteria. The Summary type provides only transaction totals.
In the Parameters window, enter any needed information in the fields to define your search.
If you leave all optional fields blank, then the search returns all records across all organizations in the format that you requested.
Task Number: Enter the task number to further limit your search results to those items that have been issued to a particular task for a project.
Project Number: To limit your search results to those items that have been issued to a specific project, enter the project number here.
Organization: To limit your results to a particular organization, enter that organization here.
Inventory Item: To limit your search results to records for a specific item, enter the item number here.
Click OK to close the Parameters window.
Click Submit when you have finished defining the report.
The application assigns an ID number to your request. Use the ID number to find your request in the View Request window.
Related Topics
Use this procedure to generate a bill of lading report, which displays the following:
Move order number
Transaction request date
Ship-to location name and address
Project number
Task number
Line item number
Item number
Item revision
Quantity requested and quantity shipped, both with totals for each item number
CLEI
Serial number
Vendor serial number
Follow these steps to generate a bill of lading.
Note: To print a bill of lading for a specific range of dates, enter a date in both the Data Required From and Data Required To fields. If you do not enter any dates in these fields, then the bill of lading report shows all move orders up to the system date.
If you enter a value for Task Number, then enter a corresponding Project Number.
To keep the report results to a manageable length, enter data for as many of the parameter fields as possible.
To request a bill of lading report
Using the Asset Tracking Super User responsibility, navigate to Request and then select Run.
Choose to run a single report.
In the Name field, choose Bill of Lading Report.
In the Parameters window, enter any necessary information in the fields to define your search.
If you leave all fields blank, then the report will include all move orders for the current day.
Move Order Number: To limit the report to a specific move order, enter that number here.
Organization Name: Limits the report to a specific organization.
Date From: To limits the report to all move orders generated from a specific date forward, enter that date here.
Date To: To limit the report to all move orders generated before a specific date, enter that date here.
Project Number: To limit the report to only those move orders for a specific project, enter that project number here.
Task Number: To limit the report to only those move orders for a particular project task, enter that task number here.
Location: To limit the report to only those move orders for a particular physical location, enter that location here.
Click OK to close the Parameters window.
Click Submit when you have finished defining the report.
The application assigns an ID number to your request. Use the ID number to find your request in the View Request form.
Related Topics
When assets are procured through Oracle Purchasing they are created with purchase order costs.
After the invoice is created, any cost difference must be adjusted in project accounting or fixed asset applications. For the depreciable items, the difference is adjusted in Oracle Assets. For non-depreciable items, the adjustment is done in Oracle Projects.
For both normal and depreciable items, in Oracle Payables, the invoice must be approved, and accounting must be created. Also you need to run an Oracle Payables concurrent program to interface the transaction to Oracle General Ledger before adjusting the invoice price variance.
You need to run a concurrent program to ensure that the construction cost of the project is as close to the actual cost as possible.
Two types of invoice price variance are available:
Invoice Price Variance in Oracle Projects
To adjust the cost from Oracle Payables, you must bring in invoice cost from Oracle Payables into Oracle Projects and then assign attributes to new expenditures. The steps are as follows:
Run the program Interface Invoice Price Variance to Oracle Projects. It creates invoice price variance data in project interface table.
Run the program PRC: Transaction Import. It creates expenditure lines for the invoice price variance amount in projects.
Run the program PRC: Generate Asset Lines.
Run the Oracle Assets request set Post Mass Additions for the category book.
Invoice Price Variance in Oracle Assets
To adjust the cost from Oracle Payables, bring the invoice cost from Oracle Payables into Oracle Assets, and then update the Mass Addition table. The steps are as follows:
Run the program Interface Invoice Price Variance to Oracle Assets.
Run the Oracle Assets request set Post Mass Additions for the category book.
The topics in this section are the following:
Running the Interface Invoice Price Variance to Oracle Assets Program
Running the Interface Invoice Price Variance to Oracle Projects Program
In Oracle Payables, first approve the invoice, then create accounting for the invoice.
Run the Oracle Payables program Payables Transfer to General Ledger.
To run the Interface Invoice Price Variance to Oracle Assets program
Using the Asset Tracking Super User responsibility, navigate to Request and then select Run.
Choose to run a single report.
In the Name field, choose Interface Invoice Price Variance to Oracle Assets program.
In the Parameters window, enter the parameters: PO Number, Inventory Item, Organization, Include Zero IPV.
Click OK to close the Parameters window.
Click Submit when you have finished defining the report.
The application assigns an ID number to your request. Use the ID number to find your request in the View Request window.
Related Topics
In Oracle Payables, first approve the invoice, then create accounting for the invoice.
Run the Oracle Payables program Payables Transfer to General Ledger.
To run the Interface Invoice Price Variance to Oracle Projects Program
Using the Asset Tracking Super User responsibility, navigate to Request and then select Run.
Choose to run a single report.
In the Name field, choose Interface Invoice Price Variance to Oracle Projects.
In the Parameters window, enter the parameters: Project Number, Task Number, Purchase Order Number, Inventory Item, and Organization.
Click OK to close the Parameters window.
Click Submit when you have finished defining the report.
The application assigns an ID number to your request. Use the ID number to find your request in the View Request window.
Related Topics
You can run the concurrent program Generate Notification - New Fixed Assets for Install Base Tracking, from the Asset Tracking Super User or Asset Tracking Planner responsibilities. This program generates a workflow notification for all the assets which may need an item instance created. If an asset is created in Oracle Assets and the source of the asset is not Oracle Asset Tracking, then running this program inserts a row in the staging table CSI_FA_TRANSACTIONS and generates a notification. Depending on the setup of Oracle Workflow, an email is sent to users associated to the seeded responsibilities, Asset Tracking Super User or Asset Tracking Planner. The Asset Tracking Planner responsibility has been created to simplify the process of generating and acting on the new assets workflow notifications.
Note: You can also view a notification from the Oracle Workflow worklist.
To run the Generate Notification - New Fixed Assets for Install Base Tracking program
From the Asset Tracking Super User responsibility, navigate to Request and then select Run.
Choose to run a single report.
In the Name field, choose Generate Notification - New Fixed Assets for Install Base Tracking.
Click Submit.
The application assigns an ID number to your request. Use the ID number to find your request in the View Request window.
Oracle Asset Tracking enables you to capitalize assets regardless whether they are in inventory. As depreciable assets move in and out of inventory, accounting entries are generated by the Cost Manager to update the associated inventory value. The Cost Manager has no way to identify these assets as capital assets. To prevent duplication, Oracle Asset Tracking uses the Create Reversal GL Entries for Inventory FA Items program to reverse the accounting entries made by the Cost Manager.
Following is a description of how the Create Reversal GL Entries for Inventory FA Items program works:
Finds unprocessed CSI transactions using the 1 value (Pending) of gl_interface_status_code column. (The CSI_TRANSACTIONS table stores all transactions related to Item Instances.)
If there are no unprocessed transactions, then the program ends.
Otherwise, it gets the corresponding MTL_MATERIAL_TRANSACTIONS (MMT) row for each unprocessed CSI transactions. For each inventory transaction of an item instance, a CSI_TRANSACTIONS row is created with the MMT transaction id as foreign key.
After the MMT record is found, checks to determine whether any item instances are capitalized item instances.
If there is none, the record is not processed.
Otherwise, it will process to find the corresponding SLA entries.
To ensure that there will be no other changes before proceeding any further with the SLA entries, the process looks for Final Mode SLA entries.
The amount to be reversed is computed using the following formula: (Ledger Amount / quantity in MMT)multiplied by the # of capitalized item instances .
The accounts used to generate reversal entries are the same as the original distribution entry which is being reversed.
Inserts reversal entries into GL_INTERFACE, to be posted in General Ledger later.
Sets the gl_interface_status_code of CSI_TRANSACTIONS to 2 (Posted). This ensures the transactions are not processed again the next time the program runs. If the program logic derives that the transaction does not need accounting reversal then the gl_adjustment_process_flag of CSI_TRANSACTIONS is updated to 3 (None). This typically is the case when the distributions are not transferable to general ledger as with some upgrade data.
Note: The process can be initiated any time. However, you must also run it after all your SLA entries have transferred to the GL, and before you close your period.
From the GL side, the Journal Import process can be run to create journal entries from the GL_INTERFACE records. After reviewing for validity, they can be posted to GL .
To run the Create Reversal GL Entries for Inventory FA Items program
From the Asset Tracking Super User responsibility, navigate to Request and then select Run.
Choose to run a single report.
In the Name field, choose Create Reversal GL Entries for Inventory FA Items.
Click Submit.
The application assigns an ID number to your request. Use the ID number to find your request in the View Request window.
In the Find Personal Profile Values window, you can search for the personal profile values that have already been defined in other Oracle applications. Then use the Personal Profile Values window to display and make changes to your personal settings. Do not enter user values unless you require a setting that is different from the default setting.
Follow these steps to find and edit personal profile values used in the Oracle Asset Tracking application.
Create profiles.
To find personal profile values
Using the Asset Tracking Super User responsibility, navigate to Setup and then select Profiles.
The Find Personal Profile Values window opens.
Click [...] to open the list of values.
The Organizations window appears.
Enter any partial search mask, if you want, in the Find field, and click Find.
The Profiles window displays the profiles for Oracle Asset Tracking.
Select the profile that you want to edit, and click OK.
The Find Personal Profile Values window displays the name of the selected profile.
Click Find.
The Personal Profile Values window opens and displays the selected profile.
Enter values in the User Value column to customize the user profile.
Save.