Search Results ship_sets_include_lines_flag




Overview
Explore in AI Chat

Overview

RA_SITE_USES_MORG is a Receivables (AR) view that exposes the business purpose assigned to a customer address — that is, the site use records that determine whether a given address functions as a Bill-To, Ship-To, Statement-To, Dunning-To, or other usage type for a customer account. In Oracle EBS 12.1.1 and 12.2.2, this view is one of several "ORG" (multi-organization) variants of the site-use data model, alongside RA_SITE_USES and RA_SITE_USES_ALL. Its name and structure indicate that it is intended to surface site-use rows in a multi-org context, associating each site use with an ORG_ID so that customer address purposes are evaluated at the operating unit level.

The view is documented in ETRM as "Not implemented in this database" for the source documentation environment, and it exposes no documented referenced base objects. Practically, this means RA_SITE_USES_MORG is treated as a reporting and integration surface rather than a primary transactional object. It is typically consumed by reports, concurrent programs, and interface logic that need to resolve the effective purpose of a customer site without directly joining the underlying HR/AR site-use tables.

Underlying Base Objects

The ETRM metadata documents no referenced base objects for RA_SITE_USES_MORG, and the view is noted as not implemented in the documentation database. Where the view is present in a deployed environment, its column list — including SITE_USE_ID, CUST_ACCT_SITE_ID, PRIMARY_FLAG, STATUS, ORG_ID, and WH_UPDATE_DATE — is consistent with the standard AR site-use schema, so the view is best understood as a projection over the base site-use table (the RA_SITE_USES family) filtered or organized by operating unit.

The comment ADDRESS_ID attached to CUST_ACCT_SITE_ID reflects the historical evolution of the data model from the older ADDRESS_ID-based customer model to the current CUST_ACCT_SITE_ID-based model. Similarly, the NULL placeholders for TAX_EXEMPT, TAX_EXEMPT_NUM, and TAX_EXEMPT_REASON_CODE document columns that are "NO LONGER USED" in the current release. In 12.2.2 these legacy tax-exempt attributes are superseded by TAX_CLASSIFICATION, TAX_HEADER_LEVEL_FLAG, and TAX_ROUNDING_RULE, which appear in the view with an inline note that TAX_CLASSIFICATION was "ADDED - BUG 1335212."

Key Columns

  • SITE_USE_ID — Primary identifier for the site-use record.
  • CUST_ACCT_SITE_ID — The customer account site (formerly ADDRESS_ID) to which the use applies.
  • SITE_USE_CODE — The business purpose: BILL_TO, SHIP_TO, STATEMENT, DUNNING, etc.
  • PRIMARY_FLAG — Indicates the primary site use for that purpose.
  • STATUS — Active or inactive status of the site use.
  • ORG_ID — Owning operating unit, central to the multi-org nature of this view.
  • LOCATION and CONTACT_ID — Address reference and associated contact.
  • BILL_TO_SITE_USE_ID — Links ship-to and other uses back to the designated bill-to.
  • PAYMENT_TERM_ID, PRICE_LIST_ID, FREIGHT_TERM, FOB_POINT, WAREHOUSE_ID, TERRITORY_ID — Commercial defaults carried at the site-use level.
  • TAX_CLASSIFICATION, TAX_HEADER_LEVEL_FLAG, TAX_ROUNDING_RULE — Tax determination attributes in the current model.
  • DEMAND_CLASS_CODE, SHIP_PARTIAL, SHIP_VIA — Order-management attributes.
  • SORT_PRIORITY — Ordering for site-use resolution.
  • ATTRIBUTE1–25 and GLOBAL_ATTRIBUTE1–20 — Descriptive flexfield and global descriptive flexfield segments.

Common Use Cases and Queries

Typical usages include: identifying the bill-to or ship-to purpose for a customer account site; resolving tax classification for 12.2.2 tax engine integration; populating order defaults (freight terms, price list, warehouse) during order entry; and feeding customer master data into downstream systems. A representative query:

  • SELECT su.site_use_id, su.site_use_code, su.primary_flag, su.status, su.cust_acct_site_id FROM ra_site_uses_morg su WHERE su.org_id = :p_org_id AND su.site_use_code = 'BILL_TO' AND su.status = 'A';
  • SELECT su.cust_acct_site_id, su.tax_classification, su.tax_rounding_rule FROM ra_site_uses_morg su WHERE su.org_id = :p_org_id AND NVL(su.primary_flag,'N') = 'Y';
  • SELECT su.site_use_id, su.bill_to_site_use_id, su.payment_term_id, su.price_list_id FROM ra_site_uses_morg su WHERE su.cust_acct_site_id = :p_site_id;

Because the view is not implemented in the documentation database, availability should be verified in each target instance before it is referenced in custom reports or interfaces. The search term "arrivalsets_include_lines_flag" does not correspond to any column in this view's text; it belongs to a separate object and should be investigated independently of RA_SITE_USES_MORG.