Results for “received_attvalue”

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

Overview

The view RLX_INTERFACE_LINES_V is a release management interface construct within the Oracle E-Business Suite RLM (Release Management) module. It projects demand-side line information from supply/demand planning records into a flattened, interface-ready shape suitable for downstream consumption by release management and order fulfillment processes. In the 12.1.1 and 12.2.2 code lines, this view serves as a translation layer that takes planning entries and emits attribute-tagged columns (for example STARTDATE_ATTVALUE, QUANTITY_ATTVALUE, DELIVACT_ATTVALUE) that map directly onto interface attribute slots consumed by the release/order interface logic.

Because the view normalizes quantity, item, unit of measure, and delivery-related values into fixed literal tokens such as 'REQUIRED', 'EACH', 'ITEM', 'DELIVACT', 'PO', 'RECEIVED', 'SHIP', and 'DELIVERED', it is designed to satisfy a rigid interface contract rather than to serve ad-hoc reporting. The attribute value columns act as constant discriminators, while the corresponding data columns supply the dynamic values.

Underlying Base Objects

Per the documented ETRM metadata, the view text is defined over three referenced base objects:

• MSC_SUP_DEM_ENTRIES (aliased MSD) — the supply/demand entries that supply item, organization, plan, quantity, sequence, and date information.
• IPD_ITEMS_V (aliased IIV) — the item view joined to resolve PARTY_ITEM_NUMBER and the owning party.
• MSC_PLANS (aliased MP) — the plan header, joined to constrain the plan and its type.

The join predicates are:

• MSD.INVENTORY_ITEM_ID = IIV.ITEM_ID
• MSD.PUBLISHER_ORG_ID = IIV.PARTY_ID
• MP.PLAN_ID = MSD.PLAN_ID
• MP.PLAN_TYPE = 4 — restricting output to the applicable plan type (a supply/demand or production plan category).

Notably, the ETRM metadata states that this object is not implemented in the referenced database and that no base objects are separately documented beyond the view text. The relationship is therefore a straightforward three-table equijoin producing one interface row per qualifying supply/demand entry.

Key Columns

• HEADER_ID — sourced from MP.PLAN_ID; identifies the plan header the line belongs to.
• START_DATE — the line start date from MSD.START_DATE.
• STARTDATE_ATTVALUE — literal 'REQUIRED', tagging the start date as a required attribute.
• ITEM_NAME — the party item number from IIV.PARTY_ITEM_NUMBER.
• UOM_CODE — literal 'EACH'.
• PRIMARY_QUANTITY / QUANTITY_ATTVALUE — the line quantity and the literal 'ITEM' tag.
• PROD_SEQ_NUMBER — production sequence from MSD.PRODUCTION_SEQUENCE.
• MODEL_SERIAL_NUMBER — from MSD.END_ASSEMBLY_ITEM_NAME.
• LINE_FEED — from MSD.LINE_CODE.
• DELIVACT_ATTVALUE — literal 'DELIVACT' (delivery activity tag).
• PO_ATTVALUE, RECEIVED_ATTVALUE, SHIP_ATTVALUE, DELIVERED_ATTVALUE — constant discriminators 'PO', 'RECEIVED', 'SHIP', 'DELIVERED'.
• RECEIVEDQTY_ATTVALUE, SHIPPED_ATTVALUE — literals 'RECEIVED' and 'SHIPPED'.

Common Use Cases and Queries

Typical scenarios include driving release/order interfaces, validating plan-type-4 demand lines, and debugging interface attribute mapping. A representative query follows:

• List all interface lines for a given plan header:
  SELECT header_id, item_name, primary_quantity, prod_seq_number
FROM rlx_interface_lines_v
WHERE header_id = :plan_id
ORDER BY prod_seq_number;
• Confirm item/party resolution against the item view:
  SELECT item_name, uom_code, start_date, model_serial_number
FROM rlx_interface_lines_v
WHERE start_date BETWEEN :from_date AND :to_date;
• Extract quantities with their attribute tags for interface staging:
  SELECT primary_quantity, quantity_atvalue, line_feed
FROM rlx_interface_lines_v;

Because the object is documented as not implemented in the reference database, availability should be confirmed locally before relying on it in production interfaces.