Search Results result_date

Overview

GMD_QC_E_SAMPLE_RESULTS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the GMD product family (Process Manufacturing Product Development). The view consolidates quality control sample results into a single denormalized record set, joining sample header data, test definitions, tester identity, and organization context. Because the object is a view and not a table, it introduces no storage of its own; it resolves at runtime against the underlying application tables.

The view exposes a flattened representation of the relationship between a quality sample, the tests applied to it, and the resulting measured values. This design supports ad hoc reporting, Oracle Discoverer or BI Publisher queries, and downstream integration requirements where consumers need QC results without navigating the normalized transactional model. A user searching on "result_date" will find that the view projects RSLT.RESULT_DATE directly from GMD_RESULTS, making the column available for filtering, sorting, and date-range reporting.

Underlying Base Objects

The documented view text references five base objects, all resolved in APPS through synonyms:

• GMD_RESULTS (aliased RSLT) — the driving results table supplying result identifiers, test values, tester, result date, and replicate count.
• GMD_SAMPLES (aliased SMPLS) — the sample header supplying sample number, description, and organization.
• GMD_QC_TESTS_B (aliased GQTS) — the QC test definition supplying test type, test unit, and the decode logic that determines whether the numeric or character result column is returned.
• FND_USER (aliased FUSER) — the application user joined via USER_ID to TESTER_ID as an outer join, resolving the tester name.
• MTL_PARAMETERS (aliased ORGS) — the organization definition supplying the organization code.

Joins are established on SAMPLE_ID, TEST_ID, and ORGANIZATION_ID. The outer join on FND_USER ensures results remain visible even when no tester is recorded.

Key Columns

• SAMPLE_ID / SAMPLE_NO / SAMPLE_DESC — identity and descriptive attributes of the quality sample.
• RESULT_ID / TEST_ID — keys linking to the result record and its governing test definition.
• TEST_RESULT — a decoded value column. The DECODE on TEST_TYPE returns RESULT_VALUE_CHAR for type 'T', and RESULT_VALUE_NUM for types 'E', 'N', and 'L'; any other type falls through to the character value.
• TEST_UNIT — the unit of measure associated with the test.
• RESULT_DATE — the date the result was recorded; this is the primary date dimension in the view.
• USER_NAME — the tester's application user name.
• ORGANIZATION_CODE — the inventory organization code from MTL_PARAMETERS.
• TEST_REPLICATE_CNT — the number of replicates associated with the result.
• UPDATE_INSTANCE_ID — the update instance identifier supporting audit and change tracking.

Common Use Cases and Queries

Typical usage centers on extracting QC outcomes over time, by organization, or by sample. The following query returns all test results recorded within a date range:

• SELECT sample_no, sample_desc, test_result, test_unit, result_date, user_name, organization_code FROM apps.gmd_qc_e_sample_results_v WHERE result_date BETWEEN :start_date AND :end_date;
• SELECT test_id, COUNT(*) FROM apps.gmd_qc_e_sample_results_v WHERE organization_code = :org GROUP BY test_id;
• SELECT sample_no, result_date, user_name FROM apps.gmd_qc_e_sample_results_v WHERE sample_id = :sample_id ORDER BY result_date;

Because the view performs a DECODE across heterogeneous test types, consumers should treat TEST_RESULT as a display value and apply their own conversion when numerical aggregation is required. Organizations should expect this view to be read-only and rely on it as a stable interface for reporting rather than as a target for DML.