Journal Wand Messages

Journal Statuses

During the Loading Journals process, the journal will progress through one or more of the following statuses:

Status	Meaning
NEW	New journal
VALID	Journal successfully validated
INVALID	Journal failed validation
LOADED	Journal successfully loaded into Oracle GL Interface table
LOAD ERROR	Error encountered when inserting journal into GL Interface table
IMPORTED	Journal Import program submitted for this journal
IMPORT ERROR	Error encountered in the submission of the Journal Import request
APPROVAL	Journal successfully submitted for approval
APPROVAL ERROR	Error encountered in the submission of the Journal Approval workflow
AUTOPOST	AutoPost program submitted for this journal
AUTOPOST ERROR	Error encountered in the submission of the AutoPost request

Validation Error Messages

The validation stage of the Loading Journals process, validates the journal data for compliance with the rules imposed by Oracle’s Journal Import program. The following are validation error messages per journal field:

Journal Header Fields

Field	Message	Validation Rule
Ledger Id	Ledger is required.	Ledger Id
Ledger Id	Ledger is invalid or not accessible to this Responsibility.	Ledger Id
Ledger Id	Ledger does not share same Chart of Accounts and/or Calendar as template’s master ledger.	Ledger Id
Ledger Id	Read-only access to this Ledger.	Ledger Id
Ledger Id Batch Name Journal Name Source Category Currency Period/Accounting Date	A journal header with the same unique key values is duplicated elsewhere in the upload range.	Journal Header
Batch Name	Batch Name may not exceed 100 characters.
Journal Name	Journal Name is required.
Journal Name	Journal Name may not exceed 100 characters.
Journal Name	The journal, in which this journal header is grouped, is unbalanced. Refer to the User Guide for more information on journal balance validation.	Balanced Journal
Journal Name	AutoPost not submitted. The ‘Wands Journal Wand’ AutoPost Set does not exist for this Ledger.	AutoPost
Journal Name	AutoPost not submitted. The option for this journal’s values does not exist in the ‘Wands Journal Wand’ AutoPost Criteria Set.	AutoPost
Journal Name	A journal with this batch and journal name could not be found in Oracle. Refer to the User Guide for further information.	Journal/Batch Name
Journal Name	AutoPost not submitted. Responsibility does not have access to AutoPost.	AutoPost
Category	Journal Category is required.	Category
Category	Journal Category is not valid.	Category
Source	Journal Source is required.	Source
Source	Journal Source is not valid.	Source
Source	The Journal Source has been restricted in the Journal Wand Options. The only valid source is: <secured_source>	Source
Currency	Currency is required.	Currency
Currency	Currency is not valid.	Currency
Currency	The ledger’s functional currency must be used for this journal type.	Currency
Period	Period is not valid.	Period
Period Accounting Date	An Accounting Date or Period Name is required.	Accounting Date
Period Accounting Date	Accounting Date does not fall within the specified Period.	Accounting Date
Period Accounting Date	Accounting Date is not in an Open or Future Enterable Period.	Period
Period Accounting Date	Accounting date is not within any period in an open encumbrance year.	Period
Accounting Date	This date is not a business day.	Business Day
Accounting Date	There are no business days in this Period.	Business Day
Accounting Date	An Accounting Date is required for ledgers where Average Balance Processing is enabled.	Accounting Date
Batch Description	Batch Description may not exceed 240 characters.
Journal Description	Journal Description may not exceed 240 characters.
Transaction Code	Transaction Code may not exceed 30 characters.
Average Journal Flag	Average Journals can only be imported into consolidation ledgers.	Average Journal
Average Journal Flag	Average Journal Flag is not valid.	Average Journal
Conversion Type	Conversion Type is not valid.	Foreign Currency Journal Conversion Type
Conversion Date	Conversion Date is required if Conversion Type is specified and is not ‘User’.	Foreign Currency Journal
Conversion Rate	Conversion Rate must be null if Conversion Type is not specified.	Foreign Currency Journal
Conversion Rate	Conversion Rate is required if Conversion Type is ‘User’.	Foreign Currency Journal
Conversion Rate	There is no Conversion Rate for this Currency, Conversion type, and Conversion date.	Foreign Currency Journal
Encumbrance Type	Valid Encumbrance Type is required for an Encumbrance journal.	Encumbrance Type
Budget	Budget Version must not be frozen.	Budget
Budget	Budget Version is not active for the specified period.	Budget
Budget	Budget Version does not exist for this ledger.	Budget
Budget	Budget Version is required.	Budget
Budget	Budget Version is not open for the specified year.	Budget
Reversal Method	Reversal Method is not valid.	Reversal Journal Reversal Method
Reversal Method	Reversal Method is required.	Reversal Journal Reversal Method
Reversal Period	Reversal Period must be the same or after the Accounting Period.	Reversal Journal Reversal Date
Reversal Period	A valid Reversal Period is required.	Reversal Journal Reversal Period
Reversal Period	A valid Reversal Period is required for ledgers where Average Balance Processing is not enabled.	Reversal Journal Reversal Period
Reversal Period	Reversal period is not in an open encumbrance year.	Reversal Journal Reversal Period
Reversal Period	Reversal Period must be the same or after the Accounting Period.	Reversal Journal Reversal Period
Reversal Period	A valid Reversal Period is required.	Reversal Journal Reversal Period
Reversal Period Reversal Date	Reversal Date is not in an Open or Future Enterable Period.	Reversal Journal Reversal Date Reversal Period
Reversal Date	Reversal Date must be the same or after the Accounting Date.	Reversal Journal Reversal Date
Reversal Date	A valid Reversal Date is required for ledgers where Average Balance Processing is enabled.	Reversal Journal Reversal Date
Reversal Date	This date is not a business day.	Reversal Journal Reversal Date Business Day
Clearing Company	Originating company may not be specified for this journal type.	Intercompany Journal
Clearing Company	Originating company can only be specified when intercompany balancing is enabled.	Intercompany Journal

