Results for “pay_cn_arch_payment_methods_v”
26 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The PAY_CN_ARCH_PAYMENT_METHODS_V view is an Oracle EBS Payroll (PAY) object owned by the APPS schema. It is a reporting and archival (archive) view that presents an integrated, denormalized picture of payment method information as it applies to employee net pay distributions. Functionally, the view consolidates the relationship between an assignment action, the organizational payment method, the employee's personal payment method, and the associated external bank account details. It is particularly relevant for organizations that need to reconcile, audit, or report on the payment instructions recorded against payroll assignment actions, including the currency and payment amount involved.
The view derives its data from the PAY_ACTION_INFORMATION table filtered to the ACTION_INFORMATION_CATEGORY of 'EMPLOYEE NET PAY DISTRIBUTION' and an ACTION_CONTEXT_TYPE of 'AAP'. This makes it a specialized object oriented toward net pay distribution and payment method analysis rather than general payroll processing.
Underlying Base Objects
The view is defined over five documented base objects, all referenced as synonyms in the APPS schema:
- PAY_ACTION_INFORMATION — the driving table containing the action context and informational segments (e.g.,
ACTION_INFORMATION1throughACTION_INFORMATION18) that map to payment identifiers, names, branches, accounts, currency, and amount. - PAY_PERSONAL_PAYMENT_METHODS_F — the employee-level personal payment method records, joined on
ACTION_INFORMATION2(thePERSONAL_PAYMENT_METHOD_ID). - PAY_ORG_PAYMENT_METHODS_F — the organization-level payment methods, appearing twice in the join: once via the personal payment method (
POPP) and once via the organizational method (POP). - PAY_PAYMENT_TYPES — provides the payment category (
CATEGORY) for both personal and organizational payment types. - PAY_EXTERNAL_ACCOUNTS — supplies the organizational bank name, branch, and account number through
SEGMENT1,SEGMENT2, andSEGMENT3.
The joins are date-effective, using EFFECTIVE_START_DATE and EFFECTIVE_END_DATE bounds against the action's effective date. The view is structured as a UNION ALL, combining multiple selection branches that align organizational and personal payment attributes into a single column set.
Key Columns
- ASSIGNMENT_ACTION_ID — sourced from
PAI.ACTION_CONTEXT_ID; identifies the assignment action. - ORG_PAYMETH_ID / ORG_PAYMENT_METHOD_ID — the organizational payment method identifier.
- ORG_PAYMENT_METHOD_NAME and ORG_PAYMENT_CATEGORY — descriptive name and category of the organizational method.
- ORG_BANK_NAME, ORG_BANK_BRANCH, ORG_BANK_ACCOUNT_NUMBER — external account segments for the organization.
- PERSONAL_PAYMENT_METHOD_ID — sourced from
PAI.ACTION_INFORMATION2; the key value commonly searched by users. - PERSONAL_PAYMENT_METHOD_NAME and PERSONAL_PAYMENT_CATEGORY — descriptive attributes of the employee's personal method.
- PERSONAL_BANK_NAME, PERSONAL_BANK_BRANCH, PERSONAL_BANK_ACCOUNT_NUMBER — the employee's bank details.
- CURRENCY_CODE and PAYMENT_AMOUNT — the currency and value of the distribution.
Common Use Cases and Queries
This view is typically used to report or audit employee net pay distributions, reconcile payment amounts against payment methods, and support archival or compliance reporting. A common query locates all distributions for a specific PERSONAL_PAYMENT_METHOD_ID:
SELECT assignment_action_id,
personal_payment_method_id,
personal_payment_method_name,
personal_bank_account_number,
currency_code,
payment_amount
FROM apps.pay_cn_arch_payment_methods_v
WHERE personal_payment_method_id = :p_personal_payment_method_id;
To summarize net pay by organizational payment method category, an aggregate query can be issued:
SELECT org_payment_category,
SUM(payment_amount) total_amount
FROM apps.pay_cn_arch_payment_methods_v
GROUP BY org_payment_category;
Because the view joins date-effective payment method tables, effective date alignment should be considered when interpreting results. The view is read-only and should not be used for data manipulation.
-
APPS.PAY_CN_ARCH_PAYMENT_METHODS_V·↳ PAY_ACTION_INFORMATION·↳ PAY_EXTERNAL_ACCOUNTS·↳ PAY_ORG_PAYMENT_METHODS_F·Explore PAY module →
-
APPS.PAY_CN_ARCH_PAYMENT_METHODS_V·↳ PAY_ACTION_INFORMATION·↳ PAY_EXTERNAL_ACCOUNTS·↳ PAY_ORG_PAYMENT_METHODS_F·Explore PAY module →
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - PAY Tables and Views 12.1.1
Temporary table used to hold invalid location addresses.
-
eTRM - PAY Tables and Views 12.2.2
Temporary table used to hold invalid location addresses.
-
eTRM - PAY Tables and Views 12.1.1
Temporary table used to hold invalid location addresses.
-
eTRM - PAY Tables and Views 12.2.2
Temporary table used to hold invalid location addresses.