Results for “cac_sync_store_data”

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

Overview

CAC_SYNC_STORE_DATA is a CRM Foundation (JTF) schema table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores attribute-level payload data associated with synchronization agents and principals. It resides in the JTF schema and is documented as VALID in ETRM 12.2.2. The table functions as a key-value store: each row binds a named attribute (NAME) and its value (VALUE) to a synchronization agent (AGENT_ID) and a principal (PRINCIPAL_ID). This design allows synchronization processes to persist arbitrary configuration and state data without requiring schema changes for each new attribute.

In the context of the user search "Data Cloud Org login," this table is relevant because principals represent the organizational or user identities participating in CRM synchronization, and the store data holds the attributes associated with those identities. Oracle's heuristic Data Vault classification for this table is standalone, meaning the mined foreign-key structure does not fit a clean hub, link, or satellite pattern. As a modeling suggestion, the table behaves most like a satellite attached to a principal, with AGENT_ID and NAME collectively forming the descriptive context for each VALUE. The single foreign key to CAC_SYNC_PRINCIPALS anchors each row to an owning principal.

Key Information Stored

The table is documented with ten columns. The most significant are summarized below.

• STORE_DATA_ID — The surrogate primary key for each row, uniquely identifying a stored attribute instance.
• PRINCIPAL_ID — Foreign key to CAC_SYNC_PRINCIPALS, identifying the principal (organization or user) that owns the stored data. This is the primary linkage used when resolving login or organizational identity context.
• AGENT_ID — Identifies the synchronization agent associated with the row. Because the unique index includes AGENT_ID, the same attribute name may be stored independently for different agents under the same principal.
• NAME — The attribute or property name being stored, such as a profile key or configuration token.
• VALUE — The attribute value corresponding to NAME. Together, NAME and VALUE form the effective key-value payload.

The business-key candidate is defined by the unique index CAC_SYNC_STORE_DATA_U1 on (NAME, PRINCIPAL_ID, AGENT_ID). This confirms that a given attribute name is unique per principal and per agent combination. Audit columns CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN follow standard Oracle EBS conventions and support change tracking and concurrent processing diagnostics.

Common Use Cases and Queries

Typical use cases include diagnosing synchronization failures, auditing stored configuration per principal, and reporting which attributes are maintained for each agent. A representative query retrieves all stored attributes for a principal:

• SELECT s.NAME, s.VALUE, s.AGENT_ID FROM JTF.CAC_SYNC_STORE_DATA s WHERE s.PRINCIPAL_ID = :principal_id;
• SELECT s.* FROM JTF.CAC_SYNC_STORE_DATA s WHERE s.NAME = :attribute_name AND s.AGENT_ID = :agent_id;
• SELECT p.*, s.NAME, s.VALUE FROM JTF.CAC_SYNC_PRINCIPALS p JOIN JTF.CAC_SYNC_STORE_DATA s ON s.PRINCIPAL_ID = p.PRINCIPAL_ID;

Because the table stores values as text, reporting should cast or interpret values according to the expected attribute semantics. Performance is generally driven by the unique index and the PRINCIPAL_ID foreign key; queries filtering on PRINCIPAL_ID or on the unique key columns benefit most.

Related Objects

• CAC_SYNC_PRINCIPALS — Referenced by the documented foreign key CAC_SYNC_STORE_DATA.PRINCIPAL_ID. Join on PRINCIPAL_ID.
• JTF.CAC_SYNC_STORE_DATA_U1 — Unique index on (NAME, PRINCIPAL_ID, AGENT_ID), enforcing business-key uniqueness.
• CRM Foundation (JTF) synchronization agent objects — AGENT_ID associates rows with synchronization agents, which may be resolved through the corresponding agent definition tables in the JTF schema.
• JTF concurrent and audit views — Standard audit columns integrate with EBS audit and concurrent request reporting.

Administrators troubleshooting Data Cloud organization login or synchronization issues should begin with CAC_SYNC_PRINCIPALS for identity resolution and then inspect CAC_SYNC_STORE_DATA for the attribute-level state associated with each agent and principal.