My Oracle Support Banner

Member Asset Unplanned Depreciation with Allocate Tracing Is Getting Posting To GL Twice (Doc ID 2085261.1)

Last updated on NOVEMBER 08, 2022

Applies to:

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

Symptoms

 

Find when processing Unplanned Depreciation on Member Asset with Member Asset tracking (Allocate Tracking) find:

transactions are created on both member and group asset:

Member get the Member Tracking record in FA_ADJUSTMENTS (since reserve is not stored at member level)
+ Group gets regular unplanned entry to FA_ADJUSTMENTS

For BOTH SLA is getting GL Transfer = Y thus duplicating in the GL.

EXPECTED BEHAVIOR
-----------------------
Event on Member Asset for the Member Tracking record should be non-accountable in SLA and NOT transferred to GL

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Unplanned at Member Level on book with Member Asset Tracking
2. Run Create Accounting



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
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.