Invoice Price Variance (IPV) For a Serialized To

Normal Item (Doc ID 1555771.1) Bottom

Modified:May 28, 2013 Type:BULLETIN

In this Document

Purpose
Scope
Details
Test Case Overview
Test Case Pre-requisites
Test Case Steps
Step 1: Create The Asset
CheckPoint
Step 2: Create an Invoice
Step 3: Create Accounting Entries
CheckPoint
Step 4: Interface Invoice Price Variance to Oracle Projects
CheckPoint
Step 5: Import IPV Transaction into Projects
CheckPoint
Step 6: Adjust Asset Cost in Projects
CheckPoint
Step 7: Interface Project Asset Line to Oracle Fixed Assets
CheckPoint
Step 8: Update Asset in Oracle Fixed Assets
CheckPoint
Further Reading
References

APPLIES TO:

Oracle Asset Tracking - Version 12.1.1 and later

Information in this document applies to any platform.

PURPOSE
To provide a test case example showing how to adjust the cost in Projects
and Fixed Assets for an asset created for a serialized normal item, which is
purchased from a supplier and received into a project task. It covers:

* Test Case Overview

* Test Case Pre-requisites
* Test Case Steps
* Further Reading

SCOPE

This article is intended for Asset Tracking implementers and/or Application

Administrators for R12.

DETAILS

Test Case Overview

The following test case shows how to adjust the cost in Projects and Fixed
Assets for an asset created for a serialized normal item. Using Oracle Asset
Tracking responsibility, Vision Operations will adjust the asset cost in Projects
and Fixed Assets by the IPV value. The test case will mainly cover the
following business flows:
Test Case Pre-requisites

Complete all mandatory setup steps as per Test Case: How to Complete
Mandatory Setups For Oracle Asset Tracking [ID 1550972.1]

Create a serialized normal item as per Test Case: How to Create a

Normal or Depreciable Item For Use in Oracle Asset Tracking [ID
1550969.1]

Test Case Steps

Instance: VISBDE07

Release: 12.1.3

User: operations
Step 1: Create The Asset

Create an asset for a serialized normal item as per Test Case: PO Receipt to
Project For a Serialized Normal Item [ID 1550645.1]

CheckPoint

(R) Asset Tracking Super User

(N) Assets > Item Instances

1) Instance number = 3438997 is created and linked to Asset Number

= 113917 as shown below:

2) Asset Number = 113917 has cost = 150 in Projects (same as cost PO cost)
as shown below:
2) Asset Number = 113917 has cost = 150 in Fixed Assets (same as cost PO
cost) as shown below:
1) 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.

2) For normal items, the adjustment is done first in Oracle Projects and
transfered to Fixed Assets.

Step 2: Create an Invoice

(R) Asset Tracking Super User

(N) Payables > Invoices > Entry > Invoices

Created and validated Invoice Number = 124 against PO Number = 6054

(same PO used to create the asset in Step1) as shown below:

1) The asset is created in Projects and Fixed Assets with cost = 150.
However, the invoice is created with Total Amount = 160.35 (PO Cost: 150 +
Tax: 10.35). The cost different of 10.35 has to be adjusted in Projects and
Fixed Assets.

2) In Oracle Payables, the invoice must be approved. In this environment,

invoice approval was not required. If invoice approval is required, then follow
the procedures as implemented in the environment to approve the invoice.

Step 3: Create Accounting Entries

(R) Asset Tracking Super User

(N) Payables > Invoices > Entry > Invoices

Open Invoice Number = 124, click on Actions button, then select 'Create
Accounting' checkbox as shown below:

Before interfacing the IPV adjustements to Oracle Projects, the transaction

has to be accounted by creating accounting entries so that 'Interface Invoice
Price Variance to Oracle Projects' can adjust the cost for the existing asset.

CheckPoint

1) 'Create Accounting' program complets successfully and 'Journal Import

Execution Report' shows the Payables Invoice of 160.35 has been processed
correctly (no errrors) and accounted as shown below:

Step 4: Interface Invoice Price Variance to Oracle Projects

(R) Asset Tracking Super User

(N) Request > Run

Run the Oracle Asset Tracking program 'Interface Invoice Price Variance to
Oracle Projects' for PO Number = 6054. This program basically takes the
various amounts from ap_invoice_distributions_all and finds all
expenditure_item IDs with same PO_DISTRICTION_ID, then creates invoice
price variance data in pa_transaction_interface_all.
CheckPoint

1) Program log shows po_distribution_id = 273850 has related_exp_item_id =

102957 and this expenditure_item_id will be adjusted by total IPV, freight
and tax amount = 10.35 (9.75 + .6 + 0) as shown below:

Inside API cse_ap_pa_pkg.process_ipv_to_pa

