Oracle Fusion Financials utilizes a comprehensive set of tables to manage and store financial data across its various modules. Below is an overview of key tables associated with each financial module:
General Ledger (GL):
• GL_LEDGERS: Stores information about the ledgers defined in the system.
• GL_CODE_COMBINATIONS: Contains the chart of accounts and segment values.
• GL_JE_HEADERS: Holds journal entry header information.
• GL_JE_LINES: Contains journal entry line details.
Accounts Payable (AP):
• AP_INVOICES_ALL: Stores supplier invoice information.
• AP_SUPPLIERS: Contains supplier details and contact information.
• AP_PAYMENTS_ALL: Records payments made to suppliers.
• AP_PAYMENT_SCHEDULES_ALL: Manages payment schedule information.
Accounts Receivable (AR):
• AR_INVOICES_ALL: Stores customer invoice information.
• AR_CUSTOMERS: Contains customer details and contact information.
• AR_PAYMENTS_ALL: Records payments received from customers.
• AR_PAYMENT_SCHEDULES_ALL: Manages payment schedule information.
Cash Management (CM):
• CE_BANK_ACCOUNTS: Stores bank account information.
• CE_STATEMENTS: Contains bank statement details.
• CE_RECONCILIATION_HEADERS: Manages bank reconciliation header information.
Fixed Assets (FA):
• FA_ASSET_HISTORY: Records asset transaction history.
• FA_ADDITIONS_B: Contains information about newly added assets.
• FA_BOOKS: Stores asset book information.
• FA_DEPRN_DETAIL: Manages asset depreciation details.
Expense Management (EM):
• EXM_EXPENSE_REPORTS: Stores employee expense report information.
• EXM_EXPENSE_ITEMS: Contains individual expense item details.
• EXM_EXPENSE_APPROVERS: Manages expense report approver information.
For a comprehensive and detailed list of all tables, including their descriptions and relationships, it is recommended to consult the official Oracle Fusion Cloud Financials documentation. Oracle provides extensive resources that detail the tables and views for each module, which can be accessed through their official documentation.
Additionally, the Oracle community forums and customer connect discussions can be valuable resources for specific inquiries and shared experiences related to Oracle Fusion Financials tables.
Please note that access to certain tables and data may require appropriate permissions within your Oracle Fusion Financials implementation.
Oracle Fusion Financials comprises numerous tables across its modules, each containing various columns that store specific data. Understanding the purpose and sensitivity of these columns is crucial for effective data management and compliance. Below is an overview of key tables, their columns, purposes, and data sensitivity considerations:
General Ledger (GL):
1. GL_JE_HEADERS: Stores journal entry header information.
• Columns:
• JE_HEADER_ID: Primary key for journal entries.
• JE_BATCH_ID: Identifier linking to the journal batch.
• STATUS: Indicates the approval status of the journal entry.
• Sensitivity: Generally low; however, the STATUS column may indicate internal financial processes.
2. GL_JE_LINES: Contains detailed journal entry line information.
• Columns:
• JE_LINE_ID: Primary key for journal entry lines.
• ACCOUNTED_DR: Debit amount in the accounted currency.
• ACCOUNTED_CR: Credit amount in the accounted currency.
• Sensitivity: Medium; financial amounts should be protected to prevent unauthorized access.
Accounts Payable (AP):
1. AP_INVOICES_ALL: Stores supplier invoice information.
• Columns:
• INVOICE_ID: Primary key for invoices.
• VENDOR_ID: Identifier for the supplier.
• INVOICE_AMOUNT: Total amount of the invoice.
• Sensitivity: High; contains financial transaction details and supplier information.
2. AP_SUPPLIERS: Contains supplier details.
• Columns:
• SUPPLIER_ID: Primary key for suppliers.
• SUPPLIER_NAME: Name of the supplier.
• TAXPAYER_ID: Supplier’s tax identification number.
• Sensitivity: High; includes personally identifiable information (PII) such as tax IDs.
Accounts Receivable (AR):
1. AR_INVOICES_ALL: Stores customer invoice information.
• Columns:
• INVOICE_ID: Primary key for customer invoices.
• CUSTOMER_ID: Identifier for the customer.
• INVOICE_AMOUNT: Total amount billed to the customer.
• Sensitivity: High; contains financial transaction details and customer information.
2. AR_CUSTOMERS: Contains customer details.
• Columns:
• CUSTOMER_ID: Primary key for customers.
• CUSTOMER_NAME: Name of the customer.
• CONTACT_NUMBER: Customer’s contact information.
• Sensitivity: High; includes PII such as contact details.
Data Sensitivity and Security Measures:
Oracle Fusion Applications implement several measures to protect sensitive data:
• Masking and Encryption: Sensitive fields in application user interfaces are masked to prevent unauthorized viewing. Encryption APIs are utilized to protect data during transmission and storage.
• Data Classification: Oracle Data Safe provides predefined sensitive types categorized under Identification Information, Financial Information, and more. This classification aids in identifying and securing sensitive columns.
• Data Masking: In non-production environments, data masking techniques are applied to scramble sensitive data, ensuring that it is not exposed during development or testing phases.
For a comprehensive understanding of table structures, columns, and their purposes, consulting the official Oracle Fusion Financials documentation is recommended. This resource provides detailed descriptions of tables and columns, aiding in effective data management and security implementation.
By leveraging these resources and implementing robust data security measures, organizations can ensure the confidentiality and integrity of their financial data within Oracle Fusion Financials.
