| 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.
|
| 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.
|
| 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. |
| CONTAINER_TYPE
Indexed - no
Format – varchar2(5)
May be null? Yes
| Defines the type of container used for each shipment. |
| 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. |
| 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.
|
| PACKAGE_ACTUAL_QUANTITY
Indexed - no
Format - varchar2(10)
May be null? Yes
| Denotes the number of packages (pieces) contained within a shipment. |
| PACKAGE_ACTUAL_QUANTITY_UOM
Indexed - no
Format - varchar2(5)
May be null? Yes
| Unit of measure used to denote the number of packages (pieces) contained within a shipment. |
| PACKAGE_ACTUAL_WEIGHT
Indexed - no
Format - varchar2(15)
May be null? Yes
| The actual weight of a package measured by utilizing a standard scale. |
| PACKAGE_ACTUAL_WEIGHT_UOM
Indexed - no
Format – varchar2(5)
May be null? Yes
| Unit of measure used to obtain the actual weight of a package. |
| PACKAGE_BILLED_WEIGHT
Indexed - no
Format - varchar2(10)
May be null? Yes
| Denotes the billable weight used to determine the charges of a shipment. |
| PACKAGE_BILLED_WEIGHT_TYPE
Indexed - no
Format - varchar2(5)
May be null? Yes
| Denotes whether the billed weight relates to the physical weight of the shipment or to its dimensional weight. |
| PACKAGE_BILLED_WEIGHT_UOM
Indexed - no
Format - varchar2(5)
May be null? Yes
| Denotes whether the billed weight is in kilograms or pounds. |
| PACKAGE_DIMENSION_HEIGHT
Indexed - no
Format - varchar2(10)
May be null? Yes
| Denotes the height of a package when determining its dimensional weight. |
| PACKAGE_DIMENSION_LENGTH
Indexed - no
Format - varchar2(10)
May be null? Yes
| Denotes the length of a package when determining its dimensional weight. |
| PACKAGE_DIMENSION_UOM
Indexed - no
Format - varchar2(5)
May be null? Yes
| Denotes the unit of measure utilized in calculating the dimensional weight of a package. |
| PACKAGE_DIMENSION_WIDTH
Indexed - no
Format - varchar2(10)
May be null? Yes
| Denotes the width of a package when determining its dimensional weight. |
| PACKAGE_ID
Indexed - yes
Format - number(12)
May be null? No
| Unique identifier of each package. |
| PACKAGE_OVERSIZE_QUANTITY
Indexed - no
Format - varchar2(10)
May be null? Yes
| Denotes the number of packages (pieces) which were classified as either Oversize 1, 2, or 3. |
| PACKAGE_OVERSIZE_QUANTITY_UOM
Indexed - no
Format - varchar2(5)
May be null? Yes
| Unit of measure used to assess the number of packages (pieces) which are Oversized. |
| PACKAGE_REFERENCE2
Indexed - no
Format - varchar2(35)
May be null? Yes
| Contains the PennID of the shipper as well as a shipper provided description of the shipment. |
| PENN_LAST_EDITED
Indexed - no
Format - Date
May be null? Yes
| Represents the date that an Allocator allocated shipment charges from the default General Ledger account to another General Ledger account. |
| PENN_LAST_EDITED_BY
Indexed - no
Format - varchar2(8)
May be null? Yes
| Denotes the PennID of the Allocator who allocated the shipment charges. |
| 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. |
| TRACKING_NUMBER
Indexed - no
Format – varchar2(30)
May be null? Yes
| Denotes the tracking number associated with a specific charge. In the event the charge is at the shipment level, this is the lead package of the shipment. Package charges display the individual tracking number of the package. |
| TRANSACTION_MASTER_ID
Indexed - yes
Format - number(12)
May be null? Yes
| A sequence of numbers used to uniquely identify a transaction. |
| ZONE
Indexed - no
Format - varchar2(5)
May be null? Yes
| Denotes the zone number associated with the distance between the origin and destination of the shipment or package referenced in the transaction. |
