Error types and reason codes

Errors in IGFC messaging can be classified into three types:

  • Poller error (POLLER_ERROR) – errors that originate from the inbox poller in the process of reading the business documents.

  • Rule execution error (RULE_EXEC_ERROR) – errors that originate from the rule engine.

  • Journal entry generation error (JE_GENERATE_ERROR) – errors that originate from the journal generator module.

    For each type, there are specific reason codes that further provide details on the error. This table shows the major reason codes behind poller, rule execution, and journal entry generation error.
    Error type Reason code
    Invalid BOD Missing master data Missing GFC Setup

    Poller Error (POLLER_ERROR)

    		 An incoming business document is considered invalid when:
    • The attribute value for TenantID, VariationID or Action Code is blank.

    • The attribute value for VariationID or Action Code is not recognized.

    • There is an error on a system file named NounIDsInstance.xml

    		 These setup does not exist:
    • Tenant Registration
    • Valid License Key
    • BOD Mapping

    Rule execution error (RULE_EXEC_ERROR)

    A search-template type expression was included in the rule script that was run. However, the search template could not retrieve a value because the arguments did not match the records being searched.

    For an existing search template, parameters have been added or removed but the related master data BOD was not regenerated after the change.

    Journal entry generation error (JE_GENERATE_ERROR)

    A search-template type expression was defined for an SSJE attribute in the JE. However, the search template could not retrieve a value because the arguments did not match the records being searched. This will be triggered only for mandatory SSJE attributes.
    The JE template setup does not exist for these mandatory attributes:

    • JournalEntryHeader/BaseJournalEntryHeader/AccountingJournalReference/ID

    • JournalEntryLine/GLAccount/GLNominalAccount

    • JournalEntryLine/SourceAccountingDate/PostDateTime

    A "Failed Message" reason code is also available for all types of error. This is generally applied as a catch-all message when the cause of the error does not specifically fall under any existing error category.

    See Troubleshooting guide.