Search Results do_transfer




Overview

PAY_JP_DEF_SS is a Japanese localization package within the Oracle EBS Payroll (PAY) application, owned by the APPS schema and classified under the OTHER API category. It implements the server-side logic supporting the Japanese payroll "SS" (Social Security / monthly labor and social insurance submission) workflow, exposed through the Oracle Forms Web Interface pattern. The package provides the standard do_init / do_finalize / do_X action-handler stack that Oracle Forms-based localization modules invoke when a user performs lifecycle actions on a submission record, together with date-tracked validation of element entries and contact extra information.

The package is documented at 12.2.2 and the header ($Header: pyjpdefs.pkh 120.0.12000000.3) confirms the 12.0.12000000 code line, so behaviour is consistent across 12.1.1 and 12.2.2. It is referenced by two other packages, indicating it is a subordinate component rather than a top-level entry point.

Key Procedures and Functions

The 32 documented procedures and functions fall into four groups.

Tables Accessed

The package operates on payroll and HR tables through APPS synonyms. Payroll action data is held in PAY_ACTION_INFORMATION and PAY_ASSIGNMENT_ACTIONS, while element data is read and written through PAY_ELEMENT_ENTRIES_F, PAY_ELEMENT_ENTRY_VALUES_F, PAY_ELEMENT_LINKS_F, PAY_INPUT_VALUES_F and PAY_LINK_INPUT_VALUES_F. Japanese-specific numbering is stored in PAY_JP_SWOT_NUMBERS. Person and address data come from PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, PER_ADDRESSES, PER_CONTACT_EXTRA_INFO_F, PER_CONTACT_RELATIONSHIPS and PER_JP_ADDRESS_LOOKUPS. FND_SESSIONS holds the session context established by INSERT_SESSION.

Usage Notes

PAY_JP_DEF_SS is invoked indirectly by the Japanese payroll forms when a user runs a submission action; the form calls DO_INIT, then the appropriate DO_* procedure, then DO_FINALIZE. It is not a concurrent program entry point and should not be called directly from custom code without preserving the action-information and object-version contract. Because it is referenced by two other packages, changes should be treated as dependent-object changes requiring impact analysis. Any customisation must respect the date-track semantics enforced by the EE_ and CEI_ mode functions.