Oracle General Ledger provides several methods to create and update daily currency conversion rates. For manual updates, the Currency Rates Manager user interface is accessible from both the Functional Setup Manager (for initial setup) and the General Ledger's Period Close work area (for ongoing maintenance). For bulk updates, users can download a spreadsheet template from the Currency Rates Manager, populate it with rate data, and upload it. For automated, system-to-system updates, the recommended approach is to load data into the Daily Rates open interface table and run an import process.

A. The Currency Rates Manager is not accessible only from the Functional Setup Manager; it is also available in the Period Close work area.

B. Existing transactions are immutable regarding their conversion rates. Updating rates is a master data function and does not involve editing posted transactions.

1. Oracle Fusion Cloud Financials, Implementing General Ledger, 24B, Chapter 11: Currency. The section "Currency Rates Manager" states: "You can enter and maintain daily rates manually in the Currency Rates Manager page or upload them using a spreadsheet."

2. Oracle Fusion Cloud Financials, Using General Ledger, 24B, Chapter 10: Period Close. The section "Tasks in the Period Close Work Area" lists "Manage Currency Rates" as an available task, confirming access outside of FSM.

3. Oracle Fusion Cloud SCM, Implementing Common Features for SCM, 24B, File-Based Data Import (FBDI) for SCM, Chapter: Daily Conversion Rates Import. This document details the process of using the GlDailyRates.xlsm template to upload rates, which corresponds to the open interface method.

The "Adjustment Only" data conversion level prevents the automatic transfer of journals from the primary ledger to the secondary ledger. This setup is appropriate when the secondary ledger must reflect different accounting principles or when only specific transactions, such as manual adjustments for a subset of legal entities, should be recorded. By choosing this level, the customer gains full control to manually enter or upload journals specifically for the required subset of legal entities, thus meeting the requirement without receiving unwanted data from the primary ledger.

B. Journal: This level automatically transfers all approved General Ledger journals for all mapped legal entities from the primary to the secondary ledger.

C. Balance: This level automatically transfers ending balances for all mapped legal entities from the primary to the secondary ledger.

1. Oracle Fusion Cloud Financials Documentation, Implementing General Ledger, Chapter: Ledgers, Section: "Secondary Ledgers". This section describes the four data conversion levels, stating that "Adjustment Only" secondary ledgers are populated with manual journal entries.

2. Oracle Fusion Cloud Financials Documentation, Creating and Administering Analytics and Reports for Financials, Chapter: Financial Reporting and Analysis, Section: "Primary, Secondary, and Reporting Currency Ledgers". The guide explains that the Adjustment Only level requires manual data entry, giving users control over what is posted.

Oracle's recommended best practice for defining a chart of accounts with an intercompany segment is to share the same value set between the company (primary balancing) segment and the intercompany segment. This approach ensures that the list of possible intercompany trading partners is always synchronized with the list of companies. It also simplifies maintenance, as new companies added to the value set are immediately available for both balancing and intercompany transactions. Crucially, any segment value security rules applied to the company segment's value set will automatically apply to the intercompany segment, meeting the requirement efficiently.

A. Defining a default value for the intercompany segment does not address the core requirement of linking it to the company segment values or managing security.

C. The company and intercompany segments must be two distinct segments in the COA structure; assigning both labels to a single segment is functionally incorrect.

D. Creating two different value sets would require redundant maintenance and separate security rule definitions, which is inefficient and contrary to best practices.

1. Oracle Fusion Cloud Financials, Implementing General Ledger, 24A, Chapter: Define Chart of Accounts, Section: Intercompany Segment: Critical Choices. The guide explicitly recommends: "Use the same value set for the company and intercompany segments. This configuration simplifies maintenance and ensures that the intercompany segment is always synchronized with the company segment."

2. Oracle Fusion Cloud Financials, Implementing Intercompany, 24A, Chapter: Intercompany Balancing, Section: Intercompany Balancing Rules: Explained. The documentation on setting up balancing rules assumes a consistent set of values for balancing segments, which is best achieved by sharing a value set.

The procedure involves first defining the Chart of Accounts (COA) structure, which acts as a template for the key flexfield. This includes defining each segment (Company, Cost Center, etc.) and assigning critical segment labels like Primary Balancing, Natural Account, and Cost Center, which control the behavior of the General Ledger. Subsequently, a structure instance is created. The instance is the specific implementation of the structure that will be used by a ledger. Key settings on the instance, such as enabling dynamic combination creation, are configured as required by the scenario.

Oracle Fusion Cloud Financials. (2024). Implementing Enterprise Structures and General Ledger. Chapter 4: Create Chart of Accounts. Section: "Chart of Accounts Structures: Critical Choices" and "Chart of Accounts Structure Instances: Critical Choices".

Oracle Fusion Cloud Financials. (2024). Using General Ledger. Chapter 2: Accounting Setup. Section: "Overview of Chart of Accounts".

A shorthand alias is a code that represents a full or partial account combination. It is used to accelerate the process of manual journal entry by reducing the number of keystrokes required. The steps outlined create a new alias named 07REVDOMESTIC for the "US Chart of Accounts" structure, which, when used in a journal entry, will automatically populate the specified segment values for the domestic revenue account combination.

