Search Results migrate_credit_card_data_mgr




Overview
Explore in AI Chat

Overview

The APPS.ASO_PAYMENT_DATA_MIGRATION_PVT package is a private PL/SQL migration utility that belongs to the Oracle Advanced Supply Chain Planning/Order Capture (ASO) application family, specifically supporting the Quote-to-Order and iStore payment data flows. Its sole documented purpose is to migrate legacy credit card and payment instrument data into the Oracle Payments (IBY) repository structure used by Oracle E-Business Suite Release 12. The package header (originally named asovmpds.pls, revision 120.0, dated 30-Nov-2005) traces its lineage to Release 11i-to-12 upgrade preparation, where credit card details previously held in legacy ASO payment columns had to be relocated into the IBY framework introduced in R12.

The API classification is PVT (private), indicating it is internal implementation code not intended for direct customer invocation. Application code and upgrade drivers call into it; end users do not. The object contains two documented procedures — a manager and a worker — that together implement a parallel, batch-oriented migration of credit card records from ASO payment tables into IBY credit card, external payer, and payment instrument tables. All references below apply equally to EBS 12.1.1 and 12.2.2, where the underlying IBY schema is consistent.

Key Procedures and Functions

  • MIGRATE_CREDIT_CARD_DATA_MGR — The manager (driver) procedure. It accepts standard concurrent-program error-buffer and return-code OUT parameters, plus inputs controlling batch size (default 1000) and the number of parallel workers (default 5). Its role is to divide the migration workload into batches and dispatch worker processes to perform the actual data movement. As a concurrent-program-compatible entry point, it returns x_errbuf and x_retcode to the concurrent manager framework.
  • MIGRATE_CREDIT_CARD_DATA_WKR — The worker procedure. It takes the error buffer and return code, plus the batch size, a worker identifier, and the total worker count. Each worker processes its assigned subset of records, enabling the migration to run in parallel across multiple concurrent requests. It is invoked by the manager rather than called independently.

No public functions are exposed; the package is deliberately encapsulated as a private implementation unit. It is not referenced by any other packaged API (0 dependents), confirming its role as a specialized, upgrade-oriented utility.

Tables Accessed

The documented tables, accessed through APPS synonyms, span the ASO payment source and the IBY destination model:

Together these tables support converting legacy ASO-stored card details into the structured, secure R12 Payments instrument model.

Usage Notes

Because this is a private (PVT) package, it is invoked indirectly — typically during R12 upgrade or data-conversion activity, either from an upgrade driver or through a concurrent program definition that points at MIGRATE_CREDIT_CARD_DATA_MGR. The presence of x_errbuf and x_retcode in both procedures confirms concurrent-program registration. Administrators run it with an appropriate batch size and worker count to parallelize large volumes. Direct calls from forms or custom code are not recommended; customers requiring payment migration should use supported conversion tools that internally leverage this package. Given the security sensitivity of credit card data, migrations should be executed in controlled windows, with validation of IBY instrument records afterward.