Inventory Integrations, Reporting, and Period Close
Inventory Integrations, Reporting, and Period Close
This domain tests how data enters and leaves Oracle Cloud Inventory and how the period is closed. The exam focuses on FBDI, REST, reporting, ESS jobs, and close sequencing.
Core rules
- File-Based Data Import (FBDI) uses templates, a load step, and an import step. You validate and correct errors before import; a successful load does not guarantee a successful import.
- REST APIs support real-time integration for items, transactions, and on-hand queries. Batch integrations often use FBDI or scheduled ESS jobs.
- Reporting includes OTBI for real-time analytics and BI Publisher for formatted reports. Inventory balances, transaction history, and receiving reports are common subjects.
- Period close includes transaction processing, cost processor, transfer order accounting, and reconciliation. The inventory period must be open for transactions; close after subledger accounting is complete.
Worked example
You need to load 1,000 new items. Use the Item Import FBDI template, validate the CSV, load it to the interface table, then run the import ESS job. Check the import output for errors before assigning items to organizations. The reasoning: FBDI separates load and import; fixing errors after import is harder. For reporting, use OTBI for a quick on-hand-by-subinventory analysis and BI Publisher for a formatted month-end report.
Traps
- Treating FBDI load as import; the data is not in the application until the import job succeeds.
- Running period close with unprocessed transactions or unaccounted transfer orders.
- Using OTBI for transactional updates; it is a reporting tool.
- Ignoring ESS job output and assuming a scheduled job succeeded.