/mcpSchedule_Import, on page 430 contains the actual scheduling data for various time periods. Schedule_Import_Real_Time, on page 432 contains the scheduling data that is currently in effect. Schedule_Source, on page 438 indicates where the data are imported from. Schedule_Map, on page 434 gives the primary key value for the scheduling data in the source. ICR_View, on page 271 indicates how the Schedule Import records for a schedule are to be interpreted. View_Column, on page 606 indicates how to interpret each field in Schedule Import Import_Schedule, on page 282 defines import processes to be run automatically at specified times. Import_Log, on page 273 contains information about these import processes. A schedule may recur daily, weekly, monthly, etc. The Recurring Schedule Map describes a recurrence pattern for a schedule. Script Tables To see an illustration and a list of all tables in the Script category, see Script, on page 629. The Unified CCE classifies each incoming call into a Call Type (see Call_Type, on page 112) based on a Dialed Number Map (see Dialed_Number_Map, on page 217). The mapping considers the dialed number, caller-entered digits, and calling line ID. The calling line ID can be specified as a specific number, a wildcard, or a Region (see Region, on page 370) composed of Prefixes. Each routing client may have a Default Call Type (see Default_Call_Type, on page 209). A script is a series of steps performed to determine the best route for a call or to perform periodic administrative actions. You can create several versions of each script. General information about each script is stored in the Master Script (see Master_Script, on page 302). Specific information about each version is stored in the Script (see Script, on page 441). The binary representation of the script version is stored in the Script Data (see Script_Data, on page 444) table. Each Script version has a Cross Reference for each database entity that it references. A Call Type Map (see Call_Type_Map, on page 128) associates one or more routing scripts to the call type based on a schedule of when each script is active. An Admin Script Schedule Map (see Admin_Script_Schedule_Map, on page 14) schedules a periodic administrative script. For each script version, Real Time and Five-Minute data are produced. Also, Real-Time data are produced for each call type. You can define User Variables (see User_Variable, on page 604) that you can set and reference in scripts. Optionally, you can define Persistent Variables (see Persistent_Variable, on page 342) that retain their values between script invocations. You can also define custom functions that are stored as User Formulas (see User_Formula, on page 597). The expression associated with a custom function is stored in User Formula Equation (see User_Formula_Equation, on page 598). With the optional Gateway feature, a script can communicate with an external application. An Application Gateway (see Application_Gateway, on page 84) represents such an external application. Each side of the Central Controller can maintain a separate Connection for each Application Gateway. Unified CCE software also maintains Global default values for Application Gateway connections. Half-hour data are produced for each Application Gateway. With the optional Gateway SQL feature, a script can query an external database. The tables that can be accessed are stored in Script Table (see Script, on page 441) and the specific columns in Script Table Column (see Script_Table_Column, on page 449). Database Schema Handbook for Cisco Unified Contact Center Enterprise, Release 15.0(1) 701 Database Rules Script Tables