My Oracle Support Banner

Create Asset Program Passed Transaction_Date Instead Of Source_Transaction_Date To FA_MASS_ADDITIONS.date_placed_in_service (DPIS) (Doc ID 1494627.1)

Last updated on MARCH 08, 2019

Applies to:

Oracle Asset Tracking - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms



ACTUAL BEHAVIOR
---------------
After run Create Asset program fa_mass_additions.date_placed_in_service was updated with sysdate instead of the source_transaction_date
of "Misc Issue to Field Location" therefore Post Mass Addition program could not post this transaction to the current FA period.
For example: FA period is Jun-2012, the "Issue to Field Location" was create on 01-JUN-2012 (source_transaction_date) but run the create Asset program
on 18-AUG-2012 the fa_mass_additions.date_placed_in_service was entered as 18-AUG-2012.

EXPECTED BEHAVIOR
-----------------------
Expect the date_placed_in_service was entered as source_transaction_date (01-JUN-2012) of "Misc Issue to Field Location"

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
- Create "Mis issue to Field" Transaction, then Run Create Accounting-cost Management, after that
- Run "Crate Asset Interface Inventory Transactions to Oracle Asset" and then run Post Mass Addition

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.