Hi Minh,

Thanks, that helps. We did some additional investigation. FISCAL_TIME_INTERVAL_ID appears to be the Workday WID for the fiscal time interval reference. For BUSINESS_PLAN_DETAIL, the corresponding readable interval code may already be available in the same table as either FISCAL_POSTING_INTERVAL_CODE or AWARD_POSTING_INTERVAL_CODE, depending on the interval type.

Could you check whether either of those fields is populated in your destination for the rows where FISCAL_TIME_INTERVAL_ID is present, and whether that gives your team the value they are looking for?

If you need additional attributes beyond the readable interval code, such as fiscal period start/end dates, fiscal schedule, fiscal year context, or period status, please share the exact fields needed so we can scope the enhancement correctly.

Thanks,
Tom

Hi Tom, 

Thanks for digging into this some more. Both of those fields have all null values on our side. We are just looking to see what that field means since the field '# YEAR' is the only time related field from that table, but it doesn't match with the `FISCAL_TIME_INTERVAL_ID`. So `FISCAL_POSTING_INTERVAL_CODE` should be the code value for `FISCAL_TIME_INTERVAL_ID`?

The support engineer from my previous said there is a lookup table that exists, but is not built, so we wanted the code version of what the interval means. Let me check with a team member on the other fields (fiscal period start/end dates, fiscal schedule, fiscal year context, or period status) you mentioned and I'll get back to you.

Hi Tom, 

Just spoke with my teammate. He needs the readable FISCAL_TIME_INTERVAL_ID and anything and everything related to that field if available. The goal is to build out a table with contains the budget for general ledger accounts. We do not have exact field names but yes to the fiscal period start/end dates, fiscal schedule, fiscal year context, or period status. Is there a list somewhere with available field/information that can be built? 

Hi Tom,

Do you know when this can be pulled out of the backlog and actively worked on? Roughly how long would that entire process take?

Thanks!

 Hi Minh, thanks for following up. We're still investigating the implementation path for this. The main complexity is that the Workday API for retrieving fiscal interval details requires us to enumerate inputs (company and fiscal year) first before we can call it, and the connector's current API version doesn't expose the fiscal year enumeration endpoint cleanly. We're also checking whether start/end dates for fiscal periods can be sourced from the same API or a separate one, since the primary endpoint we tested doesn't return those. I'll update this thread as soon as we have clarity on the approach - likely within the next 1 week.

Hi Tom, 

That does sound tricky. Thanks so much for the update! Looking forward to hearing your findings and if there is a workaround that is available. 

Hi Minh, thanks for your patience. A few questions to help us investigate further:

1. In your Workday FM destination, is FISCAL_POSTING_INTERVAL_CODE showing as NULL for all records in BUSINESS_PLAN_DETAIL? If so, can you check whether your Workday FM service account has permissions to read business plan data, and whether the field is populated in Workday itself?
2. Could you try a full re-sync of BUSINESS_PLAN_DETAIL? The column may have been added after your initial sync.
3. On the fiscal interval data itself - to confirm what you need: is the main requirement a readable label for FISCAL_TIME_INTERVAL_ID (e.g. JAN, FEB, MAR)? Or do you also need fiscal period start/end dates and schedule context? Asking because the API behaves differently for each - want to make sure we're scoping the right solution.

Hi Tom,

See my comments in the bullets below. 

1. In your Workday FM destination, is FISCAL_POSTING_INTERVAL_CODE showing as NULL for all records in BUSINESS_PLAN_DETAIL? If so, can you check whether your Workday FM service account has permissions to read business plan data, and whether the field is populated in Workday itself?

• Yes, the FM service account has permissions to read this data. The security domains have been added and tested with our Workday admin. I will have to reach out about the field being populated. 

2. Could you try a full re-sync of BUSINESS_PLAN_DETAIL? The column may have been added after your initial sync.

• I've ran a full re-sync of the business_plan_detail table and all the values are still null. 

3. On the fiscal interval data itself - to confirm what you need: is the main requirement a readable label for FISCAL_TIME_INTERVAL_ID (e.g. JAN, FEB, MAR)? Or do you also need fiscal period start/end dates and schedule context? Asking because the API behaves differently for each - want to make sure we're scoping the right solution.

• Thanks for providing context on the API. I would say yes to both - We are looking for a readable label for fiscal_time_interval_id and/or any fiscal period start/end dates. I know both month and period are relied on or will be asked for if not already. 
• However, if not feasible, the priority is a readable fiscal_time_interval_id. Whatever data is already more accessible and available.