Oracle eBusiness Suite Technical Reference

Release 11i - Copyright (c) 2001 - 2005 Oracle

This Technical Reference Manual (TRM) in any form, software or printed matter, contains proprietary information of Oracle ; it is provided under an Oracle agreement containing restrictions on use and disclosure and is also protected by copyright, patent, and other intellectual property law. Restrictions applicable to this TRM include, but are not limited to: (a) exercising either the same degree of care to safeguard the confidentiality of this TRM as you exercise to safeguard the confidentiality of your own most important Confidential Information or a reasonable degree of care, whichever is greater; (b) maintaining agreements with your employees and agents that protect the Confidential Information of third parties such as Oracle and instructing such employees and agents of these requirements for this TRM; (c) restricting disclosure of this TRM to those of your employees who have a 'need to know' consistent with the purposes for which this TRM was disclosed to you; (d) maintaining this TRM at all times on your premises; (e) not removing or destroying any proprietary or confidential legends or markings placed upon this TRM in whatever form, software or printed matter; and (f) not reproducing or transmitting this TRM in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Oracle. You should not use this TRM in any form, software or printed matter, to create software that performs the same or similar functions as any Oracle products.

The information in this TRM is subject to change without notice. If you find any problems in the TRM in any form, software or printed matter, please report them to us in writing. Oracle does not warrant that this TRM is error free. This TRM is provided to customer 'as is' with no warranty of any kind. This TRM does not constitute Documentation as that term is defined in Oracle's agreements. Reverse engineering of the Programs (software and documentation) associated with this TRM are prohibited. The Programs associated with this TRM are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be licensee's responsibility to take all appropriate fail safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and Oracle disclaims liability for any damages caused by such use of the Programs. Program Documentation is licensed for use solely to support the deployment of the Programs and not for any other any other purpose. Restricted Rights Legend

This TRM and the Programs associated with this TRM delivered subject to the DOD FAR Supplement are 'commercial computer software' and use, duplication and disclosure of the TRM and the Programs associated with this TRM shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement. Otherwise, this TRM and the Programs associated with this TRM delivered subject to the Federal Acquisition Regulations are 'restricted computer software' and use, duplication and disclosure of the TRM and the Programs associated with this TRM shall be subject to the restrictions in FAR 52.227-14, Rights in Data General, including Alternate III (June 1987). Oracle, 500 Oracle Parkway, Redwood City, CA 94065.

Oracle is a registered trademark. AIM Advantage™, Big Business. Small Business. All Business.™, CDM Advantage™, .comference™, ConText®, Des40®, Easy*Query™, Easy*SQL®, Education Objects™, EMM Advantage™, Enabling the Information Age®, ExpertDetectSM, Express®, FastForwardSM, GEMMS®, Gist™, Hyper*SQL™, instantOracle™, "Internet Business Intelligence - Insight for Everyone"™, iSQL*Plus™, JInitiator™, NLS*Workbench®, Object Marketplace™, ODP Pulse™, ODP Techwire™, OLA™, On Oracle™, Oracle®, Oracle Book®, Oracle Bookbatch®, Oracle BookBuilder®, OracleBRONZE®, Oracle Business OnLine®, OracleDevConnectSM, Oracle® Discoverer™, Oracle® Expert™, Oracle Financials®, OracleGOLDSM, OracleIncidentSM, OracleJSP™, OracleLifeCycleSM, Oracle Media Objects®, OracleMERCURYSM, OracleMetaLinkSM, OraclemetalsSM, OracleMobile™, Oracle Names®, Oracle NetSolutions®, Oracle® One™, Oracle Open Gateways®, Oracle OpenWorld®, OraclePLATINUMSM, Oracle Power Objects®, Oracle Press®, Oracle Procedural Gateway®, Oracle Quality®, Oracle Secure Network Services®, OracleSILVERSM, Oracle® SQL/Services™, Oracle® SQL*TutorSM, OracleSTERLINGSM, Oracle Store®, Oracle Transparent Gateway®, OracleWare®, Oracle8i™, Oracle9i™, PC Express®, Personal Express®, PJM Advantage™, PL/SQL™, Pro*Ada®, Pro*C™, Pro*C/C++™, Pro*COBOL®, Pro*FORTRAN®, Pro*Pascal®, Pro*PL/1®, Pro*REXX®, Profit™, ProREXX™, Report Card™, Secure Access 2.0™, Secure Network Services®, Security Without Compromise™, SellingPoint®, SQL*Plus®, Tutor™ are trademarks or registered trademarks of Oracle. Other names may be trademarks of their respective owners. The absence of a product or service name, slogan, or logo from this list does not constitute a waiver of Oracle's trademark or other intellectual property rights concerning that name, slogan, or logo.

eTRM - IBE Tables and Views

TABLE - IBE.IBE_ACTIVE_QUOTES_ALL

TABLE - IBE.IBE_CT_IMEDIA_SEARCH

TABLE - IBE.IBE_CT_RELATED_ITEMS

TABLE - IBE.IBE_CT_RELATION_RULES

