Integrations

Below are the some of integrations in oracle application's modules.

Order To Customer Integration:

     OE_ORDER_HEADERS_ALL OOH
     OE_ORDER_LINES_ALL OOL   
     HZ_CUST_ACCOUNTS_ALL HCAA
     HZ_CUST_SITE_USES_ALL HCSUA
OOH.SOLD_TO_ORG_ID                  = HCAA.CUST_ACCOUNT
OOH.SHIP_TO_ORG_ID                    = HCSUA.SITE_USE_ID
 AND HCSUA.SITE_USE_CODE      = 'SHIP_TO'
OOH.INVOICE_TO_ORG_ID            = HCSUA.SITE_USE_ID
 AND HCSUA.SITE_USE_CODE      = 'BILL_TO'

Order To Inventory Reservations:

     OE_ORDER_HEADERS_ALL OOH
     OE_ORDER_LINES_ALL OOL
     MTL_RESERVATIONS MR
     MTL_DEMAND MD

OOH.HEADER_ID        = MR.DEMAND_SOURCE_HEADER_ID
OOL.LINE_ID               = MR.DEMAND_SOURCE_LINE_ID
OOH.HEADER_ID       = MD.DEMAND_SOURCE_HEADER_ID

Order to Shipping Execution Integration:

OE_ORDER_HEADERS_ALL OOH
OE_ORDER_LINES_ALL OOL
WSH_DELIVERY_DETAILS WDD
WSH_DELIVERY_ASSIGNMENTS WDA
WSH_NEW_DELIVERIES  WND

OOH.HEADER_ID                       = WDD.SOURCE_HEADER_ID
OOL.LINE_ID                              = WDD.SOURCE_LINE_ID
WDD.DELIVERY_DETAIL_ID  = WDA.DELIVERY_DETAIL_ID
WDA.DELIVERY_ID                 = WND.DELIVERY_ID

Note: WDA.DELIVERY_ID will be not null after pick release till before ship confirm.

Order to Move Order Integration:

OE_ORDER_HEADERS_ALL OOH
OE_ORDER_LINES_ALL OOL
MTL_TXN_REQUEST_HEADERS MTRH
MTL_TXN_REQUEST_LINES MTRL

OOH.HEADER_ID = MTRL.TXN_SOURCE_ID
OOL.LINE_ID        = MTRLTXN_SOURCE_LINE_ID

Order to Material Transactions Integration

OE_ORDER_HEADERS_ALL OOH
OE_ORDER_LINES_ALL OOL
MTL_MATERIAL_TRANSACTIONS MMT

OOL.LINE_ID = MMT.TRX_SOURCE_LINE_ID

AR Transaction,SLA and GL Integration:

AP Invoices, SLA and GL Integration:

PO,Receiving, and AP Integration:

AP Invoices to CE
AP_INVOICES_ALL AIA
AP_INVOICE_LINES_ALL AILA
AP_INVOICE_DISTRIBUTIONS_ALL AIDA
AP_INVOICE_PAYMENTS_ALL AIPA
AP_CHECKS_ALL ACL
CE_BANK_ACCOUNTS CBA

AIA.INVOICE_ID = AILA.INVOICE_ID
AIA.INVOICE_ID = AIDA.INVOICE_ID
AIA.INVLICE_ID = AIPA.INVOICE_ID
AIPA.CHECK_ID = ACL.CHECK_ID
AIDA.DIST_CODE_COMBINATION_ID = CBA.ASSET_CODE_COMBINATION_ID

AP Payments TO CE
AP_INVOICES_ALL AIA
AP_INVOICE_PAYMENTS_ALL AIPA
AP_CHECKS_ALL ACA
CE_BANK_ACCOUNTS CBA
CE_BANK_ACCT_USES_ALL CBAUA

AIA.INVOICE_ID = AIPA.INVOICE_ID
AIPA.CHECK_ID = ACA.CHECK_ID
ACA.CE_BANK_ACCT_USE_ID = CBAUA.BANK_ACCT_USE_ID
CBAUA.BANK_ACCOUNT_ID = CBA.BANK_ACCOUNT_ID

AR Cash Receipts to CE Integration:
AR_CASH_RECEIPTS_ALL ACRA
CE_BANK_ACCOUNTS CBC
CE_BANK_ACCT_USES_ALL CBAUA

