Search Results oie_attendees




Overview
Explore in AI Chat

Overview

OIE_ATTENDEES is a reporting and integration view in the APPS schema within Oracle E-Business Suite, owned by the Payables (AP) product family. It exposes attendee-level data associated with Oracle Internet Expenses (OIE) expense report lines, presenting one row per attendee recorded against a given expense report line. In EBS 12.1.1 and 12.2.2, the view serves as the multi-org secured presentation layer over the underlying attendee storage, allowing forms, reports, and extensions to read attendee details without querying the base table directly. Because the view applies the standard Oracle Applications multi-org security predicate, rows returned are restricted to the organization currently set in the session's CLIENT_INFO context, which is populated by MO_GLOBAL or FND_GLOBAL during a user session. The view is documented as VALID and is referenced in the context of the "report_line_id" search term, indicating its role in joining attendee records back to the expense report line that owns them.

Underlying Base Objects

The view is defined over a single documented base object: the synonym OIE_ATTENDEES_ALL, which resolves to the attendee detail table stored in the APPS schema. The defining query selects a fixed list of columns from OIE_ATTENDEES_ALL and applies an ORG_ID filter. The filter compares the NVL-wrapped ORG_ID of each row against a value decoded from the first ten characters of USERENV('CLIENT_INFO'), treating a leading space as NULL and substituting -99 when no value is present. This construction is the classical Oracle EBS multi-org view pattern. OIE_ATTENDEES_ALL itself is the organization-unsecured ("_ALL") table, and OIE_ATTENDEES is its secured counterpart, ensuring that a session only sees attendee rows belonging to the organization to which it is currently restricted. Because the view is built on a synonym rather than a fully qualified table name, the physical table is resolved at runtime through standard synonym resolution in the APPS schema.

Key Columns

The view exposes the following columns, each carrying specific meaning in the Internet Expenses attendee model:

  • ATTENDEE_LINE_ID — Primary identifier for the attendee record; uniquely identifies a single attendee entry.
  • REPORT_LINE_ID — Foreign key linking the attendee to the specific expense report line to which the attendee belongs. This is the column referenced by the "report_line_id" search term and is the principal join key to expense report line data.
  • EMPLOYEE_FLAG — Indicator of whether the attendee is an internal employee.
  • EMPLOYEE_ID — Identifier of the employee attendee where applicable.
  • ATTENDEE_TYPE — Classification of the attendee (for example, employee or external party).
  • NAME, TITLE, EMPLOYER, EMPLOYER_ADDRESS, TAX_ID — Descriptive and, where relevant, tax-reporting attributes of the attendee.
  • ORG_ID — Operating unit identifier used by the multi-org security predicate.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Oracle Applications who-columns used for auditing and concurrency control.

Common Use Cases and Queries

The view is typically used to report attendee detail for expense reports, to reconcile attendee counts and names against report lines, and to build integrations that export attendee information for reimbursement or tax purposes. A common query joins attendees to their owning report line via REPORT_LINE_ID:

  • Retrieve all attendees for a specific report line: SELECT attendee_line_id, report_line_id, name, title, employer, attendee_type FROM oie_attendees WHERE report_line_id = :p_report_line_id;
  • Count attendees per report line: SELECT report_line_id, COUNT(*) FROM oie_attendees GROUP BY report_line_id;
  • Filter to internal employees only: SELECT name, employee_id FROM oie_attendees WHERE employee_flag = 'Y';

Because the view enforces org security, callers must ensure the correct operating unit context is initialized, otherwise the predicate resolves to -99 and no rows are returned. Direct queries from SQL*Plus without a valid CLIENT_INFO will therefore appear empty, which is expected behavior for this class of EBS view.