Troubleshooting guide

Message	Details of Run Time error	Additional information	How to investigate and troubleshoot
101	Description BOD TenantID is not registered in GFC. Type POLLER_ERROR. Reason Code Missing GFC setup.	The TenantID for the business document in the COR_INBOX table is not registered in IGFC.	TenantID must be the same as Tenant specified during installation.
102	Description BOD already exists. Type POLLER_ERROR. Reason Code Invalid BOD.	An earlier business document was already processed by the poller for the same BODID. A BODID contains the Document, DocumentID, VariationID, AccountingEntity, and Location.	Verify from the IGFC View page for the same document that was processed.
103	Description BOD mapping does not exist. Type POLLER_ERROR. Reason Code Invalid BOD.	There were no attributes mapped on the BOD Registration page.	Define attributes for the corresponding BOD in the IGFC BOD Registration page. Go to Documents > BOD > then click Attributes hyperlink for the particular noun. Add and define attribute records.
104	Description Variation ID does not exist. Type POLLER_ERROR. Reason Code Invalid BOD.	The business document's attribute for variationID is blank.	Attribute {Noun}\DocumentID\ID\@variationID must be defined with a numeric value.
105	Description Unable to find BOD XSD. Type POLLER_ERROR. Reason Code Invalid BOD.	The incoming business document is not registered in IGFC.	Register the business document in the IGFC BOD Registration page. Go to Documents > BOD and add and define a new record for the particular business document.
106	Description Unable to find class file. Type POLLER_ERROR. Reason Code Invalid BOD.	The Master Data BOD is not yet generated in the BOD Registration page.	Generate Master Data BOD in the IGFC BOD Registration page. Go to Documents > BOD > Select the particular MDM then click Generate Class.
107	Description Action Code not recognized. Type POLLER_ERROR. Reason Code Invalid BOD.	The value retrieved for ActionCode attribute from the business document is not valid. Valid action codes in IGFC are Add, Replace, Delete and Accepted.	Attribute {Verb}/ActionCriteria/ActionExpression/@actionCode must be defined with a valid value.
108	Description Error reading {Document Name}.xml Type POLLER_ERROR. Reason Code Invalid BOD.	A required system file of the document does not exist or is corrupted.	Ensure that the system file of the document found in IGFC Folder(gfc\xsd\Standard\XML) exists and is not corrupted.
109	Description Error reading {Document Name}.xml Type POLLER_ERROR. Reason Code Invalid BOD.	The source application's logicalID does not match an existing license key.	Ensure license file exists in gfc\resources\ license folder.
199	Description {Description of Error} Type POLLER_ERROR. Reason Code Failed Message	An error was encountered during poller processing that does not have a specific error category.	All other errors that do not fall under a specific error category will be investigated based on the error description.
204	Description Cannot run Rule: {Rule Name}. Search Template:{Search Template Name and Parameters} is not active. Type RULE_EXEC_ERROR Reason Code Missing GFC setup.	For an existing search template, parameters have been added or removed but the relevant master data BOD was not re-activated after the change. A new search template was added and the relevant master data BOD has not yet been generated.	Generate the relevant master data in BOD page. Go to Document > BOD to generate the master data BOD.
209	Description Reference master data is missing for Search template {Search template name and parameters}. Document must be manually reprocessed once all missing master data are sent to GFC. Type RULE_EXEC_ERROR Reason Code Missing master data.	The search template used in an expression failed to retrieve a value because the master data document being referenced is not yet received by IGFC after 45 minutes from the receipt of the input transaction document.	Verify that the referenced master data exists in IGFC View > BOD > Master Data before clicking the Reprocess hyperlink. Alternatively, check the accuracy of the expression arguments; they must match a master data being searched.
250	Description Journal not generated for these rules: {Rule Name}. Type RULE_EXEC_WARNING Reason Code Rule script condition did not create journal.	Rule script conditions for the rule names listed in the message description were not met.	Warning Message only and does not necessarily indicate an execution error. If no output is generated from the input business document, check whether there is an existing rule record which matches the accounting entity and document name but has inactive status.
251	Description Output not generated for rule: {Rule Name}. Document Reference is missing. Document will be automatically reprocessed once all Document References are sent to GFC. Type RULE_EXEC_WARNING Reason Code Missing reference.	The business document referenced by the originating master data or transaction is not yet received by IGFC.	This message does not necessarily indicate an execution error. IGFC will process the master data or transaction once it receives the referenced document.
252	Description Journal not generated for rule: {Rule Name}. Acknowledge BOD for the original document was not yet received. Updated document will be automatically reprocessed once acknowledgment is sent to GFC. Type RULE_EXEC_WARNING Reason Code Missing reference.	The Acknowledge BOD for the original document which is the basis for processing the updated document is not yet received by IGFC.	The message does not necessarily indicate an execution error. IGFC will process the transaction once it receives the Acknowledge BOD for the original document.
253	Description Output not generated for these rules: {Rule Name}. Reference master data is missing for Search template {Search template name and parameters}. Document will be automatically reprocessed once all missing master data are sent to GFC. Type RULE_EXEC_WARNING Reason Code Missing master data.	The search template used in an expression failed to retrieve a value because the master data document being referenced is not yet received by IGFC.	This message does not necessarily indicate an execution error. IGFC will process the transaction once it receives the referenced master data document. The master data document must exist in IGFC within 45 minutes from the time of receipt of the input transaction document. Alternatively, check the accuracy of the expression arguments; they must match the master data being searched.
254	Description Rules not found. Please check if Rule record or Rule script exists and has Active status. Type RULE_EXEC_WARNING Reason Code Missing GFC setup.	Applicable rule record does not exist or is not active for the input BOD.	This message does not necessarily indicate an execution error. There is no active rule record that matches the document type and sender entity of the input document. Check the status or the setup of the applicable rule record, if any. Go to Business Rule > Rules to check if the desired rule record exists or activate an inactive rule.
255	Description This is a document reference for these rules: {Rule Name}. The input document or other document references are not yet received. Type RULE_EXEC_WARNING Reason Code Missing reference.	The document is used as a reference to another input document through the Reference Mapping facility in the Rule setup. The input document applicable for the rule or other related references are not yet received by IGFC to generate an output journal.	This message does not necessarily indicate an execution error. IGFC will process the transaction once it receives the required documents.
256	Description Journal not generated for rule: {Rule Name}. A document with higher variation ID has been processed. Type RULE_EXEC_WARNING Reason Code Variation ID outdated.	IGFC received a transaction business document with lower variation ID after processing the same document with a higher variation ID. Alternatively, multiple variations of the same document are pending processing in IGFC due to missing references. Once the reference is received, the document with highest variation ID will be processed. As a result, the outdated document will no longer be processed.	Identify the updated document with higher variation ID and ensure that it was processed correctly.
299	Description Journal cannot be generated for Rule: {Rule Name}.Reason: {Error} Type RULE_EXEC_ERROR Reason Code Failed Message.	An error was encountered during rule execution which does not have a specific error category. An example is when an attribute operand for a Date type expression has an invalid or unsupported date format. This error message is displayed: `com.infor.gfc.exceptions.GfcDateFormatException: [dateValue] is not supported date format`	All other errors that do not fall under a specific error category are investigated based on the error description. For the particular example given, fix can be made by updating the date value of the input business document to a valid and supported date format. These formats are accepted: `mm/dd/yyyy` `mm-dd-yyyy` `yyyy/mm/dd` `yyyy-mm-dd` `yyyy-mm-ddThh:mm:ssZ` (UTC format)
300	Description Journal cannot be generated for Rule: {Rule Name}.There are errors in {Expression Value}. Type JE_GENERATE_ERROR Reason Code Missing master data.	A search-template type expression was defined for an SSJE attribute in the JE template. However, the expression could not retrieve a value because the arguments did not match a master data record. This will be triggered only for mandatory SSJE attributes. Mandatory SSJE attributes are: JournalEntryLine/GLAccount/GLNominalAccount- JournalEntryLine/SourceAccountingDate/PostDateTime- JournalEntryHeader/BaseJournalEntryHeader/AccountingJournalReference/ID ID	The error message will indicate the expression in question, including its arguments. Check the accuracy of the arguments, they must match the master data being searched.
302	Description Journal cannot be generated for Rule: {Rule Name}. {Output SSJE Attribute} is blank. Type JE_GENERATE_ERROR Reason Code Missing GFC setup.	The JE template setup does not exist for mandatory SSJE attributes.	Ensure that mandatory SSJE attributes are defined in Rule Setup or Journal Entry Templates. Go to BPA Designer > Rules or BPA Designer > Journal Entry Templates to check whether mandatory SSJE attributes have been defined and the value source returns an actual value.
398	Description Reference BOD has been purged. Type JE_GENERATE_ERROR Reason Code Missing reference.	The master data or transaction document referenced by the input document is no longer available in IGFC as a result of purging activities.	Identify and republish the referenced document from the source application, if applicable.
399	Description Journal cannot be generated for Rule: {Rule Name}. Reason: {Error} Type JE_GENERATE_ERROR Reason Code Failed Message.	An error was encountered during output generation which does not have a specific error category. An example would be when a search-template type expression was defined for an SSJE attribute in the JE template. However, the search template could not retrieve a value because the expression used no longer investigate by checking exists or has been removed.	All other errors that do not fall under a specific error category will be investigated based on the error description. For the particular example given, investigate by checking the existing JE Templates with type "Expression" and look for values which are not names of an expression. This value is presented as a numeric value which means that the JE template uses a deleted expression.