TABLE - IBE.IBE_CT_REL_EXCLUSIONS

TABLE - IBE.IBE_DSP_CONTEXT_B

TABLE - IBE.IBE_DSP_CONTEXT_TL

TABLE - IBE.IBE_DSP_LGL_PHYS_MAP

TABLE - IBE.IBE_DSP_MSITE_SCT_ITEMS

TABLE - IBE.IBE_DSP_MSITE_SCT_SECTS

TABLE - IBE.IBE_DSP_OBJ_LGL_CTNT

TABLE - IBE.IBE_DSP_SECTIONS_B

TABLE - IBE.IBE_DSP_SECTIONS_TL

TABLE - IBE.IBE_DSP_SECTION_ITEMS

TABLE - IBE.IBE_DSP_TPL_CTG

TABLE - IBE.IBE_ECR_MVLOG

TABLE - IBE.IBE_ECR_ORDERS_FACT

TABLE - IBE.IBE_ECR_ORDER_HEADERS_FACT

TABLE - IBE.IBE_ECR_QUOTES_FACT

TABLE - IBE.IBE_LEAD_IMPORT_DETAILS

TABLE - IBE.IBE_LEAD_IMPORT_LOG

TABLE - IBE.IBE_MIGRATION_HISTORY

TABLE - IBE.IBE_MIGRATION_LOG

TABLE - IBE.IBE_MSITES_B

TABLE - IBE.IBE_MSITES_TL

TABLE - IBE.IBE_MSITE_CURRENCIES

TABLE - IBE.IBE_MSITE_INFORMATION

TABLE - IBE.IBE_MSITE_LANGUAGES

TABLE - IBE.IBE_MSITE_ORGS

TABLE - IBE.IBE_MSITE_PRTY_ACCSS

TABLE - IBE.IBE_MSITE_RESPS_B

TABLE - IBE.IBE_MSITE_RESPS_TL

TABLE - IBE.IBE_ORD_ONECLICK_ALL

TABLE - IBE.IBE_SECTION_SEARCH

TABLE - IBE.IBE_SECTION_SEARCH_PART

TABLE - IBE.IBE_SHP_LIST_ITEMS_ALL

TABLE - IBE.IBE_SH_QUOTE_ACCESS

TABLE - IBE.IBE_SH_SHLITEM_RELS

TABLE - IBE.IBE_SH_SHP_LISTS_ALL

TABLE - IBE.IBE_WF_NOTIF_MSG_MAPS

TABLE - IBE.IBE_WF_NOTIF_SETUP

VIEW - APPS.IBE_BIS_LIST_MSITES_V

VIEW - APPS.IBE_BI_CURRENCY_V

VIEW - APPS.IBE_BI_MSITES_V

VIEW - APPS.IBE_BI_MSITE_DIMN_V

VIEW - APPS.IBE_CT_RELATED_ITEMS_V

VIEW - APPS.IBE_DSP_AMV_ITEMS_V

VIEW - APPS.IBE_DSP_ATTACHMENTS_V

VIEW - APPS.IBE_DSP_CONTEXT_V

VIEW - APPS.IBE_DSP_CONTEXT_VL

VIEW - APPS.IBE_DSP_FEATURED_MEDIA_V

VIEW - APPS.IBE_DSP_LGL_CTNT_V

VIEW - APPS.IBE_DSP_LGL_PHYS_MAP_V

VIEW - APPS.IBE_DSP_LGL_TEMPLATES_V

VIEW - APPS.IBE_DSP_OBJ_LGL_CTNT_V

VIEW - APPS.IBE_DSP_SECTIONS_VL

VIEW - APPS.IBE_DSP_TPL_CONTEXT_V

VIEW - APPS.IBE_DSP_TPL_CTG_V

VIEW - APPS.IBE_DSP_TPL_ITEM_CTG_V

VIEW - APPS.IBE_INVOICE_DETAIL_V

VIEW - APPS.IBE_INVOICE_HEADER_V

VIEW - APPS.IBE_MSITES_VL

VIEW - APPS.IBE_MSITE_RESPS_VL

VIEW - APPS.IBE_OE_CONTACTS_V

VIEW - APPS.IBE_ORDER_DETAIL_V

VIEW - APPS.IBE_ORDER_HEADER_ADV_V

VIEW - APPS.IBE_ORDER_HEADER_V

VIEW - APPS.IBE_ORDER_ITEMS_ADV_V

VIEW - APPS.IBE_ORDER_LINE_DTL_V

VIEW - APPS.IBE_ORDER_SUM_V

VIEW - APPS.IBE_PAYMENT_DETAIL_V

VIEW - APPS.IBE_PAYMENT_HEADER_V

VIEW - APPS.IBE_QUOTE_HEADERS_V

VIEW - APPS.IBE_RETURNABLE_LINES_V

VIEW - APPS.IBE_RETURNABLE_SERIAL_V

VIEW - APPS.IBE_RETURN_DETAIL_V

VIEW - APPS.IBE_RETURN_SUM_V

VIEW - APPS.IBE_SHIP_DETAIL_V

