Search Results get_concatenated_dependents




Overview
Explore in AI Chat

Overview

PAY_JP_REPORT_PKG is an Oracle EBS payroll package that supports Japanese localization reporting requirements. Its primary role is to generate the data structures and formatted output required by Japanese statutory payroll reports, including social insurance, labor insurance, and tax-related submissions governed by Japanese regulatory formats. The package combines date-conversion utilities (notably Gregorian-to-Era calendar translation), string-encoding helpers for Japanese character sets, and dynamic SQL execution utilities that allow reports to be assembled at runtime from repository metadata such as element sets and assignment sets.

In Oracle EBS 12.1.1 and 12.2.2, the package resides in the APPS schema and is classified as API classification OTHER, indicating it is an internal utility package rather than a formally published public API. It is referenced by approximately ten other packages, confirming its role as a shared services layer for Japanese payroll reporting components.

Key Procedures and Functions

  • INSERT_SESSION_DATE / DELETE_SESSION_DATE — Manage a session-scoped effective date used as the default context for subsequent report queries within the same database session.
  • TO_ERA — Converts a Gregorian date into the corresponding Japanese imperial era code and the associated era year, month, and day. This function is central to Japanese payroll reporting, which frequently requires era-based dating.
  • GET_CONCATENATED_NUMBERS — Accepts up to ten numeric values and returns a single concatenated string, used to build composite identifiers for report keys.
  • GET_CONCATENATED_DEPENDENTS — Returns a concatenated representation of dependent information for a person as of an effective date, with a Kanji formatting flag.
  • CONVERT2, SJTOJIS, SUBSTRB2, SUBSTR2 — Character-set and string-manipulation utilities supporting Shift-JIS and byte-aware substring operations required by Japanese report layouts.
  • DYNAMIC_SQL — Executes a supplied SQL statement with bind variables and column names defined by packaged record and table types, enabling runtime-configurable report queries.
  • SET_SPACE_ON_ADDRESS — Normalizes address formatting by inserting spacing at defined positions.
  • GET_MAX_VALUE / GET_MIN_VALUE — Return extreme values from supplied inputs for range calculations in report headers and totals.
  • ELIGIBLE_FOR_SUBMISSION — Determines whether an assignment or entry qualifies for inclusion in a given statutory submission.
  • GET_PREV_SWOT_INFO, GET_PJOB_INFO — Retrieve prior-period social insurance and personnel/job information used in comparison sections of reports.
  • CONVERT_TO_WTM_FORMAT — Reformats data into the layout expected by the applicable reporting medium.
  • GET_CONCATENATED_DISABILITY, GET_HI_DEPENDENT_EXISTS, GET_HI_DEPENDENT_NUMBER — Return disability-related concatenated attributes and determine the presence and count of health-insurance dependents.

Tables Accessed

The package reads and writes payroll and HR data primarily through APPS synonyms. People and assignment data are drawn from PER_ALL_PEOPLE_F and HR_ASSIGNMENT_SETS, while reporting scope is defined through PAY_ELEMENT_SETS and PAY_ELEMENT_LINKS_F. Element-level payroll values are obtained from PAY_ELEMENT_ENTRIES_F, PAY_ELEMENT_ENTRY_VALUES_F, and PAY_ELEMENT_TYPES_F. Payroll run context and processing status are read from PAY_ASSIGNMENT_ACTIONS, PAY_ACTION_INTERLOCKS, and PAY_ACTION_INFORMATION. Organization attributes come from HR_ORGANIZATION_INFORMATION. Supporting lookups and messages use FND_LOOKUP_VALUES and FND_NEW_MESSAGES, session context uses FND_SESSIONS, and UTL_FILE provides file output for report generation.

Usage Notes

PAY_JP_REPORT_PKG is typically invoked from Japanese localization concurrent programs and report generators, and from Oracle Forms-based payroll inquiry screens where era dates or dependent information must be displayed. Custom code extending Japanese statutory reports commonly calls TO_ERA, CONVERT2, and DYNAMIC_SQL directly. Because the package is not a published API, callers should treat signatures as version-specific and validate behavior after patch application. The NOCOPY OUT parameters on TO_ERA are a performance optimization for PL/SQL callers only.