Journal Line Fields

Field	Message	Validation Rule
Accounting Flex Segments	Dependent Segment value is not valid for its Independent Segment value.	Accounting Flexfield Segments
Accounting Flex Segments	Segment is required.	Accounting Flexfield Segments
Accounting Flex Segments	Segment value is not valid.	Accounting Flexfield Segments
Accounting Flex Segments	Segment does not allow posting.	Accounting Flexfield Segments
Accounting Flex Segments	Accounting Date is not in the effective date range for this Segment.	Accounting Flexfield Segments
Accounting Flex Segments	Segment is not enabled.	Accounting Flexfield Segments
Accounting Flex Segments	Segment is a parent segment.	Accounting Flexfield Segments
Accounting Flex Segments	The account combination does not exist and cannot be created as the dynamic insert option is not enabled for this ledger.	Account Combination
Accounting Flex Segments	The account combination does not exist. It is valid and will be created during the load process.	Account Combination
Accounting Flex Segments	Account combination does not allow posting.	Account Combination
Accounting Flex Segments	Accounting date is not in the effective date range for this account combination.	Account Combination
Accounting Flex Segments	Account combination is a summary combination.	Account Combination
Accounting Flex Segments	Segment value violates the Security Rule for this Segment and Responsibility.	Accounting Flexfield Segments
Balancing Segment	Balancing segment value is not valid for this ledger.	Balancing Segment
Balancing Segment	No or read-only access to this balancing segment value.	Balancing Segment
Management Segment	No or read-only access to this management segment value.	Management Segment
Entered Debit	Entered Debit is required when Accounted Debit is populated and Conversion Type is not specified.	Foreign Currency Journal
Entered Debit	The Entered Debit and Credit fields may not both contain values on the same line.
Entered Credit	Entered Credit is required when Accounted Credit is populated and Conversion Type is not specified.	Foreign Currency Journal
Entered Credit	The Entered Debit and Credit fields may not both contain values on the same line.
Accounted Debit	Accounted Debit must be null if Conversion Type is specified.	Foreign Currency Journal
Accounted Debit	Accounted Debit is required when Conversion Type is not specified.	Foreign Currency Journal
Accounted Credit	Accounted Credit must be null if Conversion Type is specified.	Foreign Currency Journal
Accounted Credit	Accounted Credit is required when Conversion Type is not specified.	Foreign Currency Journal
Accounted Debit Accounted Credit	The Entered Debit/Credit amount must equal the Accounted Debit/Credit amount when Currency is STAT.	Statistical Journal
Accounted Debit Accounted Credit	The Accounted Debit and Credit fields may not both contain values on the same line.
Line Description	Line Description may not exceed 240 characters.
Additional Line Info 1	Additional Line Info 1 may not exceed 240 characters.
Additional Line Info 2	Additional Line Info 2 may not exceed 240 characters.
Additional Line Info 3	Additional Line Info 3 may not exceed 240 characters.
Additional Line Info 4	Additional Line Info 4 may not exceed 240 characters.
Additional Line Info 5	Additional Line Info 5 may not exceed 240 characters.
Additional Line Info 6	Additional Line Info 6 may not exceed 240 characters.
Additional Line Info 7	Additional Line Info 7 may not exceed 240 characters.
Additional Line Info 8	Additional Line Info 8 may not exceed 240 characters.
Additional Line Info 9	Additional Line Info 9 may not exceed 240 characters.
Additional Line Info 10	Additional Line Info 10 may not exceed 240 characters.
Line Context Captured Info Context	Context value is not valid.	Descriptive Flexfields
Line Context Captured Info Context	Context value is required.	Descriptive Flexfields
Attribute 1..20	Oracle API message pertaining to an invalid descriptive context or flexfield value.	Descriptive Flexfields
Attribute 1..20	Descriptive flexfield value is required.	Descriptive Flexfields
Attribute 1..20	Descriptive flexfield value must not contain a value for this context.	VAT Context
VAT Context	VAT Context is not valid.	VAT Context
VAT Context	Value Added Tax data is not valid for this journal type.	VAT Context
Recon. Reference	Reconciliation Reference may not exceed 240 characters.
Statistical Amount	Statistical Amount must be null when Currency is STAT.	Statistical Journal

