Results for “payable”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The view PAY_NL_PAY_DED_ACTION_INFO_V is an APPS-owned database view within the Oracle E-Business Suite Payroll (PAY) module. It is documented in ETRM as a "View Used in Dutch Payslip Report" and carries a VALID status. Its purpose is to expose grouped payroll action information that is specifically associated with the Dutch (Netherlands) localization, presenting the calculation components required to print pay and deduction action lines on the Dutch payslip. The view aggregates multiple action-information rows for the same action context and sequence grouping so that a single, consolidated record is returned per logical payslip element. This makes it a reporting-only construct: no application logic writes to it, and it is not an entity that supports transactional DML. Because the view isolates the Dutch localization category ('NL CALCULATIONS'), it shields the report layer from the broader and more generic content of PAY_ACTION_INFORMATION. The inclusion of FND_NUMBER.CANONICAL_TO_NUMBER conversions indicates that the stored action information values are text/character values that must be numerically canonicalized before summation or comparison, which is typical of the flexible ACTION_INFORMATION1 through ACTION_INFORMATIONn columns.
Underlying Base Objects
The view is defined over a single base data source, PAY_ACTION_INFORMATION, which appears in the documented metadata as a synonym. It also calls the FND_NUMBER package to convert canonical string representations into numeric values. The defining query filters the base table with two predicates: ACTION_CONTEXT_TYPE = 'AAP' and ACTION_INFORMATION_CATEGORY = 'NL CALCULATIONS'. It then performs GROUP BY on ACTION_CONTEXT_ID, ACTION_INFORMATION4, ACTION_INFORMATION5, ACTION_INFORMATION6, ACTION_INFORMATION7, ACTION_INFORMATION9, and EFFECTIVE_DATE. The aggregation uses MAX on ACTION_INFORMATION8, ACTION_INFORMATION13, and the three numeric rate fields, with DECODE logic keyed on whether ACTION_INFORMATION13 is NULL to decide between SUM and MAX. This design means the view is a derived, read-only projection whose grain is one row per unique combination of action context, sequence, description, extra-information grouping, and effective date.
Key Columns
ACTION_CONTEXT_ID— Identifier linking the rows to a payroll action context; carries the action context grouping from the base table.MAIN_SEQUENCE— Mapped fromACTION_INFORMATION4; the primary ordering sequence used to place the element on the payslip.SUB_SEQUENCE— Mapped fromACTION_INFORMATION5; the secondary ordering sequence.DESCRIPTION— Mapped fromACTION_INFORMATION6; textual description of the action line.EXTRA_INFO1,EXTRA_INFO2,EXTRA_INFO3— Derived fromACTION_INFORMATION7,ACTION_INFORMATION8(aggregated with MAX), andACTION_INFORMATION9; supplementary descriptive attributes.STANDARD_RATE— Numeric conversion ofACTION_INFORMATION10; summed when the year indicator is NULL, otherwise the MAX value is used.SPECIAL_RATE— Numeric conversion ofACTION_INFORMATION11, following the same SUM/MAX logic.PAYABLE— Numeric conversion ofACTION_INFORMATION12, with the same conditional aggregation.YEAR— Derived from MAX ofACTION_INFORMATION13; controls whether amounts are summed or single-valued. This is precisely the column the search term "action_information13" refers to, and it is the pivot value in the view's conditional logic.
Common Use Cases and Queries
The principal use case is the Dutch payslip report, where the view supplies pre-aggregated rate and payable figures. A typical query retrieves all consolidated lines for a given action context:
SELECT ACTION_CONTEXT_ID, MAIN_SEQUENCE, SUB_SEQUENCE, DESCRIPTION,
STANDARD_RATE, SPECIAL_RATE, PAYABLE, YEAR
FROM APPS.PAY_NL_PAY_DED_ACTION_INFO_V
WHERE ACTION_CONTEXT_ID = :p_action_context_id
ORDER BY MAIN_SEQUENCE, SUB_SEQUENCE;
Analysts often filter on YEAR IS NULL to obtain only rows subject to summation, or on YEAR IS NOT NULL to isolate the single-valued year indicator rows that switch the aggregation behavior. A debugging query that reproduces the view's grouping from the base synonym is also common when validating balance figures prior to printing. Because the view is read-only, it should never be used in DML; it serves exclusively as a reporting and integration surface for the Dutch payroll localization under Oracle EBS 12.1.1 and 12.2.2.
-
View Used in Dutch Payslip Report
APPS.PAY_NL_PAY_DED_ACTION_INFO_V·↳ FND_NUMBER·↳ PAY_ACTION_INFORMATION·Explore PAY module →
-
View Used in Dutch Payslip Report
APPS.PAY_NL_PAY_DED_ACTION_INFO_V·↳ FND_NUMBER·↳ PAY_ACTION_INFORMATION·Explore PAY module →
-
Lookup Type: NO_TIME_ACCOUNT 12.2.2
Unit measurement for Part time absences
-
Investor Product Primary Purposes
-
Lookup Type: NO_TIME_ACCOUNT 12.1.1
Unit measurement for Part time absences
-
Investor Product Primary Purposes
-
Concurrent Program: FVAPRFPR 12.2.2
FMS 224 Populate Payable Refunds Report
-
Gives meaning for the business flow class
-
Gives meaning for the business flow class
-
Concurrent Program: FVAPRFPR 12.1.1
FMS 224 Populate Payable Refunds Report
-
Stream Type Purpose
-
IBY_PMT_CREATION_RULES specifies how documents payable are grouped into payments. Creation rules are determined by payment process profiles. This table corresponds to the Payment Creation tab of the Update Payment Process Profile page.
-
Concurrent Program: APXRTB 12.1.1
Accounts Payable Trial Balance
-
Stream Type Purpose
-
IBY_GEN_DOCUMENT_LINES serves as a template for source product tables or views from which Oracle Payables can import documents payable.
-
Lookup Type: ATTENTION 12.1.1
Parameter for Tax Information Verification letter
-
Lookup Type: ATTENTION 12.2.2
Parameter for Tax Information Verification letter
-
Concurrent Program: APXRTB 12.2.2
Accounts Payable Trial Balance
-
Document Type for Receivables and Payables
-
Lookup Type: BEN_PYMT_STAT 12.1.1
-
IBY_GEN_DOCS_PAYABLE serves as a template for source product tables or views from which Oracle Payables can import documents payable.
-
Transaction Entities
-
Transaction Entities
-
Lookup Type: DEPARTMENT_TYPE 12.2.2
Department Type
-
IBY_DOCUMENTS_PAYABLE_H stores historical snapshots of documents payable. This table contains denormalized versions of documents payable from specific points in time, such as when the payment for this document was submitted to a payment sys
-
Defines how much of a payment process request can be rejected when a document payable fails validation
-
Concurrent Program: APXTBRTB 12.1.1
Accounts Payable Trial Balance (obsolete - replaced by APXRTB)
-
Concurrent Program: IBYBUILD 12.1.1
Validates documents payable and groups them into payments
-
Lookup Type: RESPONSIBILITY 12.2.2
Possible responsibilities for the primary customer contact
-
Invoice information of mass additions you deleted from the FA_MASS_ADDITIONS table using the Delete Mass Additions form
-
Defines how much of a payment process request can be rejected when a document payable fails validation
-
Document Payable Assignment Views
-
GL Payable invoice lookup
-
GL Payable invoice lookup
-
Lookup Type: DEPARTMENT_TYPE 12.1.1
Department Type
-
Lookup Type: BEN_PYMT_STAT 12.2.2
-
Concurrent Program: APXFPMDR 12.1.1
Future Payment Maturity Date Report