Search Results jl_ar_ar_doc_letter




Overview
Explore in AI Chat

Overview

JL_AR_AR_DOC_LETTER_PKG is a PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema that manages the JL_AR_AR_DOC_LETTER table, which stores tax document letter assignments for Argentina localization (JL) transactions. The package serves as the maintenance layer for document letters, the codes that Argentine tax authorities require on fiscal documents to indicate the type of transaction (for example, invoice class or operation category). Each record associates a document letter with a combination of tax category and organization and concept tax attributes, with an effective date range controlling when the assignment is valid. In Oracle EBS 12.1.1 and 12.2.2 this object belongs to the Latin American localization (JL) foundation and supports the region-specific tax reporting required for Argentine operations. The package body carries the standard EBS header comment ($Header: jlarrdob.pls 120.3 2003/07/11), indicating it is a shipped, pre-11i vintage object that has remained stable across releases; it is therefore classified as a generic "OTHER" API rather than a formal public interface.

Key Procedures and Functions

The documented package exposes seven procedures:

  • INSERT_ROW — Inserts a new document letter assignment into JL_AR_AR_DOC_LETTER. It accepts the tax category, organization and concept tax attribute name/value pairs, the document letter, the active date range, WHO audit columns (creation and last-update audit information), the ORG_ID for multi-org security, the fifteen descriptive flexfield attribute columns, and a calling sequence parameter. The body first checks for an existing row with the same tax category and attribute combination before inserting, and returns the new ROWID to the caller.
  • LOCK_ROW — Acquires a row-level lock on an existing document letter record, serializing concurrent modifications before an update or delete.
  • UPDATE_ROW — Modifies an existing document letter record, typically after LOCK_ROW has secured the row.
  • DELETE_ROW — Removes a document letter assignment from the table.
  • CHECK_UNIQUE — Validates that no duplicate document letter assignment exists for the same tax category and attribute combination, enforcing the logical uniqueness of the record.
  • CHECK_OVERLAPPED_DATES — Verifies that the start and end dates of a new or modified assignment do not overlap the effective period of another record sharing the same key, preventing ambiguous date ranges.
  • CHECK_GAPS — Detects unassigned date intervals between consecutive effective records, ensuring continuous coverage of the document letter assignment across time.

Tables Accessed

The package reads and writes a single table, JL_AR_AR_DOC_LETTER, accessed through its APPS synonym. The table is the repository of document letter definitions keyed by tax_category_id, org_tax_attribute_name, org_tax_attribute_value, con_tax_attribute_name, and con_tax_attribute_value. The INSERT_ROW cursor queries these five columns to detect existing records, and all maintenance procedures operate against this table. The overlapping-date and gap checks logically depend on the start_date_active and end_date_active columns of the same table, while ORG_ID supports the EBS multi-organization access control model.

Usage Notes

This package is an internal localization utility rather than a published API; the ETRM metadata records no other package referencing it. It is most commonly invoked indirectly from Oracle Argentina localization forms or from concurrent programs that generate or validate fiscal documents, and from custom extensions that maintain document letter setups programmatically. Because the package is not a formal public interface, custom code should invoke it only after consulting Oracle Support, and callers must supply the calling sequence parameter to preserve the diagnostic call stack. In 12.1.1 and 12.2.2 the object behaves identically; no post-2003 changes are indicated in the source header, so the primary compatibility concerns are the ORG_ID multi-org context and the standard WHO audit columns, both of which must be populated consistently by any direct caller.