Search Results factore_recourse

Overview

APPS.AR_BILLS_MAINTAIN_LIB_PVT is a private PL/SQL library package in Oracle Receivables that supports the maintenance and lifecycle management of billing transactions, adjustments, receipts, and receipt applications. The package is classified as PVT (private) within the ETRM repository, indicating that it is an internal implementation library rather than a published public API. Its procedures are invoked by other Receivables packages, forms, and concurrent processes to perform the underlying database operations that drive transaction generation, adjustment creation and reversal, receipt application and unapplication, and document sequence assignment.

The header comment ($Header: ARBRMALS.pls 120.4 2005/10/30) reflects the file's origin in the AutoInvoice / Bills Receivable maintenance area, and the package remains present and documented in both Oracle EBS 12.1.1 and 12.2.2. Because it is private, it should not be called directly from customer extensions; Oracle does not guarantee backward compatibility for private packages.

Key Procedures and Functions

The package exposes 23 documented procedures. The procedure most relevant to the search term get_doc_seq is GET_DOC_SEQ, which assigns the document sequence value to a transaction record based on the application, ledger (set of books), and transaction method code supplied by the caller.

• GET_DOC_SEQ — Retrieves and assigns the next document sequence number for a customer transaction, honoring the transaction method and set of books.
• GET_REMITTANCE_BATCH — Returns the batch record associated with a given customer transaction identifier.
• UPDATE_RESERVED_COLUMNS — Maintains reserved (internal-use) columns on the payment schedule for a specified schedule and reservation type/value.
• DEFAULT_ACTION_DATES — Defaults the transaction date and GL date values used during transaction maintenance.
• COMPLETE_ACC_REQUIRED — Completes the accounting-required step associated with a customer transaction.
• COMPLETE_OR_ACCEPT — Completes or accepts a transaction history record during the transaction workflow.
• CREATE_ADJUSTMENT — Creates an adjustment against a transaction and payment schedule, returning the new adjustment identifier.
• FIND_LAST_ADJUSTMENT — Locates the most recent adjustment for a given customer transaction.
• APPROVE_ADJUSTMENT, MODIFY_ADJUSTMENT, REVERSE_ADJUSTMENT — Manage the approval, modification, and reversal stages of an adjustment's lifecycle.
• REVERSE_ASSIGNMENTS_ADJUSTMENT — Reverses adjustments linked to assignment transactions.
• FIND_LAST_RECEIPT, FIND_LAST_STD — Locate the most recent receipt or standard (cash) transaction record.
• REVERSE_RECEIPT, APPLY_RECEIPT, UNAPPLY_RECEIPT — Reverse receipts and manage receipt application and unapplication logic.
• APPLY_STD, UNAPPLY_STD — Apply and unapply standard (cash) transactions.
• FACTORE_RECOURSE — Handles recourse factoring logic for factored transactions.

Tables Accessed

The package reads and writes the core Receivables transaction and receipt tables through APPS synonyms, including:

• RA_CUSTOMER_TRX, RA_CUSTOMER_TRX_LINES, RA_CUST_TRX_TYPES — Transaction headers, lines, and transaction type definitions used in document sequencing and adjustment creation.
• AR_ADJUSTMENTS — Creation, approval, modification, and reversal of adjustments.
• AR_PAYMENT_SCHEDULES — Payment schedule updates tied to adjustments and reserved column maintenance.
• AR_TRANSACTION_HISTORY — Transaction workflow and action date tracking.
• AR_CASH_RECEIPTS, AR_RECEIVABLE_APPLICATIONS — Receipt handling, application, and unapplication processing.
• AR_BATCHES, RA_BATCH_SOURCES — Remittance batch retrieval and batch source validation.
• AR_RECEIVABLES_TRX, AR_RECEIPT_METHODS, AR_RECEIPT_METHOD_ACCOUNTS — Adjustment activity types and receipt method configuration.
• DUAL — Used for single-row selection and default computations.

Usage Notes

Because AR_BILLS_MAINTAIN_LIB_PVT is a private package, it is not intended to be called directly from customer-developed code. It is invoked internally by Oracle Receivables forms and by other Receivables packages — the ETRM metadata records that it is referenced by one other package. Typical invocation contexts include the Transactions and Receipts forms, adjustment approval workflows, and concurrent programs that process receipts and adjustments. When a user searches for get_doc_seq, the relevant entry point is the GET_DOC_SEQ procedure, which populates the transaction document sequence during transaction creation and completion. Developers should reference public Receivables APIs (such as AR_RECEIPT_API_PUB or AR_ADJUSTMENT_API_PUB) rather than this private library, and should treat its behavior as subject to change across patch levels.