Search Results get_segments_from_ccid

Overview

HR_PROCESS_SIT_SS is a server-side PL/SQL package body owned by APPS in the Oracle E-Business Suite. The package supports the Supplemental Information Type (SIT) infrastructure within Oracle Human Resources, specifically the processing, persistence, and retrieval of person analysis data captured through configurable flexfield-based Supplemental Information Types. Its controlling header (hrsitwrs.pkb, version 120.0) dates to Release 12 and the object remains valid in both EBS 12.1.1 and 12.2.2, functioning unchanged across the two releases because it operates primarily against PER_* and HR_API_TRANSACTION_STEPS interfaces.

The core business function is transactional: it accepts person-level analysis information entered through a form or API, persists the resulting rows into the person analysis tables, and records the individual steps of each transaction so that the operation can be audited, retried, or rolled back independently. Of the eight documented program units, six are conventional transaction lifecycle procedures and one, GET_SEGMENTS_FROM_CCID, provides the key-flexfield segment resolution utility that users frequently search for.

Key Procedures and Functions

• SAVE_TRANSACTION_DATA — The primary entry point. It receives person, analysis criteria, business group, ID flex, structure, item type/key, activity, and action context together with a set of generic attribute columns, then writes the corresponding transaction and returns a transaction step identifier and error message. It orchestrates the other DML helpers.
• INSERT_SIT — Creates new Supplemental Information Type rows for a person and analysis criteria combination.
• UPDATE_SIT — Modifies existing SIT rows, typically when a person's analysis information is corrected or re-keyed.
• DELETE_SIT — Removes SIT rows for a person, supporting end-dating and cleanup of erroneous entries.
• GET_SEGMENTS_FROM_CCID — Resolves the individual key-flexfield segment values from a concatenated code combination identifier, allowing callers to present or validate the structure and segment values behind an accounting or key flexfield combination without querying FND tables directly.
• GET_TRANSACTION_DATA — Retrieves previously saved transaction information, enabling forms and APIs to re-display or re-process an existing transaction.
• PROCESS_API — Executes the API-side processing logic associated with a saved transaction, driving validation and downstream HR updates.
• DEL_TRANSACTION_DATA — Purges transaction step and staging records once processing has completed or been abandoned.

Tables Accessed

• PER_ANALYSIS_CRITERIA — Defines the analysis criteria configured for a Supplemental Information Type; read to validate and contextualize the criteria identifiers passed into the save routines.
• PER_PERSON_ANALYSES — The principal store of person analysis results; INSERT_SIT, UPDATE_SIT, and DELETE_SIT maintain rows here.
• HR_API_TRANSACTION_STEPS — Records each step of an HR API transaction; SAVE_TRANSACTION_DATA and DEL_TRANSACTION_DATA write and purge these rows to provide auditable, restartable processing.
• WF_ITEM_ATTRIBUTES — Holds workflow item attribute values used to pass context between the transaction and the workflow/API engine.

Usage Notes

The package is normally invoked indirectly. The Supplemental Information Type maintenance forms and the HR person analysis flows call these procedures to save, update, or delete SIT data, and the GET_SEGMENTS_FROM_CCID utility is invoked when a form must translate a code combination ID into readable key-flexfield segments. Concurrent or batch processing that must replay or clean up an HR API transaction uses GET_TRANSACTION_DATA, PROCESS_API, and DEL_TRANSACTION_DATA. The package is referenced by no other documented package in the ETRM inventory, so customizations should call it explicitly rather than relying on a supported wrapper. Because the public procedures expose generic OUT parameters for error messaging and transaction step identity, callers must check the returned error message after every invocation rather than assuming success, and should run the save and process steps within a single logical transaction boundary to preserve consistency of PER_PERSON_ANALYSES and HR_API_TRANSACTION_STEPS.