Skip to main content

Troubleshooting Guide: Resolving Import Failures for Budget By Account\/Month Application

Distributor troubleshooting for failed imports in the legacy Budget By Account/Month app: use Import Routine 634111 to load the Bgt_Budget table (not ZZ_Budget) and Report 12731031 to reconcile budget vs actuals. Requires v23.01+.

B
Written by Bailey Naas-Thornton

Minimum Version Required: 23.01

Pre-Conditions

  • Application: "Budget By Account/Month" (Legacy version).

  • System Requirement: Active access to the global Import Routine tool and the Report Library.

  • Schema Requirement: Applicable to customers on the modern database schema utilizing the Bgt_Budget table.

Steps

  1. Identify Schema Mismatch: If the import task within the "Budget By Account/Month" application fails, it is likely attempting to write to the legacy ZZ_Budget table which does not exist in your environment.

  2. Access the Modern Import Routine: Navigate to the system-wide Import Routine tool.

  3. Search by Routine ID: Search for and execute Import Routine ID: 634111. This routine is specifically configured to map data to the modern Bgt_Budget schema. Please note you may need to filter to EncompassID = Support to see this record.

  4. Verify Data via Report Library: Once the import is successful, navigate to the Report Library.

  5. Search by Report ID: Search for Report ID: 12731031. This report is designed to pull from the modern schema and should be used to reconcile your imported budget against actuals. Please note you may need to filter to EncompassID = Support to see this record.

  6. Discontinue Application-Level Imports: Move away from using the "Budget By Account/Month" application dashboard for imports, as it may still reference legacy data structures.

  7. Contact Support: If the IDs provided do not appear in your search results or the import fails, contact support with the following information:

    • IDs Attempted: Confirm use of Import ID 634111 and Report ID 12731031.

    • Error Messages: Provide the exact error code or text encountered.

    • Screenshots: Attach images of the search results or the import configuration screen.

    • Log Files: Provide any generated import error logs.

    • Step-by-Step: Document the exact path taken to reach the Import Routine tool.

    • System History: Note the date/time the issue started and if any recent migrations occurred.

Fields And Definitions

  • Use IDs for Accuracy: When searching for tools, use the unique ID numbers (634111/12731031) rather than names to ensure you are using the version compatible with the Bgt_Budget schema.

  • Transition to the Report Library: Favor the "Budget" section in the Report Library over application-specific dashboards, as these are more frequently updated for schema changes.

  • Verify Source Headers: Ensure your import file aligns with the requirements of the modern Bgt_Budget table to avoid mapping errors.

Best Practices

  • Bgt_BudgetModern Schema Table: The current standard database structure for all budget data.
    ​
    ​

  • ZZ_BudgetLegacy Schema Table: An older database structure no longer present in newer system environments.
    ​
    ​

  • Import Routine ID: 634111The specific system tool used to ingest budget data into the modern Bgt_Budget table.
    ​
    ​

  • Report ID: 12731031The designated report for reconciling modern budget data against actuals.SchemaThe underlying structure or "map" of the database that determines where data is stored.

Did this answer your question?