Oracle Financials: Fixed Assets and Receivables

Transaction Types in Oracle Receivables provide default values for each transaction, including the transaction class (CM, DM, INV, etc.), payment terms, printing options, and whether posting to GL is allowed. Transaction Class is a property, not a setup entity. Transaction Sources control numbering and batch source validation. System Options control global AR module settings, not transaction-specific defaults.

In Oracle Receivables, non-invoice related receipts, such as interest, investments, or refunds, are classified as miscellaneous receipts. Standard receipts are applied against specific customer invoices, and Cash Receipts or Interest Receipts are not the formal subledger terms for this category.

In Oracle Collections, when a customer makes a promise to pay but fails to fulfill it, the promise status is updated to 'Broken'. This triggers collections workflows for escalated follow-up. 'Collectible' is not a valid status, 'No' is too vague, and 'Not Collectible' is different - that's when the debt is deemed uncollectible and written off, not merely when a promise is broken.

During the AutoInvoice import process, data that fails validation checks is placed in the Interface Exceptions table, allowing users to correct the errors. Posting receipts belongs to Receivables (not Cash Management), pricing details are retrieved from Oracle Pricing Engine lists, and booked orders must go through the shipping and fulfillment steps before AutoInvoice imports them.

The Create Accounting program in Oracle Subledger Accounting creates draft journal entries that can be reviewed, but does not post or transfer them to the General Ledger, nor does it reserve funds. Standard entry creation is the main capability of draft mode, confirming B is correct.

AutoLockbox processes receipts in three sequential steps: Import (loading bank transmission data into interface tables), Validation (validating data and ensuring customers are correctly matched), and Post QuickCash (applying validated receipts to customer transactions). Changing this order is incorrect as validation must follow import and precede final posting.

In the Collections window, the Task tab displays all open tasks associated with the customer shown in the header. This is where collectors manage collection activities like follow-up calls, promises to pay, and dispute resolution. Notes (B) are on a separate Notes tab, Profiles (C) shows customer profile information, and Transactions (D) displays the customer's transaction history - each has its own dedicated tab.

Invoicing rules determine when you bill your customer, while accounting rules determine when you recognize revenue. In Oracle Receivables, if you assign an invoicing rule to a transaction, you must also assign an accounting rule to define the revenue recognition schedule.

In Oracle Receivables, a Lockbox is set up and defined for a specific bank account to automate the receipt entry process. Defining it at the bank account level ensures that incoming payments are correctly matched and processed.

Auto Lockbox is the banking service that automatically processes and applies customer receipts via electronic transmission. Banks send payment files containing remittance information, and the Auto Lockbox program automatically applies receipts to open invoices. Direct Debit (A) pulls funds from accounts, Automatic Clearing (B) is not a standard term for this service, and Electronic Fund Transfer (D) is the generic technology but not the specific Oracle Receivables feature name.

In accounts receivable, a commitment represents a guarantee or deposit provided by a customer, often as security for future transactions or credit. This is distinct from adjustments, debit memos, or credit memos which are transactional documents. The commitment serves as a financial assurance until the underlying obligation is fulfilled.

Merging customers is the standard process in Oracle Receivables to consolidate duplicate customer records, clean up data, and merge accounts or sites. Creating relationships merely links different customer accounts without resolving duplication issues.

AutoInvoice (or Autoinvoice Master) is the Oracle Receivables program used to import transaction data from external systems like order management or spreadsheets. It's the interface that converts external transaction data into Receivables transactions. Create Accounting is for journal generation, Revenue Recognition is for revenue management, and Receivables Interface is a broader concept.

AutoCash rules in Oracle Receivables are applied to QuickCash receipts, which are receipts created through the QuickCash feature for automatic receipt creation and application. Manual receipts are processed differently, and 'automatic' is not a specific receipt type in this context.

When a payment is received without identifying the customer, it should be left as 'unidentified' until the customer can be determined. 'On Account' is used when the customer is known but specific invoices aren't. 'Leave as applied' is incorrect because the payment hasn't been applied, and 'mass apply' requires known customer association.

The revenue account assignment error occurs when Receivables cannot build the revenue account code combination. This happens if AutoAccounting is not set up, or if AutoAccounting relies on salesperson data that was omitted from the transaction.

Oracle Assets uses three key flexfields to define asset structure: the Category Flexfield (to group assets), the Location Flexfield (to track physical placement), and the Asset Key Flexfield (for non-financial grouping). Thus, all options are correct.

CIP (Construction in Progress) Assets are capital assets that are being constructed or developed over an extended period before being placed in service. Unlike regular capitalized assets which are typically purchased ready-to-use, CIP assets track costs incurred during the construction phase.

While Category, Asset Type, and Book are essential, mandatory attributes required to define and depreciate an asset, the Category Descriptive Flexfield is an optional field used for capturing additional user-defined information and is not mandatory by default.

Before posting mass additions in asset management systems like Oracle Assets, you can add new lines, split existing lines across multiple assets or categories, and merge lines that should be combined. All three operations are supported to ensure accuracy before final posting.