Commonly used Tables in Oracle E-Business Suite Payables

 In Oracle E-Business Suite (EBS), the following tables are commonly used to store payable invoice information:

1. AP_INVOICES_ALL: This table stores header information for invoices entered into Payables. Each record represents an invoice.

2. AP_INVOICE_LINES_ALL: Contains information about the individual lines (line items) of each invoice, such as item description, amount, tax details, etc. 

3. AP_INVOICE_DISTRIBUTIONS_ALL: Stores distribution information for each invoice line, including the account code combination, amount, and other accounting details.

4. AP_PAYMENT_SCHEDULES_ALL: If an invoice is scheduled for multiple payments, this table stores the payment schedule information, including due dates and payment amounts.

5. AP_CHECKS_ALL: If payments are made by checks, this table contains information about the issued checks, including check numbers, amounts, and payment dates.

6. AP_PAYMENT_HISTORY_ALL: Stores payment history information, such as payment numbers, dates, and status.

7. AP_PAYMENT_SCHEDULES_PAY: Contains detailed payment schedule information for scheduled payments.

8. AP_CHECKS_ALL: This table stores information about payments made by checks, including check numbers, amounts, and payment dates.

9. AP_CHECKS_ALL: This table contains information about payment batches, including batch numbers, status, and processing dates.

10. AP_BANK_ACCOUNTS_ALL: Stores details about bank accounts used for payments, including bank account numbers, names, and other relevant information.

These are some of the key tables in Oracle EBS Payables where invoice and payment-related information is stored. Depending on the specific needs of your organization and the configuration of your EBS instance, there may be additional tables or variations in table names. Always refer to Oracle's official documentation or consult with your system administrator for the most accurate and up-to-date information.

How to Create an Invoice in Oracle Fusion Payables

To create an invoice in Oracle Fusion Payables, you typically follow these steps:

1. Sign In to Oracle Fusion Applications: Log in to your Oracle Fusion Applications instance with your credentials.

2. Navigate to Payables: Go to the Payables work area. You can find it either on the Navigator menu or through a dashboard depending on your organization's setup.

3. Create Invoice: Once in the Payables work area, navigate to the Invoices tab or section. Look for an option like "Create Invoice" or "Enter Invoice".

4. Enter Invoice Information: Fill out the necessary fields with information about the invoice. This typically includes details such as supplier name, invoice date, invoice number, payment terms, invoice amount, and any applicable taxes.

5. Add Invoice Lines: Enter the line items for the invoice. These are the individual products or services being billed, along with their quantities, unit prices, and any other relevant details.

6. Validate Invoice: Before submission, you may have the option to validate the invoice to ensure all required information is provided and that there are no errors.

7. Submit Invoice: Once everything looks correct, submit the invoice for processing. Depending on your organization's workflow, this might involve routing the invoice for approval by one or more individuals.

8. Review and Approve: If required, review and approve the invoice according to your organization's approval processes. 

9. Payment Processing: After the invoice is approved, it will be ready for payment processing. This might involve scheduling payments, applying discounts, or other financial actions.

10. Record Payment: Once the invoice is paid, record the payment in the system to update the invoice's status and maintain accurate financial records.

Remember, the exact steps and terminology may vary slightly depending on your organization's configuration and the specific version of Oracle Fusion Applications you're using. If you're unsure about any step, consult your organization's internal documentation or reach out to your system administrator for guidance.