$START_PERIODKEY$ uses calendar dates, not fiscal.

Summary:

We use a fiscal calendar in Global Period Mapping, and the Period Key is derived from that fiscal calendar. ARCS is integrated with Oracle ERP reports executed via ESS jobs, where the Period parameter is supplied through $START_PERIODKEY$. Report inputs vary—some require a yyyy-mm-dd date, while others require MMM-YY.Our October fiscal period ends on 2025-11-01. When the parameter format is MMM-YY, $START_PERIODKEY$ resolves to NOV-25, but it should resolve to OCT-25 to align with our fiscal period.What’s the correct approach to make $START_PERIODKEY$ evaluate to the fiscal period name (e.g., OCT-25) in these cases? If $START_PERIODKEY$ isn’t suitable, is there