Results for “first_char_flag”

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

Overview

JTY_DEA_ATTR_PRODUCTS is a CRM Foundation (JTF) table that stores attribute product records used for date effectivity assignment. Within Oracle E-Business Suite 12.1.1 and 12.2.2, the table supports the date-effectivity framework that governs when a given attribute-product relationship is active, allowing CRM applications — most notably territory and resource assignment functions — to resolve which attributes apply to a product over a defined effective period. The table resides in the JTF schema, holds VALID status in the data dictionary, and comprises 15 documented columns.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a standalone classification. No parent-child hierarchy or outbound dependency chain beyond the security group reference is documented, so the table may be modeled as an independent hub-adjacent structure rather than as a link or satellite. This classification is heuristic and should be validated against actual ETL lineage before adoption.

Key Information Stored

The documented columns describe a compact record centered on a surrogate identifier and a set of foreign-key and control attributes.

• DEA_ATTR_PRODUCTS_ID — the surrogate primary key uniquely identifying each attribute-product date-effectivity record.
• ATTR_RELATION_PRODUCT — the attribute-product relationship descriptor; a principal business attribute of the row.
• SOURCE_ID — source identifier tying the record back to its originating entity or dataset.
• TRANS_TYPE_ID — transaction type identifier qualifying the nature of the assignment.
• TERR_ANALYZE_ID — territory analysis identifier, linking the row to territory evaluation logic.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-tenant data segregation.
• FIRST_CHAR_FLAG and BUILD_INDEX_FLAG — processing control flags governing index-building behavior.
• INDEX_NAME — the index identifier associated with the record.
• Audit and concurrency columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER, the last supporting optimistic locking under the OAF framework.

No unique business-key index is documented in the supplied metadata; the surrogate DEA_ATTR_PRODUCTS_ID remains the reliable join key.

Common Use Cases and Queries

Typical usage centers on resolving which attributes apply to a product during date-effectivity evaluation, and on reporting territory analysis configuration.

• Retrieving all attribute-product rows for a security group: SELECT * FROM jtf.jty_dea_attr_products WHERE security_group_id = :p_sg_id;
• Joining territory analysis records: SELECT d.dea_attr_products_id, d.attr_relation_product, d.terr_analyze_id FROM jtf.jty_dea_attr_products d WHERE d.terr_analyze_id = :p_terr_id;
• Audit reporting on recent changes using LAST_UPDATE_DATE and LAST_UPDATED_BY.
• Validating data segregation by joining to FND_SECURITY_GROUPS on SECURITY_GROUP_ID.

Related Objects

• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; the only documented foreign key.
• JTY_DEA_ATTR_PRODUCTS territory analysis entities keyed by TERR_ANALYZE_ID.
• CRM Foundation territory and resource assignment tables consuming date-effectivity attribute data.
• OAF-based maintenance pages relying on OBJECT_VERSION_NUMBER for optimistic locking.