Search Results rcv_fail_if_line_fails




Overview
Explore in AI Chat

Overview

RCV_UPDATE_RTI_LC is a package body in the APPS schema that supports the landed cost integration flow within Oracle E-Business Suite Receiving. Its principal responsibility is to transfer landed cost allocation results back onto the Receiving Transactions Interface (RTI) so that receipt transactions previously staged with the status LC_INTERFACED can be completed with their landed cost attributes. The package operates on the RCV_TRANSACTIONS_INTERFACE table, updating only those interface transaction rows that have not yet been assigned a landed cost shipment line or unit landed cost.

The naming convention reflects its role: "RCV" denotes the Receiving module, "UPDATE_RTI" denotes the update of the Receiving Transactions Interface, and "LC" denotes landed cost. The package is classified as an OTHER API within ETRM 12.2.2 and is referenced by one other package, indicating it is a supporting component rather than a standalone user-facing API. It is present across the 12.1.1 and 12.2.x code lines, with the header comment in the source referencing version 120.1.12010000.4.

Key Procedures and Functions

The package exposes a single documented procedure, UPDATE_RTI. This procedure accepts an inbound collection of landed cost interface records and returns an outbound collection of landed cost interface results. Its logic is structured as follows:

  • It declares the procedure with an autonomous transaction pragma, allowing the update work to commit independently of the calling transaction.
  • It reads the profile option RCV_FAIL_IF_LINE_FAILS into a local variable, defaulting to 'N' when the profile is not set. This profile governs whether processing should abort when an individual interface line fails.
  • It obtains a new group identifier from the RCV_INTERFACE_GROUPS_S sequence.
  • It iterates over the inbound collection and, for each record where unit landed cost, landed cost shipment line identifier, and interface identifier are all populated, it performs an update against RCV_TRANSACTIONS_INTERFACE, restricting the update to rows with processing status LC_INTERFACED whose landed cost columns are still null.
  • It accumulates the affected row count and, for each successful update, extends the outbound collection with the corresponding result record.
  • Diagnostic messages are written through the ASN debug utility, recording entry into the procedure, the number of records supplied, the retrieved group identifier, and the row counts resulting from each update.

The procedure therefore acts as a controlled write-back mechanism that guarantees landed cost values are applied only once, since the update predicate requires both landed cost columns to be null.

Tables Accessed

  • RCV_TRANSACTIONS_INTERFACE — the primary target of the update. The procedure sets LCM_SHIPMENT_LINE_ID and UNIT_LANDED_COST for interface transaction rows matching the supplied interface identifier and still in LC_INTERFACED status.
  • RCV_INTERFACE_GROUPS_S — used solely to generate the next group identifier applied to the batch of updated interface rows.
  • RCV_HEADERS_INTERFACE — referenced in the package, consistent with header-level context required to associate grouped interface transactions correctly.
  • DUAL — used for the sequence selection.
  • PLITBLM — the underlying table type supporting the PL/SQL collection structures used for the inbound and outbound parameters.

Usage Notes

RCV_UPDATE_RTI_LC is not intended for direct invocation by end users. It is called by other Receiving landed cost packages during the landed cost allocation and receipt interface cycle, typically as part of a concurrent program or a spawned PL/SQL process that reconciles landed cost results with staged receipt transactions. Because the update is wrapped in an autonomous transaction, callers should be aware that landed cost updates commit independently; failures in the calling process do not automatically roll back the interface updates. The RCV_FAIL_IF_LINE_FAILS profile option allows implementers to control failure behavior for individual lines, and debug output should be enabled through the ASN debug facility when diagnosing landed cost interface issues.