Results for “hr_de_tax_information_v”
43 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The HR_DE_TAX_INFORMATION_V view is a German localization object delivered within the Oracle E-Business Suite PER – Human Resources product. It is owned by the APPS schema and carries a VALID status in both the 12.1.1 and 12.2.2 releases. Its stated purpose is to expose German tax information stored against employee element entries in a decoded, presentation-ready format. Rather than forcing consumers to interpret raw ENTRY_INFORMATIONn columns, the view translates the underlying payroll element entry data into named, semantically meaningful columns such as tax card number, tax year, tax status, tax class, and number of children.
Because the view is built on top of PAY_ELEMENT_ENTRIES_F, it acts as a convenience layer for reporting and integration. HR and payroll developers can query German statutory tax attributes without embedding the same SUBSTR, date-conversion, and lookup-decoding logic in every report. The view is therefore most useful in reporting, extract, and downstream integration scenarios where German tax card details must be read in a stable, labeled form.
Underlying Base Objects
Per the ETRM metadata, the view is defined over the following referenced objects:
- PAY_ELEMENT_ENTRIES_F (synonym) — the primary driving object, supplying the element entry rows and the
ENTRY_INFORMATION1throughENTRY_INFORMATIONncolumns. The view exposes itsROWIDasROW_IDand itsOBJECT_VERSION_NUMBER. - FND_DATE (package) — used via
FND_DATE.CANONICAL_TO_DATEto convert the stored canonical date value into anISSUE_DATE. - HR_GENERAL (package) — used via
HR_GENERAL.DECODE_LOOKUPto resolve lookup codes into descriptive values (tax status, tax table, tax class, and the various YES_NO flags). - HR_DE_GENERAL (package) — used via
HR_DE_GENERAL.GET_TAX_OFFICE_DETAILSto derive tax office code and name from the numeric tax office identifier held inENTRY_INFORMATION20. - FND_SESSIONS (synonym) — referenced for session context, typical of EBS views relying on
FND_DATE/HR_GENERALutilities that depend on the current session.
The view is essentially a thin, decoded projection over an _F (date-tracked) element entry table; it does not introduce its own persisted storage.
Key Columns
ROW_ID,OBJECT_VERSION_NUMBER— identity and optimistic-locking support inherited fromPAY_ELEMENT_ENTRIES_F.ELEMENT_ENTRY_ID— the unique element entry identifier.TAX_CARD_NUMBER,TAX_YEAR,ISSUE_DATE,CARD_ISSUER,TAX_CARD_LOCATION— identification of the German tax card and its issuing details.TAX_STATUS_CODE/TAX_STATUS— coded and decoded values using theDE_TAX_STATUSlookup.TAX_TABLE_CODE/TAX_TABLE— coded and decoded values using theDE_TAX_TABLElookup.TAX_CLASS_CODE/TAX_CLASS— coded and decoded German tax class using theDE_TAX_CLASSlookup.YEARLY_CHURCH_TAX_FLAG,MAX_CHURCH_TAX_FLAG,YEARLY_INCOME_TAX_CALC_FLAG,CHAMBER_CONTRIBUTION,PENSIONERS_TAX_FLAG— YES_NO derived indicators.NO_OF_CHILDREN— this is the column most relevant to the search term no_of_children. It is mapped directly fromSUBSTR(ENTRY_INFORMATION11, 1, 30), exposing the number of children declared for German child-related tax allowance (Kinderfreibetrag) purposes.- Tax office columns derived from
ENTRY_INFORMATION20viaHR_DE_GENERAL.GET_TAX_OFFICE_DETAILS, returning a four-character code and a longer descriptive name.
Common Use Cases and Queries
A frequent requirement is to retrieve an employee's declared number of children together with the associated tax card record. Because the view keys on element entry, the query is typically joined back to the element entry and assignment context to isolate a person. Where NO_OF_CHILDREN is stored as character data, comparisons should cast it explicitly.
A basic query follows:
SELECT tax_card_number, tax_year, tax_class, no_of_children, tax_status FROM apps.hr_de_tax_information_v WHERE element_entry_id = :p_element_entry_id;- Filtering employees with dependants:
SELECT row_id, tax_card_number, TO_NUMBER(no_of_children) children FROM apps.hr_de_tax_information_v WHERE TO_NUMBER(no_of_children) > 0; - Reporting by tax office:
SELECT tax_card_number, tax_status, no_of_children FROM apps.hr_de_tax_information_v WHERE tax_year = :p_year;
Typical scenarios include German payroll extract files, tax card reconciliation, and HR self-service reporting. Because the view resolves lookups and tax office details at query time via HR_GENERAL and HR_DE_GENERAL, callers must ensure the named lookups (for example DE_TAX_CLASS) exist and that session context is initialized; otherwise decoded columns may return null.
-
View for german Tax information in the form of Elements
APPS.HR_DE_TAX_INFORMATION_V·↳ FND_SESSIONS·↳ PAY_ELEMENT_ENTRIES_F·Explore PER module →
-
View for german Tax information in the form of Elements
APPS.HR_DE_TAX_INFORMATION_V·↳ FND_SESSIONS·↳ PAY_ELEMENT_ENTRIES_F·Explore PER module →
-
PACKAGE: APPS.HR_DE_GENERAL 12.1.1
-
PACKAGE: APPS.HR_DE_GENERAL 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
SYNONYM: APPS.FND_SESSIONS 12.1.1
-
SYNONYM: APPS.FND_SESSIONS 12.2.2
-
PACKAGE: APPS.HR_GENERAL 12.2.2
-
PACKAGE: APPS.HR_GENERAL 12.1.1
-
PACKAGE: APPS.FND_DATE 12.1.1
-
PACKAGE: APPS.FND_DATE 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person
-
eTRM - PER Tables and Views 12.2.2
Table to store NQF Training info for a person
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person
-
eTRM - PER Tables and Views 12.2.2
Table to store NQF Training info for a person