Search Results jtf_msite_currencies




Overview
Explore in AI Chat

Overview

The JTF_MSITE_CURRENCIES table is a core data object within the Oracle E-Business Suite CRM Foundation (JTF) module. It functions as a junction table that defines the specific currencies available for transactional use on configured mini-sites. A mini-site represents a specialized, often customer-specific, web portal or storefront within the EBS ecosystem. This table's primary role is to enforce and manage the relationship between a mini-site and the subset of system currencies it is permitted to use, thereby controlling the financial context for pricing and transactions presented to different customer segments or channels.

Key Information Stored

The table's structure centers on linking a mini-site identifier with a currency code and associating specific pricing lists for different customer types. The critical columns include MSITE_ID, which references the parent mini-site from JTF_MSITES_B, and CURRENCY_CODE, which references the valid currency from FND_CURRENCIES. The primary key is the surrogate MSITE_CURRENCY_ID, while a unique key constraint on the combination of MSITE_ID and CURRENCY_CODE ensures no duplicate currency assignments per site. Three pivotal foreign key columns—BIZPARTNER_PRC_LISTID, REGISTERED_PRC_LISTID, and WALKIN_PRC_LISTID—each reference QP_LIST_HEADERS_B. These columns allow for the assignment of distinct price lists from Oracle Advanced Pricing (QP) to business partners, registered users, and walk-in customers, respectively, for that specific mini-site and currency combination.

Common Use Cases and Queries

This table is central to multi-currency and segmented pricing configurations for EBS storefronts. A common operational use case involves retrieving all active currencies and their corresponding price lists for a given mini-site to render the correct pricing options on a web page. For reporting and administration, queries often join to related tables to audit currency coverage or validate pricing list assignments. A typical diagnostic SQL pattern would be:

  • SELECT msite.msite_name, curr.currency_code, curr.NAME, mcurr.* FROM jtf_msite_currencies mcurr JOIN jtf_msites_b msite ON mcurr.msite_id = msite.msite_id JOIN fnd_currencies curr ON mcurr.currency_code = curr.currency_code WHERE msite.msite_id = :p_site_id;

Data maintenance tasks involve inserting or updating records in this table when configuring a new mini-site's supported currencies or when modifying its tiered pricing strategy for different customer classes.

Related Objects

The JTF_MSITE_CURRENCIES table maintains documented foreign key relationships with several fundamental EBS tables, as per the provided metadata:

  • JTF_MSITES_B: The master table for mini-site definitions. Joined via JTF_MSITE_CURRENCIES.MSITE_ID.
  • FND_CURRENCIES: The application's core currency master. Joined via JTF_MSITE_CURRENCIES.CURRENCY_CODE.
  • QP_LIST_HEADERS_B: The header table for price lists in Oracle Advanced Pricing. Joined via three separate columns: BIZPARTNER_PRC_LISTID, REGISTERED_PRC_LISTID, and WALKIN_PRC_LISTID, enabling differentiated pricing.

These relationships position JTF_MSITE_CURRENCIES as a critical integration point between CRM site management (JTF), the general ledger currency setup (FND), and the advanced pricing engine (QP).