Results for “ship_sets_include_lines_flag”

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

Overview

AST_CUST_SITE_USES_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite, defined within the AST (TeleSales) product family. It exposes the site-use records that describe how a customer account site is utilized — for example, whether it functions as a bill-to, ship-to, or statement-to location. In EBS 12.1.1 and 12.2.2, this view is a coding convenience layer over the High Availability (HZ) customer model, presenting the validated, active column set that TeleSales and downstream reporting logic expect.

The view is of particular interest to users searching for the column GL_ID_TAX, which is among the fifty-plus columns selected. Because it is a simple projection with no joins or filters beyond a horizontal column list, it behaves like a synonym-with-projection: all rows in the underlying base table are returned, and the view's value lies in name standardization and controlled column visibility. The view is documented as VALID in the ETRM metadata, meaning its definition compiles cleanly and the base object it references is present.

Underlying Base Objects

The view is defined over a single base object, documented as HZ_CUST_SITE_USES_ALL, referenced through a synonym in the APPS schema. The view text performs a straight SELECT ... FROM HZ_CUST_SITE_USES_ALL with an explicit column list and includes ROWID as the first projected expression. No WHERE clause, GROUP BY, join, or DISTINCT is applied.

HZ_CUST_SITE_USES_ALL is the multi-org (ALL) table in the Trading Community Architecture (TCA) that stores site-use assignments and their operational attributes. Because the base table is org-striped, the view exposes ORG_ID directly, allowing callers to filter by operating unit. The inclusion of ROWID permits the view to be used in updateable contexts and in interfaces that require a stable physical row identifier, although DML through the view is not the intended usage in the TeleSales flow.

Key Columns

The view projects a broad set of columns that can be grouped functionally:

• Identity and hierarchy: SITE_USE_ID (primary identifier), CUST_ACCT_SITE_ID, BILL_TO_SITE_USE_ID, CONTACT_ID, ORG_ID.
• Classification: SITE_USE_CODE (BILL_TO, SHIP_TO, etc.), PRIMARY_FLAG, STATUS, TERRITORY_ID, DEMAND_CLASS_CODE.
• Ordering and logistics: SHIP_PARTIAL, SHIP_VIA, FOB_POINT, ORDER_TYPE_ID, PRICE_LIST_ID, WAREHOUSE_ID, SORT_PRIORITY, SHIP_SETS_INCLUDE_LINES_FLAG, ARRIVALSETS_INCLUDE_LINES_FLAG, SCHED_DATE_PUSH_FLAG, INVOICE_QUANTITY_RULE, PRICING_EVENT.
• Tax handling: TAX_CODE, TAX_REFERENCE, TAX_HEADER_LEVEL_FLAG, TAX_ROUNDING_RULE, and GL_ID_TAX, which identifies the General Ledger account derivation source used for tax accounting on the site.
• Accounting flexfield references: GL_ID_REC, GL_ID_REV, GL_ID_TAX, GL_ID_FREIGHT, GL_ID_CLEARING, GL_ID_UNBILLED, GL_ID_UNEARNED, GL_ID_UNPAID_REC, GL_ID_REMITTANCE, GL_ID_FACTOR.
• Charge accrual and finance: LAST_ACCRUE_CHARGE_DATE, SECOND_LAST_ACCRUE_CHARGE_DATE, LAST_UNACCRUE_CHARGE_DATE, SECOND_LAST_UNACCRUE_CHRG_DATE, FINCHRG_RECEIVABLES_TRX_ID, DATES_NEGATIVE_TOLERANCE, DATES_POSITIVE_TOLERANCE, DATE_TYPE_PREFERENCE, OVER/UNDER_SHIPMENT_TOLERANCE, OVER/UNDER_RETURN_TOLERANCE.
• Descriptive flexfield and audit: ATTRIBUTE_CATEGORY, ATTRIBUTE1 through ATTRIBUTE25, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical scenarios include validating tax accounting setup for a customer site, extracting bill-to and ship-to defaults for order entry, and auditing GL account assignments ahead of a period close.

• Locate the tax GL account derivation for a site:
  SELECT site_use_id, site_use_code, gl_id_tax FROM apps.ast_cust_site_uses_v WHERE site_use_id = :p_site_use_id;
• List all bill-to sites with their tax references for an operating unit:
  SELECT cust_acct_site_id, tax_code, tax_reference, gl_id_tax FROM apps.ast_cust_site_uses_v WHERE site_use_code = 'BILL_TO' AND org_id = :p_org_id AND status = 'A';
• Find sites missing a tax accounting reference:
  SELECT site_use_id, cust_acct_site_id FROM apps.ast_cust_site_uses_v WHERE gl_id_tax IS NULL AND site_use_code = 'BILL_TO';
• Join to order defaults for TeleSales quoting by resolving site-use to price list and order type.

Because the view performs no filtering, callers should always constrain by ORG_ID and STATUS where operating-unit or active-record scope matters. For high-volume reconciliation, querying HZ_CUST_SITE_USES_ALL directly with an index on SITE_USE_ID or CUST_ACCT_SITE_ID will generally outperform the view, while AST_CUST_SITE_USES_V remains preferable for readability and column-name stability across EBS 12.1.1 and 12.2.2.