ACRA.REMIT_BANK_ACCT_USE_ID = CBAUA.BANK_ACCT_USE_ID
CBAUA.BANK_ACCOUNT_ID = CBC.BANK_ACCOUT_ID

CE to GL Integration:
CE_BANK_ACCOUNTS CBA
CE_BANK_ACCT_USES_ALL CBAUA
GL_JE_LINES GJL

CBA.BANK_ACCOUNT_ID                        = CBAUA.BANK_ACCOUNT_ID
CBA.ASSET_CODE_COMBINATION_ID = GJL.CODE_COMBINATION_ID

AR Invoices to Customer Balances
AR_CUSTOMER_TRX_ALL                     CT
AR_CUST_TRX_LINE_GL_DIST_ALL   CTD
AR_PAYMENT_SCHEDULES_ALL        PS ( AMOUNT_DUE_REMAINING)

CT.CUSTOMER_TRX_ID   = CTD.CUSTOMER_TRX_ID
CT.CUSTOMER_TRX_ID  = PS.CUSTOMER_TRX_ID

AR

After shipping goods or services to customer, we will have to generate invoice in Accounting Receivables, this is a document that will be shared with customers for receiving payments from customers for goods or services provided to them. In order to generate invoice we should define below setups.
Define System Options (OU Level for a ledger )
Auto Accounting
Transaction Sources
Transaction Types
Collectors
Remit to Addresses
Open Accounting Periods
Approval Limits
Receivable Activities
Customer and Customer Sites
Invoicing and Accounting Rules

Once it is generated, amount can be received against to invoices generated for customers. In order to receive amount below are some important setups needed in oracle applications.
Receipt Classes and Receipt Methods
Assign Bank Accounts to Receipt Methods
Receipt Sources
Statement Cycles
Standard Memo Lines

Credit Memo : Seller identifies defective items which were shipped to customer and raise credit memo,
reduces customer liability.
1. After shipping goods, already a standard invoice is in place. ( Eg: $5000 ) 2. Seller identified that there is some defective item shipped, so the invoice should be less $1000. 3. So, seller create ‘Credit Memo’ for $1000 against $5000 invoice and bring it to $4000. 4. Send this credit memo to customer.
Debit Memo: Seller identifies missing some charges in actual invoice ( eg: freight charges), so raises debit memo,
increases customer liability.
1. After shipping goods, already a standard invoice is in place. ( Eg: $5000 ). 2. Later, seller identified that it is $500 missed towards freight charges. 3. Seller creates a Debit Memo for $1000 and send it to customer/buyer which increases liability of the customer. 4. This debit memo will be shared to customer.
Charge Back: When customer is valued to company, company will create a charge back invoice which is a new invoice with new due date on old invoice where due date already passed.

Basic accounting entries for invoice and receipts

When we create invoice

   Receivable A/C  Dr 1000

Revenue A/C Cr 1000

When we create Receipt - Cash

Cash A/C Dr 1000

Receivable A/C Cr 1000

Realized gain/loss account:

Customer will pay the invoice amount in different currency based on the payment terms. However, when paying customer may pay in other currency than functional currency as well.
Let us take an example.
The invoice amount on 01-DEC-2017 is INR 15000 and 1 USD = 60 INR on this date.
And, the payment term is N30 - 30 Days.

Now, customer paying $150 on 15-DEC-2017 ( AR takes exchange rate based on the invoice date.)
That means, customer has paid 150 * 60 = INR 9000 invoice amount.

Let us assume that if the exchanged rate on 15-DEC-2017 is 66.6666.
Based on this , the company gained some amount other than INR 9000.
(66.6666-60) * 150 = INR 1000, this amount goes into Realized Gains Account.

Let us assume that if the exchanged rate on 15-DEC-2017 is 58.
Based on this , the company lost some amount other than INR 9000.
(60-58) * 150 = INR 300, this amount goes into Realized Loss Account.

Grouping Rules to segregate AR invoices:

AutoInvoice uses the following hierarchy to determine which grouping rule to use for a transaction line:
1. The grouping rule specified in the Transaction Sources window for the batch source of the transaction line
2. The grouping rule specified in the Customer Profile Classes window for the bill-to site use of the transaction line
3. If you do not specify a rule in either the Transaction Sources or Customer Profile Classes window, AutoInvoice uses the default grouping rule specified in the System Options window.


