Search Results per_ptu_dff_mig




Overview
Explore in AI Chat

Overview

PER_PTU_DFF_MIG is a concurrent program owned by the Oracle Human Resources (PER) product family within Oracle E-Business Suite. Its user-facing name is Migrate Person DFF to PTU DFF (Internal). The program is documented in ETRM as an internal process reserved strictly for Development use, meaning it is not intended for customer-facing execution, functional configuration, or end-user business workflows.

The name and description indicate that the program migrates data associated with Person Descriptive Flexfields (DFF) into PTU (Person/Party Transaction Usage) DFF structures. PTU in the Oracle HRMS data model relates to how person and party records support transactional usage patterns, so a migration of this kind would involve transforming or copying descriptive flexfield attribute values from legacy Person DFF contexts into the corresponding PTU DFF contexts. Because it is flagged as internal, it is typically invoked by Oracle development or support personnel during upgrade, patching, or data-fix activities rather than by application administrators.

The program is enabled in the environment (Enabled: Yes), so it can technically be submitted from the Concurrent Programs form, but its internal designation means it should only be run under the direction of Oracle Support or Development.

Execution Details

The documented execution method for PER_PTU_DFF_MIG is Spawned. A spawned concurrent program does not execute as a standalone process on the concurrent manager; instead, it is launched by another program or by a PL/SQL routine that calls the appropriate spawn API. This reinforces its internal role — it is generally triggered as a sub-step of a larger process rather than selected directly from the Submit Requests window.

The documented argument method is Database fetch, meaning the program derives its parameters from a database query at runtime rather than from user-entered arguments or a predefined parameter list. The ETRM metadata records the executable and execution file fields as empty, which is consistent with an internal, spawned process whose invocation logic is embedded in a parent routine rather than exposed through standard executable registration.

How to Run

Under normal circumstances, PER_PTU_DFF_MIG is not submitted through the standard Submit Request (SRS) flow. Because it is spawned and its arguments are fetched from the database, direct submission would typically fail or produce no meaningful result unless the required context, such as driving identifiers and DFF context values, already exists in the database.

  • Internal processes of this type are launched by the parent program or migration routine that supplies the runtime context.
  • If Oracle Support requests execution, it is normally performed in a controlled environment following a documented migration or patch procedure.
  • Users should never schedule, rerun, or cancel this program independently, as doing so may leave DFF migration data in an inconsistent state.
  • Any parameter-like values are retrieved automatically, so no manual entry is expected from a submitter.

Related Objects

Related objects for this program center on Person and PTU descriptive flexfield storage. These commonly include the Person DFF context and segment columns within the PER_* tables, the FND_DF_* flexfield definition tables that hold context and segment metadata, and PTU DFF tables that receive the migrated values. It may also interact with HR person/party APIs such as HR_PERSON_API and related flexfield update routines.

  • Person and PTU descriptive flexfield definition and value tables (FND_DF_*).
  • PER person and party tables containing DFF segment columns.
  • HR and PER public APIs used for person and party flexfield updates.
  • The parent migration or patch routine that spawns this program and fetches its arguments.

Because ETRM documents this object only as an internal Development process, the object list above reflects commonly associated structures; Oracle Support should confirm exact dependencies before execution.