GL Account Upload
Description
GL Account Upload creates new General Ledger accounts (code combinations) and updates existing ones in a ledger’s chart of accounts, from Excel. Download the accounts of a ledger, filtered by segment values or ranges, change their Enabled, active dates and detail posting or budgeting flags, add new accounts by typing the account string, then upload. Each new account is validated against your segment values and cross-validation rules before it is created.
When to use it
- Mass-create new accounts (code combinations) from existing segment values.
- Enable or disable many existing accounts at once.
- Set or change Start Date Active and End Date Active across many accounts.
- Switch Detail Posting Allowed or Detail Budgeting Allowed for a range of accounts.
- Download a filtered list of accounts for review.
Before you start
- Run Blitz Report from a responsibility whose GL Data Access Set profile gives access to the ledger; the Ledger list shows only the ledgers in that access set.
- The segment values of new accounts exist and are enabled, active and detail (not parent) values.
Step 1 – Set the parameters
Open GL Account Upload in Blitz Report and set the parameters. The segment filters are shown with the segment names of the ledger’s chart of accounts (for example Company, Department, Account, Sub-Account, Product).
| Parameter | Meaning |
|---|---|
| Ledger | The ledger whose chart of accounts is maintained. Required. |
| Upload Mode | Create opens an empty sheet for new accounts; Create, Update downloads existing accounts for editing and lets you add new rows. Required. |
| Active Accounts Only | Yes downloads only enabled accounts that are active today. |
| <Segment>, <Segment> From, <Segment> To | Restrict the download to one segment value or a range of values, per segment. |
For a Create, Update download, restrict at least one segment so that only the accounts you want to maintain are downloaded. Summary accounts are not downloaded.
Step 2 – Run to download the Excel file
Click Run. The Excel file downloads and opens with one row per account, showing the Concatenated Segments, the Description built from the segment value descriptions, the Account Type, each segment in its own column and the maintenance attributes.
Step 3 – Enter or change the accounts
- Existing account – change Enabled, Start Date Active, End Date Active, Detail Posting Allowed or Detail Budgeting Allowed. The row is marked Update.
- New account – on an empty row enter the full account in Concatenated Segments, using the chart of accounts’ segment separator. The segment columns and the Description fill in automatically and the row is marked Create.
The segment columns, Account Type and Summary cannot be edited. A new account takes its account type and its enabled, active date and detail flag settings from the segment values, as when it is created in Oracle; change them afterwards with an update if needed. The Description is derived from the segment values and is not uploaded.
Step 4 – Validate and Save
Click Validate and Save. This checks for missing required values and, for new accounts, checks every segment value: missing, invalid, disabled, not yet active, expired or parent values are flagged on the row. Correct any flagged rows; the file is saved for upload.
Step 5 – Upload the file
In Blitz Report click Upload and select the saved file. This submits the upload request, which creates the new code combinations, applying your cross-validation rules, and updates the changed accounts.
Step 6 – Review the result report
When the request completes, a result report opens listing every row with its status and message, and the account values as stored in General Ledger, including the account type and attributes of the created accounts.
What’s produced
- New code combinations in the ledger’s chart of accounts, and updated attributes of existing ones.
- A result report listing every row with a status (success or error) and a message.
Common questions
How does it decide between create and update?
The concatenated segments are matched against the existing accounts of the chart of accounts. A match is updated; otherwise the account is created.
Does my chart of accounts need to allow dynamic insertion?
No. When dynamic insertion is disabled, the upload still creates the account after full validation, including cross-validation rules.
Can I delete or rename an account?
No. Accounts cannot be deleted, and the segments identify the account. Disable the account or end-date it instead.
Why does a row show “No change.”?
The row was marked Update but its values equal the stored ones, so nothing was updated.
Can I maintain the account descriptive flexfield?
Yes. The upload supports the Attribute Context and GL Account Attribute columns, but the Default template does not include them; add them to a template of your own with Edit Template.
Troubleshooting
| Message | Cause | What to do |
|---|---|---|
| Missing value for segment : <segment> | A segment of the chart of accounts has no value on the row. | Enter the complete account in Concatenated Segments. |
| Invalid value <value> for segment <segment>. | The value does not exist in the segment’s value set. | Use an existing segment value. |
| Segment value <value> for <segment> is disabled / is not yet active / has expired. | The value is disabled or outside its active dates. | Use an enabled, currently active value, or correct the value set. |
| Segment value <value> for <segment> is a parent value and cannot be used in transactions. | A parent value was used. | Use a detail (child) value. |
| Cross Validation Rule: <rule message> | The combination violates a cross-validation rule. | Correct the combination, or the rule if the account is legitimate. |
| Account was not created | The combination failed validation without a specific message. | Check the segment values and cross-validation rules for the account. |
SQL 62 lines
select to_char(null) action_, to_char(null) status_, to_char(null) message_, null modified_columns_, gl.name ledger, gcck.concatenated_segments, gl_flexfields_pkg.get_concat_description(gl.chart_of_accounts_id,gcck.code_combination_id) description, ffvv.description account_type, gcck.segment1 gl_segment1, gcck.segment2 gl_segment2, gcck.segment3 gl_segment3, gcck.segment4 gl_segment4, gcck.segment5 gl_segment5, gcck.segment6 gl_segment6, gcck.segment7 gl_segment7, gcck.segment8 gl_segment8, gcck.segment9 gl_segment9, gcck.segment10 gl_segment10, gcck.segment11 gl_segment11, gcck.segment12 gl_segment12, gcck.segment13 gl_segment13, gcck.segment14 gl_segment14, gcck.segment15 gl_segment15, xxen_util.meaning(gcck.summary_flag,'YES_NO',0) summary, xxen_util.meaning(gcck.enabled_flag,'YES_NO',0) enabled, gcck.start_date_active, gcck.end_date_active, xxen_util.meaning(gcck.detail_budgeting_allowed,'YES_NO',0) detail_budgeting_allowed, xxen_util.meaning(gcck.detail_posting_allowed,'YES_NO',0) detail_posting_allowed, xxen_util.display_flexfield_context(101,'GL_CODE_COMBINATIONS',gcck.context) attribute_context, xxen_util.display_flexfield_value(101,'GL_CODE_COMBINATIONS',gcck.context,'ATTRIBUTE1',gcck.rowid,gcck.attribute1) gl_account_attribute1, xxen_util.display_flexfield_value(101,'GL_CODE_COMBINATIONS',gcck.context,'ATTRIBUTE2',gcck.rowid,gcck.attribute2) gl_account_attribute2, xxen_util.display_flexfield_value(101,'GL_CODE_COMBINATIONS',gcck.context,'ATTRIBUTE3',gcck.rowid,gcck.attribute3) gl_account_attribute3, xxen_util.display_flexfield_value(101,'GL_CODE_COMBINATIONS',gcck.context,'ATTRIBUTE4',gcck.rowid,gcck.attribute4) gl_account_attribute4, xxen_util.display_flexfield_value(101,'GL_CODE_COMBINATIONS',gcck.context,'ATTRIBUTE5',gcck.rowid,gcck.attribute5) gl_account_attribute5, xxen_util.display_flexfield_value(101,'GL_CODE_COMBINATIONS',gcck.context,'ATTRIBUTE6',gcck.rowid,gcck.attribute6) gl_account_attribute6, xxen_util.display_flexfield_value(101,'GL_CODE_COMBINATIONS',gcck.context,'ATTRIBUTE7',gcck.rowid,gcck.attribute7) gl_account_attribute7, xxen_util.display_flexfield_value(101,'GL_CODE_COMBINATIONS',gcck.context,'ATTRIBUTE8',gcck.rowid,gcck.attribute8) gl_account_attribute8, xxen_util.display_flexfield_value(101,'GL_CODE_COMBINATIONS',gcck.context,'ATTRIBUTE9',gcck.rowid,gcck.attribute9) gl_account_attribute9, xxen_util.display_flexfield_value(101,'GL_CODE_COMBINATIONS',gcck.context,'ATTRIBUTE10',gcck.rowid,gcck.attribute10) gl_account_attribute10, gcck.code_combination_id, to_number(null) upload_row from gl_code_combinations_kfv gcck, gl_code_combinations_kfv gccka, fnd_flex_values_vl ffvv, fnd_flex_value_sets ffvs, fnd_id_flex_structures_tl fifs, gl_ledgers gl where 1=1 and gl.chart_of_accounts_id=gcck.chart_of_accounts_id and gcck.gl_account_type=ffvv.flex_value and ffvv.flex_value_set_id=ffvs.flex_value_set_id and ffvs.flex_value_set_name='GL_SRS_ACCOUNT_TYPE' and gcck.alternate_code_combination_id=gccka.code_combination_id(+) and fifs.id_flex_num=gcck.chart_of_accounts_id and fifs.application_id=101 and fifs.id_flex_code='GL#' and fifs.language=userenv ('lang') and nvl(gcck.summary_flag,'N')<>'Y' |
Parameters 37
| Parameter | Type | List of values SQL | |
|---|---|---|---|
| Ledger | LOV |
| |
| Upload Mode | LOV |
| |
| Active Accounts Only | LOV |
| |
| GL_SEGMENT1 | LOV |
| |
| GL_SEGMENT1 From | LOV |
| |
| GL_SEGMENT1 To | LOV |
| |
| GL_SEGMENT2 | LOV |
| |
| GL_SEGMENT2 From | LOV |
| |
| GL_SEGMENT2 To | LOV |
| |
| GL_SEGMENT3 | LOV |
| |
| GL_SEGMENT3 From | LOV |
| |
| GL_SEGMENT3 To | LOV |
| |
| GL_SEGMENT4 | LOV |
| |
| GL_SEGMENT4 From | LOV |
| |
| GL_SEGMENT4 To | LOV |
| |
| GL_SEGMENT5 | LOV |
| |
| GL_SEGMENT5 From | LOV |
| |
| GL_SEGMENT5 To | LOV |
| |
| GL_SEGMENT6 | LOV |
| |
| GL_SEGMENT6 From | LOV |
| |
| GL_SEGMENT6 To | LOV |
| |
| GL_SEGMENT7 | LOV |
| |
| GL_SEGMENT7 From | LOV |
| |
| GL_SEGMENT7 To | LOV |
| |
| GL_SEGMENT8 | LOV |
| |
| GL_SEGMENT8 From | LOV |
| |
| GL_SEGMENT8 To | LOV |
| |
| GL_SEGMENT9 | LOV |
| |
| GL_SEGMENT9 From | LOV |
| |
| GL_SEGMENT9 To | LOV |
| |
| GL_SEGMENT10 | LOV |
| |
| GL_SEGMENT10 From | LOV |
| |
| GL_SEGMENT10 To | LOV |
| |
| GL_SEGMENT11 From | LOV |
| |
| GL_SEGMENT11 To | LOV |
| |
| GL_SEGMENT12 From | LOV |
| |
| GL_SEGMENT12 To | LOV |
|





