Results for “document_date”

50+ results




Overview
Explore in AI Chat

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

Overview

IBY_DOCS_PAYABLE_SEC_V is a security-enabled view in the Oracle Payments (IBY) module, owned by the APPS schema. It exposes payable document information from the IBY_DOCS_PAYABLE_ALL synonym while enforcing data access restrictions through Oracle's access control, security profile, and multi-org frameworks. Unlike its underlying base object, which stores payable documents for all operating units and users, this view filters rows so that a querying user sees only documents authorized by the user's security profile, payment function assignments, and MOAC (Multi-Org Access Control) responsibilities.

The view is central to payments reporting, reconciliation, and integration scenarios. It presents a flattened, security-compliant projection of payable documents that external systems, custom reports, and internal IBY concurrent processes can consume without reimplementing row-level security logic. Because it is a view rather than a table, no data is stored within it; every query re-evaluates the security predicates at runtime.

The search term "payment_due_date" reflects a common reporting requirement: users frequently need to identify when a payable document is due for payment. Although the excerpted column list does not include an explicit PAYMENT_DUE_DATE column, the view exposes related dates such as PAYMENT_DATE, DOCUMENT_DATE, and ANTICIPATED_VALUE_DATE, which are commonly used to derive or approximate due-date logic.

Underlying Base Objects

The view is defined over the synonym IBY_DOCS_PAYABLE_ALL, which points to the underlying IBY_DOCS_PAYABLE_ALL table storing the master payable document records. Security enforcement is achieved by joining this base data to several supporting objects documented in ETRM 12.2.2:

  • IBY_DOCS_PAYABLE_ALL (SYNONYM): The primary source of document rows and columns.
  • IBY_USER_PAY_FUNS_SEC_V (VIEW): Restricts rows to payment functions the user is authorized to access.
  • CE_SECURITY_PROFILES_V (VIEW): Applies cash management security profile restrictions.
  • FND_ACCESS_CONTROL_UTIL (PACKAGE): Central access control utility used to evaluate data security.
  • FND_GLOBAL (PACKAGE): Supplies session context such as user ID, responsibility, and org ID.
  • FND_PROFILE (PACKAGE): Retrieves profile option values that drive security behavior.
  • MO_GLOBAL (PACKAGE): Enforces Multi-Org Access Control operating unit filtering.
  • XTR_USER_ACCESS (PACKAGE): Applies treasury/user access rules.

Together these objects form a layered security model: base payable data is filtered by payment function, organization, security profile, and treasury access before being returned to the caller.

Key Columns

The view projects the full column set of IBY_DOCS_PAYABLE_ALL. Significant columns include:

Common Use Cases and Queries

Typical uses include building secure payments dashboards, reconciling payment batches, and exposing payable data to integrations that must respect user or org-level security. A common query retrieves documents with their payment and anticipated value dates:

SELECT document_payable_id, payment_function, document_date, payment_date, anticipated_value_date, document_amount FROM iby_docs_payable_sec_v WHERE org_id = :p_org_id;

For due-date analysis, users combine DOCUMENT_DATE with payment terms data, since no explicit due-date column is exposed by the view. Filtering by PAYMENT_FUNCTION and DOCUMENT_STATUS is typical when building reconciliation reports, while LEGAL_ENTITY_ID and ORG_ID filters leverage the embedded MOAC and security profile predicates. Because security is enforced at runtime, results vary by the querying responsibility, making the view safe for shared reporting and integration use.