101

Description: BOD TenantID is not registered in GFC.
Type: POLLER_ERROR.
Reason Code: Missing GFC setup.

The TenantID for the business document in the COR_INBOX table is not registered in IGFC.

TenantID must be the same as Tenant specified during installation.

102

Description: BOD already exists.
Type: POLLER_ERROR.
Reason Code: Invalid BOD.

An earlier business document was already processed by the poller for the same BODID.

A BODID contains the Document, DocumentID, VariationID, AccountingEntity, and Location.

Verify from the IGFC View page for the same document that was processed.

103

Description: BOD mapping does not exist.
Type: POLLER_ERROR.
Reason Code: Invalid BOD.

There were no attributes mapped on the BOD Registration page.

Define attributes for the corresponding BOD in the IGFC BOD Registration page.

Go to Documents > BOD > then click Attributes hyperlink for the particular noun. Add and define attribute records.

104

Description: Variation ID does not exist.
Type: POLLER_ERROR.
Reason Code: Invalid BOD.

The business document's attribute for variationID is blank.

Attribute {Noun}\DocumentID\ID\@variationID must be defined with a numeric value.

105

Description: Unable to find BOD XSD.
Type: POLLER_ERROR.
Reason Code: Invalid BOD.

The incoming business document is not registered in IGFC.

