Results for “market_segment_fk”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
BIM_MARKET_SEGMENT_PKG is a small PL/SQL package owned by the APPS schema in Oracle E-Business Suite, shipped as part of the Oracle Marketing (AMS) application family. Its declared purpose is to resolve the market segment associated with a trading partner or customer for a given transaction date. The package header is defined with AUTHID CURRENT_USER, meaning that its SQL statements execute under the privileges of the invoking session rather than the definer, which is characteristic of utility or lookup packages intended to be called from multiple application contexts.
The source header ($Header: bimmkts.pls 115.2 2000/01/07 ...) indicates the file was last revised in early 2000 and has remained largely static across releases. The package is classified as OTHER in the ETRM metadata, indicating it is not a public, supported business API with a documented interface contract, but rather an internal helper routine used within Oracle Marketing processing logic.
Key Procedures and Functions
The package exposes exactly one documented program unit:
- MARKET_SEGMENT_FK — A function that returns a numeric value, conventionally the foreign key to a market segment record, for a supplied customer and transaction date. Based on the naming convention and the underlying table, the returned number identifies the market segment applicable to the customer at the point in time represented by the transaction date. Because the metadata does not publish the full parameter list, only the function's name and purpose are asserted here; parameter-level details are not documented in the reference material.
The _FK suffix follows standard Oracle EBS naming practice for functions that derive a foreign key value, typically from a lookup or intersection table, so that callers can populate a foreign key column without embedding the lookup logic themselves.
Tables Accessed
The package references a single documented table through an APPS synonym:
- AMS_PARTY_MARKET_SEGMENTS — The Oracle Marketing table that stores the association between parties (customers or prospects) and the market segments to which they belong. The function reads this table to determine which segment record applies to the party supplied by the caller, presumably applying the transaction date to select the effective or current segment assignment.
No other tables are documented as referenced by this package. Because the function is read-only in intent, no inserts, updates, or deletes are expected; the package serves purely as a query and resolution layer over the market segment assignment data.
Usage Notes
The ETRM metadata records that BIM_MARKET_SEGMENT_PKG is referenced by zero other packages. This is a significant observation: the package is not part of a documented call chain within the shipped PL/SQL code base, and there is no evidence of internal reuse by other packaged APIs. Consequently, invocation is most likely to occur from Oracle Forms user exits, from concurrent program logic in the Marketing modules, or from customer-written customizations that require market segment resolution for a given party and date.
The AUTHID CURRENT_USER declaration means callers must hold appropriate privileges on AMS_PARTY_MARKET_SEGMENTS and its synonyms in their own right; grants must be verified when integrating the function into custom code. As an undocumented, classified-as-OTHER package, it should be treated as an internal Oracle object: custom code may call it, but Oracle does not warrant the stability of its signature across patches or upgrades, and its behavior should be validated during any 12.1.1 to 12.2.2 upgrade or later maintenance activity. Where equivalent public APIs exist for market segment data, those are preferable to direct reliance on this package.
-
View: ISC_EDW_BOOKINGS_F_FCV 12.1.1
APPS.ISC_EDW_BOOKINGS_F_FCV·↳ EDW_CURRENCY·↳ EDW_GEOGRAPHY_PKG·↳ EDW_ORGANIZATION_PKG·Explore ONT module →
-
View: ISC_EDW_BOOKINGS_F_FCV 12.1.1
This is the collection view for the Bookings fact table
APPS.ISC_EDW_BOOKINGS_F_FCV·↳ EDW_CURRENCY·↳ EDW_GEOGRAPHY_PKG·↳ EDW_ORGANIZATION_PKG·Explore ISC module →
-
View: FII_AR_TRX_DIST_FCV 12.1.1
Internal view used for warehouse data extraction
APPS.FII_AR_TRX_DIST_FCV·↳ EDW_CURRENCY·↳ EDW_UTIL·↳ FIIBV_AR_TRX_DIST_FCV·Explore FII module →
-
View: OPI_EDW_OPMCOGS_FCV 12.1.1
This is the source view for extracting Cost of gods sold and shipment data from the Process Manufacturing source tables.
APPS.OPI_EDW_OPMCOGS_FCV·↳ EDW_CURRENCY·↳ EDW_GEOGRAPHY_PKG·↳ EDW_INSTANCE·Explore OPI module →
-
Interface table for the Bookings fact
-
Accounts Receivable Revenue Fact table
-
Interface table for COGS Shipment Fact
-
Interface table for Consolidated Revenue fact
-
View: BIC_PARTY_LIST_V 12.1.1
Not implemented in this database·Explore BIC module →
-
View: BIC_PARTY_LIST_V 12.2.2
Not implemented in this database·Explore BIC module →
-
View: BIC_DIMV_CUSTOMERS 12.2.2
Not implemented in this database·Explore BIC module →
-
View: BIC_NEW_PARTY_LIST_V 12.1.1
Not implemented in this database·Explore BIC module →
-
View: BIC_SUMV_ACTIVATION 12.2.2
Not implemented in this database·Explore BIC module →
-
View: BIC_NEW_PARTY_LIST_V 12.2.2
Not implemented in this database·Explore BIC module →
-
View: BIC_SUMV_LOYALTY 12.1.1
Not implemented in this database·Explore BIC module →
-
View: BIC_SUMV_PROFITABILITY 12.2.2
Not implemented in this database·Explore BIC module →
-
View: BIC_SUMV_RETENTION 12.2.2
Not implemented in this database·Explore BIC module →
-
View: BIC_DIMV_CUSTOMERS 12.1.1
Not implemented in this database·Explore BIC module →
-
View: BIC_SUMV_REVENUE 12.2.2
Not implemented in this database·Explore BIC module →
-
View: BIC_SUMV_ACTIVATION 12.1.1
Not implemented in this database·Explore BIC module →
-
View: BIC_SUMV_LIFECYCLE 12.2.2
Not implemented in this database·Explore BIC module →
-
View: BIC_SUMV_REVENUE 12.1.1
Not implemented in this database·Explore BIC module →
-
View: BIC_SUMV_PROFITABILITY 12.1.1
Not implemented in this database·Explore BIC module →
-
View: BIC_SUMV_COGS 12.2.2
Not implemented in this database·Explore BIC module →
-
View: BIC_SUMV_SATISFACTION 12.2.2
Not implemented in this database·Explore BIC module →
-
View: BIC_SUMV_COGS 12.1.1
Not implemented in this database·Explore BIC module →
-
View: BIC_SUMV_SATISFACTION 12.1.1
Not implemented in this database·Explore BIC module →
-
View: BIC_SUMV_LOYALTY 12.2.2
Not implemented in this database·Explore BIC module →
-
View: BIC_SUMV_ACQUISITION 12.2.2
Not implemented in this database·Explore BIC module →
-
View: BIC_SUMV_LIFECYCLE 12.1.1
Not implemented in this database·Explore BIC module →
-
View: BIC_SUMV_ACQUISITION 12.1.1
Not implemented in this database·Explore BIC module →
-
View: BIC_SUMV_RETENTION 12.1.1
Not implemented in this database·Explore BIC module →
-
Not implemented in this database·Explore BIC module →
-
View: BIC_PARTY_SUMM_V 12.1.1
Not implemented in this database·Explore BIC module →
-
View: BIC_PMF_SUMMARY_V 12.2.2
Not implemented in this database·Explore BIC module →
-
Not implemented in this database·Explore BIC module →
-
View: BIC_PARTY_SUMM_V 12.2.2
Not implemented in this database·Explore BIC module →
-
View: BIC_PARTY_SUMMARY_V 12.1.1
Not implemented in this database·Explore BIC module →
-
Not implemented in this database·Explore BIC module →
-
Not implemented in this database·Explore BIC module →
-
View: BIC_PMF_SUMMARY_V 12.1.1
Not implemented in this database·Explore BIC module →
-
View: BIC_PARTY_SUMMARY_V 12.2.2
Not implemented in this database·Explore BIC module →
-
View: BIC_PARTY_SAT_INDEX_V 12.2.2
Not implemented in this database·Explore BIC module →
-
View: BIC_PARTY_SAT_INDEX_V 12.1.1
Not implemented in this database·Explore BIC module →
-
View: BIC_CUSTOMER_SUMMARY_V 12.2.2
Not implemented in this database·Explore BIC module →
-
View: BIC_CUSTOMER_SUMMARY_V 12.1.1
Not implemented in this database·Explore BIC module →