Search Results allow_express_delivery_flag

Overview

RCV_RECEIVING_PARAMETERS_V is a VALID reporting and integration view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is registered under the PO — Purchasing product family and is documented in ETRM as "Retrofitted," meaning the object was carried forward across release boundaries to preserve backward compatibility for customizations, reports, and interfaces that reference it.

The view presents receiving control parameters at the inventory organization level. One row is returned per organization defined in RCV_PARAMETERS, enriched with descriptive routing names resolved from RCV_ROUTING_HEADERS. It is the conventional access point for answering the question "how is receiving configured for this organization?" without querying the base parameter table directly. Because it exposes the parameter flags alongside human-readable routing names, it is widely used in receiving reports, tolerance validation logic, and interfaces that must respect organization-specific receiving rules before submitting receipt transactions.

Underlying Base Objects

The view is defined over two documented base objects:

• RCV_PARAMETERS (exposed as a synonym) — the primary source, supplying all receiving control flags, tolerances, exception codes, account references, and the routing header identifiers.
• RCV_ROUTING_HEADERS (a view) — joined twice to resolve the receiving routing name and the RMA receiving routing name.

The join is an outer join on both routing columns: RP.RECEIVING_ROUTING_ID = RRH.ROUTING_HEADER_ID (+) and RP.RMA_RECEIPT_ROUTING_ID = RRH1.ROUTING_HEADER_ID (+). Organizations with no routing configured therefore still return a row, with ROUTING_NAME and RMA_ROUTING_NAME null. The view also carries standard WHO audit columns and concurrent program context columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) inherited from RCV_PARAMETERS.

Key Columns

• ORGANIZATION_ID — the inventory organization the parameter set applies to; the principal filter key.
• ALLOW_EXPRESS_DELIVERY_FLAG — controls whether express delivery is permitted for receipts in the organization. This is the column most frequently searched by implementers validating express receipt behavior.
• QTY_RCV_TOLERANCE / QTY_RCV_EXCEPTION_CODE — over-receipt quantity tolerance and the action taken when it is exceeded.
• DAYS_EARLY_RECEIPT_ALLOWED / DAYS_LATE_RECEIPT_ALLOWED / RECEIPT_DAYS_EXCEPTION_CODE — date-based receipt tolerances and their exception handling.
• ENFORCE_SHIP_TO_LOCATION_CODE — whether the ship-to location on the receipt must match the order.
• ALLOW_SUBSTITUTE_RECEIPTS_FLAG, ALLOW_UNORDERED_RECEIPTS_FLAG, BLIND_RECEIVING_FLAG — core receiving behavior switches.
• RECEIVING_ROUTING_ID / ROUTING_NAME and RMA_RECEIPT_ROUTING_ID / RMA_ROUTING_NAME — routing identifiers and their resolved names.
• RECEIVING_ACCOUNT_ID, RETROPRICE_ADJ_ACCOUNT_ID, CLEARING_ACCOUNT_ID — accounting references used during receipt and adjustment processing.
• USER_DEFINED_RECEIPT_NUM_CODE, MANUAL_RECEIPT_NUM_TYPE, NEXT_RECEIPT_NUM — receipt numbering configuration.
• ENFORCE_RMA_SERIAL_NUM, ENFORCE_RMA_LOT_NUM — RMA serial and lot enforcement.

Common Use Cases and Queries

Typical uses include confirming whether express delivery is enabled for an organization, driving tolerance validation in custom receiving forms, and feeding routing names into reports.

• Check express delivery configuration for a single organization:

  SELECT organization_id, allow_express_delivery_flag
  FROM   apps.rcv_receiving_parameters_v
  WHERE  organization_id = :p_org_id;

• Audit receiving tolerances and exception handling across organizations:

  SELECT organization_id, qty_rcv_tolerance, qty_rcv_exception_code,
         days_early_receipt_allowed, days_late_receipt_allowed
  FROM   apps.rcv_receiving_parameters_v
  ORDER  BY organization_id;

• List organizations with receiving routing names resolved:

  SELECT organization_id, receiving_routing_id, routing_name,
         rma_receipt_routing_id, rma_routing_name
  FROM   apps.rcv_receiving_parameters_v
  WHERE  routing_name IS NOT NULL;

Because the view is a simple non-aggregated projection with outer joins, it can be joined freely to organization and receipt tables in custom concurrent programs and BI Publisher data models without introducing row multiplication.