Oracle Financials Glossary of Terms


	Previous	Next		Contents	Library

COMMON GLOSSARY

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

This combined glossary defines terms we use in the Assets, Cash Management, General Ledger, Payables, Projects, and Receivables User's Guides and in various country-specific and region-specific manuals.

4-4-5 calendar: A depreciation calendar with 12 uneven periods: four cycles of a four-week period, followed by a four-week period, followed by a five-week period. Depreciation is usually divided by days for a 4-4-5 calendar. Since a 4-4-5 calendar has 364 days per year, it has different start and end dates for the fiscal year each year.

1099 form: The forms the Internal Revenue Service supplies to record a particular category of payment or receipt.

1099 number: The tax identification number for a supplier. According to IRS rules in the United States, lack of a valid tax identification number may result in tax withholding.
Oracle Applications stores the tax identification number for each supplier. Oracle Applications also enables you to enter a withholding status for each supplier.

1099 types: A 1099 classification scheme used in the United States for types of payments. Each 1099 form has one or more payment types. A 1099 supplier may receive payments from more than one type. The 1099-MISC form has the following types: rents, royalties, prizes and awards, federal income tax withheld, fishing boat proceeds, medical and health care payments, non-employee compensation, and substitute payments in lieu of dividends or interest.
Oracle Applications records 1099 payments by type so that you can report them according to IRS requirements.

2-way matching

The process of verifying that purchase order and invoice information matches within accepted tolerance levels. Oracle Applications uses the following criteria to verify two-way matching:
Invoice price <= Order price
Quantity billed <= Quantity ordered

See also matching.

24-hour format: A time format that uses a 24 hour clock instead of am and pm, so that 3:30 would be 3:30 am, 16:15 would be 4:15 pm, 19:42 would be 7:42 pm, etc.

3-way matching

The process of verifying that purchase order, invoice, and receiving information matches within accepted tolerance levels. Oracle Applications uses the following criteria to verify three-way matching:
Invoice price <= Purchase Order price
Quantity billed <= Quantity ordered
Quantity billed <= Quantity received

See also matching.

4-way matching

The process of verifying that purchase order, invoice, and receiving information matches within accepted tolerance levels. Oracle Applications uses the following criteria to verify four-way matching:
Invoice price <= Order price
Quantity billed <= Quantity ordered
Quantity billed <= Quantity received
Quantity billed <= Quantity accepted

See also matching.

A

accepted quantity: The quantity of inventory items received from a customer, based on a return authorization for which you credit the customer. See also received quantity.

account hierarchy: An Oracle Financials feature you use to perform summary level funds checking. An account hierarchy lets Oracle Purchasing and Oracle Applications quickly determine the summary accounts into which your detail accounts roll up.

Account segment

One of up to 30 different sections of your Accounting Flexfield, which together make up your general ledger account code. Each segment is separated from the other segments by a symbol you choose (such as -, /, or \). Each segment typically represents an element of your business structure, such as Company, Cost Center or Account.

Account segment value: A series of characters and a description that define a unique value for a particular value set.

account structure: See Accounting Flexfield structure.

accounting calendar: The calendar that defines your accounting periods and fiscal years in Oracle General Ledger. You define accounting calendars using the Accounting Calendar window. Oracle Financial Analyzer will automatically create a Time dimension using your accounting calendar.

Accounting Flexfield: The code you use to identify a general ledger account in an Oracle Financials application. Each Accounting Flexfield segment value corresponds to a summary or rollup account within your chart of accounts.

Accounting Flexfield structure: The account structure you define to fit the specific needs of your organization. You choose the number of segments, as well as the length, name, and order of each segment in your Accounting Flexfield structure.

Accounting Flexfield value set

A group of values and attributes of the values. For example, the value length and value type that you assign to your account segment to identify a particular element of your business, such as Company, Division, Region, or Product.

accounting method: The method you select for recording accounts payable transactions. You can choose between accrual basis, cash basis, or combined basis of accounting. With accrual basis accounting, Oracle Applications creates journal entries for invoices and payments. With cash basis accounting, Oracle Applications creates journal entries only after you make payments. With combined basis accounting, Oracle Applications creates journal entries for invoices and payments to post to your accrual set of books and creates journal entries for payments to post to your cash set of books.

accounting period: The periods which make up your fiscal year. You depreciate assets each period.

accounting rule start date

The date Oracle Receivables uses for the first accounting entry it creates when you use an accounting rule to recognize revenue.

If you choose a variable accounting rule you need to specify a rule duration to let Oracle Receivables know how many accounting periods to use this accounting rule.

accounting rules: Rules that Oracle Payables AutoInvoice uses to specify revenue recognition schedules for your transactions. You can define an accounting rule where revenue is recognized over a fixed or variable period of time. For example, you can define a fixed duration accounting rule with monthly revenue recognition for a period of 12 months.

accrual accounting: An accounting method you use to recognize revenue when you create invoices.

accrual basis of accounting: A method of accounting in which you recognize revenues in the accounting period you earn revenues and recognize expenses in the accounting period in which you incur the expense. Both revenues and expenses need to be measurable to be reportable.

accrue through date

The date through which to accrue revenue for a project. Oracle Projects picks up expenditure items having an expenditure item date on or before this date, and events having a completion date on or before this date, when accruing revenue. An exception to this rule are projects that use cost-to-cost revenue accrual; in this case, the accrue through date used is the PA Date of the expenditure item's cost distribution lines.

accumulation: An obsolete term. See also summarization.

accumulated depreciation: The total depreciation taken for an asset since it was placed in service. Also known as life-to-date depreciation and depreciation reserve.

ACE: See adjusted current earnings.

ACE book: A tax book for Adjusted Current Earnings ("ACE") tax calculations.

action: See cycle action.

action result: A possible outcome of an order cycle action. You can assign any number of results to a cycle action. Combinations of actions/results are used as order cycle action prerequisites. See also order cycle, cycle action.

address validation: The type of validation you want the system to use for your address, if you are not using a flexible address format for validation. You can implement address validation at three levels: Error, No Validation, or Warning. 'Error' ensures that all locations exist for your address before it can be saved. 'Warning' displays a warning message if a tax rate does not exist for this address (allows you to save the record). 'No Validation' does not validate the address.

adjusted current earnings ("ACE"): A set of depreciation rules defined by United States tax law. Oracle Assets supports the Adjusted Current Earnings tax rules.

adjustment: An Oracle Applications feature that allows you to increase or decrease the amount due of your invoice, debit memo, chargeback, deposit or guarantee. Oracle Applications lets you create manual or automatic adjustments.

advance

An amount of money prepaid in anticipation of receipt of goods, services, obligations or expenditures. In Oracle Payables, an advance is a prepayment paid to an employee. You can apply an advance to an employee expense report during expense report entry, once you fully pay the advance.

aggregate balance: The sum of the end-of-day balances for a range of days. There are three types of aggregate balances: period-to-date (PTD), quarter-to-date (QTD), and year-to-date (YTD). All three are stored in the General Ledger database for every calendar day.

agent: The customer name or supplier name on a bank statement line.

aging buckets

Time periods you define to age your debit items. Aging buckets are used in Aged Trial Balance reports to see both current and outstanding debit items. For example, you can define an aging bucket that includes all debit items that are 1 to 30 days past due.

Oracle Applications uses the aging buckets you define for its Invoice Aging Report.

agreement

A contract with a customer which serves as the basis for work authorization. An agreement may represent a legally binding contract, such as a purchase order, or a verbal authorization. An agreement sets the terms of payment for invoices generated against the agreement, and affects whether there are limits to the amount of revenue you can accrue or bill against the agreement. An agreement can fund the work of one or more projects.

An arrangement with a customer that sets business terms for sales orders in advance. Oracle Order Entry lets you assign pricing, accounting, invoicing, and payments terms to an agreement. You can assign discounts to agreements that are automatically applied. You can refer to an agreement when you enter an order for a particular customer, and have relevant default values automatically fill in the order using standard value rule sets. See also customer family agreement, generic agreement.

agreement type: A classification for agreements. Reference agreement types in defining discounts or automatic note rules, classify your agreements to control selection of agreements during order entry, as well as for reporting purposes. (Order Entry QuickCode)An implementation-
defined classification of agreements. Typical agreement types include purchase order and service agreement.

alert: An entity you define that checks your database for a specific condition and sends or prints messages based on the information found in your database.

alert input: A parameter that determines the exact definition of the alert condition. You can set the input to different values depending upon when and to whom you are sending the alert. For example, an alert testing for users to change their passwords uses the number of days between password changes as an input. Oracle Alert does not require inputs when you define an alert.

alert output: A value that changes based on the outcome at the time Oracle Alert checks the alert condition. Oracle Alert uses outputs in the message sent to the alert recipient, although you do not have to display all outputs in the alert message.

allocation entry: A recurring journal entry you use to allocate revenues or costs.

alternative region: An alternative region is one of a collection of regions that occupy the same space in a window where only one region can be displayed at any time. You identify an alternative region by a poplist icon that displays the region title, which sits on top of a horizontal line that spans the region.

Always Take Discount: An Oracle Applications feature you use to always take a discount on a supplier's invoice if the payment terms for the invoice include a discount. You define Always Take Discount as a system default that Oracle Applications assigns to new suppliers you enter. When Always Take Discount is Yes for a supplier site, you take a discount on that supplier's invoice site regardless of when you pay the invoice. When Always Take Discount is No, you only take a discount if you pay the invoice on or before the discount date.

applied: Payment in which you record the entire amount as settlement for one or more debit items.

approval action: A cycle action that you can define in your order cycle to require explicit approval of an order or order line before that order or line progresses further through the order cycle. You can define an approval step at the order or order line level. When you define an approval step, you must approve all orders or order lines using that order cycle, depending on the approval step level. You can also use approvals in order cycles for returns (RMAs). See also configure-to-order.

approval limits: Limits you assign to users for adjustment entry. Oracle Applications enforces the limits that you define here as your users enter receivables adjustments. When users enter adjustments that are within their approval limit, Oracle Applications automatically approves the adjustment. When users enter adjustments outside their approval limit, Oracle Applications assigns a status of pending to the adjustment.

approved date: The date on which an invoice is approved.

archive: To archive a fiscal year is to copy the depreciation expense and adjustment transaction data for that year to a storage device.

archive: To store historical transaction data outside your database.

archive table

Oracle Applications copies your account balances from the Balances Table (GL_BALANCES) to your Archive Table (GL_ARCHIVE_BALANCES). Oracle Applications copies your journal details from the Journal Entry tables (GL_JE_BATCHES, GL_JE_HEADERS, and GL_JE_LINES) to your archive tables (GL_ARCHIVE_BATCHES, GL_ARCHIVE_HEADERS, and GL_ARCHIVE_LINES).

Oracle Assets copies depreciation expense and adjustment transaction data for a fiscal year to temporary tables called archive tables.

archive tablespace: The tablespace where your archive table is stored. A tablespace is the area in which an Oracle7 database is divided to hold tables.

attribute: An Oracle Financial Analyzer database object that links or relates the values of two dimensions. For example, you might define an attribute that relates the Sales District dimension to the Region dimension so that you can select data for sales districts according to region.

assemble-to-order (ATO): An environment where you open a final assembly order to assemble items that customers order.

assemble-to-order (ATO) item: An item you make in response to a customer order.

assemble-to-order (ATO) model: A configuration you make in response to a customer order that includes optional items.

assembly: An item that has a bill of material. You can purchase or manufacture an assembly item. See also assemble-to-order, bill of material.

asset

An object of value owned by a corporation or business. Assets are entered Oracle Projects as non-labor resources. See non-labor resource.

See fixed asset.

asset account: A general ledger account to which you charge the cost of an asset when you purchase it. You must define an account as an asset account.

Asset Key Flexfield: Oracle Assets lets you define additional ways to sort and categorize your assets without any financial impact. You use your Asset Key Flexfield to define how you want to keep the information.

assignment: A rule governing how FlexBuilder fills in your key flexfield segments. Oracle Applications usually provides default assignments, and you can define additional assignments or modify the default, depending on the application. You assign parameters to key flexfield segments. You can assign one parameter to an entire key flexfield structure, or several different parameters to individual segments of a key flexfield structure. You can also assign a constant value to a key flexfield segment. Assignments can be conditional on parameter values. See also derived parameter, function, parameter (FlexBuilder), raw parameter.

ATO: See assemble-to-order.

ATO item: See assemble-to-order (ATO) item.

ATO Model: See assemble-to-order (ATO) model.

ATP: See available to promise.

ATR: See available to reserve.

attribute: A field (or database column), usually associated with the Enter Orders form that you can define security rules for, default information to, or which you could use as a source for a default value for another field or attribute. An example is Price List. See also default value, object, security rules, standard value.

Audit Set: The group of forms that are available for auditing in your application.

AutoAccounting

A feature used by Oracle Projects to automatically determine the account coding for an accounting transaction based on the project, task, employee, and expenditure information.

An Oracle Payables feature that lets you determine how the Accounting Flexfields for your revenue, receivable, freight, tax, unbilled receivable and unearned revenue account types are created

AutoAccounting function: A group of related AutoAccounting transactions. There is at least one AutoAccounting function for each Oracle Projects process that uses AutoAccounting. AutoAccounting functions are predefined by Oracle Projects.

AutoAccounting Lookup Set: An implementation-defined list of intermediate values and corresponding Accounting Flexfield segment values. AutoAccounting lookup sets are used to translate intermediate values such as organization names into account codes.

AutoAccounting parameter: A variable that is passed into AutoAccounting. AutoAccounting parameters are used by AutoAccounting to determine account codings. Example AutoAccounting parameters available for an expenditure item are the expenditure type and project organization. AutoAccounting parameters are predefined by Oracle Projects.

AutoAccounting Rule: An implementation-defined formula for deriving Accounting Flexfield segment values. AutoAccounting rules may use a combination of AutoAccounting parameters, AutoAccounting lookup sets, SQL statements, and constants to determine segment values.

AutoAccounting Transaction: A repository of the account coding rules needed to create one accounting transaction. For each accounting transaction created by Oracle Projects, the necessary AutoAccounting rules are held in a corresponding AutoAccounting Transaction. AutoAccounting transactions are predefined by Oracle Projects.

AutoAdjustment: An Oracle Applications feature used to automatically adjust the remaining balances of your invoices, debit memos, and chargebacks that meet the criteria that you define.

AutoApproval: An Oracle Applications feature which prevents you from paying an invoice when your supplier overcharges you or bills you for items you have not received, ordered or accepted. AutoApproval also validates tax, period, currency, budgetary, and other information. If you use budgetary control and encumbrance accounting, AutoApproval also creates encumbrances for unmatched invoices or for invoice variances.
AutoApproval prevents payment or posting of invoices that do not meet defined approval criteria by placing holds on the invoice. AutoApproval also releases holds when you resolve invoice exceptions. You must submit AutoApproval for each invoice to pay and post the invoice.

AutoAssociate: An option that allows you to specify whether you want Oracle Applications to determine the customer using invoice numbers if the customer cannot be identified from either the MICR number or the customer number. Oracle Applications checks the invoice numbers until they find a unique invoice number for a customer. Oracle Applications then uses this invoice number to identify the customer. You can only use this feature if your bank transmits invoice numbers, and if the AutoLockbox Validation program can identify a unique customer for a payment using an invoice number. Otherwise, Oracle Applications treats the payment as unidentified.

AutoCash Rule: An Oracle Applications feature that automatically applies receipts to a customer's open items according to the AutoCash rule set that you define. AutoCash Rules include: Apply to the Oldest Invoice First, Clear the Account, Clear Past Due Invoices, Clear Past Due Invoices Grouped by Payment Term, and Match Payment with Invoice.

AutoCash Rule Set: An Oracle Applications feature used to determine the order of the AutoCash Rules that you want Oracle Applications to use. You also have the option to include discounts, finance charges, and in dispute items in your customer's open balance.

AutoClear: An Oracle Applications feature you use to automatically reconcile your bank account with your payment history in Oracle Applications. You load bank reconciliation information from a tape or diskette and Oracle Applications verifies that your bank information is complete and accurate, then updates your payment history.

AutoReconciliation: A feature of Oracle Cash Management that allows you to reconcile bank statements automatically.

available transactions: Receivables and payables transactions that are available to be reconciled by Cash Management.

AutoCopy - budget organizations: An Oracle Applications feature that automatically creates a new budget organization by copying account assignments from an existing budget organization.

AutoCopy - budgets: An Oracle Applications feature that automatically creates a new budget by copying all of the data from an existing budget. Budget AutoCopy copies budget amounts only from open budget years.

AutoEntry: An Oracle Applications feature which provides user-defined defaults during various phases of data entry to simplify entry. With AutoEntry, you can often enter only a few fields when entering invoices or initiating a payment batch.

AutoInvoice: A program that imports invoices, credit memos, and on account credits from other systems to Oracle Payables.

automatic event: An event with an event type classification of Automatic. Billing extensions create automatic events to account for the revenue and invoice amounts calculated by the billing extensions.

automatic asset numbering: Oracle Applications automatically numbers your assets if you do not enter an asset number.

automatic note: A standard note that you assign automatic application rules to so that it can be applied automatically to orders, returns, order lines and return lines. See also one-time note, standard note.

automatic payment: An Oracle Applications process which automatically selects invoices based on your selection criteria, creates a payment (check or electronic funds transfer), and confirms the status of each payment.

automatic payment processing: An Oracle Applications process which produces payments for groups of invoices. The complete process includes: invoice selection (payment batch), payment building, manual modification/addition to invoice payments in the payment batch, payment formatting, and confirmation of results. You can modify a payment batch up until the time you format payments for the payment batch. You can cancel a payment batch up until the time you confirm the payment batch.

automatic receipt: In addition to standard check processing, you can use the automatic receipt feature to automatically generate receipts for customers with whom you have predefined agreements. These agreements you transfer funds from the customer's bank account to yours on the receipt maturity date.

AutoOffset: An Oracle Applications feature that automatically determines the offset (or credit) entry for your allocation entry. AutoOffset automatically calculates the net of all previous journal lines in your allocation entry, reverses the sign, and generates the contra amount.

AutoReduction: A feature in the list window that allows you to shorten a list so that you must scan only a subset of values before choosing a final value. Just as AutoReduction incrementally reduces a list of values as you enter additional character(s), pressing [Backspace] incrementally expands a list.

AutoSelection: A feature in the list window that allows you to choose a valid value from the list with a single keystroke. When you display the list window, you can type the first character of the choice you want in the window. If only one choice begins with the character you enter, AutoSelection selects the choice, closes the list window, and enters the value in the appropriate field.

AutoSkip: A feature specific to flexfields where Oracle Applications automatically moves your cursor to the next segment as soon as you enter a valid value into a current flexfield segment. You can turn this feature on or off with the user profile option Flexfields:AutoSkip.

average balance: The amount computed by dividing an aggregate balance by the number of calendar days in the related range.

available to promise (ATP): The quantity of current on-hand stock, outstanding receipts and planned production that has not already been committed, either through a reservation or placing demand. In Oracle Inventory, you define the types of supply and demand that should be included in your ATP calculation.

available-to-promise quantity: See available to promise (ATP).

available-to-promise rule: A set of Yes/No options for various entities that the user enters in Oracle Inventory. The combination of the various entities are used to define what is considered supply and demand when calculating available to promise quantity.

Available-to-reserve (ATR): The quantity of on-hand stock that is available for reservation. ATR is the current on-hand stock less any reserved stock.

average exchange rate

An exchange rate that is the average rate for an entire accounting period. Oracle General Ledger automatically translates revenue and expense account balances using period-average rates in accordance with FASB 52 (U.S.). And, for companies in highly inflationary economies, Oracle General Ledger uses average exchange rates to translate your non-historical revenue and expense accounts in accordance with FASB 8 (U.S.). Also known as period-average exchange rate.

B

back-value transactions: Transactions whose effective date is prior to the current accounting date. Also known as value-dated transactions.

B-record: A summary record of all 1099 payments made to a supplier for one tax region.

backorder: An unfulfilled customer order or commitment. Oracle Order Entry allows you to create backorders either automatically or manually from released order lines. See also Pick Release.

BACS: See Bankers Automated Clearing System.

BAI: An acronym for the Banking Administration Institute. This organization has recommended a common format that is widely accepted for sending lockbox data. If your bank provides you with this type of statement, you can use Bank Statement Open Interface to load your bank statement information into Oracle Cash Management.See alsoBank Statement Open Interface bank statement

balances table: An Oracle Applications database table that stores your account balances, called GL_BALANCES.

balancing segment

An Accounting Flexfield segment that you define so that Oracle General Ledger automatically balances all journal entries for each value of this segment. For example, if your company segment is a balancing segment, Oracle General Ledger ensures that, within every journal entry, the total debits to company 01 equal the total credits to company 01.

bank file: The bank file is the data file you receive from the bank which contains all of the payment information that the bank has deposited in your bank account.

bank statement: A report sent from a bank to a customer showing all transaction activity for a bank account for a specific period of time. Bank statements report beginning balance, deposits made, checks cleared, bank charges, credits, and ending balance. Enclosed with the bank statement are cancelled checks, debit memos, and credit memos. Large institutional banking customers usually receive electronic bank statements as well as the paper versions.

bank statement tables: The primary database tables Oracle Cash Management works with for each bank statement. Bank statement tables are populated manually or by importing data from Bank Statement Open Interface. There are two tables for each bank statement--a bank statement headers table and a bank statement lines table. See also bank statement

Bank Statement Open Interface: The database interface tables that must be populated when you want to load an electronic bank file into Oracle Cash Management. The Bank Statement Open Interface consists of one header and multiple detail lines for each bank statement.

bank transaction code: The transaction code used by a bank to identify types of transactions on a bank statement, such as debits, credits, bank charges, and interest. You define these codes for each bank account using the Cash Management Bank Transaction Codes window.

