Results for “inquiry_method_code”

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

Overview

IGR_I_A_LINES_V is a reporting and integration view belonging to the IGS — Student System product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The view is documented as obsolete, and the ETRM metadata records that it was not implemented in the database against which the documentation was generated. It was designed to present a consolidated, integration-oriented projection of sales lead line data combined with student inquiry and application line information, exposing only the attributes required by OSS consumers.

The view's distinguishing feature is the CONCATENATED_PRODUCT_CAT_DESC column, which materializes the full hierarchical product category description for a lead line by travelling through the product hierarchy denormalization view. This makes the view suited to downstream reporting, interface extraction, and third-party consumption where a flattened category path is preferred over recursive lookups.

Underlying Base Objects

The view definition joins four objects. According to the ETRM excerpt, the design was to be based on the OMO public view AS_SALES_LEAD_LINES_V and the IGS_IN_INQUIRY_APPL_LINES junction table, though the implemented SQL text references IGR_I_A_LINES, AS_SALES_LEAD_LINES, IGR_I_APPL, and ENI_PROD_DEN_HRCHY_PARENTS_V. No referenced base objects are additionally documented in the ETRM metadata.

• IGR_I_A_LINES (aliased IPF) — supplies the primary integration line identifiers, person, enquiry/application number, preference, program, and request columns.
• AS_SALES_LEAD_LINES (aliased LINE) — supplies who-columns, category identifiers, and category set identifiers.
• IGR_I_APPL (aliased EAP) — supplies enquiry date and inquiry method code; joined by person and enquiry/application number.
• ENI_PROD_DEN_HRCHY_PARENTS_V (aliased DENORM) — supplies the denormalized category parentage and category description used to build the concatenated description.

Joins are equated on SALES_LEAD_LINE_ID between IPF and LINE, on person plus enquiry/application number between IPF and EAP, and on CATEGORY_ID between DENORM and LINE.

Key Columns

• ROW_ID — the row identifier sourced from IGR_I_A_LINES.
• SALES_LEAD_LINE_ID, PERSON_ID, ENQUIRY_APPL_NUMBER, PREFERENCE — core integration keys linking leads to persons and enquiries.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — concurrent program and program-context attributes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Who columns taken from the sales lead line.
• ENQUIRY_DT, INQUIRY_METHOD_CODE — the date and channel by which the enquiry was received.
• PRODUCT_CATEGORY_ID, PRODUCT_CATEGORY_SET_ID — the category and its set, aliased from the lead line category columns.
• CONCATENATED_PRODUCT_CAT_DESC — the flattened category parentage. The DECODE/GREATEST/SUBSTR logic: if the concatenated parentage is 2000 characters or fewer it is returned intact; if longer, the trailing 2000 characters are returned.
• PRODUCT_CATEGORY_DESC — the description of the category from the denormalization view.

Common Use Cases and Queries

The view supports extraction of lead lines with a fully-qualified category path for interface files and downstream reporting, avoiding recursive category traversals.

SELECT sales_lead_line_id,
       person_id,
       enquiry_appl_number,
       concatenated_product_cat_desc,
       product_category_desc
FROM   igr_i_a_lines_v
WHERE  enquiry_dt >= :p_start_date;

A typical lookup resolves the category path for a single lead line:

SELECT sales_lead_line_id,
       product_category_id,
       concatenated_product_cat_desc
FROM   igr_i_a_lines_v
WHERE  sales_lead_line_id = :p_lead_line_id;

Because the object is documented as obsolete and not implemented, these patterns describe the intended usage. Implementations should verify the authoritative replacement object before relying on the view.