[ BEN Financials ]
510.GA: Detail Transactions By Object By Organization
Documentation :|: BEN Balances Report Documentation :|: Quick View
* Return to Quick View List
Last Updated: 12/03/97
Although the 510.GA report was originally designed to provide transaction detail to the School of Medicine to support the management and reconciliation of CPUP and area Hospital accounts, it can be a useful report for broader purposes because it lists transaction detail for a given range of accounts.
The 510.GA report lists journal entry information for actuals only -- no budget or encumbrance entries are shown. Transactions are grouped, based on the object code, into either "University Charges" or "Hospital Charges" with a sub-total labeled "Total Current Activity". These transactions are followed by a net monthly total which adjusts the Total Current Activity by any transactions in object code 1526. For a definition of "University Charges" and "Hospital Charges", see the Report Template section below.
The report will provide a page break for each unique ORGanization defined in the parameters.
The report level sort is by ORGanization in ascending order.
The primary row sort within the report is by Object Code. Within the accounting flexfield, the secondary sort is by Source and within each Source, the third level of sort is the Posted Date.
Sub-totaling occurs at the Object code level. The report displays sub-totals for University Charges, Hospital Charges, Current Activity, and Total Monthly Net. ORGanization level Beginning and Ending Balance are also displayed on the report.
No report template is used for this report. However, object parents are used to define which objects should be included in each of the transaction groupings. The following table identifies the objects used in these groupings:
1529, 1531, 1533, 1535, 1536, 1537
All object codes, except 1526 and those listed under the "Hospital Charges" category, are included in the University Charges category.
Total Monthly Net
Hospital Charges + University Charges + object code 1526.
In addition to the Accounting Period (Period Name), all seven account segments are available as parameters for account selection:
- CNAC (School/Center Net Asset Class)
- ORG (Organization)
- BC (Budget Control)
- OBJ (Object Code)
- PROG (Program)
- CREF (Center Reference)
A low to high segment value range may be entered for any of the segment parameters. Parent values for any of the segments may also be used.
The report heading includes the following information:
- Report Break:
Indicates the accounting segment the report will break on. For this report, the ORGanization segment is the report break.
- Period Ending: MMM-YY
Indicates the accounting period for which journal activity is provided. Accounting period is provided as a parameter when the report is requested.
Indicates the 4 character segment value and the segment value description for the ORGanization segment.
From left to right, the report columns provide the following information.
This column displays the originating source of the journal entry batch.
- Batch Name
This column displays the journal entry batch name.
- Accounting Flexfield
This column provides the seven segment account number to which the journal was posted.
This column displays the journal entry line description.
- HUP Cost center
If a HUP Cost center was provided as additional descriptive information on the journal entry line, it will be displayed in this column.
- Line Item
For transactions originating from Accounts Payable (source = Payables), this column displays additional line item information. For all other transactions, this column will be blank.
- Posted Date
This column displays the date the journal was posted.
- Journal Amount
This column displays the amount of the transaction. Credit amounts are identified with a CR displayed next to the amount.
Last Page Of The Report:
On the last page of every report information is provided regarding the parameters used to request the report. If the account combinations returned to you in the report are not what you expected, the report parameters list is a useful first place to start. At a minimum, you can verify the range of values you provided at the time you submitted the request.