Search Results cnt_point_email

Overview

ASF_ORG_CREATE_V is a reporting view in the Oracle EBS Sales Online (ASF) module that consolidates organization-level party data with profile, contact, and ordering attributes. The view is documented under the title "View: ASF_ORG_CREATE_V" with the description "View for Organization Create," indicating it was designed to support organization creation and maintenance flows within the Sales Online application. It is important to note that the ETRM metadata explicitly records the implementation status as "Not implemented in this database." Consequently, the view may not exist in every EBS instance and referencing it in custom code should be preceded by a validation query against ALL_VIEWS or ALL_OBJECTS.

For the 12.1.1 and 12.2.2 releases, the view is relevant because it joins the Trading Community Architecture (TCA) model — HZ_PARTIES, HZ_ORGANIZATION_PROFILES, and HZ_CONTACT_POINTS — into a single, denormalized result set. This makes it useful for form-level population, concurrent program extracts, and integration interfaces that need one row per organization with its primary phone, email, and web contact points.

Underlying Base Objects

The view text is defined over three TCA base tables, aliased as ORG, PROFILE, and three separate aliases of CNT_POINT:

• HZ_PARTIES (ORG) — provides the party identifier, party type, name, number, tax reference, status, SIC code type, category code, URL, known-as name, year established, email address, fiscal year-end month, last ordered date, total ordered amount, and standard WHO columns.
• HZ_ORGANIZATION_PROFILES (PROFILE) — supplies DUNS number, current fiscal year potential revenue, line of business, preferred functional currency, total employees text, and internal flag. The join restricts to the current profile row via PROFILE.EFFECTIVE_END_DATE IS NULL.
• HZ_CONTACT_POINTS (CNT_POINT_PHONE, CNT_POINT_EMAIL, CNT_POINT_WEB) — three aliased instances, each filtered to OWNER_TABLE_NAME = 'HZ_PARTIES', PRIMARY_FLAG = 'Y', and the respective CONTACT_POINT_TYPE of PHONE, EMAIL, or WEB.

Because the same table is joined three times with hard-coded contact point type filters, the view returns at most one primary contact point per type per organization.

Key Columns

• PARTY_ID — primary identifier of the organization in HZ_PARTIES; appears twice in the select list.
• PARTY_NAME, PARTY_NUMBER, KNOWN_AS — organization identity attributes.
• STATUS — restricted to 'A' (active) or 'I' (inactive).
• LAST_ORDERED_DATE — the most recent date the organization placed an order; this is the column the user searched for and is directly exposed to the view.
• TOTAL_ORDERED_AMOUNT, CURR_FY_POTENTIAL_REVENUE — revenue and ordering aggregates for segmentation and tiering.
• PHONE_COUNTRY_CODE, PHONE_AREA_CODE, PHONE_NUMBER, PHONE_EXTENSION, PHONE_LINE_TYPE — primary phone details.
• DUNS_NUMBER, LINE_OF_BUSINESS, TOTAL_EMPLOYEES_TEXT, INTERNAL_FLAG — profile-level attributes used for classification.
• CONTACT_POINT_ID — returned separately for phone, email, and web.

Common Use Cases and Queries

Typical uses include organization data validation during customer onboarding, duplicate detection, and recency analysis for sales prioritization. A sample query to retrieve organizations with their last ordered date and primary phone is:

• SELECT party_id, party_name, party_number, status, last_ordered_date, phone_country_code, phone_area_code, phone_number FROM asf_org_create_v WHERE status = 'A' ORDER BY last_ordered_date DESC;
• SELECT party_id, party_name, duns_number, total_ordered_amount FROM asf_org_create_v WHERE last_ordered_date < SYSDATE - 365;

Before executing, verify the view exists in the target instance, since the ETRM registry marks it as not implemented in the documented database and no base objects are formally listed in the 12.2.2 metadata aside from the inline view text.