Results for “locked_flag”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
FND_PRIVACY_ATTRIBUTES_B is a core configuration table in the Oracle E-Business Suite Application Object Library (FND), owned by the APPLSYS schema. It stores the definition of privacy attributes that the EBS Data Privacy and Data Vault framework uses to identify, classify, and protect sensitive data elements across the application. Each row describes a single privacy attribute — a logical name that the framework maps to physical columns in application tables — together with metadata governing how that attribute should be treated for personally identifiable information (PII), sensitivity, locking, and descrambling behavior.
In Oracle EBS 12.1.1 and 12.2.2, this table underpins the Data Privacy feature set that helps organizations comply with privacy regulations (for example, GDPR and CCPA) by allowing administrators to declare which fields contain sensitive personal data. The "_B" suffix denotes the base (language-independent) table; translated or descriptive elements typically reside in an associated "_TL" table. From a data-modeling perspective, the mined metadata classifies FND_PRIVACY_ATTRIBUTES_B heuristically as a standalone entity, suggesting it behaves as a hub-like reference table rather than a link or satellite. The single foreign key to FND_SECURITY_GROUPS indicates the table participates in the multi-tenant security group model.
Key Information Stored
The table contains 30 documented columns. The most significant include:
- PRIVACY_ATTRIBUTE_CODE — the business-key candidate, protected by the unique index FND_PRIVACY_ATTRIBUTES_B_U1. This is the human-readable identifier used to reference the attribute throughout the framework.
- PRIVACY_ATTRIBUTE_TYPE — classifies the nature of the attribute, guiding how the framework interprets it.
- SENSITIVITY — records the sensitivity level assigned to the attribute, informing protection and masking decisions.
- PII_FLAG — indicates whether the attribute is considered personally identifiable information.
- LOCKED_FLAG — signals that the attribute definition is locked against modification.
- DSCRAM_LEVEL and DSCRAM_ALGO_ID — control descrambling level and algorithm used by the Data Vault scrambling mechanism.
- SECURITY_GROUP_ID — the foreign key linking the attribute to a security group in FND_SECURITY_GROUPS.
- OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — standard EBS audit and optimistic-locking columns.
- ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard DFF (descriptive flexfield) columns enabling extensible attribute metadata.
The primary key is the surrogate key on the attribute record, while PRIVACY_ATTRIBUTE_CODE serves as the unique business key.
Common Use Cases and Queries
Typical scenarios include auditing which attributes are flagged as PII, generating compliance reports, and validating security-group assignments before enabling Data Vault scrambling.
- List all PII attributes:
SELECT PRIVACY_ATTRIBUTE_CODE, PRIVACY_ATTRIBUTE_TYPE, SENSITIVITY FROM FND_PRIVACY_ATTRIBUTES_B WHERE PII_FLAG = 'Y'; - Find locked attributes:
SELECT PRIVACY_ATTRIBUTE_CODE, LOCKED_FLAG FROM FND_PRIVACY_ATTRIBUTES_B WHERE LOCKED_FLAG = 'Y'; - Join to security groups:
SELECT p.PRIVACY_ATTRIBUTE_CODE, g.SECURITY_GROUP_NAME FROM FND_PRIVACY_ATTRIBUTES_B p, FND_SECURITY_GROUPS g WHERE p.SECURITY_GROUP_ID = g.SECURITY_GROUP_ID; - Inspect descrambling configuration: query DSCRAM_LEVEL and DSCRAM_ALGO_ID to reconcile with Data Vault setup.
Related Objects
- FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; the principal foreign-key relationship.
- FND_PRIVACY_ATTRIBUTES_TL — likely translation/description companion for language-dependent text.
- FND_PRIVACY_ATTRIBUTE_USAGES — maps attributes to physical columns (framework usage).
- FND_DATA_VAULT_* objects — descrambling and vault configuration consuming DSCRAM_LEVEL/DSCRAM_ALGO_ID.
- FND_DF_FLEXFIELDS — relevant where ATTRIBUTE_CATEGORY flexfield metadata is interpreted.
These relationships confirm FND_PRIVACY_ATTRIBUTES_B as the reference hub anchoring EBS privacy and Data Vault configuration.
-
Header level information for consolidation processes
-
Table that stores the information related to Security Grants defined by the user.
-
View: IGS_SC_GRANTS_V 12.1.1
Self-Service view
APPS.IGS_SC_GRANTS_V·↳ IGS_SC_GRANTS·↳ WF_LOCAL_ROLES·Explore IGS module →
-
This table stores information about visits
-
Stores tracking information on pristine data loads made to FEM_BALANCES
-
PA_CONTROL_ITEMS stores user-defined control items in a project. Each item is of an item type as specified by the CI_TYPE_ID column. The items are categorized using the Classification, Reason and Priority attributes
-
APPS.FND_PRIVACY_ATTRIBUTES_VL·↳ FND_PRIVACY_ATTRIBUTES_B·↳ FND_PRIVACY_ATTRIBUTES_TL·Explore FND module →
-
APPS.FND_PRIVACY_ATTRIBUTES_VL·↳ FND_PRIVACY_ATTRIBUTES_B·↳ FND_PRIVACY_ATTRIBUTES_TL·Explore FND module →
-
View: XNP_SV_SOA_VL 12.2.2
Shows porting information for a single telephone number. Removed ( SVA.CREATED_BY_SP_ID=SPR_OWN.SP_ID ) from WHERE clausefor Service Bureau, since this will be handled automagically by VPD. rnyberg, 11/06/2000.
APPS.XNP_SV_SOA_VL·↳ XNP_ROUTING_NUMBERS·↳ XNP_SERVICE_PROVIDERS·↳ XNP_SV_SOA·Explore XNP module →
-
View: XNP_SV_SOA_VL 12.1.1
Shows porting information for a single telephone number. Removed ( SVA.CREATED_BY_SP_ID=SPR_OWN.SP_ID ) from WHERE clausefor Service Bureau, since this will be handled automagically by VPD. rnyberg, 11/06/2000.
APPS.XNP_SV_SOA_VL·↳ XNP_ROUTING_NUMBERS·↳ XNP_SERVICE_PROVIDERS·↳ XNP_SV_SOA·Explore XNP module →
-
Container object for a porting request on a single telephone number
-
View: PA_CI_BASIC_CTL_V 12.2.2
APPS.PA_CI_BASIC_CTL_V·↳ FND_CURRENCIES_TL·↳ HZ_PARTIES·↳ PA_CI_TYPES_VL·Explore PA module →
-
View: AHL_VISITS_VL 12.2.2
This view stores the query to retrieve Visit information
APPS.AHL_VISITS_VL·↳ AHL_VISITS_B·↳ AHL_VISITS_TL·Explore AHL module →
-
Container object for a porting request on a single telephone number
-
Journalling table for the XNP_SV_SOA table
-
Journalling table for the XNP_SV_SOA table
-
VIEW: AHL.AHL_VISITS_B# 12.2.2
-
VIEW: PA.PA_CONTROL_ITEMS# 12.2.2
-
VIEW: XNP.XNP_SV_SOA# 12.2.2
-
VIEW: XNP.XNP_SV_SOA_JN# 12.2.2
-
VIEW: APPS.IGS_SC_GRANTS_V 12.1.1
-
TABLE: IGS.IGS_SC_GRANTS 12.1.1
-
TABLE: GCS.GCS_CONS_ENG_RUNS 12.1.1
-
VIEW: AHL.AHL_VISITS_B# 12.2.2
-
View: IGS_SC_GRANTS_V 12.2.2
Self-Service view
Not implemented in this database·Explore IGS module →
-
VIEW: PA.PA_CONTROL_ITEMS# 12.2.2
-
TABLE: GCS.GCS_DATA_SUB_DTLS 12.1.1
-
VIEW: XNP.XNP_SV_SOA# 12.2.2
-
VIEW: XNP.XNP_SV_SOA_JN# 12.2.2