Results for “create_dm”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AP_AUTO_DM_CREATION_PKG is an Oracle Payables PL/SQL package body owned by the APPS schema that supports the automatic creation of debit memos within Oracle E-Business Suite Release 12.1.1 and 12.2.2. A debit memo in Payables is a supplier-facing document that reduces the amount owed on a payable, commonly generated to recover overpayments, correct invoicing errors, or apply supplier chargebacks. The package encapsulates the logic required to detect or assemble the underlying invoice, batch, supplier, and distribution context, and to build the debit memo header and lines programmatically rather than through manual entry in the Payables forms.

The object carries an API classification of OTHER in the ETRM registry, indicating that it is a supporting internal utility rather than a formally published open interface or public API. Its status is VALID, and the package body references a broad set of Payables, Purchasing, Receiving, and currency objects, reflecting the multi-source nature of the data it must reconcile when constructing a debit memo.

Key Procedures and Functions

The documented interface exposes a single program unit:

• CREATE_DM — The core entry point of the package. It performs the automated debit memo creation flow, orchestrating the validation and assembly steps needed to produce a debit memo from the relevant source records. ETRM documents only the name and purpose; the formal parameter list is not published in the metadata and should be determined at runtime from the data dictionary if required.

Supporting logic is inherited from dependent packages rather than re-declared here, notably AP_INVOICES_PKG, AP_CREATE_PAY_SCHEDS_PKG, AP_ETAX_PKG, AP_MATCHING_PKG, AP_RECT_MATCH_PKG, AP_UTILITIES_PKG, and APP_EXCEPTION. These dependencies indicate that CREATE_DM leverages the standard invoice creation, payment schedule, tax, matching, and exception handling routines already maintained within Payables.

Tables Accessed

The package reads and writes against a defined set of Payables and related tables, accessed through APPS synonyms:

• AP_BATCHES, AP_BATCHES_ALL, AP_BATCHES_S, AP_BATCHES_S1 — Batch header structures, including the AP_BATCHES_S1 sequence synonym, which is directly relevant to users searching for that object. These support grouping of invoices and debit memos into Payables batches.
• AP_INVOICES, AP_INVOICES_ALL, AP_INVOICES_S, AP_INVOICES_S1 — Invoice header records, including sequences, used to insert and identify the debit memo.
• AP_INVOICE_DISTRIBUTIONS and AP_INVOICE_LINES_ALL — Line and distribution detail carried onto the generated debit memo.
• AP_SUPPLIERS, AP_SUPPLIER_SITES, AP_SUPPLIER_SITES_ALL — Supplier and supplier site validation for the memo.
• AP_SYSTEM_PARAMETERS — Payables system options governing defaults and controls.
• FND_CURRENCIES — Currency validation and related GL currency handling.

Additional dependencies on PO_DISTRIBUTIONS, PO_HEADERS, PO_LINES, PO_LINE_LOCATIONS, RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, and RCV_TRANSACTIONS indicate that purchase order and receipt matching data may be consulted when deriving debit memo amounts.

Usage Notes

AP_AUTO_DM_CREATION_PKG is an internal utility rather than a publicized API. It is not referenced by any other database object and is not exposed as a documented open interface. Invocation would typically occur from custom Extensions or from concurrent programs written by implementation teams needing to automate debit memo generation. Oracle Forms for Payables do not directly call the package in a published manner. Because the parameter list of CREATE_DM is undefined in the documentation, developers must inspect the package specification in the APPS schema before calling it. Testing should be conducted in a non-production environment, and the package should be treated as subject to change during patching.