BT Inc. Is Implementing Oracle Accounts Receivable to Interface with an external non-Oracle legacy billing system. The client wants Receivables to generate accounting entries, Instead of sending…

Question

Options

• AAutoAccounting
• Btransaction type
• Caccounting rules
• Dtransaction source
• Ecustomer bill-to site
• Fstandard memo line

• A
  81% (25)
• C
  13% (4)
• D
  6% (2)

Explanation

AutoAccounting (A) is the core engine that uses configurable rules to dynamically derive GL account segments based on transaction data - it's the primary mechanism for generating code combinations. Transaction Type (B) drives AutoAccounting by supplying revenue, receivable, freight, and tax account defaults tied to each transaction class. Customer Bill-To Site (E) provides the customer location used by AutoAccounting to derive territory-based or site-specific GL segments. Standard Memo Line (F) carries revenue account information used when AutoAccounting looks up revenue accounts for non-inventory items.

Why the distractors are wrong: Accounting Rules (C) control when revenue is recognized (e.g., over time via schedules), not which GL accounts are used - they affect timing, not code combinations. Transaction Source (D) defines the origin of transactions (manual, import, etc.) and controls import behavior, but it does not feed account segment values into AutoAccounting.

Memory tip: Think of the four correct answers as the "WHO, WHAT, WHERE, WHAT LINE" formula - AutoAccounting is the engine, Transaction Type is what kind of transaction, Bill-To Site is where the customer is, and Standard Memo Line is what item is being billed. If it doesn't answer one of those questions for account derivation, it's not in the four.

No community discussion yet for this question.