JTF Tables (552)
JTF - CRM Foundation — documented tables from Oracle EBS ETRM 12.2.2. Click any name for its documentation, columns and AI summary.
| Table | Columns | Description |
|---|---|---|
CAC_SR_EXCEPTIONS_B |
16 | |
CAC_SR_EXCEPTIONS_TL |
10 | |
CAC_SR_EXCP_DETAILS |
10 | This is used to store details of a template based exception |
CAC_SR_OBJECT_CAPACITY |
18 | This table is used to store availability summary. This includes (Schedules - Exception - Tasks) |
CAC_SR_PERIODS_B |
18 | This table stores non-translated data of periods |
CAC_SR_PERIODS_TL |
10 | This table stores translated data of periods |
CAC_SR_PERIOD_CATS_B |
10 | This table stores non-translated data of period category |
CAC_SR_PERIOD_CATS_TL |
11 | This table stores translated data of period category |
CAC_SR_PERIOD_DETAILS |
13 | This table stores details of a period |
CAC_SR_PERIOD_DTL_TYPES_B |
8 | This table is used to store details about period detail types. |
CAC_SR_PERIOD_DTL_TYPES_TL |
11 | This table is used to store details about period detail types. |
CAC_SR_PUBLISH_SCHEDULES |
11 | |
CAC_SR_SCHDL_DETAILS |
11 | |
CAC_SR_SCHDL_EXCEPTIONS |
9 | |
CAC_SR_SCHDL_OBJECTS |
13 | |
CAC_SR_SCHEDULES_B |
13 | |
CAC_SR_SCHEDULES_TL |
10 | |
CAC_SR_TEMPLATES_B |
12 | Base Table JTF_SR_TEMPLATES_B stores general information about a Schedule Template |
CAC_SR_TEMPLATES_TL |
10 | This tables stores translated data of a Schedule Template |
CAC_SR_TMPL_DETAILS |
12 | This table stores non translated data of a detail line of a Schedule Template |
CAC_SYNC_AGENTS |
14 | |
CAC_SYNC_ANCHORS |
11 | Stores general information about the last anchor date when sync was done for appointments/tasks/contacts |
CAC_SYNC_CONTACT_MAPPINGS |
16 | |
CAC_SYNC_MAPPINGS |
11 | Each line includes sync server and sync client mappings for each for appointments, tasks and contacts |
CAC_SYNC_MESSAGES |
10 | Each line stores truncated version of SyncML reply and response payload |
CAC_SYNC_PRINCIPALS |
9 | Stores information about client devices synced with. |
CAC_SYNC_STORE_DATA |
10 | |
CAC_VIEW_COLLAB_DETAILS |
15 | |
CAC_VIEW_COLLAB_DETAILS_TL |
10 | |
JTA_SYNC_TASK_MAPPING |
10 | Mapping table for Task Sync |
JTA_TASK_EXCLUSIONS |
10 | Stores the information of tasks/appointments excluded from a repeating series. |
JTF_ACT_ACTIVITY_CATS |
13 | This table maps activity type and categories. |
JTF_ACT_ACTIVITY_LOGS |
52 | This table is the default table to store all activities. |
JTF_ACT_APP_CATS |
12 | this table maps application and categories. |
JTF_ACT_TYPES_ATTRS_B |
11 | This table maps activity type and attributes. |
JTF_ACT_TYPES_ATTRS_TL |
12 | the translation table of jtf_act_types_attrs_b table. |
JTF_ACT_TYPES_B |
10 | Define the activity type. |
JTF_ACT_TYPES_TL |
14 | the table is the translation table of jtf_act_types_tl. |
JTF_ALERT |
15 | |
JTF_AMV_ATTACHMENTS |
54 | This table stores the documents that are attached to the JTF_AMV_ITEMS_B table. Attached files are stored in the FND_LOBS. |
JTF_AMV_ITEMS_B |
42 | Store document. |
JTF_AMV_ITEMS_TL |
13 | Stores all translated columns. |
JTF_AMV_ITEM_AUTHORS |
10 | Stores one to many authors for a specific item. |
JTF_AMV_ITEM_KEYWORDS |
10 | Stores one to many keywords for a specific item. |
JTF_AM_SCREEN_SETUPS_B |
40 | This table is the setup table to modify the Assignment Manager UI layout |
JTF_AM_SCREEN_SETUPS_TL |
11 | This table is the translation table for JTF_AM_SCREEN_SETUPS_B for Assignment Manager |
JTF_AM_SKILL_RULES |
31 | This table contains the skill rule mapping with product, category, problem code and component. It will help in finiding the rule id for spec |
JTF_AM_SKILL_RULE_DTLS |
32 | This table contains the combination which has to be checked in Skill Bank for a given Rule Id. |
JTF_AM_TERR_QUALIFIERS |
27 | This table contains data that maps the territory qualifier id to the territory qualifier record attribute name in the territory/am api |
JTF_AUTH_ACCT_ROLE_MAPS |
12 | This table maps a type of user to a particular role and a particular application domain. |
JTF_AUTH_DOMAINS_B |
13 | Defines the domain for which the role or the permission is granted to the principal. A domain may belong to a parent domain |
JTF_AUTH_DOMAINS_TL |
13 | Translation table |
JTF_AUTH_MAPS_SOURCES |
13 | This table stores the source information for the user-role mapping table. A role can be assigned to a user coming from different sources. An |
JTF_AUTH_PERMISSIONS_B |
16 | This table will store the permissions [which are simple strings] for all the domains in the system. We will partition the permissions by app |
JTF_AUTH_PERMISSIONS_TL |
13 | Translation table |
JTF_AUTH_PRINCIPALS_B |
15 | A principal will be a user or a role. If the principal is a user then the column IS_USER_FLAG is set to 1 and USER_ID points to a user in FN |
JTF_AUTH_PRINCIPALS_TL |
13 | Translation table |
JTF_AUTH_PRINCIPAL_MAPS |
13 | This table will be used to grant roles to users by making users [JTF_AUTH_PARENT_PRINCIPAL_ID] parents of the roles [JTF_AUTH_PRINCIPAL_ID] |
JTF_AUTH_READ_PERMS |
13 | Is the denormalized table that maps every user [JTF_AUTH_PRINCIPAL_NAME] to a permission [JTF_AUTH_PERMISSION_NAME] for a given domain [JTF_ |
JTF_AUTH_ROLE_PERMS |
14 | This table groups roles [which are a type of principals] to permissions. Permissions can be positive or negative, based on the column POSITI |
JTF_BIND_DATA |
5 | Temp table used for passing bind variables and bind values for business objects. |
JTF_BIS_CHART_FUNCTIONS |
14 | CRM BIS 11.5.1 Chart Plug Reports |
JTF_BIS_RELATED_LINKS |
22 | This table store Links to Releted Reports. Each Link is striped for a User, Report. |
JTF_BIS_USER_CHART_PLUGS |
12 | This table is for storing Chart report information for each user-defined Chart Plug |
JTF_BIS_USER_FAVORITE_PLUGS |
16 | This table is for storing Chart report information for each user-defined Favorite Plug |
JTF_BRM_EXPRESSION_LINES |
37 | Expression Lines for simple business rule definitions. |
JTF_BRM_PARAMETERS |
33 | Parameters for the main workflow process of the Business Rule Monitor. |
JTF_BRM_PROCESSES |
38 | In this table a workflow process is linked to a business rule. |
JTF_BRM_RULES_B |
34 | Base table for business rules that are monitored by the business rule monitor. |
JTF_BRM_RULES_TL |
13 | Translation table for a business rules that are monitored by the business rule monitor. |
JTF_BRM_WF_ATTR_VALUES |
33 | Contains Workflow attribute values for each process |
JTF_BUS_OBJ_XREF |
12 | Business Object X-reference for Inbound messages. |
JTF_CALENDARS_B |
27 | Calendar Name,Type, Description and Effectivity. |
JTF_CALENDARS_TL |
11 | Translation table for JTF_CALENDARS_B |
JTF_CAL_ADDRESSES |
41 | This table is used to store addresses of private contacts, the table is design to make Palm sync possible in the future. |
JTF_CAL_EXCEPTIONS_B |
27 | Exception Name, Type, Description, and Effectivity. |
JTF_CAL_EXCEPTIONS_TL |
11 | Translation table for JTF_CAL_EXCEPTIONS_B table. |
JTF_CAL_EXCEPTION_ASSIGN |
29 | Assign Exceptions to a Calendar. |
JTF_CAL_ITEMS_B |
19 | Base table for Calendar Items. |
JTF_CAL_ITEMS_TL |
12 | Translation table for Calendar Items. |
JTF_CAL_RESOURCE_ASSIGN |
30 | Assign Resources to a Calendar. |
JTF_CAL_SHIFTS_B |
26 | Shift Name, Description, and Effectivity. |
JTF_CAL_SHIFTS_TL |
11 | Translation table for JTF_CAL_SHIFTS_B table. |
JTF_CAL_SHIFT_ASSIGN |
32 | Assign Shifts to a Calendar. |
JTF_CAL_SHIFT_CONSTRUCTS |
31 | Shift patterns comprising of start and end times for a particular day, availability type, and effectivity. |
JTF_CHANGED_TERR_ALL |
79 | Stores records of changes to JTF_TERR_ALL, JTF_TERR_VALUES, and JTF_TERR_RSC |
JTF_CUSTOM_BIND_VALUES |
12 | Bind variable values for End user customizations of filtering criteria to a spreadtable UI component. |
JTF_CUSTOM_GRIDS |
16 | User named sets of customizations, in Oracle Applications commonly referred to as "Folders" |
JTF_CUSTOM_GRID_COLS |
14 | End user customizations (on a column by column basis) to the visual appearance and sort, filtering criteria for a spreadtable UI component. |
JTF_DAC_CRITERIA |
13 | Do not use |
JTF_DAC_ROLE_PERMS |
14 | Do not use |
JTF_DAC_ROLE_PERM_CRIT |
22 | Do not use |
JTF_DEF_CUSTOM_GRIDS |
9 | Holds a reference to what the end user has specified as the default set of customizations. |
JTF_DIAGNOSTIC_ALERT |
13 | Stores information about tests that are security alertable |
JTF_DIAGNOSTIC_APP |
10 | Stores applications registered with diagnostic fwk and html platform which is a pseudo application |
JTF_DIAGNOSTIC_ARG |
18 | Stores argument name-value pairs for a testcase for a row number |
JTF_DIAGNOSTIC_CMAP |
4 | Contains test to application class correlation |
JTF_DIAGNOSTIC_DECL_STEP_COLS |
15 | Stores information about columns within a sub test type = column |
JTF_DIAGNOSTIC_DECL_TEST_STEPS |
26 | contains information about steps in the test |
JTF_DIAGNOSTIC_DOWNLOAD_RPT |
5 | This table will hold the downloadable report which got generated for a particular request. The Report column in the table will hold the zip |
JTF_DIAGNOSTIC_GROUP |
13 | Stores group info. for apps registered with the framework |
JTF_DIAGNOSTIC_LOG |
36 | Stores the results of tests executes in the diagnostics framework |
JTF_DIAGNOSTIC_PREREQ |
13 | Stores prereqs for groups and application registered within diagnostics |
JTF_DIAGNOSTIC_REPORT |
5 | This table holds the individual components in a report for a test as separate entities. To construct the report for a particular execution, |
JTF_DIAGNOSTIC_STATS |
18 | Stores the statistical information about a historical test execution |
JTF_DIAGNOSTIC_TEST |
19 | Stores information about testcases registered within the group and app with diagnostics |
JTF_DIAGNOSTIC_TESTSET |
9 | This table will hold the details of the test sets which were seeded/saved by the user. |
JTF_DPF_LGCL_FLOW_PARAMS |
12 | Stores the input/output params for a flow. |
JTF_DPF_LGCL_NEXT_RULES |
15 | See description |
JTF_DPF_LGCL_PHY_RULES |
14 | See description |
JTF_DPF_LOGICAL_FLOWS_B |
18 | See description |
JTF_DPF_LOGICAL_FLOWS_TL |
10 | See description |
JTF_DPF_LOGICAL_PAGES_B |
15 | See description |
JTF_DPF_LOGICAL_PAGES_TL |
10 | See description |
JTF_DPF_PHYSICAL_PAGES_B |
11 | See description |
JTF_DPF_PHYSICAL_PAGES_TL |
10 | See description |
JTF_DPF_PHY_ATTRIBS |
11 | See description |
JTF_DPF_RULES_B |
11 | See description |
JTF_DPF_RULES_TL |
10 | See description |
JTF_DPF_RULE_PARAMS |
13 | See description |
JTF_DSP_CONTEXT_B |
11 | Stores the display contexts associated with templates and media attributes for media. |
JTF_DSP_CONTEXT_TL |
12 | Translations for JTF_DSP_CONTEXT_B. |
JTF_DSP_LGL_PHYS_MAP |
14 | Stores the logical to physical media mapping based on site and language |
JTF_DSP_MSITE_SCT_ITEMS |
12 | This table stores the assocation between mini-site and items. |
JTF_DSP_MSITE_SCT_SECTS |
16 | This table stores the association between mini-site and sections. |
JTF_DSP_OBJ_LGL_CTNT |
12 | This table Contains the default logical items for selected display context labels and objects |
JTF_DSP_SECTIONS_B |
34 | This table stores information about the sections. |
JTF_DSP_SECTIONS_TL |
14 | This table stores the translatable information about the sections. |
JTF_DSP_SECTION_ITEMS |
15 | This table stores the association between sections and items. |
JTF_DSP_TPL_CTG |
11 | This table stores the category to logical template mappings |
JTF_EVT_HANDLERS_B |
12 | This table has the information about all the event handlers for a given event. |
JTF_EVT_HANDLERS_TL |
11 | Translation table has the information about all the event handlers for a given event. |
JTF_EVT_TYPES_B |
9 | This table holds information about the different types of Events. |
JTF_EVT_TYPES_TL |
11 | Translation table holds information about the different types of Events. |
JTF_EXCEPTIONS_ALL |
14 | Stores the exceptions to a territory. Not used. |
JTF_FM_BATCH_SEGMENTS |
10 | Table internally used by Fulfillment server to store information on the batch segments |
JTF_FM_BOUNCE_BACKS |
16 | Table to store information about Emails that bounced back. |
JTF_FM_CONTENT_FAILURES |
13 | Table that holds details on Failed Requests |
JTF_FM_CONTENT_HISTORY |
24 | This table stores the fulfillment content history |
JTF_FM_DISPATCHERS |
14 | This table stores fulfillment dispatchers for each server |
JTF_FM_EMAIL |
19 | This table stores information about the fulfillment email servers |
JTF_FM_EMAIL_JTF_FM_GROUPS |
13 | Stores cross reference info about email servers and groups |
JTF_FM_EMAIL_STATS |
15 | Table to hold statistical information on Emails sent out by Fulfillment Server. |
JTF_FM_FAX |
18 | Stores information about Fulfillment fax servers |
JTF_FM_FAX_JTF_FM_GROUPS |
13 | Stores cross reference info about fax servers and groups |
JTF_FM_FILE |
16 | Stores information about batch files |
JTF_FM_FILE_JTF_FM_GROUPS |
13 | Stores cross reference info about batch files and groups |
JTF_FM_GROUPS_ALL |
13 | Stores info about fulfillment groups |
JTF_FM_GROUP_FND_USER |
10 | Stores cross reference info between groups and agents |
JTF_FM_INT_REQUEST_BATCHES |
12 | Table to hold the data for request in progress. This table stores the batches and line ID range for every request inserted into the table |
JTF_FM_INT_REQUEST_HEADER |
127 | Table to hold the data for request in progress. This table stores the header level details about the request. |
JTF_FM_MIGRATION_HISTORY |
9 | Table for storing Migration Information |
JTF_FM_MIG_HISTORY_DETAILS |
14 | Table to Store Details of Migration. |
JTF_FM_PARTITION_X_REQUEST |
3 | This table will be used to store the list of all partitions that will be pooled among FFM requests |
JTF_FM_PREVIEWS |
21 | Table to hold temporary placement of Fulfillment Content to be previewed and then either submitted for dispatch or deleted |
JTF_FM_PRINTER |
17 | Stores information about Fulfillment printers |
JTF_FM_PRINTERS |
10 | Table to store the Printers available. |
JTF_FM_PRINTER_JTF_FM_GROUPS |
13 | Stores cross reference info about printers and groups |
JTF_FM_PRINT_SERVERS |
9 | Table to Store the Print Servers |
JTF_FM_PROCESSED |
116 | Table that stores information all the requests that have been processed |
JTF_FM_QUERIES_ALL |
18 | This table stores information about the fulfillment queries |
JTF_FM_QUERY_MES |
11 | Cross reference entity to store query and master document association |
JTF_FM_REQUESTS_AQ |
8 | Table that is used internally by the Fulfillment Server to store information about the Queues in which requests are placed. |
JTF_FM_REQUEST_CONTENTS |
18 | Table to hold details on the contents within the request. |
JTF_FM_REQUEST_HISTORY_ALL |
35 | Stores request history information |
JTF_FM_RESUBMITTED |
8 | Table to hold information about the resubmitted requests. |
JTF_FM_RESULT_TAB_ALL |
7 | Result table to store HTML output from Intermedia cartridge. |
JTF_FM_SERVICE_ALL |
46 | This table stores information about the fulfillment servers |
JTF_FM_SERVICE_MONITOR |
20 | Table to Store information on all the servers that were ever used in any environment |
JTF_FM_STATUS_ALL |
41 | This table stores information about the fulfillment status for requests. |
JTF_FM_TEMPLATE_ALL |
17 | This table stores information about the fulfillment templates |
JTF_FM_TEMPLATE_CONTENTS |
15 | Stores cross reference information between the fulfillment templates and contents. |
JTF_FM_TESTTOOL_TEST_DETAILS |
7 | This table stores the log details for the test submitted through the test harness |
JTF_FM_TEST_REQUESTS |
1 | this is a table where the request id for TEST requests is held temporarily |
JTF_GRID_COLS_B |
33 | Meta Data information for each column defined for a spreadtable UI component. |
JTF_GRID_COLS_TL |
12 | Translation table for JTF_GRID_COLS_B |
JTF_GRID_DATASOURCES_B |
16 | Meta Data definitions that are used to initialize and set up a a spreadtable UI component. |
JTF_GRID_DATASOURCES_TL |
11 | Translation table for JTF_GRID_DATASOURCES_B |
JTF_GRID_SORT_COLS |
11 | The default columns and priority of the columns for the current set of meta data, used for sorting the data displayed in a spreadtable UI co |
JTF_HEADER_DTD |
15 | |
JTF_HOOKS_DATA |
15 | Table the stores all the internal hooks call out. |
JTF_IAPP_FAMILIES_B |
12 | Table holds app family names for the inter-app navigation framework. Base table. |
JTF_IAPP_FAMILIES_TL |
11 | Table holds app family names for the inter-app navigation framework. Translated table. |
JTF_IAPP_FAMILY_APP_MAP |
8 | Table holds app to family mapping for the inter-app navigation framework. |
JTF_IAPP_FAMILY_USR_MAP |
9 | Table holds user, responsibility, app family mapping for the inter-app navigation framework. |
JTF_IH_ACTIONS_B |
10 | An act that can occur upon an Action Item. Examples: Add, Update, Delete, Inquiry. |
JTF_IH_ACTIONS_TL |
13 | Translation table for Actions. |
JTF_IH_ACTION_ACTION_ITEMS |
12 | Intersction table for a valid set of Action Items and Actions. |
JTF_IH_ACTION_ITEMS_B |
10 | An item upon which an act can occur. Example: Order, Quote, Service Request, E-Mail, Phone Call. |
JTF_IH_ACTION_ITEMS_TL |
13 | Translation table for Action Items. |
JTF_IH_ACTIVITIES |
65 | An act performed by a human or automated agent as part of an Interaction. An Interaction Activity can be related to the handling of the Med |
JTF_IH_ACTIVITIES_STG |
64 | An act performed by a human or automated agent as part of an Interaction. An Interaction Activity can be related to the handling of the Med |
JTF_IH_ACTIVITIES_STG_LOG |
64 | An act performed by a human or automated agent as part of an Interaction. An Interaction Activity can be related to the handling of the Med |
JTF_IH_BULK_ERRORS |
17 | JTF_IH_BUILK_ERRORS table required to hold data about the errors encountered while attemting to create Interaction records from builk reques |
JTF_IH_BULK_RECOVERY |
17 | Interaction History Bilk Recovery Table |
JTF_IH_CAMPAIGNS_RESULTS |
12 | This table is an intersection table between Results and Oracle Campaign. Pairing a set of Results to a specific Campaign. |
JTF_IH_CAMPAIGN_RESULT_REASONS |
13 | Intersection table that pairs a RESULT-REASON for a Specific Oracle Marketing Campaign. |
JTF_IH_DOCUMENTS |
11 | A business entity that can be created, updated or queried during the process of an interaction . Individual document types are defined in |
JTF_IH_INTERACTIONS |
68 | A contact point between a customer, customer system or potential customer and a single human or automated agent (Handler and Handler Resourc |
JTF_IH_INTERACTIONS_CAMPAIGNS |
12 | This table is an intersection table between INTERACTIONS and CAMPAIGNS. |
JTF_IH_INTERACTIONS_STG |
67 | A contact point between a customer, customer system or potential customer and a single human or automated agent (Handler and Handler Resourc |
JTF_IH_INTERACTIONS_STG_LOG |
68 | A contact point between a customer, customer system or potential customer and a single human or automated agent (Handler and Handler Resourc |
JTF_IH_INTERACTION_INTERS |
9 | Groups multiple interactions within the system. |
JTF_IH_MEDIA_ITEMS |
33 | An instance of media that was processed by the system and/or its users. Media Items can be generated by a customer or by the system or an a |
JTF_IH_MEDIA_ITEMS_STG |
30 | An instance of media that was processed by the system and/or its users. Media Items can be generated by a customer or by the system or an a |
JTF_IH_MEDIA_ITEMS_STG_LOG |
30 | An instance of media that was processed by the system and/or its users. Media Items can be generated by a customer or by the system or an a |
JTF_IH_MEDIA_ITEM_LC_SEGS |
22 | An interval in the life of a Media Item within the system. |
JTF_IH_MEDIA_ITM_LC_SEG_TYS |
11 | The descriptor of a Media Lifecycle Segment. It can denote the system or activity to which the interval of time is attributed. |
JTF_IH_OUTCOMES_B |
16 | The outcome of an interaction. Example: Contact. Busy. |
JTF_IH_OUTCOMES_CAMPAIGNS |
12 | Intersection table pairing Outcomes for specific Oracle Campaigns. |
JTF_IH_OUTCOMES_TL |
15 | Translation table for Outcomes. |
JTF_IH_OUTCOME_RESULTS |
9 | The valid combination of results for an Outcome. This table represents an intersection between JTF_IH_OUTCOMES and JTF_IH_RESULTS tables. Th |
JTF_IH_REASONS_B |
14 | A reason for the result of an interaction or an activity. Example: The reason the interaction resulted in a no-sale was that the customer |
JTF_IH_REASONS_TL |
15 | Translation table for Reason. |
JTF_IH_RESULTS_B |
15 | The result of an interaction or an activity. Example: The interaction resulted in a sale. |
JTF_IH_RESULTS_TL |
15 | Translation table for Results. |
JTF_IH_RESULT_REASONS |
9 | The valid combination of reasons for a result. |
JTF_IH_SCRIPTS |
9 | Defined in the Call Center Schema for scripting. |
JTF_IH_SOURCES |
9 | The system from which a Media Item was received or through which a Media Item was generated. |
JTF_IH_TRACKING_LISTS |
12 | This table is used by Oracle iMarketing for tracking web-clicks in the context of an Oracle Campaign. |
JTF_IH_WRAP_UPS |
23 | This table identifies the information that has to be provided by the application inserting Interaction History records. |
JTF_LOC_AREAS_B |
20 | A generic table to hold geographical location definitions that is not stored somewhere else in Oracle Applications. |
JTF_LOC_AREAS_TL |
12 | Stores columns that should be translated for a location area. |
JTF_LOC_HIERARCHIES_B |
31 | Stores a flattened out structure of all geographical information. |
JTF_LOC_POSTAL_CODES |
15 | A generic table that stores range of postal code within a location area. |
JTF_LOC_TYPES_B |
10 | Stores location types, like CITY and STATE. |
JTF_LOC_TYPES_TL |
12 | Stores columns that should be translated for a location types. |
JTF_MESSAGE_OBJECTS |
21 | business objects store |
JTF_MSG_OBJ_ROUTE |
16 | Stores the Queue name for each registered Business Object. |
JTF_MSITES_B |
41 | Stores Mini Site (Specialty Stores) Information. |
JTF_MSITES_TL |
12 | Translations for JTF_MSITES_B |
JTF_MSITE_CURRENCIES |
14 | Stores the currencies supported by the mini-sites |
JTF_MSITE_LANGUAGES |
10 | Stores the languages supported by the mini-sites |
JTF_MSITE_ORGS |
10 | Define the organizations supported by the mini-sites |
JTF_MSITE_PRTY_ACCSS |
12 | Defines the parties supported by the mini-sites (Currently not used in 11.5.1) |
JTF_MSITE_RESPS_B |
14 | Defines the responsibilities supported by the minisite |
JTF_MSITE_RESPS_TL |
11 | Translations for JTF_MSITE_RESPS_B |
JTF_NAV_NODE_TYPES |
18 | Define the node types that will be shown in the navigator |
JTF_NAV_TABS_B |
13 | Base table that stores the tabs by application id. |
JTF_NAV_TABS_TL |
11 | Translation table that stores the translated values for the tabs in the UI navigator. |
JTF_NAV_TREE_ROOTS_B |
11 | Base table that stores the tree root for each view by. |
JTF_NAV_TREE_ROOTS_TL |
11 | Translation table which stores the language dependent text to be shown on the tree root. |
JTF_NAV_VIEWBYS_B |
11 | Base table that stores the view-bys associated with each tab. |
JTF_NAV_VIEWBYS_TL |
11 | JTF_NAV_VIEWBYS_TL stores information about the lables that appear in the drop down list. Each row includes the value, its translated data, |
JTF_NOTES_B |
33 | Non-translated base table for Notes module. |
JTF_NOTES_SOURCE_TYPE_MAP |
11 | JTF_NOTES_SOURCE_TYPE_MAP is the base table for defining application/object specific note types. |
JTF_NOTES_TL |
11 | Translated base table for Notes module. |
JTF_NOTE_CONTEXTS |
10 | Base table for Contexts to Notes, which are references to other objects. |
JTF_OBJECTS_B |
48 | This table stores the details of objects(modules). |
JTF_OBJECTS_TL |
15 | Translation Table for JTF_OBJECTS_B |
JTF_OBJECT_MAPPINGS |
31 | Mapping Table between Source and Object Types eg Task Types,Note Types . The point of the table is to allow applications to define mapping |
JTF_OBJECT_PG_DTLS |
12 | |
JTF_OBJECT_PG_PARAMS |
11 | |
JTF_OBJECT_USAGES |
28 | Intersection Table between JTF_OBJECTS and Objects User. The point of the table is to allow other applications to hook to the OBJECT USAGES |
JTF_PC_CATEGORIES_B |
28 | Stores information about categories used in the Runtime Product Catalog |
JTF_PC_CATEGORIES_TL |
11 | Translation table for JTF_PC_CATEGORIES_B |
JTF_PC_HIERARCHIES |
35 | Stores node hierarchy of Categories and Price Lists for the Runtime Product Catalog |
JTF_PERZ_DATA |
14 | JTF_PERZ_DATA stores personalized data objects. |
JTF_PERZ_DATA_ATTRIB |
12 | JTF_PERZ_DATA_ATTRIB stores the data attributes associated with a personalized data object. |
JTF_PERZ_DATA_DEFAULT |
14 | JTF_PERZ_DATA_DEFAULT stores personalized data defaults. |
JTF_PERZ_LF_ATTRIB |
10 | JTF_PERZ_LF_ATTRIB stores the attributes associated with an object type defined in JTF_PERZ_LF_OBJECT_TYPE. |
JTF_PERZ_LF_OBJECT |
13 | JTF_PERZ_LF_OBJECT stores instances of look and feel objects created from the meta data defined in JTF_PERZ_LF_OBJECT_TYPE and JTF_PERZ_LF_A |
JTF_PERZ_LF_OBJECT_TYPE |
10 | JTF_PERZ_LF_OBJECT_TYPE stores the meta data for a look and feel object. |
JTF_PERZ_LF_VALUE |
13 | JTF_PERZ_LF_VALUE store the values associated with the attributes of a look and feel object instance. |
JTF_PERZ_OBJ_MAP |
9 | JTF_PERZ_OBJ_MAP stores the mapping between the look and feel object instance and the actual values for the attributes. |
JTF_PERZ_OBJ_TYPE_MAP |
9 | JTF_PERZ_OBJ_TYPE_MAP stores the mapping between the object type and the object attributes. |
JTF_PERZ_PROFILE |
12 | JTF_PERZ_PROFILE stores the personalization tag or profile for an entity. The entity could be a user, an object, a group etc. |
JTF_PERZ_PROFILE_ATTRIB |
11 | JTF_PERZ_PROFILE_ATTRIB stores the attributes associated with a personalization profile. |
JTF_PERZ_QUERY |
14 | JTF_PERZ_QUERY stores personalized query objects. |
JTF_PERZ_QUERY_ORDER_BY |
11 | JTF_PERZ_QUERY_ORDER_BY stores the order by parameters associated with a personalized query object. |
JTF_PERZ_QUERY_PARAM |
13 | JTF_PERZ_QUERY_PARAM stores the query parameters associated with a personalized query object. |
JTF_PERZ_QUERY_RAW_SQL |
14 | JTF_PERZ_QUERY_RAW_SQL stores the SQL string associated with a personalized query object. |
JTF_PF_ANON_ACTIVITY |
27 | Record all the anonymous (not falling within any session) activities |
JTF_PF_APP_SUMM |
11 | |
JTF_PF_HOST_SUMM |
12 | |
JTF_PF_LOGICAL_FLOWS |
8 | Record all Declarative Page flow data |
JTF_PF_PAGE_SUMM |
17 | |
JTF_PF_PURGEABLE |
2 | |
JTF_PF_SESSION_SUMM |
24 | |
JTF_PF_SES_ACTIVITY |
27 | Record all the actvities that falls within a session |
JTF_PF_TMP_ACTIVITY |
26 | Temporary |
JTF_PF_USER_SUMM |
21 | |
JTF_PREFAB_CACHE_STATS |
20 | JTF_PREFAB_CACHE_STATS captures the statistics of cache usage. |
JTF_PREFAB_CA_COMPS_B |
21 | JTF_PREFAB_CA_COMPS_B models a cache component for an application. |
JTF_PREFAB_CA_COMPS_TL |
11 | JTF_PREFAB_CA_COMPS_TL is a translation table. |
JTF_PREFAB_CA_FILTERS_B |
11 | JTF_PREFAB_CA_FILTERS_B models a cache filter. |
JTF_PREFAB_CA_FILTERS_TL |
11 | JTF_PREFAB_CA_FILTERS_TL is a translation table. |
JTF_PREFAB_CA_FL_LANGS |
11 | JTF_PREFAB_CA_FL_LANGS stores all the language codes associated with a cache filter in the table JTF_PREFAB_CA_FILTERS_B. |
JTF_PREFAB_CA_FL_RESPS |
11 | JTF_PREFAB_CA_FL_RESPS stores all the responsibility id's associated with a cache filter in the table JTF_PREFAB_CA_FILTERS_B. |
JTF_PREFAB_FILTERS_B |
14 | JTF_PREFAB_FILTERS_B models a prefabrication filter. |
JTF_PREFAB_FILTERS_TL |
11 | JTF_PREFAB_FILTERS_TL is a translation table. |
JTF_PREFAB_HA_COMPS |
14 | JTF_PREFAB_HA_COMPS models the policy for a cache component (CA_COMP_ID) on a specific host (HOST_APP_ID). |
JTF_PREFAB_HA_FILTERS |
12 | JTF_PREFAB_HA_FILTERS stores the policy for a cache filter (CA_FILTER_ID) on a particular host (HOST_APP_ID). |
JTF_PREFAB_HOST_APPS |
15 | JTF_PREFAB_HOST_APPS models applications belonging to a host. |
JTF_PREFAB_POLICIES_B |
22 | JTF_PREFAB_POLICIES_B models prefabrication policies. |
JTF_PREFAB_POLICIES_TL |
11 | JTF_PREFAB_POLICIES_TL is a translation table. |
JTF_PREFAB_PRBS |
14 | JTF_PREFAB_PRBS models the PRBs for the prefabricator. |
JTF_PREFAB_STATISTICS |
23 | JTF_PREFAB_STATISTICS stores the statistics information of Prefabrication. |
JTF_PREFAB_SYS_POLICIES |
19 | JTF_PREFAB_SYS_POLICIES models the system-wide policy for the prefabrication system. |
JTF_PREFAB_UD_KEYS_B |
14 | JTF_PREFAB_UD_KEYS models the user defined key for the prefabrication system. |
JTF_PREFAB_UD_KEYS_TL |
11 | JTF_PREFAB_UD_KEYS_TL is a translation table. |
JTF_PREFAB_UR_POLICIES |
12 | JTF_PREFAB_UR_POLICIES models user id's and responsibility id's that are associated with a policy in the table JTF_PREFAB_POLICIES_B. |
JTF_PREFAB_WSHP_POLICIES |
10 | JTF_PREFAB_WSHP_POLICIES models ports associated with a given host in the table JTF_PREFAB_WSH_POES_B. |
JTF_PREFAB_WSH_POES_B |
14 | JTF_PREFAB_WSH_POES_B captures the list of web-servers and their associated characteristics. |
JTF_PREFAB_WSH_POES_TL |
11 | JTF_PREFAB_WSH_POES_TL is a translation table. |
JTF_PROD_MSG_ROUTE |
16 | product level message queue |
JTF_PROFILEPROPERTIES_B |
13 | Contains base profile properties defined for profiles. This is not application specific |
JTF_PROFILEPROPERTIES_TL |
14 | Contains the translation related columns for JTF_PROFILEPROPERTIES_B table |
JTF_PROFILE_MAPPINGS_B |
10 | Base table that contains mapping between a base table and corresponding profile table |
JTF_PROFILE_MAPPINGS_TL |
14 | Translation table that contains mapping between a base table and corresponding profile table |
JTF_PROFILE_METADATA_B |
15 | Contains metadata information about base and extended profile properties that is application specific. |
JTF_PROFILE_METADATA_TL |
13 | Translation table that contains metdata for profile columns |
JTF_PROFILE_RULES_B |
11 | |
JTF_PROFILE_RULES_TL |
13 | |
JTF_QUAL_TYPES_ALL |
21 | This table will store the different transaction types that are processed by territories. |
JTF_QUAL_TYPE_USGS_ALL |
14 | This is an intersection table between JTF_SOURCES and JTF_QUAL_TYPES. This is the source of the qualifier type. |
JTF_QUAL_USGS_ALL |
95 | This table stores the association between a qualifer and the transaction type of a source via JTF_QUAL_TYPE_USGS (stores association between |
JTF_QUERYDETAILS |
16 | |
JTF_QUERYOBJECT |
10 | |
JTF_RS_ACTIVE_GRP_MBRS |
11 | This Table contains only active group membership detais. |
JTF_RS_CHGD_GRP_RELATIONS |
13 | This table stores the relations between Groups. Primary key is Group_relate_id. Ex. for relation_type is 'PARENT_GROUP' (Similar to JTF_RS_G |
JTF_RS_CHGD_ROLE_RELATIONS |
14 | This table stores the relations between Groups. Primary key is Group_relate_id. Ex. for relation_type is 'PARENT_GROUP' (Similar to JTF_RS_G |
JTF_RS_DBI_DENORM_RES_GROUPS |
22 | |
JTF_RS_DBI_MGR_GROUPS |
10 | |
JTF_RS_DEFAULT_GROUPS |
14 | |
JTF_RS_DEFAULT_GROUPS_INT |
19 | |
JTF_RS_DEFAULT_GROUPS_STAGE |
14 | |
JTF_RS_DYNAMIC_GROUPS_B |
29 | Base Table JTF_RS_DYNAMIC_GROUPS_B stores general information about a given Dynamic Group. |
JTF_RS_DYNAMIC_GROUPS_TL |
11 | Translation table for JTF_RS_DYNAMIC_GROUPS_B. It is used to store all columns and data that are needed for Multi-Language Support. |
JTF_RS_GROUPS_AUD_B |
24 | Base Table which stores audit information for a Group. |
JTF_RS_GROUPS_AUD_TL |
13 | Translation Table which stores audit information for a Group. |
JTF_RS_GROUPS_B |
31 | Base Table JTF_RS_GROUPS_B stores general information about a given Group. |
JTF_RS_GROUPS_DENORM |
33 | This is a denormalized table for Group. It stores information about parent group and immediate parent flag. |
JTF_RS_GROUPS_TL |
11 | Translation table for JTF_RS_GROUPS_B. It is used to store all columns and data that are needed for Multi-Language Support. |
JTF_RS_GROUP_MEMBERS |
28 | This table stores the resources who are assigned to be group members. Primary key is Group_member_id. |
JTF_RS_GROUP_MEMBERS_AUD |
16 | Table which stores audit information for a Group Members. |
JTF_RS_GROUP_ORGANIZATIONS |
24 | |
JTF_RS_GROUP_USAGES |
26 | This table stores the usages which are assigned to be groups. Primary key is Group_usage_id. Group_id and usage are unique key. |
JTF_RS_GRP_RELATE_AUD |
20 | The table that stores audit information for a group relation |
JTF_RS_GRP_RELATIONS |
30 | This table stores the relations between Groups. Primary key is Group_relate_id. Ex. for relation_type is 'PARENT_GROUP' |
JTF_RS_JOB_ROLES |
26 | This table stores the relations between roles and jobs. Primary key is job_role_id. |
JTF_RS_REP_MANAGERS |
37 | Denormalized table that stores the reporting hierarchy of group members |
JTF_RS_RESOURCE_DENORM |
13 | This is a denormalized table for Resources. It stores hierarchial information about resources. |
JTF_RS_RESOURCE_EXTNS |
86 | This is table stores all important information about Resources. These Resources are coming from HR or HZ or Vonder table etc. Primary key is |
JTF_RS_RESOURCE_EXTNS_INT |
52 | This interface table is used for population of Resource entity in JTF_RS_RESOURCE_EXTNS and JTF_RS_RESOURCE_EXTNS_TL tables. |
JTF_RS_RESOURCE_EXTNS_TL |
11 | This is table stores all important information about Resources. These Resources are coming from HR or HZ or Vonder table etc. Primary key is |
JTF_RS_RESOURCE_EXTN_AUD |
134 | The table that stores audit information for Resources |
JTF_RS_RESOURCE_PARAMS |
31 | This table stores resource params. Resource_param_id is the primary key. |
JTF_RS_RESOURCE_PICTURES |
26 | This table is used to store the Pictures of individual resources. |
JTF_RS_RESOURCE_SKILLS |
35 | This table stores the skills for individual resource |
JTF_RS_RESOURCE_VALUES |
28 | This table stores resource values. Resource_param_value_id is the primary key. |
JTF_RS_RES_AVAILABILITY |
30 | This table stores those resources who are unavailable |
JTF_RS_ROLES_B |
33 | Base Table JTF_RS_ROLES_B stores general information about a given Role. |
JTF_RS_ROLES_TL |
12 | Translation table for JTF_RS_ROLES_B. It is used to store all columns and data that are needed for Multi-Language Support. |
JTF_RS_ROLE_RELATE_AUD |
20 | Base Table which stores audit information for a Role Relation. |
JTF_RS_ROLE_RELATIONS |
31 | This table stores the association between resources and roles. Primary key is Resource_id and Role_id. Each resource can be assigned to mult |
JTF_RS_SALESREPS |
41 | This table stores information about salesreps. Salesrep_id is the primary key. If resource category is 'OTHERS' then salesrep_number and or |
JTF_RS_SALESREPS_INT |
23 | This interface table is used for populating data in JTF_RS_SALESREPS table |
JTF_RS_SKILL_LEVELS_B |
26 | This table stores the Skill Levels (Master Data) |
JTF_RS_SKILL_LEVELS_TL |
12 | This table stores the Skill Levels (Master Data) - TL table |
JTF_RS_SRP_GROUPS |
14 | This table stores the primary group id for salesreps. This table is populated by concurrent program 'Update Primary Sales Groups for Salespe |
JTF_RS_SRP_GROUPS_INT |
19 | This is intermediate table for defaulting of groups for salesreps |
JTF_RS_SRP_GROUPS_STAGE |
14 | |
JTF_RS_SRP_TERRITORIES |
30 | This table stores information about combination of salesrep and territories. |
JTF_RS_TABLE_ATTRIBUTES_B |
27 | Base Table JTF_RS_TABLE_ATTRIBUTES_B stores general information of Table attributes that can be modified by users |
JTF_RS_TABLE_ATTRIBUTES_TL |
11 | Translation table for JTF_RS_TABLE_ATTRIBUTES_B. It is used to store all columns and data that are needed for Multi-Language Support. |
JTF_RS_TEAMS_B |
29 | Base Table JTF_RS_TEAMS_B stores general information about a given Team. |
JTF_RS_TEAMS_TL |
11 | Translation table for JTF_RS_TEAMS_B. It is used to store all columns and data that are needed for Multi-Language Support. |
JTF_RS_TEAM_MEMBERS |
29 | This table stores the resources who are assigned to be team members. Primary key is Team_member_id. |
JTF_RS_TEAM_USAGES |
26 | This table stores the usages which are assigned to be teams. Primary key is team_usage_id. Team_id and usage are unique key. |
JTF_RS_UPLOAD_DATA |
73 | This table stroes the information about upload data. |
JTF_R_RULECONTEXTS |
12 | Store Rule Defintion name, and description |
JTF_R_RULESETS_B |
18 | group a set of rules into an application unit |
JTF_R_RULESETS_TL |
13 | Translated table to store description of rule set information |
JTF_R_RULES_B |
13 | name and describes the condition and action of a rule |
JTF_R_RULES_TL |
14 | rule definition translation table |
JTF_SEEDED_QUAL_ALL_B |
11 | This table will contain all the qualifiers that are going to be used to define territories. |
JTF_SEEDED_QUAL_ALL_TL |
13 | This is the MLS support table for the JTF_SEEDED_QUAL_B table. This table will contain all the translations in different languages for the t |
JTF_SOURCES_ALL |
28 | Group Column Name |
JTF_STATE_RESPONSIBILITIES |
27 | Intersection table between State Rules and Responsibilities. It associates Rules with Responsibilities. |
JTF_STATE_RULES_B |
27 | Base table which stores rule definitions |
JTF_STATE_RULES_TL |
11 | Translation table for JTF_STATE_RULES_B. |
JTF_STATE_TRANSITIONS |
28 | Table for State Transitions. |
JTF_STORES_B |
25 | Stores details of a WEB store. |
JTF_STORES_TL |
13 | Translation for JTF_STORES_B |
JTF_SUBSCRIBED_PROFILES |
11 | A subscription table that indicates whether an application has subscribed to a profile. |
JTF_SYNC_REPLY_MSG |
7 | This table is obsolete |
JTF_TAE_1001_ACCOUNT_NM_TRANS |
37 | This table stores stores the input data for the new mode BULK TAE |
JTF_TAE_1001_LEAD_NM_TRANS |
41 | This table stores the input data for the new mode BULK TAE. |
JTF_TAE_1001_OPPOR_NM_TRANS |
41 | This table stores the input data for the new mode BULK TAE. |
JTF_TAE_1001_PROP_NM_TRANS |
37 | This table stores the input data for the new mode BULK TAE. |
JTF_TAE_1001_QUOTE_NM_TRANS |
39 | This table stores the input data for the new mode BULK TAE. |
JTF_TAE_1600_CUST_NM_TRANS |
36 | This table stores the input data for the new mode BULK TAE. |
JTF_TAE_QUAL_FACTORS |
19 | This table stores the factor data for the qualifier. |
JTF_TAE_QUAL_PRODUCTS |
16 | This table stores the product for the qualifier. |
JTF_TAE_QUAL_PRODUCTS_HINTS |
14 | This table stores the SQL hints for the qualifier combination. |
JTF_TAE_QUAL_PROD_FACTORS |
12 | This table stores the product factors for the qualifier combination. |
JTF_TAE_RPT_OBJS |
155 | This table stores the input data for the BULK TAE. |
JTF_TAE_RPT_OBJ_MATCHES |
23 | This table stores the matching territories for reports |
JTF_TAE_RPT_OBJ_WINNERS |
32 | This table stores winning territories |
JTF_TAE_RPT_STAGING_IN |
55 | This table stores input data for reports |
JTF_TAE_RPT_STAGING_OUT |
74 | This table stores final output data from which report is rendered |
JTF_TASKS_B |
103 | Base Table JTF_TASKS_B stores general information about a given Task. |
JTF_TASKS_TL |
12 | Translation table for JTF_TASKS_B. It is used to store all columns and data that are needed for Multi-Language Support. |
JTF_TASK_ASSIGNMENTS |
61 | JTF_TASK_ASSIGNMENTS stores information about the resource assignments associated with the task. |
JTF_TASK_ASSIGNMENTS_AUDIT_B |
53 | Table for stroing changes in Task Assignments.It has row for every change in Task Assignment. |
JTF_TASK_AUDITS_B |
107 | Base Table which stores audit information for a task. |
JTF_TASK_AUDITS_TL |
13 | Translation table for JTF_TASKS_B. It is used to store all columns and data that are needed for Multi-Language Support. |
JTF_TASK_CONTACTS |
30 | JTF_TASK_CONTACTS stores the contact information for a given customer. |
JTF_TASK_CUSTOM_COLORS |
16 | This table stores the custom color setup |
JTF_TASK_DATES |
27 | JTF_TASK_DATES stores the actual date values for a task.... |
JTF_TASK_DATE_TYPES_B |
26 | Allows for the description of date types other than those included as basic date types within JTF_TASK. For example, a customer may want to |
JTF_TASK_DATE_TYPES_TL |
11 | Translation table for JTF_TASKS_B. It is used to store all columns and data that are needed for Multi-Language Support. |
JTF_TASK_DEPENDS |
31 | JTF_TASK_DEPENDS stores the dependency information between the two tasks. |
JTF_TASK_PHONES |
28 | JTF_TASK_PHONES contains stores pointer for contact phones. |
JTF_TASK_PRIORITIES_B |
32 | This table stores information for all task priorities. |
JTF_TASK_PRIORITIES_TL |
12 | Translation table for JTF_TASKS_B. It is used to store all columns and data that are needed for Multi-Language Support. |
JTF_TASK_PURGE |
7 | |
JTF_TASK_RECUR_RULES |
41 | This table stores all the recurrence rules. |
JTF_TASK_REFERENCES_B |
30 | JTF_TASK_REFERENCES stores the reference details for a given task. |
JTF_TASK_REFERENCES_TL |
10 | Translation table for JTF_TASKS_B. It is used to store all columns and data that are needed for Multi-Language Support. |
JTF_TASK_RSC_REQS |
30 | JTF_TASK_RSC_REQS contains the resource requirements for a task. |
JTF_TASK_STATUSES_B |
53 | JTF_TASK_STATUSES stores all the task statuses. |
JTF_TASK_STATUSES_TL |
12 | Translation table for JTF_TASKS_B. It is used to store all columns and data that are needed for Multi-Language Support. |
JTF_TASK_TEMPLATES_B |
53 | JTF_TASK_TEMPLATES_B stores all the Task templates. |
JTF_TASK_TEMPLATES_TL |
12 | Translation table for JTF_TASKS_B. It is used to store all columns and data that are needed for Multi-Language Support. |
JTF_TASK_TEMP_GROUPS_B |
29 | JTF_TASK_TEMPLATES_B stores all task template groups. |
JTF_TASK_TEMP_GROUPS_TL |
12 | Translation table for JTF_TASKS_B. It is used to store all columns and data that are needed for Multi-Language Support. |
JTF_TASK_TYPES_B |
43 | JTF_TASK_TYPES stores all task types. |
JTF_TASK_TYPES_TL |
12 | Translation table for JTF_TASKS_B. It is used to store all columns and data that are needed for Multi-Language Support. |
JTF_TERR_ALL |
64 | Stores the definition of the territories. There are 3 categories of territories, Standard, Escalation and Template. Information stored in th |
JTF_TERR_CNR_GROUPS |
28 | Stores the Customer Name Range Groups. |
JTF_TERR_CNR_GROUP_VALUES |
15 | Stores the values that have been assigned to the territory qualifiers. |
JTF_TERR_DENORM |
33 | Denormalized Territory tables for reporting purposes |
JTF_TERR_DENORM_ALL |
8 | Denormalized Territory tables for performance purposes |
JTF_TERR_DENORM_RULES_ALL |
48 | Denormalized Territory tables for performance purposes |
JTF_TERR_QTYPE_USGS_ALL |
13 | Stores the transaction types that can be assigned to a territory. |
JTF_TERR_QUAL_ALL |
15 | Stores the qualifiers that used to define a territory. |
JTF_TERR_RESULTS |
13 | |
JTF_TERR_RESULTS_GT_L1 |
8 | |
JTF_TERR_RESULTS_GT_L2 |
8 | |
JTF_TERR_RESULTS_GT_L3 |
8 | |
JTF_TERR_RESULTS_GT_L4 |
8 | |
JTF_TERR_RESULTS_GT_L5 |
8 | |
JTF_TERR_RESULTS_GT_MT |
14 | |
JTF_TERR_RESULTS_GT_WT |
8 | |
JTF_TERR_RSC_ACCESS_ALL |
12 | Stores the access type that a resource has to a territory. |
JTF_TERR_RSC_ALL |
35 | Stores the resources that are assigned to a territory. |
JTF_TERR_TYPES_ALL |
34 | Stores the territory type definition. It holds the information about the types of territories defined for your organisation. |
JTF_TERR_TYPE_QUAL_ALL |
15 | Stores the qualifiers that used to define a territory type. |
JTF_TERR_TYPE_USGS_ALL |
11 | Stores the association between territory types and the Oracle Application module(s) that use them. |
JTF_TERR_USGS_ALL |
11 | Stores the association between territories and the Oracle Application module(s) that use them. |
JTF_TERR_VALUES_ALL |
30 | Stores the values that have been assigned to the territory qualifiers. |
JTF_TTY_ACCT_METRICS |
15 | Stores Alignment metrics data for each Named Account. |
JTF_TTY_ACCT_QUAL_MAPS |
16 | This table stores mapping for Named Accounts |
JTF_TTY_ACCT_RSC_DN |
13 | This table stores named account assignments in denormalized manner |
JTF_TTY_ADMIN_BIN_SUMM |
17 | This table stores summarized data for territory administrator bins |
JTF_TTY_ALIGNMENTS |
15 | Contains basic Alignment information |
JTF_TTY_ALIGN_ACCTS |
9 | Stores Accounts used in an Alignment |
JTF_TTY_ALIGN_PTERR |
13 | Stores the Resources used in the Alignment and their proposed quotas |
JTF_TTY_GEOGRAPHIES |
16 | This table stores source geography data |
JTF_TTY_GEO_GRP_VALUES |
12 | This table stores Geography Territory Group Values |
JTF_TTY_GEO_TERR |
15 | This table stores Geography Territory data |
JTF_TTY_GEO_TERR_RSC |
13 | This table stores sales person assignments for Geography Territories |
JTF_TTY_GEO_TERR_VALUES |
9 | This table stores geography territory values like postal code assignment |
JTF_TTY_GEO_WEBADI_INTERFACE |
17 | Geography WEB ADI interface table |
JTF_TTY_NAMED_ACCTS |
11 | Stores Named Accounts |
JTF_TTY_NAMED_ACCT_CHANGES |
11 | This table stores the changes in the self service territory groups. |
JTF_TTY_NAMED_ACCT_RSC |
30 | Contains Named Account assignments. |
JTF_TTY_PTERR_ACCTS |
9 | Stores the Proposed Territory assignments in the Alignment |
JTF_TTY_PTERR_METRICS |
12 | Stores Alignment metrics data for each Proposed Territory in an Alignment |
JTF_TTY_ROLE_ACCESS |
11 | This table stores role access for territory groups |
JTF_TTY_ROLE_PROD_INT |
11 | This table stores product interest for territory groups |
JTF_TTY_RSC_ACCT_SUMM |
14 | This table stores summarized data for sales RM bin |
JTF_TTY_TERR_GROUPS |
21 | This table stores territory group data |
JTF_TTY_TERR_GRP_ACCTS |
29 | This table stores named accounts information for territory groups |
JTF_TTY_TERR_GRP_OWNERS |
12 | This table stores owner information for territory groups |
JTF_TTY_TERR_GRP_ROLES |
9 | This table stores roles for Territory Groups |
JTF_TTY_WEBADI_INTERFACE |
442 | Interface table to store data that needs to be displayed in Excel |
JTF_TTY_WEBADI_INTERFACES |
112 | Interface table to store data that needs to be displayed in Excel |
JTF_TYPE_QTYPE_USGS_ALL |
10 | Stores the transaction types that can be assigned to a territory type. |
JTF_UM_APPROVALS_B |
15 | . |
JTF_UM_APPROVALS_TL |
13 | Translation table for JTF_UM_APPROVALS_B. |
JTF_UM_APPROVERS |
14 | Defines the individual approvers for an approval (JTF_UM_APPROVAL_B). The approvers can be defined globally, as well as overridden for a giv |
JTF_UM_SUBSCRIPTIONS_B |
18 | An enrollment usually gives access to some specific part of the system through roles, permissions, and the responsibility defined for the en |
JTF_UM_SUBSCRIPTIONS_TL |
13 | Translation table for JTF_UM_SUBSCRIPTIONS_B |
JTF_UM_SUBSCRIPTION_REG |
16 | Stores the enrollments that a user has signed up for, whether approved, rejected, pending, removed. |
JTF_UM_SUBSCRIPTION_RESP |
12 | Intersection table which defines what responsibility is attached to each enrollment. |
JTF_UM_SUBSCRIPTION_ROLE |
11 | Intersection table which defines what roles are attached to each enrollment. |
JTF_UM_SUBSCRIPTION_TMPL |
11 | Intersection table where a subscription is attached to one or more templates. |
JTF_UM_TEMPLATES_B |
16 | A template is used to capture information about the user for an enrollment or a usertype. A template is essentially one or more jsp pages as |
JTF_UM_TEMPLATES_TL |
12 | Translation table for JTF_UM_TEMPLATES_B. |
JTF_UM_USERTYPES_B |
17 | . |
JTF_UM_USERTYPES_TL |
13 | Translation table for JTF_UM_USERTYPES_B |
JTF_UM_USERTYPE_REG |
15 | Stores what usertype a user has been registered as. |
JTF_UM_USERTYPE_RESP |
13 | Stores what responsibilities are attached to each usertype. |
JTF_UM_USERTYPE_ROLE |
11 | Stores what roles are assigned to each usertype. |
JTF_UM_USERTYPE_SUBSCRIP |
13 | Intersection table storing the enrollments that should be available to each usertype.. |
JTF_UM_USERTYPE_TMPL |
11 | Intersection table where a usertype is attached to one or more templates. |
JTF_USER_HOOKS |
17 | Stores Execution status for user hooks |
JTF_VAL_RULES |
15 | |
JTF_VAL_TYPES |
13 | |
JTF_XML_EVENT_MAPPINGS |
12 | Mapping table between XML Services Events and XML Services Subscribers |
JTF_XML_INVOCATIONS_B |
14 | Table that stores XML Services Events |
JTF_XML_INV_AUTHS |
13 | Table that stores authentication profiles |
JTF_XML_INV_PARAMS |
15 | Table that stores input parameters info for an invocation |
JTF_XML_INV_SERVICES_B |
17 | Table that stores invocations. |
JTF_XML_INV_TMAPPINGS |
17 | Table that stores type mapping info for the XML Services Client |
JTF_XML_SERVICES_B |
15 | Table that stores services. |
JTF_XML_SVC_GROUPS_B |
15 | Table that stores the Service Groups. |
JTF_XML_TYPE_MAPPINGS |
17 | Table that stores typemapping information for the Execution Engine |
JTY_1001_DENORM_ATTR_VALUES |
21 | This table stores denormalized territory values. |
JTY_1001_DENORM_DEA_VALUES |
21 | This table stores denormalized territory values for date effectivity assignment. |
JTY_1002_DENORM_ATTR_VALUES |
42 | This table stores denormalized territory values. |
JTY_1003_DENORM_ATTR_VALUES |
64 | This table stores denormalized territory values. |
JTY_1004_DENORM_ATTR_VALUES |
21 | This table stores denormalized territory values. |
JTY_1500_DENORM_ATTR_VALUES |
21 | This table stores denormalized territory values. |
JTY_1600_DENORM_ATTR_VALUES |
21 | This table stores denormalized territory values. |
JTY_1700_DENORM_ATTR_VALUES |
21 | This table stores denormalized territory values. |
JTY_CHANGED_DEA_TERRS |
11 | |
JTY_CHANGED_TERRS |
11 | This table stores changed territories. |
JTY_CHANGED_TERRS_GT |
5 | |
JTY_CONC_REQ_SUMM |
22 | This table stores concurrent request summary. |
JTY_DEA_ATTR_FACTORS |
18 | This table stores attribute factors for date effectivity assignment. |
JTY_DEA_ATTR_PRODUCTS |
15 | This table stores attribute product for date effectivity assignment. |
JTY_DEA_ATTR_PRODUCTS_SQL |
20 | This table stores attribute product SQL for date effectivity assignment. |
JTY_DEA_ATTR_PROD_FACTORS |
11 | This table stores attribute product factors for date effectivity assignment. |
JTY_DEA_VALUES_IDX_DETAILS |
12 | This table stores indexes for date effectivity assignment. |
JTY_DEA_VALUES_IDX_HEADER |
14 | This table stores indexes for date effectivity assignment. |
JTY_DENORM_DEA_RULES_ALL |
25 | This table stores denormalized territories for date effectivity assignment. |
JTY_STR_TO_TABLE_GT |
3 | |
JTY_TAE_ATTR_PRODUCTS_SQL |
21 | This table stores attribute product SQL for TAE. |
JTY_TERR_1001_ACCOUNT_TRANS_GT |
42 | |
JTY_TERR_1001_LEAD_TRANS_GT |
53 | |
JTY_TERR_1001_OPPOR_TRANS_GT |
60 | |
JTY_TERR_1001_PROP_TRANS_GT |
42 | |
JTY_TERR_1001_QUOTE_TRANS_GT |
42 | |
JTY_TERR_1003_CLAIM_TRANS_GT |
111 | |
JTY_TERR_1003_OFFER_TRANS_GT |
111 | |
JTY_TERR_1500_CNTRCT_TRANS_GT |
111 | |
JTY_TERR_1600_CUST_TRANS_GT |
37 | |
JTY_TERR_1600_DELQCY_TRANS_GT |
111 | |
JTY_TERR_1700_PARTNER_TRANS_GT |
111 | |
JTY_TERR_NVP_TRANS_GT |
4 | |
JTY_TERR_VALUES_IDX_DETAILS |
12 | This table stores indexes for territory values. |
JTY_TERR_VALUES_IDX_HEADER |
14 | This table stores indexes for territory values. |
JTY_TRANS_USG_PGM_DETAILS |
35 | This table stores program details for bulk TAE. |
JTY_TRANS_USG_PGM_SQL |
21 | This table stores program SQL for bulk TAE. |
JTY_WEBADI_OTH_TERR_INTF |
497 | Interface table to store data that needs to be displayed in Excel |
JTY_WEBADI_QUAL_HEADER |
18 | Interface table to store data that needs to be displayed in Excel |
JTY_WEBADI_QUAL_TYPE_HEADER |
5 | Interface table to store data that needs to be displayed in Excel |
JTY_WEBADI_RESOURCES |
52 | Interface table to store data that needs to be displayed in Excel |