Register the business document in the IGFC BOD Registration page.

Go to Documents > BOD and add and define a new record for the particular business document.

106

Description: Unable to find class file.
Type: POLLER_ERROR.
Reason Code: Invalid BOD.

The Master Data BOD is not yet generated in the BOD Registration page.

Generate Master Data BOD in the IGFC BOD Registration page.

Go to Documents > BOD > Select the particular MDM then click Generate Class.

107

Description: Action Code not recognized.
Type: POLLER_ERROR.
Reason Code: Invalid BOD.

The value retrieved for ActionCode attribute from the business document is not valid.

Valid action codes in IGFC are Add, Replace, Delete and Accepted.

Attribute {Verb}/ActionCriteria/ActionExpression/@actionCode must be defined with a valid value.

108

Description: Error reading {Document Name}.xml
Type: POLLER_ERROR.
Reason Code: Invalid BOD.

A required system file of the document does not exist or is corrupted.

Ensure that the system file of the document found in IGFC Folder(gfc\xsd\Standard\XML) exists and is not corrupted.

109

Description: Error reading {Document Name}.xml
Type: POLLER_ERROR.
Reason Code: Invalid BOD.

The source application's logicalID does not match an existing license key.

Ensure license file exists in gfc\resources\ license folder.

199

Description: {Description of Error}
Type: POLLER_ERROR.
Reason Code: Failed Message

