Search Results return_from_deployment




Overview
Explore in AI Chat

Overview

APPS.HR_PERSON_DEPLOYMENT_SWI is a self-service wrapper package within the Oracle E-Business Suite Human Resources module. Its principal role is to expose the underlying deployment business logic implemented in HR_PERSON_DEPLOYMENT_API to self-service (SSHR) and workflow-driven callers in a controlled, single point of entry. The "_SWI" suffix denotes a self-service web interface wrapper, a convention Oracle applies to packages that adapt a core API for use by the self-service layer without requiring the caller to derive internal identifiers directly.

In Oracle EBS 12.1.1 and 12.2.2, the package supports the person deployment business process — the movement of an employee from a source business group, organization, or assignment context to a target context, together with the associated dates, terms, and approvals. Because deployment transactions are subject to approvals, the wrapper coordinates both the deployment record itself and the workflow metadata that tracks approval progress. The package is classified under the "OTHER" API category in ETRM, and the documented header explicitly states that access is intended for internal development use only, meaning it is not published as a supported public API for external or customer extension development.

Key Procedures and Functions

The package contains thirty documented procedures and functions. The core transactional procedures are:

  • CREATE_PERSON_DEPLOYMENT — the self-service wrapper to HR_PERSON_DEPLOYMENT_API.create_person_deployment; it creates a new deployment record. Its parameter list carries the source and target business groups, source and target persons, deployment type, start and end dates, organization, location, job, position, grade, supervisor, payroll, and related leaving-reason and policy attributes, plus a validation flag defaulting to the API false constant.
  • UPDATE_PERSON_DEPLOYMENT — modifies an existing deployment record.
  • DELETE_PERSON_DEPLOYMENT — removes a deployment record.
  • INITIATE_DEPLOYMENT — starts the deployment transaction, including its approval workflow.
  • CHANGE_DEPLOYMENT_DATES — adjusts the effective period of an existing deployment.
  • RETURN_FROM_DEPLOYMENT — the procedure matching the user's search term; it processes the return of a deployed person from the deployment back to the originating context, closing out the deployment.
  • PROCESS_API — the generic internal driver that executes the requested operation and populates the return status.

Supporting getter functions return attributes of a deployment: GETDEPLOYMENTTYPE, GETPERSONDEPLOYMENTID, GETFROMPERSONID, GETTOBGID, GETFROMBGID, GETPERSONTYPEID, GETSTARTDATE, GETENDDATE, GETEMPLOYEENUMBER, and GETORGANIZATIONID. Two validation predicates, ISUPDATEALLOWED and ISDELETEALLOWED, determine whether the current deployment may be modified or removed.

Tables Accessed

The package reads and writes HR_PERSON_DEPLOYMENTS, the base table holding deployment records. Workflow and approval state are managed through WF_ITEM_ACTIVITY_STATUSES and WF_ITEM_ATTRIBUTE_VALUES, which record the status and attributes of the approval process, and PQH_SS_APPROVAL_HISTORY, which stores the approval audit trail. HR_API_TRANSACTIONS and HR_API_TRANSACTION_STEPS capture the API transaction and its processing steps. Attachment handling uses FND_ATTACHED_DOCUMENTS, FND_DOCUMENTS, and FND_DOCUMENTS_TL. XMLDOM, XMLPARSER, and DUAL support internal parsing and utility operations.

Usage Notes

HR_PERSON_DEPLOYMENT_SWI is invoked from the self-service deployment flow and from workflow background processes rather than directly from Oracle Forms. Because the source header marks the package as internal development use only, customizations should call HR_PERSON_DEPLOYMENT_API rather than this wrapper wherever possible. ETRM records zero packages referencing this wrapper, confirming its role as a top-level entry point rather than a shared library. Deployments rely on the p_return_status convention: success or failure is indicated by the returned status value, which callers must check.