R12 PAXTRAPE: Capitalizable Flag is not Set on Expenditures though Transaction Controls are in Place to Set Items to Non Capitalizable.

(Doc ID 2110253.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Project Costing - Version 12.2.4 and later
Oracle Project Foundation - Version 12.2.4 and later
Information in this document applies to any platform.

Symptoms

Transaction controls are set on a task on a capital project. The task is chargeable and billable, but the transaction control for certain expenditure types is chargeable and billable (capitalizable) is set to NO. When an expenditure batch is created in the pre-approved batch form, the new expenditure items are marked as capitalizable.

The customer does not use task start and end dates for Capital project tasks. When a new task is created and the transaction control is added to it, the effective start date (start_date_active) of the transaction control is the sys date.

Steps to reproduce:
.
1. Create a capital project with 1 task with no start and end date
2. Set the Transaction Control at the Task level with Category = Labor, Type = Professional, chargable checked and billable = NO. Sys Date = 10-FEB-2016.   This will be the task's transaction control effective start date.
3. Enter a pre-approved batch with an expenditure dated 09-FEB-2016 and 11-FEB-2016. Submit and Release
4. Go into the Expenditure Inquiry and note that the ei dated 09-FEB-2016 has a capitalizable flag = YES and the one dated 11-FEB-2016 has a capitalizable flag = NO

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