An error was encountered during poller processing that does not have a specific error category.

All other errors that do not fall under a specific error category will be investigated based on the error description.

204

Description: Cannot run Rule: {Rule Name}. Search Template:{Search Template Name and Parameters} is not active.
Type: RULE_EXEC_ERROR
Reason Code: Missing GFC setup.

For an existing search template, parameters have been added or removed but the relevant master data BOD was not re-activated after the change.

A new search template was added and the relevant master data BOD has not yet been generated.

Generate the relevant master data in BOD page.

Go to Document > BOD to generate the master data BOD.

209

Description: Reference master data is missing for Search template {Search template name and parameters}. Document must be manually reprocessed once all missing master data are sent to GFC.
Type: RULE_EXEC_ERROR
Reason Code: Missing master data.

The search template used in an expression failed to retrieve a value because the master data document being referenced is not yet received by IGFC after 45 minutes from the receipt of the input transaction document.

Verify that the referenced master data exists in IGFC View > BOD > Master Data before clicking the Reprocess hyperlink.

Alternatively, check the accuracy of the expression arguments; they must match a master data being searched.

250

Description: Journal not generated for these rules: {Rule Name}.
Type: RULE_EXEC_WARNING
Reason Code: Rule script condition did not create journal.

Rule script conditions for the rule names listed in the message description were not met.

Warning Message only and does not necessarily indicate an execution error. If no output is generated from the input business document, check whether there is an existing rule record which matches the accounting entity and document name but has inactive status.

251

Description: Output not generated for rule: {Rule Name}. Document Reference is missing. Document will be automatically reprocessed once all Document References are sent to GFC.
Type: RULE_EXEC_WARNING
Reason Code: Missing reference.

The business document referenced by the originating master data or transaction is not yet received by IGFC.

This message does not necessarily indicate an execution error. IGFC will process the master data or transaction once it receives the referenced document.

252

Description: Journal not generated for rule: {Rule Name}. Acknowledge BOD for the original document was not yet received. Updated document will be automatically reprocessed once acknowledgment is sent to GFC.
Type: RULE_EXEC_WARNING
Reason Code: Missing reference.

The Acknowledge BOD for the original document which is the basis for processing the updated document is not yet received by IGFC.

The message does not necessarily indicate an execution error. IGFC will process the transaction once it receives the Acknowledge BOD for the original document.

253

Description: Output not generated for these rules: {Rule Name}. Reference master data is missing for Search template {Search template name and parameters}. Document will be automatically reprocessed once all missing master data are sent to GFC.
Type: RULE_EXEC_WARNING
Reason Code: Missing master data.

The search template used in an expression failed to retrieve a value because the master data document being referenced is not yet received by IGFC.

This message does not necessarily indicate an execution error. IGFC will process the transaction once it receives the referenced master data document. The master data document must exist in IGFC within 45 minutes from the time of receipt of the input transaction document. Alternatively, check the accuracy of the expression arguments; they must match the master data being searched.

254

Description: Rules not found. Please check if Rule record or Rule script exists and has Active status.
Type: RULE_EXEC_WARNING
Reason Code: Missing GFC setup.

Applicable rule record does not exist or is not active for the input BOD.

This message does not necessarily indicate an execution error. There is no active rule record that matches the document type and sender entity of the input document. Check the status or the setup of the applicable rule record, if any. Go to Business Rule > Rules to check if the desired rule record exists or activate an inactive rule.

