Results for “user_pwd”

8 results




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

Overview

BSC_USER_INFO is a table within the Oracle EBS Balanced Scorecard (BSC) module, a component that Oracle has designated as obsolete in the 12.1.1 and 12.2.2 release streams. The table is described in ETRM documentation as holding "connection information," which reflects its original purpose of storing credentials and connection details associated with Balanced Scorecard users. In the ETRM reference environment, the object is recorded with the note "Not implemented in this database," meaning that it is a documented schema artifact rather than an actively populated table in the sampled instance. The physical schema is recorded with owner BSC and nine columns.

From a Data Vault modeling perspective, the mined metadata classifies BSC_USER_INFO as satellite-leaning. This is a heuristic suggestion: the table carries a surrogate primary key (SID) and descriptive attributes tied to a single parent entity, BSC_USERS, rather than acting as a hub or a many-to-many link. The classification should be treated as a design hint, not an authoritative architectural statement, particularly given the table's obsolete status.

Key Information Stored

The table's primary key is BSC_USER_INFO_PK, defined on the SID column. A documented unique index, BSC_USER_INFO_U1, also spans SID, making it a business-key candidate alongside the surrogate key. The nine documented columns are:

  • SID — surrogate identifier and the sole column in both the primary key (BSC_USER_INFO_PK) and the unique index (BSC_USER_INFO_U1).
  • USER_ID — foreign key to BSC_USERS, linking each connection record to its owning user.
  • USER_NAME, USER_PWD — stored user name and password credentials.
  • USER_TYPE — discriminator describing the category of connection or account.
  • OBSC_UN, OBSC_PWD — credentials for an associated (likely "obsolete scorecard" or internal) connection context.
  • UBSC_UN, UBSC_PWD — a second credential pair for an alternate connection context.

The proliferation of three credential pairs (USER_PWD, OBSC_PWD, UBSC_PWD) indicates the table was designed to hold multiple parallel connection identities per user, an unusual pattern now superseded.

Common Use Cases and Queries

Because the table is obsolete and unimplemented, practical use is limited to migration forensics, historical auditing, and schema analysis. Typical patterns include:

  • Resolving connections per user: SELECT i.SID, i.USER_NAME, i.USER_TYPE FROM BSC.BSC_USER_INFO i WHERE i.USER_ID = :user_id;
  • Joining to the parent entity: SELECT u.*, i.USER_NAME FROM BSC.BSC_USERS u, BSC.BSC_USER_INFO i WHERE u.USER_ID = i.USER_ID;
  • Auditing credential inventory by type: SELECT USER_TYPE, COUNT(*) FROM BSC.BSC_USER_INFO GROUP BY USER_TYPE;

Reporting queries should guard against empty results, since the table is typically unpopulated in standard 12.1.1 and 12.2.2 environments.

Related Objects

The documented foreign-key relationship anchors BSC_USER_INFO to the Balanced Scorecard user registry. Significant related objects include:

  • BSC_USERS — parent table; join via BSC_USER_INFO.USER_ID = BSC_USERS.USER_ID.
  • BSC_USER_INFO_PK — primary-key constraint on SID.
  • BSC_USER_INFO_U1 — unique index on SID, the business-key candidate.
  • Other BSC schema objects that consume user context, such as scorecard and security configuration tables, depend indirectly on the user registry that BSC_USER_INFO supplements.

Given the obsolete designation, no supported API or concurrent-program integration is documented for this table in 12.1.1 or 12.2.2.