Results for “aei_object_version_number”

50+ results




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

Overview

PAY_JP_ISDF_LIFE_PENS_V is an APPS-owned database view within the Oracle E-Business Suite Payroll (PAY) product, documented as VALID in ETRM for release 12.1.1 and 12.2.2. Its description states that the view is used for Japanese localization only. The object presents a filtered, canonicalized projection of life insurance pension declaration data captured against assignment-level action information, exposing the records classified under the action context type AAP and the action information category JP_ISDF_LIFE_PENS. In practice, it functions as a reporting and integration surface for the Japanese statutory insurance reporting feature set, allowing external extracts, concurrent programs, and downstream interfaces to consume life pension declaration rows without querying the underlying DML view directly. Because the view applies its own predicate filters, it isolates the Japan-specific life pension slice of the broader action information model.

Underlying Base Objects

The documented referenced base objects are the FND_DATE package, the FND_NUMBER package, and the view PAY_JP_ISDF_LIFE_PENS_DML_V. The view text confirms that all three are used directly: the SELECT list is built entirely over PAY_JP_ISDF_LIFE_PENS_DML_V, and the two FND packages supply the canonical conversion functions FND_NUMBER.CANONICAL_TO_NUMBER and FND_DATE.CANONICAL_TO_DATE. These calls convert internally stored canonical (character-based) representations into true numeric and date datatypes for consumers, which is a common pattern in Oracle EBS localization objects where the DML layer stores flexible-form values. The outer WHERE clause restricts the result set to rows where ACTION_CONTEXT_TYPE = 'AAP' and ACTION_INFORMATION_CATEGORY = 'JP_ISDF_LIFE_PENS', meaning the DML view supplies the superset and this view supplies the Japan life pension subset. There is no documented dependency on base tables other than those reached through the DML view.

Key Columns

The view exposes twenty-six columns. The identity and concurrency columns include ROW_ID, ACTION_INFORMATION_ID, OBJECT_VERSION_NUMBER, and AEI_OBJECT_VERSION_NUMBER — the latter converted via FND_NUMBER.CANONICAL_TO_NUMBER and matching the user search term "aei_object_version_number", indicating it is the version number of the assignment extra information row. Context columns are ASSIGNMENT_ACTION_ID, ACTION_CONTEXT_TYPE, ASSIGNMENT_ID, EFFECTIVE_DATE, ACTION_INFORMATION_CATEGORY, and STATUS. ASSIGNMENT_EXTRA_INFO_ID is likewise canonicalized to a number. The Japanese life pension business attributes are PENS_INS_CLASS, PENS_INS_COMPANY_CODE, INS_COMPANY_NAME, INS_TYPE, the canonicalized INS_PERIOD_START_DATE, INS_PERIOD, CONTRACTOR_NAME, BENEFICIARY_NAME, BENEFICIARY_RELSHIP, and the canonicalized ANNUAL_PREM. Standard audit columns close the list: LAST_UPDATE_LOGIN, LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATED_BY, and CREATION_DATE.

Common Use Cases and Queries

Typical scenarios include extracting life pension insurance declarations for a given assignment or effective period, reconciling premium amounts, and feeding statutory reports. Because the view has already applied the category and context filters, queries can focus on business predicates. For example, to retrieve declarations for an assignment:

  • SELECT assignment_id, effective_date, pens_ins_class, ins_company_name, ins_period, annual_prem FROM apps.pay_jp_isdf_life_pens_v WHERE assignment_id = :p_assignment_id ORDER BY effective_date;
  • SELECT beneficiary_name, beneficiary_relship, annual_prem FROM apps.pay_jp_isdf_life_pens_v WHERE assignment_action_id = :p_aai AND status = 'A';
  • SELECT effective_date, action_information_id, aei_object_version_number FROM apps.pay_jp_isdf_life_pens_v WHERE last_update_date >= :p_since;

Analysts should note that AEI_OBJECT_VERSION_NUMBER and the numeric or date columns are returned as converted datatypes, so no further canonical decoding is required by the caller. Any query should include the standard APPS schema qualification and appropriate access grants.