Search Results expense_check_address_flag

Overview

MTL_EMPLOYEES_VIEW is an APPS-owned database view in Oracle E-Business Suite, registered under the Inventory (INV) product module. In both release 12.1.1 and 12.2.2, the object carries a VALID status in the ETRM repository and is documented as a "View of employees." Functionally, it publishes a streamlined, employee-scoped projection of person records joined to the organization units that anchor those persons to a business group, making it convenient for inventory-side reporting, integrations, and lookups that require a flat employee list rather than the full, date-tracked PER_PEOPLE_X structure.

Because the view restricts its result set to rows where EMPLOYEE_NUMBER is not null, it excludes applicants, contingent workers without an employee number, and other non-employee person types. This makes it a natural source for reports and interfaces that must reference bona fide employees — for example, inventory approvers, requesters named on transactions, or contacts used in expense-related routing. The view is date-filtered so that only the currently effective person version is returned, which simplifies downstream SQL by removing the need for callers to apply their own effective-date predicates.

Underlying Base Objects

The documented view text is defined over two base objects: PER_PEOPLE_X, a date-tracked view over the person tables, and HR_ORGANIZATION_UNITS, which supplies the organization and business group context. The join is driven by BUSINESS_GROUP_ID: the view text concatenates a zero literal to P.BUSINESS_GROUP_ID to defeat index usage where required and equates it to ORG.BUSINESS_GROUP_ID.

ETRM metadata additionally lists HR_GENERAL (PACKAGE), HR_PERSON_NAME (PACKAGE), and HR_SECURITY (PACKAGE) as referenced base objects. These are the standard HRMS building blocks: HR_GENERAL and HR_PERSON_NAME supply the name-derivation and business-group logic surfaced through PER_PEOPLE_X, while HR_SECURITY enforces the security profile applied when the view is queried in an environment with enabled HR security. The effective-dating predicate TRUNC(SYSDATE) BETWEEN P.EFFECTIVE_START_DATE AND P.EFFECTIVE_END_DATE is the mechanism that returns only the current person record.

Key Columns

• ORGANIZATION_ID — identifier of the HR organization unit associated with the employee's business group.
• BUSINESS_GROUP_ID — the business group that owns the person record; drives the join to HR_ORGANIZATION_UNITS.
• EMPLOYEE_ID / PERSON_ID — the person identifier, the primary key used when joining the view to other person-referencing objects.
• EMPLOYEE_NUMBER — the assigned employee number; non-null is enforced by the view's WHERE clause.
• FULL_NAME, FIRST_NAME, MIDDLE_NAME, LAST_NAME, PREFIX — name attributes exposed for display and matching.
• EXPENSE_CHECK_ADDRESS_FLAG / EXPENSE_CHECK_SEND_TO_ADDRESS — the expense check routing indicator. This column is directly responsive to the search term "expense_check_address_flag." In the 12.2.2 documented column list the attribute appears as EXPENSE_CHECK_ADDRESS_FLAG; the view text exposes the underlying P.EXPENSE_CHECK_SEND_TO_ADDRESS attribute, so implementations should verify the physical column label in the target release before relying on either name.
• EMAIL_ADDRESS — the employee's electronic mail address.
• ATTRIBUTE1 through ATTRIBUTE20, ATTRIBUTE_CATEGORY — the standard descriptive flexfield segment columns, enabling DFF-based reporting directly from the view.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical usage includes employee lookup lists for inventory forms and reports, reconciliation of person data against transaction history, and extraction of flexfield or email attributes for downstream interfaces. A representative query retrieving employees and their expense check routing is:

• SELECT employee_id, employee_number, full_name, email_address, expense_check_address_flag FROM mtl_employees_view WHERE organization_id = :org_id;
• SELECT employee_number, full_name FROM mtl_employees_view WHERE business_group_id = :bg_id ORDER BY full_name;
• SELECT m.employee_number, m.attribute1, m.attribute_category FROM mtl_employees_view m WHERE m.email_address IS NOT NULL;

Because HR_SECURITY is referenced, query results may be filtered by the HR security profile of the connecting user; integrations should account for this and, where a full population is required, use a privileged or secured-profile-free connection.