An Oracle Fusion GL journal-batch query can identify the posting state and the errors attached to a specific batch. Start with the batch, then inspect its journal headers and lines. A matching batch name alone does not establish that the expected accounting entries were posted.
A scoped search is GET /fscmRestApi/resources/11.13.18.05/journalBatches?q=BatchName='DEMO-GL-1042'&limit=5. The batch name is synthetic. Oracle's journal-batch reference documents its searchable fields and finder. Inspect all matches and confirm the period and source before selecting a batch.
Retain JeBatchId and read the item through its returned resource link. Inspect the documented status and meaning fields. Approval, completion and posting state describe different parts of the workflow. A complete batch can still have a posting error.
This Oracle-documented SQL example retrieves a synthetic batch's posting state and summary error. Replace the batch name and illustrative period name with values from your ledger calendar. Oracle defines the fields in GL_JE_BATCHES.
SELECT je_batch_id,
name AS batch_name,
default_period_name,
status,
approval_status_code,
posted_date,
error_message
FROM gl_je_batches
WHERE name = 'DEMO-GL-1042'
AND default_period_name = 'Oct-26'
ORDER BY je_batch_id;Inspect every returned batch ID before selecting a record. ERROR_MESSAGE can summarize several validation failures; a blank value does not establish that every journal line is valid. Use the journal-error resource below for detailed evidence.
Query errors using GET /fscmRestApi/resources/11.13.18.05/journalBatches/{JeBatchId}/child/journalErrors. Oracle's journal-error resource describes the returned evidence. Keep the message and its journal or line references together so an operator can locate the affected entry.
Read the batch's journalHeaders child collection to inspect the journals. Select the required header using its returned key, then read its journalLines collection. Keep those resource keys separate from displayed journal names and line numbers.
Check the ledger and accounting period for the selected journal. Compare entered and accounted amounts using their own currencies and meanings. A balanced set of entered debits and credits does not establish that conversion, account validation or posting completed successfully.
If errors refer to a process, capture the available request ID and inspect that request's final state and output. Do not submit another posting process merely because an earlier terminal command timed out. The ESS recovery guide explains how to investigate an uncertain result.
Fusion Toolkit's journal-investigation recipe reads a resolved batch with its errors and headers. Detailed line reads use the selected journal header. Review collection completeness before calling the investigation complete. The examples were reviewed on 8 November 2026.
You can also use an LLM with the Fusion Toolkit AI Administrator skill and ask, "Why has journal batch DEMO-GL-1042 not posted, and which journal lines are involved?" It can inspect supported Oracle records without requiring you to write the queries. Include the accounting period and request a diagnosis before any correction.