VIEW - APPS.IBE_SHIP_DLVY_DTL_V

VIEW - APPS.IBE_SHIP_DLVY_V

Table: IBE_ACTIVE_QUOTES_ALL

Primary Key: IBE_ACTIVE_QUOTES_ALL_PK

1. ACTIVE_QUOTE_ID

Foreign Keys from this table:

Comments

IBE_ACTIVE_QUOTES_ALL is used to store the current active cart of a user.
The user is identified by party_id and cust_account_id referring HZ_PARTIES and
the active cart is identified by the quote_header_id referring ASO_QUOTE_HEADERS_ALL.
This is an org striped table. Primary key is a combination of party_id, cust_account_id
and org_id

Indexes

Columns

[top of page]

IBE.IBE_ACTIVE_QUOTES_ALL does not reference any database object

IBE.IBE_ACTIVE_QUOTES_ALL is referenced by following:

IBE

VIEW - IBE_ACTIVE_QUOTES_ALL#

[top of page]

Table: IBE_CT_IMEDIA_SEARCH

Primary Key: IBE_CT_IMEDIA_SEARCH_PK

1. IBE_CT_IMEDIA_SEARCH_ID

Primary Key: IBE_CT_IMEDIA_SEARCH_UK

1. ORGANIZATION_ID
2. INVENTORY_ITEM_ID

Foreign Keys from this table:

Comments

IBE_CT_IMEDIA_SEARCH is used by iStore to search for product items. This table is denormalized, and it combines data from MTL_SYSTEM_ITEMS_TL table and MTL_ITEM_CATEGORIES table . An intermedia index on the INDEXED_SEARCH column is primarily used in the search.
INDEXED_SEARCH Column can be customized depending on what data merchant wants to enable searching on . Currently it contains Item name (description from mtl_system_items_tl) and Item description (long description from mtl_system_items_tl) as an out of box implementation.

Primary Key: IBE_CT_IMEDIA_SEARCH_PK

1. IBE_CT_IMEDIA_SEARCH_ID

Indexes

Columns

[top of page]

IBE.IBE_CT_IMEDIA_SEARCH does not reference any database object

IBE.IBE_CT_IMEDIA_SEARCH is referenced by following:

IBE

VIEW - IBE_CT_IMEDIA_SEARCH#

[top of page]

Table: IBE_CT_RELATED_ITEMS

Primary Key: IBE_CT_RELATED_ITEMS_PK

1. INVENTORY_ITEM_ID
2. RELATED_ITEM_ID
3. RELATION_TYPE_CODE
4. ORGANIZATION_ID

Foreign Keys from this table:

Comments

IBE_CT_RELATED_ITEMS contains information about the product relationships generated from mapping rules stored in IBE_CT_RELATION_RULES table. The information about the relationship types is stored in FND_LOOKUPS view with lookup type of 'IBE_RELATIONSHIP_TYPES'.
This table contains results of preevaluation of the mapping rules stored in IBE_CT_RELATION_RULES table to improve performance. In the runtime, instead of evaluating the mapping rules on the fly, the programs will retrieve the results directly from this table.
The relationship rules based on SQL cannot be preevaluated because the value of bind arguments in the query will typically change in different requests.
Each row in this table represents a relationship between two products. When a product A is related to product B under relationship type R, product A's item ID is stored in inventory_item_id column, B's item ID in related_item_id, and relationship type R's code in relation_type_code. There can be multiple rows for a pair of products under a relationship type when more than one mapping rules generate the given pair. But they will have different value in relation_rule_id column that identifies which mapping rule generates this row.

Indexes

Columns

[top of page]

IBE.IBE_CT_RELATED_ITEMS does not reference any database object

IBE.IBE_CT_RELATED_ITEMS is referenced by following:

IBE

VIEW - IBE_CT_RELATED_ITEMS#

[top of page]

Table: IBE_CT_RELATION_RULES

Primary Key: IBE_CT_RELATION_RULES_PK

1. RELATION_RULE_ID

Foreign Keys from this table:

Foreign Keys to this table:

Comments

IBE_CT_RELATION_RULES contains information about the rules that define relationships. The information about the relationship types is stored in FND_LOOKUPS view with lookup type of 'IBE_RELATIONSHIP_TYPES'. There are two types of relationship rules: mapping and SQL rule. Any relationship type can have either multiple mapping rules or one SQL rule but not both of them.
The mapping rules define relationships in a from-to form. The type of from and to objects can be Categories, Sections or Items. The relationships generated by mapping rules are preevaluated and stored in IBE_CT_RELATED_ITEMS table. When a mapping rule is added and deleted, corresponding item level relationships will be added and deleted in IBE_CT_RELATED_ITEMS table. For example, when we add a rule 'Section A is related to Category B' for the relationship type 'SERVICE', IBE_CT_RELATED_ITEMS table is added with new rows where the inventory_item_id column has item ID of products in Section A, and related_item_id has item ID of products in Category B.
A relationship type can have a SQL rule instead of mapping rules, which will be executed at run time to get the actual item level relationships. The SQL queries can have up to 10 bind variables and unlike the mapping rules the SQL rules are not preevaluated. These SQL queries are executed in the runtime using input parameters.