p_project_id : 5251
invoice dist record # 1
invoice_dist_id : 3430568
invoice_id : 214300
po_distribution_id : 273850
project_id : 5251
task_id : 137187
base_amount : 9.75
org_id : 204
Calling freight and tax
l_total_ipv_amount 9.75
l_total_ft_amount 0
l_total_amount 9.75
TOTAL ipv and freight and tax amount : 9.75
ap_code_combination_id : 12854
inventory_item_id : 212958
inventory_item : OAT_SRL_ITEM
organization : Seattle Manufacturing
project_number : IT Project 2
task_number : 1
vendor_id : 600
vendor_number : 5037
exp_ending_date : 05-MAY-13
ipv_ccid : 332053
Inside API cse_ap_pa_pkg.get_prorated_ei
invoiced_quantity : 1
base_ipv_amount : 9.75
unit_ipv_amount : 9.75
Project_id : 5251
Task id : 137187
Org Id : 204
Dist Id : 273850
Inside rcv cursor - open
Inside rcv cursor -fetch count 1
received expenditure record # 1
expenditure_stage : EI
expenditure_item_id : 102957
orig_transaction_ref : 3438997-124
attribute6 : OAT_SRL_ITEM
attribute7 : TC01
 not already prorated
remaining_quantity : 0
prorate_quantity : 1
Inside API cse_ap_pa_pkg.populate_pa_txn_intf
prorated invoice distributions. record # 1
invoice_distribution_id : 3430568
project_id : 5251
task_id : 137187
prorated_amount : 9.75
related_exp_item_id : 102957
orig_transaction_ref : EI-102957-3430568
Inside API cse_ipa_trans_pkg.populate_pa_interface
nl_pa_tbl.count : 1
updating ap_invoice_distributions_all.pa_addition_flag = Y
invoice dist record # 2
invoice_dist_id : 3430569
invoice_id : 214300
po_distribution_id : 273850
project_id : 5251
task_id : 137187
base_amount : .6
org_id : 204
Calling freight and tax
l_total_ipv_amount .6
l_total_ft_amount 0
l_total_amount .6
TOTAL ipv and freight and tax amount : .6
ap_code_combination_id : 12854
inventory_item_id : 212958
inventory_item : OAT_SRL_ITEM
organization : Seattle Manufacturing
project_number : IT Project 2
task_number : 1
vendor_id : 600
vendor_number : 5037
exp_ending_date : 05-MAY-13
ipv_ccid : 332053
Inside API cse_ap_pa_pkg.get_prorated_ei
invoiced_quantity : 1
base_ipv_amount : .6
unit_ipv_amount : .6
Project_id : 5251
Task id : 137187
Org Id : 204
Dist Id : 273850
Inside rcv cursor - open
Inside rcv cursor -fetch count 1
received expenditure record # 1
expenditure_stage : EI
expenditure_item_id : 102957
orig_transaction_ref : 3438997-124
attribute6 : OAT_SRL_ITEM
 attribute7 : TC01
not already prorated
remaining_quantity : 0
prorate_quantity : 1
Inside API cse_ap_pa_pkg.populate_pa_txn_intf
prorated invoice distributions. record # 1
invoice_distribution_id : 3430569
project_id : 5251
task_id : 137187
prorated_amount : .6
related_exp_item_id : 102957
orig_transaction_ref : EI-102957-3430569
Inside API cse_ipa_trans_pkg.populate_pa_interface
nl_pa_tbl.count : 1
updating ap_invoice_distributions_all.pa_addition_flag = Y
invoice dist record # 3
invoice_dist_id : 3430570
invoice_id : 214300
po_distribution_id : 273850
project_id : 5251
task_id : 137187
base_amount : 0
org_id : 204
Calling freight and tax
l_total_ipv_amount 0
l_total_ft_amount 0
l_total_amount 0
TOTAL ipv and freight and tax amount : 0

2) 2 records are inserted in PA_TRANSACTION_INTERFACE_ALL table identified

by ATTRIBUTE6 has the item number and ATTRIBUTE7 has the serial number.

select *
from PA_TRANSACTION_INTERFACE_ALL
where ATTRIBUTE6 = 'OAT_SRL_ITEM'
and ATTRIBUTE7 = 'TC01';

Result: 2 records are created with TRANSACTION_SOURCE =

'CSE_IPV_ADJUSTMENT', DOCUMENT_DISTIRBUTION_TYPE = 'NONREC_TAX', and
BURDENED_COST = 9.75 + 0.6 = 10.35

Step 5: Import IPV Transaction into Projects

(R) Asset Tracking Super User

(N) Request > Run

Ran 'PRC: Transaction Import' with parameter Transaction Source =

'CSE_IPV_ADJUSTMENT'. This program imports the IPV adjustment data from
PA interface table and creates new expenditure items in the projects
application for the same project and task specified in the purchase order
distribution.

CheckPoint

1) 'PRC: Transaction Import'' program output shows that Expenditure Groups

has been created as shown below:

2) New Expenditures are created for the IPV adjustment as shown below:

(R) Asset Tracking Super User

(N) Projects > Expenditures > Expenditure Inquiry > Projects

