Results for “country_code”

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

Overview

The PV_COUNTRY_TIMEOUTS table is a Partner Management (PV) module data object that stores timeout periods defined on a per-country basis. It resides in the PV schema and holds a status of VALID in both Oracle EBS 12.1.1 and 12.2.2. Functionally, the table supplies the configurable duration values that govern time-sensitive partner-management processing, allowing organizations to apply different timeout thresholds depending on the territory in which a partner or transaction is registered.

Under the heuristic Data Vault classification mined from its foreign-key structure, PV_COUNTRY_TIMEOUTS is assessed as satellite-leaning. In modeling terms, this suggests the table behaves primarily as a descriptive attribute store attached to a parent business key (the country/territory), rather than as an independent hub of business entities or as a pure associative link between two hubs. The classification is offered as a modeling suggestion and should be validated against actual usage.

Key Information Stored

The table is documented with 11 physical columns. The most significant are:

• TIMEOUT_ID — The surrogate primary key, enforced by the PV_COUNTRY_TIMEOUTS_PK constraint and also backed by the unique index PV_COUNTRY_TIMEOUTS_U1.
• TIMEOUT_TYPE and COUNTRY_CODE — Together these form the business-key candidate enforced by the unique index PV_COUNTRY_TIMEOUTS_U2, ensuring each timeout type is defined only once per country.
• TIMEOUT_PERIOD — The numeric duration value (the timeout length) associated with a given type and country.
• COUNTRY_CODE — The foreign key to FND_TERRITORIES, identifying the territory to which the timeout applies.
• SECURITY_GROUP_ID — The foreign key to FND_SECURITY_GROUPS, supporting multi-org / security-group data partitioning.
• Standard WHO/audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER (used for optimistic locking).

Common Use Cases and Queries

Typical uses include reporting on configured timeouts by country, auditing territory-specific configuration, and troubleshooting partner-management processing where a timeout appears inconsistent across regions. A representative query retrieves all timeout periods for a given territory:

• SELECT t.timeout_type, t.timeout_period, t.country_code
  FROM pv_country_timeouts t
 WHERE t.country_code = :country_code;

Because COUNTRY_CODE references FND_TERRITORIES, joins are commonly made to resolve the territory name, and to FND_SECURITY_GROUPS for security-group context. A reporting join pattern is:

• SELECT ft.territory_short_name, t.timeout_type, t.timeout_period
  FROM pv_country_timeouts t, fnd_territories ft
 WHERE t.country_code = ft.territory_code;

The TIMEOUT_TYPE plus COUNTRY_CODE unique constraint makes it a reliable lookup source when resolving the applicable timeout for a specific type and territory.

Related Objects

The following objects are most significant to PV_COUNTRY_TIMEOUTS:

• FND_TERRITORIES — Referenced via PV_COUNTRY_TIMEOUTS.COUNTRY_CODE; supplies territory names and validation. This is the object most directly relevant to the search term fnd_territories.
• FND_SECURITY_GROUPS — Referenced via PV_COUNTRY_TIMEOUTS.SECURITY_GROUP_ID, enforcing security-group partitioning.
• FND_TERRITORIES-dependent views and PV module processing logic that read timeout configuration during partner operations.
• PV_COUNTRY_TIMEOUTS_PK and unique indexes PV_COUNTRY_TIMEOUTS_U1 (TIMEOUT_ID) and PV_COUNTRY_TIMEOUTS_U2 (TIMEOUT_TYPE, COUNTRY_CODE), which enforce data integrity.