Known Limitations
Hard stops, workarounds, and fix timelines — review before scoping
ReferencePre-Sales
🚨 Scope Review Required
Review every limitation in this table with the customer before scoping the engagement — not after. Hard-stop limitations (High severity with no workaround) must be resolved before proceeding to a Statement of Work.
Limitation Reference Table
| Limitation | Severity | Workaround | Fix Timeline |
|---|---|---|---|
| BYOK requirement (AWS) — Some customers require Bring Your Own Key encryption on public cloud. ADO requires AWS and cannot be deployed in private/sovereign environments. | High | None — ADO is an AWS-native service. Customer must be willing to use AWS-hosted ADO or IFP is not suitable. | No change planned |
| AWS dependency — Customers who cannot use AWS (public sector, federal, sovereign cloud) cannot use ADO and therefore cannot use IFP v2.0+. | High | None. This is a hard stop. Do not scope IFP for these customers. | No change planned |
| 8-dimension limit on Polaris models — The Polaris engine enforces a hard limit of 8 dimensions per model. Customers with complex dimensional structures may exceed this. | High | Reduce dimensions to fit within 8. Entity and Time always count. If customer requires >6 additional dimensions, IFP is not suitable. | No change planned near term |
| Top-Down disaggregation not available — Executive targets entered at L2 level cannot be automatically disaggregated to lower levels. Users must manually distribute targets. | Medium | Manual target distribution at each level. Plan extra configuration and training time for this workflow. | Planned for future release — no date confirmed |
| Finance Analyst / CoPlanner pending GA — Embedded but not yet fully released. Functionality is visible in the UX but behavior may change before GA. | Medium | Do not demo or scope Finance Analyst / CoPlanner features until GA is confirmed. Do not include in SOW scope. | GA planned — confirm current status with Apps team |
| CapEx entity-level only — Capital expense planning is at the entity level only. No employee-level or project-level CapEx planning is supported. | Medium | Use GL-level OpEx planning for project-level CapEx tracking. Dedicated CE model handles asset-level detail at entity only. | No change planned |
| No employee-level headcount — HC planning is job-role based, not employee-based. Individual employee records require OWP integration. | Medium | Scope OWP alongside IFP for employee-level detail. IFP HC provides job/grade-level planning which satisfies most FP&A use cases. | By design — use OWP for employee-level |
| 5 ADO links broken out of box — Five known ADO pipeline links are missing or broken after generation: Vendor Hierarchy (FP), and SYS by J2/J3/J4 Job + Job Grade (HC). | Medium | Create these links manually using the ADO manual setup steps in the Configuration Guide. Budget 30–60 minutes for this task during post-generation. | Fix expected in future PAF release |
| Basic allocations only — OpEx allocations support simple percentage-based or amount-based rules. Waterfall and reciprocal allocation methods are not available. | Low | Use manual workarounds for complex cost allocation. Scope custom development if waterfall or reciprocal allocations are required. | No timeline |
| End-user import templates removed in v2.0 — The Excel-based data entry templates from v1.x are not available in v2.0. All data entry is via the Anaplan UX. | Low | Use native Anaplan UX for all data entry. For bulk uploads, use ADO-based flat file import pipelines. | Not planned for reintroduction |
| Dependent dropdowns inconsistent in generation — Dependent dropdown UX behavior does not always generate correctly. Pages may show all options rather than filtered options. | Low | Repair manually after generation by configuring the dropdown filter in the Page Builder. Typically 15–30 minutes per affected page. | No fix timeline — manual repair required |
| Line item codes not in generation — Line item codes must be populated manually after generation. They do not auto-populate from the configuration answers. | Low | Populate line item codes from the template model post-generation. Budget time for this in the post-generation checklist. | No fix expected near term |
| Naming mismatches in generation — If entity dimension name in configuration questions doesn't exactly match the hierarchy rename, modules and line items may not rename correctly throughout the model. | Low | Ensure exact name match (including capitalization) between the question response and hierarchy rename field. Review the generation log for naming errors immediately after generation. | By design — requires careful configuration |
Exclusion Checklist
Before scoping IFP v2.1, confirm the customer does NOT have any of the following hard stops:
- Requires BYOK encryption on public cloud infrastructure
- Cannot use AWS-hosted services (public sector, federal, sovereign cloud)
- Requires more than 8 dimensions in any planning model
- Requires employee-level CapEx or headcount planning without OWP
- Requires waterfall or reciprocal cost allocation out of box
If any box cannot be unchecked, stop and engage the Apps team before proceeding.
Ecosystem Gap Coverage
| Gap | Solution | Integration Pattern |
|---|---|---|
| Employee-level headcount | Operational Workforce Planning (OWP) | OWP → ADO → IFP HC DAT module |
| Commercial revenue planning | Consensus Margin Planning (CMP) | CMP → ADO → IFP Revenue DAT module |
| Consolidation and statutory reporting | Financial Consolidation | IFP → ADO → Financial Consolidation |
| Extended workforce budgeting | Workforce Budgeting (WFB) | Confirm integration pattern with Apps team |