Oracle Fusion Cloud Financials. (2024). Using General Ledger. Chapter 5: Journal Entry Processing. Section: "Shorthand Aliases: Explained".

Oracle Fusion Cloud Financials. (2024). Implementing Enterprise Structures and General Ledger. Chapter 4: Create Chart of Accounts. Section: "Chart of Accounts Structure Instances: Critical Choices" (describes enabling shorthand aliases at the instance level).

Chart of Accounts (COA) mappings are used to transfer and consolidate data between ledgers that use different charts of accounts. The "Copy" rule is used for segments that share the same value set. The "Rule-based" mapping is used for segments like Account and Cost Center where values need to be transformed. Using ranges (e.g., "is between", "is greater than or equal to") and an "Otherwise" clause ensures that all existing and future segment values are handled by the mapping rules, as required by the scenario.

Oracle Fusion Cloud Financials. (2024). Using General Ledger. Chapter 10: Financial Reporting and Analysis. Section: "Chart of Accounts Mapping: Explained".

Oracle Fusion Cloud Financials. (2024). Implementing Enterprise Structures and General Ledger. Chapter 6: Manage Ledgers. Section: "Ledger Sets and Data Access Sets: Explained" (mentions COA mapping in the context of ledgers).

In Oracle Fusion General Ledger, statistical balances (e.g., number of employees, floor space) are recorded using a special currency code, conventionally 'STAT'. For the system to process these non-monetary amounts correctly, the currency must be explicitly defined as statistical. This is achieved by enabling the "Statistical Unit" option in the currency's configuration. If this option is not enabled, the system cannot record statistical amounts in journals, as it treats 'STAT' like any other monetary currency.

B. The derivation flag is used for reporting currency ledgers to define how conversion rates are derived; it is unrelated to statistical balances.

C. The STAT currency is not an official ISO 4217 currency, so the ISO currency flag should be disabled. Enabling it would be incorrect.

1. Oracle Fusion Cloud Financials, Implementing General Ledger, Release 24B, Chapter: Define Ledgers, Section: "Define Ledger Options". The guide explains that to use statistical accounts, you must enable the STAT currency.

2. Oracle Fusion Cloud Financials, Implementing General Ledger, Release 24B, Chapter: Define General Ledger Foundation, Section: "Currencies". The documentation on the "Manage Currencies" task details the "Statistical Unit" checkbox, which must be selected for currencies used to record statistical balances.

Whether an intercompany transaction generates AR/AP invoices is controlled on the Intercompany Transaction Type. In the Manage Intercompany Transaction Types page you set the “Invoicing Rule” (Invoiced/Not Invoiced); the choice applies to every transaction created with that type, independent of batch, category, or source.

A. Batch controls grouping, not invoice creation.

B. Category only tags the transaction; no invoicing flag.

C. Source indicates origin (e.g., Spreadsheet, Web Service); it has no invoicing attribute.

1. Oracle Financials Cloud, Implementing Intercompany Financial Flows, 24D, “Define Intercompany Transaction Types,” step 4, table 5-2.

2. Oracle Financials Cloud, Using Intercompany Financial Flows, 24D, “Create Intercompany Transactions,” paragraph “Invoice Generation.”

Cross-validation rules stop creation of new invalid combinations at entry time. Existing combinations that already violate a rule remain unless you execute the “Cross-Validation Rule Violations” scheduled process, which lists and can disable them. Thus you must run that process (B), and the rule can then be made effective for both new and existing combinations (E).

A. No scheduled process named “Cross-Validation Rules”; mis-named, therefore incorrect.

C. Dynamic Combination Creation setting is unrelated; CVRs still control manual entry.

D. After running the violation process, existing accounts can also be disabled, so not limited to new.

1. Oracle Fusion Cloud Financials, Implementing General Ledger (23C), “Define Cross-Validation Rules”, pp. 53-55.

2. Oracle Fusion Cloud Financials, Scheduled Processes Guide (23C), “Cross-Validation Rule Violations”, pp. 241-242.

To prevent the entry of new intercompany transactions for a specific period, you should close the period in the Intercompany subledger. Each subledger, including Intercompany, has its own set of accounting periods that can be managed independently of the General Ledger periods. Closing the Intercompany period changes its status to "Closed," which prohibits the creation of any new transactions within that period. This provides precise control over intercompany transaction entry without affecting other modules.

A: Freezing the journal source in GL only prevents posting to GL; it does not stop transaction creation in the Intercompany subledger itself.

C: Closing all subledger periods is overly broad and would unnecessarily halt operations in modules like Payables, Receivables, and Assets.

D: Closing the General Ledger period prevents posting to the general ledger but does not stop transaction creation in the source subledgers.

1. Oracle Fusion Applications Cloud, Implementing Intercompany, Release 13 (Update 24B), Chapter 4: Intercompany System Options and Periods, Section: "Intercompany Periods". "You can open and close intercompany periods to control intercompany transaction entry... When the intercompany period is closed, no new intercompany transactions can be entered."

2. Oracle Help Center, Financials for General Ledger, Chapter: Period Close, Section: "Subledger Period Close". "You must close the subledgers before closing the General Ledger." This highlights the independence of subledger period statuses.