Note: Receivables provides the DEFAULT grouping rule which contains all of the mandatory attributes. If you upgrade from a previous version of Receivables, the DEFAULT grouping rule initially becomes your default grouping rule.


COGS Account:  This is important account information for any organization in Income Statement(IS) that tells you that
Once revenue recognization is done then only deferred COGS account will be move to actual COGS account.

Technical Information

Below are some important tables in Oracle e-Business Accounts Receivables.

RA_CUSTOMER_TRX_ALL
This is the header table to store Invoices, debit memos, credit memos, charge backs and commitments headers information,
CUSTOMER_TRX_ID is the primary key which stores customer transaction id.

PREVIOUS_CUSTOMER_TRX_ID stores the customer_trx_id of the invoice for which a credit memo is created.
INITIAL_CUSTOMER_TRX_ID stores the customer_trx_id of the deposit and guarantee type invoices.
COMPLETE_FLAG = Y/N - Indicates whether a transaction is completed or not.

RA_CUSTOMER_TRX_LINES_ALL
This table stores invoices, debit memo, credit memo, charge back and commitment lines information.
CUSTOMER_TRX_LINE_ID is the primary key which stores customer transaction line id.

PREVIOUS_CUSTOMER_TRX_LINE_ID - actual invoice line id of credit memo invoice line, for ‘On Account’ line this will be null.

RA_CSUT_TRX_LINE_GL_DIST_ALL

At least one distribution line should exist in this table for each invoice line or credit memo line. Oracle uses this info to post proper amounts to GL.

AR_PAYMENT_SCHEDULES_ALL

RA_CUSTOMER_TRX_ALL CUSTOMER_TRX_ID

AR_PAYMENT_SCHEDULES_ALL CLASS       BR PMT INV DM CM CB DEP GUR STATUS - OP/CL AMOUNT_DUE_ORIGINAL AMOUNT_DUE_REMAINING AMOUNT_APPLIED CONFIRMATION_FLAG TERMS_SEQUENCE_NUMBER REVERSED_CASH_RECEIPT_ID ASSOCIATED_CaSH_RECEIPT_ID ACTUAL_DATE_CLOSED GL_DATE_CLOSED

AR_CASH_RECEIPTS_ALL CASH_RECEIPT_ID

            

IF AMOUNT_DUE_REMAINING = 0 THEN STATUS = ‘CL’ and ACTUAL_DATE_CLOSED  = SYSDATE.
REVERSED_CASH_RECEIPT_ID  → Debit memo Receipt Reverse.
ASSOCIATED_CASH_RECEIPT_ID → Chargeback Receipt.
AMOUNT_DUE_REMAINING contains on-account and unapplied amounts also.
Credit items such as credit memos and receipts are stored as negative numbers and others are +ve.
CONFIRMED_FLAG - Receipts can be confirmed using this column.

AR_CASH_RECEIPTS_ALL
AR_RECEIVABLES_TRX_ALL
AR_RECEIVABLE_APPLICATIONS_ALL
AR_CASH_RECEIPT_HISTORY_ALL

General Ledger

Below is the multi org structure in oracle applications.

                                         Business Group
                                         Legal Entity
                                         Ledger
                                         Operating Units
                                         Inventory Organizations

Business Group is the main entity of the organization under which all employees are managed, payroll is generated, it is head office of any company.

Legal Entity - Is the office under which an organization report to government. A legal entity should be associated with only one ledger, and multiple legal entities can be associated with one ledger.  But one legal entity should not be associated with multiple ledgers. So you can have multiple companies under one ledger.

Ledger : A ledger is useful to capture financial transactions in an organization which can be converted into financial statements. In order to capture any financial transaction in a ledger, we need basic 4 elements, these are easily remembered with 4Cs, Chart of Accounts, Currency, Calendar, and Convention of SLA

Chart of Accounts: This holds structure of accounting, for example Company, Department, Account, Sub-Account, Future 1, Future 2.

Currency : In which currency( USD, INR, CAD..) the transaction is happened.

Calendar : In order to capture the date of transaction, it is required to have calendar.

SLAC - Sub-Ledger Accounting Convention

There are different currencies that can be used for different purposes for transactions and reporting.
Below are few important currencies that are used for this purpose.
          Transnational Currency - An payment invoice currency that is raised for a supplier.
          Entered Currency - Journal entry currency that can be different than Transnational currency.
          Accounting Currency - A currency that is associated with ledger used for accounting.
          Secondary Ledger Currency - A secondary ledger associated with primary ledger used for reporting financial statements in an organization.
          Consolidated Ledger Currency -  A Primary ledger  used for reporting financial status to stock exchange or outer world.

