GL Summary Account Upload
Description
GL Summary Account Upload creates and deletes GL summary account templates from Excel – the rollup definitions you would otherwise enter one at a time in the Summary Accounts window. For each row the upload writes the template and then runs Oracle’s standard Add/Delete Summary Accounts program, which generates or removes the summary accounts and their balances.
When to use it
- Create a set of summary templates for a ledger in one pass.
- Roll out a standard set of summary templates across several ledgers (one run per ledger).
- Add rollups for new rollup groups across many segment combinations.
- Delete obsolete summary templates in bulk.
Before you start
- A responsibility whose GL data access set includes the target ledger.
- The rollup groups you reference exist and are assigned to the parent values of the segment.
- The concurrent managers are running: each row submits Add/Delete Summary Accounts and waits for it to finish.
Step 1 – Set the parameters
Open GL Summary Account Upload in Blitz Report and set the parameter:
| Parameter | Meaning |
|---|---|
| Ledger | The ledger whose summary templates are downloaded and to which new templates are added. The list shows the ledgers of your GL data access set. |
Step 2 – Run to download the Excel file
Click Run. The Excel file downloads and opens with one row per completed summary template of the ledger. The segment columns are named after the ledger’s chart of accounts segments (for example Company, Department, Account).
Step 3 – Enter or change the data
Each row is one summary template. To create a template, add a row with the Template Name, the Earliest Period from which balances are maintained, an optional Description, and for every segment column a segment type: D (Detail, one summary account per detail value), T (Total, one summary account for all values) or the name of a rollup group of that segment (one summary account per parent value in the group). Add Or Delete defaults to Add, and Concatenated Description defaults to the segment types joined by the segment separator, for example T-T-Headcount-T-T.
On a downloaded row only Add Or Delete can be changed: set it to Delete to remove that template and its summary accounts. An existing template cannot be modified; delete it and add it again with the new definition.
To use summary-level funds checking, also enter Funds Check Level, Debit Or Credit, Amount Type, Boundary and Funding Budget on the new row.
Step 4 – Validate and Save
Click Validate and Save. This checks for missing required values and saves the file. Correct any rows it flags before uploading.
Step 5 – Upload the file
In Blitz Report click Upload and select the saved file. This submits the upload request, which writes each template and runs Add/Delete Summary Accounts for it, waiting for each request to finish.
Step 6 – Review the result report
When the request completes, a result report opens listing every uploaded row with its status and message. The Request Log column links to the log of the Add/Delete Summary Accounts request of each row.
What’s produced
- Summary templates added to or deleted from the ledger, with their summary accounts and balances generated or removed by Add/Delete Summary Accounts.
- A result report listing every row with a status, a message and a link to the request log.
Common questions
Does it generate the summary accounts, or only the template?
Both. After writing the template it runs Add/Delete Summary Accounts, and the row status reflects how that request completed.
How is a row matched to an existing template?
By the ledger and the exact combination of segment types, not by the template name.
Can I rename a template or change its earliest period or segment types?
No. These columns are read-only on downloaded rows. Delete the template and add it again.
Why were my funds checking options not created?
They are written only when a template is added, and only when all five values (Funds Check Level, Debit Or Credit, Amount Type, Boundary and Funding Budget) are entered. Otherwise the template is created without them.
Why does the upload take a while?
Each row submits Add/Delete Summary Accounts and waits for it to complete before the next row is processed. Templates with many detail segments over a long period range take longest.
Troubleshooting
| Message | Cause | What to do |
|---|---|---|
| This action cannot be performed by the upload. | Add on a row whose segment types match a completed template of the ledger, or Delete on a row that matches no template. | Use a combination of segment types that does not exist yet, or check the template exists before deleting it. |
| Add/Delete Summary Accounts not Submitted due to … | The concurrent request could not be submitted. | Correct the reason given in the message and upload the row again. |
| Add/Delete Summary Accounts completed in Error. Oracle request id: … | The summary account program failed. | Open the Request Log link, correct the cause and upload the row again. |
SQL 76 lines
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, to_number(null) upload_row 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' |
Parameters 2
| Parameter | Type | List of values SQL | |
|---|---|---|---|
| Ledger | LOV |
| |
| Upload Mode | LOV |
|