How to Create GL Journals from Spreadsheet in Oracle Fusion ERP Cloud

[@robinverma7780]

What is the difference between single je tab and multiple je.. And how Multiple je tab works

[@lauren3638]

Very helpful thank you 🙏🏾

[@rayjoanne1]

Do you ever have formatting errors when uploading? If so, any tricks for resolving those types of errors?

[@yemionigbode]

Yes, formatting errors can occur when uploading General Ledger (GL) journals into Oracle Fusion Cloud, especially when using the ADFdi (Application Development Framework Desktop Integration) tool or uploading via Spreadsheet Templates. These errors usually arise due to issues with the structure of the data or how the file is prepared. Here are some common causes and tricks for resolving such formatting errors: 1. Common Formatting Errors - Invalid or Missing Data: One of the most common issues is missing required fields like Account, Debit, Credit, or Description. If any mandatory field is not filled, the system will reject the journal. - Incorrect Date Format: The date might be in an incorrect format (e.g., US format vs. global format). Oracle Fusion typically expects a specific date format based on your system settings. - Currency Issues: Incorrect or invalid currency codes (like using a 2-character code instead of a 3-character one) can cause rejection. - Decimal Precision: Inconsistent use of decimal points (e.g., using a comma instead of a dot) for debit/credit values can also be an issue. - Inconsistent Account Combinations: When the account string (segments like company, department, cost center) doesn't conform to a valid account combination, the journal will fail to upload. - Improper Template Usage: Sometimes, cells in the spreadsheet are inadvertently deleted or altered, especially the hidden metadata rows or columns. This disrupts the upload process. 2. Tips for Resolving Formatting Errors - Use the Correct Template: Ensure you are using the correct ADFdi template for GL journal uploads. Oracle provides a predefined spreadsheet template that includes built-in validation rules. Avoid modifying the structure of the template. - You can download the template from General Accounting > Journals > Create Journal in Spreadsheet. - Verify Required Fields: Double-check that all required fields (Account, Debit, Credit, etc.) are filled correctly. The spreadsheet often includes validation or color-coding to indicate missing or incorrect values. - Ensure Valid Account Combinations: Before uploading, ensure that the account combinations you are using are valid within your Chart of Accounts (COA). If you're unsure, run the Account Combination Inquiry to verify that the combination exists in Oracle. - Check for Hidden Errors: Sometimes errors aren't visible directly in the template. Use the "Validate" button in the ADFdi template to check the data before uploading. - Use the "Check for Upload Errors" option in the Oracle UI after uploading. This provides a detailed log of errors. - Clear Excess Formatting in Excel: Ensure that no extra rows, columns, or hidden metadata are inadvertently modified. Deleting rows, columns, or hidden data elements can cause a failed upload. - Excel often retains formatting for cells you might not be using; clear unused rows and columns to avoid issues. - Date and Number Formats: Ensure your date formats and number formats match what Oracle expects. For instance: - Dates should be in MM/DD/YYYY or DD/MM/YYYY format, depending on your locale settings. - Numbers should not include commas, and decimals should use a dot (.) for separation. - Currency Codes: Always use the correct 3-character ISO currency codes. Verify that the currency you are using is enabled in the system. - Enable Debug Logging: If you're encountering persistent issues, turn on debug logging (if available) during the upload process. This can give you more detailed information about the source of the error. - Use the "Correct" Mode for Corrections: If you need to re-upload due to errors, ensure that you are in the correct mode. For example, if you're re-uploading, choose the "Replace Existing Journal" option to avoid duplicates. 3. Validating the Spreadsheet Before Upload - Pre-validation: Always use the built-in validation function in the ADFdi template before uploading the journal to the system. This allows you to catch errors like missing data, invalid account combinations, and formatting issues before submission. 4. Post-Upload Error Checking - After uploading, check the Error Log in Oracle for specific messages. This log will tell you if there’s a format or data validation error and provide details on what needs to be corrected. 5. Using Web Services for Mass Uploads - For large journal entries, you can use Web Services (SOAP/REST) for mass uploads. These allow more control over formatting and are less prone to Excel formatting issues. However, this requires technical expertise and might not be suitable for every user. By following these best practices, you can avoid and resolve many common formatting errors encountered during GL journal uploads in Oracle Fusion Cloud.