Search Results cs_chg_sub_restrictions




Overview
Explore in AI Chat

Overview

The CS_CHG_SUB_RESTRICTIONS table, owned by the CS (Service) schema, stores configuration rules that govern automatic submission of charges within Oracle E-Business Suite Service modules. It functions as a control table that determines when charge lines generated by service contracts, subscriptions, or related service transactions may be released for automatic billing or invoicing, and when such submission must be blocked or deferred because a qualifying restriction condition applies.

In Oracle EBS 12.1.1 and 12.2.2, the table is available and marked VALID. From a Data Vault modeling perspective, the mined foreign key structure classifies this object as a standalone entity rather than a hub, link, or satellite. This is a heuristic suggestion only: the only documented foreign key targets the security infrastructure (FND_SECURITY_GROUPS), not a business parent, so no natural business hub-link-satellite pattern is exposed through the constraints. Practically, this reflects a configuration/reference table whose restriction definitions are applied procedurally by the charge submission programs rather than enforced through declarative parent relationships.

Key Information Stored

The table contains 32 documented columns. The most significant are:

  • RESTRICTION_ID — the surrogate primary key, uniquely identifying each restriction row. It is the sole column of the primary key constraint CS_CHG_SUB_RESTRICTIONS_PK.
  • RESTRICTION_TYPE — classifies the kind of submission restriction being defined, driving which evaluator logic the submitting process applies.
  • CONDITION — the condition text or code evaluated to decide whether the restriction is triggered.
  • VALUE_OBJECT_ID and VALUE_AMOUNT — the qualifying object and the threshold monetary amount associated with the restriction.
  • CURRENCY_CODE — currency of VALUE_AMOUNT; relevant when thresholds are compared across transactions.
  • START_DATE_ACTIVE and END_DATE_ACTIVE — the effective date range during which the restriction is enforced, making the table a date-effective reference set.
  • SECURITY_GROUP_ID — the only documented foreign key column, referencing FND_SECURITY_GROUPS, controlling row-level visibility in a multi-organization or secured deployment.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/BC4J framework during concurrent maintenance.
  • ATTRIBUTE1–ATTRIBUTE15, CONTEXT — the standard EBS descriptive flexfield columns available for customer-specific extension.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns.
  • ZD_EDITION_NAME — the editioning column introduced by the 12.2 online patching (Edition-Based Redefinition) architecture; it also participates in the unique business-key index CS_CHG_SUB_RESTRICTIONS_U1 alongside RESTRICTION_ID.

Common Use Cases and Queries

Typical use cases include diagnosing why a charge line was not auto-submitted, auditing the set of active restrictions for a given period, and reporting restrictions that are nearing expiry.

To retrieve currently effective restrictions:

  • SELECT restriction_id, restriction_type, condition, value_amount, currency_code FROM cs.cs_chg_sub_restrictions WHERE TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);

To scope rows by security group in a secured environment:

  • SELECT r.* FROM cs.cs_chg_sub_restrictions r, fnd_security_groups g WHERE r.security_group_id = g.security_group_id;

For audit and change tracking, join the audit columns to FND_USER on CREATED_BY and LAST_UPDATED_BY. Under 12.2 EBR, always filter or be aware of ZD_EDITION_NAME where editions are in play.

Related Objects

  • FND_SECURITY_GROUPS — referenced by CS_CHG_SUB_RESTRICTIONS.SECURITY_GROUP_ID; the only documented foreign key relationship.
  • CS_CHG_SUB_RESTRICTIONS_PK — primary key constraint on RESTRICTION_ID.
  • CS_CHG_SUB_RESTRICTIONS_U1 — unique index on RESTRICTION_ID, ZD_EDITION_NAME, the documented business-key candidate.
  • CS_SERVICE_CHARGES / charge submission interfaces — the Auto Submission of Charges process consumes these restriction definitions when evaluating whether to submit charges.
  • FND_USER — joined via the WHO audit columns for ownership and change history.

Because the declaration contains a single foreign key, referencing objects are primarily procedural consumers rather than declarative dependents, so integration queries should confirm the exact evaluator program in use for a given release.