Results for “as_contact_education”

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

Overview

The AS_CONTACT_EDUCATION table is a component of the AS (Sales Foundation) product family within Oracle E-Business Suite, implemented in the OSM schema. It stores educational background information for contacts maintained in the Sales Foundation data model, allowing organizations to record academic history such as schools attended, fields of study, and degrees earned for each contact record. In Oracle EBS releases 12.1.1 and 12.2.2, the table is documented as VALID and forms part of the reference and descriptive data used by sales, marketing, and relationship-management functions that depend on rich contact profiles.

From a data-modeling perspective, the heuristic Data Vault classification mined from the foreign key structure is standalone. This classification suggests that, at the physical level, the table does not exhibit the enforced parent-child relationships typical of hub or link entities; it may therefore be treated as a descriptive satellite-style construct attached to a contact, holding attributes (school, major, degree, type) that describe the contact's education rather than defining new business entities or relationships. Modelers should treat this as a suggestion and validate against actual constraints in their environment.

Key Information Stored

The table is documented with 11 physical columns in the ETRM 12.2.2 schema. The most significant columns are:

• EDUCATION_ID — the surrogate primary key, uniquely identifying each education record. It is the single column of the AS_CONTACT_EDUCATION_PK primary key constraint.
• CONTACT_ID — the identifier of the contact to whom the education record belongs. This is the principal business-key candidate and the primary join column to contact-related tables.
• SCHOOL — the name of the educational institution attended.
• MAJOR — the field or subject of study pursued by the contact.
• DEGREE — the qualification or degree awarded (for example, bachelor's, master's, or doctorate).
• TYPE — a classification or category value associated with the education record (for example, institution type or education level).
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns recording when, by whom, and through which session the row was last modified.
• CREATION_DATE, CREATED_BY — standard audit columns recording row creation.

No unique indexes beyond the primary key are documented. CONTACT_ID should nonetheless be treated as the primary business-key candidate for querying and joining, while EDUCATION_ID remains the technical identifier.

Common Use Cases and Queries

Typical scenarios include contact-profile enrichment for sales prospecting, segmenting contacts by degree or major for targeted campaigns, and validating educational credentials during partner or customer onboarding. A representative query to retrieve the full education history for a specific contact is:

• SELECT education_id, contact_id, school, major, degree, type FROM as_contact_education WHERE contact_id = :contact_id;
• SELECT school, major, degree, COUNT(*) FROM as_contact_education GROUP BY school, major, degree;
• SELECT c.contact_id, e.school, e.degree FROM as_contact_education e JOIN contact c ON c.contact_id = e.contact_id WHERE e.major = :major;

Reporting use cases include education-distribution dashboards, alumni or institution-based segmentation, and audit reports on who last updated a given education record using the standard audit columns.

Related Objects

Because the table is classified as standalone, documented foreign key relationships are limited; however, the following objects are functionally associated and are the most significant for joins and dependency analysis:

• CONTACT (or AS_CONTACT) — the parent contact entity, joined on CONTACT_ID.
• AS_CONTACT_EDUCATION_PK — the primary key constraint on EDUCATION_ID governing row uniqueness.
• Contact-related Sales Foundation tables — such as contact address and contact communication objects, which share the CONTACT_ID key for building complete contact profiles.
• Sales Foundation setup tables — lookups that may supply valid values for TYPE, DEGREE, and MAJOR where flexfield or lookup validation is configured.
• Standard EBS audit columns consumers — concurrent programs and audit reports relying on CREATED_BY, LAST_UPDATED_BY, and associated date columns.