Once the PO is received, order gets created either in ERP (Order Management) directly or imported from the legacy

tools. The Main tables on Order Management Application which holds the data for Order information are Oe_order_headers_all (header level information of the order) Oe_order_lines_all (line level information of the order) Once the order is booked after all the validations (booking validations), It undergoes various steps before getting interfaced to AR (Account Receivables) for invoicing. Booking Validations: 1) Credit Check Customer Credit is checked (at BID level/Customer level), if the order amount is less than the difference of Credit limit and Customer/BID Exposure i.e. (Credit limit - Customer/BID Exposure) it gets booked. 2) Customer Validation, If the Customer is active or not, order eligible to get booked if the customer is only active.

Once the order gets booked, it gets scheduled (based on the order request date), once scheduled, pick released and after this Order gets shipped.

Pick release to Shipping (this process is carried out under manufacturing); once manufacturing is done the data from Order Management is interfaced to Account Receivables for invoicing and status of the order gets closed. OM AR Interface tables on AR are ra_interface_lines_all header and line information of the order ra_interface_salescredits_all sales credit information of the order ra_interface_distributions_all line account distribution ra_interface_errors_all AR Interface Error Information Now the Auto Invoice process runs on AR which creates the Invoices and populates the bases tables on AR. ra_customer_trx_all Header information of the invoice ra_customer_trx_lines_all Line information of the invoice ra_cust_trx_line_gl_dist_all Distribution (account) information of the invoices. Auto Accounting (as part of auto invoice) is the main process (heart of AR) which decides which account to be hit when the invoices are generated, generally the revenue accounts are derived (as shown below) from the accounts which are setup at the Item level Autoinvoice uses auto accounting to decide the periods in which the revenue has to be recognized, generally product invoices are recognized immediately and Service invoices are recognized over a period of time (amortization) Services are offered over a period of time; hence the revenue is also recognized over a period of time and is posted to GL in different periods.

Once the revenue recognition is done as part of GL transfer, GL posting is run which will post the entries to GL. Interface table on GL is (gl_interface) Main tables on GL are Gl_je_batches Gl_je_headers Gl_je_lines Once the Invoices are generated, they are sent to customers for payments, customer makes payment in the form of cash/check/wire. Lockbox is the provision provided by the bank where in the customer can direct the payments to Organization for all the invoices at one go, customer provides the details of the invoices to which the payments are been made, bank prepares the transmission file (payment file) and sends to Organization which uses Oracle Lockbox functionality to import the payments by automatically creating the receipts and applies to various mentioned invoices and closes them. Other important tables on AR are, Ar_payment_schedules_all, which stores the information about the payment schedules of the invoices, the payment schedule is derived based on the payment terms used on the order (decides the due date before which customer is expected to pay the invoices) Ar_cash_receipts_all. This tables stores the information about the receipts which gets created upon the customer payments, the receipts are applied to invoices/debit memos to close them Ar_cash_receipt_history_all, stores the status of the receipts, like CONFIRMED and CLEARED, REMITTED and REVERSED Ar_receivable_applications_all, this tables stores the application information like which receipt is applied to what invoice etc. The receipt information gets posted to GL, the data from ar_cash_receipt_history_all gets posted. Basic flow OM ARGL