Results for “csr_win_promis_all_b”

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

Overview

The CSR_WIN_PROMIS_ALL_B table, owned by the CSR schema, stores window-to-promise parameters used by the Oracle EBS Scheduler module (CSR). It defines the time windows available for promising delivery or service dates to customers, capturing the start and end boundaries of each promise window along with multi-organization and security-group context. The table is registered as a VALID database object in both Oracle EBS 12.1.1 and 12.2.2, and is described in the ETRM repository simply as "Window-to-promise parameters."

In terms of heuristic Data Vault classification mined from the foreign key structure, the object is treated as a standalone entity — neither a strict hub, link, nor satellite. This classification is a modeling suggestion only; in practice, the primary key (WIN_PROMIS_ID) and the foreign key to FND_SECURITY_GROUPS suggest the table functions as a configuration hub with a lightweight link to security groups. The presence of ORG_ID confirms it is organization-specific configuration data rather than transactional data.

Key Information Stored

The documented physical schema contains 26 columns. The most important are:

• WIN_PROMIS_ID — the surrogate primary key, defined by the constraint CSR_WIN_PROMIS_ALL_B_PK. This is the identifier most users search for when referencing this table.
• START_TIME and END_TIME — the opening and closing boundaries of the promise window, defining the interval during which a promise may be offered.
• ORG_ID — the operating unit / organization identifier. Together with WIN_PROMIS_ID it forms the unique business key candidate documented as CSR_WIN_PROMIS_ALL_B_U1.
• SECURITY_GROUP_ID — references FND_SECURITY_GROUPS, tying the window definition to a security group for visibility and access control.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield (DFF) columns, enabling site-specific extensions without schema changes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns tracking insert and update history.

The surrogate key WIN_PROMIS_ID is distinct from the business-key candidate (WIN_PROMIS_ID, ORG_ID) enforced by the unique index; the business key is what should be used for natural identification across organizations, while the surrogate key remains the physical row identifier.

Common Use Cases and Queries

Typical use cases include validating, extending, or decommissioning promise windows per operating unit, and reconciling scheduler promise behavior against configured boundaries. A standard lookup by identifier follows:

• SELECT WIN_PROMIS_ID, START_TIME, END_TIME, ORG_ID, SECURITY_GROUP_ID FROM CSR.CSR_WIN_PROMIS_ALL_B WHERE WIN_PROMIS_ID = :win_promis_id;
• List all windows for a given operating unit: SELECT * FROM CSR.CSR_WIN_PROMIS_ALL_B WHERE ORG_ID = :org_id ORDER BY START_TIME;
• Audit recent changes: SELECT WIN_PROMIS_ID, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM CSR.CSR_WIN_PROMIS_ALL_B WHERE LAST_UPDATE_DATE > SYSDATE - 30;

Reporting scenarios frequently join this table to organization and security-group reference data to present promise windows in business terms.

Related Objects

• FND_SECURITY_GROUPS — referenced via CSR_WIN_PROMIS_ALL_B.SECURITY_GROUP_ID; join to resolve the security group name and access rules associated with each window.
• CSR_WIN_PROMIS_ALL_B_PK — the primary key constraint on WIN_PROMIS_ID, used for direct row retrieval.
• CSR_WIN_PROMIS_ALL_B_U1 — the unique index on (WIN_PROMIS_ID, ORG_ID), supporting business-key enforcement and the common per-organization lookups.
• HR_OPERATING_UNITS / ORG_ORGANIZATION_DEFINITIONS — the standard organization views used with ORG_ID to translate the identifier into a business entity name.
• FND_FLEX_VALUES and related flexfield views — used with ATTRIBUTE_CATEGORY and ATTRIBUTE columns when the descriptive flexfield is enabled and configured.

Because the table is classified as standalone, no additional parent-child FK dependencies beyond FND_SECURITY_GROUPS are documented, which simplifies dependency analysis during upgrades and cloning.