Bankers Automated Clearing System (BACS): The standard format of electronic funds transfer used in the United Kingdom. You can refer to the BACS User Manual, Part III: Input Media Specifications, published by the Bankers Automated Clearing System, for the exact specifications for BACS electronic payments.

base amount: The amount that represents the denominator for the ratio used to determine the amount due. You specify your base amount when you define your payment terms.

Amount Due = Relative Amount/Base Amount * Invoice Amount

base model: The model item from which a configuration item was created.

baseline budget: The authorized budget for a project or task which is used for performance reporting and revenue calculation. A project's baseline budget is created by copying the draft budget when the project is baselined.

basis reduction rate: Each Investment Tax Credit Rate has a basis reduction rate associated with it. Oracle Assets applies the basis reduction rate to the ITC basis to determine the amount by which it will reduce the depreciable basis. Oracle Assets displays the basis reduction rate with its corresponding investment tax credit rate in the Assign Investment Tax Credit form so you can easily see whether the rate you choose will reduce the depreciable basis of the asset.

batch sources: A source you define in Oracle Receivables to identify where your invoicing activity originates. The batch source also controls invoice defaults and invoice numbering. Also known as invoice batch sources.

beginning balance: The beginning balance is the balance of the transaction item as of the beginning GL Date that you have specified. This amount should be the same as the Outstanding Balance amount of the Aged Trial Balance - 7 Buckets Report where the As Of Date is the same as the beginning GL Date.

best discount: The most advantageous discount for the customer. For example, you have a customer discount of 15% and a item discount of 25% for Product B. If you enter an order line for the customer for Product A, the line is discounted 15%. If you enter an order line for the customer for product B, the line is discounted 25%.

bill in advance: An invoicing rule that enables you to recognize your receivable immediately for invoices that span more than one accounting period.

bill in arrears: An invoicing rule that enables you to recognize the receivable at the end of the revenue recognition schedule for invoices that span more than one accounting period.

Bill of Exchange

A method of payment. Also known as a future dated payment in some countries, including France. See also Future Date Payment.

An agreement made with your customer promising to pay you a specified amount on a specific date (called the maturity date). This process involves the transfer of funds from your customer's bank account to your bank account.

Bill of Lading: A carrier's contract and receipt of goods transported from one location to another.

bill of material: (BOM) A listing of all the subassemblies, intermediates, parts, and raw materials that go into a parent assembly or product configuration. It shows the quantity of each part required to make an assembly. You may think of a bill of material as a recipe or formula for a configuration. Oracle Order Entry uses a bill of material format to define configurations. See also configuration, model.

bill rate

A rate per unit at which an item accrues revenue and/or is invoiced for time and material projects. Employees, jobs, expenditure types, and non-labor resources can have bill rates.

bill rate schedule

A set of standard bill rates that maintains the rates and percentage markups over cost that you charge clients for your labor and non-labor expenditures.

bill site: The customer address to which project invoices are sent.

bill through date: The date through which to invoice a project. Oracle Projects picks up revenue distributed expenditure items having an expenditure item date on or before this date, and events having a completion date on or before this date, when generating an invoice.

Bill To Address: The address of the customer who is to receive the invoice. Equivalent to Invoice To Address in Oracle Order Entry.

Bill To Site: A customer location to which you have assigned a Bill-To business purpose. You can define your customer's bill-to sites in the Customers windows.

business purpose

The business reason you have for communicating with a customer's address. For example, you would assign the business purpose of Ship To to an address if you ship to that address. If you also send invoices to that address, you could also assign the business purpose Bill To.

Bill To and Ship To are the only business purposes recognized in Oracle Order Entry. (Receivables QuickCode)

billing

The functions of revenue accrual and invoicing.

billing cycle

A negotiated cycle, measured in days, by which Time and Materials project invoices are generated for a customer.

billing cycle days

The interval between each invoice, measured by days. Billing cycle days are used to determine when a draft invoice should be automatically created for a project and sent to a customer.

billing title: See Employee Billing Title, Job Billing Title.

block: Every Oracle Applications window (except root and modal windows) consists of one or more blocks. A block contains information pertaining to a specific business entity Generally, the first or only block in a window assumes the name of the window. Otherwise, a block name appears across the top of the block with a horizontal line marking the beginning of the block.

book: See depreciation book.

booking: An action on an order signifying that the order has all the necessary information to be a firm order and processed through its order cycle.

Borrowed and Lent revenue: A revenue entry that is created to record when an employee works on a project that is managed by a different organization than the expenditure organization. This revenue entry is created to separately track project organization revenue versus employee organization revenue.

budget

Estimated cost, revenue, labor hours or other quantities for a project or task. Each budget may optionally be categorized by resource. Different budget types may be set up to classify budgets for different purposes. In addition, different versions can exist for each user-defined budget type: current, original, revised original, and historical versions. The current version of a budget is the most recently baselined version.

See also budget line, cost breakdown category.

resource

budget book: A book that you use to track planned capital expenditures.

budget formula: A mathematical expression used to calculate budget amounts based on actual results, other budget amounts and statistics. With budget formulas, you can automatically create budgets using complex equations, calculations and allocations.

budget hierarchy: A group of budgets linked at different levels such that the budgeting authority of a lower-level budget is controlled by an upper-level budget.

budget interface table

An Oracle Applications database table that stores information needed for budget upload.

The interface table from which Oracle Assets uploads budget information.

budget line

Estimated cost, revenue, labor hours, or other quantity for a project or task categorized by a cost breakdown category.

budget organization

An entity (department, cost center, division or other group) responsible for entering and maintaining budget data. You define budget organizations for your company, then assign the appropriate accounts to each budget organization.

budget rules: A variety of shorthand techniques you can use to speed manual budget entry. With budget rules you can divide a total amount evenly among budget periods, repeat a given amount in each budget period or enter budget amounts derived from your account balances.

budget upload

The ability to transfer budget information from a spreadsheet to Oracle Applications. For example, with the spreadsheet interface you can upload budget information from your spreadsheet to Oracle Applications.

The process by which Oracle Assets loads budget information from the Budget Interface table into the Budget worksheet. You can use the Budget Upload process to transfer budget information from a feeder system, such as a spreadsheet, to Oracle Assets.

budget worksheet: Oracle Assets holds your budget in the budget worksheet so that you can review and change it before you load it into your budget book. Your budget must be in a budget book before you can run depreciation projections or reports.

budgetary account: An account segment value (such as 6110) that is assigned one of the two budgetary account types. You use budgetary accounts to record the movement of funds through the budget process from appropriation to expended appropriation.

Budgetary Account: An account that contains a budgetary account.

budgetary account type: Either of the two account types Budgetary DR and Budgetary CR.

budgetary control: An Oracle Financials feature you use to control actual and anticipated expenditures against a budget. When budgetary control is enabled, you can check funds online for transactions, and you can reserve funds for transactions by creating encumbrances. Oracle Financials automatically calculates funds available (budget less encumbrances less actual expenditures) when you attempt to reserve funds for a transaction. Oracle Financials notifies you online if funds available are insufficient for your transaction.

burden cost code

An implementation-defined classification of overhead costs. A burden cost code represents the type of burden cost you want to apply to raw cost. For example, you can define a burden cost code of G&A to burden specific types of raw costs with General and Administrative overhead costs.

business day: Days on which financial institutions conduct business. In General Ledger, you choose which days of the calendar year are defined as business days. You can include or exclude weekends and holidays as needed.

burden costs

Burden costs are legitimate costs of doing business that support raw costs and cannot be directly attributed to work performed. Examples of burden costs are fringe benefits, office space, and general and administrative costs.

burden multiplier

A numeric multiplier associated with an organization for burden schedule revisions, or with burden cost codes for projects or tasks. This multiplier is applied to raw cost to calculate burden cost amounts. For example, you can assign a multiplier of 95% to the burden cost code of Overhead

burden schedule

An implementation-defined set of burden multipliers that is maintained for use across projects. Also referred to as a standard burden schedule. You may define one or more schedules for different purposes of costing, revenue accrual, and invoicing. Oracle Projects applies the burden multipliers to the raw cost amount of an expenditure item to derive an amount; this amount may be the total cost, revenue amount, or bill amount. You can override burden schedules by entering negotiated rates at the project and task level. See Also: Firm Schedule, Provisional Schedule, Burden Schedule Revision, Burden Schedule Overrides.

burden schedule override: A schedule of negotiated burden multipliers for projects and tasks that overrides the schedule you defined during implementation.

burden schedule revision

A revision of a set of burden multipliers. A schedule can be made of many revisions.

burden structure

A burden structure determines how cost bases are grouped and what types of burden costs are applied to the cost bases. A burden structure defines relationships between cost bases and burden cost codes and between cost bases and expenditure types.

burdened cost

The cost of an expenditure item, including raw cost and burden costs.

business entity: A person, place, or thing that is tracked by your business. For example, a business entity can be an account, a customer, or a part.

Business group: The highest level of organization and the largest grouping of employees across which a company can report. A business group can correspond to an entire company, or to a specific division within the company. Each installation of Oracle Projects uses one business group with one hierarchy.

button: You choose a button to initiate a predefined action. Buttons do not store values. A button is usually labeled with text to describe its action or it can be an icon whose image illustrates its action.

C

calculated depreciation method: A depreciation method that uses the straight-line method to calculate depreciation based on the asset life and the recoverable cost.

call actions: Actions that you record and plan to take as a result of a call with a customer. Examples of actions that you might note for future reference include creating a credit memo, excluding a customer from dunning, or alerting another member of your staff of an escalated issue.

call topics: Each call may have many points or topics of discussion. Examples include invoice, debit memo, invoice lines, and customer problems.

cancellation code: A reason that justifies the cancellation of an order or order line. To cancel an order you must enter a cancellation code to record why the customer wants to nullify the order or order line. (Order Entry QuickCode)

candidate: A record which Oracle Applications selects to purge based on the last activity date you specify. Oracle Applications only selects records which you have not updated since the last activity date you specify. Oracle Applications does not purge a candidate until you confirm a purge.

capital gain threshold: The minimum time you must hold an asset for Oracle Applications to report it as a capital gain when you retire it. If you hold an asset for at least as long as the capital gain threshold, Oracle Applications reports it as a capital gain when you retire it. If you hold the asset for less than the threshold, Oracle Applications reports it as an ordinary income from the retirement.

capitalized assets: Capitalized assets are assets which you depreciate (spread the cost expense over time). The Asset Type for these assets is "Capitalized".

capital project: A project in which you build one or more depreciable fixed assets.

carrier: See freight carrier.

cash basis: An accounting method you use to recognize revenue at the time you receive payment for an invoice.

cash basis of accounting: An accounting method in which you only recognize an expense when you incur the expense. With the Cash Basis of Accounting, Oracle Applications only creates journal entries for invoice payments.

Cash Clearing Account: The cash clearing account you associate with a payment document. You use this account if you integrate Oracle Payables with Oracle Cash Management, or if you generate future dated payment documents. Oracle Payables credits this account instead of your Asset (Cash) account and debits your Liability account when you post uncleared payments. Oracle Payables debits this account and credits your Asset (Cash) account once you clear your payments in Oracle Cash Management. You must enable the Allow Reconciliation Accounting Payables option to be able to enter a cash clearing account for a bank account and payment document.

category

See Item Category.

An Oracle Applications feature you use to purge a particular group of records from the database.

Oracle Applications lets you choose from 5 separate categories: Suppliers Simple Invoices Simple Requisitions (only if you installed Oracle Purchasing) Simple Purchase Orders (only if you installed Oracle Purchasing) Matched Invoices and POs (only if you installed Oracle Purchasing)

category flexfield: Oracle Assets lets you group your assets and define what descriptive and financial information you want to keep about your asset categories. You use your Category Flexfield to define how you want to keep the information.

chargebacks: A new debit item that you assign to your customer when you close an existing, outstanding debit item.

child segment value: A detail-level segment value that is part of a parent segment value. See also parent segment value

chart of accounts: The account structure your organization uses to record transactions and maintain account balances.

chart of accounts structure: A classification of account segment values that assigns a particular range of values a common characteristic. For example, 1000 to 1999 might be the range of segment values for assets in the account segment of your accounting flexfield.

check: A bill of exchange drawn on a bank and payable on demand. Or, a written order on a bank to pay on demand a specified sum of money to a named person, to his or her order, or to the bearer out of money on deposit to the credit of the maker.
A check differs from a warrant in that a warrant is not necessarily payable on demand and may not be negotiable. It differs from a voucher in that a voucher is not an order to pay.

check box: You can indicate an on/off or yes/no state for a value by checking or unchecking its check box. One or more check boxes can be checked since each check box is independent of other check boxes.

check overflow: A check printing situation where there are more invoices paid by a check than can fit on the remittance advice of the check.

check run: The process of creating multiple payment documents for a group of invoices.
See also Automatic Payment Processing.

child request: A concurrent request submitted by another concurrent request (a parent request.) For example, each of the reports and/or programs in a report set are child requests of that report set.

CIP assets: See construction-in-process assets.

chargeable project: For each expenditure, a project to which the expenditure can be charged or transferred.

class category

An implementation-defined category for classifying projects. For example, if you want to know the market sector to which a project belongs, you can define a class category with a name such as Market Sector. Each class category has a set of values (class codes) that can be chosen for a project. See class code

class code

An implementation-defined value within a class category that can be used to classify a project. See class category.

clear: A payment status when the bank has disbursed funds for the payment, and the payment has been cleared but not matched to a bank statement within Oracle Cash Management.

clearing account: An account used to ensure that both sides of an accounting transaction are recorded. For example, when you purchase an asset, your payables group creates a journal entry to the asset clearing account. When your fixed assets group records the asset, they create another journal entry to the asset clearing account to balance the entry from the payables group.

closed order: An order and its order lines that have completed all actions of the order cycle and on which the Close Orders program has been run.

COGS Account: See Cost of Goods Sold Account.

column set

A Financial Statement Generator report component you build within Oracle Applications by defining all of the columns in a report. You control the format and content of each column, including column headings, spacing and size, calculations, units of measure, and precision. A typical column set includes a header column for headings and subheadings, currency assignments, amount types, and calculation columns totals.

You can also define a column set with each column representing a different company to enhance consolidation reporting.

columns: Oracle7 Tables consist of columns. Each column contains one type of information. The format to indicate tables and columns is: (TABLE_NAME.COLUMN_NAME).

combination block: A combination block displays the fields of a record in both multi-record (summary) and single-record (detail) formats. Each format appears in its own separate window that you can easily navigate between.

combination of segment values: A combination of segment values uniquely describes the information stored in a field made up of segments. A different combination of segment values results when you change the value of one or more segments. When you alter the combination of segment values, you alter the description of the information stored in the field.

combination query: See Existing Combinations.

combined basis of accounting: A method of accounting that combines both Accrual Basis of Accounting and Cash Basis of Accounting. With Combined Basis of Accounting, you use two separate sets of books, one for the accrual basis accounting method and the other for the cash basis accounting method. Oracle Applications creates journal entries for invoices and payments to post to your accrual set of books and creates journal entries for payments to post to your cash set of books.

comment alias: A user-defined name for a frequently used line of comment text, which can be used to facilitate online entry of timecards and expense reports.

commitment

A contractual guarantee with a customer for future purchases; usually with deposits or prepayments. You can then create invoices against the commitment to absorb the deposit or prepayment. Oracle Payables automatically records all necessary accounting entries for your commitments. Oracle Order Entry allows you to enter order lines against commitments.

An encumbrance you record when you complete a purchase requisition.

common bill: A bill of material that is shared between organizations. This enables you to reduce your maintenance effort by sharing the same bill structure among two or more bills of material. For example, if you have identical bills of material that produce the same product in two different organizations, you can define common bills of material for the identical structures.

compensation rule

An implementation-defined name for an employee compensation method. Also known as pay type. Typical compensation rules include Hourly and Exempt.

complete invoice

An invoice whose status is Complete. In order for an invoice to have a status of Complete, the invoice total must be greater than or equal to zero, have at least one invoice line, revenue records must exist for each line, revenue records for each line must add up to the line amount, and a tax and sales credit record must exist for each line. It is only after you complete the invoice that your customer's balance will be updated.

compound tax: A method of calculating tax on top of other tax charges. You can create compound taxes in the Transaction window or with AutoInvoice.

complete matching: A condition where the invoice quantity matches the quantity originally ordered, and you approve the entire quantity. See also matching, partial matching.

construction-in-process (CIP) asset: A depreciable fixed asset you plan to build during a capital project. The costs associated with building CIP assets are referred to as CIP costs. See also capital project.

component: See Standard Component.

component item: An item associated with a parent item on a bill of material.

concurrent manager: A unique facility that manages many time-consuming, non-interactive tasks within Oracle Applications for you, so you do not have to wait for their completion. When you submit a request in Oracle Applications that does not require your interaction, such as releasing shipments or running a report, the Concurrent Manager does the work for you, enabling you to complete multiple tasks simultaneously.

concurrent process: A non-interactive task that you request Oracle Applications to complete. Each time you submit a non-interactive task, you create a new concurrent process. A concurrent process runs simultaneously with other concurrent processes (and other interactive activities on your computer) to help you complete multiple tasks at once.

concurrent processing: Allows a single processor to switch back and forth between different programs.

concurrent queue: A list of concurrent requests awaiting completion by a concurrent manager. Each concurrent manager has a queue of requests waiting to be run. If your system administrator sets up your Oracle Application to have simultaneous queuing, your request can wait to run in more than one queue.

concurrent request: A request to Oracle Applications to complete a non-interactive task for you. You issue a request whenever you submit a non-interactive task, such as releasing a shipment, posting a journal entry, or running a report. Once you submit a request, Oracle Applications automatically takes over for you, completing your request without further involvement from you or interruption of your work.

configuration: A group of order lines that correspond to a customer's selection of a base model and associated options. Configurations can either be shipped as individual pieces, as a set (kit), or as an assemble (configuration item). See also assemble-to-order model, configuration item, model, pick-to-order model.

configuration item: The item that corresponds to a base model and a specific list of options chosen by the customer. Oracle Bills of Material creates a new configuration item each time a customer orders an ATO model. A PTO model appears as a list of items on the pick slip for the picker to gather for shipment. See also assemble-to-order model, configuration, pick-to-order model.

configurator: The Enter Configuration Options form that allows you to choose options that are available for a particular model, thus defining a particular configuration for the model.

configure-to-order: An environment where you enter customer orders by choosing a base model and then selecting options from a list of choices.

consolidation: An Oracle Applications feature that allows you to combine the results of multiple companies, even if they are in different sets of books with different currencies, calendars, and charts of account.

consolidation set of books: A set of books which has average balance processing enabled and which is defined as a consolidation set of books. A consolidation set of books must be used to consolidate average balances using the balances consolidation method.

construction-in-process (CIP) assets: You construct CIP assets over a period of time rather than buying a finished asset. Oracle Assets lets you create, maintain, and add to your CIP assets as you spend money for material and labor to construct them. When you finish the assets and place them in service (capitalize them), Oracle Assets begins depreciating them.

consumption tax: An indirect tax imposed on transfer of goods and services at each stage of their supply. The difference between output tax (tax collected for revenue earned from the transfer) and the input tax (tax paid on expense paid on the transfer) will be the tax liability to the government. This tax is, in concept, value added tax (VAT).

contact

A representative who is responsible for communication between you and a specific part of your customer's company. For example, your customer may have a shipping contact person who handles all questions regarding orders shipped to that address. Oracle Applications lets you enter contacts for your customers, addresses and business purposes.

A customer representative who is involved with a project. For example, a contact can be a billing contact, the customer representative who receives project invoices.

contact role: A responsibility that you associate to a specific contact. Oracle Applications provides 'Bill To', 'Ship To', and 'Statements,' but you can enter additional responsibilities.

contact type

An implementation-defined classification of project contacts according to their role in the project. Typical contact types are Billing and Shipping.

content set: A report component you build within Oracle Applications that defines the information in each report and the printing sequence of your reports. For example, you can define a departmental content set which prints one report for each department.

context field prompt: A question or prompt to which a user enters a response, called a context field value. When Oracle Applications displays a descriptive flexfield pop-up window, it displays your context field prompt after it displays any global segments you have defined. Each descriptive flexfield can have up to one context prompt.

context field value: A response to your context field prompt. Your response is composed of a series of characters and a description. The response and description together provide a unique value for your context prompt, such as 1500, Journal Batch ID, or 2000, Budget Formula Batch ID. The context field value determines which additional descriptive flexfield segments appear.

context response: See context field value.

context segment value: A response to your context-sensitive segment. The response is composed of a series of characters and a description. The response and description together provide a unique value for your context-sensitive segment, such as Redwood Shores, Oracle Corporation Headquarters, or Minneapolis, Merrill Aviation's Hub.

context-sensitive segment: A descriptive flexfield segment that appears in a second pop-up window when you enter a response to your context field prompt. For each context response, you can define multiple context segments, and you control the sequence of the context segments in the second pop-up window. Each context-sensitive segment typically prompts you for one item of information related to your context response.

contract project: A project for which you can generate revenue and invoices. Typical contract project types include Time and Materials and Fixed Price. Formerly known as a direct project.

control amount: An Oracle Applications feature you use to specify the total amount available for payment of a recurring payment. When you generate invoices for a recurring payment, Oracle Applications uses the control amount and the total number of payments to determine the invoice amount.

control book: A tax book, used for mass depreciation adjustments, which holds the minimum accumulated depreciation for each asset.

control file: A file used by SQL*Loader to map the data in your bank file to tables and columns in the Oracle7 database. You must create one control file for each different bank file you receive, unless some or all of your banks use the exact same format.

conversion

Converts foreign currency transactions to your functional currency.

See also foreign currency conversion.

Corporate book: A depreciation book that you use to track financial information for your balance sheet.

corporate exchange rate: An exchange rate you can optionally use to perform foreign currency conversion. The corporate exchange rate is usually a standard market rate determined by senior financial management for use throughout the organization.

cost base

A cost base refers to the grouping of raw costs to which burden costs are applied. Examples of cost bases are Labor and Materials.

cost breakdown category: A breakdown of a project or task budget to categorize costs. You can categorize costs by expenditure category, expenditure type, job, or expenditure organization.

cost budget

The estimated cost amounts at completion of a project. Cost budget amounts can be summary or detail, and can be burdened or unburdened.

cost burden schedule

A burden schedule used for costing to derive the total cost amount. You assign the cost burden schedule to a project type which is burdened; this default cost burden schedule defaults to projects that use the project type; and then from the project to the tasks below the project. You may override the cost burden schedule for a project or a task if you have defined the project type option to allow overrides of the cost burden schedule.

cost distribution: The act of calculating the cost and determining the cost accounting for an expenditure item.

Cost of Goods Sold Account: The general ledger account number affected by receipts, issuances and shipments of an inventory item. Oracle Order Entry allows dynamic creation of this account number for shipments recording using FlexBuilder. See also FlexBuilder.

cost rate

The monetary cost per unit of an employee, expenditure type, or resource.

Cost-to-Cost: A revenue accrual method that calculates project revenue as budgeted revenue multiplied by the ratio of actual cost to budgeted cost. Also known as percentage of completion method or percentage spent method.

credit check: An Oracle Order Entry feature that automatically checks a customer order total against predefined order and total order limits. If an order exceeds the limit Oracle Order Entry places the order on hold for review by your finance group. See also credit profile class, credit check rule.

credit check rule: A rule that defines the components used to calculate a customer's outstanding credit balance. Components include open receivables, uninvoiced orders, and orders on hold. You can include or exclude components in the equation to derive credit balances consistent with your company's credit policies.

credit invoice

An invoice you receive from a supplier representing a credit amount that the supplier owes to you. A credit invoice can represent a quantity credit or a price reduction.

You can create a mass addition line from a credit invoice and apply it to an asset.

credit items: Any item you can apply to an open debit item to reduce the balance due for a customer. Oracle Applications includes credit memos, on account credits, and unapplied and on account cash as credit items. Credit items remain open until you apply the full amount to debit items.

credit memo

A document which partially or fully reverses an original invoice.

A document which partially or fully reverses an original invoice. You can create credit memos through the Oracle Payables Enter Credit Memos form or through AutoInvoice.

credit memo reasons

Standard explanations as to why you credit your customers. (Receivables QuickCode)

See also return reason.

cross site and cross customer receipts: Receipts that you apply across customers and sites and are fully applied. Each of these receipts appears on the statements of the customer site that owns the receipt. The invoice(s) to which you have applied a cross receipt appear on the statement of the customer or site that owns the invoice.

credit receiver: A person receiving credit for project or task revenue. One project or task may have many credit receivers for one or many credit types.

credit type

An implementation-defined classification of the credit received by a person for revenue a project earns. Typical credit types include Quota Credit and Marketing Credit.

cross rate: An exchange rate you use to convert one foreign currency amount to another foreign currency amount. In Oracle Applications, you use a cross rate to convert your invoice currency to your payment currency. Currently, the payment currency must be the same as the invoice currency.

Cross-Project responsibility: A responsibility that permits users to view and update any project.

cross-project user: A user who is logged into Oracle Projects using a Cross-Project responsibility.

cross-validation rules

Rules that define valid combinations of segment values a user can enter in an account. Cross-validation rules restrict users from entering invalid combinations of account segment values.

Rules that define valid combinations of segment values that a user can enter in an key flexfield. Cross-validation rules restrict users from entering invalid combinations of key flexfield segment values.

Cumulative Translation Adjustment: A balance sheet account included in stockholder's equity in which Oracle Applications records net translation adjustments in accordance with FASB 52 (U.S.). You specify the account you want to use for Cumulative Translation Adjustment when you define each set of books in the Define Set of Books form.

current dimension: The Oracle Financial Analyzer dimension from which you are selecting values. The current dimension is the one you specified in the Dimension box of the Selector window. Choices you make and actions you take in lower-level windows ultimately affect this dimension by selecting values from it to include in a report, graph, or worksheet.

current object: The Oracle Financial Analyzer object upon which the next specified action takes place. Generally, the current object is the one most recently selected. However, if you use a highlight a group of objects, such as data cells in a column, the first object in the group is the current object.

current budget: The most recently baselined budget version of the budget.

current record indicator: Multi-record blocks often display a current record indicator to the left of each record. A current record indicator is a one character field that when filled in, identifies a record as being currently selected.

customer address: A location where your customer can be reached. A customer may have many addresses. You can also associate business purposes with addresses.

customer agreement: See agreement.

customer agreement type

See agreement type.

customer bank: A bank account you define when entering customer information to allow funds to be transferred from these accounts to your remittance bank accounts as payment for goods or services provided. See also remittance bank

customer business purpose: See business purpose

customer class: A method to classify your customers by their business type, size, or location. You can create an unlimited number of customer classes. (Receivables QuickCode)

customer contact: A specific customer employee with whom you communicate. Oracle Applications lets you define as many contacts as you wish for each customer. You can also define contacts for an address and assign previously defined contacts to each business purpose.

customer family agreement: An agreement for a specific customer, available to any related customer. See also agreement, generic agreement.

customer interface: A program that transfers customer data from foreign systems into Oracle Payables.

customer interface tables: A series of two Oracle Receivables tables from which Customer Interface inserts and updates valid customer data into your customer database.

customer merge: A program that merges business purposes and all transactions associated to that business purpose for different sites of the same customer or for unrelated customers.

customer number: The number a supplier assigns to your organization.

customer number: A number you assign to your customers to uniquely identify them. A customer number can be assigned manually or automatically, depending on how you setup your system.

customer phone: A phone number that is associated with a customer. You can also assign phone numbers to your contacts.

customer profile: A method used to categorize your customers based on credit information. Oracle Payables uses credit profiles to assign statement cycles, dunning letter cycles, salespersons, and collectors to your customers. You can also decide whether you want to charge your customers interest. Oracle Order Entry uses the order and total order limits when performing credit checking.

customer profile class: A category for your customers based on credit information, payment terms, currency limits and correspondence types.

customer relationship

An association that exists between customers which allows you to

apply payments to related customers, apply invoices to related customer's commitments, and create invoices for related customers.

share agreements, bill-to and ship-to addresses.

customer response: Explanations, comments, or claims customers make during conversation with the collector regarding the call reason.

customer site: A site where a customer is located. Each customer may have more than one site. A site name can more easily identify a customer address, making invoice and order entry quicker. See also location.

customer status: The Active/Inactive flag you use to inactivate customers with whom you no longer do business. If you are using Oracle Order Entry, you can only enter orders, agreements, and returns for active customers, but you can continue to process returns for inactive customers. If you are using Oracle Payables, you can only create invoices for active customers, but you can continue collections activities for inactive customers.

cutoff day: The day that is used to determine when an invoice with proxima payment terms is due. For example, if it is January and the cutoff day is the 10th, invoices dated before January 10 are due in February and invoices dated after January 10 are due in March.

cycle action: A cycle action is a discrete event that can occur one or more times during the life of an order. Actions can occur at the order level (where all lines on the order are processed together), such as credit or legal reviews. Actions can also occur at the line level (where each line can be processed independently), such as shipping confirmation or backordering. Oracle Order Entry uses actions to identify each step in your order cycle. See also action result, order cycle.

D

DBA library: If an Oracle Financial Analyzer database object belongs to a DBA library, it means that the object was created by an administrator and cannot be modified by a user.

database table: A basic data storage structure in a relational database management system. A table consists of one or more units of information (rows), each of which contains the same kind of values (columns). Your application's programs and windows access the information in the tables for you. See also customer interface tables

date placed in service: The calendar date that you start using an asset.

debit invoice: An invoice you generate to send to a supplier representing a credit amount that the supplier owes to you. A debit invoice can represent a quantity credit or a price reduction.

debit items: Any item that increases your customer's balance. Oracle Applications includes invoices, debit memos, and chargebacks as debit items. Debit items remain open until the balance due is 0.

debit memo reversal: A reversal of a payment which generates a new debit memo, instead of reopening old invoices and debit memos.

debit memos: Debits that you assign to your customer for additional charges that you want to collect. You may want to charge your customers for unearned discounts taken, additional freight charges, taxes, and finance charges.

default value: Information that Oracle Order Entry automatically enters depending on other information you enter. See also standard value.

deferred depreciation: The difference between the depreciation expense for an asset in a tax book and its depreciation expense in the associated corporate book.

deferred revenue: An event type classification that generates an invoice for the amount of the event, and has no immediate effect on revenue. The invoice amount is accounted for in an unearned revenue account that will be offset as the project accrues revenue.

delete group: A set of items, bills, and routings you choose to delete.

demand: An effective method of communicating current or future product need to Inventory and other manufacturing products. Effective demand management allows you make timely decisions on product procurement and resource scheduling.

demand class: A category you can use to segregate scheduled demand and supply into groups, so that you can track and consume the groups independently. You can define a demand class for a very important customer or a group of customers, such as distributor. (Manufacturing QuickCode)

demand management: The function of recognizing and managing all demands for products, to ensure the master scheduler is aware of them. This encompasses forecasting, order entry, order promising (available to promise), branch warehouse requirements, and other sources of demand.

demand time fence: A date within which the planning process does not consider forecast demand when calculating actual demand. Within the demand time fence, sales orders are the only source of demand. Outside the demand time fence, the planning process considers forecast entries.

dependent segment: An account segment in which the available values depend on values entered in a previous segment, called the independent segment. For example, the dependent segment Sub-Account 0001 might mean Bank of Alaska when combined with the independent segment Account 1100, Cash, but the same Sub-Account 0001 might mean Building #3 when combined with Account 1700, Fixed Assets.

deposit: A type of commitment whereby a customer agrees to deposit or prepay a sum of money to be used for the future purchase of goods and services.

depreciable basis: The amount of your asset that is subject to depreciation, generally the cost minus the salvage value. Also known as recoverable cost.

depreciate: To depreciate an asset is to spread its cost over the time you use it. You charge depreciation expense for the asset each period. The total depreciation taken for an asset is stored in the accumulated depreciation account.

depreciation book: A book to store financial information for a group of assets. A depreciation book can be corporate, tax, or budget. Also known as book.

depreciation calendar: The depreciation calendar determines the number of accounting periods in a fiscal year. It also determines, with the divide depreciation flag, what fraction of the annual depreciation amount to take each period. You must specify a depreciation calendar for each book.

depreciation projection: The expected depreciation expense for specified future periods.

depreciation reserve: See accumulated depreciation.

derived parameter: A parameter that FlexBuilder uses that is determined from raw or other derived parameters, from key flexfield segments, qualifiers, or value sets, or from a constant. Derived parameters can be dependent on the value of another parameter (raw or derived). Oracle Applications provides some derived parameters and you can define additional derived parameters. See also assignment, function, parameter (FlexBuilder), raw parameter.

descriptive flexfieldDescriptive Flexfield

A field that your organization can extend to capture extra information not otherwise tracked by Oracle Applications. A descriptive flexfield appears on your form as a single character, unnamed field. Your organization can customize this field to capture additional information unique to your business.

A field that your organization can extend to capture extra information that is otherwise not tracked by Oracle Applications. A Descriptive Flexfield appears on your form as a single character, unnamed field. Your organization can customize this field to capture additional information that is necessary and unique to your business.

direct project: An obsolete term. See also contract project.

detail budget: A budget whose authority is controlled by another budget.

dimension: An Oracle Financial Analyzer database object used to organize and index the data stored in a variable. Dimensions answer the following questions about data: "What?" "When?" and "Where?" For example, a variable called Units Sold might be associated with the dimensions Product, Month, and District. In this case, Units Sold describes the number of products sold during specific months within specific districts.

dimension label: A text label that displays the name of the Oracle Financial Analyzer dimension associated with an element of a report, graph, or worksheet. For example, the data markers in a graph's legend contain dimension labels that show what data each data marker represents. Dimension labels can be short, meaning they display the object name of a dimension, or user-specified, meaning they display a label that you typed using the Dimension Labels option on the Graph, Report, or Worksheet menus.

dimension values: Elements that make up an Oracle Financial Analyzer dimension. For example, the dimension values of the Product dimension might include Tents, Canoes, Racquets, and Sportswear.

direct debit: An agreement made with your customer to allow the transfer of funds from it's bank account to your bank account. The transfer of funds occurs when the bank receives a document or tape containing the invoices to be paid.

disbursement type: An Oracle Applications feature you use to determine the type of payment for which a payment document is used. Examples: computer-generated payments, and recorded checks or wire transfers.

discount

(Order Entry) A reduction of the list price of an item. In Oracle Order Entry, you can associate discounts with price lists and apply them either automatically or manually to an order or order line.

See also best discount, fixed price discount, price adjustment. See earned discounts.

discrete job: A production order for the manufacture of a specific (discrete) quantity of an assembly, using specific materials and resources, within a limited range of time. A discrete job collects the costs of production and allows you to report those costs -- including variances -- by job. Also known as work order or assembly order.

display group: A range of rows or columns in your row set or column set for which you want to control the display in your report. You assign a display group to a display set where you specify whether you want to display or hide your rows or columns.

display set: A Financial Statement Generator report component you build within Oracle Applications to control the display of ranges of rows and columns in a report, without reformatting the report or losing header information. You can define a display set that works for reports with specific row and column sets. Alternatively, you can define a generic display set that works for any report.

distribution line

A line corresponding to an accounting transaction for an expenditure item on an invoice or a liability on a payment.

Information such as employee, general ledger depreciation expense account, and location to which you have assigned an asset. You can create any number of distribution lines for each asset. Oracle Assets uses distribution lines to allocate depreciation expense and to produce your Property Tax and Responsibility Reports.

distribution list: A distribution list is a set of mail names to whom Oracle Alert sends a message when it finds an exception condition. An alert can have many distribution lists and each distribution list can have its own set of input variables to increase your control over who gets messages about what. For example, to send a message about furniture to Joe Smith and about telecommunications equipment to Sally Jones, you can define two distribution lists and enter the appropriate item class as an input variable to each list.

distribution rule: See revenue distribution rule.

distribution set

A predefined group of general ledger accounting codes that would determine the debit accounts for other receipt payments. Oracle Applications lets you relate distribution sets to receivables activities to speed data entry.

An Oracle Applications feature you use to assign a name to a predefined expense distribution or combination of distributions (by percentage). Oracle Applications displays the list of names in a pop-up window. With Distribution Sets, you can enter routine invoices into Oracle Applications without having to enter accounting information.

distribution total: The total amount of the distribution lines of an invoice. The distribution total must equal the invoice amount before you can pay or post an invoice.

document category: A document category is used to split transactions into logical groups. You can assign a different sequence to each category and by doing so separately number each logical group. Each category is associated with a table. When you assign a sequence to a category, the sequence numbers the transactions in that table. Oracle Applications lets you set up categories for each type of transaction, receipt and adjustment.

document sequence: Used to uniquely number documents created by Oracle Applications. A Document Sequence has a sequence name, initial value and a type of automatic or manual.

domestic transaction: Transactions between registered traders in the same EU (European Union) country. Domestic transactions have VAT charged on goods and services with different countries applying different VAT rates to specific goods and services. See also external transaction, EU

document sequence number: A number that is manually or automatically assigned to your documents to provide an audit trail. For example, you can choose to sequentially number invoices in Oracle Payables or journal entries in Oracle General Ledger. See also voucher number.

document sets: A grouping of shipping documents that you can run from the Confirm Shipments form.

draft budget: A preliminary budget which may be changed without affecting revenue accrual on a project.

draft invoice

A potential project invoice that is created, adjusted, and stored in Oracle Projects. Draft invoices require approval before they are officially accounted for in other Oracle Applications.

draft revenue

A project revenue transaction that is created, adjusted, and stored in Oracle Projects. You can adjust draft revenue before you transfer it to other Oracle Applications.

drilldown: A software feature that allows you to view the details of an item in the current window via a window in a different application.

Dual Currency: An Oracle General Ledger feature that allows you to report in your functional currency and in one or more foreign currencies.

dunning letter set: A group of dunning letters which you can assign to your customer's credit profile.

dunning letters: A letter that you send to your customers to inform them of past due debit items. Oracle Payables lets you specify the text and format of each letter. You can choose to include unapplied and on-account payments.

duplicate: An exception that Oracle Alert has previously sent to the same distribution list. You can choose to suppress duplicates completely for detail messages, or to identify them with asterisks (*) in summary messages. For example, if on Monday Oracle Alert notifies a purchasing agent that a supplier shipment is overdue, then on Tuesday Oracle Alert finds that the shipment is still overdue, you can choose whether Oracle Alert should renotify the purchasing agent or suppress the message.

dynamic distribution: A distribution that includes at least one recipient whose electronic mail ID is represented by an alert output. Oracle Alert locates the actual electronic mail ID in one of the application tables, and substitutes it into the distribution before sending the alert message.

dynamic insertion

An Accounting Flexfields feature that allows you to enter and define new combinations of segment values directly in a flexfield pop-up window. The new combination must satisfy any cross-validation rules before it is accepted. Your organization can decide if an Accounting Flexfield supports dynamic insertion. If an account does not support dynamic insertion, you can only enter new combinations of segment values using the Define Accounts form.

A feature specific to key flexfields that allows you to enter and define new combinations of segment values directly into a flexfield pop-up window. The new combination must satisfy any cross-validation rules, before your flexfield accepts the new combination. Your organization can decide if a key flexfield supports dynamic insertion. If a flexfield does not support dynamic insertion, you can only enter new combinations of segment values using a combinations form (a form specifically used for creating and maintaining code combinations).

An Oracle Applications feature that lets you automatically create new key flexfield combinations when you enter transactions or customers. If you do not use dynamic insertion, you can only create new key flexfield combinations using the various flexfield setup forms.

E

effective date: The date a transaction affects the balances in the general ledger. This does not have to be the same as the posting date. Also known as the value date.

earned discounts: Discounts your customers are allowed to take if they pay for their invoices on or before the discount date. Oracle Applications takes into account any discount grace days you assign to this customer's credit profile. For example, if the discount due date is the 15th of each month, but discount grace days is 5, your customer must pay on or before the 20th to receive the earned discount. Discounts are determined by the terms you assign to an invoice during invoice entry. Oracle Applications differentiates between earned and unearned discounts. An earned discount is a discount you give to a customer who pays on or before the discount date or within the discount grace period. For example, a customer may earn a 2% discount off the original invoice if payment is received within 10 days. Oracle Applications lets you decide whether to allow unearned discounts. If you allow unearned discounts, Oracle Applications lets you give a customer the unearned discount if the customer pays after the discount date or after the discount grace day period. Oracle Applications defaults the discount taken to zero if the discount is unearned. If the discount is earned, Oracle Applications defaults discount taken to the amount of the earned discount. Oracle Applications lets you override the discount taken amount during payment entry and warns you if you are taking an unearned discount.

effective payment: An invoice payment that is not void or an applied prepayment that is not reversed. See also Prepayment.

EFT: See Electronic Funds Transfer (EFT).

Electronic Funds Transfer (EFT): A method of payment in which your bank transfers funds electronically from your bank account into another bank account. In Oracle Applications, your bank transfers funds from your bank account into the bank account of a supplier you pay with the EFT payment method.

employee billing title

An employee title, which differs from a job billing title, that may appear on an invoice. Each employee can have a unique employee billing title.

employee organization: The organization to which an employee is assigned.

encumbrance

See encumbrance journal entry

encumbrance accounting

An Oracle Financials feature you use to create encumbrances automatically for requisitions, purchase orders, and invoices. The budgetary control feature uses encumbrance accounting to reserve funds for budgets. If you enable encumbrance accounting only, you can create encumbrances automatically or manually; however, you cannot check funds online and Oracle Financials does not verify available funds for your transaction. See also budgetary control.

encumbrance journal entry

A journal entry which increases or relieves encumbrances. Encumbrance entries can include encumbrances of any type. If you have enabled encumbrance accounting, when you successfully approve an invoice matched to an encumbered purchase order, Oracle Applications automatically creates encumbrance journal entries that relieve the original encumbrance journal entries. Oracle Applications also creates new encumbrance journal entries for any quantity or price variance between an invoice and the matched purchase order. Oracle Applications automatically creates encumbrance journal entries for an unmatched invoice when you approve the invoice.

A journal entry you create online that increases or relieves your encumbrances. Encumbrance entries can include encumbrances of any type. You can enter manual encumbrance entries, define encumbrance allocations, or use Journal Import to import encumbrance entries from other financial systems.

encumbrance type

An encumbrance category that allows you to track your anticipated expenditures according to your purchase approval process and to more accurately control your planned expenditures. Examples of encumbrance types are commitments (requisition encumbrances) and obligations (purchase order encumbrances).

An encumbrance category that allows you to track your anticipated expenditures according to your purchase approval process and better control your planned expenditures. You can also attach an encumbrance type to your invoices for reporting purposes. Examples of encumbrance types are commitments (requisition encumbrances) and obligations (purchase order encumbrances)

end-of-day balance: The actual balance of a general ledger account at the end of a day. This balance includes all transactions whose effective date precedes or is the same as the calendar day.

ending balance: The ending balance represents the balance of the transaction item as of the ending GL Date that you have specified. This column should be the same as the Outstanding Balance of the Aged Trial Balance - 7 Buckets Report for this transaction item.

EU: European Union, is a single European market where customs and tariff barriers between member states have been removed.

engineer-to-order: An environment where customers order unique configurations that engineering must define and release custom bills for material and routings that specify how to build them. Oracle Manufacturing Release 10 does not provide special support for this environment beyond the support it provides for assemble-to-order manufacturing.

engineering change order (ECO): A record of revisions to one or more items usually released by engineering.

error checking group: An Oracle Applications feature you use to verify that the information you load from a bank tape or diskette is accurate and complete. You define error checking groups in Oracle Applications to verify against the bank error checking group. For example, your bank may count all records as an error check. When you load a bank tape, Oracle Applications counts all records, compares your error checking total with the bank total, and does not proceed with payment reconciliation unless they are equal.

event

A summary level transaction assigned to a project or top task that records work completed and generates revenue and/or billing activity, but is not directly related to any expenditure items. For example, unlike labor costs or other billable expenses, a bonus your business receives for completing a project ahead of schedule is not attributable to any expenditure item, and would be entered as an event.

event alert

An alert that runs when a specific event that you define occurs. For example, you can define an event alert to immediately send a message to the buyer if an item is rejected on inspection.

An alert that runs when a specific event occurs that you define. For example, you can define an event alert to send a message to the Accounts Payable Supervisor when an Accounts Payable Clerk enters an invoice that exceeds your maximum invoice amount for that supplier.

event type: An implementation-defined classification of events that determines the revenue and invoice effect of an event. Typical event types include Milestones, Scheduled Payments, and Write-Offs.

exception: A single occurrence of an event returned by an alert check. For example, if an alert checking for invoices that AutoApproval places on funds hold finds five such invoices, each invoice is an exception.

exception reporting: Exception reporting is an integrated system of alerts, messages and distribution lists to focus attention on time-sensitive or critical information, streamline your communication channels, shorten your reaction time, and eliminate your information clutter. Exception reporting communicates information by either electronic mail or paper reports.

exchange rate

A rate that represents the amount of one currency that you can exchange for another at a particular point in time. Oracle Applications use the daily, periodic, and historical exchange rates you maintain to perform foreign currency conversion, revaluation, and translation.

A rate that represents the amount in one currency that you can exchange for another at a particular point in time. You can enter and maintain daily exchange rates for Oracle Applications to use to perform foreign currency conversion. Oracle Applications multiplies the exchange rate times the foreign currency to calculate the functional currency.

exchange rate type: A specification of the source of an exchange rate. For example, a user exchange rate or a corporate exchange rate. See also corporate exchange rate, spot exchange rate.

exchange rate variance: The difference between the exchange rate for a foreign-currency invoice and its matched purchase order. Payables tracks any exchange rate variances for your foreign-currency invoices.

Existing Combinations: A feature specific to key flexfields in data entry mode that allows you to enter query criteria in the flexfield to bring up a list of matching predefined combinations of segment values to select from.

expenditure: A group of expenditure items incurred by an employee or an organization for an expenditure period. Typical expenditures include Timecards and Expense Reports.

expenditure (week) ending date: The last day of an expenditure week period. All expenditure items associated with an expenditure must be on or before the expenditure ending date, and must fall within the expenditure week identified by the expenditure week ending date.

expenditure category

An implementation-defined grouping of expenditure types by type of cost. For example, an expenditure category with a name such as Labor refers to the cost of labor.

expenditure comment

Free text that can be entered for any expenditure item to explain or describe it in further detail.

expenditure cost rate: The monetary cost per unit of a non-labor expenditure type.

expenditure cycle: A weekly period for grouping and entering expenditures.

expenditure group

A user-defined name used to track a group of pre-approved expenditures, such as Timecards, or Expense Reports.

expenditure item

The smallest logical unit of expenditure you can charge to a project and task. For example, an expenditure item can be a timecard item or an expense report item.

expenditure item date: The date on which work is performed, and on which work is charged to a project and task.

expenditure operating unit: For an expenditure, the operating unit where the expenditure item was incurred against a project.

expenditure organization: For timecards and expense reports, the organization to which the incurring employee is assigned, unless overridden by organization overrides. For usage, supplier invoices, and purchasing commitments, the incurring organization entered on the expenditure.

expenditure type: An implementation-defined classification of cost that you assign to each expenditure item. Expenditure types are grouped into cost groups (expenditure categories) and revenue groups (revenue categories).

expenditure type class: An additional classification for expenditure types that indicates how Oracle Projects processes the expenditure types. Oracle Projects predefines the five valid expenditure type classes: Straight Time, Overtime, Expense Reports, Usages, and Supplier Invoices. For example, if you run the Distribute Labor Costs process, Oracle Projects will calculate the cost of all expenditure items assigned to the Straight Time expenditure type class. Formerly known as system linkage.

expense report

A document that, for purposes of reimbursement, details expenses incurred by an employee.

You can enter expense reports online, or as part of a pre-approved batch.

expense report: A document that, for purposes of reimbursement, details expenses incurred by an employee. You can set up expense report templates to match the format of your expense reports to speed data entry. You must create invoices from Payables expense reports using Invoice Import before you can pay the expense reports.

expensed asset: An asset which you do not depreciate, but charge the entire cost in a single period. Oracle Assets does not depreciate an expensed asset, or create any journal entries for it. You can, however, use Oracle Assets to track expensed assets. The Asset Type for these assets is "Expensed".

expensed item: Items that do NOT depreciate; the entire cost is charged in a single period to an expense account. Oracle Applications tracks expensed items, but does not create journal entries for them.

export: A utility that enables you to copy data from an Oracle7 table to a file in your current directory. The export utility is part of the Oracle7 Relational Database Management System.

export: To move archive data to a different storage device.

external transaction: Transactions between an EU (European Union) trader and a vendor or customer located in a non-EU country. Customers and sites in Non-EU countries are tax exempt and should have a zero tax code assigned to all invoices. See also domestic transaction, EU

export file: The file the export utility creates in your directory. Export files must have the extension .dmp. It is wise to name the export file so it identifies the data in the table. For example, if you are saving fiscal year 1994 for your Fremont set of books, you might call your export file FY94FR.dmp.

external organization: See organization.

F

factor

Data upon which you perform some mathematical operation. Fixed amounts, statistical account balances, account balances, and report rows and columns are all data types you can use in formulas.

The payee of an invoice when the payee differs from the supplier on the invoice. For example, a supplier may have sold their receivables to a factor.

factoring: The process by which you sell your accounts receivable to a financial institution in return for cash. The financial institution charges a fee for factoring.

FASB 52 (U.S.): See SFAS 52.

FASB 8 (U.S.): See SFAS 8.

Federal Identification Number: See Tax Identification Number.

feeder program: A custom program you write to transfer your transaction information from an original system into Oracle Application interface tables. The type of feeder program you write depends on the environment from which you are importing data.

feeder system: Another system from which you can pass information into Oracle Assets. For example, you can pass budget or production information from a spreadsheet into Oracle Assets.

financial data item: An Oracle Financial Analyzer database object that is made up of either a variable, or a variable and a formula. For example, a financial data item called "Actuals" would be a variable, while a financial data item called "Actuals Variance" would be made up of a variable (Actuals) and a formula that calculates a variance.

field: A position on a form that you use to enter, view, update, or delete information. A field prompt describes each field by telling you what kind of information appears in the field, or alternatively, what kind of information you should enter in the field.

field type: Each record you import is divided into regions, and each region holds a different piece of information. Oracle Applications calls these regions "fields", and provides you with a list of the types of fields that can be interfaced through AutoLockbox.

final assembly order: A discrete job created from a custom configuration or a standard configure to order item and linked to a sales order. Also known as final assembly schedule.

finance charges: Additional charges that you assign to your customers for past due items. You specify whether you want to charge your customers finance charges through their customer profiles. Finance charges can be included on your customer's statements and dunning letters.

Financial Statement Generator: A powerful and flexible tool you can use to build your own custom reports without programming. You can define reports online with complete control over the rows, columns and contents of your report.

firm schedule

A burden schedule of burden multipliers that will not change over time. This is compared to provisional schedules in which actual multipliers are mapped to provisional multipliers after an audit.

first bill offset days

The number of days that elapse between a project start date and the date that the project's first invoice is issued.

fiscal year

Any yearly accounting period without regard to its relationship to a calendar year.

fixed asset: An item owned by your business and used for operations. Fixed assets generally have a life of more than one year, are acquired for use in the operation of the business, and are not intended for resale to customers. Assets differ from inventory items since you use them rather than sell them.

fixed assets unit: A measure for the number of asset parts tracked in Oracle Assets. You can assign one or more units to a distribution line.

fixed date: See Schedule Fixed Date.

fixed price discount: A discount which fixes the final selling price of the item so it is not affected by changes to the list price of the item. It is a method of implementing discounts to the list price where the final price is contractually fixed regardless of changes to the list price, as is the case with GSA prices. For example, if Item A has a list price of $100, a fixed price discount specifying a selling price of $90 results in a selling price of $90 even if the list price later increases to $110.

flat file: A file where the data is unformatted for a specific application.

flat tax: A specific amount of tax, regardless of the amount of the item. There is no rate associated with flat taxes. Flat taxes are charged on items such as cigarettes, gasoline and insurance.

flat-rate depreciation method: A depreciation method which calculates the depreciation for an asset based on a fixed rate each year. This method uses a constant rate which Oracle Applications multiplies by an asset's recoverable cost or net book value as of the beginning of each fiscal year.

FlexBudgeting: An Oracle Applications feature that uses budget formulas and statistics to create a flexible budget. For example, a manufacturing organization may want to maintain a flexible budget based on actual units of production to eliminate volume variances during an analysis of actual versus budgeted operating results.

FlexBuilder: A feature that provides Oracle Applications with the ability to construct Accounting Flexfield combinations automatically using customized construction criteria.

FlexBuilder: A feature that provides Oracle Applications with the ability to construct Accounting Flexfield combinations automatically using customized construction criteria.

flexfield: An Oracle Applications field made up of segments. Each segment has an assigned name and a set of valid values. Oracle Applications uses flexfields to capture information about your organization. There are two types of flexfields: key flexfields and descriptive flexfields.

flexfield segment: One of the sections of your key flexfield, separated from the other sections by a symbol you define (such as -,/, or \). Each segment typically represents an element of your business, such as cost center, product, or account.

flexible address format: Oracle Applications allows you to enter an address in the format most relevant for the country of your customer, supplier, bank or remit-to site. This is done by using descriptive flexfields to enter and display address information in the appropriate formats. The descriptive flexfield opens if the country you enter has a flexible address style assigned to it, allowing you to enter an address in the layout associated with that country.

FOB: (Free On Board) The point or location where the ownership title of goods is transferred from the seller to the buyer. (Receivables QuickCode)

folder: A flexible entry and display window in which you can choose the fields you want to see and where each appears in the window. Read: About folders

follow up date: The date when you plan to perform a subsequent action. Examples include a date that you specify for verifying that you have received payment or a date that you note for calling the customer again.

forecast: An estimate of future demand on inventory items. A forecast contains information on the original and current forecast quantities (before and after consumption), the confidence factor, and any specific customer information. You can assign any number of inventory items to the forecast and use the same item in multiple forecasts. For each inventory item you specify any number of forecast entries.

forecast level: The level at which a forecast is defined. Also, the level at which to consume a forecast. Example forecast levels include items, customers, customer bill-to, and customer ship to locations.

foreign currency

A currency that you define for your set of books for recording and conducting accounting transactions in a currency other than your functional currency. When you enter and pay an invoice in a foreign currency, Oracle Applications automatically converts the foreign currency into your functional currency based on the exchange rate you define. See also exchange rate, functional currency.

A currency that you define for your set of books to record and conduct accounting transactions in a currency other than your functional currency.

foreign currency conversion

A process that allows you to convert a foreign currency journal entry into your functional currency. Oracle Applications automatically converts currency whenever you enter a journal entry in a currency other than your functional currency. Oracle Applications multiplies the daily exchange rate you define or the exchange rate you enter to convert amounts for your functional currency. You can view the results of foreign currency conversion in the Enter Journals form.

A conversion of a foreign currency transaction, such as an invoice or a payment, into your functional currency. Oracle Applications automatically performs this conversion whenever you enter an invoice or make a payment in a currency other than your functional currency.

foreign currency journal entry: A journal entry in which you record transactions in a foreign currency. Oracle Applications automatically converts foreign currency amounts into your functional currency using an exchange rate you specify. See also foreign currency, functional currency.

foreign currency revaluation: A process that allows you to revalue assets and liabilities denominated in a foreign currency using a period-end (usually a balance sheet date) exchange rate. Oracle Applications automatically revalues your foreign assets and liabilities using the period-end exchange rate you specify. Revaluation gains and losses result from fluctuations in an exchange rate between a transaction date and a balance sheet date. Oracle Applications automatically creates a journal entry in accordance with FASB 52 (U.S.) to adjust your unrealized gain/loss account when you run revaluation.

foreign currency translation: A process that allows you to restate your functional currency account balances into a reporting currency. Oracle Applications multiplies the average, periodic, or historical rate you define by your functional currency account balances to perform foreign currency translation. Oracle Applications translates foreign currency in accordance with FASB 52 (U.S.). Oracle Applications also remeasures foreign currencies for companies in highly inflationary economies, in accordance with FASB 8 (U.S.).

form: A logical collection of fields, regions, and blocks that appear on a single screen. Oracle Applications forms look just like the paper forms you use to run your business. All you need to do to enter data is type onto the form.

formula entry: A recurring journal entry that uses formulas to calculate journal entry lines. Instead of specifying amounts, as you would for a standard entry, you use formulas, and Oracle Applications calculates the amounts for you. For example, you might use recurring journal entries to do complex allocations or accruals that are computed using statistics or multiple accounts.

Free On Board (FOB): See FOB.

freeze: To fix the definition of a flexfield or a bill of material at a certain moment in time.

freight carrier: A commercial company used to send product shipments to your customers.

freight charges: A shipment-related charge added during ship confirmation and billed to your customer. (Order Entry QuickCode)

freight terms: An agreement indicating who pays the freight costs of an order and when they are to be paid. Freight terms do not affect accounting freight charges. (Order Entry QuickCode)

function: An AOL feature which uses parameters and assignments to build a key flexfield combination (identified by a CCID) for a particular key flexfield structure. Function names are always predefined. See also assignment, derived parameter, parameter (FlexBuilder), raw parameter.

functional currency

The principal currency you use to record transactions and maintain your accounting data within Oracle Applications. The functional currency is usually the currency in which you perform most of your business transactions. You specify the functional currency for each set of books in the Define Set of Books form.

The principal currency you use to record transactions and maintain your accounting data for your set of books. You define the functional currency for each set of books within your organization. When you enter and pay an invoice in a foreign currency, Oracle Applications automatically converts the foreign currency into your functional currency based on the exchange rate you define. Oracle Applications creates journal entries for your multiple currency invoices and payments in both your foreign and functional currencies.

funding budget: A budget against which accounting transactions are checked for available funds when budgetary control is enabled for your set of books.

funds available

The difference between the amount you are authorized to spend and all actual and anticipated expenditures. In other words, funds available is the amount budgeted less actual expenses and encumbrances of all types. Oracle Financials allow you to check funds available online for requisitions, purchase orders, and invoices. Funds Available = Budget - (Actual Expenses + Encumbrances)

The difference between the amount you are authorized to spend and the amount of your expenditures plus commitments. You can track funds availability at different authority levels using the online funds available inquiry form, or you can create custom reports with the Oracle Applications Financial Statement Generator.

The difference between the amount you are authorized to spend and the amount of your expenditures plus commitments. You can track funds availability at different authority levels using the online funds available inquiry form.

funds checking

The process of certifying funds available.

You can check funds when you enter a requisition, purchase order, or invoice.

You can check funds when you enter actual, budget, or encumbrance journals.

When you check funds, Oracle Financials compares the amount of your transaction against your funds available and notifies you online whether funds are available for your transaction. Oracle Financials does not reserve funds for your transaction when you check funds.

funds reservation

The creation of requisition, purchase order, or invoice encumbrance journal entries. Oracle Applications reserves funds for your invoice when you approve the invoice. AutoApproval creates encumbrance journal entries for an unmatched invoice or for price and quantity variances between an invoice and the purchase order to which you match the invoice. Oracle Applications immediately updates your funds available balances and creates an encumbrance journal entry which you can post in your general ledger.

The process of reserving funds available. You can reserve funds when you enter actual, budget, or encumbrance journals. When you reserve funds, Oracle Financials compares the amount of your transaction against your funds available and notifies you online whether funds are available for your transaction.

future date: A date you use to record the payment date of a future dated payment document. You only use future dates on payment documents with a future payment method.
Oracle Applications displays the future date on the future dated payment document to inform your supplier and bank when the bank should transfer funds to the supplier's bank. In Oracle Applications the future date of a future dated payment is the same as the scheduled payment due date of the invoices being paid. Oracle Applications also refers to the future date as the Payment Due Date.

G

gain / loss: The profit or loss resulting from the retirement of an asset.

gain or loss: The difference between your invoice amount (expressed in your functional currency) and the amount you need to settle a foreign currency obligation (expressed in your functional currency). You may have a gain or loss on a foreign currency invoice due to changes in the exchange rate between your invoice currency and your functional currency over time.

general ledger date: The date used to determine the correct accounting period for your transactions. The Oracle Applications posting program uses this date when interfacing revenue accounting transactions to your general ledger.

general ledger: The accounting system which tracks the journal entries that affect each account.

General Services Administration: See GSA.

generic agreement: An agreement without a specified customer, so it is available to all customers. See also agreement, customer family agreement.

GL Date

The date used to determine the correct accounting period for your invoice and payment transactions. You assign a GL Date to your invoices during invoice entry and your payments during payment creation.

The end date of the GL Period in which costs or revenue are transferred to Oracle General Ledger. This date is determined from the open or future GL Period on or after the PA Date of a cost distribution line or revenue. For invoices, the GL Date is the date within the GL Period on which an invoice is transferred to Oracle Receivables, and is based on the invoice date.

GL Date range: An accounting cycle which is defined by a beginning and ending GL Date.

global segment prompt: A non-context-sensitive descriptive flexfield segment. Each global segment typically prompts you for one item of information related to the zone or form in which you are working.

global segment value: A response to your global segment prompt. Your response is composed of a series of characters and a description. The response and description together provide a unique value for your global segment, such as J. Smith, Financial Analyst, or 210, Building C.

grace period: See Receipt Acceptance Period.

GSA

(General Services Administration)

A customer classification that indicates the customer is a U.S. government customer and pricing for products on the GSA price sheet should reflect the fixed pricing of the GSA contract. Whenever a product is on the GSA price sheet, it cannot be sold to commercial customers for the same or less price than the government customer.

guarantee: A contractual obligation to purchase a specified amount of goods or services over a predefined period of time.

H

hard limit: An option for an agreement that prevents revenue accrual and invoice generation beyond the amount allocated to a project or task by the agreement. If you do not impose a hard limit, Oracle Projects automatically imposes a soft limit of the same dollar amount. See also soft limit.

historical exchange rate: A weighted-average rate for transactions that occur at different times. Oracle Applications uses historical rates to translate owner's equity accounts in accordance with FASB 52 (U.S.). For companies in highly inflationary economies, Oracle Applications uses historical rates to remeasure specific historical account balances, according to FASB 8.

hold

An Oracle Applications feature that prevents a transaction from occurring or completing until the hold has been released. You can place a hold on an invoice or an invoice schedule line in Oracle Applications. All holds in Oracle Applications prevent payment; some holds also prevent posting to your general ledger.

A feature that prevents an order or order line from progressing through the order cycle. You can place a hold on any order or order line.

hold parameter: A criterion you use to place a hold on an order or order line. Valid hold parameters are customer, customer site, order and item.

hold source: An instruction for Oracle Order Entry to place a hold on all orders or lines that meet criteria you specify. Create a hold source when you want to put all current and future orders for a particular customer or for a particular item on automatic hold. Oracle Order Entry gives you the power to release holds for specific orders or order lines, while still maintaining the hold source. Oracle Order Entry holds all new and existing orders for the customer or item in your hold source until you remove the hold source.

hold type: A term that indicates the kind of hold you place on an order or order line. (Order Entry QuickCode)

HP Notation: Mathematical logic upon which EasyCalc is based. HP Notation is used by Hewlett-Packard calculators. HP Notation emphasizes straightforward, logical entry of data, and de-emphasizes complicated parenthetical arrangements of data.

I

import: A utility that enables you to bring data from an export file into an Oracle7 table. The import utility is part of the Oracle7 Relational Database Management System. This utility is used to restore archived data.

import journal entry: A journal entry from a non-Oracle application, such as accounts payable, accounts receivable, and fixed assets. You use Journal Import to import these journal entries from your feeder systems.

integer data type: Any Oracle Financial Analyzer variables with an integer data type containing whole numbers with values between -2.14 billion and +2.14 billion.

import program: A program that imports your bank file from an external system into Oracle Applications. Oracle Applications is set up to work with SQL*Loader as the import program. Two sample SQL*Loader control files are included with Oracle Applications to assist you in writing your own custom control file.

imported invoice

An invoice that is imported into Oracle Applications through the AutoInvoice program.

An invoice that is imported into Oracle Applications through the Invoice Import program.

included item: A mandatory standard item in a bill of material that is shippable, indicating that it ships whenever an order that includes its parent item is shipped. Included items are shippable components of models, kits, option classes, and option items. See also bill of material, pick-to-order, standard item.

income tax region: The region or state you assign to paid invoice distribution lines for a 1099 supplier. If you participate in the Combined Filing Program, Oracle Applications produces K records for all income tax regions participating in the Combined Filing Program that have qualifying payments.

income tax type: A type of payment you make to 1099 suppliers. With Oracle Applications you can assign an income tax type to each paid invoice distribution line for a supplier. The Internal Revenue Service (IRS) requires that you report, by income tax type, payments made to 1099 suppliers

incomplete invoice: An invoice whose status has not been changed to Complete or has failed validation.

indirect project: A project for which you cannot generate revenue or invoices. Generally you use indirect projects for the administration of overhead costs, such as overtime. Typical indirect project types include Bid and Proposal and Overtime.

input VAT: The tax charge on the receipt of taxable goods and services (i.e. Tax on supplier invoices).

installment: One of many successive payments of a debt. You specify how you want payments made when you define your payment terms.

installment number: A number that identifies the installment for a specific transaction.

intraEU, taxed transaction: Transactions between non-registered traders in different EU (European Union) countries. VAT must be charged to customers within the EU, if you do not know their VAT registration number. The Destination country and inventory item controls which VAT rate to use.

intraEU, zero rated transaction: Transactions between registered traders in different EU (European Union) countries. An Intra-EU transaction is zero rated if and only if you know the customer's VAT registration number; otherwise, VAT must be charged on the invoice.

intangible asset: A long term asset with no physical substance, such as a patent, copyright, trademark, leasehold, and formula. You can depreciate intangible assets using Oracle Applications.

intangible item: A non-physical item sold to your customers such as consulting services or a warranty. Intangible items are non-shippable and do not appear on pick slips and pack slips. See also shippable item.

inter-organization transfer: Transfer of items from one inventory organization to another. You can have freight charges and transfer credits associated with inter-organization transfer. You can choose to ship items directly or have them go through in transit inventory.

intercompany account: A general ledger account which you define in an Accounting Flexfield to balance intercompany transactions. You can define multiple intercompany accounts for use with different types of accounts payable journal entries.

intercompany journal entry: A journal entry that records transactions between affiliates. Oracle General Ledger keeps your accounting records in balance for each company by automatically creating offsetting entries to an intercompany account you define.

interest invoice: An invoice that Oracle Applications creates to pay interest on a past-due invoice. Oracle Applications automatically creates an expense distribution line for an interest invoice using an Accounting Flexfield you specify. You cannot modify an interest invoice.

interface table: A temporary database table used for transferring data between applications or from an external application. See also database table.

intermediate value: The parameter value, constant, or SQL statement result that is determined during the first step in the execution of an AutoAccounting rule.

internal organization: See organization.

internal requisition: See internal sales order, purchase requisition.

internal sales order: A request within your company for goods or services. An internal sales order originates from an employee or from another process as a requisition, such as inventory or manufacturing, and becomes an internal sales order when the information is transferred from Purchasing to Order Entry. Also known as internal requisition or purchase requisition.

intransit inventory: Items being shipped from one inventory organization to another. While items are intransit you can view and update arrival date, freight charges, and so on.

inventory controls: Parameter settings that control how Oracle Inventory will function, such as lot, locator, and serial number control.

inventory item: Items that you stock in inventory. You control inventory for inventory items by quantity and value. Typically, the inventory item remains an asset until you consume it. You recognize the cost of an inventory item as an expense when you consume it or sell it. You generally value the inventory for an item by multiplying the item standard cost by the quantity on hand. See also item.

investment tax credit (ITC): A United Sates tax credit that is based on asset cost.

invoice

A document that you create in Oracle Receivables that lists amounts owed for the purchases of goods or services. This document also lists any tax and freight charges.

A document you receive from a supplier that lists amounts owed to the supplier for purchased goods or services. In Oracle Payables, you create an invoice online using the information your supplier provides on the document. Payments, inquiries, adjustments and any other transactions relating to a supplier's invoice are based upon the invoice information you enter.

A summarized list of charges, including payment terms, invoice item information, and other information that is sent to a customer for payment.

invoice batch

A group of invoices you enter together to ensure accurate invoice entry. Invoices within the same batch share the same batch source and batch name. Receivables displays any differences between the control and actual counts and amounts. An invoice batch can contain invoices in different currencies.

An Oracle Applications feature that allows you to enter multiple invoices together in a group. You enter the batch count, or number of invoices in the batch, and the total batch amount, which is the sum of the invoice amounts in the batch, for each batch of invoices you create. You can also optionally enter batch defaults for each invoice in a batch. When you enable your batch control system option, Oracle Applications automatically creates invoice batches for Payables expense reports, prepayments, and recurring invoices, as well as all standard invoices.

invoice burden schedule

A burden schedule used for invoicing to derive the bill amount of an expenditure item. This schedule may be different from your revenue burden schedule, if you want to invoice at a different rate at which you want to accrue.

invoice date

The date that appears on a customer invoice. This date is used to calculate the invoice due date, according to the customer's payment terms.

The date Oracle Applications prints on an invoice. Oracle Applications also use this date to determine the payment due date based on the payment terms you specify on the invoice. Oracle Applications ensures that your invoice date always matches your general ledger date.

The date you assign to an invoice you enter in Oracle Applications. Oracle Applications uses this date to calculate the invoice due date, according to the payment terms for the invoice. The invoice date can be the date the invoice was entered or it can be a different date you specify.

invoice distribution line: A line representing an expenditure item on an invoice. A single expenditure item may have multiple distribution lines for cost and revenue. An invoice distribution line holds an amount, account code, and accounting date.

invoice distribution line types: An Oracle Applications feature which classifies every invoice distribution line as an item, tax, freight, or miscellaneous distribution.

invoice format: The columns, text, and layout of invoice lines on an invoice.

Invoice Import: An Oracle Payables process you use to import invoices from non-Oracle payables systems and to create invoices from Payables expense reports. You can also use Invoice Import to create invoices from expense reports in Oracle Projects.
When you initiate Invoice Import, Oracle Payables imports the required invoice or expense report information and automatically creates invoices with invoice distribution lines from the information. Oracle Payables also produces a report for all invoices or expense reports it could not import.

invoice item

A single line of a project's draft invoice, formatted according to the project invoice formats.

invoice number: A number or combination of numbers and characters that uniquely identifies an invoice within your system. Usually generated automatically by your receivables system to avoid assigning duplicate numbers.

invoice price variance: The difference between the item price for an invoice and its matched purchase order. For your inventory items, Payables tracks any invoice price variances.

invoice quantity variance: The difference between the quantity-billed for an invoice and the quantity-ordered (or received/accepted, depending on the level of matching you use) for its matched purchase order. Payables distributes invoice quantity variances to the Accounting Flexfield for your invoice distribution lines.

invoice set

For each given run of invoice generation for a project, if multiple agreements exist and multiple invoices are created, Oracle Projects creates the invoices within a unique set ID. You approve, release, and cancel all invoices within an invoice set.

invoice split amount

An amount that you determine which represents a breaking point in most your invoice amounts. For example, if your company generates invoices that are either $200 or over $400, then you choose a number between, like $300. When you run your Collection Effectiveness Indicators report you use this information to review how much of your outstanding receivables are over or under your invoice split amount. Oracle Applications calculates counts, amounts, and averages above and below your split term amount.

invoice transaction type

An Oracle Receivables transaction type that is assigned to invoices and credit memos that are created from Oracle Projects draft invoices.

invoice write-off: A transaction that reduces the amount outstanding on an invoice by a given amount and credits a bad debt account.

invoicing

The function of preparing a client invoice. Invoice generation refers to the function of creating the invoice. Invoicing is broader in the terms of creating, adjusting, and approving an invoice.

invoicing rules: Rules that Oracle Payables uses to determine when you bill your invoices. You can bill In Advance or In Arrears.

ITC: See investment tax credit.

ITC amount: The investment tax credit allowed on an asset. The ITC amount is based on a percentage of the asset cost. When you change an asset's cost in the accounting period you enter it, Oracle Assets automatically recalculates the ITC amount.

ITC basis: The maximum cost that Oracle Assets can use to calculate an investment tax credit amount for your asset. If you enabled ITC ceilings for the asset category you assigned to an asset, the ITC basis is the lesser of the asset's original cost or the ITC ceiling.

ITC ceiling: A limit on the maximum cost that Oracle Assets can use to calculate investment tax credit for an asset. You can use different ceilings depending on the asset's date placed in service.

ITC rate: A rate used to calculate the investment tax credit amount. This percentage varies according to the expected life of the asset and the tax year.

ITC recapture: If you retire an asset before the end of its useful life, Oracle Assets automatically calculates what fraction of the original investment tax credit must be repaid to the government. This amount is called the investment tax credit recapture.

item

Anything you make, purchase, or sell including components, subassemblies, finished products, or supplies. Oracle Manufacturing also uses items to represent planning items that you can forecast, standard lines that you can include on invoices, and option classes that you can use to group options in model and option class bills. See also inventory item.

Anything you buy, sell, or handle in your business. An item may be a tangible item in your warehouse, such as a wrench or tractor, or an intangible item, such as a service.

item attribute control level: A method to maintain item attributes at the item master attribute level or the organization specific level by defining item attribute control consistent with your company policies. For example, if your company determines serial number control at headquarters regardless of where items are used, you define and maintain serial number attribute control at the item master level. If each organization maintains serial number control locally, they maintain those attributes at the organization specific level.

item attributes: Specific characteristics of an item, such as order cost, item status, revision control, COGS account, and so on.

item category: Code used to group items with similar characteristics, such as plastic, metal, or glass items.

Item Flexfield: See System Items Flexfield.

item groups: A group of related products that can be added to one or more price list.

Item Validation Organization

The organization that contains your master list of items. You define it by setting the OE: Item Validation Organization profile option.

You must define all items and bills in your Item Validation Organization, but you also need to maintain your items and bills in separate organizations if you want to ship them from other warehouses. Oracle Order Entry refers to organizations as warehouses on all Order Entry forms and reports.

J

job

A name for a set of duties to which an employee may be assigned. You create jobs in Oracle Projects by combining a job level and a job discipline using your job key flexfield structure. For example, you can combine the job level Staff with the job discipline Engineer to create the job Staff Engineer.

job billing title: A job billing title, which differs from a job title, that may appear on an invoice.

job discipline: A categorization of job vocation, used with Job Level to create a job title. For example, a job discipline may be Engineer, or Consultant.

job level: A categorization of job rank, used with Job Discipline to create a job title. For example, a job level may be Staff, or Principal.

job title

A unique combination of job level and job discipline that identifies a particular job.

How your contacts are known in their companies.

journal details tables: Journal details are stored in the database tables GL_JE_BATCHES, GL_JE_HEADERS, and GL_JE_LINES.

journal entry

A debit or credit to a general ledger account.

A debit or credit to a general ledger account. See also manual journal entry.

A debit or credit to a general ledger account.

journal entry batch: A method used to group journal entries according to your set of books and accounting period. When you initiate the transfer of invoice or payment information to your general ledger for posting, Oracle Applications transfers the necessary information to create journal entry batches for the information you transfer. Journal Import in Oracle General Ledger uses the information to create a journal entry batch for each set of books and accounting period.
You can name your journal entry batches the way you want for easy identification in your general ledger. Oracle Applications attaches the journal entry category, date, and time of transfer to your batch name so that each name is unique. If you choose not to enter your own batch name when you transfer posting information, Oracle Applications uses the journal entry category, date, and time of transfer.

journal entry category

A category used to indicate the purpose or nature of your journal entry. Oracle General Ledger associates each of your journal entry headers with a journal entry category. Journal entry categories specify what kind of transaction the journal entry represents.

A category used to indicate the purpose or nature of your journal entry. Oracle General Ledger associates each of your journal entry headers with a journal entry category. There are three journal entry categories in Oracle Applications if you use the accrual basis accounting method: Invoices, Payments, and All (both Invoices and Payments). If you use the cash basis accounting method, Oracle Applications only assigns the Payment journal entry category to your journal entries.

A category in which Oracle Applications describes the purpose or type of journal entry. Standard journal entry categories include accruals, payments, and vouchers.

journal entry header: A method used to group journal entries by currency and journal entry category within a journal entry batch. When you initiate the transfer of invoices or payments to your general ledger for posting, Oracle Applications transfers the necessary information to create journal entry headers for the information you transfer. Journal Import in Oracle General Ledger uses the information to create a journal entry header for each currency and journal entry category in a journal entry batch. A journal entry batch can have multiple journal entry headers.

journal entry lines: Each journal entry header contains one or more journal entry lines. The lines are the actual journal entries that your general ledger posts to update account balances. The number and type of lines in a journal entry header depend on the volume of transactions, frequency of transfer from Oracle Applications, and your method of summarizing journal entries from Oracle Applications.

journal entry source

An indicator of which feeder system your journal entries come from, such as Oracle Applications. Oracle General Ledger associates each of your journal entries with one journal entry source. This allows you to group related journal entry transactions for reporting and analysis in your general ledger.

The source by which Oracle Applications identifies and differentiates the origin of journal entries. Standard journal entry sources include payables, payroll, personnel, and receivables.

Journal Import: An Oracle General Ledger program that creates journal entries from transaction data stored in the Oracle General Ledger GL_INTERFACE table. Journal entries are created and stored in GL_BATCHES, GL_HEADERS and GL_LINES.

jurisdiction code: An abbreviated address that is specific to a Tax Supplier and more accurate than a simple five digit zip code.

K

K-record: A summary record of all 1099 payments made to suppliers for a single tax region that participates in the Combined Filing Program.

key flexfield

An Oracle Applications feature you use to build custom fields in which to enter and display information relating to your business. The Oracle General Ledger Accounting Flexfield is a key flexfield.

An intelligent key that uniquely identifies an application entity. Each key flexfield segment has a name you assign, and a set of valid values you specify. Each value has a meaning you also specify. You use this Oracle Applications feature to build custom fields used for entering and displaying information relating to your business. The Accounting Flexfield in your Oracle General Ledger application is an example of a key flexfield used to uniquely identify a general ledger account.

An Oracle Applications feature you use to build custom fields used for entering and displaying information relating to your business. Oracle Applications uses the following key flexfields: Accounting Flexfield Category Flexfield Location Flexfield Asset Key Flexfield

An Oracle Applications feature you use to build custom fields used for entering and displaying information relating to your business. Oracle Applications uses the following key flexfields: Accounting Flexfield Item Catalogs Item Categories Flexfield Sales Order Flexfield Sales Tax Location Flexfield Stock Locators Flexfield System Items Flexfield Territory Flexfield

An Oracle Applications feature you use to build custom fields used for entering and displaying information relating to your business. Oracle Applications uses the following key flexfields: Accounting Flexfield System Items Flexfield

An Oracle Applications feature you use to build custom fields used for entering and displaying information relating to your business. Oracle Applications uses the following key flexfields: Accounting Flexfield Sales Tax Location Flexfield System Items Flexfield Territory Flexfield

key flexfield segment: One of up to 30 different sections of your key flexfield. You separate segments from each other by a symbol you choose (such as -, / or \.). Each segment can be up to 25 characters long. Each key flexfield segment typically captures one element of your business or operations structure, such as company, division, region, or product for the Accounting Flexfield and item, version number, or color code for the Item Flexfield.

key flexfield segment value: A series of characters and a description that provide a unique value for this element, such as 0100, Eastern region, or V20, Version 2.0.

key indicators

A report that lists statistical receivables and collections information that lets you review trends and projections.

Also an Oracle Applications feature you use to gather and retain information about your productivity, such as the number of invoices paid. You define key indicators periods, and Oracle Applications provides a report which shows productivity indicators for your current and prior period activity.

key member

An employee who is assigned a role on a project. A project key member can view and update project information and expenditure details for any project to which they are assigned. Typical key member types include Project Manager and Project Coordinator.

kit: An item that has a standard list of components (or included items) that you ship when you process an order for that item. A kit is similar to a pick-to-order model because it has shippable components, however it has no options and you order it directly by its item number, not using the configuration selection screen. See also pick-to-order model.

L

labor cost: The cost of labor expenditure items.

labor cost multiplier: A multiplier that is assigned to an indirect project task and applied to labor costs to determine the premium cost for overtime or other factors.

labor cost rate: The hourly raw cost rate for an employee. This cost rate does not include overhead or premium costs.

labor invoice burden schedule

A burden schedule used to derive invoice amounts for labor items.

labor multiplier

A multiplier that is assigned to a project or task, and is used to calculate the revenue and/or bill amount for labor items by applying the multiplier to the raw cost of the labor items.

labor revenue burden schedule

A burden schedule used to derive revenue amounts for labor items.

legal entity: An organization that represents a legal company for which you prepare fiscal or tax reports. You assign tax identifiers and other relevant information to this entity.

lamp

A one-word message that Oracle Applications displays in the message line of any window to notify you that a particular feature is available for a particular field.

A single word message that appears on the message line to indicate whether a function such as <Insert> or <List> is available for the current field.

leasehold improvement: An improvement to leased property or leasehold. Leasehold improvements are normally amortized over the service life or the life of the lease, whichever is shorter.

lien: See commitment, obligation.

life-based depreciation method: A depreciation method which spreads out the depreciation for an asset over a fixed life, usually using rates from a table.

life-to-date depreciation: The total depreciation taken for an asset since it was placed in service. Also known as accumulated depreciation.

line ordering rules: You define line ordering rules for invoice lines that you import into Receivables using AutoInvoice. AutoInvoice uses these rules to order invoice lines when it groups the transactions it creates into invoices, debit memos, and credit memos.

list price: Your base item cost to your customers. You define the item list price on a price list and Oracle Order Entry applies all price adjustments against the item list price.

location

A shorthand name for an address. Location appears in address QuickPicks to let you select the correct address based on an intuitive name. For example, you may want to give the location name of 'Receiving Dock' to the Ship To business purpose of 100 Main Street.

A key flexfield combination specifying a particular place. You assign each asset to a location. Oracle Assets uses location information to produce Responsibility and Property Tax Reports.

Location Flexfield: Oracle Assets lets you define what information you want to keep about the locations you use. You use your Location Flexfield to define how you want to keep the information.

locator: Physical area within a subinventory where you store material. For example, a row, aisle, bin, or shelf.

locator control: A system technique for enforcing use of locators during a material transaction.

lot: A specific batch of an item identified by a number.

lot control: A system technique for enforcing use of lot numbers during material transactions thus enabling the tracking of batches of items throughout their movement in and out of inventory.

M

make-to-order: An environment where customers order unique configurations that must be manufactured using multiple discrete jobs and/or final assembly orders where the product from one discrete job is required as a component on another discrete job. Oracle Manufacturing Release 10 does not provide special support for this environment beyond the support it provides for assemble-to-order manufacturing.

mandatory component: A component in a bill that is not optional. Usually refers to components in an assemble-to-order model or option class bill that are not optional, to distinguish them from options. Mandatory components in pick-to-order model bills are often referred to as included items, especially if they are shippable.

manual invoice: An invoice that is entered through the Transaction or Transactions Summary window.

manual journal entry

A journal entry you enter at a computer terminal. Manual journal entries can include regular, statistical, intercompany and foreign currency entries.

Many-to-Many attribute: In Oracle Financial Analyzer, a relationship between one or more values of one base dimension with one or more values of a second base dimension. For example, if you have a Many-to-Many attribute definition where the first base dimension is Organization and the second base dimension is Line Item, then a single organization can be related to several line items, and a single line item can be related to several organizations.

mask: An Oracle Applications feature which allows you to enter information (dates or figures) in a format other than the format Oracle Applications utilizes. For example, you may wish to store dates in the format DD/MM/YY. You define a DD/MM/YY date mask and Oracle Applications translates entered dates, using the date mask, into a format that Oracle Applications supports. Oracle Applications uses these masks when you create a SQL*Loader control file to load bank file information during AutoClear.

Mass Additions

An Oracle Assets feature which allows you to copy asset information from another system, such as Oracle Payables. Create Mass Additions for Oracle Assets creates mass addition lines for potential assets. You can review these mass addition lines in the Prepare Mass Additions form, and actually create an asset from the mass addition line by posting it to Oracle Assets.

Invoice distribution lines that you transfer to Oracle Assets for creating assets. Oracle Applications only creates mass additions for invoice distribution lines that are marked for asset tracking. Invoice distribution lines distributed to Asset Accounting Flexfields are automatically marked for asset tracking. Oracle Assets does not convert the mass additions to assets until you complete all of the required information about the asset and post it in Oracle Assets.

Mass Change: An Oracle Assets feature which allows you to change the prorate convention, depreciation method, life, rate, or capacity for a group of assets in a single transaction.

mass change order: A record of a plan to replace, delete, or update one or more component items in many bills of material at the same time.

Mass Copy: An Oracle Assets feature which allows you to copy a group of asset transactions from your corporate book to a tax book. Use Initial Mass Copy to create a new tax book. Then use Periodic Mass Copy each period to update the tax book with new assets and transactions.

Mass Depreciation Adjustment: An Oracle Assets feature which allows you to adjust the depreciation expense in the previous fiscal year for all assets in a tax book. Oracle Assets adjusts the depreciation expense between the minimum and maximum depreciation amounts by a depreciation adjustment factor you specify.

Mass Purge: See archive, purge, restore.

Mass Revaluation: See revaluation

Mass Transfers: An Oracle Assets feature which allows you to transfer a group of assets between locations, employees, and general ledger depreciation expense accounts.

MassAllocations: A single journal entry formula that allocates revenues and expenses across a group of cost centers, departments, divisions, and so on. For example, you might want to allocate your employee benefit costs to each of your departments based on headcount in each department.

MassBudgeting: A feature that allows you to build a complete budget using simple formulas based on actual results, other budget amounts, and statistics. For example, you may want to draft next year's budget using last year's actual results plus 10 percent or some other growth factor. With MassBudgeting, you can apply one rule to a range of accounts.

master budget: A budget that controls the authority of other budgets.

master-detail relationship: A master-detail relationship is an association between two blocks--a master block and its detail block. When two blocks are linked by a master-detail relationship, the detail block displays only those records that are associated with the current (master) record in the master block, and querying between the two blocks is always coordinated. Master and detail blocks can often appear in the same window or they can each appear in separate windows.

matching: The process of comparing purchase order, invoice, and receiving information to verify that ordering, billing, and receiving information is consistent within accepted tolerance levels. Oracle Applications uses matching to control payments to suppliers. You can use the matching feature in Oracle Applications if you have Oracle Purchasing or another purchasing system.
Oracle Applications supports two-, three-, and four-way matching. In Oracle Cash Management, matching can be done manually or automatically.

open interface transaction: Any receipt or payment not created by an Oracle Financial Applications system. See also Reconciliation Open Interface

matching tolerances: The acceptable degrees of variance you define for matched invoices and purchase orders. Oracle Applications measures variance between quantities and item prices for invoices and purchase orders. You can define tolerances for order quantities, including Maximum Quantity Ordered and Maximum Quantity Received. You can also define tolerances for price variances, including exchange rate amounts, shipment amounts, and total amounts. If any of the variances between a matched invoice and purchase order exceed the tolerances you specify, AutoApproval places the invoice on hold.

material transaction: Transfer between, issue from, receipt to, or adjustment to an inventory organization, subinventory, or locator. Receipt of completed assemblies into inventory from a job or repetitive schedule. Issue of component items from inventory to work in process.

maturity date: A specific date that determines when funds for an automatic receipt can be transferred from your customer's bank account to your bank account.

maximum depreciation expense: The maximum possible depreciation expense for an asset in a mass depreciation adjustment. The maximum depreciation expense for an asset is the greatest of the depreciation actually taken in the tax book, the amount needed to bring the accumulated depreciation up to the accumulated depreciation in the corporate book, or the amount needed to bring the accumulated depreciation up to the accumulated depreciation in the control book.

memo pad: Area where you write as many notes as you need regarding your conversation with the customer.

message: The text or data that Oracle Alert sends when it finds an exception while running an alert.

message distribution: See distribution list A line on the bottom of your form that displays helpful hints, warning message, and basic entry errors. On the same line, ZOOM, PICK, EDIT, and HELP lamps appear, to let you know when Zoom, QuickPick, Edit, and online help features are available.

message line: A line on the bottom of your form that displays helpful hints or warning messages when you encounter an error. On the same line, ZOOM, PICK, EDIT, and HELP lamps appear, to let you know when Zoom, QuickPick, Edit, and online help features are available.

meta data: Data you enter in Oracle General Ledger to represent structures in Oracle Financial Analyzer. Meta data consists of the dimensions, segment range sets, hierarchies, financial data items, and financial data sets you define in Oracle General Ledger. When you load financial data from Oracle General Ledger, Oracle Financial Analyzer creates dimensions, dimension values, hierarchies, and variables based on the meta data.

model: A set of interrelated equations for calculating data in Oracle Financial Analyzer.

MICR number: An MICR (Magnetic Ink Character Recognition) number identifies your customer to a bank. This number consists of two segments. The first segment is the Transit Routing number, which identifies the bank from which your customer draws their check. The second segment identifies your customer's account at that bank.

minimum accountable unit: The smallest meaningful denomination of a currency (this might not correspond to the standard precision). While a currency may require a precision of three places to the right of the decimal point, .001(one thousandth), the lowest denomination of the currency may represent 0.025 (twenty-five thousandths). Under this example, the Minimum Accountable Unit would be .025. Calculations in this currency would be rounded to .025 (the Minimum Accountable Unit), not .001 (the precision).

min-max planning: An inventory planning method used to determine when and how much to order based on a fixed user-entered minimum and maximum inventory levels.

minimum depreciation expense: The minimum possible depreciation expense for an asset in a mass depreciation adjustment. The minimum depreciation expense for an asset in a tax book is the amount needed to bring the accumulated depreciation up to the accumulated depreciation in the corporate book or control book, or zero, whichever is greater.

minimum interest amount: The amount below which Oracle Applications does not pay interest on an overdue invoice. Oracle Applications automatically compares the interest amount it calculates on past due invoices with the minimum interest amount you have defined, and does not create an interest invoice unless the amount of interest exceeds the minimum interest amount.

modal window: Certain actions that you perform may cause a modal window to display. A modal window requires you to act on its contents before you can continue, usually by choosing OK or Cancel.

model: (model item) An item whose bill of material lists options and option classes available when you place an order for the model item.

model bill of material: A bill of material for a model item. A model bill lists option classes and options available when you place an order for the model item.

model invoice: An invoice that is used as a template to create your recurring invoices.

multiple payment formats: You can choose from several payment methods to pay your supplier invoices. Within each payment method you can define as many payment formats as you want. A payment format determines your payment creation and remittance advice programs.

N

natural account segment: In Oracle General Ledger, the segment that determines whether an account is an asset, liability, owners' equity, revenue, or expense account. When you define your chart of accounts, you must define one segment as the natural account segment. Each value for this segment is assigned one of the five account types.

Natural Application Only: A Transaction Type parameter that, if enabled, does not let you apply a transaction to a debit item if the application will reverse the sign of the debit item (for example, from a positive to a negative balance). Natural Application does not apply to chargebacks and adjustments. See Overapplication.

navigation preference set: A series of user-defined navigational options in the Enter Orders and Enter Return Material Authorizations forms. You can define as many navigation preference sets as you want and assign one to each order type.

nesting: The act of grouping calculations to express the sequence of routines in a formula. Traditional mathematical nesting uses parenthesis and brackets. Oracle Applications EasyCalc uses a straightforward and logical nesting method that eliminates the need for parenthetical expressions.

net allocation: Allocation in which you post the net of all allocations to an allocated-out account.

non-labor invoice burden schedule

A burden schedule used to derive invoice amounts for non-labor items.

non-labor resource

An implementation- defined asset or pool of assets. For example, you can define a non-labor resource with a name such as PC to represent multiple personal computers your business owns.

non-labor revenue burden schedule

A burden schedule used to derive revenue amounts for non-labor items.

non-posting hold: A hold that prevents you from paying your invoice, but allows posting. All holds prevent payment but you can decide if you want to allow or disallow posting for each hold you define.

non-quota sales credit: See non-revenue sales credit

non-revenue sales credit: Sales credit you assign to your salespeople that is not associated to your invoice lines. This is sales credit given in excess of your revenue sales credit. See also revenue sales credit.

O

object: A region in Order Entry such as order, line, shipment schedule, and so on. You can provide Security Rules for objects. See also attribute, default value, security rules,standard value rule set.

obligation

An encumbrance you record when you turn a requisition into a purchase order.

One-to-Many attribute: A relationship in Oracle Financial Analyzer where one or more values of a base dimension are related to a single value of an aggregate dimension. For example, if you have a One-to-Many attribute definition where the base dimension is Organization and the aggregate dimension is Level, each organization can be related to only a single level.

offset account: An offset account is used to balance journal entries in your General Ledger. For example, offsetting accounts for a guarantee are the Unbilled Receivables and the Unbilled Revenue accounts.

on account: Payments where you intentionally apply all or part of the payment amount to a customer without reference to a debit item. On account examples include prepayments and deposits.

on account credits: Credits that you assign to your customer's account that are not related to a specific invoice. You can create on account credits in the Transaction window or through AutoInvoice.

on account payment: The status of a payment of which you apply all or part of its amount to a customer without reference to a specific debit item. Examples of these are prepayments and deposits.

one time billing hold: A type of hold that places expenditure items and events on billing hold for a particular invoice; when you release that invoice, the items are billed on the next invoice.

operating unit: An organization that partitions data for subledger products (AP, AR, PA, PO, OE). It is roughly equivalent to a single pre-Multi-Org installation.

one-time note: A unique message you can attach to orders, returns, order lines and return lines to convey important information. See also standard note.

online processing: When, during the processing of a single process, no further input is allowed until the process is complete.

open batch: Status of a batch that is in balance, but contains unapplied or unidentified payments.

open items: Any item such as an invoice, debit memo, credit memo, chargeback, on account credit, on account payment, or unapplied payment whose balance due is not yet zero.

operator: A mathematical symbol you use to indicate the mathematical operation in your calculation.

option: See option item.

option class: A group of related option items. An option class is orderable only within a model. An option class can also contain included items.

option class bill of material: A bill of material for an option class item that contains a list of related options.

option class item: An item whose bill of material contains a list of related options.

option group: An option group is a set of option buttons. You can choose only one option button in an option group at a time, and the option group takes on that button's value after you choose it. An option button or option group is also referred to as a radio button or radio group, respectively.

option item: A non-mandatory item component in an option class or model bill of material.

Oracle7 tables: A table is a two-dimensional graphic representation of data consisting of columns and rows. Categories of information are listed across the top of each table, while individual listings of information are listed down the left side. In this format, you can readily visualize, understand, and use the information. Oracle Financials products use Oracle7 tables to store the information you need to run your business.

order cycle: An order cycle is a sequence of actions you or Oracle Order Entry perform on an order to complete the order. An order cycle lets you define the activity an order follows from initial entry through closing. You can define as many order cycles as your business requires. Order cycles are assigned to order types. See also action result.

order cycle action: See cycle action.

order date: The date upon which an order for goods or services is entered.

order scheduling: See scheduling.

order type: A classification of an order. In Oracle Order Entry order type controls order cycle, order numbering source, point in the cycle to credit check, transaction type, standard value rule set and navigation preference set of an order.

OrderImport: An Oracle Order Entry open interface that allows you to import your transaction information from an original system into Oracle Applications. See also feeder program.

organization

A business unit such as a plant, warehouse, division, department, and so on. Oracle Order Entry refers to organizations as warehouses on all Order Entry forms and reports.

A business unit such as a company, division, or department. Organization can refer to a complete company, or to divisions within a company. Typically, you define an organization or a similar term as part of your account when you implement Oracle Financials.

Internal organizations are divisions, groups, cost centers or other organizational units in a company. External organizations can include the contractors your company employs. Organizations can be used to demonstrate ownership or management of functions such as projects and tasks, non-labor resources, and bill rate schedules.

P

PA Date: The end date of the PA Period in which costs are distributed, revenue is created, or an invoice is generated. This date is determined from the open or future PA Period on or after the latest date of expenditure item dates and event completion dates included in a cost distribution line, revenue, or an invoice.

PA Period: See Project Accounting Period

PA Period Type

The Period Type as specified in the PA implementation options for Oracle Projects to copy project accounting periods. Oracle Projects uses the periods in the PA Period Type to populate each Operating Unit's PA periods. PA periods are mapped to GL periods which are used when generating accounting transactions. PA periods drive the project summary for Project Status Inquiry. You define your accounting periods in the Operating Unit's Set of Books Calendar.

pack slip: An external shipping document that accompanies a shipment itemizing in detail the contents of that shipment.

packing instructions: Notes that print on the pack slip. These instructions are for external shipping personnel. For example, you might wish to warn your carriers of a fragile shipment or your customer's receiving hours.

parallel processing: Parallel processing allows segments of a program to be processed by different processors at the same time to reduce the overall time to complete the program.

parameter (FlexBuilder): A parameter is a source of values that you can assign, directly or indirectly, to key flexfield segments using FlexBuilder in Oracle Applications. See also assignment, derived parameter, function.

parameter (report): See report parameter.

parent asset: A parent asset has one or more subcomponent assets. First you add the parent asset. Then, you add the subcomponent asset and assign it to the parent asset in the Additions form. You can change parent/subcomponent relationships at any time.

parent request: A concurrent request that submits other concurrent requests (child requests). For example, a report set is a parent request that submits reports and/or programs (child requests.)

parent segment value

An account segment value that references a number of other segment values, called child segment values. Oracle Applications uses parent segment values for creating summary accounts, for reporting on summary balances, and in MassAllocations and MassBudgeting. You can create parent segment values for independent segments, but not for dependent segments.

An Accounting Flexfield segment value that references a number of other segment values, referred to as children segment values. Oracle Applications uses parent segment values for creating Accounting Flexfields that summarize others and for creating summary reports.

Oracle Financial Analyzer uses parent and child segment values to create hierarchies.

An Accounting Flexfield segment value that references a number of other segment values, referred to as children segment values. Oracle Applications uses parent segment values for creating Accounting Flexfields that summarize others and for creating summary reports.

Q

quarter average-to-date: The average of the end-of-day balances for a related range of days within a quarter.

quantity on hand: Current quantity of an item in inventory.

query: A search for applications information that you initiate using an Oracle Applications form.

Quick Check: See Quick payment.

Quick payment: An Oracle Applications feature you use to create an automatic payment on demand. With Quick payment, you choose the invoices you want to pay, and Oracle Applications creates the check on a printer you choose. You can also void and reissue a Quick payment if your printer spoils it while printing.

Quick Release: An Oracle Applications feature you can use to release all user-assigned and many system-assigned invoice holds. You can define and apply unlimited approval criteria to an invoice, and you can then use QuickRelease to release all holds for a particular invoice, batch, or supplier with a single keystroke.

QuickCash: An Oracle Payables feature that enables you to enter receipts quickly. After you use QuickCash to enter your receipts, you post your payment batches to your customer accounts with PostQuickCash.

QuickCodes

Codes that you define for the activities and terminology you use in your business.

For example, you can define QuickCodes for personal titles, so you can refer to people using titles you define.

For example, you can define QuickCodes for sales channels so that you can specify the various sales channels used for different kinds of orders.

An Oracle Assets feature which allows you to enter standard descriptions for your business. You can enter QuickCode values for your Property Types, Retirement Types, Asset Descriptions, Journal Entries, and Mass Additions Queue Names.

An Oracle Applications feature which you use to create reference information you use in your business. This reference information appears in QuickPick lists for many of the fields in Oracle Applications forms. There are three basic kinds of QuickCodes: supplier, payables, and employee. With QuickCodes you can create Pay Groups, supplier types, and other references used in Oracle Applications.

quota sales credits: See revenue sales credit, non-revenue sales credit.

R

raw costs

Costs that are directly attributable to work performed. Examples of raw costs are salaries and travel expenses.

raw parameter: A parameter that FlexBuilder gets directly from a form or program in Oracle Applications. Some raw parameters you can assign directly to key flexfield segments; others you can use to derive other parameters. You cannot define raw parameters; Oracle Applications provides them for you. See also assignment, derived parameter, function, parameter (FlexBuilder).

realized gain: For foreign currency entries, a realized gain is the difference in your functional currency between the invoiced amount and the payment amount, if the payment in functional currency is less than the invoiced amount.

realized gain or loss: For foreign currency entries, the realized gain or loss is the difference in your functional currency between the invoiced amount and the payment amount. The difference is caused by fluctuations in exchange rates between the invoice date and payment date. A realized gain exists if the payment in your functional currency is less than the invoiced amount. A realized loss exists if the invoiced amount in your functional currency is less than the amount of the payment.

realized loss: For foreign currency entries, a realized loss is the difference in your functional currency between the invoiced amount and the payment amount, if the invoiced amount in functional currency is less than the amount of the payment.

reasons: Standard definitions that you can customize to clarify your adjustment entries, debit memos, customer responses, invoices, credit memos, payment reversals and on account credits from Invoice Interface. Use reasons to improve the quality of your reporting.

receipt acceptance period: The number of days you allow for acceptance or rejection of goods. Oracle Applications uses this to recalculate invoice scheduled payments. You specify receipt acceptance days when you define your Financials options.

receipt batch source

A name that you use to refer to how your company accounts for receipts. Receipt batch sources relate your receipt batches to both the bank and the accounting information required for recording and posting your receipts.

receipt class: Automatic receipt processing steps that you relate to your payment methods. You can choose whether to confirm, remit and clear automatic receipts.

receipt grace days: A number of grace days that you assign to your customers and sites to effectively extend the due dates for their outstanding debit items.

receipt source

Your name for a source from which your company receives cash. Your receipt sources determine the accounting for payments that are associated with them. Receipts that you deposit in different banks belong in different payment sources.

receipts: These include applied and unapplied receipts entered within the GL date range that you specified. If the receipt is applied within the GL date range that you specified, it will appear in the Applied Receipts register, otherwise it will appear in the Unapplied Receipt Register. See Cross Site and Cross Customer Receipts.

receivable activities: Predefined Oracle Applications activities used to define the general ledger accounts with which you associate your receivables activities

receivables activity name: A name that you use to refer to a receivables activity. You use your receivables activities during the setup process to create accounting distributions for payments, other receipt payments, receivables adjustments, discounts, receivables accounts, and finance charges.

received quantity: The quantity of an inventory item returned by a customer for which you are not issuing a credit. Sometimes this is temporary, while you evaluate the condition of the item, other times you return the items to the customer, or keep them but do not allow a credit. See also accepted quantity.

receiving and inspection: A condition of a returned inventory item signifying it has been received but is being inspected for damage. If in acceptable condition, the items are transferred to stock and a credit can be issued. If unacceptable, the items can be returned to the customer or scrapped.

recipient: A person to whom Oracle Alert sends a message. The recipient may receive a message through electronic mail or via a printer.

reciprocal customer relationship

An equal relationship shared between two customers. Both customers can enter invoices against each others commitments as well as pay off each others debit items.

An equal relationship shared between two customers. Both customers share agreements, enter invoices against each others commitments, as well as pay off each others debit items.

reconciliation

