Data element |
Definition |
CONTACT_EMAIL
Indexed - no
Format - varchar2(50)
May be null? yes |
The email address of the contact person for the work request.
Facility Focus source: ae_p_pro_e.contact_mc
|
CONTACT_NAME
Indexed - no
Format - varchar2(25)
May be null? yes |
The Point of Contact (POC) for the work to be completed.
Facility Focus source: ae_p_pro_e.contact
|
CONTACT_PENN_ID
Indexed - yes
Format - varchar2(8)
May be null? yes |
For work requests generated via customer requests, this field containts the Penn ID of the contact person for the work request; for work requests from other sources, the value will be null.
Facility Focus source: ae_p_req_e.login
|
CONTACT_PHONE
Indexed - no
Format - varchar2(15)
May be null? yes |
The phone number of the contact person for the work request.
Facility Focus source: ae_p_pro_e.contact_ph
|
CONT_SVCS_COST_EST
Indexed - no
Format - number(18,4)
May be null? yes |
Estimated contracted services cost, at the phase level.
Facility Focus source: ae_p_phs_e.tot_oth
|
CUSTOMER_ORG
Indexed - yes
Format - char(4)
May be null? yes |
The organization code associated with the work request. For work requests initiated by students, this column will be null.
Facility Focus source: ae_p_pro_e.requestor
|
CUSTOMER_PENN_ID
Indexed - yes
Format - varchar2(8)
May be null? yes |
The student Penn ID associated with the work request. For work requests initiated by faculty or staff, this column will be null.
Facility Focus source: ae_p_pro_e.requestor |
HISTORY_STATUS
Indexed - no
Format - char(1)
May be null? yes |
The 1-character code that indicates whether the WORK_REQUEST_PHASE_HISTORY record is Current (C) or History (H). Records with a History_Status of "C"
reproduce the WORK_REQUEST_PHASE records as they currently exist in the Facility Focus
system. Records with a History_Status of "H" represent earlier
versions of the data. (See also History_Status_Date.)
Values:
C Current (that is, the most recent in
the Facility Focus system)
H History
|
HISTORY_STATUS_DATE
Indexed - yes
Format - date
May be null? no |
Date on which the record became history, generated upon the record load to the Warehouse.
|
LABOR_COST_EST
Indexed - no
Format - number(18,4)
May be null? yes |
Estimated labor cost, at the phase level.
Facility Focus source: ae_p_phs_e.tot_lab
|
LABOR_HR_EST
Indexed - no
Format - number(18,4)
May be null? yes |
Estimated labor hours, at the phase level.
Facility Focus source: ae_p_phs_e.tot_hrs
|
MATERIALS_COST_EST
Indexed - no
Format - number(18,4)
May be null? yes |
Estimated materials cost, at the phase level.
Facility Focus source: ae_p_phs_e.tot_mat
|
PART_CODE
Indexed - no
Format - varchar2(25)
May be null? no |
An equipment class defined for a group of unique assets that are serviced at scheduled intervals.
|
PHASE
Indexed - yes
Format - varchar2(15)
May be null? no |
Phases define the tasks and costs involved in performing the requested work. Each phase is associated with one trade or housekeeping shop. Although not mandatory, phase one should occur before phase two, and so on, as a logical way of ordering the steps in a job. The number of phases in a single work request is unlimited.
Facility Focus source: ae_p_phs_e.sort_code
|
PHASE_ACCOUNTING_PERIOD_CLOSED
Indexed - yes
Format - varchar2(6)
May be null? yes |
The GL accounting period in which the phase was closed. This column will be populated based on the PHASE_CLOSED_DATE, which will be populated for any phases with status of 70 or greater (cancelled, complete, or closed).
|
PHASE_CLOSED_DATE
Indexed - no
Format - date
May be null? yes |
The date on which the phase was closed. This column will be populated with the PHASE_STATUS_DATE for any phases with status of 70 or greater (cancelled, complete, or closed).
|
PHASE_DESC
Indexed - no
Format - varchar2(70)
May be null? yes |
The explanation of the task required for each particular phase.
Facility Focus source: ae_p_phs_e.phsdsc
|
PHASE_EST_END_DATE
Indexed - no
Format - date
May be null? yes |
Estimated end date for the work defined in that phase.
Facility Focus source: ae_p_phs_e.end_date
|
PHASE_EST_START_DATE
Indexed - no
Format - date
May be null? yes |
Estimated start date for the work defined in that phase.
Facility Focus source: ae_p_phs_e.beg_date
|
PHASE_FISCAL_MONTH_CLOSED
Indexed - yes
Format - varchar2(2)
May be null? yes |
The fiscal month sequence in which the phase was closed. This column will be populated based on the PHASE_CLOSED_DATE, which will be populated for any phases with status of 70 or greater (cancelled, complete, or closed).
|
PHASE_FLOOR
Indexed - no
Format - char(8)
May be null? yes |
Identifies the floor within the building associated with the work request.
Facility Focus source: ae_p_phs_e.flr_id
|
PHASE_FY_CLOSED
Indexed - no
Format - varchar2(4)
May be null? yes |
The fiscal year in which the phase was closed. This column will be populated based on the PHASE_CLOSED_DATE, which will be populated for any phases with status of 70 or greater (cancelled, complete, or closed).
|
PHASE_PRIORITY
Indexed - yes
Format - varchar2(10)
May be null? yes |
Estimated end date for the work defined in that phase.
Facility Focus source: ae_p_phs_e.end_date
|
PHASE_ROOM
Indexed - no
Format - char(16)
May be null? yes |
Estimated start date for the work defined in that phase.
Facility Focus source: ae_p_phs_e.beg_date
|
PHASE_STATUS
Indexed - yes
Format - varchar2(10)
May be null? yes |
The status of the phase. Statuses are defined by FRES based on the way work is processed within the organization. Statuses are selected by the authorized user of the system as the work changes from first being accepted to lastly being closed out. Statuses are specific to each category of work in the Work Management module, such as maintenance, corrective, or events, and thus mirror a specific workflow process. The work request itself has a set of statuses as does each phase.
Facility Focus source: ae_p_pro_e.status_code
|
PHASE_STATUS_DATE
Indexed - no
Format - date
May be null? yes |
The date on which the phase status went into effect.
|
PROBLEM_CODE
Indexed - yes
Format - varchar2(5)
May be null? yes |
A code which helps define the situation involved in the request for work.
Facility Focus source: ae_p_phs_e.problem_code |
SHOP
Indexed - yes
Format - varchar2(15)
May be null? yes |
The trade (e.g., CARP, AC, ELEC) to which the phase has been assigned.
Facility Focus source: ae_p_phs_e.shop
|
WORK_CODE
Indexed - yes
Format - varchar2(15)
May be null? yes |
An identifier of the kind of work to be performed, such as core change, filters, etc. It is the granularity of a skilled set or craft.
Facility Focus source: ae_p_phs_e.craft_code
|
WR_ACCOUNTING_PERIOD_CLOSED
Indexed - yes
Format - varchar2(6)
May be null? yes |
The GL accounting period in which the work request as a whole was closed. This column will be populated based on the WR_CLOSED_DATE, which will be populated for any work requests with status of 70 or greater (cancelled, complete, or closed).
|
WR_ACCOUNTING_PERIOD_CREATED
Indexed - yes
Format - varchar2(6)
May be null? yes |
The GL accounting period in which the work request was created.
|
WR_CLOSED_DATE
Indexed - no
Format - date
May be null? yes |
The date on which the work request as a whole was closed. This column will be populated based on the WR_STATUS_DATE, which will be populated for any work requests with status of 70 or greater (cancelled, complete, or closed).
|
WR_BUILDING_CODE
Indexed - yes
Format - char(16)
May be null? yes |
The unique identifier of the building site that requires the work being requested.
Facility Focus source: ae_p_pro_e.bldg
|
WR_CATEGORY
Indexed - yes
Format - varchar2(5)
May be null? yes |
A grouping of types of work requests. Example categories are Corrective Maintenance, Events and Small Projects.
Facility Focus source: ae_p_pro_e.category
|
WR_ENTRY_DATE
Indexed - no
Format - date
May be null? yes |
The date the work request was originally created.
Facility Focus source: ae_p_pro_e.ent_date
|
WR_FISCAL_MONTH_CLOSED
Indexed - yes
Format - varchar2(2)
May be null? yes |
The fiscal month sequence in which the work request as a whole was closed. This column will be populated based on the WR_CLOSED_DATE, which will be populated for any work requests with status of 70 or greater (cancelled, complete, or closed).
|
WR_FISCAL_MONTH_CREATED
Indexed - yes
Format - varchar2(2)
May be null? yes |
The fiscal month sequence in which the work request was created.
|
WR_FY_CLOSED
Indexed - no
Format - varchar2(4)
May be null? yes |
The fiscal year in which the work request as a whole was closed. This column will be populated based on the WR_CLOSED_DATE, which will be populated for any work requests with status of 70 or greater (cancelled, complete, or closed).
|
WR_FY_CREATED
Indexed - no
Format - varchar2(4)
May be null? yes |
The fiscal year in which the work request was created.
Facility Focus source: ae_p_pro_e.program_fy
|
WR_NUMBER
Indexed - yes
Format - varchar2(15)
May be null? no |
The unique number for the work request. It is the number the customer will receive, via email from a FRES customer service rep, letting him/her know that the work has been approved and is going to be placed on a schedule. It remains with the work request through its life.
Facility Focus source: ae_p_pro_e.proposal
|
WR_STATUS
Indexed - yes
Format - varchar2(10)
May be null? yes |
The status of the work request as a whole. Statuses are defined by FRES based on the way work is processed within the organization. Statuses are selected by the authorized user of the system as the work changes from first being accepted to lastly being closed out. Statuses are specific to each category of work in the Work Management module, such as maintenance, corrective, or events, and thus mirror a specific workflow process. The work request itself has a set of statuses as does each phase.
Facility Focus source: ae_p_pro_e.status_code
|
WR_STATUS_DATE
Indexed - no
Format - date
May be null? yes |
The date on which the work request status went into effect.
|
WR_TITLE
Indexed - yes
Format - varchar2(40)
May be null? yes |
A description of the situation. For example, ‘my bathroom sink is clogged’. If this is a request for chargeable work, the account that is being charged is also in this field.
Facility Focus source: ae_p_pro_e.title
|
WR_TYPE
Indexed - yes
Format - varchar2(1)
May be null? yes |
The type denotes the funding source of the request. Most maintenance requests are Type N or non-allocated cost. There is no direct charge to the client. If work is performed in a customer owned building, the Type is C or COM for customer. If your request requires that you pay for the work requested, it will be Type P or CPW for customer paid work.
Facility Focus source: ae_p_pro_e.order_type
|