Results for “job_title_code”

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

Overview

AMS_LT_ORG_CONTACT_V is a data source view owned by the APPS schema in Oracle E-Business Suite, defined under the AMS (Marketing) product family. Its documented purpose is to retrieve information about business-to-business (B2B) contacts for use within Oracle Marketing and its downstream reporting and integration surfaces. The view serves as a lightweight, filtered abstraction over organization contact data, presenting a stable column projection that Oracle Marketing's data source framework can consume without directly referencing the underlying Oracle Customers (HZ) tables. Because the view is registered as a VALID object at both 12.1.1 and 12.2.2, it retains the same structural contract across both release lines.

Practically, the view is intended for read-only consumption: report definitions, list-generation data sources, and integration extracts query it rather than the base table. Its most important behavioural characteristic is a row filter on contact status, meaning the view returns only active contacts.

Underlying Base Objects

The view is defined over a single documented base object, the synonym HZ_ORG_CONTACTS. In the view text, this object is aliased as C. HZ_ORG_CONTACTS is the Oracle Trading Community Architecture table that stores contact records associated with an organization party in the B2B relationship model; each row links a contact party to an organization party via a party relationship.

The view applies a single, explicit predicate: WHERE C.STATUS = 'A'. This restricts the result set to active organization contacts only, excluding inactive or otherwise non-'A' status rows. No joins, outer joins, or aggregations are present in the documented view text, so the cardinality of the view is at most equivalent to the filtered active subset of HZ_ORG_CONTACTS. The view performs no column transformation beyond aliasing ORG_CONTACT_ID to the exposed name CONTACT_ID; every other exposed column passes through unchanged.

Key Columns

• CONTACT_ID — Aliased from HZ_ORG_CONTACTS.ORG_CONTACT_ID; the primary identifier of the organization contact record.
• CONTACT_NUMBER — The user-visible contact number assigned in TCA.
• PARTY_SITE_ID — Identifier of the party site associated with the contact.
• DECISION_MAKER_FLAG — Indicates whether the contact is a decision maker, a key attribute for marketing targeting.
• REFERENCE_USE_FLAG — Indicates whether the contact may be used as a reference.
• RANK — Relative rank of the contact within its organization context.
• TITLE, JOB_TITLE, JOB_TITLE_CODE — Job title information in descriptive and coded forms.
• DEPARTMENT, DEPARTMENT_CODE — Department description and its coded value.
• MANAGED_BY — Identifies the party or person that manages the contact; the column that matches the search term "managed_by".
• MAILING_ADDRESS_ID, MAIL_STOP — Mailing address reference and internal mail stop designation.
• NATIVE_LANGUAGE, OTHER_LANGUAGE_1, OTHER_LANGUAGE_2 — Language attributes for the contact.
• PARTY_RELATIONSHIP_ID — Identifier of the underlying party relationship linking the contact to the organization.

Common Use Cases and Queries

The view is typically used to source B2B contact lists for marketing campaigns, to validate contact attributes before list generation, and to extract active contacts into external systems. A basic selection of decision makers with their management linkage is shown below.

SELECT contact_id, contact_number, title, job_title, department, managed_by, decision_maker_flag FROM apps.ams_lt_org_contact_v WHERE decision_maker_flag = 'Y';

A targeted lookup on the managed_by attribute, matching the search that surfaced this object, would be written as:

SELECT contact_id, contact_number, title, job_title, managed_by FROM apps.ams_lt_org_contact_v WHERE managed_by IS NOT NULL;

Because the view already restricts to STATUS = 'A', no additional status predicate is required. Note that callers cannot rely on the view for inactive contacts; those queries must be issued against HZ_ORG_CONTACTS directly. As with all APPS-owned views, grants and synonym exposure should be confirmed in the target environment before integrating, and the view should be treated as a read-only reporting interface rather than a DML target.