Search Results sampling_plan_desc

Overview

GMD_SAMPLING_PLANS_VL is an APPS-owned, VALID view in Oracle E-Business Suite Release 12.1.1 and 12.2.2, delivered as part of the GMD Process Manufacturing Product Development module. It presents sampling plan definitions used in process manufacturing quality operations, where a sampling plan determines how many samples are drawn, in what quantity, in which unit of measure, and at what frequency during production, receiving, or quality inspection activities.

The view follows the standard Oracle EBS "_VL" (view with translation, language-specific) naming convention. It is a reporting and integration artifact rather than a transactional entity: it joins the language-independent base table to its translation table so that the description column is returned in the session's current language. External reports, concurrent programs, Discoverer workbooks, OBIEE extracts, and interface programs query this view rather than the base tables directly, because it returns the multilingual description without requiring an explicit join at the call site. The view is not a table and holds no data of its own; all values are read from the underlying base objects at query time.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, the view is defined over two referenced base objects, both exposed to APPS through synonyms:

• GMD_SAMPLING_PLANS_B — the language-independent base table holding the sampling plan header and its operational attributes (identifier, name, sample counts and quantities, frequency, reserve and archive settings, DFF attributes, and WHO audit columns).
• GMD_SAMPLING_PLANS_TL — the translation table holding the language-specific description, keyed by the same sampling plan identifier.

The view text joins the two on SAMPLING_PLAN_ID and additionally restricts the translation row with T.LANGUAGE = USERENV('LANG'), so exactly one translated row is returned per sampling plan in the session language. No outer join is applied, so a sampling plan lacking a matching translation row for the session language is not returned. The view also selects B.ROWID as ROW_ID, which for the B table is a valid base-row identifier usable in limited contexts, but because the view is a join it is not inherently updatable and cannot generally be used for DML.

Key Columns

• SAMPLING_PLAN_ID — primary identifier of the sampling plan; the join key between B and TL and the recommended foreign key for downstream references.
• SAMPLING_PLAN_NAME — user-defined name from the base table (not translated).
• SAMPLING_PLAN_DESC — language-specific description drawn from the translation table.
• SAMPLE_CNT_REQ — number of samples required.
• SAMPLE_QTY — the search term reported by the user; the quantity to be drawn per sample.
• SAMPLE_QTY_UOM — unit of measure applicable to SAMPLE_QTY.
• FREQUENCY_TYPE, FREQUENCY_CNT, FREQUENCY_PER — define how often sampling occurs (type of frequency, count, and period).
• RESERVE_CNT_REQ, RESERVE_QTY — reserve (retained) sample count and quantity.
• ARCHIVE_CNT_REQ, ARCHIVE_QTY — archive sample count and quantity.
• DELETE_MARK — soft-delete/obsolete indicator; exclude rows where this is set.
• TEXT_CODE, ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE30 — descriptive flexfield context and segment values.
• CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — WHO audit columns.

Common Use Cases and Queries

Typical scenarios include listing active sampling plans for a quality report, reconciling sample quantities against UOM, and exposing plan definitions to integrations. Because the view filters on the session language, callers should set the language environment or supply an explicit language when running under a controlled session.

• List active plans with quantity information:

SELECT sampling_plan_name, sampling_plan_desc, sample_cnt_req, sample_qty, sample_qty_uom FROM apps.gmd_sampling_plans_vl WHERE NVL(delete_mark,0) = 0 ORDER BY sampling_plan_name;

• Retrieve all plans with their frequency rules and reserve/archive settings:

SELECT sampling_plan_id, sampling_plan_name, frequency_type, frequency_cnt, frequency_per, reserve_cnt_req, reserve_qty, archive_cnt_req, archive_qty FROM apps.gmd_sampling_plans_vl;

• Use it as a lookup for joins in custom reports or interfaces by matching on SAMPLING_PLAN_ID; join the base table GMD_SAMPLING_PLANS_B directly when the translated description is not required or when a specific language must be forced.