OAT is Passing Sysdate as In-Service Date To Projects Instead of Deployment Date. (Doc ID 1383369.1)

Last updated on SEPTEMBER 11, 2015

Applies to:

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

Symptoms


ACTUAL BEHAVIOR
---------------
In-Service dates entered in OAT are not being sent to Projects (PA). Regardless of what In-Service date was populated in OAT, the sysdate flows through to the Project Asset Header in PA.

EXPECTED BEHAVIOR
-----------------------
Want the In-Service date in Projects to match the what was entered as the In-Service date in OAT.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:


1. Run the 'Interface In-Service Items to Oracle Projects' concurrent process

2. Run the 'Transaction Import for PO Receipts in Projects' concurrent process

2. Run the 'Create Asset Headers in Oracle Projects - Normal Items' concurrent process

3. View the asset header in Projects and the In-service date is the sysdate

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms