Skip to main content

OE/OM to AR to GL Overview

OE/OM to AR to GL Overview
Oracle Order Entry (Order Management in R11i) is the starting point and main
processing module for the revenue stream in Oracle Financials. Sales orders are entered,
booked and shipped within Order Entry. Orders booked in OE represent the first
accessible revenue forecast in Oracle Financials. Booked orders may be considered as
expected or future revenue, though they are not treated as revenue in accounting terms
nor does OE send them directly to the GL for accounting purposes. In fact, they must
pass through several possible stages, like shipment and invoicing, before they are
considered revenue by Oracle Financials and thus available in the GL. Thus, revenue
managers relying solely on the GL for revenue figures will be disappointed by the
absence of “bookings” information and/or the lag time for shipped orders to make their
way into the GL as revenue

Comments

Popular posts from this blog

Applying Prepayments to Invoices

You can apply the available amount of Item type distributions from a Temporary type prepayment to one or more invoices to offset the amount you pay on the invoice(s). If you entered the prepayment as a Permanent type and want to apply it, you can query the prepayment in the Invoices window and change the Prepayment Type to Temporary. If you use Automatic Offsets then your setting for the Prevent Prepayment Application Across Balancing Segments Payables option controls whether you can apply a prepayment to an invoice or expense report with a different balancing segment. Prerequisites The invoice type is Standard, Mixed, or Expense Report. Today's date is on or after the Settlement Date of the prepayment. The invoice date is on or after the date of the prepayment. The prepayment is type Temporary, fully paid, validated, not cancelled, has no active holds, and has not already been fully applied. The prepayment has the same supplier, invoice currency and payment currenc...

Application Utilities Lookups and Application Object Library Lookups

Maintain existing and define additional Lookups for your shared Lookup types. You can define up to 250 Lookups for each Lookup type. Each Lookup has a code and a meaning. For example, Lookup type YES_NO has a code Y with meaning Yes, and a code N with a meaning No. Note: In Releases 11.0 and earlier, there were two Lookup features, Special Lookups and Common Lookups. These two features have been merged into one. The new consolidated Lookups feature has Lookups maintained in this form. If you make changes to a Lookup, users must log out then log back on before your changes take effect. Lookups Block Type Query the type of your Lookup. You can define a maximum of 250 Lookups for a single type. User Name The user name is used by loader programs. Application Query the application associated with your Lookup type. Description If you use windows specialized for a particular Lookup type, the window uses this description in the window title. Access Level The access level restricts changes that...

About Bank Reconciliation

The diagram in this section provides an overview of the Cash Management process, from entering bank statements to posting accounting entries to your general ledger. There are two major process steps you need to follow when reconciling bank statements: 1. Load Bank Statements: You need to enter the detailed information from each bank statement, including bank account information, deposits received by the bank, and payments cleared. You can enter bank statements manually or load electronic statements that you receive directly from your bank. (See: Entering Bank Statements Manually and Loading Bank Statement Open Interface ) 2. Reconcile Bank Statements: Once you have entered detailed bank statement information into Cash Management, you must reconcile that information with your system transactions. Cash Management provides two methods of reconciliation: Automatic--Bank statement details are automatically matched and reconciled with system transactions. This method is ideally suited for b...