Accounting Principles and Practices

Cross-validation rules is correct because they prevent invalid account code combinations from being created during dynamic insertion by defining valid segment value relationships. Chart of accounts defines the structure, not validation rules. This is about preventing data entry errors.

All of the above is correct because both Financial Statement Generator (FSG) and Global Consolidation System (GCS) are consolidation tools within Oracle General Ledger. FSG creates financial statements for single or multiple entities. GCS handles multi-entity consolidation across different currencies and calendars.

All of the above is correct because Fixed Assets, Projects, and Inventory are all valid sources that can generate journal entries and feed into the general ledger in Oracle EBS. Each module creates accounting entries that flow to GL. Fixed Assets generates depreciation entries. Projects generates cost and revenue accounting. Inventory generates COGS and valuation entries.

The expense AP Accrual Account used in period-end accrual processes defaults from Purchasing Options. This account captures accrued expenses for goods received but not yet invoiced, and its default is configured in the purchasing setup options.

Payables and Purchasing can close independently of each other. These are separate modules with their own period close processes. While there may be business dependencies, the system does not enforce any technical requirement that one must close before the other.

Entering invoices and matching them to purchase orders in Payables generates the accounting entries for period-end accruals. The accrual process creates liabilities for goods received but not yet invoiced, which happens when you enter and match invoices to corresponding receipts/POs.

The special calendar in Payables is used for recurring invoices - it defines the schedule for invoices that occur at regular intervals. Option B refers to the Payables calendar (not special calendar), and Option C refers to the future periods setting (not calendar-based).

In Oracle EBS, once an invoice is validated it cannot be deleted - only cancelled. Prepayments can be applied to one or more invoices sharing the same supplier and site as the prepayment. Payables invoices integrate with Oracle Assets by sending lines marked 'Track as Asset' to the Mass Additions interface for asset creation. Since all three statements are true, 'All of the above' is correct.

An Expense Report in Oracle Payables represents the amount due to an employee for business-related expenses incurred. Employees submit expense reports for reimbursement of costs like travel, meals, or supplies. Mixed invoices are PO-related, PO Default references purchase orders, and Credit Memos represent supplier credits, not employee reimbursements.

To interface Payables invoice lines with Oracle Assets, two prerequisites exist: the invoice must be transferred to General Ledger (accounting created), and the distribution account must be either an Asset Clearing account or a CIP (Construction in Progress) account. These conditions ensure only asset-related capital costs flow to Assets. Since both A and B are required, 'All the above' is correct.

A Credit Memo in Oracle Payables represents a credit for goods or services, typically issued when goods are returned to a supplier or when a supplier owes the customer money. It reduces the amount owed to the supplier. Debit Memos increase liability (not credits), Expense Reports reimburse employees, and QuickMatch is an invoice creation method.

In Oracle Payables, period closure is blocked by unaccounted invoices or payments because all transactions must be accounted for and transferred to the General Ledger before a period can be locked. Fully accounted transactions do not prevent closure, and 'All of the above' is incorrect because accounted invoices are valid for closing.

Oracle Receivables enforces a strict workflow where invoice validation must precede accounting entry creation. You cannot pay an unvalidated invoice, and accounting entries are only created after validation completes successfully. This ensures data integrity before financial impact occurs.

An On-Account Credit Memo is the correct mechanism for creating a customer credit that is not tied to a specific invoice. Unlike debit memos or regular invoices which typically relate to specific transactions, an on-account credit memo creates a general credit balance that can be applied later to any invoice.

In manual receipt processing, the 'Confirmed' status indicates that a receipt has been approved and is ready for remittance to the bank. This status comes after initial entry and validation, confirming the receipt is valid and should be included in the next remittance batch.