Results for “shipping_interval”
36 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OE_CREDIT_CHECK_RULES_115 is an APPS-owned database view within the Oracle Order Management (ONT) product family, valid in Oracle E-Business Suite 12.1.1 and 12.2.2. Per the documented metadata, the object is explicitly flagged as "No longer used." This designation indicates that the view is a legacy artifact retained for backward compatibility and is not referenced by any active application logic, concurrent program, or supported integration path in the current release.
The view exposes the credit checking rule definitions historically maintained by Order Management. Credit check rules determine when an order or order line should be flagged for credit review, based on criteria such as open receivables balances, uninvoiced orders, orders already on hold, and configurable time intervals. The _115 suffix corresponds to the multi-org / multi-language view naming convention used throughout EBS, in which a view is layered over an underlying synonym to support row-level security and language-specific filtering. In practice, however, this particular view simply selects all columns directly from its base object without any WHERE clause, organization filter, or language predicate, reflecting its deprecated status.
Because the view survives in the data dictionary, it will appear in ETRM inventories, schema crawls, and dependency reports. Practitioners searching for credit_check_rule_id will frequently encounter it. Understanding its purpose and its retired status is essential to avoid building new customizations on a non-supported object.
Underlying Base Objects
The view is defined over a single referenced base object:
- OE_CREDIT_CHECK_RULES — accessed through a SYNONYM owned by APPS.
The relationship is a straightforward one-to-one projection. Every row in OE_CREDIT_CHECK_RULES_115 corresponds to one row in OE_CREDIT_CHECK_RULES, with no joins, aggregations, or filtering applied. The view text confirms a simple SELECT ... FROM OE_CREDIT_CHECK_RULES mapping all 33 documented columns verbatim. The primary key of the base table is CREDIT_CHECK_RULE_ID, which is carried through unchanged into the view.
Because the view performs no transformation, any DML or query behavior exhibited against the base table is replicated here. DML against the view is generally not supported, as it is a read-only projection intended for query and reporting access.
Key Columns
The view exposes the complete column set of the underlying credit check rules table. The most significant columns include:
- CREDIT_CHECK_RULE_ID — The primary key and the column most commonly searched by developers and analysts. It uniquely identifies each credit checking rule.
- NAME — The user-defined name of the credit check rule, typically seeded or configured during implementation.
- FAILURE_RESULT_CODE — Determines the outcome when a credit check fails, such as hold or rejection.
- OPEN_AR_BALANCE_FLAG, UNINVOICED_ORDERS_FLAG, ORDERS_ON_HOLD_FLAG — Boolean indicators controlling which credit exposure factors are evaluated.
- SHIPPING_INTERVAL and OPEN_AR_DAYS — Define the lookback window applied to receivables and shipment history.
- START_DATE_ACTIVE / END_DATE_ACTIVE — Date-range activation for the rule.
- INCLUDE_TAX_FLAG, INCLUDE_PAYMENTS_AT_RISK_FLAG — Optional inclusion criteria for exposure calculation.
- CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — Descriptive flexfield columns for extensibility.
- CREATION_DATE, CREATED_BY, and the audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) — Standard EBS who-columns.
Common Use Cases and Queries
Given the "No longer used" status, the view should not be used in new development. Its legitimate remaining uses are diagnostic and historical: confirming whether legacy custom code references the object, validating inherited configurations during upgrade assessments, and supporting impact analysis for decommissioning. A typical lookup by primary key is:
SELECT credit_check_rule_id, name, failure_result_code, open_ar_days
FROM apps.oe_credit_check_rules_115
WHERE credit_check_rule_id = :rule_id;
Analysts auditing active rules during 12.1.1 to 12.2.2 migrations may also enumerate all rows:
SELECT credit_check_rule_id, name, start_date_active, end_date_active
FROM apps.oe_credit_check_rules_115
ORDER BY credit_check_rule_id;
Where current functionality is required, applications should query the supported OE_CREDIT_CHECK_RULES synonym directly or use the corresponding credit management APIs and UI in Order Management. Repositories and integrations that still reference the deprecated view should be remediated to eliminate reliance on an unsupported object.
-
No longer used
APPS.OE_CREDIT_CHECK_RULES_115·↳ OE_CREDIT_CHECK_RULES·Explore ONT module →
-
Table to store Credit Check Rules.
-
This table stores information about the credit check rules.
-
No longer used
APPS.OE_CREDIT_CHECK_RULES_115·↳ OE_CREDIT_CHECK_RULES·Explore ONT module →
-
Table to store Credit Check Rules.
-
This table stores information about the credit check rules.
-
eTRM - OE Tables and Views 12.2.2
Temporary table
-
eTRM - OE Tables and Views 12.1.1
Temporary table
-
eTRM - ONT Tables and Views 12.1.1
OM WorkFlow Activity Skip Log.
-
eTRM - ONT Tables and Views 12.2.2
OM WorkFlow Activity Skip Log.