Flex Fields Qualifier:

Qualifier assignment is mandatory for Company and Account  segments in Accounting Flex Fields, all other are non-mandatory.

Exchange Rate Types:

     Spot

     Corporate

     Period

Sub-Ledger Accounting (SLA) : SLA is user defined rule based accounting engine used by oracle products. It gives better control to the accounting department by having multiple currencies support, and generating various reports ( Inventory Valuation Report, Journal Entries Report, etc.,). Creating Accounting process enables user to see accounting entries of any transaction before it is transferred to GL.

Secondary-Ledger Conversions:  Below are the 4 types of Secondary Ledger Conversions.
      Sub-Ledger Level SL Conversion  -- When running 'Create Accounting' program
      Journal Level SL Conversion  - When Posting journals in Primary Ledger
      Balance Level SL Conversion - When Running 'Consolidation' in secondary ledger.
      Adjustment Level SL Conversion 

Below are important tables in General Ledgers.
GL_LEDGERS
GL_CODE_COMBINATIONS
GL_JE_HEADERS
GL_JE_LINES
GL_JE_BATCHES
GL_JE_CATEGORIES
GL_JE_SOURCES
GL_BALANCES

Queries:

Below query provides Ledgers, Legal Entities, Companies and OUs.

SELECT

       gl.ledger_id "Ledger ID",

       gl.name "Ledger Name",

       xep.legal_entity_id        "Legal Entity ID",

       xep.name                   "Legal Entity",

       gleb.flex_segment_value    "Company Code",

       hr_outtl1.name               "Organization Name",

       hr_outtl1.organization_id    "Organization ID",

       hla.location_id         "Location ID",

       hla.country             "Country Code",

       hla.location_code       "Location Code"

       

  FROM

       xle_entity_profiles            xep,

       xle_registrations              xr,

       hr_operating_units             hou,

       hr_all_organization_units_tl   hr_outtl1,

       hr_locations_all               hla,

       gl_legal_entities_bsvs         gleb,

       gl_ledgers gl

 WHERE

 xep.transacting_entity_flag   =  'Y'

   AND xep.legal_entity_id           =  xr.source_id

   AND xr.source_table              =  'XLE_ENTITY_PROFILES'

   AND xr.identifying_flag          =  'Y'

   AND xep.legal_entity_id           =  hou.default_legal_context_id

   AND xr.location_id               =  hla.location_id

   AND xep.legal_entity_id           =  gleb.legal_entity_id

   AND hr_outtl1.organization_id       =  hou.organization_id

   And hou.Set_Of_Books_Id=Gl.Ledger_Id

   ORDER BY 1,hr_outtl1.name;

TCA

Trading Community Architecture

The Trading Community Architecture holds information related to all trading partners with an organization, these are , Customers, Suppliers and Banks.

 Parties and Customers

In Oracle e-Business terminology a party is a person or organization that does not have customer account  called party, when a party posses customer account, that means it is eligible to to business with organization, is called customer. It is like, a person who is have account number in a bank able to do transaction called customer, without having an account number a person is merely a party to bank.

Customers are important entity or person who buy goods or services from an organization or business. In order to do business with customers, it is important to store their information in organization's system. The main entities of customers are Customer Account, Customer Account Sites, Customer Site Uses.

Below are the base tables relate to parties

HZ_PARTIES

HZ_PARTY_SITES

HZ_PARTY_SITE_USES

HZ_LOCATIONS

HZ_CONTACT_POINTS

HZ_RELATIONSHIPS

Creating a party and party sites is very straight forward which stores information into HZ_PARTIES,
HZ_PARTY_SITES, and HZ_PARTY_SITE_USES tables. But the contact points of customer( EMAIL/PHONE/URL) i
n TCA Architecture can be attached to different levels.
Party Directly
Party Relationship
Party Address(Site Level)

1.Party Directly:

When creating party, a record gets created in HZ_PARTIES, when creating contact to the party, the contact point created in HZ_CONTACT_POINTS, the OWNER_TABLE_ID in HZ_CONTACT_POINTS is PARTY_ID of HZ_PARTIES. The OWNER_TABLE_NAME is ‘HZ_PARTIES’.

