Search Results ap_product_registrations




Overview
Explore in AI Chat

Overview

AP_PRODUCT_REGISTRATIONS is a Payables module table owned by the AP schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as a registration repository that maps Oracle EBS applications and their sub-components to the registration events, APIs, and views through which they are recognized by the Payables product registration framework. This mechanism supports the registration of external or sub-ledger applications that post transactions into Payables, such as Oracle Projects, Oracle Assets, and third-party feeder systems, ensuring that each contributing application is formally identified before it can interact with Payables processing.

From a data modeling perspective, the mined metadata classifies this object as a standalone entity, with no foreign key dependencies documented in the ETRM vault structure. Heuristically, this suggests it is best treated as a hub-style reference object, where REGISTRATION_ID serves as the durable business key and registration attributes behave as descriptive satellites. Because the object is standalone, it does not participate in the link tables typical of a normalized Data Vault design, and its relationships to applications are maintained logically rather than through enforced referential constraints.

Key Information Stored

The table contains 12 documented columns. The most significant are:

REGISTRATION_ID is the documented surrogate primary key. The metadata does not document any additional unique indexes, so business-key candidates beyond the surrogate are not formally established in ETRM.

Common Use Cases and Queries

Typical use cases include auditing which applications are registered with Payables, diagnosing posting failures caused by missing or misconfigured registrations, and confirming whether a feeder application has been fully provisioned after an upgrade or patch. A representative query listing all registrations with their owning applications is:

SELECT pr.registration_id,
       fa.application_short_name,
       pr.reg_application_id,
       pr.registration_event_type,
       pr.registration_api,
       pr.registration_view
FROM   ap.ap_product_registrations pr,
       fnd_application fa
WHERE  pr.application_id = fa.application_id;

Support teams commonly filter by REGISTRATION_EVENT_TYPE or REGISTRATION_API when troubleshooting a specific integration, and DBAs include the table in pre- and post-patch validation scripts, particularly in 12.2 environments where the ZD_EDITION_NAME column must be accounted for in any direct data manipulation.

Related Objects

The metadata documents no foreign keys, so dependencies are logical rather than enforced. The most significant related objects are:

  • FND_APPLICATION — joined on APPLICATION_ID to resolve application short names and descriptions.
  • AP_PRODUCT_REGISTRATIONS_PK — the primary key constraint on REGISTRATION_ID.
  • AP_INVOICES_ALL — the principal Payables transaction table for feeder postings.
  • AP_INVOICE_LINES_ALL — line-level distributions tied to registered applications.
  • AP_INVOICE_DISTRIBUTIONS_ALL — distribution records originating from registered feeder systems.
  • AP_SYSTEM_PARAMETERS_ALL — Payables system configuration influencing registration behavior.
  • FND_CONCURRENT_PROGRAMS — registration-related concurrent programs that consume this configuration.