Search Results create_dm

Overview

AP_AUTO_DM_CREATION_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its name reflects its purpose: the automated creation of distribution (DM) records within the Payables (AP) module. In Oracle Payables, invoice distributions represent the accounting and tax allocation lines that make up an invoice — the individual lines that specify the expense account, amount, and descriptive detail for each portion of the invoice. Before an invoice can be accounted and validated through the Payables accounting engine, its distributions must exist in the underlying tables.

This package supports an automation pathway for generating those distribution rows programmatically, rather than requiring a user to key each distribution manually through the Payables entry forms. It is classified in the ETRM metadata as an "OTHER" API, meaning it is not part of Oracle's documented public API set and carries no formal interface guarantee. It is an internal utility intended for use by other Payables components, batch processes, or tightly-coupled custom code that needs to materialize invoice distribution records in a controlled fashion.

Key Procedures and Functions

The documented ETRM metadata identifies a single program unit within the package:

• CREATE_DM — The core routine responsible for creating distribution records. Based on the package's declared dependencies and name, this procedure handles the insertion and population of invoice distribution data, driving the batch and invoice context required to associate the generated distributions with their parent invoice. The documented metadata does not expose the parameter list, so its exact interface must be confirmed against the live source in the environment.

Because only one program unit is documented, the package is best understood as a focused single-purpose routine rather than a general-purpose API library. No functions with return values are enumerated in the metadata.

Tables Accessed

The package references a substantial set of Payables objects through APPS synonyms, which delineates both its operating context and the data it consumes and produces:

• AP_INVOICES, AP_INVOICES_ALL, AP_INVOICES_S, AP_INVOICES_S1 — the invoice header tables and their supporting views/sequences. The base process requires the invoice identity to attach distributions.
• AP_INVOICE_DISTRIBUTIONS, AP_INVOICE_LINES_ALL — the primary target tables where created distribution and line records are persisted.
• AP_BATCHES, AP_BATCHES_ALL, AP_BATCHES_S, AP_BATCHES_S1 — invoice batch tables, indicating that distribution creation may be performed in a batch or grouped context, and that the routine coordinates batch membership.
• AP_SUPPLIERS, AP_SUPPLIER_SITES, AP_SUPPLIER_SITES_ALL — supplier and supplier site data, used to resolve vendor context such as default liability or site-level accounting attributes.
• AP_SYSTEM_PARAMETERS — Payables system-level configuration that supplies defaulting behavior and accounting rules.
• FND_CURRENCIES — currency definitions, required when distributions carry amount or currency conversion attributes.

The breadth of these references confirms that CREATE_DM must validate its target invoice against batches, supplier, and system configuration before writing distributions.

Usage Notes

As an internal utility rather than a published API, AP_AUTO_DM_CREATION_PKG is not intended for direct invocation from end-user forms. It is most likely called by Payables batch and import processes — for example, invoice import or auto-creation routines that need to build distributions as part of a larger transaction — or invoked from custom concurrent programs and PL/SQL code where a developer requires programmatic generation of invoice distributions. ETRM records zero dependent packages referencing it, so its consumers are not other documented packages but application-level callers.

Because Oracle does not publish the signature of CREATE_DM or guarantee its stability across patch levels, any custom code that calls this package should be treated as a controlled extension, validated thoroughly against the specific 12.1.1 or 12.2.2 installation, and re-verified after Payables patches. Developers should prefer documented Payables APIs (such as the invoice and distribution APIs) where an equivalent public interface exists, reserving this package for cases where no supported alternative fulfills the requirement.