Oracle Cloud GL common mistakes
Oracle Cloud GL · Understand the traps and how to avoid them.
Treating the Chart of Accounts structure as a flat list of segments and assuming any segment can be reordered or added freely after go-live, then answering questions about segment changes as if they were simple edits.
Candidates study the CoA as a set of value sets and lose track of the fact that the key flexfield structure, segment order, and segment labels are fixed once accounting has begun; they conflate changing values in a value set with changing the structure itself.
What to do instead
Memorise the distinction between the Accounting Key Flexfield structure (defined once per ledger, not modifiable after transactions exist) and the individual value sets and values (maintainable). For any question, first ask whether the stem changes the structure or only the values, and answer accordingly.
Confusing the roles of the four Cs - Chart of Accounts, Calendar, Currency, and Convention (accounting method) - and picking a ledger answer that assumes two ledgers can share a chart but differ on calendar without a secondary ledger.
The four Cs are taught as a checklist, so candidates memorise the list but not the consequence: all four must be identical for a ledger to share the same accounting configuration, and any difference forces a separate ledger or secondary ledger with a defined conversion level.
What to do instead
For every ledger question, write out the four Cs side by side for each ledger in the stem. If any one differs, the answer must involve a secondary ledger, reporting currency ledger, or separate primary ledger - never a shared configuration.
Selecting 'Secondary Ledger' as the answer whenever a second currency or accounting method is mentioned, without checking the conversion level (balance, journal, subledger) implied by the scenario.
Candidates learn that secondary ledgers handle alternate currencies and methods but skip the conversion-level concept, so they cannot distinguish when a reporting currency is sufficient versus when a full secondary ledger with journal-level conversion is required.
What to do instead
Build a three-row table: Reporting Currency (balances only, same CoA/calendar/method), Secondary Ledger (own CoA/calendar/method, conversion level selectable), and Primary Ledger. Match the scenario's need for subledger detail against the conversion level before choosing.
Assuming a journal can be posted to any open period regardless of whether the period status is 'Open' versus 'Never Opened', and answering that a Never Opened period behaves like Open.
Candidates lump all non-closed periods together. In practice a period must be opened (status Open) before journals can post, and Never Opened periods reject posting even though they are not closed.
What to do instead
Memorise the period status lifecycle: Never Opened → Open → Closed → Permanently Closed, plus Close Pending and optionally Open/Closed for specific journal sources. Check the status transition that permits posting (Open) versus the one that blocks it (Never Opened).
Mixing up the order of the period close sequence and answering that subledgers can be closed after the GL period is closed, or that reconciliation can be skipped once subledgers are closed.
The close is described as a set of steps but candidates do not internalise the dependency chain: subledger accounting must be transferred and posted to GL, GL reconciled, then GL closed; and the GL period cannot close while subledger periods remain open.
What to do instead
Draw the dependency chain once: open periods → enter/import subledger transactions → create accounting → transfer to GL → post → reconcile subledger to GL → close subledger periods → close GL period. Answer ordering questions by walking this chain.
Confusing journal reversal methods - Switch Sign versus Change Sign - and applying the wrong one when the stem specifies the reversal should negate the original amounts.
The two methods sound similar. Switch Sign reverses the debit/credit sides (amounts keep their sign but Dr/Cr flips), while Change Sign negates the amounts. Candidates pick by name rather than by effect.
What to do instead
Anchor on the effect: Switch Sign swaps debit and credit; Change Sign multiplies amounts by -1. For each stem, determine whether the desired result is a side swap or a sign flip, then map to the method.
Treating an allocation as a simple percentage split and ignoring the basis, offset, and target account rules, so the candidate cannot predict where the offsetting entry posts.
Allocations are studied as 'spread costs by percentage', but real allocation definitions include a basis (pool, statistical, or formula), a target, and an offset account, and the offset determines the balancing entry. Candidates skip the offset concept.
What to do instead
For every allocation question, identify four elements explicitly: source pool, basis, target, and offset account. The offset account is where the contra entry lands; if the stem does not name it, the answer must reference the allocation definition's offset, not the target.
Assuming FSG (Financial Statement Generator) reports read live from the GL balances without a run, and answering that a report reflects a journal the moment it is posted.
Candidates conflate the report definition with report execution. FSGs are defined, then run (often with a request set), and the output reflects balances as of the run; a posted journal is not automatically in an already-generated report.
What to do instead
Separate definition from execution: define row/column sets, content sets, and report; then run the report (or request set) to produce output. Questions about 'when does the report show X' are answered by the run, not the posting.
Mistaking the role of the Accounting Key Flexfield's segment labels (e.g., Natural Account, Balancing, Cost Center) and answering that any segment can carry the Balancing label.
Segment labels drive behaviour - the Natural Account segment determines account type, and the Balancing segment determines which segment must balance - but candidates treat labels as cosmetic and assume flexibility that the label rules do not permit.
What to do instead
Memorise the mandatory/qualified labels: Natural Account (required, sets account type), Balancing (required for balance enforcement), and the optional Management/Cost Center labels. Only one segment per structure may carry each label, and the Balancing segment controls what must net to zero.
Answering currency questions as if the ledger currency and the entered currency are interchangeable, and ignoring the requirement for a conversion rate type and rate when the entered currency differs from the ledger currency.
Candidates focus on the ledger's currency and forget that journals entered in a foreign currency need a rate type (e.g., Corporate, Spot) and a rate date, and that the GL stores both entered and accounted amounts.
What to do instead
For any journal in a non-ledger currency, check three things: entered currency, conversion rate type, and rate date. The accounted amount is derived from the rate; if the stem omits a rate source, the answer must reference the rate type default, not assume 1:1.