You are currently implementing Oracle Cloud for the Singapore entity of your multinational customer. Their head office is located in Japan. Apart from Singapore, their other entities are using a…

Question

Options

• ADefine one primary ledger with Japanese Yen currency so that all the subledger data gets
• BDefine one primary ledger with SGD (Singapore Dollars) as primary currency and use the reporting
• CThis requirement cannot be fulfilled.
• DDefine two ledgers one in SGD (Singapore Dollars) and one in Japanese Yen and transfer data of all

• A
  14% (5)
• B
  77% (27)
• C
  3% (1)
• D
  6% (2)

Explanation

Option B is correct because Oracle Cloud Financials supports Reporting Currencies attached to a primary ledger - the Singapore entity's primary ledger is correctly set to SGD (its functional/operating currency), and a JPY reporting currency is added to automatically translate and present all financials in Japanese Yen for year-end group reporting, with no separate ledger required.

Option A is wrong because setting the primary ledger currency to JPY would mean all day-to-day Singapore transactions are recorded in a foreign currency, violating the principle that a ledger's functional currency must reflect the entity's actual operating environment (SGD).

Option C is wrong because Oracle Cloud explicitly provides the Reporting Currency feature to handle exactly this multinational, multi-currency reporting scenario.

Option D is wrong because creating two full ledgers and manually transferring data is unnecessarily complex - Reporting Currencies automate the conversion and eliminate the need for a separate JPY ledger or data migration.

Memory tip: Think "local ledger, global lens." The entity always books in its local currency (SGD primary ledger), and the Reporting Currency acts as a transparent JPY lens for headquarters - one setup, two currency views, zero manual transfers.

No community discussion yet for this question.