Results for “ce_pay_fc_payroll_v”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
CE_PAY_FC_PAYROLL_V is an Oracle E-Business Suite view owned by the APPS schema and catalogued under the Cash Management (CE) product family. Its documented purpose is to serve as a forecasting source for payroll expenses. In the Cash Management forecasting framework, Oracle combines projected cash inflows and outflows from multiple sources—such as payables, receivables, and payroll—to help treasury and finance users anticipate short-term liquidity requirements. This view supplies the payroll dimension of that forecast by exposing anticipated payroll disbursements tied to specific bank accounts and payment methods so they can be incorporated into a cash position projection.
Within ETRM 12.2.2 the object is recorded with a status of VALID and is referenced in the 12.1.1 / 12.2.2 documentation set. Rather than storing data itself, it presents a denormalized, query-ready projection assembled from Payroll and Cash Management base objects, allowing forecasting and reporting tools to consume payroll outflows without navigating the complex underlying payroll action model directly.
Underlying Base Objects
The view is defined over five referenced base objects, each exposed to APPS through synonyms:
PAY_PRE_PAYMENTS— the pre-payment records representing payroll amounts to be disbursed.PAY_ORG_PAYMENT_METHODS_F— organization-level payment method definitions, including the associated external bank account and currency.PAY_PAYROLL_ACTIONS— payroll action header information, including action type and effective date.PAY_ASSIGNMENT_ACTIONS— assignment-level actions that link employees to payroll runs.CE_BANK_ACCT_USES_ALL— Cash Management bank account use definitions, providing the internalBANK_ACCOUNT_ID.
The joins enforce several important filters: only actions of type 'P' (payment), 'U' (update/reversal variants), and 'E' are considered; payment methods must be effective as of the action date; and the payroll bank account must reconcile to a Cash Management bank account use through EXTERNAL_ACCOUNT_ID = PAYROLL_BANK_ACCOUNT_ID.
Key Columns
ORG_ID/BUSINESS_GROUP_ID— the operating unit or business group context for the forecast row.CURRENCY_CODE— the currency of the payment method and thus the forecasted amount.AMOUNT— the payroll pre-payment value (fromPAY_PRE_PAYMENTS.VALUE), expressed in the transaction currency.BASE_AMOUNT— the base currency equivalent, used for consolidated forecasting.EFFECTIVE_DATE/TRX_DATE— the payroll action effective date, which determines when the outflow is forecast to occur.ORG_PAYMENT_METHOD_ID/PAYMENT_METHOD— identifier and name of the organization payment method.PAYROLL_BANK_ACCOUNT_ID/BANK_ACCOUNT_ID— the external payroll bank account and the corresponding internal Cash Management bank account.PAYROLL_ID— the payroll action identifier grouping the disbursement.REFERENCE_ID— the pre-payment identifier (PRE_PAYMENT_ID), providing line-level traceability.
Common Use Cases and Queries
This view is typically consumed by cash forecasting reports, custom treasury dashboards, and integrations that populate forecast templates. A representative query projects payroll outflows by bank account and date:
SELECT org_id, currency_code, bank_account_id, effective_date, SUM(amount) payroll_amount
FROM apps.ce_pay_fc_payroll_v
WHERE org_id = :p_org_id
AND effective_date BETWEEN :p_start AND :p_end
GROUP BY org_id, currency_code, bank_account_id, effective_date
ORDER BY effective_date;
Analysts may also reconcile forecast amounts against the base currency total using BASE_AMOUNT, or trace individual entries back to their payroll run through PAYROLL_ID and REFERENCE_ID. Because the view already applies the effective-dating and payment-method join logic, it is the preferred access path for payroll-based cash forecasting rather than querying the underlying Payroll tables directly.
-
View: CE_PAY_FC_PAYROLL_V 12.2.2
Forecasting source - payroll expenses
APPS.CE_PAY_FC_PAYROLL_V·↳ CE_BANK_ACCT_USES_ALL·↳ PAY_ASSIGNMENT_ACTIONS·↳ PAY_ORG_PAYMENT_METHODS_F·Explore CE module →
-
View: CE_PAY_FC_PAYROLL_V 12.1.1
Forecasting source - payroll expenses
APPS.CE_PAY_FC_PAYROLL_V·↳ CE_BANK_ACCT_USES_ALL·↳ PAY_ASSIGNMENT_ACTIONS·↳ PAY_ORG_PAYMENT_METHODS_F·Explore CE module →
-
View: CE_FC_PAY_DISC_V 12.1.1
APPS.CE_FC_PAY_DISC_V·↳ CE_PAY_FC_PAYROLL_V·↳ CE_SECURITY_PROFILES_V·↳ FND_ACCESS_CONTROL_UTIL·Explore CE module →
-
View: CE_FC_PAY_DISC_V 12.2.2
APPS.CE_FC_PAY_DISC_V·↳ CE_PAY_FC_PAYROLL_V·↳ CE_SECURITY_PROFILES_V·↳ FND_ACCESS_CONTROL_UTIL·Explore CE module →
-
View: CE_CP_DISC_PAY_V 12.2.2
Cash Positioning Discoverer View for Payroll Expenses
APPS.CE_CP_DISC_PAY_V·↳ CE_CP_WORKSHEET_LINES·↳ CE_CP_XTR_BANK_ACCOUNTS_V·↳ CE_PAY_FC_PAYROLL_V·Explore CE module →
-
View: CE_CP_DISC_PAY_V 12.1.1
Cash Positioning Discoverer View for Payroll Expenses
APPS.CE_CP_DISC_PAY_V·↳ CE_CP_WORKSHEET_LINES·↳ CE_CP_XTR_BANK_ACCOUNTS_V·↳ CE_PAY_FC_PAYROLL_V·Explore CE module →
-
VIEW: APPS.CE_FC_PAY_DISC_V 12.1.1
-
VIEW: APPS.CE_FC_PAY_DISC_V 12.2.2
-
VIEW: APPS.CE_CP_DISC_PAY_V 12.2.2
-
VIEW: APPS.CE_CP_DISC_PAY_V 12.1.1
-
View: CE_CP_DISC_PRIOR_V 12.2.2
Cash Positioning Discoverer View for Prior-day Balances
APPS.CE_CP_DISC_PRIOR_V·↳ ARP_CASHBOOK·↳ CE_AP_FC_PAYMENTS_V·↳ CE_AR_FC_RECEIPTS_V·Explore CE module →
-
VIEW: APPS.CE_CP_DISC_PAY_V 12.1.1
-
VIEW: APPS.CE_FC_PAY_DISC_V 12.1.1
-
VIEW: APPS.CE_FC_PAY_DISC_V 12.2.2
-
View: CE_CP_DISC_PRIOR_V 12.1.1
Cash Positioning Discoverer View for Prior-day Balances
APPS.CE_CP_DISC_PRIOR_V·↳ ARP_CASHBOOK·↳ CE_AP_FC_PAYMENTS_V·↳ CE_AR_FC_RECEIPTS_V·Explore CE module →
-
12.1.1 DBA Data 12.1.1
-
VIEW: APPS.CE_CP_DISC_PAY_V 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
PACKAGE: APPS.CE_CP_PRIORDAY 12.2.2
-
PACKAGE: APPS.CE_CP_PRIORDAY 12.1.1
-
eTRM - CE Tables and Views 12.2.2
This table stores the error or warning messages from ZBA deal creation process
-
eTRM - CE Tables and Views 12.1.1
This table stores the error or warning messages from ZBA deal creation process