Datamart Extraction Job Failed - No fiscal periods have been set up

Document ID : KB000023906
Last Modified Date : 03/01/2019
Show Technical Document Details
Issue:
The Datamart job is failing with following error (shown on the job log or shown in the background log file - bg-ca.log):

Microsoft SQL Server: 
NBI_CFG_NO_FISCAL_PERIOD - No fiscal periods have been set up SQL error code: 50000

Oracle: 
DMT-0005: No fiscal periods have been setup
Cause:

The fiscal time periods have to cover the maximum date of the daily resource time slice  IDs (1,2,3,10,11).
 

Resolution:

1. Run query:

SELECT 'TS MIN/MAX', MIN(FROM_DATE), MAX(TO_DATE)
FROM PRJ_BLB_SLICEREQUESTS
where id in (1,2,3,10,11)

Review the min and max dates.

2. Go to Administration > Finance > Setup > Entities > 
Select Entity > Fiscal Time Periods tab

1. Create monthly time periods that cover the time slice date range above..
2. Checkmark the created time periods.
3. At the top right-hand side of the page, click Action > Activate
4. Run the Datamart Extraction job to completion.
5. Run the Datamart Rollup job to completion.

Additional Information:

This issue also impacts the successful execution of the Datamart Rollup job and by configuring the Fiscal Periods, you will avoid the following errors.

Reference KB000022068 : Datamart Rollup Job Failed - Determine current fiscal period no data found

Reference KB000027098: Datamart Rollup Job Failed - Cannot insert the value NULL into column 'FISCAL_TIME_KEY' table

Reference KB000027098 : Why don't weekly fiscal periods appear in NBI_DIM_FISCAL_TIME table?