Search Results csp_safety_factors




Overview
Explore in AI Chat

Overview

The CSP_SAFETY_FACTORS table is a reference and lookup object within the CSP (Spares Management) product module of Oracle E-Business Suite. It stores safety factor definitions that drive spare parts inventory planning, where a safety factor is a multiplier applied to expected demand to buffer against variability in lead times, demand fluctuations, and service-level commitments. In EBS releases 12.1.1 and 12.2.2, this table resides in the CSP schema and is documented with a VALID status. It functions as a configuration-driven lookup rather than a transactional table: rows are typically maintained by planners or administrators and are referenced during replenishment, min-max planning, and service-level computations for spare parts.

From a Data Vault modeling perspective, the mined metadata classifies CSP_SAFETY_FACTORS heuristically as standalone. This suggests the table behaves as an independent reference or lookup entity rather than a transactional hub or a dependent satellite. It carries its own surrogate primary key and a limited, slowly changing set of descriptive attributes that describe safety factor policy.

Key Information Stored

The table is documented with 11 columns in the ETRM 12.2.2 physical schema. The most significant columns are:

  • SAFETY_FACTOR_ID — the surrogate primary key, defined by the CSP_SAFETY_FACTORS_PK constraint. It uniquely identifies each safety factor record.
  • SERVICE_LEVEL — the target service level associated with the safety factor, used to determine the buffer required to meet a defined probability of not stocking out.
  • EXPOSURES — exposure or demand variability input used in the safety factor calculation.
  • SAFETY_FACTOR — the numeric multiplier or factor value applied during planning calculations.
  • ZD_EDITION_NAME — the editioning column, appearing alongside SAFETY_FACTOR_ID in the unique index CSP_SAFETY_FACTORS_U1. This index constitutes the business-key candidate. Editioning supports EBS 12.2.2 online patching and multi-tenant edition-based redefinition.
  • SECURITY_GROUP_ID — the foreign key to FND_SECURITY_GROUPS, enforcing multi-org and security-group data access control.
  • Standard Who Columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN capture audit lineage for each record.

The unique index CSP_SAFETY_FACTORS_U1 on (SAFETY_FACTOR_ID, ZD_EDITION_NAME) distinguishes the surrogate primary key from business-key candidates and reflects the edition-aware design of 12.2.2.

Common Use Cases and Queries

Typical uses include reviewing configured safety factors, validating service-level commitments, and joining safety factor values into spare parts planning reports. A representative query retrieves the active, edition-appropriate safety factor rows:

  • SELECT SAFETY_FACTOR_ID, SERVICE_LEVEL, EXPOSURES, SAFETY_FACTOR FROM CSP.CSP_SAFETY_FACTORS WHERE ZD_EDITION_NAME = 'ORA$BASE';
  • Reporting joins on SECURITY_GROUP_ID to FND_SECURITY_GROUPS to restrict output to the operating unit or security group in scope.
  • Audit queries using CREATED_BY / LAST_UPDATED_BY joined to FND_USER to trace who configured a given factor.

Common scenarios include administering the lookup table, tuning service levels for critical spares, and ensuring planning engines retrieve the correct factor for each exposure and service-level combination.

Related Objects

The documented relationship data identifies one foreign key and several implied dependencies:

  • FND_SECURITY_GROUPS — referenced by CSP_SAFETY_FACTORS.SECURITY_GROUP_ID for security-group scoping.
  • CSP_SAFETY_FACTORS_PK — the primary key constraint on SAFETY_FACTOR_ID.
  • CSP_SAFETY_FACTORS_U1 — the unique index on (SAFETY_FACTOR_ID, ZD_EDITION_NAME).
  • FND_USER — join target for the CREATED_BY and LAST_UPDATED_BY audit columns.
  • CSP planning and replenishment tables — downstream consumers that read safety factor values during spare parts planning.

As a standalone lookup, CSP_SAFETY_FACTORS is referenced by CSP planning logic rather than owning child records, making it a configuration anchor for spares safety stock policy.