Search Results ins_ra_batches

Overview

The APPS.JL_BR_AR_GENERATE_DEBIT_MEMO package is a Brazilian localization component within Oracle E-Business Suite Receivables. It provides the server-side APIs used to generate interest-based debit memos against an existing, overdue customer transaction. The package automates the creation of the debit memo document, its lines, sales credit assignments, accounting distributions, and payment schedules within a single, coordinated flow, and it integrates the resulting accounting with Subledger Accounting (SLA). Its header originally identified the companion package name JL_BR_INT_DEB_MEMO_SV, reflecting its role as the server-side line-level API layer for Brazilian interest debit memo processing.

Functionally, the package exists to charge interest on delinquent receivables in the Brazilian localizations context. Given an original invoice, an interest amount, and related transaction attributes, it derives the correct debit memo type, batch source, customer, GL account, and interest revenue account, then constructs the entire debit memo structure that Receivables requires. The package is classified under OTHER in the ETRM registry and is owned by APPS. It is referenced by one other package and targets Release 12.1.1 and 12.2.2 environments.

Key Procedures and Functions

• JL_BR_INTEREST_DEBIT_MEMO — The primary public entry point. It accepts the original customer transaction identifier, invoice amount, user identifier, transaction type, batch source, receipt method, payment schedule, and interest date, and returns status, error, and token values, together with an interest revenue accounting flexfield identifier. It orchestrates the full debit memo creation process.
• GET_ACCOUNT — A function that resolves an accounting flexfield account based on an account type, transaction type, and salesperson, plus an interest revenue CCID and structure number. It returns the derived account identifier and error information.
• INS_RA_BATCHES — Inserts a Receivables batch into RA_BATCHES using the batch source, invoice amount, currency, and user, returning the generated batch identifier.
• GENERATE_INTEREST_DM_NUMBER — A function that derives the debit memo document number associated with the original transaction.
• INS_RA_CUSTOMER_TRX, INS_RA_CUSTOMER_TRX_LINES, INS_RA_CUST_TRX_LINE_SALESREPS, INS_RA_CUST_TRX_LINE_GL_DIST, and INS_AR_PAYMENT_SCHEDULES — Internal insert procedures that populate the transaction header, its lines, sales credit lines, accounting distributions, and payment schedules, respectively.
• SLA_CREATE_EVENT — Added on 20-JUN-2005 as part of Subledger Accounting KI bug fix 4301543. This procedure creates the SLA event that drives the creation of accounting entries for the generated debit memo.
• VALIDATE_AND_DEFAULT_GL_DATE — Validates and defaults the general ledger date used for the debit memo accounting, ensuring the date falls within an open or valid accounting period.

Tables Accessed

• RA_BATCHES — Written by INS_RA_BATCHES to create the batch container for the debit memo.
• RA_CUSTOMER_TRX, RA_CUSTOMER_TRX_ALL, and RA_CUSTOMER_TRX_LINES / RA_CUSTOMER_TRX_LINES_S — Written to build the debit memo header and its line records.
• RA_CUST_TRX_LINE_SALESREPS — Populated to assign sales credit to the debit memo lines.
• RA_CUST_TRX_LINE_GL_DIST — Written to record the accounting distributions for the debit memo lines.
• AR_PAYMENT_SCHEDULES and AR_PAYMENT_SCHEDULES_S — Inserted by INS_AR_PAYMENT_SCHEDULES to establish the payment schedule and open receivable balance for the debit memo.
• RA_ACCOUNT_DEFAULTS and RA_ACCOUNT_DEFAULT_SEGMENTS — Read by GET_ACCOUNT to derive default accounting flexfield values.
• FND_ID_FLEX_STRUCTURES — Read to resolve the accounting flexfield structure used for account derivation.
• GL_PERIOD_STATUSES — Read by VALIDATE_AND_DEFAULT_GL_DATE to confirm period validity.
• AR_SYSTEM_PARAMETERS, HZ_CUST_SITE_USES — Read to obtain system-level and customer site defaults.

Usage Notes

The package is typically invoked through Brazilian localization Receivables functionality, either from user-facing forms or from concurrent programs that process overdue interest charges in batch. Application logic calls the top-level JL_BR_INTEREST_DEBIT_MEMO procedure, passing the original transaction, the calculated interest amount, and supporting attributes; the subordinate procedures execute in sequence to build the complete debit memo. The SLA_CREATE_EVENT procedure is the critical integration point for Release 12 Subledger Accounting, ensuring that the generated debit memo produces correct accounting entries. Custom extensions that create interest debit memos should call the documented public procedure rather than the internal insert routines directly, and should pass NOCOPY-based OUT parameters for status, error code, error message, and token to capture execution results reliably.