Results for “per_dpf_shd”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
PER_DPF_SHD is a shadow (SHD) package in the APPS schema that supports Oracle E-Business Suite's Deployment Factors subsystem within Oracle Human Resources (PER). Deployment factors define the criteria by which employees, assignments, or positions are matched to a deployment or competency framework. The shadow package operates in close partnership with the primary business logic packages PER_DPF_BUS, PER_DPF_INS, PER_DPF_UPD, PER_DPF_DEL, and PER_DPF_FLEX, collectively forming the DPF package family that governs create, update, delete, and validation processing for deployment factor rows in PER_DEPLOYMENT_FACTORS.
The "_SHD" suffix in Oracle EBS denotes a package whose members are invoked by sibling packages or generated code rather than directly by end-user forms. PER_DPF_SHD encapsulates the low-level plumbing shared across the family: Data Manipulation Language (DML) status reporting, concurrency locking tokens, argument coercion, and constraint-conflict signaling. In release 12.1.1 and 12.2.2 alike, this design pattern centralizes error and locking semantics so the public API packages remain thin and consistent. The ETRM record confirms the package is VALID in the 12.2.2 environment and classified as a non-public API ("OTHER") in the API registry.
Key Procedures and Functions
The ETRM metadata documents five callable units:
- RETURN_API_DML_STATUS — Reports the outcome of the DML operations performed by the enclosing API call. This is the standard EBS mechanism by which shadow helpers surface whether the most recent row-level insert, update, or delete succeeded, allowing the caller to decide whether to continue processing or raise an error.
- CONSTRAINT_ERROR — Centralizes handling of Oracle integrity constraint violations. It intercepts and interprets errors raised against the impacted table so meaningful messages can be propagated to the calling API rather than raw ORA- errors.
- API_UPDATING — Marks or tests the in-progress update state for a deployment factor operation. It prevents re-entrant or conflicting modifications while a given row is being processed by the DPF family, providing the framework-level "who is updating" guard used by peer packages.
- LCK — The locking routine. It acquires the row-level lock or lock token required before a deployment factor row is mutated, ensuring serialized access and consistent behavior when concurrent sessions touch the same PER_DEPLOYMENT_FACTORS record.
- CONVERT_ARGS — Argument normalization utility. It coerces incoming parameter values into the datatypes and formats expected by the DPF business packages, insulating the public API surface from representation mismatches.
Tables Accessed
- PER_DEPLOYMENT_FACTORS — The primary operational table. This package and its siblings read and write deployment factor definitions and criteria rows here. Shadow routines participate in validation, locking, and post-DML status reporting for this table.
- ALL_CONSTRAINTS — The data dictionary view of constraint definitions. PER_DPF_SHD queries this view through its PUBLIC synonym to resolve constraint names and metadata so that the CONSTRAINT_ERROR routine can interpret violations correctly and produce targeted error messages.
The reference to SYS.STANDARD reflects normal PL/SQL language usage rather than a business table dependency.
Usage Notes
PER_DPF_SHD is not intended for direct invocation by end users or external integrations. It is a helper layer beneath the public deployment factor API. In practice it is called by PER_DPF_BUS, PER_DPF_INS, PER_DPF_UPD, PER_DPF_DEL, PER_DPF_FLEX, HR_DEPLOYMENT_FACTOR_API, PER_PQH_SHR, PER_QH_MAINTAIN_UPDATE, and recursively by itself, as evidenced by the eight dependent packages catalogued in the ETRM dependency listing.
Typical invocation occurs when a form or concurrent program in the Deployment Factors setup path performs an insert, update, or delete; the business package calls PER_DPF_SHD to lock the row (LCK), normalize arguments (CONVERT_ARGS), translate constraint failures (CONSTRAINT_ERROR), and then report the DML result upstream (RETURN_API_DML_STATUS). Custom extensions that manipulate PER_DEPLOYMENT_FACTORS directly should replicate this sequence by calling the public business packages instead of calling PER_DPF_SHD directly, preserving supportability and upgrade safety. Because it accesses ALL_CONSTRAINTS, appropriate grants via the PUBLIC synonym are required; no additional synonym creation is normally necessary in a standard EBS installation.
-
PACKAGE: APPS.PER_DPF_SHD 12.1.1
-
PACKAGE: APPS.PER_DPF_SHD 12.2.2
-
PACKAGE: APPS.PER_DPF_FLEX 12.1.1
-
PACKAGE: APPS.PER_DPF_FLEX 12.2.2
-
PACKAGE: APPS.PER_DPF_DEL 12.2.2
-
PACKAGE: APPS.PER_DPF_UPD 12.1.1
-
PACKAGE: APPS.PER_DPF_DEL 12.1.1
-
PACKAGE: APPS.PER_DPF_UPD 12.2.2
-
PACKAGE: APPS.PER_DPF_INS 12.1.1
-
PACKAGE: APPS.PER_DPF_INS 12.2.2