2. Party Relationship

When creating a party the record gets created in HZ_PARTIES table.

Eg: NOMS HEALTHCARE

When creating a party contact  it create two records in HZ_PARTIES,

              Contact Person → 419-626-6161 SHELLY LINDENCAMP

              Relation between contact and party. → 419-626-6161 SHELLY LINDENCAMP-NOMS HEALTHCARE-701080.

Note: There are three parties created in HZ_PARTIES table.

It establishes relationship among these three parties in  HZ_RELATIONSHIPS table. In HZ_RELATIONSHIPS,

SUBJECT_ID → 419-626-6161 SHELLY LINDENCAMP

           PARTY_ID → 419-626-6161 SHELLY LINDENCAMP-NOMS HEALTHCARE-701080

           OBJECT_ID → NOMS HEALTHCARE

And, with PARTY_ID of HZ_RELATIONSHIPS is the OWNER_TABLE_ID in  HZ_CONTACT_POINTS which holds contact information of the party. The OWNER_TABLE_NAME is ‘HZ_PARTIES’.

3.Site Level

When creating contact point at site level, the OWNER_TABLE_ID of HZ_CONTACT_POINTS is PARTY_SITE_ID  of HZ_PARTY_SITES, and OWER_TABLE_NAME is ‘HZ_PARTY_SITES’.

Once party got customer account number and eligible to transact with organization, important information will be available under below tables.

HZ_PARTIES HZ_CUST_ACCOUNTS_ALL   ( PARTY_ID )

HZ_PARTY_SITES HZ_CUST_ACCT_SITES_ALL ( PARTY_SITE_ID,LOCATION_ID)

HZ_PARTY_SITE_USES HZ_CUST_SITE_USES_ALL

HZ_LOCATIONS

HZ_CONTACT_POINTS

HZ_RELATIONSHIPS

In order to create customers in Oracle e Business applications, either we can use APIs or Open Interfaces.

Below are the APIs used to create customer information in oracle e-Business Applications.

HZ_CUST_ACCOUNT_V2PUB.CREATE_CUST_ACCOUNT
HZ_LOCATION_V2PUB.CREATE_LOCATION
HZ_PARTY_SITE_V2PUB.CREATE_PARTY_SITE
HZ_CUST_ACCOUNT_SITE_V2PUB.CREATE_CUST_ACCT_SITE
HZ_CUST_ACCOUNT_SITE_V2PUB.CREATE_CUST_SITE_USE
HZ_CUSTOMER_PROFILE_V2PUB.CREATE_CUSTOMER_PROFILE
HZ_CUSTOMER_PROFILE_V2PUB.CREATE_CUST_PROFILE_AMT
HZ_CONTACT_POINT_V2PUB.CREATE_EMAIL_CONTACT_POINT
HZ_CONTACT_POINT_V2PUB.CREATE_PHONE_CONTACT_POINT
HZ_CONTACT_POINT_V2PUB.CREATE_EMAIL_CONTACT_POINT
HZ_PARTY_V2PUB.CREATE_PERSON
HZ_PARTY_CONTACT_V2PUB.CREATE_ORG_CONTACT
HZ_CUST_ACCOUNT_ROLE_V2PUB.CREATE_CUST_ACCOUNT_ROLE
HZ_CUST_ACCOUNT_ROLE_V2PUB.CREATE_ROLE_RESPONSIBILITY

Account Payables

In simple terms, account payable is paying amount for vendors for the goods or services received
and accounting/recording them correctly.A supplier is an individual or company who provide services
to an organization, in order to automate payments supplier’s information should be recorded in our
system.

Below are the the main entities in Account Payable:

Supplier and Supplier Sites               → These are shared entities to AP and PO.

Bank, Bank Branches, Bank Accounts → CE ( Cash Management )

Invoice and Payments. → AP, CE

Basically, a supplier holding a registered office at one place and can be operated at many places,
called supplier sites. And, obviously, he will be having contact points to outsiders to interact with them.
A supplier site can be designated as ‘Purchasing’, ‘Payment’,’RFQ only’ sites. In oracle applications, all
suppliers are global accessible and supplier sites are assigned to OUs.

‘Purchasing’ option enables site to select in purchasing for specific OU.

‘Payment’ option enables site to select in payables for specific OU.

