Results for “com_wp_smr_info”

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

Overview

APPS.PAY_JP_WP_COMP_ENTRIES_V is a Japanese localization view in Oracle E-Business Suite that exposes element entry data associated with the element name COM_WP_SMR_INFO. This element is part of the Japanese payroll statutory reporting framework and is used to capture the "Summary Information" (SMR—Social / Statutory Monthly Report, referred to as 社会保険月変 or a related summary declaration) components that feed Japanese payroll processing and reporting obligations. The view presents a pivoted, denormalized representation of element entry records, where up to six input values defined against the COM_WP_SMR_INFO element are transposed into discrete columns based on their DISPLAY_SEQUENCE. Its role is primarily as a reporting and integration layer: Oracle's Japanese localization concurrent programs, extract definitions, and third-party payroll interfaces query this view rather than navigating the underlying element entry tables directly.

Underlying Base Objects

The view is defined over the following documented base objects, all owned by or referenced through APPS:

• FND_SESSIONS (synonym) — joined on USERENV('SESSIONID') to constrain the query to the current application session and to obtain the effective date for element type resolution.
• PAY_ELEMENT_TYPES_F (synonym) — filtered by ELEMENT_NAME = 'COM_WP_SMR_INFO' and by effective date, ensuring only the correct element definition version is used.
• PAY_ELEMENT_ENTRIES_F (synonym) — the primary driver of returned rows; supplies element_entry_id, assignment_id, effective dates, and audit columns.
• PAY_ELEMENT_LINKS_F (synonym) — provides the element_link_id relationship between the element type and the assignment.
• PAY_ELEMENT_ENTRY_VALUES_F (synonym) — the source of the actual screen_entry_value data for each input value.
• PAY_INPUT_VALUES_F (synonym) — supplies display_sequence and lookup_type, which drive the pivot logic.
• HR_GENERAL (package) — invoked via HR_GENERAL.DECODE_LOOKUP to translate coded lookup values into their display meanings.

The view applies an ORDERED hint and explicit index hints (FND_SESSIONS_U1, PAY_ELEMENT_TYPES_F_UK2, PAY_ELEMENT_ENTRIES_F_N50, PAY_ELEMENT_LINKS_F_PK, PAY_ELEMENT_ENTRY_VALUES_F_N50, PAY_INPUT_VALUES_F_PK) to enforce a deterministic join order and dependency on the seed data populated by the Japanese localization installation.

Key Columns

• element_entry_id — Primary key of the element entry record; useful for joining back to PAY_ELEMENT_ENTRIES_F.
• effective_start_date / effective_end_date — Datetracked validity window of the element entry.
• assignment_id — Identifies the assignment to which the entry applies.
• element_link_id — Links the entry to the element link definition.
• object_version_number — Optimistic locking / versioning column.
• Six pivoted value columns (derived from DISPLAY_SEQUENCE 1–6) — each holds either the input_value_id or the corresponding screen_entry_value, truncated or converted as appropriate (SUBSTRB to 6/30 characters, or TO_NUMBER).
• Decoded lookup column — HR_GENERAL.DECODE_LOOKUP(piv.lookup_type, peev.screen_entry_value) for the sequence-4 value, exposed as a readable meaning.
• Audit columns — creation_date, created_by, last_update_date, last_updated_by, last_update_login, each aggregated via MIN(DISTINCT ...).

Common Use Cases and Queries

Typical scenarios include extracting the six summary inputs for a given assignment for statutory reporting, reconciling element entries with upstream payroll runs, and feeding external Japanese social insurance declaration files.

• Retrieve all summary entries for a specific assignment:

  SELECT element_entry_id, assignment_id, effective_start_date,
         col1, col2, col3, col4, col5, col6, decoded_value
    FROM apps.pay_jp_wp_comp_entries_v
   WHERE assignment_id = :p_assignment_id
     AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;

• Audit recently created entries:

  SELECT element_entry_id, creation_date, created_by
    FROM apps.pay_jp_wp_comp_entries_v
   WHERE creation_date >= TRUNC(SYSDATE) - 7
   ORDER BY creation_date DESC;

• Join to PAY_ELEMENT_ENTRIES_F for reconciliation:

  SELECT v.assignment_id, e.element_entry_id, e.creator_type
    FROM apps.pay_jp_wp_comp_entries_v v,
         apps.pay_element_entries_f e
   WHERE v.element_entry_id = e.element_entry_id;

Note that because the view filters on FND_SESSIONS using the current session, it must be queried within an active EBS application session context to return valid effective dates. Direct database access outside that context may return no rows.