GL Summary Account Upload
GL Summary Account Upload creates and deletes GL summary account templates from Excel – the rollup definitions you would otherwise set up one at a time in the GL Summary Accounts form. For each row the upload writes the template and then runs Oracle’s standard Add/Delete Summary Accounts program to generate or remove the underlying summary accounts.
When to use it
- Mass-create summary account templates for a ledger in one pass.
- Roll out a standard set of summary templates across several ledgers (run once per ledger).
- Add rollups for a new rollup group or segment hierarchy across many combinations.
- Bulk-delete obsolete summary templates.
Before you start
- Blitz Report is installed and you are signed in to a General Ledger responsibility with access to the target ledger.
- The rollup groups and segment hierarchies you reference already exist in the chart of accounts.
- The Add/Delete Summary Accounts program and its concurrent managers are available – the upload submits it and waits for it.
Step 1 – Set the parameter and download
In Blitz Report, open GL Summary Account Upload and choose the Ledger (limited to your GL access set). Run the upload to download and open the Excel file – it includes the ledger’s existing summary templates for reference.
Step 2 – Define the summary templates
Each row is one summary template. Enter the Template Name, the Earliest Period and a Description, and a segment type for each GL Segment column – a rollup group, a segment hierarchy, or detail / all, per account segment. Set Add Or Delete to Add to create the template, or Delete to remove an existing one. The optional budgetary-control columns (Funds Check Level, Debit Or Credit, Amount Type, Boundary, Funding Budget) set up summary-level funds checking when all of them are supplied together.
Step 3 – Validate and Save
Click Validate and Save. This checks for missing required values and validates your segment values against the chart of accounts, then saves the file. Correct anything it flags before continuing.
Step 4 – Upload and view the result
Back in Blitz Report, click Upload and select your saved file. This submits the Blitz Upload request, which writes each template and then runs Oracle’s Add/Delete Summary Accounts program to generate or remove the summary accounts, waiting for it to finish. When it completes, a result report opens showing each row as success or error.
What’s produced
- Summary account templates created or deleted in the chosen ledger, with the underlying summary accounts generated or removed by Oracle’s Add/Delete Summary Accounts program.
- A result report listing every row with a status and a message, including the Oracle request id for each template.
Common questions
Does it actually generate the summary accounts, or just the template?
Both. It writes the template, then runs Oracle’s Add/Delete Summary Accounts program, which generates (or removes) the underlying summary accounts. The row’s status reflects how that program finished.
How does it know whether a row is new or existing?
By matching the ledger plus the exact set of segment-type values – not by the template name. An exact match is treated as the same template.
What is the difference between Add and Delete?
Add creates a new template (or refreshes a matching active one); Delete marks a matching existing template for removal. Delete on a row that matches no template is rejected.
Why didn’t my budgetary-control options get created?
They are written only on Add, and only when all five (Funds Check Level, Debit Or Credit, Amount Type, Boundary and Funding Budget) are supplied. If any is missing the template is still created, but the budgetary-control row is skipped.
Why does each row take a while?
Each processed row submits a concurrent request and waits for it to finish before reporting status, so timing depends on your GL concurrent managers.
Troubleshooting
| Message | Cause | What to do |
|---|---|---|
| This action cannot be performed by the upload | An action/state mismatch – for example Delete on a row that matches no existing template. | Confirm the template exists for that ledger and segment-type set before deleting; use Add to create. |
| Add/Delete Summary Accounts not submitted | The concurrent request could not be submitted. | Check that the program is registered and the concurrent managers are running. |
| Add/Delete Summary Accounts completed in error | The submitted request ended in error or warning. | Open that request’s log/output to see why generation failed, fix, and re-run the row. |
| Missing or invalid segment value | A required segment is blank, or a segment value is invalid, disabled or a parent value. | Provide a valid, enabled, detail value for each enabled segment. |
select to_char(null) action_, to_char(null) status_, to_char(null) message_, null modified_columns_, to_char(null) summary_row_id, to_char(null) summary_bc_row_id, to_number(null) template_id_, to_char(null) request_id_, to_char(null) request_log, gst.template_name, to_char(null) add_or_delete, gst.description, gst.start_actuals_period_name earliest_period, gl.name ledger, gst.segment1_type gl_segment1, gst.segment2_type gl_segment2, gst.segment3_type gl_segment3, gst.segment4_type gl_segment4, gst.segment5_type gl_segment5, gst.segment6_type gl_segment6, gst.segment7_type gl_segment7, gst.segment8_type gl_segment8, gst.segment9_type gl_segment9, gst.segment10_type gl_segment10, gst.segment11_type gl_segment11, gst.segment12_type gl_segment12, gst.segment13_type gl_segment13, gst.segment14_type gl_segment14, gst.segment15_type gl_segment15, gst.segment16_type gl_segment16, gst.segment17_type gl_segment17, gst.segment18_type gl_segment18, gst.segment19_type gl_segment19, gst.segment20_type gl_segment20, gst.segment21_type gl_segment21, gst.segment22_type gl_segment22, gst.segment23_type gl_segment23, gst.segment24_type gl_segment24, gst.segment25_type gl_segment25, gst.segment26_type gl_segment26, gst.segment27_type gl_segment27, gst.segment28_type gl_segment28, gst.segment29_type gl_segment29, gst.segment30_type gl_segment30, gst.concatenated_description, flvv1.meaning funds_check_level, flvv2.description debit_or_credit, flvv3.description amount_type, flvv4.meaning boundary, gbrjv.budget_name funding_budget from gl_summary_templates gst, gl_summary_bc_options gsbo, fnd_lookup_values_vl flvv1, fnd_lookup_values_vl flvv2, fnd_lookup_values_vl flvv3, fnd_lookup_values_vl flvv4, gl_budgets_require_journals_v gbrjv, gl_ledgers gl where 1=1 and gst.status='F' and gl.ledger_id=gst.ledger_id and gst.template_id=gsbo.template_id(+) and gsbo.funding_budget_version_id=gbrjv.budget_version_id(+) and gl.ledger_id=gbrjv.ledger_id(+) and gsbo.funds_check_level_code=flvv1.lookup_code(+) and flvv1.lookup_type(+)='FUNDS_CHECK_LEVEL' and gsbo.dr_cr_code=flvv2.lookup_code(+) and flvv2.lookup_type(+)='DR_CR' and gsbo.amount_type=flvv3.lookup_code(+) and flvv3.lookup_type(+)='PTD_YTD' and gsbo.boundary_code=flvv4.lookup_code(+) and flvv4.lookup_type(+)='BOUNDARY_TYPE' |
| Parameter Name | SQL text | Validation | |
|---|---|---|---|
| Ledger |
| LOV |