Search Results display_last

Overview

The ASO_PAYMENT_DATA_MIGRATION_PVT package body is part of the Oracle Order Management / Oracle Advanced Pricing payment infrastructure within Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its documented purpose is to migrate legacy ASO credit card payment data into the Oracle Payments (IBY) schema. The header comment records an initial creation date of September 7, 2005, and the shipped source file is identified as asovmpdb.pls (with the filename comment variant asovmpdb.pls), carrying a header revision of asovpdmb.pls 120.1 dated July 31, 2006.

The package is classified as a Private (PVT) API, meaning it is intended for internal use by Oracle application code rather than for direct customer invocation. It is referenced by zero other documented packages, confirming its role as a self-contained data migration utility rather than a shared library. Its central business function is to move stored credit card payment instrument data and related external payer records from ASO-owned structures into the IBY Payments tables so that payment processing, instrument validation, and security segment definitions are consistent across the two schemas.

Key Procedures and Functions

The ETRM metadata documents exactly two program units:

• MIGRATE_CREDIT_CARD_DATA_MGR — the manager (driver) procedure. It serves as the entry point for the migration, logs concurrent program output via FND_FILE, reads the ASO debug profile option (ASO_ENABLE_DEBUG) and applies aso_debug_pub tracing, and then dispatches parallel worker subrequests through AD_CONC_UTILS_PKG.submit_subrequests using the product short name ASO. It accepts a batch size (default 1000) and a worker/thread count (default 5).
• MIGRATE_CREDIT_CARD_DATA_WKR — the worker procedure. Each submitted subrequest invokes this worker to process an assigned batch of credit card records, performing the actual extraction from ASO and insertion/update into the IBY payment instrument tables.

The source excerpt confirms the manager's concurrent-program signature (x_errbuf, x_retcode, batch size, and number of workers) and its role in controlling parallelism. Parameter details for the worker are not reproduced in the provided metadata and are therefore not restated here.

Tables Accessed

The following APPS synonyms are documented as referenced by this package:

• ASO_PAYMENTS and ASO_QUOTE_HEADERS_ALL — source ASO payment and quote header data that anchors the credit card records to their originating quote.
• IBY_CREDITCARD and IBY_CC_ISSUER_RANGES — target credit card instrument data and issuer range validation.
• IBY_EXTERNAL_PAYERS_ALL and IBY_EXTERNAL_PAYERS_ALL_S — external payer records and their translation table.
• IBY_PMT_INSTR_USES_ALL and IBY_PMT_INSTR_USES_ALL_S — payment instrument usage assignments and translations.
• IBY_FNDCPT_TX_EXTENSIONS and IBY_FNDCPT_TX_EXTENSIONS_S — funding capture transaction extension attributes and translations.
• IBY_INSTR_S and IBY_SECURITY_SEGMENTS — instrument translation and security segment definitions.
• PLITBLM — the standard PL/SQL index-by table manipulation package used for in-memory batch handling.

Usage Notes

This package is normally invoked through the associated Oracle Payments / Order Management concurrent program that migrates ASO credit card payment data, with batch size and worker count supplied as concurrent program parameters. Because it is a PVT API and is not referenced by other packaged code, it should not be called directly from customer extensions; any re-run or backfill should be driven through the delivered concurrent program to preserve logging, error buffer handling, and parallel worker coordination. The ASO_ENABLE_DEBUG profile option controls the diagnostic output written through aso_debug_pub, which is the recommended mechanism for troubleshooting migration failures. Note that the user search term "display_last" does not appear in the documented metadata for this object.