The Eye

How DigitAI Manages Cost Centers Extracted from Folders for ERP Export

Administratoruser

This guide explains how DigitAI processes cost centers extracted from folder structures for ERP export. Understanding this logic is crucial for correct configuration and to avoid inconsistencies in the destination system.

Step by step

  1. 1

    Identifying Cost Centers from Folder Structure

    DigitAI identifies cost centers directly from folder names within your structure. A specific format is expected, such as 'CODE - Cost Center Name', where the code is the primary identifier and the name is the description. MISSING: Confirm the exact format expected by DigitAI (e.g., 'CODE - Name', 'CODE_Name', etc.).

  2. 2

    Cost Center Code Validation

    It is important to note that DigitAI does not perform a pre-validation of cost center codes against an external endpoint or an internal database. The validation of the code's existence and validity falls entirely on the destination ERP system during the export process. This means that any incorrect or non-existent code in the ERP will be rejected by the ERP itself, not by DigitAI.

  3. 3

    Cost Center Description Extraction

    The cost center description is extracted directly from the folder name, following the established format (e.g., the 'Cost Center Name' part in 'CODE - Cost Center Name'). DigitAI does not query or overwrite this description with information from an external endpoint. The description sent to the ERP is exactly what is found in the folder name.

  4. 4

    Recommendations for Consistency

    To ensure correct integration and avoid errors in the ERP, it is essential to maintain strict consistency between the folder structure in DigitAI and the cost center configuration in your ERP system. 1. **Consistent Format:** Ensure that all folders representing cost centers follow the exact format expected by DigitAI (e.g., 'CODE - Name'). 2. **Valid Codes:** Verify that the cost center codes used in folder names exist and are valid in your ERP before export. 3. **Manual Update:** If there are changes to cost centers in the ERP (codes or descriptions), these must be manually reflected in the DigitAI folder structure to maintain synchronization. 4. **Testing:** Perform tests with a limited dataset to confirm that cost center export works as expected.

[@portabletext/react] Unknown block type "helpCallout", specify a component for it in the `components.types` prop
[@portabletext/react] Unknown block type "helpCallout", specify a component for it in the `components.types` prop
Was this article helpful?

Last updated: 10/30/2026

Still have questions?

Contact support