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).

ParameterMeaning
LedgerThe ledger whose chart of accounts is maintained. Required.
Upload ModeCreate opens an empty sheet for new accounts; Create, Update downloads existing accounts for editing and lets you add new rows. Required.
Active Accounts OnlyYes downloads only enabled accounts that are active today.
<Segment>, <Segment> From, <Segment> ToRestrict 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.

Blitz Report run screen for GL Account Upload with Ledger Vision Operations (USA), Upload Mode Create, Update, Company 01, Department 000 and Account 1410

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.

Excel file with the three existing accounts 01-000-1410-0000-000, 01-000-1410-1200-000 and 01-000-1410-2111-000

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.

Detail Budgeting Allowed of 01-000-1410-1200-000 set to No, marked Update, and new account 01-000-1410-2112-000 entered in Concatenated Segments, with segments and description filled in, marked Create

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.

Both edited rows show status Valid after Validate and Save

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.

File Upload page with the saved Excel file selected for upload

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.

Result report showing the updated and the created account with status Success and the stored account type and flags

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

MessageCauseWhat 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 createdThe combination failed validation without a specific message.Check the segment values and cross-validation rules for the account.

SQL 62 lines

Parameters 37