Search Results call_app_pay_service_req_code

Overview

The IBY_PAY_REQUEST_SEC_V view is a security-constrained reporting object within the Oracle Payments (IBY) module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It is owned by the APPS schema and holds a VALID status. The view exposes payment service request records from IBY_PAY_SERVICE_REQUESTS, but restricts the returned rows according to the organization-level and function-level access privileges of the querying user. In effect, it presents the payment request universe that a given user or responsibility is authorized to see, rather than the entire transactional population. This makes the view the canonical access point for reporting, personalization, and integration logic that must respect Oracle Payments security without reimplementing the underlying access control model. Because it is a view rather than a table, it introduces no storage of its own; queries execute against the base tables and the security subqueries dynamically, ensuring that authorization is evaluated at runtime.

Underlying Base Objects

Per the documented metadata, IBY_PAY_REQUEST_SEC_V is defined over several objects. The primary source is IBY_PAY_SERVICE_REQUESTS (referenced through a synonym). Two additional base objects participate in the WHERE clause: IBY_PROCESS_ORGS, which maps requests to organizations and organization types, and IBY_PROCESS_FUNCTIONS, which maps requests to payment functions. Security enforcement is supplied by the views CE_SECURITY_PROFILES_V (organization access) and IBY_USER_PAY_FUNS_SEC_V (payment function access). Supporting packages referenced in the definition include FND_ACCESS_CONTROL_UTIL, FND_GLOBAL, FND_PROFILE, MO_GLOBAL, and XTR_USER_ACCESS. The joins require that each payment request be associated with at least one organization permitted by the user's CE security profile and at least one payment function permitted by the user's function-level security, as implemented through IBY_USER_PAY_FUNS_SEC_V.

Key Columns

The view projects the full column set of the underlying payment service request record. Notable columns include:

• PAYMENT_SERVICE_REQUEST_ID — Primary identifier of the payment service request.
• CALLING_APP_ID — Identifier of the application that originated the request; the term most relevant to the user's search, distinguishing requests by source application.
• CALL_APP_PAY_SERVICE_REQ_CODE — The application-specific request code supplied by the calling application.
• PAYMENT_SERVICE_REQUEST_STATUS and PROCESS_TYPE — Lifecycle state and processing classification of the request.
• INTERNAL_BANK_ACCOUNT_ID, PAYMENT_PROFILE_ID, MAXIMUM_PAYMENT_AMOUNT, MINIMUM_PAYMENT_AMOUNT — Disbursement and constraint attributes.
• ORG_TYPE — The organizational context of the request.
• Audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, OBJECT_VERSION_NUMBER, and LAST_UPDATE_LOGIN.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — Descriptive flexfield segments.

Common Use Cases and Queries

The view is typically used to build secure inquiry screens, extract payment request data for reconciliation, and support integration routines that must honor Payments security. A representative query filtering by calling application and status follows:

SELECT payment_service_request_id,
  calling_app_id,
  call_app_pay_service_req_code,
  payment_service_request_status,
  creation_date
FROM  iby_pay_request_sec_v
WHERE  calling_app_id = :p_app_id
AND    payment_service_request_status IN ('SUBMITTED','PROCESSING');

Because the view already applies organization and function security, it avoids the need to manually join IBY_PROCESS_ORGS, IBY_PROCESS_FUNCTIONS, and the security profile views in custom code. When broader visibility is needed for administrative diagnostics, query the base table IBY_PAY_SERVICE_REQUESTS directly, recognizing that such queries bypass application security and should be restricted to privileged users.