255

Description: This is a document reference for these rules: {Rule Name}. The input document or other document references are not yet received.
Type: RULE_EXEC_WARNING
Reason Code: Missing reference.

The document is used as a reference to another input document through the Reference Mapping facility in the Rule setup. The input document applicable for the rule or other related references are not yet received by IGFC to generate an output journal.

This message does not necessarily indicate an execution error. IGFC will process the transaction once it receives the required documents.

256

Description: Journal not generated for rule: {Rule Name}. A document with higher variation ID has been processed.
Type: RULE_EXEC_WARNING
Reason Code: Variation ID outdated.

IGFC received a transaction business document with lower variation ID after processing the same document with a higher variation ID. Alternatively, multiple variations of the same document are pending processing in IGFC due to missing references. Once the reference is received, the document with highest variation ID will be processed. As a result, the outdated document will no longer be processed.

Identify the updated document with higher variation ID and ensure that it was processed correctly.

299

Description: Journal cannot be generated for Rule: {Rule Name}.Reason: {Error}
Type: RULE_EXEC_ERROR
Reason Code: Failed Message.

An error was encountered during rule execution which does not have a specific error category.

An example is when an attribute operand for a Date type expression has an invalid or unsupported date format.

This error message is displayed:

com.infor.gfc.exceptions.GfcDateFormatException: [dateValue] is not supported date format

All other errors that do not fall under a specific error category are investigated based on the error description.

For the particular example given, fix can be made by updating the date value of the input business document to a valid and supported date format.

These formats are accepted:

mm/dd/yyyy
mm-dd-yyyy
yyyy/mm/dd
yyyy-mm-dd
yyyy-mm-ddThh:mm:ssZ (UTC format)

300

Description: Journal cannot be generated for Rule: {Rule Name}.There are errors in {Expression Value}.
Type: JE_GENERATE_ERROR
Reason Code: Missing master data.

A search-template type expression was defined for an SSJE attribute in the JE template. However, the expression could not retrieve a value because the arguments did not match a master data record. This will be triggered only for mandatory SSJE attributes.

Mandatory SSJE attributes are:

JournalEntryLine/GLAccount/GLNominalAccount-
JournalEntryLine/SourceAccountingDate/PostDateTime-
JournalEntryHeader/BaseJournalEntryHeader/AccountingJournalReference/ID
ID

The error message will indicate the expression in question, including its arguments. Check the accuracy of the arguments, they must match the master data being searched.

302

Description: Journal cannot be generated for Rule: {Rule Name}. {Output SSJE Attribute} is blank.
Type: JE_GENERATE_ERROR
Reason Code: Missing GFC setup.

The JE template setup does not exist for mandatory SSJE attributes.

Ensure that mandatory SSJE attributes are defined in Rule Setup or Journal Entry Templates.

Go to BPA Designer > Rules or BPA Designer > Journal Entry Templates to check whether mandatory SSJE attributes have been defined and the value source returns an actual value.

398

Description: Reference BOD has been purged.
Type: JE_GENERATE_ERROR
Reason Code: Missing reference.

The master data or transaction document referenced by the input document is no longer available in IGFC as a result of purging activities.

Identify and republish the referenced document from the source application, if applicable.

399

Description: Journal cannot be generated for Rule: {Rule Name}. Reason: {Error}
Type: JE_GENERATE_ERROR
Reason Code: Failed Message.

An error was encountered during output generation which does not have a specific error category.

An example would be when a search-template type expression was defined for an SSJE attribute in the JE template. However, the search template could not retrieve a value because the expression used no longer investigate by checking exists or has been removed.

All other errors that do not fall under a specific error category will be investigated based on the error description.

For the particular example given, investigate by checking the existing JE Templates with type "Expression" and look for values which are not names of an expression. This value is presented as a numeric value which means that the JE template uses a deleted expression.

Troubleshooting guide

IGFC errors and warnings