Versions Compared

Old Version 16

changes.mady.by.user Former user

Saved on

compared with

New Version 17

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

his view contains the all of the transactions posted below UCSD General Ledger at the interface level.

  • This view contains only transactions that have posted.  This does not include pre-posted, unposted, not approved transactions, not posted, and/or un-processed costs.

(info) In order to see the General Ledger data within Oracle UI you'll need access to General Accounting Dashboard > Inquiry and Analysis Balances

Data Loads:

Data is loaded nightly from oracle.  To see when the data completed being loaded by UCSD into FINAH see this report:Tableau > Public > AH Data Load Status Report

Granularity:

Granularity is the scale or level of detail present in a set of data.  It identifies where levels of uniqueness exists in the data.  The data lives in the view at the lowest level, but each BI tool totals the levels differently.

Please note:  The Level of Detail (LOD) calculations listed here for Tableau developers are a baseline and do not necessary include all of the LOD equations needed for your report.


LevelKey (uniqueness / group by)Measure
1CCOA Levels

There are multiple groups of fields that live at a higher grain than the Transaction Line.  These groups are not part of a hierarchy and should be considered separately.

If you use the measures from this group you will see them repeat with combined with lower grain data.

Example:

Tableau report developers:  {FIXED[Entity Code]: MIN([Entity Is Current Count])}

Be sure to use the matching fields.

{FIXED[% Code]: MIN([% Is Current Count])}


All measures in the Flag Measures folder
2Transaction Line

Transaction Header Code + Transaction Line Code

Tableau report developers: {FIXED[Transaction Header Code], [Transaction Line Code]: MIN([Transaction...])}

All measures starting with Transaction%
3SLA Line

SLA Event ID + SLA Event Header ID + SLA Event Line Number

Lowest level, no LOD needed.

All measures starting with SLA%


Key Fields to View:

  • Account
  • Accounting Period
  • Activity
  • Award
  • Award Fiscal Manger
  • Award Fund Manager
  • Award MSO DBO CAO
  • Award Principal Investigator
  • Award Project Manager
  • Entity
  • Expenditure
  • Financial Unit
  • Function
  • Fund
  • Future
  • General Ledger
  • Journal
  • Location
  • Managerial Reporting Account Hierarchy
  • Managerial Reporting Fund Hierarchy
  • Program
  • Project
  • SLA Event

Key Fields Filter on:

  • Accounting Period
  • Ledger Encumbrance Type
  • SLA Event ID
  • SLA Event Header ID
  • SLA Event Line Number
  • Transaction Header Code
  • Transaction Line Code



Additional Notes:



Ui expand
titleDate Fields Description

Date Fields Description

  • Batching Accounting Date is coming from GL_JE_SOURCES.DEFAULT_EFFECTIVE_DATE 
  • Batch Posting Date is the date which is originally posted via the batch.
  • Transaction Creation Timestamp is the timestamp of the transaction when it is created.
  • Transaction Date is the date for the transaction (most users should use this date)
  • Transaction Effective Date is the effective date of the transaction.
  • Transaction System Date Time is the date that the transaction is physically entered into the system.  This date is more helpful for ITS team internal use for troubleshooting.


Ui expand
titleOracle Set Up Scenario

We sometimes see a setup scenario in OFC where a sponsored project is assigned to more than one award. This seems to happen when they increment the award version from -00001 to -00002.

If there are two records with the same base number then always select the -0002 record.