Mapped PO/Actual records sit inside a specific FY hierarchy. If newer FYs are empty while older ones have data, your import pipeline likely paused.
What this answers:
- Why mapped PO/Actual records appear on older fiscal years but not newer ones
- How the relationship between FY hierarchies and imports actually works
- How to confirm whether imports are still running and what to do if they're not
How it actually works
Each fiscal-year hierarchy in Allocadia (e.g. AOP — FY24, AOP — FY25) is its own container. Mapped PO and Actual records belong to a specific FY hierarchy — they are not carried forward year over year.
What does get carried forward during your annual rollover is the mapping configuration itself — the rules that tell Allocadia how to match an incoming record to a line item. The Uptempo team handles that mapping carry-forward as part of rollover, so from your side it should feel seamless year over year as long as imports are still running.
The most common cause when newer FYs are empty
If you see mapped PO/Actual data on older fiscal years (FY19, FY20, FY21) but nothing on the newer ones, the most likely explanation is that imports paused at some point and haven't been running into the newer FY hierarchies since.
Common patterns:
- Imports paused after a specific fiscal year. The upstream system feeding POs and Actuals to Allocadia (your ERP, accounting tool, or procurement platform) stopped sending data, or the integration was reconfigured and never re-pointed at the newer hierarchies.
- Imports are running but landing somewhere else. Data is going to a parallel hierarchy or a different folder than the one you're looking at.
- The new FY hierarchy was never enabled for imports. A new hierarchy was stood up but its import setup was never completed, so no records can land there.
What to check first
- Confirm with the team that owns the upstream feed that data is still being sent to Allocadia. Often this is the person who set up the SFTP or integration originally — they'll know whether the pipeline is alive.
- Look at the most recent successful import run in your scheduled imports. If the last successful run is more than a year old, the pipeline has stopped — that's the cause.
- Open one of the new FY hierarchies and check the Imports view for any failed or paused schedules.
What to do next
If imports paused some time ago and you want to resume them for your current fiscal years, this typically requires a Professional Services engagement to redo the initial setup. PS handles the import configuration for the new FY hierarchies, and Support takes incremental adjustments from there.
Contact Support and let your CSM know — they'll coordinate the scoping with the right team.
If imports are running but data isn't landing where you expect, that's a routing question Support can help diagnose directly. Share the schedule name, the date of the most recent run, and the hierarchy where you expected the records to land.
Comments
Please sign in to leave a comment.