Search Results last_ordered_date




Overview
Explore in AI Chat

Overview

AST_ORG_PARTIES_V is a TeleSales (AST) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a filtered, denormalized projection of organization-type trading community parties, exposing the subset of HZ_PARTIES records where PARTY_TYPE equals 'ORGANIZATION'. Because the view joins no additional tables, it functions as a controlled read interface over the master party entity rather than as a transformation or aggregation layer.

The view's purpose within TeleSales is to supply organization party data for the sales and telesales user interfaces and for supporting reports. The inclusion of derived commercial statistics — TOTAL_NUM_OF_ORDERS, TOTAL_ORDERED_AMOUNT, and LAST_ORDERED_DATE — makes the view particularly relevant to telesales agents who require a quick indication of a customer organization's historical buying activity. These columns are maintained on HZ_PARTIES through order-processing and data-quality processes, and the view simply surfaces them alongside descriptive and classification attributes.

Because it is a simple single-table view, it is broadly usable across SQL*Plus, Oracle Reports, BI Publisher, OAF pages, and custom PL/SQL integrations. It supports both reporting queries and lookups, though it is not a substitute for the full HZ_PARTIES table when person parties or the complete column set are required.

Underlying Base Objects

The view is defined over a single synonym-referenced base object: HZ_PARTIES, the central table of the Oracle Trading Community Architecture (TCA) model. The documented ETRM metadata lists HZ_PARTIES (SYNONYM) as the only referenced base object, and the view text confirms a direct SELECT from HZ_PARTIES with the alias PARTY.

The defining predicate is WHERE PARTY_TYPE = 'ORGANIZATION'. This restricts the result set to organization records and excludes person parties, groups, and other party types stored in the same table. No joins to HZ_ORGANIZATION_PROFILES, HZ_CUST_ACCOUNTS, or order tables are present; all columns, including organization-related statistics such as TOTAL_NUM_OF_ORDERS and LAST_ORDERED_DATE, are read directly from HZ_PARTIES.

PARTY_NAME is projected through SUBSTR(PARTY.PARTY_NAME, 1, 360), which enforces a maximum display length on the returned party name. The view also returns PARTY.ROWID as ROW_ID and OBJECT_VERSION_NUMBER for optimistic locking support in OAF-based TeleSales pages.

Key Columns

Common Use Cases and Queries

The most frequent use is identifying organizations that have recently placed orders. Because LAST_ORDERED_DATE is stored on the party record, a single query returns both the customer identity and its last order activity.

Example: retrieve organizations ordered most recently.

SELECT party_id, party_number, party_name, last_ordered_date,
       total_num_of_orders, total_ordered_amount
FROM   apps.ast_org_parties_v
WHERE  last_ordered_date IS NOT NULL
ORDER BY last_ordered_date DESC;

Example: find dormant organizations that have not ordered within a defined window.

SELECT party_name, last_ordered_date, total_num_of_orders
FROM   apps.ast_org_parties_v
WHERE  last_ordered_date < SYSDATE - 365
   OR  last_ordered_date IS NULL;

Example: high-value organizations by order amount.

SELECT party_number, party_name, total_ordered_amount
FROM   apps.ast_org_parties_v
WHERE  total_ordered_amount > 100000
ORDER BY total_ordered_amount DESC;

Example: targeted lookup using the DFF and classification columns.

SELECT party_id, party_name, category_code, attribute1
FROM   apps.ast_org_parties_v
WHERE  category_code = 'CUSTOMER'
AND    sic_code LIKE '737%';

These patterns are typical for telesales call-list generation, customer profiling, and activity reporting. Because the view filters to organizations only, queries are naturally scoped and do not require an explicit PARTY_TYPE predicate, though adding one is harmless. Performance is generally good for lookups on PARTY_ID, PARTY_NUMBER, and PARTY_NAME; range or sort operations on LAST_ORDERED_DATE benefit from indexing on the corresponding HZ_PARTIES column.