Search Results delete_freight

Overview

ARP_PROCESS_FREIGHT is an Oracle Apps (APPS) schema PL/SQL package within the Oracle E-Business Suite Receivables (AR) module. Its business purpose is to manage freight charge lines on customer transactions — inserting, updating, validating, and deleting freight-related distribution lines that are attached to AR invoices, credit memos, debit memos, and similar transaction records. Freight handling in Receivables is distinct from ordinary revenue lines because freight amounts require their own accounting distributions and validation rules, and ARP_PROCESS_FREIGHT encapsulates the logic that enforces those rules.

The package is classified as "OTHER" in the ETRM API taxonomy, meaning it is an internal processing package rather than a formally published public API. It is marked VALID in the 12.1.1/12.2.2 data dictionary. It both references and is referenced by multiple AR packages, indicating it sits at the center of a small freight-processing subsystem that includes ARP_PROCESS_FREIGHT_UTIL, ARP_PROCESS_FREIGHT_COVER, ARP_PROCESS_CREDIT, and ARP_CACHE_UTIL.

Key Procedures and Functions

The package exposes nine documented procedures. Exact parameter signatures are not published in the ETRM metadata and are not reproduced here.

• INIT — Performs package-level initialization, typically establishing cached values, global state, or session context required by subsequent freight operations.
• CHECK_FRT_LINE_COUNT — Verifies the number of freight lines associated with a given transaction, used to determine whether freight processing is applicable or to enforce line-count constraints.
• VALIDATE_INSERT_FREIGHT — Applies business validation rules before a new freight line is inserted, checking transaction type, currency, and structural consistency.
• VALIDATE_UPDATE_FREIGHT — Applies validation rules when an existing freight line is modified, ensuring the change preserves accounting and transaction integrity.
• VALIDATE_DELETE_FREIGHT — Confirms that a freight line may be safely removed, typically guarding against deletion where downstream distributions would be orphaned.
• SET_FLAGS — Sets internal control flags used to signal state or mode to the insert, update, and delete routines.
• INSERT_FREIGHT — Creates the freight line and its associated accounting distribution records.
• UPDATE_FREIGHT — Modifies an existing freight line and adjusts its corresponding distributions.
• DELETE_FREIGHT — Removes a freight line and cleans up its related distribution records.

Tables Accessed

The package reads and writes the following documented tables via APPS synonyms:

• RA_CUSTOMER_TRX — The parent transaction header; read to confirm transaction context and possibly updated for freight-related totals.
• RA_CUSTOMER_TRX_LINES — Stores the freight line records themselves; the primary target of INSERT_FREIGHT, UPDATE_FREIGHT, and DELETE_FREIGHT.
• RA_CUST_TRX_LINE_GL_DIST — Holds the accounting distributions; freight lines require their own distribution rows, which this package maintains.
• RA_CUST_TRX_TYPES — Supplies transaction type attributes used during validation.
• AR_SYSTEM_PARAMETERS — Provides system-level Receivables configuration that governs freight behavior.
• FND_CURRENCIES — Used to validate currency codes and currency-related attributes on freight lines.

Usage Notes

ARP_PROCESS_FREIGHT is not intended for direct invocation by end users. It is called programmatically by other AR packages — notably by ARP_PROCESS_CREDIT, ARP_PROCESS_FREIGHT_UTIL, ARP_PROCESS_FREIGHT_COVER, and ARP_CACHE_UTIL — which supply the freight line context and drive the validation and DML routines. This dependency pattern indicates the package is invoked as part of broader transaction processing flows, such as credit memo application or freight re-derivation on transaction changes, rather than from a standalone form or concurrent program.

Custom code should not call this package directly. Oracle's supported extension points for Receivables freight behavior are the documented AR APIs; ARP_PROCESS_FREIGHT may change between releases without notice. When troubleshooting freight line issues, developers typically trace the call chain from the invoking package and inspect RA_CUSTOMER_TRX_LINES and RA_CUST_TRX_LINE_GL_DIST to confirm whether the package's validation or DML path completed successfully.