Results for “distribution_set_id”

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

Overview

AP_DISTRIBUTION_SETS_DSN_V is a view owned by the APPS schema within the Oracle Payables (AP) module. As documented in the ETRM metadata, its description carries the annotation "(Release 10SC Only)", indicating that the object originated in an early release of the Oracle Applications Financials family and has been retained in the data dictionary for backward compatibility. The view is currently marked VALID in both Oracle E-Business Suite 12.1.1 and 12.2.2, meaning it continues to compile and resolve against its underlying base object even though it is not a core object in the current release.

The "DSN" suffix in the object name denotes "distribution set name", and the view is designed specifically to expose a filtered, name-oriented projection of the AP_DISTRIBUTION_SETS table. Its role is to present only those distribution sets that are active and that allocate exactly one hundred percent of a transaction amount. Because distribution sets are reusable templates that determine how an invoice or payment line is apportioned across accounts, this view serves as a convenient lookup surface for reports, list-of-values definitions, and integration extracts that need a simple list of valid, fully-allocated distribution set names. Users searching on the term "distribution_set_name" are typically routed to this object because its first exposed column, DISTRIBUTION, is derived directly from the DISTRIBUTION_SET_NAME base column and is the most human-readable attribute available.

Underlying Base Objects

The view is defined over a single documented base object: AP_DISTRIBUTION_SETS, referenced in the metadata as a synonym. In the APPS schema, AP_DISTRIBUTION_SETS is the synonym that resolves to the Payables distribution sets entity, which stores the header definition of each distribution set, including its name, identifier, allocation percentages, and inactive date. The view does not join to any additional table; it is a straight projection with a filter predicate, which keeps its execution plan simple and its maintenance cost low.

The defining query selects DISTRIBUTION_SET_NAME, DISTRIBUTION_SET_ID, and TOTAL_PERCENT_DISTRIBUTION from the base object, applying two restricting conditions: the record must not be inactive, expressed as NVL(INACTIVE_DATE, SYSDATE + 1) > SYSDATE, and the total percentage distribution must equal 100. The NVL construct treats a null inactive date as a future date, so rows without a defined inactivation date are always considered active. Consequently, the view behaves as a static, always-current snapshot of usable distribution sets rather than a historical record.

Key Columns

• DISTRIBUTION — The alias assigned to the base column DISTRIBUTION_SET_NAME. This is the principal business-facing attribute and the value most commonly used in lookups, reports, and integration payloads. It carries the descriptive name that users recognize when selecting a distribution set.
• DISTRIBUTION_SET_ID — The unique system identifier for the distribution set, sourced from DISTRIBUTION_SET_ID in the base table. It is the primary key of the underlying entity and is the correct column to use for joins to distribution set line tables or for programmatic references where names may change.
• TOTAL_PERCENT_DISTRIBUTION — The aggregate allocation percentage of the distribution set, sourced from TOTAL_PERCENT_DISTRIBUTION. Because the view's filter forces this value to equal 100, the column always returns the value 100 in every row. It is retained in the projection primarily for reporting clarity and to confirm that the returned sets are fully allocated.

Common Use Cases and Queries

The most frequent use case is providing a validated list of active, fully-allocated distribution set names for a value set, a concurrent program parameter, or an ad hoc report. Because the view already filters inactive and non-100-percent sets, consuming applications avoid duplicating that logic. A typical query is:

SELECT distribution, distribution_set_id, total_percent_distribution FROM apps.ap_distribution_sets_dsn_v ORDER BY distribution;

For a targeted lookup by name, the DISTRIBUTION column can be constrained directly:

SELECT distribution_set_id FROM apps.ap_distribution_sets_dsn_v WHERE distribution = :p_distribution_set_name;

Integration scenarios commonly join the view's identifier back to the distribution set lines to retrieve the account and percentage detail needed to construct invoice distributions. A representative pattern is:

SELECT v.distribution_set_id, v.distribution, l.distribution_line_number, l.percent FROM apps.ap_distribution_sets_dsn_v v, apps.ap_distribution_set_lines l WHERE v.distribution_set_id = l.distribution_set_id ORDER BY v.distribution, l.distribution_line_number;

Because the underlying base object is a synonym owned by APPS, queries should be issued with the APPS schema prefix, and access should be granted through standard APPS responsibilities. Given the "(Release 10SC Only)" annotation, implementers should treat the view as a legacy compatibility object, confirm its continued validity after any upgrade, and prefer current Payables APIs where transaction creation, rather than reporting, is the objective.