Enterprise Service Automation (ESA) - PSFT (MOSC)

MOSC Banner

F&A continues to run against old rows in proj_resource

edited Sep 5, 2014 8:21AM in Enterprise Service Automation (ESA) - PSFT (MOSC) 4 commentsAnswered ✓

We are on 9.1 and currently testing bundles 23-30. As of these bundles we are running into an issue where it looks like F&A is running nightly against old rows in proj resource that are not allowed F&A (FA_STATUS = 'N'). Either they not allowed by sponsor agreement or the particular account is not on the GM_FA_BASE TREE under a node that allows F&A charges. Although it doesn't appear to be doing anything with F&A charges, the DTTM_STAMP keeps getting updated to the current date. We use this date for many reports and it is really throwing them out of

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center