Results for “user_name”

1 result




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CSF_ODF_CTRY_MAPPING is a configuration and reference table in the Oracle E-Business Suite Field Service (CSF) product family. It stores country-level mappings used by the Oracle Data Fulfillment (ODF) integration layer, connecting Oracle Functional Areas to specific countries through a dataset identifier. In Oracle EBS 12.1.1 and 12.2.2, this table typically supports multitenancy or multi-region data partitioning logic, ensuring that field service transactions and reference data are scoped to the correct country and functional area context.

The table resides in the CSF schema and holds five documented columns: USER_NAME, COUNTRY_NAME, COUNTRY_CODE_2, DATASET, and AREA_ID. Based on the heuristic Data Vault classification derived from its foreign key structure, CSF_ODF_CTRY_MAPPING is best modeled as a standalone entity. It does not reference other core business hubs directly and functions as a reference or cross-reference table rather than a transactional hub, link, or satellite. Its single foreign key relationship points to PAY_FUNCTIONAL_AREAS, anchoring the country mapping to a valid functional area definition.

Key Information Stored

The five columns in CSF_ODF_CTRY_MAPPING capture the essential data needed to associate users, countries, and functional areas within a specific dataset context:

  • USER_NAME — Identifies the Oracle EBS user or application context for which the country mapping applies. This is a key business attribute for scoping mappings per user or integration account.
  • COUNTRY_NAME — The full descriptive name of the country (for example, "United States" or "Germany"). This column supports display and reporting requirements.
  • COUNTRY_CODE_2 — The ISO 3166-1 alpha-2 country code (for example, "US" or "DE"). This is the standard business key used for joins to other country reference tables and for filtering in queries.
  • DATASET — A dataset identifier that groups mappings for a particular data set or integration run. This enables multi-dataset scenarios where the same country may map differently across datasets.
  • AREA_ID — The foreign key referencing PAY_FUNCTIONAL_AREAS. It ties the country mapping to a specific Oracle Functional Area, ensuring that country-specific configuration is applied only within valid functional area boundaries.

No surrogate primary key is documented in the available metadata. In practice, the combination of USER_NAME, COUNTRY_CODE_2, DATASET, and AREA_ID likely acts as a composite business key or unique index ensuring that each user-country-dataset-area combination is unique.

Common Use Cases and Queries

This table is primarily used during ODF integration and field service configuration to resolve the correct country context for a given user and functional area. Typical scenarios include:

  • Validating country mappings: Checking that a specific user has a valid country and dataset assignment before processing field service transactions.
  • Resolving country codes for reporting: Joining to PAY_FUNCTIONAL_AREAS to produce reports that group field service activity by functional area and country.
  • Data partitioning and filtering: Using the DATASET column to filter reference data by integration run or tenant.

A representative query pattern is:

SELECT m.USER_NAME, m.COUNTRY_NAME, m.COUNTRY_CODE_2, m.DATASET, f.FUNCTIONAL_AREA_NAME
FROM CSF.CSF_ODF_CTRY_MAPPING m
JOIN PAY.PAY_FUNCTIONAL_AREAS f ON m.AREA_ID = f.AREA_ID
WHERE m.COUNTRY_CODE_2 = 'US';

This join confirms the link between the country mapping and the functional area definition, which is the only documented foreign key relationship.

Related Objects

The most significant related object is the parent table referenced by the sole foreign key:

  • PAY_FUNCTIONAL_AREAS — Referenced via CSF_ODF_CTRY_MAPPING.AREA_ID → PAY_FUNCTIONAL_AREAS.AREA_ID. This join is essential for resolving functional area context.

Because the table is classified as standalone, it has no other documented foreign keys. Related objects in the broader CSF and ODF integration landscape may include country reference tables (typically FND_TERRITORIES), user reference tables (FND_USER), and ODF staging or mapping tables that consume the DATASET and COUNTRY_CODE_2 values. However, only the PAY_FUNCTIONAL_AREAS relationship is explicitly documented in the ETRM metadata.

Consult the Oracle EBS Field Service and ODF integration documentation for the specific version (12.1.1 or 12.2.2) to confirm any additional dependencies introduced by patches or configuration changes.