Searched for project = IT Project 2 and I could see the new expenditures
created as shown below:

3) The records in PA_TRANSACTION_INTERFACE_ALL are removed and 2 new

records are created in PA_EXPENDITURE_ITEMS_ALL table identified by
ATTRIBUTE6 has the item number and ATTRIBUTE7 has the serial number.

select *
from PA_TRANSACTION_INTERFACE_ALL
where ATTRIBUTE6 = 'OAT_SRL_ITEM'
and ATTRIBUTE7 = 'TC01';

Result: no record returned

select *
from PA_EXPENDITURE_ITEMS_ALL
where ATTRIBUTE6 = 'OAT_SRL_ITEM'
and ATTRIBUTE7 = 'TC01';

Result: 2 new records have been created with TRANSACTION_SOURCE =

'CSE_IPV_ADJUSTMENT', DOCUMENT_DISTIRBUTION_TYPE = 'NONREC_TAX', and
BURDENED_COST = 9.75 + 0.6 = 10.35

select *
from PA_COST_DISTRIBUTION_LINES_ALL
where EXPENDITURE_ITEM_ID in (102955,102956);

Result:2 new records are created to reflect the total IPV and Tax
amount of 10.35

Step 6: Adjust Asset Cost in Projects

(R) Asset Tracking Super User

(N) Request > Run

Run 'PRC: Generate Asset Lines for a Single Project'. This program ties the
new expenditure items for IPV adjustement to the existing asset header and
creates project asset line with the IPV value.

CheckPoint

1) 'PRC: Generate Asset Lines for a Single Project' program output shows that
Asset Line has been created under section "Capital Asset Lines Generated"
as shown below:

2) Total Asset cost is adjusted by the IPV value in Projects. Now, Asset has
Total Cost = 160.35 (Original Cost: 150 + IPV: 10.35) as shown below:

3) New Asset Line in Capital Project form.

(R) Asset Tracking Super User

(N) Projects > Capitalization > Capital Projects

Searched for project = IT Project 2 and I could see a new Asset Line with
Amount = 10.35 (IPV adjustment) has been created for Asset Name = Task 1-
125 as shown below:
 3) The asset record in pa_project_assets_all table is updated with new cost =
160.35, one new record is created in pa_project_asset_lines_all table, no
record in pa_reporting_exceptions:

select *
from pa_project_assets_all
where ATTRIBUTE6 = 'OAT_SRL_ITEM'
and ATTRIBUTE7 = 'TC01';

Result: 1 record returned with PROJECT_ASSET_ID = 2504,

CAPITALIZED_COST = 150, and CROUPED_CIP_COST = 160.35 (Asset Cost has
been afjusted in Project by the IPV value of 10.35)

select *
from pa_project_asset_lines_all
where project_asset_id = 2504;

Result: 1 new record is created with project_asset_line_id = 4481,

project_asset_line_detail_id = 4469, and current_asset_cost = 10.35

select *
from pa_project_asset_line_details
where project_asset_line_detail_id = 4469;

Result: 2 records are returned showing that this Asset Line has been
created for EXPENDITURE_ITEM_IDs = 104955 & 104956

Step 7: Interface Project Asset Line to Oracle Fixed Assets

(R) Asset Tracking Super User

(N) Request > Run

Run the Oracle Projects program 'PRC: Interface Assets to Oracle Assets'. This
program sends new asset lines to Oracle Assets to update the exesiting asset
in fixed assets. The process creates one mass addition line in Oracle Assets
for each asset line in Oracle Projects, assigning the asset information entered
for the CIP asset to the mass addition line in Oracle Assets.

CheckPoint
1) 'PRC: Interface Assets to Oracle Assets' program output shows Capital
Asset Name = Task 1-125 has been interfaced to Oracle Fixed Assets as
shown below:

2) 1 record is created in fa_mass_additions table

select *
from fa_mass_additions
where project_asset_line_id = 4481;

Result: 1 record returned with MASS_ADDITION_ID = 953111, ASSET_NUMBER

= NULL, FIXED_ASSETC_COST = 10.35, PAYABLES_COST = 10.35, QUEUE_NAME =
'ADD TO ASSET', ADD_TO_ASSET_ID = 113917

Step 8: Update Asset in Oracle Fixed Assets

(R) Asset Tracking Super User

(N) Fixed Assets > Mass Additions > Post Mass Additions

Run 'Post Mass Additions' program for Asset Book = 'OPS CORP' to create the
Asset in Oracle Fixed Asset as shown below:

CheckPoint

1) Post Mass Additions Report output shows Asset Number = 113917 has
been adjusted by 10.35 as shown below:

2) Total Asset cost is adjusted by the IPV value in Fixed Assets. Now, Asset
has Total Cost = 160.35 (Original Cost: 150 + IPV: 10.35) in Asset Workbench
as shown below:

(R) Asset Tracking Super User

(N) Fixed Assets > Assets > Asset Workbench