Reconciliation is an analysis which explains the difference between two balances. If you are using the Reconcile Receipts form, reconciled payments have an associated cleared date and amount. If you are using Cash Management to reconcile receipts, payments are reconciled when they are matched to a bank statement line. The rollforward formula is the following: beginning balance + sale and payment (invoices, credit memos, debit memos, deposits, guarantees, payments and reversed payments entered with GL Dates within the specified GL Date range)+ adjustments (entered with GL Dates within the specified GL Date range - credit memo application (CM applications entered with GL Dates within the specified GL Date range) - payment application (CASH applications entered with GL Dates within the specified GL Date range) = Ending Balance

The process of matching and clearing your bank account statement lines with payments and receipts entered in Payables and Receivables. A reconciled document has been matched to a bank statement line in Cash Management. Oracle Applications inserts a cleared date and amount for all payments that your bank reports as cleared.

reconciliation: The process of matching and clearing bank account statement lines with payments and receipts entered in Oracle Payables and Oracle Receivables. See also reconciliation tolerance.

Reconciliation Open Interface: The database interface table that must be populated if you want to use Oracle Cash Management to reconcile receipts and payments transactions that originate in non-Oracle receivables and payables feeder systems. See also open interface transaction

reconciliation tolerance: A variance amount used by Cash Management's AutoReconciliation program to match bank statement lines with receivables and payables transactions. If a transaction amount falls within the range of amounts defined by a bank statement line amount, plus/minus the reconciliation tolerance, a match is made. See also AutoReconciliation

record: A record is one occurrence of data stored in all the fields of a block. A record is also referred to as a row or a transaction, since one record corresponds to one row of data in a database table or one database transaction.

record code: An Oracle Applications feature you use to describe bank records before initiating automatic account reconciliation from a bank tape. You define the record codes based on those your bank provides, and Oracle Applications uses them to load bank account information from a tape or diskette. For example, your bank may use record codes R01, R02, and R03 to represent outstanding check, bank originated entry (wire transfer), and paid check.

recoverable cost: The lesser of the cost ceiling or the current asset cost less the salvage value and ITC basis reduction amount. Recoverable cost is the total amount of depreciation you are allowed to take on an asset throughout its life.

recurring formula: See recurring journal entry.

recurring invoice: An Oracle Applications feature you use to create invoices for an expense which occurs regularly and is not usually invoiced. Monthly rents and lease payments are examples of typical recurring payments. You define recurring invoice templates, and Oracle Applications lets you define recurring invoices using these templates. See also recurring rule.

recurring journal entry: A journal entry you define once; then, at your request, Oracle Applications repeats the journal entry for you each accounting period. You use recurring journal entries to define automatic consolidating and eliminating entries. Also known as recurring formula.

recurring rule: A rule that is applied to the model invoice to determine the invoice dates of the recurring invoices. You can choose Annually, Bi-Monthly, Days, Monthly, Quarterly, Semi-Annually, Single Copy, and Weekly.

recurring schedule: A schedule used to determine the number of recurring invoices created. You specify the recurring rule and number of recurring invoices you want to create.

reference designator: An optional identifier you can assign to a component on a bill. For example, when the bill requires four of a component, you can assign four reference designators to that component, one for each usage.

reference document type: The kind of source used to provide default information on a return, such as a sales order, purchase order entered on a sales order, or an invoice. See also reference source.

reference field: A field from which you can obtain the default context field value for your context prompt. The reference field you use for a particular descriptive flexfield is always located in the zone or form that contains the descriptive flexfield.

reference source: Provides default information on a return by allowing the user to enter a unique combination of reference document type, document number and line number, that identifies the original sales order for the returning item. See also reference document type.

region: A collection of logically-related fields set apart from other fields by a dashed line that spans a block. Regions help to organize a block so that it is easier to understand.

related transaction

Additional transactions that are created for labor transactions using the Labor Transaction Extension. All related transactions are associated with a source transaction and are attached to the expenditure item ID of the source transaction. You can identify and process the related transactions by referring to the expenditure item ID of the source transaction. Using labor transaction extensions, you can create, identify, and process the related transactions along with the source transaction.

relationship: An association you can create between two or more customers in Receivables to make payment applications easier. See also reciprocal customer relationship.

relative amount: The amount that represents the numerator for the ratio used to determine the amount due. You specify your relative amount when you define your payment terms.
Amount Due = Relative Amount/Base Amount * Invoice Amount

release

An actual order of goods or services you issue against a blanket purchase order. The blanket purchase order determines the characteristics and prices of the items. The release specifies the actual quantities and dates ordered for the items. You identify a release by the combination of blanket purchase order number and release number.

See Pick Release.

release code: The release name Oracle Applications or you assign when releasing a hold from an invoice.

release reason: Justification for removing a hold on an order or order line. (Order Entry QuickCode)

released date: The date on which an invoice and its associated revenue is released.

remit to addresses: The address to which your customers remit their payments.

remittance advice: A document that lists the invoices being paid with a particular payment document. You can create and define remittance advices which you can use with any payment format or you can use a standard remittance advice that Oracle Applications provides.

remittance bank: The bank in which you deposit your receipts.

reorder point planning: An inventory planning method used to determine when and how much to order based on customer service level, safety stock, carrying cost, order setup cost, lead time and average demand.

replacement order: A sales order created to replace goods being returned by a customer.

replenish-to-order: See assemble-to-order (ATO).

report

An organized display of Oracle Applications information. A report can be viewed online or sent to a printer. The content of information in a report can range from a summary to a complete listing of values.

A combination of at least a row set and column set, and optionally a content set, display group, row order, and runtime options, such as currency and override segment name, that you can define and name. When you request financial statements, you can enter this name, and Oracle Applications automatically enters the report components and runtime options for you. You simply specify the accounting period. Oracle Applications automatically enters the rest.

resource: A user-defined group of employees, organizations, jobs, suppliers, expenditure categories, revenue categories, expenditure types, or event types for purposes of defining budgets or summarizing actuals.

report component: An element of a Financial Statement Generator report that defines the format and content of your report. Report components include row sets, column sets, content sets, row orders, and display sets. You can group report components together in different ways to create custom reports.

report headings

A descriptive section found at the top of each report giving general information about the contents of the report.

Report headings provide you with general information about the contents of the report. Report headings provide you with the name of the Set of Books selected for all Oracle Applications transactions and reports. Oracle Applications prints the name of your Set of Books in the heading of most reports.

report option: See report parameter.

report parameter

Most Oracle Applications reports offer options for sorting, formatting, selecting, and summarizing the information in your report.

A variable you use to restrict information in a report, or determine the format of the report. For example, you may want to limit your report to the current month, or display information by supplier number instead of supplier name. Most standard reports in Oracle Applications that you can submit manually have a set of report parameters.

report security group: A feature that helps your system administrator control your access to reports and programs. Your system administrator defines a report security group which consists of a group of reports and/or programs and assigns a report security group to each responsibility that has access to run reports using Standard Report Submission. When you submit reports using Standard Report Submission, you can only choose from those reports and programs in the report security group assigned to your responsibility.

report set: A group of reports that you submit at the same time to run as one transaction. A report set allows you to submit the same set of reports regularly without having to specify each report individually. For example, you can define a report set that prints all of your regular month-end management reports.

reporting currency: The currency you use for financial reporting. If your reporting currency is not the same as your functional currency, you can use foreign currency translation to restate your account balances in your reporting currency.

reporting hierarchies: Summary relationships within an account segment that let you group detailed values of that segment to prepare summary reports. You define summary (parent) values that reference the detailed (children) values of that segment.

ReqExpress: An Oracle Purchasing feature you use to create requisitions quickly and easily from a standard template. Using ReqExpress, you can create a requisition by entering as little as item quantities and accounting information.

ReqImport: An Oracle Purchasing feature you use to automatically import requisitions from other Oracle applications or your existing non-Oracle systems. ReqImport lets you integrate Oracle Purchasing quickly with new or existing applications such as Material or Distribution Requirement Planning system. You can import requisitions as often as you want. Then, you can review, reject, or place these requisitions on purchase orders.
You cannot use ReqImport if you are using requisition encumbrance.

request date: The date the customer requests the products be either shipped or received.

request for quotation (RFQ): A document you use to solicit supplier quotations for goods or services you need. You usually send a request for quotation to many suppliers to ensure that you get the best price and terms possible. Depending on the way you do business, you can use two general types of RFQs: specific and generic.

requirement date: The date when the requirement needed by the discrete job or repetitive schedule is to be consumed. Requirement dates are defaulted to the start date of the operation where a requirement is consumed.

requisition: See purchase requisition.

requisition encumbrance: A transaction representing an intent to purchase goods and services as indicated by the completion and approval of a requisition. Oracle Purchasing subtracts requisition encumbrances from funds available when you reserve funds for a requisition. If you cancel a requisition, Oracle Purchasing creates appropriate reversing entries in your general ledger. Also known as commitment, pre-encumbrance or pre-lien.

reservation: A guaranteed allotment of product to a specific sales order. A hold is placed on specific items that assures that a certain quantity of an item is available on a certain date when transacted against a particular charge entity. Once reserved, the product cannot be allocated to another sales order or transferred in Inventory. Oracle Order Entry checks ATR (Available to Reserve) to verify an attempted reservation. Also known as hard reservation. See also Available to Reserve.

Reserve for Encumbrance: A portion of fund balance you use to record anticipated expenditures. In Oracle Financials, you define your Reserve for Encumbrance account when you define your set of books. Oracle Financials uses your Reserve for Encumbrance account to create offsets for unbalanced encumbrance entries you create in Oracle Purchasing, Oracle Payables, and Oracle General Ledger.

Reserve for Encumbrance account: The account you use to record your encumbrance liability. You define a Reserve for Encumbrance account when you define your set of books. When you create encumbrances automatically in Oracle Purchasing or Oracle Applications, Oracle General Ledger automatically creates a balancing entry to your Reserve for Encumbrance account as you post your encumbrance journal entries. Oracle General Ledger overwrites the balancing segment for your Reserve for Encumbrance account, so you automatically create the reserve for encumbrance journal entry to the correct company.

responsibility

A level of authority in an application. Each responsibility lets you access a specific set of Oracle Applications forms, menus, reports, and data to fulfill your role in an organization. Several users can share the same responsibility, and a single user can have multiple responsibilities.

A level of authority within Oracle Applications. Each responsibility provides a user with access to a menu and a set of books. You can assign one or more responsibilities to each user. Responsibilities let you control security in Oracle Applications.

responsibility report

A financial statement containing information organized by management responsibility. For example, a responsibility report for a cost center contains information for that specific cost center, a responsibility report for a division manager contains information for all organizational units within that division, and so on. A manager typically receives reports for the organizational unit(s) (such as cost center, department, division, group, and so on) for which he or she is responsible.

responsibility type: See process responsibility type.

restore: To restore a fiscal year is to reload the depreciation expense and adjustment transaction records for that fiscal year into Oracle Assets from a storage device. You can only restore the most recently purged fiscal year.

result: See action result.

retroactive addition: See prior period addition.

retroactive reinstatement: See prior period reinstatement.

retroactive retirement: See prior period retirement.

retroactive transfer: See prior period transfer.

return: The opposite of a sales order, it involves receipt of goods previously sold to a customer, credit to a customer, and possibly replacement with an identical or similar product. 'Return' is often used synonymously with 'RMA'. See also Return Material Authorization (RMA).

Return (of) Material Goods: (RMG) See Return Material Authorization.

Return Material Authorization: (RMA) Permission for a customer to return items. Oracle Applications allows you to authorize the return of your sales orders as well as sales made by other dealers or suppliers, as long as the items are part of your item master and price list. 'RMA' is often used synonymously with 'Return'. See also return.

return reason: Justification for a return of product. Many companies have standard reasons that are assigned to returns to be used to analyze the quantity and types of returns. See also credit memo reasons.

revaluation

See foreign currency revaluation.

An Oracle Assets feature which allows you to adjust the cost of your assets by a revaluation rate. The cost adjustment is necessary due to inflation or deflation. You can define revaluation rules for accumulated depreciation, for amortization of revaluation reserve, and for revaluation ceilings.

Restatement of assets of liabilities denominated in a foreign currency using exchange rates that you enter. Fluctuations in exchange rates between the transaction and revaluation dates result in revaluation gains or losses.

revaluation gain/loss account: An income statement account you specify in which Oracle Applications records net revaluation gains and losses, in accordance with FASB 52 (U.S.). You specify the account you want to use for unrealized revaluation gains and losses in the Run Revaluation form. You can change your revaluation gain/loss account as often as you want. When you run revaluation, Oracle Applications creates a batch of revaluation journal entries that adjust your revaluation gain/loss account. Oracle Applications also marks the journal entries for reversal in the next accounting period.

revaluation journal entry: A journal entry that is automatically created when you run revaluation for a range of accounts denominated in a foreign currency. Oracle Applications creates a batch of revaluation journal entries when the exchange rate used for conversion on your transaction date differs from the exchange rate on your balance sheet date. Oracle Applications creates a journal entry to adjust an income statement gain and loss account for exchange rate fluctuations, in accordance with FASB 52 (U.S.).

revaluation status report: A report that summarizes the results of your revaluation. Oracle Applications automatically generates this report whenever you revalue foreign asset and liability account balances for an accounting period in your calendar. You can review this report to identify accounts that were revalued in Oracle Applications and journal batches and entries that were created because of the revaluation.

revenue: In Oracle Projects, the amounts recognized as income or expected billing to be received for work on a project.

revenue accrual

The function of calculating and distributing revenue.

revenue authorization rule

A configurable criterion that, if enabled, must be met before a project can accrue revenue. For example, an active mandatory revenue authorization rule states that a project manager must exist on a project before that project can accrue revenue. Revenue authorization rules are associated with revenue distribution rules. See also revenue distribution rule.

revenue budget

The estimated revenue amounts at completion of a project. Revenue budget amounts can be summary or detail.

revenue burden schedule

A burden schedule used for revenue accrual to derive the revenue amount for an expenditure item. This schedule may be different from your invoice burden schedule, if you want to accrue revenue at a different rate than you want to invoice.

revenue category

An implementation- defined grouping of expenditure types by type of revenue. For example, a revenue category with a name such as Labor refers to labor revenue.

revenue credit

Credit that an employee receives for project revenue.

See revenue sales credit

revenue distribution rule

A specific combination of revenue accrual and invoicing methods that determine how Oracle Projects generates revenue and invoice amounts for a project. See revenue authorization rule.

revenue item

A single line of a project's revenue, containing event or expenditure item revenue summarized by top task and revenue category or event.

revenue recognition: The schedule for which revenue for a particular transaction is recorded in your general ledger.

revenue sales credit: Sales credit you assign to your salespeople that is based on your invoice lines. The total percentage of all revenue sales credit must be equal to 100% of your invoice lines amount. Also known as quota sales credits. See also non-revenue sales credit, sales credit.

revenue write-off

An event type classification that reduces revenue by the amount of the write-off. You cannot write-off an amount that exceeds the current unbilled receivables balance on a project. See also invoice write-off.

reversing journal entry: A journal entry Oracle General Ledger creates by reversing an existing journal entry. You can reverse any journal entry and post it to any open accounting period.

RFQ: See request for quotation.

RFQ Only Site: A supplier site from which you receive quotations.

revision: A particular version of an item, bill of material, or routing.

revision control: An inventory control option that tracks inventory by item by revision and forces you to specify a revision for each material transaction.

RMA: See Return Material Authorization.

RMG: (Return (of) Material Goods) See Return Material Authorization.

rollforward: The process of taking the beginning balance of a period, and then accounting for the transactions within a period by attempting to equate this beginning balance with the ending balance of a period.

rollup group: A collection of parent segment values for a given segment. You use rollup groups to define summary accounts based on parents in the group. You can use letters as well as numbers to name your rollup groups.

root node: A parent segment value in Oracle General Ledger which is the topmost node of a hierarchy. When you define a hierarchy using the Hierarchy window, you specify a root node for each segment. Oracle Financial Analyzer creates a hierarchy by starting at the root node and drilling down through all of the parent and child segment values. See also parent segment value

root window: The root window displays the main menu bar and tool bar for every session of Oracle Applications. In Microsoft Windows, the root window is titled "Oracle Applications" and contains all the Oracle Applications windows you run. In the Motif environment, the root window is titled "Toolbar" because it displays just the toolbar and main menu bar.

routing: A sequence of manufacturing operations that you perform to manufacture an assembly. A routing consists of an item, a series of operations, an operation sequence, and operation effective dates.

row: One occurrence of the information displayed in the fields of a block. A block may show only one row of information at a time, or it may display several rows of information at once, depending on its layout. The term "row" is synonymous with the term "record".

row order

A report component that you use to modify the order of detail rows and account segments in your report. You can rank your rows in ascending or descending order based on the amounts in a particular column and/or by sorting your account segments either by segment value or segment value description. You also specify display options, depending on the row ranking method you choose. For example, if you want to review Total Sales in descending order by product, you can rank your rows in descending order by the Total Sales column and rearrange your segments so that product appears first on your report.

row set

A Financial Statement Generator report component that you build within Oracle Applications by defining all of the lines in your report. For each row, you control the format and content, including line descriptions, indentations, spacing, page breaks, calculations, units of measure, precision and so on. A typical row set includes row labels, accounts and calculation rows for totals. For example, you might define a standard income statement row set or a standard balance sheet row set.

rule numbers: A sequential step in a calculation. You use rule numbers to specify the order in which you want Oracle Applications to process the factors you use in your budget and actual formulas.

S

segments: The building blocks of your chart of accounts in Oracle General Ledger. Each account is comprised of multiple segments. Users choose which segments will make up their accounts; commonly-used segments include company, cost center, and product.

segment values: The possible values for each segment of the account. For example, the Cost Center segment could have the values 100, which might represent Finance, and 200, which might represent Marketing.

selection tools: A set of tools in Oracle Financial Analyzer that provide shortcut methods for selecting the values that you want to work with in a report, graph, or worksheet.

sales channel: A term that indicates the method used to generate a sales order, such as Telemarketing or Direct Marketing. You can use this attribute of an order to classify orders for reporting purposes. (Order Entry QuickCode)

sales credit: Credits that you assign to your salespeople when you enter orders, invoices and commitments. Credits can be either quota or non-quota and can be used in determining commissions. See also non-revenue sales credit, revenue sales credit.

sales tax: A tax collected by a tax authority on purchases of goods and services. The supplier of the good or service collects sales taxes from its customers (tax is usually included in the invoice amount), and remits them to a tax authority. Tax is usually charged as a percentage of the price of the good or service. The percentage rate usually varies by authority and sometimes by category of product. Sales taxes are expenses to the buyer of goods and services.

sales tax structure

The collection of taxing bodies that you will use to determine your tax authority. 'State.County.City' is an example of a Sales Tax Structure. Oracle Applications adds together the tax rates for all of these components to determine a customer's total tax liability for

an order.

a transaction.

salesperson: A person who is responsible for the sale of products or services. Salespeople are associated with orders, returns, invoices, commitments, and customers. You can also assign sales credits to your salespeople.

schedule date: The date the order line should be ready to ship. This date is communicated from Oracle Order Entry to Oracle Inventory as the request date anytime you reserve or place demand for an order line.

schedule fixed date

The date used to freeze bill rate or burden schedules for a project or task. You enter a fixed date to specify that you want to use particular rates or multipliers as of that date. You do not use schedule fixed dates if you want to use the current effective rates or multipliers for a particular schedule.

scheduled payment: A schedule used to determine the amount and date of payment due. You use payment terms to determine your scheduled payment as well as any discounts offered.

scheduling: Order scheduling includes assigning demand or reservations, warehouses, shipment dates, and lots or subinventories to an order line. Scheduling can be done on unbooked orders in the Schedule Details zone of the Enter Orders form or on booked orders in the same zone on the Schedule Orders form.

scrollable region: A region whose contents are not entirely visible in a window. A scrollable region contains a horizontal or vertical scroll bar so that you can scroll horizontally or vertically to view additional fields hidden in the region.

secondary accounting method: The accounting method you choose for your secondary set of books. You can choose either the cash basis or accrual basis accounting methods. Your secondary accounting method cannot be the same as your primary accounting method. You do not need a secondary accounting method if you do not use a secondary set of books.

secondary set of books: The set of books you maintain for reporting purposes. You can run your business using accrual accounting and report on a cash basis, or run your business on a cash basis and report on an accrual basis.

security rules: (Order Entry) The control over the steps in the order process where you no longer allow users to add, delete or cancel order or return lines or change order or return information.

segment: A single sub-field within a flexfield. You define the structure and meaning of individual segments when customizing a flexfield.

selection options: For each report, Oracle Applications provides you with parameters you can choose to make your report as brief as possible. For example, on the Aged Trial Balance - 4 Buckets report, you specify that you want to review the report for a range of customers, or you can specify that you want to review only the aging information for one customer. This feature saves you needless time shuffling through large reports and allows you to retrieve your data in many different ways.

senior tax authority: The first tax location in your sales tax structure. This segment does not have a parent location. For example, if your sales tax structure is 'State.County.City', then State is the senior tax authority.

sequence type: Automatic numbering sequentially assigns a unique number to each transaction as it is created. Manual numbering requires a user to manually assign a unique number to each transaction as it is created. You can skip or omit numbers if desired.

sequencing: A parameter you can set when defining your dunning letter sets to ensure that your customers and sites receive proper notification of past due debit items. Sequencing ensures that a customer receives each of the dunning letters in their dunning letter set in the proper order.

serial number: A number assigned to each unit of an item and used to track the item.

serial number control: A system technique for enforcing use of serial numbers during a material transaction, such as receipt or shipment.

service type: An implementation-defined classification of the type of work performed on a task.

set of books: A financial reporting entity that uses a particular chart of accounts, functional currency and accounting calendar. You must define at least one set of books for each business location.

soft limit: The default option for an agreement that generates a warning when you accrue revenue or generate invoices beyond the amount allocated to a project or task by the agreement, but does not prevent you from running these processes. See also hard limit.

SFAS 52 (U.S.): Statement of Financial Accounting Standards number 52, issued by the Financial Accounting Standards Board (FASB), which dictates accounting and reporting standards for translating foreign currency transactions in the United States. Oracle Applications translates and revaluates such transactions according to SFAS 52 (U.S.) standards. Usually, SFAS 52 (U.S.) mandates the use of a period-end exchange rate to translate asset and liability accounts, and an average exchange rate to translate revenue and expense accounts. Foreign currency denominated assets and liabilities are revalued using a period-end rate on each balance sheet date, to reflect the period-end exchange rate in accordance with SFAS 52 (U.S.). You specify the account used for revaluation gains and losses in the Run Revaluation form. You maintain the rates used for translation and revaluation in the Define Period Rates and Define Historical Rates forms. SFAS 52 (U.S.) also mandates that you post any out-of-balance amounts arising from translation to a Cumulative Translation Adjustment account included in stockholders equity. You define the Cumulative Translation Adjustment account in the Define Set of Books form.

SFAS 8 (U.S.): Statement of Financial Accounting Standards number 8, issued by the Financial Accounting Standards Board (FASB), which mandates that you use a historical exchange rate for all accounts based on past purchase exchanges, and that you use a current exchange rate for all accounts based on current purchase, current sale, and future exchanges. Oracle Applications remeasures specific account balances using historical rates you specify for companies in highly inflationary economies according to the standards of SFAS 8 (U.S.). SFAS 8 (U.S.) also mandates that you record any out-of-balance amounts arising from translation to an income/expense account included in your income statement.

shortdecimal data type: Oracle Financial Analyzer variables with a shortdecimal data type contain decimal numbers with up to 7 significant digits.

shortinteger data type: Oracle Financial Analyzer variables with a shortinteger data type contain whole numbers with values between -32768 and +32768.

Settlement Date: The date before which you cannot apply a prepayment to an invoice. Oracle Applications prevents you from applying a temporary prepayment to an invoice until on or after the Settlement Date of the prepayment.

Shared use assets: When your accounting entities in the same corporate book share the use of an asset, you can apportion depreciation expense to each by percentage or units used.

Ship Confirm: An Oracle Applications feature that allows shipping personnel to verify that they have shipped or backordered the items of an order line.

ship date: The date upon which a shippable item is shipped.

Ship Partial: An order attribute indicating whether you allow partial shipments of an order. If you enter Yes for the Ship Partial field on an order, individual order lines can be shipped as they are available and you can assign different ship to locations and other order line details to different shipments in an order line. See also Ship Together.

ship set: A ship set is a group of order lines, linked by a common number, that you want the full quantity to ship all together. A ship set may include as many items on an order as you want, and one order may contain more than one ship set. Assigning order lines to a ship set allows you to force the full quantity of those order lines to ship simultaneously.

Ship To Address: The address of the customer who is to receive products or services listed on the invoice or order.

Ship Together: An order attribute indicating that you do not allow partial shipments of the order. You can also specify a configuration as Ship Together by setting the Ship Model Complete item attribute for the model item to Yes. See also Ship Partial and ship together model.

Ship Together model: A model item with the Ship Model Complete item attribute set to Yes. This indicates that the entire configuration must be delivered in the same shipment. If the item attribute is set to No, components can ship separately. ATO items and configurations are inherently Ship Together models. See also ship set.

ship via: See freight carrier.

shipment: A shipment is an individual package sent to a customer. Thus, a shipment might contain an entire order, if all items in that order are pick released and packed together. A shipment might contain just part of an order that is pick released and packed. A shipment might also contain only part of a released order line, where some of the items on the picking slip are not in stock.

shipment priority: A term that indicates the urgency with which an order should be shipped to the customer. (Order Entry QuickCode)

shipment schedule: An itemized list of when, how, where and in what quantities to ship an order line.

shippable item: An item with the Shippable inventory item attribute set to Yes, indicating that this item will appear on pick slips and pack slips. See also intangible item.

shipping batch: See picking batch.

shipping documents: Shipping related reports, such as the Bill of Lading, Commercial Invoice, Mailing Label, and Pack Slip.

shipping instructions: Notes that print on the pick slip. These instructions are intended for internal use.

shorthand alias: A user-defined code or character string that represents a complete or partial flexfield value. You can define as many aliases as you need for each key flexfield.

shorthand flexfield entry: A quick way to enter key flexfield data using shorthand aliases (names) that represent valid flexfield combinations or patterns of valid segment values. Your organization can specify flexfields that will use shorthand flexfield entry and define shorthand aliases for these flexfields that represent complete or partial sets of key flexfield segment values.

shorthand window: A single-segment customizable field that appears in a pop-up window when you enter a key flexfield. The shorthand flexfield pop-up window only appears if you enable shorthand entry for that particular key flexfield.

SIC code: (Standard Industry Classification Code) A standard classification created by the government used to categorize your customers.

sign-on: An Oracle Applications username and password that allows you to gain access to Oracle Applications. Each sign-on is assigned one or more responsibilities.

site use: See business purpose.

skeleton entry: A recurring journal entry the amounts of which change each accounting period. You simply define a recurring journal entry without amounts, then enter the appropriate amounts each accounting period. For example, you might define a skeleton entry to record depreciation in the same accounts every month, but with different amounts due to additions and retirements.

source: The origin of imported invoices. When you enter and import an expense report in Oracle Applications, the source is Payables Expense Reports. When you import an expense report from Oracle Projects, the source is Oracle Projects. You can define other sources in Oracle Applications for invoices you import from other accounting systems.

source transaction

For related transactions, the identifying source transaction from which the related items are created.

sourcing: The action of identifying a purchasing source or supplier for goods or services. To identify the best sources for your purchases, you can create RFQs that you send to your suppliers, enter quotations from your supplier, and evaluate these quotations for each item you purchase.

split amount: A dollar amount that determines the number of invoices over and under this amount, as well as the total amounts remaining. For example, your company generates invoices that are either $300 or $500. You choose $400 as your split amount so that you can review how much of your open receivables are comprised of your $300 business and how much corresponds to your $500 business. The split amount appears in the Collection Effectiveness Indicators Report.

split payment terms: An Oracle Applications feature used to automatically schedule multiple payments for an invoice. You can split payments using either a flat amount or a percentage of the total due.

spot exchange rate: A daily exchange rate you use to perform foreign currency conversion. The spot exchange rate is usually a quoted market rate that applies to the immediate delivery of one currency for another.

spreadsheet interface: A program that uploads your actual or budget data from a spreadsheet into Oracle Applications.

standard balance: The usual and customary period-to-date, quarter-to-date, or year-to-date balance for an account. The standard balance is the sum of an account's opening balance, plus all activity for a specified period, quarter, or year. Unlike an average balance, no additional computations are needed to arrive at the standard balance.

standard actions: Oracle Order Entry provides you with a selection of predefined actions, called standard actions. Use these actions, along with those you define yourself, to create your customized order cycles. See also cycle action, order cycle.

standard bill of material: A bill of material for a standard item, such as a manufactured product or assembly. Standard bills contain no optional components. See also bill of material.

standard component: A mandatory component that is used to assemble an ATO (assemble-to-order) item or configuration.

standard entry: A recurring journal entry whose amount is the same each accounting period. For example, you might define a standard entry for fixed accruals, such as rent, interest, and audit fees.

standard item: Any item that can have a bill or be a component on a bill except planning items, option classes, or models. Standard items include purchased items, subassemblies, and finished products.

standard memo lines: An invoice item you predefine to speed invoice entry.

standard note: A routine message you can predefine and automatically or manually attach to orders, returns, order lines and return lines to convey important information. See also one-time note, automatic note.

Standard Request Submission: A standard interface in Oracle Applications in which you run and monitor your application's reports and other processes.

STAT: The statistical currency Oracle General Ledger uses for maintaining statistical balances. If you enter a statistical transaction using the STAT currency, Oracle General Ledger will not convert your transaction amounts.

standard reversal: A payment reversal where Oracle Applications automatically updates your general ledger and re-opens the debit items you closed by reversing the original payment.

standard value: The default value that Oracle Order Entry automatically places in an attribute to improve the efficiency and accuracy with which you enter an order. The standard value for an attribute is frequently based on other values in the order. See also attribute, default value, object, standard value rule set.

standard value rule set: A collection of attributes and associated standard value sources. You associate a rule set with an order type to control the source and priority of default information on the Enter Orders form See also Attribute, Default Value, Object Order Type.

standard value source: The attribute or value Oracle Applications can use to provide a standard value or default for an order attribute.

start organization: An organization which defines a set that includes itself and all subordinate organizations in the organization hierarchy. When you choose a start organization as a report parameter, all organizations below the start organization are included in the report.

statements: Printed documents you send to your customers to communicate their invoice, debit memo, chargeback, deposit, payment, on-account credit, credit memo, and adjustment activity.

statistical journal entry: A journal entry in which you enter nonfinancial information such as headcount, production units, and sales units.

statistical quantity: Statistical information relating to the unit of measure for an invoice distribution line. For example, when you enter invoices for office rent, you can enter Square Feet (or whatever Unit of Measure you define in Oracle General Ledger) in the Unit field for an invoice distribution, and the number of square feet in the Statistical Quantity field for an invoice distribution. Oracle Applications includes the statistical quantity in the journal entries it creates for Oracle General Ledger during posting. You must use Oracle General Ledger in order to define a unit of measure and to be able to enter statistical quantities.

statistics: Accounting information (other than currency amounts) you use to manage your business operations. With Oracle Applications, you can maintain budget and actual statistics and use these statistics with budget rules and formulas.

status: See customer status.

status line: A status line appearing below the message line of a root window that displays status information about the current window or field. A status line can contain the following: ^ or v symbols indicate previous records before or additional records following the current record in the current block; Enter Query indicates that the current block is in Enter Query mode, so you can specify search criteria for a query; Count indicates how many records were retrieved or displayed by a query (this number increases with each new record you access but does not decrease when you return to a prior record); the <Insert> indicator or lamp informs you that the current window is in insert character mode; and the <List> lamp appears when a list of values is available for the current field.

step-down allocation

An allocation upon which you run another allocation. For example, you might allocate parent company overhead to operating companies based on revenues. You can then use a step-down allocation to allocate overhead to cost centers within the operating companies based on headcount.

straight time cost: The monetary amount that an employee is paid for straight time (regular) hours worked.

streamline process: See streamline request.

streamline request: A process which runs multiple Oracle Projects processes in sequence. When using streamline processing, you can reschedule your streamline requests by setting rescheduling parameters. Rescheduling parameters allow you to configure your processes to run automatically, according to a defined schedule. When you reschedule a process, the concurrent manager submits another concurrent request with a status of Pending, and with a start date according to the parameters you define.

structure: A structure is a specific combination of segments for a key flexfield. If you add or remove segments, or rearrange the order of segments in a key flexfield, you get a different structure.

subinventory: A subdivision of an organization or warehouse, representing either a physical area or a logical grouping of items, such as a storeroom or receiving dock.

substitute item: An item that can be used in place of a component. Oracle Master Scheduling/MRP suggests substitutes items on some reports.

subtask: A hierarchical unit of work. Subtasks are any tasks that you create under a parent task. Child subtasks constitute the lowest level of your work breakdown structure; where Oracle Projects looks when processing task charges and for determining task revenue accrual amounts. See task.

summarization: Processing a project's cost, revenue, commitment, and budget information to be displayed in the Project, Task, and Resource Project Status windows. You must distribute costs for any expenditure items, accrue and release any revenue, create any commitments, and baseline a budget for your project before you can view summary project amounts. Formerly known as accumulation.

summary account: An account whose balance represents the sum of other account balances. You can use summary accounts for faster reporting and inquiry as well as in formulas and allocations.

summary message: A summary message is a message representing one or more exceptions. The message includes an introductory paragraph followed by the exceptions listed in a columnar report format.

summary threshold: The number of exceptions after which you want Oracle Alert to send a message for a particular distribution. For example, if you define the threshold at five, and Oracle Alert locates between one and five exceptions, the recipients get one to five separate detail messages. But if Oracle Alert locates six or more exceptions, the recipients get one summary message that includes all the exceptions.

supplier: A business or individual that provides goods or services or both in return for payment.

supplier codes: An Oracle Applications feature you use to define various kinds of supplier information, such as PayGroup and Supplier Type. You can create as many lookup codes for each item as you require. You can add or inactivate Supplier Codes to meet your changing business needs.

SWIFT940: A common format used by many banks to provide institutional customers with electronic bank statements. If your bank provides you with this type of statement, you can use Bank Statement Open Interface to load your bank statement information into Oracle Cash Management. See also Bank Statement Open Interface, bank statement

supplier invoice

An external supplier's invoice entered into Oracle Payables.

system linkage: An obsolete term. See expenditure type class.

supplier number: A number or combination of numbers and characters that uniquely identifies a supplier within your system.

supplier site: A facility maintained by a supplier for the purpose of conducting business. A supplier may have one or many supplier sites.
Payables maintains supplier information regarding each supplier site you define for a supplier. You may define a supplier site as a pay site only, a purchasing site only, both a pay site and a purchasing site, or as an RFQ only site, in which case it may not have purchase orders entered against it. See also pay site, purchasing site, RFQ only site.

supply reserved: A schedule status showing that Oracle Work in Process (WIP) has recognized the demand for an item or configuration and opened a work order to supply the demand. Once the work order is complete and the finished product is received in inventory, WIP transfers a reservation for the finished product to the sales order. The schedule status for the order line or order line detail is then changed to be Reserved.

System Items Flexfield: A flexfield that allows you to define the structure of your item identifier according to your business requirements. You can choose the number and order of segments (such as product and product line), the length of each segment, and much more. You can define up to twenty segments for your item. Also known as Item Flexfield.

T

table-based depreciation method: A depreciation method that uses the table-based method (rates) to calculate depreciation based on the asset life and the recoverable cost or net book value.

tablespace: The area in which an Oracle7 database is divided to hold tables.

task

A subdivision of project work. Each project can have a set of top level tasks and a hierarchy of subtasks below each top level task. See also Work Breakdown Structure, subtask.

task organization: The organization that is assigned to manage the work on a task.

task service type: See service type.

tax authority

A governmental entity which collects taxes on goods and services purchased by a customer from a supplier. In some countries, there are many authorities (e.g. state, local and federal governments in the U.S.), while in others there may be only one. Each authority may charge a different tax rate. You can define a unique tax name for each tax authority. If you have only one tax authority, you can define a unique tax name for each tax rate that it charges.

A governmental entity which collects taxes on goods and services purchased by a customer from a supplier. In some countries, there are many authorities (e.g. state, local and federal governments in the U.S.), while in others there may be only one. Each authority may charge a different tax rate. Within Oracle Applications tax authority consists of all components of your tax structure. For example: (California.San Mateo.Redwood Shores) for (State.County.City) Oracle Applications adds together the tax rates for all of these locations to determine a customer's total tax liabilityorderinvoice.

Tax book: A depreciation book that you use to track financial information for your reporting authorities.

tax codes

Codes to which you assign sales tax or value-added tax rates. Oracle Receivables lets you choose state codes as the tax code when you define sales tax rates for the United States. (Receivables QuickCode)

tax engine: A collection of programs, user defined system parameters, and hierarchical flows used by Oracle Applications to calculate tax.

tax exempt: A customer, business purpose, or item free from tax charges.

Tax Identification Number: In the United States, the number used to identify 1099 suppliers. If a 1099 supplier is an individual, the Tax Identification Number is the supplier's social security number. If a 1099 supplier is a corporation, the Tax Identification Number is also known as the Federal Identification Number.

tax line type: A distribution line used to record a sales or VAT tax charge on an invoice. See also invoice distribution line.

tax location: A specific tax location within your tax authority. For example 'Redwood Shores' is a tax location in the Tax Authority (California.San Mateo.Redwood Shores).

tax tolerances: The acceptable degrees of variance you define for the differences between the calculated tax amount on an invoice and the actual tax amount on the invoice. The calculated tax amount is the amount of tax on the invoice as determined by the tax name for the invoice (which has a defined tax rate) and the amount of the invoice. The actual tax amount is the sum of all the tax distribution lines. If the variance between these two amounts exceeds the tolerances you specify, AutoApproval places the invoice on hold.

tax type: An Oracle Applications feature you use to indicate the type of tax charged by a tax authority when you define tax name. Oracle Applications uses the tax type during invoice entry to determine the financial impact of the tax. When you enter a tax of type Sales, Oracle Applications creates a separate invoice distribution line for the tax amount. When you enter a tax of type Use, Oracle Applications does not create the invoice distribution line.

template: A pattern that Oracle Applications uses to create and maintain summary accounts. For each template you specify, Oracle Applications automatically creates the appropriate summary accounts.

Time dimension: An Oracle Financial Analyzer dimension whose values represent time periods. A time period can be a month, quarter, or year. The length of the Time dimension's values is determined by the Width option on the Maintain Dimension window.

Terms Date Basis: The method that determines the date from which Oracle Applications calculates an invoice scheduled payment. The terms date basis can be Current, Goods Received, Invoice, or Invoice Received.

territory: A feature that lets you categorize your customers or salespeople. For example, you can categorize your customers by geographic region or industry type.

Territory Flexfield: A key flexfield you can use to categorize customers and salespersons.

Time and Materials (T&M): A revenue accrual and billing method that calculates revenue and billings as the sum of the amounts from each individual expenditure item. The expenditure item amounts are calculated by applying a rate or markup to each item.

timecard

A weekly submission of labor expenditure items. You can enter timecards online, or as part of a pre-approved batch.

TIN: See Tax Identification Number.

Tolerance: An Oracle Applications feature you use to specify acceptable matching and tax variances. You can specify either percentage-based or amount-based tolerances or both for quantity and item price variances between matched invoices and purchase orders. You can also specify percentage-based or amount-based tolerances for your tax variances. AutoApproval uses the tolerance levels you define to determine whether to hold or approve invoices for payment. See also Matching Tolerances, Tax Tolerances.

tolerance percentage: The percentage amount by which customers are allowed to exceed their credit limit and still pass the credit check.

toolbar: The toolbar is a collection of iconic buttons that each perform a specific action when you choose it. Each toolbar button replicates a commonly-used menu item. Depending on the context of the current field or window, a toolbar button can be enabled or disabled. You can display a hint for an enabled toolbar button on the message line by holding your mouse steadily over the button. The toolbar generally appears below the main menu bar in the root window.

transaction code: An Oracle Applications feature you use to describe bank transactions prior to initiating automatic reconciliation from a bank tape. You define transaction codes based on those your bank provides, and Oracle Applications uses them to load information from your bank tape. For example, your bank may use transaction codes T01, T02, and T03 to represent debit, credit, and stop payment.

transaction type

An invoice control feature that lets you specify default values for invoice printing, posting, to the general ledger, and updating of open receivable balances.

The kind of action performed on an asset. Transaction types include Addition, Adjustment, Transfer, and Retirement.

transactions: These include invoices, debit memos, credit memos, deposits, guarantees and chargebacks entered with a GL date that is between the beginning and ending GL dates. The transactions are displayed in the Transaction Register in the Functional Currency column.

transferred date: The date on which you transfer costs, revenue, and invoices to other Oracle Applications.

translation

See revaluation.

foreign currency translation.

transmission format: A transmission format defines what data your bank is sending in the bank file, and how that data is organized. In Oracle Applications, you define a transmission format that identifies what types of records you want to import, what data is in each type of record, and the position in which that data is located on the record.

U

unapplied payment: The status of a payment for which you can identify the customer, but you have not applied or placed on account all or part of the payment. For example, you receive a check for $1200.00 and you pay an open debit item for $1000.00. The remaining $200.00 is unapplied until you either apply the payment to a debit item or place the amount On Account.

Unbilled Receivables: The amount of open receivables that have not yet been billed for a project. Oracle Projects calculates unbilled receivables using the following formula: (Unbilled Receivables = Revenue Accrued - Amount Invoice)

unearned discounts: Discounts your customers are allowed to take if they pay for their invoices after the discount date. You specify at the system level whether you want to allow your customer to take unearned discounts.

Unearned Revenue: Revenue received and recorded as a liability or revenue before the revenue has been earned by providing goos or services to a customer. Oracle Projects calculates unearned revenue using the following formula: (Unearned Revenue = Amount Invoiced - Revenue Accrued)

unidentified payment: The status of a payment for which the customer is unknown. Oracle Applications retains unidentified payments for you to process further.

unit: See unit of measure.

unit class: A group of units of measure and their corresponding base unit of measure. The standard unit classes are: Length, Weight, Volume, Area, Time and Pack.

unit of measure

A label for the production quantities for a units of production asset. The unit used to measure production amounts. Each unit of measure belongs to a unit of measure class.

A unit of measure records quantities or amounts of an expenditure item. For example, if you specify the unit Miles when you define an expenditure type for personal car use, Oracle Projects calculates the cost of using a personal car by mileage.

The unit in which the quantity of an item is expressed, such as Each or Dozen.

You can define a unit of measure in Oracle General Ledger and see the unit of measure information in Oracle Applications when matching an invoice to a purchase order. For example, you may want to define a unit of measure for Square Feet and then, when you enter invoices for office rent, you can track the square footage in addition to the dollar amount of the invoice. See also Statistical Quantity.

unit of measure classes: Groups of units of measure with similar characteristics. Typical units of measure classes are Volume and Length.

unit of measure conversions: Numerical factors that enable you to perform transactions in units other than the primary unit of the item being transacted.

units of production depreciation method: A depreciation method which calculates the depreciation for an asset based on the actual production or use for that period. This method uses the asset's actual production for the period divided by the capacity of the asset to determine depreciation. Oracle Applications multiplies this fraction by the asset's recoverable cost.

unrealized gain or loss: The gain or loss you would incur if you paid a foreign currency invoice on a specific date (such as the end of an accounting period). Oracle Applications provides a report (the Unrealized Gain and Loss Report) which you can submit from the standard report submission form at any time to review your unrealized gains and losses. See also realized gain or loss

unscheduling: The removal of the schedule status for an order line or detail if a line or detail is either demanded or reserved; unscheduling will return the status to blank.

UOM: See unit of measure.

usage: See non-labor resource.

usage cost rate override: The cost rate assigned to a particular non-labor resource and non-labor organization which overrides the rate assigned to its expenditure type.

usage logs

Usage logs record the utilization of company assets on projects as the asset is used.

use tax: A tax which you pay directly to a tax authority instead of to the supplier. Suppliers do not include use tax on their invoices. You sometimes owe use tax for goods or services you purchased outside of, but consumed (used) within the territory of a tax authority. Use taxes are liabilities to the buyer of goods and services. You can define a tax name for use taxes. When you enter a use tax name on an invoice, Oracle Applications does not create an invoice distribution or general ledger journal entry for the tax.

user procedures: Oracle Applications provides you with a report set so that you can run through your concurrent manager to generate the reports from the rollforward process. You must specify the report parameters as you are prompted. You must also specify the same GL Date range for all of the reports in the set except for the two aged trial balances. The two aged trial balances reports require that you declare an As Of Date. The As Of Date represents the date that Oracle Applications uses to determine the balance of the transaction. Oracle Applications determines the balance by taking the current balance of an item, and then reversing any transactions against this item that occurred after the As Of Date. You must enter the beginning GL Date of your GL Date range to determine your beginning balance. You must enter the ending GL Date of your GL Date range to determine the ending balance. When the process completes, you should verify the amounts on the reports.

user profile

A set of changeable options that affect the way your applications run. You can change the value of a user profile option at any time.

See profile option.

V

value: Data you enter in a parameter. A value can be a date, a name, or a code, depending on the parameter.

value set: A group of values and related attributes you assign to an account segment or to a descriptive flexfield segment. Values in each value set have the same maximum length, validation type, alphanumeric option, and so on.

value-added tax (VAT): A tax on the supply of goods and services paid for by the consumer, but collected at each stage of the production and distribution chain. The collection and payment of value-added tax amounts is usually reported to tax authorities on a quarterly basis and is not included in the revenue or expense of a company. With Oracle Applications you control the tax names on which you report and the reference information you want to record. You can also request period-to-date value-added tax reports.

variable: An Oracle Financial Analyzer database object that holds raw data. Data can be numerical, such as sales or expense data, or textual, such as descriptive labels for products.

variable text: Variable text is used when dialog boxes or their components are unlabeled or have labels that change dynamically based on their current context. The wording of variable text does not exactly match what you see on your screen.

vendor: See supplier.

void check stock: An Oracle Applications feature you use to void a range of blank check stock.

voucher number: A number used as a record of a business transaction. A voucher number may be used to review invoice information, in which case it serves as a unique reference to a single invoice.

W

warehouse: See organization.

warrant: A warrant is an order by authorized legislative or executive officials directing the treasurer to pay a specific sum to order or to the bearer. It may be payable upon demand, in which case it usually circulates the same as a bank check; or it may be payable only out of certain revenues, when and if received, in which case it does not circulate as freely.

waybill: A document containing a list of goods and shipping instructions relative to a shipment.

waybill number: The number associated with a waybill that you record for the shipping batch at ship confirmation.

weighted-average exchange rate

An exchange rate that Oracle Applications automatically calculates by multiplying journal amounts for an account by the translation rate that applies to each journal amount. You choose whether the rate that applies to each journal amount is based on the inverse of the daily conversation rate or on an exception rate you enter manually. Oracle Applications uses the weighted-average rate, instead of the period-end, average, or historical rates, to translate balances for accounts assigned a weighted-average rate type.

weighted-average translation rate

The rate Oracle General Ledger uses to translate your functional currency into a foreign currency for your transactions. Oracle Applications provides transaction information based on daily rates you enter in the system and rate exceptions you define for individual transactions. This transaction information allows Oracle General Ledger to calculate an accurate weighted-average translation rate.

window: A box around a set of related information on your screen. Many windows can appear on your screen simultaneously and can overlap or appear adjacent to each other. Windows can also appear embedded in other windows. You can move a window to a different location on your screen.

window title: A window title at the top of each window indicates the name of the window, and occasionally, context information pertinent to the content of the window. The context information, contained in parenthesis, can include the organization, set of books, or business group that the window contents is associated with.

WIP: See work in process.

withholding: In some cases, the Internal Revenue Service requires companies to withhold a portion of payments to 1099 suppliers who meet specific criteria. These payments are for federal income tax. Before withholding any payments, you need to inform the supplier in writing. You then send the accumulated withholding amount, with another form, to the Internal Revenue Service once per quarter.

withholding tax group: You can assign one or more Withholding Tax type tax names to a withholding tax group. Assign a withholding tax group to an invoice or distribution line and use Oracle Payables to automatically withhold tax for expense reports and supplier invoices.

withholding tax rate: The rate at which Oracle Payables withholds tax for an invoice distribution line that has a Withholding Tax type tax name assigned to it.

Work Breakdown Structure (WBS)

The breakdown of project work into tasks. These tasks can be broken down further into subtasks, or hierarchical units of work.

work in process: An item in various phases of production in a manufacturing plant. This includes raw material awaiting processing up to final assemblies ready to be received into inventory.

work site

The customer site where project or task work is performed.

write-off: See invoice write-off, revenue write-off.

write-on: An event type classification that causes revenue to accrue and generates an invoice for the amount of the write-on.

X

XpenseXpress: See expense report,

Y

year average-to-date: The average of the end-of-day balances for a related range of days within a year.

year-to-date depreciation: The depreciation taken for an asset so far this fiscal year.

Z

Zoom: An Oracle Applications feature that enables you to suspend processing in one form, access another form, then return to the original form and resume processing where you left off. A ZOOM lamp appears when you enter a field from which you can zoom. Zoom defines the form that you can access from the current field.

Contents

Library