Search Results b_status




Overview
Explore in AI Chat

Overview

The APPS.OKX_RESOURCES_V view is a Contracts Integration (OKX) dictionary object that consolidates resource information used throughout the Oracle E-Business Suite Contracts Integration flows. Its documented status is VALID, and it is registered under the OKX product/module, which governs the integration of contract authoring with the surrounding EBS entities such as suppliers, employees, and users. Functionally, the view presents a unified list of "resources" — party contacts, supplier contacts, and employees — together with identifiers, contact details, effective dates, and a computed availability status. This makes it a convenient single source for reporting and integration logic that would otherwise require unions across supplier and HR tables.

Because it is a view rather than a base table, OKX_RESOURCES_V carries no storage of its own; it is a query definition evaluated at runtime. This has implications for performance and for how it should be used in reporting: it inherits the access characteristics of its underlying synonyms and views.

Underlying Base Objects

ETRM records the following referenced base objects for OKX_RESOURCES_V: FND_GLOBAL (package), FND_USER (synonym), HZ_PARTIES (synonym), JTF_RS_RESOURCE_EXTNS (synonym), JTF_RS_SALESREPS_MO_V (synonym), PER_ALL_PEOPLE_F (synonym), PO_VENDOR_CONTACTS (view), and PO_VENDOR_SITES (view).

In the documented SQL, the supplier branch joins JTF_RS_RESOURCE_EXTNS (RSC) to PO_VENDOR_CONTACTS (C) and PO_VENDOR_SITES (S), restricted to RSC.CATEGORY = 'SUPPLIER_CONTACT'. The employee branch joins JTF_RS_RESOURCE_EXTNS to FND_USER (U) and PER_ALL_PEOPLE_F (EMP), restricted to RSC.CATEGORY = 'EMPLOYEE'. The two result sets are combined with UNION ALL, so JTF_RS_RESOURCE_EXTNS acts as the central resource register, while the surrounding views and tables supply descriptive and organizational attributes. HZ_PARTIES, JTF_RS_SALESREPS_MO_V, and FND_GLOBAL are documented dependencies used elsewhere in the OKX resource model; FND_GLOBAL supplies session context such as the current user and responsibility.

Key Columns

  • ID1 / ID2 — Composite key pair. ID1 carries RSC.RESOURCE_ID; ID2 is a literal '#'. Used in the data model as a distinguishing identifier.
  • RESOURCE_NUMBER — The resource number from JTF_RS_RESOURCE_EXTNS.
  • RESOURCE_TYPE — RSC.CATEGORY, indicating whether the row is a SUPPLIER_CONTACT or EMPLOYEE.
  • NAME / DESCRIPTION — Supplier contact last name and first name, or employee full name and user name, depending on the branch.
  • SOURCE_ID, ADDRESS_ID, CONTACT_ID, SUPPORT_SITE_ID, USER_ID — Foreign keys back to the originating entities.
  • ORG_ID — Operating unit from PO_VENDOR_SITES for supplier rows; hard-coded to -99 for employee rows.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — Effective date range controlling active status.
  • B_STATUS — Literal NULL. Exposed as a placeholder column; it carries no value in this definition, so any query filtering on it returns no meaningful results unless a wrapper supplies a value.
  • STATUS — Derived as 'A' (active) or 'I' (inactive) via nested DECODE/SIGN logic applied to the effective dates.
  • EMAIL_ADDRESS — Email from PO_VENDOR_SITES or PER_ALL_PEOPLE_F.

Common Use Cases and Queries

Typical usage includes resource lookups for contract integration, validating active supplier and employee resources, and reporting on resource contact details by operating unit.

  • List all active resources: 
    SELECT resource_number, name, resource_type, status
FROM   okx_resources_v
WHERE  status = 'A';
  • Filter supplier contacts for a specific operating unit: 
    SELECT name, email_address, org_id
FROM   okx_resources_v
WHERE  resource_type = 'SUPPLIER_CONTACT'
AND    org_id = :p_org_id;
  • Retrieve employees linked to a user account: 
    SELECT name, description, user_id
FROM   okx_resources_v
WHERE  resource_type = 'EMPLOYEE'
AND    user_id = :p_user_id;

Note that B_STATUS is defined as NULL; queries should not depend on it. Because the view performs UNION ALL across multiple sources, additional predicates on RESOURCE_TYPE, ORG_ID, or STATUS are recommended to limit the scanned rows.