Search Results get_num_bar_code

Overview

The APPS.JL_AR_DOC_NUMBERING_PKG package is a localization (JL/regional) utility within Oracle EBS that governs document numbering, validation, and classification logic for Oracle Receivables (AR) transactions. It is most closely associated with Latin American localization requirements — notably Brazilian and Argentine fiscal documentation rules — where statutory document letters, four-digit branches, and point-of-sale identifiers must be validated and imprinted on customer transactions. The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than the definer, which is typical for localization packages that must respect the invoking application's security context.

The header comment $Header: jlarrdns.pls 120.6 2005/11/18 02:11:20 appradha ship $ indicates the source version is 120.6, a mature release that remained largely intact through EBS 12.1.1 and 12.2.2. The package is documented against the ETRM metadata as classification OTHER, with 19 documented procedures and functions and four dependent packages referencing it.

Key Procedures and Functions

The documented API surface divides into validation, lookup, and transaction-number generation routines.

• validate_trx_type — Confirms that a transaction type, invoice class, and document letter combination is valid for a given batch source, flagging invalid interface lines.
• validate_four_digit — Validates the four-digit branch/establishment code associated with an inventory item, memo line, or sales order organization.
• validate_document_letter — Validates the fiscal document letter using a NOCOPY IN OUT parameter, allowing the procedure to correct or return the letter while preserving performance.
• validate_transaction_date and validate_interface_lines — Perform date and full line-level validations against the AR interface tables before import.
• get_imported_batch_source and get_batch_source_type — Resolve batch source identity and category from RA_BATCH_SOURCES.
• get_printing_count — Returns a printing counter for a customer transaction, supporting reprint controls.
• get_adv_days — Retrieves the advance-days value used in document numbering and billing-date calculations.
• get_branch_number_method, get_branch_number, get_hr_branch_number — Determine branch numbering methodology and return branch identifiers.
• get_flex_delimiter and get_flex_value — Extract delimiter and value segments from key flexfield strings.
• get_num_bar_code and get_point_of_sale_code — Return barcode and point-of-sale values required on Brazilian fiscal documents.
• get_doc_letter and get_last_trx_date — Retrieve the document letter and the last transaction date for numbering sequences.
• trx_num_gen — Generates the formatted transaction number, consolidating the preceding lookups and validations into the final document identifier.

Tables Accessed

The package reads configuration and transaction data through APPS synonyms.

• RA_BATCH_SOURCES / RA_BATCH_SOURCES_ALL — Source of batch source name, type, and country-specific flags.
• RA_CUSTOMER_TRX — Primary transaction records used for printing counts and last transaction dates.
• AR_MEMO_LINES — Memo line data supporting document letter and four-digit validations.
• AR_SYSTEM_PARAMETERS — System-level AR settings (set of books and defaulting behavior).
• FND_CONCURRENT_REQUESTS — Links interface lines to their concurrent program execution.
• HZ_CUST_ACCT_SITES / HZ_CUST_ACCT_SITES_ALL / HZ_CUST_SITE_USES — Customer site and site-use data resolved during validation.
• MTL_SYSTEM_ITEMS — Inventory item attributes tied to branch and document letter rules.
• JL_AR_AR_DOC_LETTER, JL_AR_AP_TRX_DGI_CODES, JG_ZZ_AR_SRC_TRX_TY, JL_ZZ_AR_TX_ATT_CLS, JL_ZZ_AR_TX_CUS_CLS_ALL — Latin American localization tables holding document-letter codes, DGI codes, and tax classification attributes.

Usage Notes

This package is invoked principally from the AutoInvoice import path and from localization forms. validate_interface_lines and the validate_* functions are called during the RAXMTR AutoInvoice workflow to reject or correct interface lines before they reach RA_CUSTOMER_TRX. trx_num_gen is called when a transaction number must be synthesized according to local fiscal rules. Custom code and extensions should call get_adv_days and its sibling getters to retrieve configuration values rather than querying the underlying tables directly, ensuring consistency with document-numbering logic. Because the package is AUTHID CURRENT_USER, proper synonym grants to the JL and RA tables are required for any custom caller to execute successfully.