Search Results create_secondary_apl_asg_b

Overview

APPS.HR_ASSIGNMENT_BK8 is a generated PL/SQL package body belonging to the Oracle HRMS API hook layer. The "$Header" comment ("peasgapi.pkb", version 120.37.12020000.11, dated 2013/02/28) identifies it as part of the Assignment API source family, and the internal comment "Code generated by the Oracle HRMS API Hook Pre-processor" confirms that the body was produced automatically rather than hand-coded. Its business purpose is to expose the business logic required to create a secondary assignment (application) record for a person within an organization, in the context of Oracle E-Business Suite 12.1.1 and 12.2.2.

The package is classified as an "OTHER" API in the ETRM repository and is owned by APPS. Two procedures are documented: CREATE_SECONDARY_APL_ASG_A and CREATE_SECONDARY_APL_ASG_B. The "_A" and "_B" suffixes follow the standard Oracle HRMS hook convention, where an "A" (after/actual) procedure carries the substantive process logic and its "B" counterpart provides a before-processing entry point used by the API hook pre-processor framework. This dual structure lets customers attach business rules before and after the secondary assignment creation without modifying Oracle's seeded code.

Key Procedures and Functions

CREATE_SECONDARY_APL_ASG_A is the primary hook procedure for creating a secondary assignment. Its signature accepts a large, flat parameter list, reflecting the breadth of attributes that the underlying HR_ASSIGNMENT_API requires. Parameters are supplied untyped-by-name and include the effective date and person identifier, organizational context (organization, source organization, recruiter, supervisor, person referred by), and assignment placement attributes such as grade, position, job, payroll, location, assignment status type, vacancy, pay basis, and special ceiling step. Additional parameters capture employment and scheduling characteristics: employment category, frequency, normal hours, manager flag, probation period and unit, probation end date, performance and salary review periods and frequencies, normal start and finish times, bargaining unit code, and the set of books. Descriptive fields (change reason, internal address line, comments, source type) and a soft coding keyflex identifier, default code combination identifier, and recruitment activity identifier complete the input set.

The procedure also exposes a full Descriptive Flexfield block through P_ASS_ATTRIBUTE_CATEGORY and P_ASS_ATTRIBUTE1 through P_ASS_ATTRIBUTE11, allowing callers to populate assignment-level DFF segments. CREATE_SECONDARY_APL_ASG_B is the companion before-processing hook that the pre-processor invokes ahead of the main creation step; it allows validation or defaulting logic to run prior to the assignment being committed. Neither procedure is documented with additional business rules in the ETRM metadata beyond these signatures.

Tables Accessed

The ETRM metadata does not list any tables referenced directly through APPS synonyms for this package. Because the body is generated by the HRMS API Hook Pre-processor, its runtime behavior is mediated through the underlying HR_ASSIGNMENT_API, which in turn writes to the standard HR assignment and assignment-extra-info tables (such as PER_ALL_ASSIGNMENTS_F and its _EXTRA_INFO counterparts) and reads supporting HR setup entities for grade, job, position, payroll, location, and status type. Any direct table access would be visible at runtime through the APPS synonyms; the metadata as provided records none, so the package should be treated as an interface layer over the seeded assignment API rather than a direct table manipulator.

Usage Notes

HR_ASSIGNMENT_BK8 is not intended to be called directly from forms or concurrent programs as part of normal configuration. It is invoked automatically by the Oracle HRMS API Hook Pre-processor framework whenever the Create Secondary Assignment API path is executed, including calls originating from the Assignment form and from custom code that calls the corresponding HR_ASSIGNMENT_API procedure. The ETRM metadata notes that the package is referenced by one other package, consistent with its role as a dependent hook rather than a top-level entry point.

Because the hook procedures ship as generated code and are overwritten by patches and upgrades, the recommended practice is to place customer-specific logic in the supported hook extension points rather than editing HR_ASSIGNMENT_BK8 itself. Custom attribute handling should use the P_ASS_ATTRIBUTE_CATEGORY and P_ASS_ATTRIBUTE1..11 parameters, and DFF or business-rule logic should be added through the documented hook mechanism so that it survives patching in both 12.1.1 and 12.2.2.