Results for “check_submission_period”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.PAY_JP_DEF_SS is a Japanese localizations package in Oracle E-Business Suite Payroll (PAY) that supports the definition and processing of the Year-End Adjustment (YEA) declaration for dependents (YEA_DEP_EXM_PROC). The package encapsulates server-side logic used by the Japanese Dependent Exemption processing flow, including datetrack-aware insert, update, and delete behavior for element entries and their input values across the PAY and PER schemas. It resolves the element type and input value identifiers for the YEA_DEP_EXM_PROC element at package initialization through HR_JP_ID_PKG, exposing constants for disability type, aged (elder) type, widow type, working student type, spouse type, spouse disability type, and the various dependent count input values (number of dependents, number of aged dependents, aged parents, specified dependents, generally disabled dependents, and severely disabled dependents). In EBS 12.1.1 and 12.2.2, this package is part of the seeded Japanese payroll localization layer and is normally accessed indirectly through payroll Year-End Adjustment concurrent processes and their associated forms rather than called by end users.

Key Procedures and Functions

The 32 documented program units fall into several functional groups:

• Datetrack mode helpers: EE_DATETRACK_UPDATE_MODE and CEI_DATETRACK_UPDATE_MODE determine the appropriate datetrack update mode for element entry and contact extra information records, while CEI_DATETRACK_DELETE_MODE governs the corresponding delete behavior.
• Session handling: INSERT_SESSION and DELETE_SESSION register and remove a processing session row in FND_SESSIONS, and FULL_NAME derives the formatted employee name for the session context.
• Change detection and error handling: CHANGED identifies whether a given record has been modified, and GET_SQLERRM returns the Oracle error message text for exception handling.
• Submission validation: CHECK_SUBMISSION_PERIOD validates the period for which a Year-End Adjustment submission is being made.
• YEA workflow control: DO_INIT, DO_FINALIZE, DO_REJECT, DO_RETURN, DO_APPROVE, DO_TRANSFER, DO_EXPIRE, DELETE_UNFINALIZED, and ARCHIVE_DEFAULT implement the state transitions of a dependent exemption declaration — initializing, finalizing, rejecting, returning, approving, transferring, and expiring submissions, deleting unfinalized records, and archiving defaults. ROLLBACK_TRANSFER and ROLLBACK_EXPIRE reverse those transfer and expire operations where correction is required.

Tables Accessed

The package reads and writes core payroll and HR tables through APPS synonyms. Element and entry data are held in PAY_ELEMENT_ENTRIES_F, PAY_ELEMENT_ENTRY_VALUES_F, PAY_INPUT_VALUES_F, PAY_ELEMENT_LINKS_F, and PAY_LINK_INPUT_VALUES_F, which store the dependent declaration entries and their input values. PAY_ASSIGNMENT_ACTIONS and PAY_ACTION_INFORMATION track the payroll action and action information associated with the declaration. PAY_JP_SWOT_NUMBERS holds the Japanese SWOT (Statement of Withholding Tax) numbering used in year-end processing. Personal and relationship data come from PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, PER_CONTACT_RELATIONSHIPS, PER_CONTACT_EXTRA_INFO_F, PER_ADDRESSES, and PER_JP_ADDRESS_LOOKUPS, which supply the dependent, spouse, address, and relationship information needed to evaluate exemption eligibility. FND_SESSIONS is used for session registration.

Usage Notes

PAY_JP_DEF_SS is invoked primarily from the Japanese Year-End Adjustment flow within Oracle Payroll, including the dependent exemption declaration forms and the associated Year-End Adjustment concurrent programs. It is referenced by two other packages according to the ETRM inventory, indicating reuse by higher-level Japanese payroll localization modules. Because the package performs datetrack-managed inserts and updates and manipulates payroll element entries, it must be invoked within a properly initialized application session and within the correct effective date context, which INSERT_SESSION and the datetrack mode helpers establish. Customizations or extensions that need the YEA_DEP_EXM_PROC element type or input value identifiers can reference the package constants rather than hard-coding IDs. Direct invocation from custom code is discouraged; the documented APIs should be reached through the standard Year-End Adjustment processes and forms to preserve datetrack integrity, approval state, and archiving behavior.