Enterprise Service Automation (ESA) - PSFT (MOSC)

MOSC Banner

In Express Capitalization, what is the recommended method of segregating transactions by fiscal year

edited Apr 17, 2019 1:17PM in Enterprise Service Automation (ESA) - PSFT (MOSC) 1 commentAnswered ✓

Hi:

Version info: 9.2.19, PeopleTools 8.54 and upgrading to PUM 30, PeopleTools 8.57 this year.

We have just configured Project Costing for Express Capitalization and are approaching the end of fiscal year 2019 (June 30, 2019). We need a procedure to prevent FY 2020 transactions from being capitalized during Express Capitalization prior to FY 2019 being closed. When express capitalization is run, it pulls all transactions with the specified analysis types regardless of transaction or accounting date. There is no date field available when defining Express Asset Filter Criteria (unless it is possible to add one).

Thus, if the process runs in August 2019 (which is in our FY 2020), it will pull in any new transactions for FY19 and FY20. Can this be controlled through delivered functionality? Perhaps by limiting cost collection to a specified accounting date so that FY20 costs are not collected until the modules are closed?

Tagged:

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

PSFT ESA Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center