The Journal Import process pulls information from the GL Interface table to create valid, postable journal entries in General Ledger. Which two statements are true about the Journal Import process?

The Journal Import process is a crucial step for bringing journal data into the Oracle General Ledger. The process first validates the data residing in the GLINTERFACE table to ensure its integrity and adherence to accounting rules before creating journal entries. A primary method for populating this interface table with data from external, non-Oracle systems is by using File-Based Data Import (FBDI) templates. The FBDI process allows users to format external data into a standardized CSV file, upload it, and run a process that loads the data into the interface table, ready for the Journal Import process to pick up.

B. Errors from Oracle Subledgers must be corrected in the source subledger application itself or using specific correction forms/spreadsheets, not by simply deleting them from the interface.
C. The Journal Import process can create journals in either Detail or Summary mode, depending on the import parameters selected, not just Summary mode.

1. Oracle Fusion Cloud Financials, Implementing Enterprise Structures and General Ledger, Release 24B, Chapter 5: Journal Processing, Section: Journal Import. "Journal Import validates the data in the GLINTERFACE table."

2. Oracle Fusion Cloud Financials, Using General Ledger, Release 24B, Chapter 5: Importing Journals, Section: Journal Import Process. "Use the Journal Import process to import journals from subledgers and external sources... The process validates your data before creating journal entries."

3. Oracle Fusion Cloud Financials, File-Based Data Imports for Financials, Release 24B, Chapter 15: Journal Import. "You can use the Journal Import process to import journals from your legacy systems... Use the JournalImportTemplate.xlsm template to prepare your journal data."