Search Results pos_exasn_lines

Overview

APPS.POS_EXCELASN_PVT is a private PL/SQL package body in the Oracle E-Business Suite Advanced Supply Chain and Procurement modules that supports the spreadsheet-based Advance Shipping Notice (ASN) upload and processing flow. The package transports receipt data originating from Excel-based ASN submissions into the Oracle Receiving open interface. It converts the flat, denormalized rows supplied by the spreadsheet template into the structured header and line records expected by the Receiving Interface tables (RCV_HEADERS_INTERFACE and RCV_TRANSACTIONS_INTERFACE), performs validation, and manages error recording through POS_EXCELASN_ERROR_TABLE. In Oracle EBS 12.1.1 and 12.2.2 the package is classified as PVT (private), meaning it is intended for internal use by the corresponding public wrapper APIS rather than being called directly by customer extensions. Its header revision string (POSVEXAB.pls 120.14.12020000.3) confirms it is a mature, actively maintained object that remained largely stable across the 12.1 and 12.2 release families.

The name is historically associated with the "pos_exasn_lines" search term, which reflects the line-level interface processing that this package coordinates. Its primary business purpose is to reduce manual keying of supplier shipping notices and to accelerate receipt creation for high-volume procurement operations, particularly for direct and outside-processing receipts involving lots, serial numbers, and license plate numbers (LPNs).

Key Procedures and Functions

The documented interface exposes seventeen procedures and functions, organized around the end-to-end Excel ASN lifecycle:

• PROCESSEXCELASN – The main entry point that orchestrates the full upload, from header creation through validation and interface insertion.
• GETCONVERTEDQUANTITY – Converts quantities between the spreadsheet unit of measure and the inventory unit of measure.
• CHECKLLSCONTROL – Verifies whether License Plate Number (LPN) and LLS (Low Level Shipping) controls are enabled before processing container data.
• CREATENEWHEADER / CREATENEWLINE – Build the RCV_HEADERS_INTERFACE and RCV_TRANSACTIONS_INTERFACE records, respectively.
• FIXHEADERSANDLINES / UPDATELINESANDLLS – Correct or refresh header, line, and LPN data after initial insert or during revalidation.
• INSERTERROR – Writes diagnostic messages into the POS_EXCELASN_ERROR_TABLE for user review.
• INSERTINTOLLS – Inserts License Plate Number and container hierarchy records.
• CREATERTI4LOT, CREATERTI4LPN, CREATERTI4SER – Create RCV_TRANSACTIONS_INTERFACE rows specifically for lot-controlled, LPN-controlled, and serial-controlled items.
• VALIDATEHEADERS, VALIDATELINES, VALIDATELLS – Apply business validation rules to headers, lines, and LPN/LLS data prior to processing.
• GET_STATUS – Returns a status code (N, P, E, EP, S, U) derived from the processing_status_code of the interface rows for a given GROUP_ID, letting the caller poll the submission outcome.
• GETVENDORPAYSITEID – Resolves the vendor pay site identifier used during header validation.

Tables Accessed

The package reads and writes through APPS synonyms. Main transactional targets are the receiving interface tables RCV_HEADERS_INTERFACE and RCV_TRANSACTIONS_INTERFACE, along with PO_INTERFACE_ERRORS. Supporting master data referenced includes AP_SUPPLIERS, HZ_PARTY_SITES, HZ_PARTY_SITE_USES, HZ_LOCATIONS, and HR_LOCATIONS_ALL_TL for supplier and site resolution; IBY_EXTERNAL_PAYEES_ALL, IBY_EXT_BANK_ACCOUNTS, IBY_EXT_PARTY_PMT_MTHDS, and IBY_PMT_INSTR_USES_ALL for payment instrument and payee validation; MTL_SYSTEM_ITEMS and MTL_UNITS_OF_MEASURE_TL for item and UOM conversion; and ORG_FREIGHT for freight context. Access is further constrained by responsibility-level security through AK_RESP_SECURITY_ATTRIBUTES, AK_RESP_SECURITY_ATTR_VALUES, and AK_WEB_USER_SEC_ATTR_VALUES, which enforce which supplier sites and contacts a user is permitted to transact against.

Usage Notes

POS_EXCELASN_PVT is not exposed directly to end users. It is invoked indirectly by the receiving Excel ASN concurrent program and by the public package wrapper that Oracle exposes for the same flow, and it is referenced by one other package in the ETRM catalog. Because it is a PVT package, customers should not call its procedures from custom code; any extension should target the documented public API or the Receiving Open Interface instead. When troubleshooting an Excel ASN submission, the most useful diagnostic path is to query RCV_HEADERS_INTERFACE and RCV_TRANSACTIONS_INTERFACE by GROUP_ID and call GET_STATUS, then inspect POS_EXCELASN_ERROR_TABLE for the specific validation failures recorded by INSERTERROR.