Results for “last_integration_date”

5 results




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

Overview

PA_INTEGRATION_OPTIONS is a configuration table in the Oracle Projects (PA) schema that stores the parameter sets used to drive the integration of Oracle Projects with external or downstream systems, most notably Oracle Grants and Oracle Financials, as well as third-party planning and billing applications. Each row in this table defines a named integration profile — the "integration option" — together with the batch sizing, currency conversion rules, rate schedules, and synchronisation status attributes that control how transactional project data is staged, validated, and exported. Because the table governs the behaviour of the integration process itself rather than holding transactional project records, it is a reference and control object situated at the boundary between the Projects module and its surrounding applications.

Under the heuristic Data Vault classification supplied in the metadata, PA_INTEGRATION_OPTIONS is characterised as standalone, indicating that no foreign key dependencies were mined from its constraint structure. In Data Vault modelling terms, this suggests treating the entity as a standalone hub or reference satellite keyed on its natural business identifier, without the parent link relationships that typically accompany subordinate integration tables. The 21 documented columns split naturally into identity attributes, integration control parameters, and standard EBS audit columns.

Key Information Stored

The primary key of the table is the constraint SYS_C00741173, defined on the single column INTEGRATION_OPTION_NAME. This column is therefore both the surrogate primary key and the principal business-key candidate: it holds the unique name by which each integration profile is identified at run time and referenced by the concurrent programs and APIs that execute the integration.

Common Use Cases and Queries

The table is queried most often to confirm which integration profiles exist and whether they are enabled before launching or troubleshooting an integration run. A typical configuration query is:

  • List active profiles: SELECT integration_option_name, description, integration_batch_size FROM pa.pa_integration_options WHERE enabled_flag = 'Y';
  • Check last run state: SELECT integration_option_name, last_integration_date, integration_process_status, resource_synced FROM pa.pa_integration_options ORDER BY last_integration_date DESC;
  • Review rate configuration: selecting the CURRENCY_CODE and the four bill-rate-schedule columns to verify that conversion and billing defaults are correctly set for a given profile.

Reporting use cases include an integration health dashboard built on INTEGRATION_PROCESS_STATUS and LAST_INTEGRATION_DATE, an audit report on profile changes derived from the audit columns, and a reconciliation query comparing INTEGRATION_BATCH_SIZE against actual throughput to tune batch performance. Because the table is small and configuration-oriented, queries against it are inexpensive and are frequently embedded in concurrent-program lookup logic.

Related Objects

The supplied metadata does not document foreign key relationships, so the following dependencies are those implied by the column semantics and standard Projects integration architecture:

  • PA_BILL_RATE_SCHEDULES — the parent of the four *_BILL_RATE_SCH_ID columns (EMP_BILL_RATE_SCH_ID, JOB_BILL_RATE_SCH_ID, NON_LABOR_BILL_RATE_SCH_ID, RES_CLASS_BILL_RATE_SCH_ID).
  • PA_PLANNING_RESOURCE_LISTS — referenced by PLANNING_RESOURCE_LIST_ID.
  • GL_DAILY_CONVERSION_TYPES — source of RATE_TYPE_CODE values used for currency conversion.
  • FND_CURRENCIES — validates CURRENCY_CODE.
  • FND_USER — resolves CREATED_BY and LAST_UPDATED_BY to user names.
  • Projects integration concurrent programs and APIs that read the profile at run time, and the interface staging tables they populate, depend on this table for their control parameters.

Given the absence of documented foreign keys, any join listed above should be validated against the actual database constraints before being relied upon in production SQL.