Search Results ou_org_id




Overview

APPS.FV_SYSTEM_PARAMETERS_V is a reporting and integration view in Oracle E-Business Suite Releases 12.1.1 and 12.2.2 that consolidates operating unit, legal entity, and location attributes into a single queryable structure. It is defined in the APPS schema and is most commonly encountered when users search for the underlying operating unit entity fv_operating_units, because the view surfaces operating unit identifiers such as ORG_ID and SET_OF_BOOKS_ID alongside the descriptive party and address data that those identifiers reference.

The view serves as a denormalized access point for party and site information associated with an operating unit. Rather than requiring a caller to join the operating unit table to first-party (legal entity) information and to HR locations independently, the view performs those joins internally and exposes a flat row per operating unit. This makes it suitable for reports, concurrent programs, and interface extracts that need legal entity name, address, and contact telephone details without re-implementing the join logic.

Underlying Base Objects

The documented base objects referenced by the view are:

The join conditions are explicit in the view text: lep.legal_entity_id = ou.legal_entity_id links the operating unit to its legal entity, and lep.location_id = l.location_id links that legal entity record to an HR location. Consequently, the view returns one row per operating unit that has a matching legal entity and location; operating units lacking a resolvable legal entity or location will not appear.

Key Columns

  • SET_OF_BOOKS_ID — the ledger associated with the operating unit, sourced from FV_OPERATING_UNITS.
  • NAME — the legal entity name from XLE_FIRSTPARTY_INFORMATION_V.
  • OU_ORG_ID — the operating unit organization identifier; this is the value most commonly used for operating unit security and partitioning.
  • LEGAL_ENTITY_ID — the identifier of the legal entity to which the operating unit is assigned.
  • ALC_CODE — the accounting location code associated with the operating unit.
  • RECEIVABLES_TRX_ID and PAYABLES_IA_PAYGROUP — default Receivables transaction and Payables intercompany paygroup references.
  • FED_EMPLOYER_ID_NUMBER and DIT_CONFIRM_CASH_ACCOUNT — tax identification and cash confirmation account attributes carried at operating unit level.
  • ADDRESS_LINE_1 through ADDRESS_LINE_3, TOWN_OR_CITY, REGION_1 through REGION_3, and POSTAL_CODE — the legal entity's location address details from HR_LOCATIONS.
  • TELEPHONE_NUMBER_1 through TELEPHONE_NUMBER_3 — contact telephone numbers for the associated location.

Common Use Cases and Queries

Typical uses include identifying the legal entity and address that back a given operating unit, driving intercompany or tax reports that require the federal employer identification number, and populating interface files that must emit trading partner name and address data. A representative query that resolves a specific operating unit follows:

  • SELECT ou_org_id, name, legal_entity_id, set_of_books_id
  • FROM  apps.fv_system_parameters_v
  • WHERE ou_org_id = :p_org_id;

A broader listing of operating units with their legal entity and city can be produced with:

  • SELECT ou_org_id, name, town_or_city, fed_employer_id_number
  • FROM  apps.fv_system_parameters_v
  • ORDER BY name;

Because the view is defined in the APPS schema and derives from operating unit data, queries should respect operating unit security where applicable. Callers who require operating units that have no resolvable legal entity or location should query FV_OPERATING_UNITS directly rather than relying on this view, since the inner joins will exclude such rows.