Journal Attachment Fields

Field	Message	Notes
Description	Description must be less than or equal to 255 characters.
Seq	Error encountered when uploading attachment: <error_message>	An error thrown by Oracle when uploading an attachment via the Loading Journals process, is reported in the Seq cell for the attachment.
Seq	Sequence is a required field and must be greater than zero.
Source	Source is a required field.
Source	The file is larger than the maximum file size admin option: <max_file_size> megabytes.	Applicable to File type only. The <max_file_size> parameter is configured in System Administrator Configuration Options.
Source	File must exist and be greater than 0 bytes.	Applicable to File type only.
Source	Text must be less than or equal to 4000 characters.	Applicable to Short Text type only.
Source	URL must be less than or equal to 4000 characters.	Applicable to Web Page type only.
Title	Title is a required field.
Title	Title must be less than or equal to 80 characters.
Type	Type is a required field.

Validation Rules

Rule Name	Description
Account Combination	If all segment values are valid, the account combination is checked to determine if it exists. If it exists, it must also be enabled, allow posting, must not be flagged as a summary combination, and the journal’s accounting date must fall within its effective date range. If the combination does not exist, then the combination will be created by Oracle’s Journal Import program provided the following criteria are met: Allow Dynamic Inserts is enabled for the Accounting Flexfield; and Cross-validation rule requirements, if any, are satisfied. If either of the above criteria are not true, then the combination will be deemed invalid and the journal status is set to INVALID. The combination must be changed to match an existing, valid combination before the journal can be uploaded. The Account Combinations tool can be used to search and select from existing combinations.
Accounting Date	For ledgers which are not enabled for average balances, either accounting date or period may be entered. If both are entered, then the accounting sate must fall within the period. For ledgers enabled for average balances, accounting date must be entered. The rules for period validation apply: The accounting date must be in a valid, existing period. For encumbrance journals, the accounting date must be in an open encumbrance year (the same as or before the latest encumbrance year on the ledger). For actual journals (functional and foreign currency), the accounting date must be in a period which has a status of Open or Future Entry.
Accounting Flexfield Segments	Only the segments applicable to the chart of accounts for the template ledger (refer to Journal Wand Ledger Selector for more information), are visible in the Create Journal Template wizard and are validated and uploaded to the GL Interface table. Each segment is mandatory and must contain a valid, existing segment value. Use the List of Values associated with each segment field to select a segment value. If the segment’s Value Set is a dependent Value Set, then the value entered for the segment must be in the independent segment’s valid set of values. The segment must: be flagged as enabled be enabled for a date range which includes the accounting date allow posting not be flagged as a parent comply with security rule restrictions associated with the user’s responsibility, as defined in Oracle.
AutoPost	A number of conditions must be met in order for Journal Wand to submit the AutoPost request: The selected responsibility must have access to run the ‘Program – Automatic Posting’ concurrent program i.e. this program must exist in the Request Group associated with the responsibility. An AutoPost Criteria Set entitled ‘Wands Journal Wand’ must exist. If this does not exist, the status of all journals eligible for automatic posting is set to AUTOPOST ERROR. In addition, Journal Wand validates that each journal in the upload range complies with the options configured in this AutoPost Criteria Set. Should a journal not meet the option criteria, AutoPost will not attempt to post the journal and Journal Wand sets the status of the journal to AUTOPOST ERROR. Refer to AutoPost Journal Wand Journals and Submit Journal AutoPost for more information.
Average Journal	To create a journal that affects the ledger’s average balances, rather than standard balances, the Average Journal flag is set to “Y” (Yes). This field is optional but if entered, must contain either “Y” or “N”. The List of Values associated with this field may be used to select a valid value. Average journals can only be imported into consolidation ledgers i.e. the Average Balance Consolidation flag is enabled for the ledger.
Balanced Journal	The sum of the entered debit values must equal the sum of the entered credit values for the target journal. Refer to Grouping of Journal Headers for more information on the grouping of journal headers into target journals. To calculate a journal’s balance, each line value is first rounded according to the currency’s precision setting in Oracle, before the rounded amounts are summed. This is in line with the calculation method applied in Oracle’s Journal Import program. The journal balance validation does not apply to: Statistical journals which have the “STAT” currency; Budget journals, unless the Force Balanced Budget Journals option is enabled.
Balancing Segment	The value entered for the balancing accounting flexfield segment must be in the list of balancing segments for the ledger and the accounting date must be within its enabled period. The logged-in responsibility must have write access to the balancing segment value specified on the journal line. For access rights to balancing segment values, refer to the configuration in Oracle of the Data Access Set associated with the responsibility.
Budget	The Budget Version is mandatory and must be the name of a valid, existing budget, which is applicable to the journal’s ledger. Use the List of Values associated with this field to select a budget from the list of available categories. This field is only applicable to budget journals. The budget must have a status of Open or Current (i.e. it may not be frozen), and must be active for the specified period.
Business Day	Business day validation is only applicable if the ledger is enabled for average balances and if the entered source has an Effective Date Rule of “Fail”. In this case, the accounting date and/or reversal date must exist in the Transaction Calendar linked to the Ledger, and it must be flagged as a business day. If the period is entered instead of the accounting date, then there must be dates within the period that are flagged as business days.
Category	Category is mandatory and must be the name of a valid, existing category. Use the List of Values associated with this field to select a category from the list of available categories.
Conversion Type	Conversion type is optional for foreign currency journals, however if specified it must be the name of a valid, existing conversion type. Use the List of Values associated with this field to select a conversion type from the list of available types. Refer to Foreign Currency Journal for more information on the ways to capture foreign currency journals.
Currency	Currency is mandatory and must be the name of a valid, existing currency. Use the List of Values associated with this field to select a currency from the list of available currencies. Functional Actual and Functional Actual Reversal journals must use the ledger’s functional currency or the “STAT” currency for statistical journals (refer to Statistical Journals for more information). Currency is not an available field for encumbrance journals, therefore it is defaulted internally by the upload process to the ledger’s functional currency.
Descriptive Flexfields	Descriptive flexfield values are validated as follows: If the context value for the particular descriptive flexfield type is configured in Oracle as required, then a context value must be entered. If a context value is entered, it must be a valid context value as configured for the particular descriptive flexfield type. Required global descriptive flexfield values must be entered as well as any required flexfield values associated with the specified context value. Oracle’s descriptive flexfield validation API is invoked to further validate context and field values for Value Set compliance, which includes data type and valid value compliance. Any resulting error messages returned by this validation API are displayed as a comment in the relevant cell.
Encumbrance Type	Encumbrance type is mandatory for encumbrance journals and must be the name of a valid, existing encumbrance type. Use the List of Values associated with this field to select an encumbrance type from the list of available types. Encumbrance type is not an applicable field for actual journals (functional or foreign currency).
Foreign Currency Journal	There are three possible ways to enter a foreign currency journal: Enter the Conversion Type (other than “User”), Conversion Date and Entered Debit/Credit fields. A conversion rate must exist in Oracle for the conversion type and conversion date specified. Entered debit/credit values are entered in the currency specified by the currency field, which should be a currency other than the ledger’s functional currency. Enter the Conversion Type of “User”, Conversion Rate and Entered Debit/Credit fields. Entered debit/credit values are entered in the currency specified by the currency field, which should be a currency other than the ledger’s functional currency. The conversion rate must be the rate applied to calculate the functional currency values from the entered debit/credit values. Enter the converted amounts (in functional currency) in the Accounted Debit/Credit fields. Entered debit/credit values are entered in the currency specified by the currency field, which should be a currency other than the ledger’s functional currency. The conversion type, conversion date and conversion rate fields should not contain values.
Intercompany Journal	The clearing company may be specified for intracompany journals that include multiple balancing segment values and where the total debits and credits for each balancing segment value do not net to zero. Clearing company is not valid for encumbrance journals.
Journal Header	A journal with identical values in its unique key fields exists elsewhere in the journal upload range. Refer to Grouping of Journal Headers.
Journal/Batch Name	Journal Import may have generated a different name for the batch and/or journal to what was populated by Journal Wand in the template. As a result, Journal Wand was not able to query back the batch and journal Ids from Oracle. Subsequent processing dependent on these Ids, such as the upload of attachments and the submission of journal approval, will not be done. Please log a support case with Wands to allow us to troubleshoot further.
Ledger Id	Ledger Id is mandatory. The selected responsibility must have write access to the ledger (see Responsibility Selection for more details). For access rights to ledgers, refer to the configuration in Oracle of the Dynamic Access Set associated with the selected responsibility. The ledger must share a common chart of accounts and calendar with the embedded template ledger (refer to Journal Wand Ledger Selector for more information). Use the List of Values associated with this field to select a ledger from the list of valid ledgers.
Management Segment	The logged-in responsibility must have write access to the management segment value specified on the journal line. For access rights to management segment values, refer to the configuration in Oracle of the Data Access Set associated with the responsibility.
Period	Either accounting date or period must be entered. If both are entered, then the accounting date must fall within the period. If only accounting date is entered, then the period is derived from the date and populated on the Journal Wand template. The rules for period validation apply: Period must be a valid, existing period. For encumbrance journals, the period must be in an open encumbrance year (the same as or before the latest encumbrance year on the ledger). For actual journals (functional and foreign currency), the period must have the status of Open or Future Entry. The List of Values may be used to select a period from the list of existing periods.
Reversal Date	The reversal date is mandatory for functional and foreign currency reversal journals where the ledger is enabled for average balances. The reversal date must be on or after the accounting date. The reversal date must also fall in a valid, existing period which has a status of Open or Future Entry.
Reversal Method	The reversal method is mandatory for reversal journals. Valid values are “Change Sign” and “Switch Debit/Credit”. The List of Values associated with this field may be used to select a valid value. Refer to Reversal Journal for more information on the capture of reversal journals.
Reversal Period	The reversal period is mandatory for encumbrance reversal journals, and for functional reversal and foreign currency reversal journals where the ledger is not enabled for average balances. The reversal period must be a valid, existing period and must be equal to or after the journal period. For actual journals (functional and foreign currency), the period must have a status of Open or Future Entry. For encumbrance journals, the period must be in an open encumbrance year (the same as or before the latest encumbrance year on the Ledger).
Source	Source is mandatory and must be the name of a valid, existing source. Use the List of Values associated with this field to select a source from the list of available sources. If the Secure Journal Source administrator option is enabled, then the entered source must be the same as the secured source. See System Administrator Configuration Options.
Statistical Journal	There are two ways to load statistical data into the GL Interface table: Set the currency to “STAT” and use the Entered Debit/Credit fields for the statistical quantities. The Statistical Amount field should be left blank. If values are entered in the Accounted Debit and Accounted Credit fields as well, then the values must be equal to the corresponding entered debit/credit values. Set the currency to a monetary currency (other than “STAT”) and use Statistical Amount field to enter the quantity (positive value for debit and negative for credit).
VAT Context	The VAT Context field is used to signify the import of Value Added Tax Descriptive Flexfield data. To import this data, the VAT context value must be set to “Y” (Yes). This field is optional but if entered, must contain either “Y” or “N”. The List of Values associated with this field may be used to select a valid value. The VAT context value may not be “Y” in an encumbrance journal.
Reversal Journal	To capture a reversal journal, the reversal period or reversal date must be entered, as well as the reversal method. For encumbrance reversal journals, the reversal period is specified, and not the reversal date. In the case of functional and foreign currency reversal journals, use of reversal date or reversal period is dictated by ledger setup. If the ledger is enabled for average balances, then the reversal date is mandatory, otherwise the reversal period must be used. Refer to Reversal Date and Reversal Period for validation rules.