‘RFQ Only’ option enables site to select for ‘RFQ’ in purchasing in specific OU.

These suppliers and supplier sites information can be created either manually, can import using API or open interfaces and self registration using iSupplier portal by suppliers. Below table provides information regarding API and Open Interface methods..

API and Open Interface:

Entity	Interface Tables	Open Interface Program	API	Base Tables
Suppliers	AP_SUPPLIERS_INT	Supplier Sites Open Interface	pos_vendor_pub_pkg.create_vendor	AP_SUPPLIERS
Supplier Sites	AP_SUPPLIER_SITES_INT	Supplier Sites Open Interface	pos_vendor_pub_pkg.create_vendor_site	AP_SUPPLIER_SITES_ALL
Supplier Contact	AP_SUP_SITE_CONTACT_INT	Supplier Sites Open Interface	ap_vendor_pub_pkg.create_vendor_contact	AP_SUPPLIER_CONTACTS

Flexible Self-Service Supplier Registration:

Using iSupplier portal any prospective supplier can register as a supplier in oracle e-Business. Any prospective supplier provide his information will be routed to administrator using AME (Approval Management Engine) which will be approved by administrator and created as supplier.

Below are some prerequisites to create a supplier.       
                            

S.No.	Setup	Comments
1	Supplier should not exist.	Verification
2	Lookup Values Supplier Type ,Pay Group,Minority Groups
3	Freight Carriers	If PO Installed.
4	Freight Terms	If PO Installed.
5	Define Financial Options
6	Define Payables System Setup
7	Define Payment Terms	Optional
8	Define Distribution Sets	Optional

The supplier information will be defaulted to supplier sites information, this supplier site defaults can be overwritten when entering supplier site information. Supplier sites information will be defaulted when entering invoices/transactions. If there is a null value at supplier site and not null value at supplier level, still the null value will get populated as default value when entering invoices/transactions.The supplier numbering can be controlled using 'Payables System Setup' form ( Navigation : Payables --> Setup --> Options --> Payables System Setup).

Invoices

When a supplier sends goods to buyer, supplier sends 'Invoice' and 'Goods Receipt Note' ( GRN ) along with goods. And invoice contains all goods and price information received from supplier, based on this buyer will pay amount to suppliers. A GRN is used to record delivery of items that is supplied by supplier.

There are various ways to create an invoice in oracle e-Business.

1. Open Invoice Import: Payables Open Interface program is used to import invoices from AP_INVOICES_INTERFACE and AP_INVOICE_LINES_INTERFACE tables, which will be stored at below base tables.

AP_INVOICES - Invoice Header Information.

AP_INVOICE_LINES_ALL - Invoice Lines Information.

AP_INVOICE_DISTRIBUTIONS_ALL - Invoice distributions(Accounts) information.

Entity	Interface Tables	Open Interface Program	Base Tables
Invoices	AP_INVOICES_INTERFACE	Payables Open Interface	AP_INVOICES
Invoice Lines	AP_INVOICE_LINES_INTERFACE	Payables Open Interface	AP_INVOICE_LINES_ALL

                                    

There are many ways to create payable invoice in oracle invoices.

1.Expense Report Export Program
2. Payables Open Interface Program
3.Manual Invoices
4.Internet Expense Reports
5. Payables expense Reports
6. EDI Invoices
7.XML Invoices
8.Invoices from legacy system
9.Property Managers.
10. Asset Leasing
11. Credit Card Agencies.

Below are the defaulting sequence of values in Oracle Payables, every lower level value overwrites the upper level value. For example, supplier site  withhold tax flag value will over writes supplier level withholding tas flag value.

                        Financial Options
                        Payables System Setup
                        Payables Options
                        Suppliers
                        Supplier Sites
                        Invoice Headers
                        Invoice Lines
                        Invoice Distributions


Below are the invoices types in oracle e-Business.

                        1. Standard
                        2. Credit Memo
                        3. Debit Memo
                        4. Expense Report
                        5. Withholding Tax
                        6. Prepayment
                        7. Mixed
1.Standard:

Below are the important tables in AP:

1) ap_invoices_all
2) ap_invoice_payments_all
3) ap_invoice_distibutions_All
4) ap_payment_schedules
5) ap_payment_distributions_all
6) ap_checks_all
7) ap_accounting_events_all
8) ap_bank_accounts_all
9) ap_bank_accounts_uses_all