| Data element |
Definition |
| ACCOUNTING_PERIOD
Indexed - yes
Format - varchar2(6)
May be null? Yes
|
The Accounting Period stated in MON-YY format. MON is the calendar month (stored in upper case), and YY is the calendar year. Note that the beginning and ending dates of an ACCOUNTING_PERIOD are not the same as the first and last day of the calendar month.
Example: JUL-08 (July 2008, which occurs in fiscal year 2009).
Values:
List of values not available.
|
| BASIS_CURRENCY_CODE
Indexed - no
Format - varchar2(5)
May be null? Yes |
Denotes the currency of the Basis Value. |
| BASIS_VALUE
Indexed - no
Format – number(31,9)
May be null? Yes
|
Denotes the monetary amount used to determine the amount of a charge. For instance, this may include the declared value of an item. |
| CALENDAR_MONTH
Indexed - yes
Format - varchar2(2)
May be null? Yes
|
The number that identifies the calendar month (or accounting period).
Example: 01 (January); 11 (November).
Values:
01 January
02 February
03 March
04 April
05 May
06 June
07 July
08 August
09 September
10 October
11 November
12 December
13 Adjustment period |
| CALENDAR_YEAR
Indexed - yes
Format – varchar2(4)
May be null? Yes
|
The calendar year for the ACCOUNTING_PERIOD. The calendar year begins January 1 and ends December 31.
Example: 2008 (the CALENDAR_YEAR for ACCOUNTING_PERIOD JUL-2009).
Values:
List of values not available.
|
| CHARGED_UNIT_QUANTITY
Indexed - no
Format - varchar2(10)
May be null? Yes
|
The number of times the charge detailed in charge description is being applied. For instance, this may include the number of Address Corrections applied to a shipment. |
| CHARGE_CLASSIFICATION_CODE
Indexed - no
Format – varchar2(5)
May be null? Yes
|
FRT Transportation Charges
GOV Government Charges
BRK Brokerage Charges
ACC Accessorial Charges
FSC Fuel Surcharges
TAX Taxes
EXM Exemptions
MSC Miscellaneous Charges
(Blank) Data Unavailable
|
| CHARGE_DESCRIPTION
Indexed - no
Format - varchar2(100)
May be null? Yes
|
Contains a textual description of the Charge Description Code.
|
| CHARGE_DESCRIPTION_CODE
Indexed - no
Format – varchar2(10)
May be null? Yes
| Denotes the code associated with the charge.
|
| COA_ACCOUNT
Indexed - yes
Format – varchar2(26)
May be null? Yes
|
The 26-digit account used in the allocation transaction. The COA_Account consists of seven segments:
COA_BC
COA_CNAC
COA_CREF
COA_FUND
COA_OBJECT
COA_ORG
COA_PROGRAM
COA_RESPONSIBLE_ORG See also the definitions for
COA_BC
COA_CNAC
COA_CREF
COA_FUND
COA_OBJECT
COA_ORG
COA_PROGRAM
COA_RESPONSIBLE_ORG |
| COA_BC
Indexed - yes
Format – varchar2(1)
May be null? Yes
|
The budgetary control (BC) code used in the allocation transaction.
|
| COA_CNAC
Indexed - yes
Format – varchar2(3)
May be null? Yes
| The 3-character center net asset class (CNAC) code used in the allocation transaction.
|
| COA_CREF
Indexed - yes
Format – varchar2(4)
May be null? Yes
| The 4-character Center Reference (CREF) code used in the allocation transaction.
|
| COA_FUND
Indexed - yes
Format – varchar2(6)
May be null? Yes
|
The 6-character fund number used in the allocation transaction.
|
| COA_OBJECT
Indexed - yes
Format – varchar2(4)
May be null? Yes
|
The 4-character object code used in the allocation transaction.
|
| COA_ORG
Indexed - yes
Format – varchar2(4)
May be null? Yes
| The 4-character organization code used in the allocation transaction.
|
| COA_PROGRAM
Indexed - yes
Format – varchar2(4)
May be null? Yes
|
The 4-character program code used in the allocation transaction.
|
| COA_RESPONSIBLE_ORG
Indexed - yes
Format – varchar2(4)
May be null? Yes
|
The 4-character code for the organization responsible for managing the fund used in the allocation transaction.
|
| CURRENCY_CODE
Indexed - no
Format – varchar2(5)
May be null? Yes
|
Denotes the currency type associated with monetary amounts within the file.
|
| DEFAULT_COA_ACCOUNT
Indexed - yes
Format – varchar2(26)
May be null? Yes
|
The 26-digit account used in the allocation transaction. The Default_COA_Account consists of seven segments:
DEFAULT_COA_BC
DEFAULT_COA_CNAC
DEFAULT_COA_CREF
DEFAULT_COA_FUND
DEFAULT_COA_OBJECT
DEFAULT_COA_ORG
DEFAULT_COA_PROGRAM
DEFAULT_COA_RESPONSIBLE_ORG See also the definitions for
DEFAULT_COA_BC
DEFAULT_COA_CNAC
DEFAULT_COA_CREF
DEFAULT_COA_FUND
DEFAULT_COA_OBJECT
DEFAULT_COA_ORG
DEFAULT_COA_PROGRAM
DEFAULT_COA_RESPONSIBLE_ORG
|
| DEFAULT_COA_BC
Indexed - yes
Format – varchar2(1)
May be null? Yes
|
The budgetary control (BC) code used in the allocation transaction.
|
| DEFAULT_COA_CNAC
Indexed - yes
Format – varchar2(3)
May be null? Yes
|
The 3-character center net asset class (CNAC) code used in the allocation transaction.
|
| DEFAULT_COA_CREF
Indexed - yes
Format – varchar2(4)
May be null? Yes
| The 4-character Center Reference (CREF) code used in the allocation transaction.
|
| DEFAULT_COA_FUND
Indexed - yes
Format – varchar2(6)
May be null? Yes
|
The 6-character fund number used in the allocation transaction.
|
| DEFAULT_COA_OBJECT
Indexed - yes
Format – varchar2(4)
May be null? Yes
|
The 4-character object code used in the allocation transaction.
|
| DEFAULT_COA_ORG
Indexed - yes
Format – varchar2(4)
May be null? Yes
|
The 4-character organization code used in the allocation transaction.
|
| DEFAULT_COA_PROGRAM
Indexed - yes
Format – varchar2(4)
May be null? Yes
| The 4-character program code used in the allocation transaction.
|
DEFAULT_COA_RESPONSIBLE_ORG
Indexed - yes
Format – varchar2(4)
May be null? Yes
|
The 4-character code for the organization responsible for managing the fund used in the allocation transaction.
|
| EXTRACT_DATE
Indexed - no
Format - date
May be null? Yes
|
Represents the day that data was successfully extracted from the Express Mail application and fed to the General Ledger and then to the Data Warehouse.
|
| FISCAL_MONTH_SEQ
Indexed - yes
Format – varchar2(2)
May be null? Yes
|
The month (or accounting period) of the fiscal year. This field is used for sorting.
Examples: 01 (July); 11 (May). See also FISCAL_YEAR
Values:
01 July
02 August
03 September
04 October
05 November
06 December
07 January
08 February
09 March
10 April
11 May
12 June
13 Adjustment period
|
| FISCAL_YEAR
Indexed - yes
Format – varchar2(4)
May be null? Yes
| The financial year in which the ACCOUNTING_PERIOD falls. Penn's fiscal year begins July 1 of one calendar year and ends June 30 of the next calendar year.
Example: 2008 (fiscal year that began July 1, 2007, and ended June 30, 2008)
Values:
List of values not available.
|
| HIBERNATE_ID
Indexed - yes
Format - number(12)
May be null? Yes
|
A sequence of numbers used to uniquely identify a row within the table.
|
| PACKAGE_CHARGE_ID
Indexed - yes
Format - number(12)
May be null? Yes
| Unique identifier of each package.
|
| PENN_AMOUNT
Indexed - no
Format - number(25,2)
May be null? Yes
| Associated charge for each shipment.
|
| PENN_LAWSON_CODE
Indexed - no
Format – varchar2(6)
May be null? Yes
| Utilized by UPHS for the purposes of aligning costs appropriately within their Lawson System.
|
| SCALE_WEIGHT
Indexed - no
Format - number(10,1)
May be null? Yes
| Package weight measured utilizing a standard scale.
|
| SCALE_WEIGHT_UOM
Indexed - no
Format – varchar2(5)
May be null? Yes
|
Identifies the unit of measure utilized when weighing a package.
|
| TAX_INDICATOR
Indexed - no
Format – varchar2(5)
May be null? Yes
| Indicates whether or not a tax has been applied to a transaction.
|
| TRANSACTION_MASTER_ID
Indexed - yes
Format - number(12)
May be null? No
| A sequence of numbers used to uniquely identify a transaction.
|