Indexes

Columns

[top of page]

IBE.IBE_CT_RELATION_RULES does not reference any database object

IBE.IBE_CT_RELATION_RULES is referenced by following:

IBE

VIEW - IBE_CT_RELATION_RULES#

[top of page]

Table: IBE_CT_REL_EXCLUSIONS

Primary Key: IBE_CT_REL_EXCLUSIONS_PK

1. ORGANIZATION_ID
2. RELATION_TYPE_CODE
3. INVENTORY_ITEM_ID
4. RELATED_ITEM_ID

Foreign Keys from this table:

Comments

IBE_CT_REL_EXCLUSIONS contains information about the product relationships that are excluded.
IBE_CT_RELATED_ITEMS contains the product relationships that are preevaluated from mapping rules stored in IBE_CT_RELATION_RULES table and IBE_CT_REL_EXCLUSIONS specify which of those preevaluated product relationships should be excluded. The information about the relationship types is stored in FND_LOOKUPS view with lookup type of 'IBE_RELATIONSHIP_TYPES'.

Indexes

Columns

[top of page]

IBE.IBE_CT_REL_EXCLUSIONS does not reference any database object

IBE.IBE_CT_REL_EXCLUSIONS is referenced by following:

IBE

VIEW - IBE_CT_REL_EXCLUSIONS#

[top of page]

Table: IBE_DSP_CONTEXT_B

Primary Key: IBE_DSP_CONTEXT_B_PK

1. CONTEXT_ID

Primary Key: IBE_DSP_CONTEXT_B_UK1

1. ACCESS_NAME
2. CONTEXT_TYPE_CODE

Foreign Keys from this table:

Foreign Keys to this table:

Comments

IBE_DSP_CONTEXT_B stores the display context labels. A display context label can be uniquely identified by its access_name. The type of the display context labels can be 'TEMPLATE' or' MEDIA', representing display styles and multimedia components respectively. Users are not allowed to change the types of any existing display context labels.
Each display context label can also be assigned one default logical item with the same type.
The default logical item is defined in table JTF_AMV_ITEMS_B, containing information about the
logical display template or media file.

Indexes

Columns

[top of page]

IBE.IBE_DSP_CONTEXT_B does not reference any database object

IBE.IBE_DSP_CONTEXT_B is referenced by following:

IBE

VIEW - IBE_DSP_CONTEXT_B#

[top of page]

Table: IBE_DSP_CONTEXT_TL

Primary Key: IBE_DSP_CONTEXT_TL_PK

1. CONTEXT_ID
2. LANGUAGE

Foreign Keys from this table:

Comments

IBE_DSP_CONTEXT_TL stores translated information about the display context labels
in IBE_DSP_CONTEXT_B. Each row includes the language the row is translated to,
the translated attributes of the display context label, and the identifier which uniquely
identifies the display context label. You need one row for each display context label
in each of the installed languages. Each row includes a language and SOURCE_LANG
column which can be used to determine if a value has been translated or defaulted.

Indexes

Columns

[top of page]

IBE.IBE_DSP_CONTEXT_TL does not reference any database object

IBE.IBE_DSP_CONTEXT_TL is referenced by following:

IBE

VIEW - IBE_DSP_CONTEXT_TL#

[top of page]

Table: IBE_DSP_LGL_PHYS_MAP

Primary Key: OCO_38364745

1. LGL_PHYS_MAP_ID

Foreign Keys from this table:

Comments

IBE_DSP_LGL_PHYS_MAP defines the logical to physical media mappings based on Specialty Store and language. Each stored mapping will involve a logical item, the associated physical media, a valid Specialty Store or all- Specialty Stores, and a valid language or all-languages. If the mapping is true for all- Specialty Stores/languages, then the respective flag (default_site, default_language) should be set to 'Y' and the site and language should be set to master Specialty Store and language 'US' respectively.
No duplicate mapping can be defined for a logical item.

Indexes

Columns

[top of page]

IBE.IBE_DSP_LGL_PHYS_MAP does not reference any database object

IBE.IBE_DSP_LGL_PHYS_MAP is referenced by following:

IBE

VIEW - IBE_DSP_LGL_PHYS_MAP#

[top of page]

Table: IBE_DSP_MSITE_SCT_ITEMS

Primary Key: IBE_DSP_MSITE_SCT_ITEMS_PK

1. MINI_SITE_SECTION_ITEM_ID

Primary Key: IBE_DSP_MSITE_SCT_ITEMS_UK1

1. MINI_SITE_ID
2. SECTION_ITEM_ID

Foreign Keys from this table:

Comments

This table contains the information about what items are associated with a Specialty Store and vice versa. A Specialty Store can have many items associated with it. An Item can belong to many Specialty Stores.

Indexes

Columns

[top of page]

IBE.IBE_DSP_MSITE_SCT_ITEMS does not reference any database object

IBE.IBE_DSP_MSITE_SCT_ITEMS is referenced by following:

IBE

VIEW - IBE_DSP_MSITE_SCT_ITEMS#

[top of page]

Table: IBE_DSP_MSITE_SCT_SECTS

Primary Key: IBE_DSP_MSITE_SCT_SECTS_PK

1. MINI_SITE_SECTION_SECTION_ID

Foreign Keys from this table:

Comments

The table IBE_DSP_MSITE_SCT_SECTS contains the information about what sections are associated with a Specialty Store and vice versa. A Specialty Store can have many sections associated with it. A section can be associated to more than one Specialty Store.
LEVEL NUMBER column specifies the level number of child section ID. This field is applicable for only master Specialty Store. Root section ID will have level number 1, and its children will have level number 2, and so on.
SORT_ORDER column specifies the order of the child section within the parent section. This field is used for displaying child sections under a parent section.
CONCAT_IDS column is applicable only for master Specialty Store. It stores the concatenation of the section IDs of its ancestors sections starting from the root section ID. The delimiter used between the section IDs is '.'. The last section ID in the field is the current section's parent section ID.

Indexes

Columns

[top of page]

IBE.IBE_DSP_MSITE_SCT_SECTS does not reference any database object

IBE.IBE_DSP_MSITE_SCT_SECTS is referenced by following:

IBE

VIEW - IBE_DSP_MSITE_SCT_SECTS#

[top of page]

Table: IBE_DSP_OBJ_LGL_CTNT

Primary Key: IBE_DSP_OBJ_LGL_CTNT_PK

1. OBJ_LGL_CTNT_ID

Primary Key: IBE_DSP_OBJ_LGL_CTNT_UK1

1. ITEM_ID
2. CONTEXT_ID
3. OBJECT_ID
4. OBJECT_TYPE

Foreign Keys from this table:

Comments

Stores the default logical items for selected display context labels and objects. The type of these objects can be ' C' (category), 'I' (item) or 'S' (section). The display context labels can have the type of either 'TEMPLATE' or 'MEDIA'. The type of the default logical items should be matched with the type of the display context labels, and the default logical items need to be applicable to the objects as well.
Display context labels with type 'TEMPLATE' can only be selected by category or item objects, and only the logical templates, which have been pre-assigned to the corresponding category or categories the item belongs to, are qualified to be chosen as the default logical templates.

Indexes

Columns

[top of page]

IBE.IBE_DSP_OBJ_LGL_CTNT does not reference any database object

IBE.IBE_DSP_OBJ_LGL_CTNT is referenced by following:

IBE

VIEW - IBE_DSP_OBJ_LGL_CTNT#

[top of page]

Table: IBE_DSP_SECTIONS_B

Primary Key: IBE_DSP_SECTIONS_B_PK

1. SECTION_ID

Primary Key: IBE_DSP_SECTIONS_B_UK1

1. ACCESS_NAME

Foreign Keys from this table:

Foreign Keys to this table:

Comments

This table contains information about the sections, which are nodes in a hierarchy.
DISPLAY_CONTEXT_ID column is used to specify the display context to be used by the leaf product items under this section. This field would be relevant for only leaf sections.
AVAILABLE_IN_ALL_SITES_FLAG determines if a section is included or excluded by default in all mini-sites. If this flag is 'Y', this section will be included in all mini-sites by default. If merchant want to exclude this section from a particular mini-site it can be excluded from that particular mini-site.
If this flag is set to 'N', this section will not be included in any mini-site by default. If merchant want to include this section in a particular mini-site, it can be include in that particular mini-site.

Indexes

Columns

[top of page]

IBE.IBE_DSP_SECTIONS_B does not reference any database object

IBE.IBE_DSP_SECTIONS_B is referenced by following:

IBE

VIEW - IBE_DSP_SECTIONS_B#

[top of page]

Table: IBE_DSP_SECTIONS_TL

Primary Key: IBE_DSP_SECTIONS_TL_PK

1. SECTION_ID
2. LANGUAGE

Foreign Keys from this table:

Comments

IBE_DSP_SECTIONS_TL stores translated information about the Sections stored
in IBE_DSP_SECTIONS_B. Each row includes the language the row is translated to,
the translated attributes of the Section, and the identifier which uniquely identifies
the Section. You need one row for each Section in each of the installed languages.
Each row includes a language and SOURCE_LANG column which can be used to
determine if a value has been translated or defaulted.

Indexes

Columns

[top of page]

IBE.IBE_DSP_SECTIONS_TL does not reference any database object

IBE.IBE_DSP_SECTIONS_TL is referenced by following:

IBE

VIEW - IBE_DSP_SECTIONS_TL#

[top of page]

Table: IBE_DSP_SECTION_ITEMS

Primary Key: IBE_DSP_SECTION_ITEMS_PK

1. SECTION_ITEM_ID

Primary Key: IBE_DSP_SECTION_ITEMS_UK1

1. SECTION_ID
2. INVENTORY_ITEM_ID
3. ORGANIZATION_ID

Foreign Keys from this table:

Foreign Keys to this table:

Comments

This table contains relationship between sections and items in the catalog. Each section can have one or more items, and also each item can belong to one or more sections.

Indexes

Columns

[top of page]

IBE.IBE_DSP_SECTION_ITEMS does not reference any database object

IBE.IBE_DSP_SECTION_ITEMS is referenced by following:

IBE

VIEW - IBE_DSP_SECTION_ITEMS#

[top of page]

Table: IBE_DSP_TPL_CTG

Primary Key: IBE_DSP_TPL_CTG_PK

1. TPL_CTG_ID

Primary Key: IBE_DSP_TPL_CTG_UK1

1. ITEM_ID
2. CATEGORY_ID

Foreign Keys from this table:

Comments

IBE_DSP_TPL_CTG stores the relationships between categories and logical templates.The logical templates assigned to the categories need be applicable to 'CATEGORY' with type 'TEMPLATE'. For any category, only its assigned logical templates can be associated to a display style, defined in IBE_DSP_CONTEXT_B.

Indexes

Columns

[top of page]

IBE.IBE_DSP_TPL_CTG does not reference any database object

IBE.IBE_DSP_TPL_CTG is referenced by following:

IBE

VIEW - IBE_DSP_TPL_CTG#

[top of page]

Table: IBE_ECR_MVLOG

Primary Key: IBE_ECR_MVLOG_PK

1. MVLOG_ID

Comments

This table capture the refresh log history of materialized views. This table will also capture the begin date and end date of the transaction records refreshed into materialized views.

Indexes

Columns

[top of page]

IBE.IBE_ECR_MVLOG does not reference any database object

IBE.IBE_ECR_MVLOG is referenced by following:

IBE

VIEW - IBE_ECR_MVLOG#

[top of page]

Table: IBE_ECR_ORDERS_FACT

Foreign Keys from this table:

Comments

This table contains the fine granular aggregate data of Orders placed for a given period.

Indexes

Columns

[top of page]

IBE.IBE_ECR_ORDERS_FACT does not reference any database object

IBE.IBE_ECR_ORDERS_FACT is referenced by following:

IBE

VIEW - IBE_ECR_ORDERS_FACT#

[top of page]

Table: IBE_ECR_ORDER_HEADERS_FACT

Foreign Keys from this table:

Comments

The table IBE_ECR_ORDER_HEADERS_FACT stores information about Orders Booked in given periods.

Indexes

Columns

[top of page]

IBE.IBE_ECR_ORDER_HEADERS_FACT does not reference any database object

IBE.IBE_ECR_ORDER_HEADERS_FACT is referenced by following:

IBE

VIEW - IBE_ECR_ORDER_HEADERS_FACT#

[top of page]

Table: IBE_ECR_QUOTES_FACT

Foreign Keys from this table:

Comments

This table will provide the fine granular aggregate information about quotes for a given period.

Indexes

Columns

[top of page]

IBE.IBE_ECR_QUOTES_FACT does not reference any database object

IBE.IBE_ECR_QUOTES_FACT is referenced by following:

IBE

VIEW - IBE_ECR_QUOTES_FACT#

[top of page]

Table: IBE_LEAD_IMPORT_DETAILS

Primary Key: IBE_LEAD_IMPORT_DETAILS_PK

1. DETAIL_ID

Foreign Keys from this table:

Comments

This table contains the details of the Leads Imported.

Indexes

Columns

[top of page]

IBE.IBE_LEAD_IMPORT_DETAILS does not reference any database object

IBE.IBE_LEAD_IMPORT_DETAILS is referenced by following:

IBE

VIEW - IBE_LEAD_IMPORT_DETAILS#

[top of page]

Table: IBE_LEAD_IMPORT_LOG

Primary Key: IBE_LEAD_IMPORT_LOG_PK

1. LOG_ID

Comments

This table contains the log information for Leads that are imported.

Indexes

Columns

[top of page]

IBE.IBE_LEAD_IMPORT_LOG does not reference any database object

IBE.IBE_LEAD_IMPORT_LOG is referenced by following:

IBE

VIEW - IBE_LEAD_IMPORT_LOG#

[top of page]

Table: IBE_MIGRATION_HISTORY

Comments

This table stores history of data migration for iStore Tables. This is an Internal table and is used by development only to populate the records.

Indexes

Columns

[top of page]

IBE.IBE_MIGRATION_HISTORY does not reference any database object

IBE.IBE_MIGRATION_HISTORY is referenced by following:

IBE

VIEW - IBE_MIGRATION_HISTORY#

[top of page]

Table: IBE_MIGRATION_LOG

Primary Key: IBE_MIGRATION_LOG_PK

1. MGLOG_ID

Comments

***** Warning: Oracle Internal Use Only *****

Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.

Indexes

Columns

[top of page]

IBE.IBE_MIGRATION_LOG does not reference any database object

IBE.IBE_MIGRATION_LOG is referenced by following:

IBE

VIEW - IBE_MIGRATION_LOG#

[top of page]

Table: IBE_MSITES_B

Primary Key: IBE_MSITES_B_PK

1. MSITE_ID

Foreign Keys from this table:

Foreign Keys to this table:

Comments

IBE_MSITES_B stores the definition of the Specialty Stores (mini-sites) . A root section also need be selected for each Specialty Store.. Only the sections and items under the selected root section will be visible at this Specialty Store. There is one and only one master Specialty Store defined in this table. It is identified by MASTER_MSITE_FLAG, 'Y' for master Specialty Store and 'N' for others.
ATP_CHECK_FLAG and WALKIN_ALLOWED_FLAG are defined for each Specialty Store to indicate if ATP check is enabled or Walking customers are allowed.
MSITE_ROOT_SECTION_ID identifies the root section of the hierarchy for this Specialty Store. Only sections and items under the root section are visible for this Specialty Store.
IBE_MSITES_B also holds information such as default language, default currency, and default date format for each Specialty Store.

Indexes

Columns

[top of page]

IBE.IBE_MSITES_B does not reference any database object

IBE.IBE_MSITES_B is referenced by following:

IBE

VIEW - IBE_MSITES_B#

[top of page]

Table: IBE_MSITES_TL

Primary Key: OCO_38364962

1. MSITE_ID
2. LANGUAGE

Foreign Keys from this table:

Comments

IBE_MSITES_TL stores translated information about the Specialty Store (mini site)
in IBE_MSITES_B. Each row includes the language the row is translated to, the
translated attributes of the Specialty Store, and theSpecialty Store identifier which uniquely
identifies theSpecialty Store.. You need one row for eachSpecialty Store in each of the installed
languages. Each row includes a language and SOURCE_LANG column which can
be used to determine if a value has been translated or defaulted.

Indexes

Columns

[top of page]

IBE.IBE_MSITES_TL does not reference any database object

IBE.IBE_MSITES_TL is referenced by following:

IBE

VIEW - IBE_MSITES_TL#

[top of page]

Table: IBE_MSITE_CURRENCIES

Primary Key: IBE_MSITE_CURRENCIES_PK

1. MSITE_CURRENCY_ID

Primary Key: IBE_MSITE_CURRENCIES_UK1

1. CURRENCY_CODE
2. MSITE_ID

Foreign Keys from this table:

Comments

IBE_MSITE_CURRENCIES stores the currencies supported by the Specialty Store defined in IBE_MSITES_B. A Specialty Store need to support at least one currency and can support more than one currencies. The default currency for aSpecialty Store must be supported by the sameSpecialty Store as well.
For each Specialty Store and any of its supported currencies, this table also stores the orderable limit and the price lists for business partners, registered and walkin customers, stored in QP_LIST_HEADERS_B.

Indexes

Columns

[top of page]

IBE.IBE_MSITE_CURRENCIES does not reference any database object

IBE.IBE_MSITE_CURRENCIES is referenced by following:

IBE

VIEW - IBE_MSITE_CURRENCIES#

[top of page]

Table: IBE_MSITE_INFORMATION

Primary Key: IBE_MSITE_INFORMATION_PK

1. MSITE_INFORMATION_ID

Foreign Keys from this table:

Comments

The table IBE_MSITE_INFORMATION Stores the Additional Information for a Specialty Store.
The column MSITE_INFORMATION_CONTEXT contains the Context of the Information. Columns MSITE_INFORMATION1-20 Stores the data for the Specific Context specified in MSITE_INFORMATION_CONTEXT column. The Context information and the columns associated with the context is maintained in a Pre-Defined Developer Flexfield Structure(s).

Indexes

Columns

[top of page]

IBE.IBE_MSITE_INFORMATION does not reference any database object

IBE.IBE_MSITE_INFORMATION is referenced by following:

IBE

VIEW - IBE_MSITE_INFORMATION#

[top of page]

Table: IBE_MSITE_LANGUAGES

Primary Key: IBE_MSITE_LANGUAGES_PK

1. MSITE_LANGUAGE_ID

Primary Key: IBE_MSITE_LANGUAGES_UK1

1. MSITE_ID
2. LANGUAGE_CODE

Foreign Keys from this table:

Comments

IBE_MSITE_LANGUAGES stores the languages supported by Speciality Store defined in IBE_MSITES_B.
A Speciality Store can support more than one language. It's possible there is no language associated to aSpeciality Store. In that case, the default language defined at the Speciality Store will be used.

Indexes

Columns

[top of page]

IBE.IBE_MSITE_LANGUAGES does not reference any database object

IBE.IBE_MSITE_LANGUAGES is referenced by following:

IBE

VIEW - IBE_MSITE_LANGUAGES#

[top of page]

Table: IBE_MSITE_ORGS

Primary Key: OCO_38365034

1. MSITE_ORG_ID

Primary Key: OCO_38365036

1. MSITE_ID
2. ORG_ID

Foreign Keys from this table:

Comments

***** Warning: Oracle Internal Use Only *****

Oracle Corporation does not support access to Oracle applications data using this object, except from standard Oracle Applications programs.

Indexes

Columns

[top of page]

IBE.IBE_MSITE_ORGS does not reference any database object

IBE.IBE_MSITE_ORGS is referenced by following:

