Search Results create_step
Overview
HR_PROCESS_ASSIGNMENT_STEP_SS is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema. It belongs to the Oracle HRMS (Human Resources Management System) product family and supports the workflow-driven processing of assignment step changes, particularly those associated with grade ladders, spinal points, and grade step placement processing. The package is classified under the ETRM registry with an API classification of OTHER, indicating it is not a public, supported API but rather an internal implementation package used by HRMS setup and transactional flows.
The package encapsulates the server-side logic required to create, update, and persist step-related transaction data for employee assignments. It coordinates data across assignment records, spinal point placements, grade ladder definitions, and payroll-related transaction tables. The "_SS" suffix and the internal constants (such as g_api_name set to 'HR_PROCESS_ASSIGNMENT_STEP_SS.PROCESS_API') indicate this is a supporting server-side package invoked from the Oracle Forms-based HRMS user interface and related workflow components.
The header comment ($Header: hrpspwrs.pkb 120.13 2010/09/14 ...) confirms the file name is hrpspwrs.pkb and that it is maintained under the HRMS schema, consistent with 12.1.1 and 12.2.2 code lines.
Key Procedures and Functions
ETRM documents six procedures or functions within this package body:
- CREATE_STEP — Creates a new step record, typically establishing a grade step or spinal point step entry for an assignment as part of the step-change flow. This is the object most relevant to the user's "create_step" search.
- UPDATE_STEP — Modifies an existing step record, allowing changes to step placement or associated attributes while preserving the transactional integrity of the assignment.
- PROCESS_STEP_SAVE — The principal save routine, exposed here as
PROCESS_API. It accepts workflow item type and item key parameters, activity and login identifiers, effective dating options, assignment, placement, step, grade, and grade-ladder identifiers, object version number, business group, effective start and end dates, a change reason, and several OUT parameters returning salary change warnings, GSP post-process warnings, a GSP salary effective date, and page-level error information. It orchestrates datetracking, transaction recording, and grade ladder validation. - PROCESS_API — The public wrapper name exposed by the package (
HR_PROCESS_ASSIGNMENT_STEP_SS.PROCESS_API), delegating to the save logic used by the calling form or workflow. - GET_TRANSACTION_DATA — Retrieves transaction-related data, populating the
hr_transaction_ss.transaction_tablestructure used during step processing. - DELETE_PAY_STEP — Removes a payroll step association, ensuring stale step data is not carried forward into subsequent payroll or salary processing.
Tables Accessed
The package reads and writes several core HRMS tables through APPS synonyms:
- PER_ALL_ASSIGNMENTS_F — The primary assignment datetrack table; step changes are applied and effective-dated here.
- PER_SPINAL_POINT_STEPS_F — Stores defined spinal point steps; used to validate and apply step identifiers.
- PER_SPINAL_POINT_PLACEMENTS_F — Holds the assignment's placement on a spinal point, updated when a step is created or changed.
- PER_SPINAL_POINTS — Defines spinal points used in grade step processing.
- BEN_PGM_F — Benefits program definitions, referenced for grade ladder programme validation.
- PER_PAY_TRANSACTIONS — Payroll transaction records affected by step and salary changes.
- WF_ITEMS — Oracle Workflow items, referenced to resolve the workflow item type and key passed into PROCESS_STEP_SAVE.
Usage Notes
HR_PROCESS_ASSIGNMENT_STEP_SS is an internal server-side package, not a supported public API. It is typically invoked from the HRMS Forms interface when a user performs an assignment step change, a grade ladder progression, or a spinal point placement transaction. The p_item_type, p_item_key, and p_actId parameters indicate integration with Oracle Workflow, allowing the step-change process to be driven through a workflow activity.
Because the package handles effective dating through PER_ALL_ASSIGNMENTS_F and writes to payroll transaction tables, callers must supply a valid business group, effective date, and object version number to avoid datetrack or concurrency errors. ORACLE EBS customers and consultants should treat this package as read-only and rely on documented HRMS APIs such as HR_ASSIGNMENT_API or the assignment form for supported customizations. Direct calls to this package are unsupported and may break across patches or upgrades.
-
PACKAGE BODY: APPS.HR_PROCESS_ASSIGNMENT_STEP_SS
12.2.2
-
PACKAGE BODY: APPS.HR_PROCESS_ASSIGNMENT_STEP_SS
12.1.1
-
PACKAGE: APPS.HR_PROCESS_ASSIGNMENT_STEP_SS
12.1.1
-
PACKAGE: APPS.HR_PROCESS_ASSIGNMENT_STEP_SS
12.2.2
-
APPS.HR_PROCESS_ASSIGNMENT_STEP_SS dependencies on HR_UTILITY
12.2.2
-
APPS.HR_PROCESS_ASSIGNMENT_STEP_SS dependencies on HR_SP_PLACEMENT_API
12.2.2
-
APPS.HR_PROCESS_ASSIGNMENT_STEP_SS dependencies on HR_SP_PLACEMENT_API
12.1.1
-
APPS.HR_PROCESS_ASSIGNMENT_STEP_SS dependencies on HR_UTILITY
12.1.1
-
PACKAGE BODY: APPS.GME_CREATE_STEP_PVT
12.1.1
-
APPS.GME_CREATE_STEP_PVT dependencies on FND_API
12.1.1
-
APPS.GME_CREATE_STEP_PVT dependencies on FND_API
12.2.2
-
PACKAGE BODY: APPS.GME_CREATE_STEP_PVT
12.2.2
-
APPS.GME_CREATE_STEP_PVT dependencies on GME_BATCH_HEADER
12.1.1
-
APPS.GME_CREATE_STEP_PVT dependencies on GME_BATCH_HEADER
12.2.2
-
APPS.GME_CREATE_STEP_PVT dependencies on GME_DEBUG
12.1.1
-
APPS.GME_CREATE_STEP_PVT dependencies on GME_DEBUG
12.2.2