R12 PRC: Update Project And Resource Base Summaries Ends with the Warning "The following periods were not found" Due to Need by Date on PO. (Doc ID 2021157.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Project Planning and Control - Version 12.1.3 and later
Information in this document applies to any platform.

Goal

PRC: Update Project And Resource Base Summaries Process Ends With Warning: "The following periods were not found."

The following returns 73 rows:

select p.segment1 "Project Number",
t.task_number "Task number",
EXPENDITURE_TYPE "Expenditure Type",
to_char(to_date(RECVR_GL_TIME_ID,'J'), 'YYYY/MM/DD') "GL date",
to_char(to_date(RECVR_PA_TIME_ID,'J'), 'YYYY/MM/DD') "PA date",
to_char(to_date(EXPENDITURE_ITEM_TIME_ID,'J'), 'YYYY/MM/DD') "EI date",
h2.name "Expenditure Organization",
PRJ_RAW_COST "Raw cost",
h1.name "Operating Unit",
DECODE (RECORD_TYPE, 'M', 'Commitment', 'A', 'Actual', 'Unknown')
"Cmt/Actual",
DECODE (CMT_RECORD_TYPE, 'I', 'Invoice','P','Purchase
Order','R','Requisition','O','Other','Unknown') "Transaction Type"
from PJI_FM_DNGL_FIN d, pa_projects_all p, pa_tasks t,
hr_all_organization_units h1, hr_all_organization_units h2
where p.PROJECT_ID=d.PROJECT_ID and
p.PROJECT_ID=t.PROJECT_ID and
t.TASK_ID=d.TASK_ID and
h1.organization_id=d.PROJECT_ORG_ID and
h2.organization_id=d.EXPENDITURE_ORGANIZATION_ID

The same rows appear to be returned in select * from PJI_FM_DNGL_FIN

The first script shows a gl date (need by date) in 2015 (future period) but the po tables shows GL_ENCUMBERED_DATE around the expenditure item date. The customer will not be defining the next calender year until AUG-15.

Why is the process using the PO's need by date for gl date? The customer does not use the need by date and wants to know how to point the process to look at a date other then the need by date. They want to know if there is a
setup or profile that we can set to ignore need by date

They need these items to properly summarize to properly report their current financial position. They are able to change the need by date manually, but that would require a lot of time and effort to change 73 POs.
 

Solution

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