IBE

VIEW - IBE_MSITE_ORGS#

[top of page]

Table: IBE_MSITE_PRTY_ACCSS

Primary Key: IBE_MSITE_PRTY_ACCSS_PK

1. MSITE_PRTY_ACCSS_ID

Primary Key: IBE_MSITE_PRTY_ACCSS_UK1

1. PARTY_ID
2. MSITE_ID

Foreign Keys from this table:

Comments

IBE_MSITE_PARTY_ACCSS stores the relationships between Specialty Stores and parties, defined in IBE_MSITES_B and HZ_PARTIES respectively. A Specialty Store can support more than one party and will grant certain permission to the parties associated to it.

Indexes

Columns

[top of page]

IBE.IBE_MSITE_PRTY_ACCSS does not reference any database object

IBE.IBE_MSITE_PRTY_ACCSS is referenced by following:

IBE

VIEW - IBE_MSITE_PRTY_ACCSS#

[top of page]

Table: IBE_MSITE_RESPS_B

Primary Key: IBE_MSITE_RESPS_B_PK

1. MSITE_RESP_ID

Primary Key: IBE_MSITE_RESPS_B_UK1

1. MSITE_ID
2. RESPONSIBILITY_ID
3. APPLICATION_ID

Foreign Keys from this table:

Foreign Keys to this table:

Comments

Defines the responsibilities supported by the Specialty Stores

Indexes

Columns

[top of page]

IBE.IBE_MSITE_RESPS_B does not reference any database object

IBE.IBE_MSITE_RESPS_B is referenced by following:

IBE

VIEW - IBE_MSITE_RESPS_B#

[top of page]

Table: IBE_MSITE_RESPS_TL

Primary Key: IBE_MSITE_RESPS_TL_PK

1. MSITE_RESP_ID
2. LANGUAGE

Foreign Keys from this table:

Comments

IBE_MSITE_RESPS_TL stores translated information about the Specialty Stores ( mini site) and responsibility association in IBE_MSITE_RESPS_B. Each row includes the language the row is translated to, the translated attributes of the Specialty Stores - responsibility association, and the identifier which uniquely identifies the association. You need one row for each Specialty Stores - Responsibility association in each of the installed languages. Each row includes a language and SOURCE_LANG column which can be used to determine if a value has been translated or defaulted.

Indexes

Columns

[top of page]

IBE.IBE_MSITE_RESPS_TL does not reference any database object

IBE.IBE_MSITE_RESPS_TL is referenced by following:

IBE

VIEW - IBE_MSITE_RESPS_TL#

[top of page]

Table: IBE_ORD_ONECLICK_ALL

Primary Key: IBE_ORD_ONECLICK_PK

1. ORD_ONECLICK_ID

Foreign Keys from this table:

Comments

This table stores the express checkout settings for any registered customer of iStore. The settings stored include a flag to indicate whether the settings are currently enabled, and foreign keys to the billing address, the shipping address, the shipment method and the payment information.
For any given combination of party_id and cust_account_id there can be only one row in this table.

Indexes

Columns

[top of page]

IBE.IBE_ORD_ONECLICK_ALL does not reference any database object

IBE.IBE_ORD_ONECLICK_ALL is referenced by following:

IBE

VIEW - IBE_ORD_ONECLICK_ALL#

[top of page]

Table: IBE_SECTION_SEARCH

Primary Key: IBE_SECTION_SEARCH_UK1

1. INVENTORY_ITEM_ID
2. MINISITE_ID
3. ORGANIZATION_ID
4. SECTION_ID

Foreign Keys from this table:

Comments

This table is the search table for restricting search for sections. It is a denormolized table of heirarchical section item data.

Primary Key: IBE_SECTION_SEARCH_PK

1. INVENTORY_ITEM_ID
2. ORGANIZATION_ID
3. SECTION_ID
4. MINISITE_ID

Indexes

Columns

[top of page]

IBE.IBE_SECTION_SEARCH does not reference any database object

IBE.IBE_SECTION_SEARCH is referenced by following:

IBE

VIEW - IBE_SECTION_SEARCH#

[top of page]

Table: IBE_SECTION_SEARCH_PART

Comments

Primary Key: IBE_SECTION_SEARCH_PART_PK

1. INVENTORY_ITEM_ID
2. ORGANIZATION_ID
3. SECTION_ID
4. MINISITE_ID

Indexes

Columns

[top of page]

IBE.IBE_SECTION_SEARCH_PART does not reference any database object

IBE.IBE_SECTION_SEARCH_PART is referenced by following:

IBE

VIEW - IBE_SECTION_SEARCH_PART#

[top of page]

Table: IBE_SHP_LIST_ITEMS_ALL

Primary Key: IBE_SHP_LIST_ITEMS_ALL_PK

1. SHP_LIST_ITEM_ID

Foreign Keys from this table:

Foreign Keys to this table:

Comments

IBE_SHOPPING_LIST_ITEMS stores information about a typical shopping list line. This includes item,
item organization, unit of measure, quantity etc.

Indexes

Columns