Oracle Apps, ADF, SOA: GLOSSARY

This glossary includes terms that are shared by all Oracle Financial Applications products.

4-4-5 calendar: A calendar with 12 uneven periods: typically two four-week periods followed by one five week period in a quarter. Calendars are defined in General Ledger and Oracle subledger applications.

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 United States 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. Payables stores the tax identification number for each supplier. Payables also lets 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. Payables 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. Payables 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. Payables 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. Payables 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

account: The business relationship that a party can enter into with another party. The account has information about the terms and conditions of doing business with the party.

account combination: A unique combination of segment values that records accounting transactions. A typical account combination contains the following segments: company, division, department, account and product.

Account Generator: A feature that uses Oracle Workflow to provide various Oracle Applications with the ability to construct Accounting Flexfield combinations automatically using custom construction criteria. You define a group of steps that determine how to fill in your Accounting Flexfield segments. You can define additional processes and/or modify the default process(es), depending on the application. See also activity, function, item type, lookup type, node, process, protection level, result type, transition, Workflow Engine

account hierarchy: A hierarchical account structure containing parent and child accounts, where a range of child values roll up to parent accounts. A multi-level parent hierarchy can exist where higher level parents are parents of lower level parents. Parent hierarchies let you define reports using parent values instead of individual child values in Oralce General Ledger. Parent values also facilitate summary account creation to allow you to view summarized account balances online.

account relationship: A relationship that implies financial responsibility between the owners of the accounts. For example, a customer account relationship lets you apply payments to and create invoices for related customers, as well as apply invoices to related customers' commitments.

Account segment

One of up to 30 different sections of your Accounting Flexfield, which together make up your general ledger account combination. 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 site: A site that is used within the context of an account, for example, for billing or shipping purposes.

account structure: See Accounting Flexfield structure.

accounting calendar: The calendar that defines your accounting periods and fiscal years in Oracle General Ledger and subledger applications. Oracle Financial Analyzer will automatically create a Time dimension using your accounting calendar.

accounting currency: In some financial contexts, a term used to refer to the currency in which accounting data is maintained. In this manual, this currency is called functional currency. See functional currency

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. See accrual basis accounting, cash basis accounting, or combined basis accounting.

accounting model: A set of selected individual accounts and account ranges. You can assign a name to an accounting model. Once an accounting model is defined for a particular group of accounts, you can reuse that accounting model whenever you want to work on that group of accounts. Use your accounting models to choose the accounts that you want to adjust when you run the inflation adjustment process. Although there are no rules for grouping accounts, you may want to define different accounting models for different kinds of accounts. For example, you can define one accounting model for all of your asset accounts and another accounting model for all of your liability accounts.

accounting period: A time period that, when grouped, comprises your fiscal year. Periods can be of any length but are usually a month, quarter, or year. Periods are defined in Oracle General Ledger.

Accounting Program: See AX Program.

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 Receivables know how many accounting periods to use for this accounting rule.

accounting rules: Rules that you can use for imported and manually entered transactions to specify revenue recognition schedules. You can define an accounting rule in which 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.

accounting scheme: A set of instructions that tell the translation program how to create accounting entries from an event. The accounting scheme contains information about how to identify a transaction and the data that is transferred from the subledger to Global Accounting Engine and General Ledger.

accrual basis accounting: A method of accounting in which you recognize revenues in the accounting period in which 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 you want 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: See 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.

activity: In Oracle Workflow, a unit of work performed during a business process.

activity: In Oracle Receivables, a name that you use to refer to a receivables activity such as a payment, credit memo, or adjustment. See also activity attribute, function activity, receivables activity name.

activity attribute: A parameter for an Oracle Workflow function activity that controls how the function activity operates. You define an activity attribute by displaying the activity's Attributes properties page in the Activities window of Oracle Workflow Builder. You assign a value to an activity attribute by displaying the activity node's Attribute Values properties page in the Process window.

ad hoc: An unplanned event created for a specific purpose. For example, an ad hoc tax code, report submission, or database query.

address validation: The type of validation you want Receivables 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: A Receivables feature that allows you to increase or decrease the amount due of your invoice, debit memo, chargeback, deposit, or guarantee. Receivables lets you create manual or automatic adjustments.

Adjustments: In the Global Accounting Engine, a feature that lets you enter transactions directly into subledger tables. Global Accounting Engine requires you to enter a third party for control accounts. Your control account balances for your control accounts are updated in sync in both the subledger system and General Ledger.

advance

An amount of money prepaid in anticipation of receipt of goods, services, obligations or expenditures.

advance

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..

agent: In Oracle Cash Management, the customer name or supplier name on a bank statement line.

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.

aging buckets: In Oracle Receivables and Oracle Payables, time periods you define to age your debit items. Aging buckets are used in the Aging 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. Applications Desktop Integrator uses the aging buckets you define for its Invoice Aging Report.

aging buckets: In Oracle Cash Management, aging buckets are used to define time periods represented in the forecast. Examples of aging buckets are date ranges or accounting periods.

agreement: A contract with a customer that 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.

agreement type: 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: A method for distributing existing amounts between and within projects and tasks. The allocation feature uses existing project amounts to generate expenditure items for specified projects.

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

allocation method: An attribute of an allocation rule that specifies how the rule collects and allocates the amounts in the source pool. There are two allocation methods, full allocation and incremental allocation. See also full allocation, incremental allocation

allocation rule: A set of attributes that describes how you want to allocate amounts in a source pool to specified target projects and tasks.

allocation run: The results of the PRC: Generate Allocation Transactions process.

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. This display method has been replaced by tabs in Release 11i and higher.

Always Take Discount: A Payables 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 Payables option that Payables assigns to new suppliers you enter. When Always Take Discount is enabled 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 disabled, you only take a discount if you pay the invoice on or before the discount date.

amount class: For allocations, the period or periods during which the source pool accumulates amounts.

API (Application Programming Interface): A program that verifies data before importing it into an application.

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

approval limits: Limits you assign to users for creating adjustments and approving credit memo requests. Receivables enforces the limits that you define here when users enter receivables adjustments or approve credit memo requests initiated from iReceivables. When users enter adjustments that are within their approval limit, Receivables automatically approves the adjustment. When users enter adjustments outside their approval limit, Receivables 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: A temporary table to which Oracle General Ledger copies your account balances from the Balances Table.

archive table: A temporary table to which Oracle Assets copies depreciation expense and adjustment transaction data for a fiscal year.

archive tablespace: The tablespace where your archive table is stored. A tablespace is the area in which an Oracle 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.

attribute: See activity attribute, item type attribute

attribute: In TCA, corresponds to a column in a TCA registry table, and the attribute value is the value that is stored in the column. For example, party name is an attribute and the actual values of party names are stored in a column in the HZ_PARTIES table.

attribute group: A group of closely related attributes within the same entity. The values for each attribute in a group must come from the same data source.

asset

An object of value owned by a corporation or business. Assets are entered in 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.

AutoAccounting: In Oracle Projects, a feature that automatically determines the account coding for an accounting transaction based on the project, task, employee, and expenditure information.

AutoAccounting: In Oracle Receivables, a 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 Rule: Rules you define for the Global Intercompany System (GIS) in Oracle General Ledger to generate intercompany transactions automatically.

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: A feature used to automatically adjust the remaining balances of your invoices, debit memos, and chargebacks that meet the criteria that you define.

Autoallocations: A feature in Oracle General Ledger that automates journal batch validation and generation for MassAllocations, Recurring Journals, MassBudgets, Project Allocations and MassEncumbrances. You can create parallel and step-down autoallocation sets.

autoallocation set: A group of allocation rules that you can run in sequence that you specify (step-down allocations) or at the same time (parallel allocations). See also step-down allocation, parallel allocation

AutoAssociate: An option that allows you to specify whether you want Oracle Receivables to determine the customer using invoice numbers if the customer cannot be identified from either the magnetic ink character recognition (MICR) number or the customer number. Receivables checks the invoice numbers until it finds a unique invoice number for a customer. Receivables 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, Receivables treats the payment as unidentified. See also MICR number.

AutoCash Rule: A feature that Post QuickCash uses to automatically apply receipts to a customer's open items. 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. See also AutoCash Rule Set, Post QuickCash.

AutoCash Rule Set: A feature that determines the order of the AutoCash Rules that the Post QuickCash program will use when automatically applying receipts to a customer's open items. You can choose to include discounts, finance charges, and items in dispute when calculating your customer's open balance.

AutoClear: Formerly an Oracle Payables feature, this was replaced by Oracle Cash Management features.

AutoReconciliation: An Oracle Cash Management feature that allows you to reconcile bank statements automatically. This process automatically reconciles bank statement details with the appropriate batch, journal entry, or transaction, based on user-defined system parameters and setup. Oracle Cash Management generates all necessary accounting entries. See also reconciliation tolerance.

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

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

AutoCopy - budgets: A 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.

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

AutoLockbox: See lockbox.

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: A feature that automatically numbers your assets if you do not enter an asset number.

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 let you transfer funds from the customer's bank account to yours on the receipt maturity date.

automatic reconciliation: See AutoReconciliation.

AutoOffset: A 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: An Oracle Applications 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.

average exchange rate

An exchange rate that is the average rate for an entire accounting period. 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, 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.

Average Costing: An average costing method is used to cost transactions in both inventory and manufacturing environments. As you perform your transactions, Oracle Cost Management uses the transaction price or cost and automatically recalculates the average cost of your items.

AX Accounting Number Sequences: A feature that numbers all accounting entries with the document sequences mechanism.

AX Balance: A balance maintained by the Global Accounting Engine for each account that is marked as a control account or third party subidentification per period. The balance reports print balances summed by period (range), third party, balancing segment, and accounting segment/accounting flexfield combination.

AX Compiler: A program that creates the master template for future translation processes. This compilation is a one-time setup step and is not a part of the actual accounting.

AX Posting Manager: A program that lets you submit a process or a series of processes to run translations, the transfer to General Ledger, the Journal Import, and the Journal Post from one place in your system.

AX Program: A compilation of event types and sequence assignments. The AX Program is a PL/SQL package that handles events.

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.

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 also Bank Statement Open Interface, bank statement.

balance: See AX Balance.

balance reports: Reports that print a balance summed by period (range), third party, balancing segment, and accounting segment. A balance report only reports within a fiscal year. A balance is only printed for accounts that are marked as control accounts.

balances table: A General Ledger database table that stores your account balances, called GL_BALANCES.

balancing segment

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

bank file: In Oracle Receivables and Oracle Payables, the data file you receive from the bank containing all of the payment information that the bank has deposited in your bank account.

bank file: In Oracle Cash Management, the electronic statement file you receive from your bank (for example, BAI format or SWIFT940). It contains all transaction information that the bank has processed through 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 automatically 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: To approve a budget for use in reporting and accounting.

baseline budget: The authorized budget for a project or task which is used for performance reporting and revenue calculation.

basis method: How an allocation rule is used to allocate the amounts from a source pool to target projects. The basis methods include options to spread the amounts evenly, allocate by percentage, or prorate amounts based on criteria you specify. Also referred to as the "basis." See also source pool

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 source: 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 a transaction batch source.

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

bill in advance: An invoicing rule that enables you to record the receivable at the beginning of the revenue recognition schedule for invoices that span more than one accounting period. See also invoicing rules, bill in arrears.

bill in arrears: An invoicing rule that records the receivable at the end of the revenue recognition schedule for invoices that span more than one accounting period. See also invoicing rules, bill in advance.

Bill of Exchange: In Oracle Payables, a method of payment. Also known as a future dated payment in some countries, including France.

Bill of Exchange: In Oracle Receivables, an agreement made with your customer in which they promise to pay a specified amount on a specific date (called the maturity date) for goods or services. This process involves the transfer of funds from your customer's bank account to your bank account.

In Oracle Cash Management, a method of payment involving the transfer of funds between bank accounts, where one party promises to pay another a specified amount on a specified date.

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 you want 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 Management.

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.

billing

The functions of revenue accrual and invoicing.

billing invoice number: A system-generated number assigned to a consolidated billing invoice when you print draft or final versions of these invoices. This number appears in some Receivables windows (next to the transaction number) and reports if the profile option AR: Show Billing Number is set to Yes. See also consolidated billing invoice.

billing cycle: The billing period for a project. Examples of billing cycles you can define are: a set number of days, the same day each week or month, or the project completion date. You can optionally use a client extension to define a billing cycle.

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.

bridging account: An inventory bridging account is an offset account used to balance your accounting entries. In some European countries, a bridging account is a legal requirement.

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,

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: In Oracle General Ledger, a database table that stores information needed for budget upload.

In Oracle Assets, the interface table from which Assets uploads budget information.

budget line

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

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 or flat file to the GL_INTERFACE table in Oracle General Ledger.

budget upload: In Oracle Assets, the process by which 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 Interface table.

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.

budget worksheet: A worksheet that contains budget data. In the Enter Budget Amounts window in Oracle General Ledger, you can choose the Worksheet mode to enter budgets for several accounts at once. You can also use Applications Desktop Integrator to upload budget data from an Excel worksheet to Oracle General Ledger.

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 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.

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 Override.

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 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.

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.

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 products to that address. If you also send invoices to that address, you could also assign the business purpose Bill To.

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

cache: A temporary storage area for holding information during processing.

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 about an escalated issue.

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

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

capital gain threshold: The minimum time you must hold an asset for Oracle Assets 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 Assets reports it as a capital gain when you retire it. If you hold the asset for less than the threshold, Oracle Assets reports it as an ordinary income from the retirement.

capitalized assets: Assets that 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.

cash activity date: The date that the cash flow from the source transaction is expected to affect your cash position. When Cash Management generates a forecast, it includes source transactions whose cash activity date falls within the time period you defined.

cash basis accounting: An accounting method that lets you recognize revenue at the time payment is received for an invoice.

An accounting method in which you only recognize an expense when you incur the expense. With the Cash Basis Accounting, Payables only creates accounting entries for invoice payments.

Cash Clearing Account: The cash clearing account you associate with a payment document. You use this account if you account for payments at clearing time. Oracle Payables credits this account instead of your Asset (Cash) account and debits your Liability account when you create accounting entries for uncleared payments. Oracle Payables debits this account and credits your Asset (Cash) account once you clear your payments in Oracle Cash Management.

cash flow: Cash receipts minus cash disbursements from a given operation or asset for a given period.

cash forecast: Projection or estimate of cash position based on estimated future sales, revenue, earnings, or costs.

category: In Global Accounting Engine, a category is a code used to group similar items, such as plastics or metals.

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.

category use: Controls which object can use a given class category. For example, the SIC code 1977 can be used only by parties of type Organization.

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

child segment value: A value that lies in a range of values belonging to one or more parent values. You can budget, enter, and post transactions to child values only.

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

chart of accounts security: Restricts user access to those charts of accounts associated with that user's responsibility.

chart of accounts structure: See: Accounting Flexfield Structure.

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.

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.

circular relationship: Circular relationships participate in a circle of relationships between entities. For example, Party A is related to Party B, who is related to Party C, who is related to Party A.

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

claim: A discrepancy between the billed amount and the paid amount. Claims are often referred to as deductions, but a claim can be positive or negative.

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 category: Consists of multiple classification codes that allow for broad grouping of entities. Categories can have rules pertaining to a set of class codes, for example, Multiple Parent, Multiple Assignment, and Leaf Node Assignment rules.

class code

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

class code: Provides a specific calue for a class category.

classification: A means of categorizing different objects in Oracle Applications. Classifications are not limited to parties but can include projects, tasks, orders, and so on. Classifications can be user defined or based on external standards.

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: A process that assigns a cleared date and status to a transaction and creates accounting entries for the cash clearing account. See also manual clearing reconciliation reconciliation

clearing account: An account used to ensure that both sides of an accounting transaction are recorded. For example, Oracle General Ledger uses clearing accounts to balance intercompany transactions.

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 an offset journal entry to the asset clearing account to balance the entry from the payables group.

column set

A Financial Statement Generator report component you build within Oracle General Ledger 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.

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

columns: Oracle database 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 query: See Existing Combinations.

combined basis accounting: A method of accounting that combines both Accrual Basis Accounting and Cash Basis 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. Payables 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

In Oracle Receivables and Oracle Payables, a contractual guarantee with a customer for future purchases, usually involving deposits or prepayments. You can create invoices against the commitment to absorb the deposit or prepayment. Receivables automatically records all necessary accounting entries for your commitments.

compensation rule

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

compiler: See AX Compiler.

Compiling Schemes: A process performed during setup that generates the accounting program. A scheme is linked to your set of books.

complete invoice

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

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

consolidated billing invoice: An invoice that you send to a customer to provide a summary of their receivables activity for the month. This invoice includes a beginning balance, the total amount of any payments received since the prior consolidated billing invoice, an itemized list of new charges (for example, invoices, credit memos, and adjustments) in either summary or detail format, a separate reporting of consumption tax, and the total balance due for this customer.

consolidation of balances: Recalculating the balances for a third party is sometimes called consolidation or consolidation of balances. This consolidation is not related to the General Ledger consolidation functionality.

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. 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.

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. When you submit a request that does not require your interaction, such as releasing shipments or running a report, the Concurrent Manager does the work for you, letting you 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, such as releasing a shipment, posting a journal entry, or running a report. Once you submit a request, Oracle Applications automatically completes your request.

consolidation: The process of combining the financial results of multiple companies into one financial statement. See: Global Consolidation System.

consolidation: The Consolidate Billing Invoice program lets you print a single, monthly invoice that includes all of your customer's transactions for the period.

consolidation set of books: A set of books into which you consolidate the financial results of multiple companies. You can consolidate actual, average, translated, budget, and statistical balances.

A field in Oracle General Ledger's Set of Books window that must be enabled in order to consolidate average balances.

constant unit of money: A constant unit of money represents the real value of money at the end of a period. Financial statements must be prepared using the constant unit of money. The constant unit of money is independent of any methods used to evaluate a company's assets.

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

In Oracle Receivables, 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. Receivables

lets you enter contacts for your customers, addresses, and business purposes.

contact: In Oracle Projects, 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 point: A means of contacting a party other than postal mail, for example, a phone number, e-mail address, fax number, and so on.

contact role: A responsibility that you associate to a specific contact. Oracle Receivables 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 Financial Statement Generator report component you build within General Ledger that lets you generate hundreds of similar reports in a single run. For example, you can define one departmental content set that prints 50 reports, one report for each department in your organization.

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 account: An accounting segment status for an account combination. This type of account is used in subledgers such as Payables or Receivables. Control accounts are used to maintain special balances for third parties per period. You should not change control accounts from a General Ledger responsibility; define and use security to protect your control accounts.

control amount: A feature you use to specify the total amount available for payment of a recurring payment. When you generate invoices for a recurring payment, Oracle Payables 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, that 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 Oracle 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

A process that 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. You define this rate in Oracle General Ledger.

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 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 that 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 group: An attribute that is used to hold item unit costs at a level below the inventory organization. Within an organization, an item might have more than one cost if the item belongs to multiple cost groups.

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 Management feature that automatically checks a customer order total against predefined order and total order limits. If an order exceeds the limit, Oracle Order Management places the order on hold for review by your finance group.

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 Receivables 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: In Oracle Payables and Oracle Projects, a document that partially or fully reverses an original invoice.

In Oracle Receivables, a document that partially or fully reverses an original invoice. You can create credit memos in the Receivables Credit Transactions window or with AutoInvoice.

credit memo reasons

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

See also return reason.

cross currency receipt: A receipt that is applied to a transaction denominated in a currency different than that of the receipt. Cross currency receipt applications usually generate a foreign exchange gain or loss due to fluctuating exchange rates between currencies.

cross charge: To charge a resource to a project owned by a different operating unit.

cross instance data transfer: A feature in the General Ledger's Global Consolidation System that lets you transfer subsidiary data to your remote parent instance over your corporate intranet.

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 Payables, you use a cross rate to convert your invoice currency to your payment 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 restrict the user from entering invalid key flexfield segment value combinations during data entry. For example, you may set up a cross-validation rule that disallows using department segments with balance sheet accounts.

Cumulative Translation Adjustment: A balance sheet account included in stockholder's equity in which Oracle General Ledger 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 Set of Books window.

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 can have many addresses. You can also associate business purposes with addresses.

customer agreement: See agreement.

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 Lookup)

customer contact: A specific customer employee with whom you communicate. Oracle Receivables 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 interface: A program that transfers customer data from foreign systems into Receivables.

customer interface tables: A series of two Oracle Receivables database 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: In Oracle Payables, the number a supplier assigns to your organization.

customer number: In Oracle Receivables, a number assigned to your customers to uniquely identify them. A customer number can be assigned manually or automatically, depending on how you set up your system.

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

customer profile: A method used to categorize your customers based on credit information. Receivables 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 Management 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 lets you

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

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

customer site: A site where a customer is located. A customer can have more than one site. Site names can more easily identify a customer address, facilitating invoice and order entry. See also Oracle Order Management 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 Management, 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 Receivables, you can only create invoices for active customers, but you can continue collections activities for inactive customers.

cutoff day: The day of the month that determines 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 or on January 10 are due in the next billing period; invoices dated after the 10th are due in the following period.

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.

Data Quality Management (DQM): A TCA feature that provides a set of tools to keep the TCA registry clean and accurate, with matching, duplicate identification, and merging functionality.

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.

data sharing group: Groups information about business entities such as parties, their addresses, contact points, relationships, and the like based on criteria such as classifications, relationship types, or created by modules. For example, one Data Sharing Group might be created for patients, another for employees, and another for parties classified as both patients and employees. A security administrator may then assign privileged access to create, update, or delete information secured by this Data Sharing Group based on the applicable business policy.

data source: The source of the records in the TCA Registry; for example user entered or third party.

date placed in service: The calendar date on which 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 Receivables includes invoices, debit memos, and chargebacks as debit items. Debit items remain open until the balance due is zero.

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

debit memos: Debits that you assign to a customer to collect additional charges. For example, you may want to charge a customer for unearned discounts taken, additional freight charges, taxes, or finance charges.

deduction: see claim.

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.

deleting the rules: Purging the rules tables. After you have loaded the rules into the accounting scheme, you can delete them.

Deleting TP: The Deleting TP program deletes your translation program. If you delete your translation program, however, you risk the integrity of your entries.

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. (Manufacturing Lookup)

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.

denomination currency: In some financial contexts, a term used to refer to the currency in which a transaction takes place. In this manual, this currency is called transaction currency. See: transaction currency

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 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.

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

direct project: An obsolete term. See contract project.

detail budget: A lower level budget whose authority is controlled by a Master 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 their 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: A feature you use to determine the type of payment for which a payment document is used. For example, computer-generated payments and recorded checks or wire transfers.

discount: The amount or percentage that you allow a customer to decrease the balance due for a debit item. In Oracle Receivables, you use Payment Terms to define customer discounts and can choose whether to allow earned and unearned discounts. See also earned discounts, unearned discounts,payment terms.

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: An optional report component in Oracle General Ledger's Financial Statement Generator. Display groups determine the range of rows in a row set or columns in a column set that will be displayed or hidden in a financial report. Display groups are assigned to Display Sets.

display set: A Financial Statement Generator report component that includes one or more display groups 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: In Oracle Payables and Oracle Projects, a line corresponding to an accounting transaction for an expenditure item on an invoice, or a liability on a payment.

distribution line: In Oracle Assets, 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 rule: See revenue distribution rule.

distribution set: In Oracle Receivables, a predefined group of general ledger accounting codes that determine the debit accounts for other receipt payments. Receivables lets you relate distribution sets to receivables activities to speed data entry.

distribution set: In Oracle Payables, a feature you use to assign a name to a predefined expense distribution or combination of distributions (by percentage). Payables displays on a list of values the list of Distributions Sets you define. With Distribution Sets, you can enter routine invoices into Payables 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: The physical base of a transaction, such as an invoice, a receipt, or a payment.

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 Receivables lets you set up categories for each type of transaction, receipt, and adjustment.

document sequence: A unique number that is manually or automatically assigned to documents such as bank statements in Oracle Cash Management, invoices in Oracle Receivables, or journal entries in Oracle General Ledger. Also used to provide an audit trail. Many countries require all documents to be sequentially numbered. Document sequencing can also be used in Public Sector implementations to comply with reporting and audit requirements.

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.

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.

DTD (Document Type Definition): The statement of rules for an XML document that specifies which elements (markup tags) and attributes (values associated with the tag) are allowed in your document.

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

dunning letters: A letter that you send to customers to inform them of past due debit items. Receivables lets you specify the text and format of each letter and whether to include unapplied and on-account payments.

DUNS (Data Universal Numbering System) number: The nine-digit identification number assigned by Dun & Broadstreet to each commercial entity in its database. For businesses with multiple locations, each location is assigned a unique DUNS number.

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 optional Accounting Flexfields feature that allows you to create new account combinations during data entry in Oracle Applications. By enabling this feature, it prevents having to define every possible account combination that can exist. Define cross-validation rules when using this feature.

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 remit payment for their invoices on or before the discount date. The discount date is determined by the payment terms assigned to an invoice. Oracle Receivables 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. See also unearned discounts.

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 Payables your bank transfers funds from your bank account into the bank account of a supplier you pay with the Electronic 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: In Oracle Payables, a journal entry that increases or relieves encumbrances. Encumbrance entries can include encumbrances of any type. If you have enabled encumbrance accounting, when you successfully validate an invoice matched to an encumbered purchase order, Oracle General Ledger automatically creates encumbrance journal entries that relieve the original encumbrance journal entries. General Ledger also creates new encumbrance journal entries for any quantity or price variance between an invoice and the matched purchase order. General Ledger automatically creates encumbrance journal entries for an unmatched invoice when you validate the invoice.

encumbrance type: In Oracle General Ledger, 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).

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 as of the ending GL Date that you have specified. This column should be the same as the Outstanding Balance of the Aging - 7 Buckets Report for this item.

end of period's unit of money: The end of period's unit of money is the value that represents money's acquiring power as of period end.

EU: European Union. A single European market in which custom and tariff barriers do not exist between member states. Member states share a single currency, the Euro.

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.

entity: A group of related attributes in the TCA Registry; for example Organization Profile, Person Profile, Address, and Contact Point.

escheatment: The legal process of remitting unclaimed property to the required authority. In the United States, escheatment laws are at the state level. Under these laws, accounts payable departments are required to perform due diligence to contact and remit the funds to the payee. Organizations must then remit to the state of last known address of the owner all unpaid items once they have been outstanding for a set time period.

estimated index value: In some countries, if the index value for a period is not known, you can use an estimated index value. The inflation adjustment process operates the same way as when the exact index value is known. See also index value

euro: A single currency adopted by the member states of the European Union. The official abbreviation, EUR, is used for all commercial, business, and financial purposes, and has been registered with the International Standards Organization (ISO).

event: In Oracle Projects, 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: In Global Accounting Engine, an event associates a document's accounting entries with a transaction. These entries were already created or must be created in the next posting process. An example of an event is an adjustment to an invoice. If a second adjustment is needed for the same document, a second event is created. Events can be of different event types, which causes different accounting entries.

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 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 one currency can be exchanged for another at a specific point in time. Oracle Applications can access daily, periodic, and historical rates. These rates are used for foreign currency conversion, revaluation, and translation.

exchange rate type: The source of an exchange rate. For example, user defined, spot, or corporate 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.

exemption certificate: A document obtained from a taxing authority which certifies that a customer or item is either partially or fully exempt from tax. The document details the reason for the exemption and the effective and expiration dates of the certificate.

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 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. 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: In Oracle Payables, a document that details expenses incurred by an employee for the purpose of reimbursement. You can enter expense reports online in Payables, or employees enter them online in Internet Expenses. You can then submit Expense Report Import to import these expense reports and expense reports from Projects. The import program creates invoices in Payables from the expense report data.

expense report: In Oracle Projects, 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 Expense Report Import before you can pay the expense reports.

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

expensed asset: An asset that 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 Assets tracks expensed items, but does not create journal entries for them.

export: The process of creating a file from selected data in an applications. Typically, archived account balances and journal data are exported or archived to backup media for storage.

export file: A file that contains data to be exported such as archived account balances and journal data copied to backup media for storage. Export files must have the extension .dmp. It is useful to name an export file so it identifies the archived data. For example, if you are saving fiscal year 1998 for your San Francisco set of books, name your export file FY98SF.dmp.

external transaction: Transactions between an EU (European Union) trader and a supplier 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.

external organization: See organization.

F

factor: In Oracle General Ledger, 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.

factor: In Oracle Payables, 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 financial institution or factor.

factoring: The process by which you sell your accounts receivable to a financial institution (such as a bank) in return for cash. Financial institutions usually charge a fee for factoring.

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

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: A non-Oracle 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 window 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 Receivables calls these regions "fields" and provides you with a list of the types of fields that can be interfaced through AutoLockbox.

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

Financial Statement Generator: A powerful and flexible report building tool for Oracle General Ledger. You can design and generate fiancial reports, apply security rules to control access to data via reports, and use specific features to improve reporting productivity.

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 rate currencies: Currencies with fixed exchange rates. No longer applicable to EU member states.

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 that calculates the depreciation for an asset based on a fixed rate each year. This method uses a constant rate which Oracle Assets multiplies by an asset's recoverable cost or net book value as of the beginning of each fiscal year.

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 that 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. This indicates that delivery of a shipment will be made on board or into a carrier by the shipper without charge, and is usually followed by a shipping point or destination (e.g. 'FOB Our warehouse in New York'). (Receivables Lookup)

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.

foreign currency

In Oracle Applications, a currency that is different from the functional currency you defined for your set of books in Oracle General Ledger. When you enter and pay a foreign currency invoice, Payables automatically converts the foreign currency into your functional currency at the rate you define. General Ledger automatically converts foreign currency journal entries into your functional currency at the rate you define.

See also exchange rate, functional currency.

foreign currency conversion: A process in Oracle Applications that converts a foreign currency transaction into your functional currency using and exchange rate you specify. See also foreign currency exchange gain or loss

foreign currency realized gain/loss: Gains or losses on foreign currency transactions due to foreign currency fluctuations. Typically, the gain or loss is tracked for assets or liabilities for a period of time. Oracle General Ledger posts all foreign currency gains or losses resulting from revaluations to the Cumulative Translation Adjustment account defined in your set of books. Oracle Payables determines the foreign currency gain or loss as the difference between the invoiced amount and the payment amount due to changes in exchange rates.

foreign currency journal entry: A journal entry in which you record transactions in a foreign currency. Oracle General Ledger 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 General Ledger 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. General Ledger 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 General Ledger multiplies the average, periodic, or historical rate you define by your functional currency account balances to perform foreign currency translation. General Ledger translates foreign currency in accordance with FASB 52 (U.S.). General Ledger also remeasures foreign currencies for companies in highly inflationary economies, in accordance with FASB 8 (U.S.).

form: A window that contains a logical collection of fields, regions, and blocks that appear on a single screen. You enter data into forms. See window.

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 General Ledger 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.

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

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

full allocation: An allocation method that distributes all the amounts in the specified projects in the specified amount class. The full allocation method is generally suitable if you want to process an allocation rule only once in a run period. See also incremental allocation

function: A PL/SQL stored procedure referenced by an Oracle Workflow function activity that can enforce business rules, perform automated tasks within an application, or retrieve application information. The stored procedure accepts standard arguments and returns a completion result. See also function activity.

function activity: An automated Oracle Workflow unit of work that is defined by a PL/SQL stored procedure. See also function.

function security: An Oracle Applications feature that lets you control user access to certain functions and windows. By default, access to functionality is not restricted; your system administrator customizes each responsibility at your site by including or excluding functions and menus in the Responsibilities window.

functional currency: The principal currency you use to record transactions and maintain accounting data for your set of books.

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: In Oracle Financial Applications, the amount budgeted less actual expenses and encumbrances of all types. Oracle Financials lets you check funds available through online inquiries or generated reports.

funds available: In Oracle General Ledger, 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 window, or you can create custom reports with the General Ledger Financial Statement Generator.

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: In Oracle Payables, the creation of requisition, purchase order, or invoice encumbrance journal entries. Payables reserves funds for your invoice when you validate the invoice. Invoice Validation 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. Payables immediately updates your funds available balances and creates an encumbrance journal entry that you can post in your general ledger.

funds reservation: In Oracle 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.

G

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

gain: See realized gain or loss, unrealized gain or loss.

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

general ledger: A record of a business entity's accounts. Contains the accounts that make up the entity's financial statements. Journal entries, in Oracle General Ledger or subledger applications, update account balances.

GL Date: The date, referenced from Oracle General Ledger, used to determine the correct accounting period for your transactions.

In Oracle Payables and Receivables, you assign a GL Date to your invoices and payments when they are created.

In Oracle Projects, 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 Project Accounting Date of a cost distribution line or revenue. For invoices, the date within the GL Period on which an invoice is transferred to Oracle Receivables.

GL Date range: An accounting cycle that 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: An acronym for the General Services Administration. In Oracle Receivables, you can indicate whether a customer is a government agency that orders against GSA agreements in Oracle Order Management.

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 amount. See also soft limit.

hierarchical relationship: A relationship in which a party is ranked above the other. The rank is determined by the role that they are taking in a relationship.

historical balances: Historical balances are composed of journal entry line amounts expressed in the units of money that were current when the transactions took place. Historical balances are the opposite of inflation-adjusted balances.

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

hold: In Oracle Payables, 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 scheduled payment line. All holds in Payables prevent payment; some holds also prevent accounting.

hold: In Oracle Receivables, a feature that prevents an order or order line from progressing through the order cycle. If you place a customer on credit hold in Receivables, you cannot create new orders for this customer in Oracle Order Management. However, you can still create transactions for this customer in Receivables.

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 Oracle8 table. The import utility is part of the Oracle8 Relational Database Management System. This utility is used to restore archived data.

import journal entry: See: Journal Import.

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 data from an external system to an Oracle application. You can use SQL*Loader as the import program to import data into the open interface tables.

imported invoice: In Oracle Receivables, an invoice that is imported into Receivables from an external system (for example, Oracle Order Management) using the AutoInvoice program.

imported invoice: In Oracle Payables, an invoice that is imported into Payables using the Payables Open Interface Import program.

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, Payables 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 Payables 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 that has failed validation. To complete an invoice, several conditions must be met. For example, the invoice must have at least one line and the GL date must be in an Open or Future period.

incremental allocation: An allocation method that creates expenditure items based on the difference between the transactions processed from one allocation to the next. This method is generally suitable if you want to use an allocation rule in allocation runs several times in a given run period. See also full allocation

index values: An index value represents the price level for the period that the value applies to in relation to a fixed base level. Index values are used to calculate the correction factor that represents the inflation rate in the inflation adjustment process. See also estimated index value

indirect project: A project used to collect and track costs for overhead activities, such as administrative labor, marketing, and bid and proposal preparation. You can also define indirect projects to track time off such as sick leave, vacation, and holidays. You cannot generate revenue or invoices for indirect projects.

inflation-adjusted balances: Inflation-adjusted balances are composed of the original journal entry line amounts and the inflation adjustment journal entry line amounts. If you use the historical/adjusted option, you maintain inflation-adjusted balances in a separate inflation-adjusted set of books in Oracle General Ledger. If you use the adjusted-only option, you maintain inflation-adjusted balances in your primary set of books.

inflation adjustment date: The inflation adjustment date (Fecha Valor) is the date that each journal entry must be adjusted from, which can be different than the journal entry's effective date. Every journal entry must be adjusted for the period from the inflation adjustment date until the present time. The default value for the inflation adjustment date is the journal entry's effective date.

inflation start date: The inflation start date for an asset specifies when inflation begins to impact an asset. The asset is adjusted for inflation from this date onward. The inflation start date is generally the same date as the date placed in service. You can, however, define an inflation start date that is different than the date placed in service. For example, if you enter an asset that is already in service and that has already been adjusted for inflation, you can set the inflation start date to an appropriate date to begin calculating new inflation adjustments in Oracle Assets.

installment: One of many successive payments of a debt. You specify a payment schedule when defining 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 transactions: 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 Assets.

intercompany account: A general ledger account that 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. General Ledger keeps your accounting records in balance for each company by automatically creating offsetting entries to an intercompany account you define.

intercompany segment: A segment you define in your chart of accounts to track intercompany transactions by company or trading partner.

: interest invoice; An invoice that Oracle Payables creates to pay interest on a past-due invoice. Payables automatically creates an expense distribution line for an interest invoice using an account you specify.

: 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 Management. 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.

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

invoice: In Oracle Receivables and Oracle Cash Management, a document that you create in Receivables that lists amounts owed for the purchases of goods or services. This document also lists any tax, freight charges, and payment terms.

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

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

invoice batch: In Oracle Receivables, 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.

invoice batch: In Oracle Payables, a 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 use the Invoice Batch Controls profile option, Payables automatically creates invoice batches for Payables expense reports, prepayments, and recurring invoices, as well as all standard invoices. In addition, you can specify a batch name when you import 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 currency: The currency in which an Oracle Projects invoice is issued.

invoice date: In Oracle Assets and Oracle Projects, 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.

In Oracle Receivables, the date an invoice is created. This is also the date that Receivables prints on each invoice. Receivables also uses this date to determine the payment due date based on the payment terms you specify on the invoice.

In Oracle Payables, the date you assign to an invoice you enter in Payables. Payables 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: A feature that 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 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 related claim: A claim that is due to a discrepancy between the billed amount and the paid amount for a specific transaction

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: See split 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 Receivables uses to determine when you will bill your customer and the accounting period in which the receivable amount is recorded. You can bill In Advance or In Arrears. See also bill in advance, bill 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 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 Flexfield: See System Items Flexfield.

item type: A term used by Oracle Workflow to refer to a grouping of all items of a particular category that share the same set of item attributes, used as a high level grouping for processes. For example, each Account Generator item type (e.g. FA Account Generator) contains a group of processes for determining how an Accounting Flexfield code combination is created. See also item type attribute

item type attribute: A feature of a particular Oracle Workflow item type, also known as an item attribute. An item type attribute is defined as a variable whose value can be looked up and set by the application that maintains the item. An item type attribute and its value is available to all activities in a process.

Item Validation Organization

The organization that contains your master list of items.

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 Management refers to organizations as warehouses on all Order Management 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.

Japanese consumption tax: The Value Added Tax (VAT) paid on any expense (Input VAT) is usually recoverable against the VAT charged on revenue (Output VAT). This ensures that VAT is not inflationary within a supply chain.

job title: In Oracle Projects, a unique combination of job level and job discipline that identifies a particular job.

job title: In Oracle Receivables, a brief description of your customer contact's role within their organization.

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. See also manual journal entry.

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 accounting entries to your general ledger for posting, Payables transfers the necessary information to create journal entry batches for the information you transfer. Journal Import in 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. General Ledger 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, General Ledger uses the journal entry category, date, and time of transfer.

journal entry category: A category to indicate the purpose or nature of a journal entry, such as Adjustment or Addition. Oracle General Ledger associates each of your journal entry headers with a journal category. You can use one of General Ledger's pre-defined journal categories or define your own.

For Oracle Payables, there are three journal entry categories in Oracle Projects 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 Projects only assigns the Payment journal entry category to your journal entries.

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 Payables transfers the necessary information to create journal entry headers for the information you transfer. Journal Import in 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 Payables, and your method of summarizing journal entries from Oracle Payables.

journal entry source: Identifies the origin of journal entries from Oracle and non-Oracle feeder systems. General Ledger supplies predefined journal sources or you can create your own.

Journal Import: A General Ledger program that creates journal entries from transaction data stored in the General Ledger GL_INTERFACE table. Journal entries are created and stored in GL_JE_BATCHES, GL_JE_HEADERS, and GL_JE_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 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 following application uses the listed Key Flexfields:

Oracle General Ledger - Accounting

Oracle Projects - Accounting, Category Flexfield, Location, Asset Key.

Oracle Payables - Accounting, System Items.

Oracle Receivables - Accounting, Sales Tax Location, Systems Items, Territory.

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 can use to gather and retain information about your productivity, such as the number of invoices paid. You define key indicator periods and Oracle Receivables provides a report that 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.

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.

legal document: A paper document sent to or sent by the customer or supplier. Many countries require that legal documents are stored for up to ten years. See also document.

legal journals: Journals that print all journal entries according to your legal requirements. Entries might include period balances for customers or suppliers. Legal journals vary from country to country.

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 that 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.

listing: An organized display of Oracle Applications information, similar to a report, but usually showing setup data as opposed to transaction data.

loading rules: The process of copying information from the rules tables into the accounting scheme tables.

location: In Oracle Receivables, a shorthand name for an address. Location appears in address list of values 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.

location: In Oracle Assets, 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: In TCA, a point in geographical space described by an address.

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.

lockbox: A service that commercial banks offer corporate customers to enable them to outsource their accounts receivable payment processing. Lockbox processors set up special postal codes to receive payments, deposit funds and provide electronic account receivable input to corporate customers.

lookup code: The internal name of a value defined in an Oracle Workflow lookup type. See also lookup type.

lookup type: An Oracle Workflow predefined list of values. Each value in a lookup type has an internal and a display name. See also lookup code.

Lookups: In Oracle Receivables, codes that you define for the activities and terminology you use in your business. These codes appear in lists of values in many Receivables windows. For example, you can define Lookups for personal titles, such as 'Sales Manager', so you can refer to people using these titles.

Lookups: In Oracle Payables, a feature you use to create reference information you use in your business. This reference information appears in lists of values for many of the fields in Payables windows. There are three basic kinds of Lookups: supplier, payables, and employee. With Lookups you can create Pay Groups, supplier types, and other references used in Payables.

loss: See realized gain or loss, unrealized gain or loss.

M

manual clearing: The process in which, prior to receiving their bank statement, users mark transactions that are known to be cleared through the bank, which creates an up-to-date cash position. These cleared transactions are still available for the actual reconciliation process. Once the bank statement is received, Oracle Cash Management can automatically perform all appropriate reconciliation steps. See also clearing.

manual reconciliation: The process where you manually reconcile bank statement details with the appropriate batch or detail transaction. Oracle Cash Management generates all necessary accounting entries. See also AutoReconciliation, reconciliation.reconciliation.

manual invoice: An invoice that you enter using either the Transactions or Transactions Summary window.

manual journal entry

A journal entry you create in the Enter Journals window in Oracle General Ledger. 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.

Mass Additions: In Oracle Assets, a feature that 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 window, and actually create an asset from the mass addition line by posting it to Oracle Assets.

Mass Additions: In Oracle Payables, invoice distribution lines that you transfer to Oracle Assets for creating assets. Oracle Payables 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: A feature that allows you to change the prorate convention, depreciation method, life, rate, or capacity for a group of assets in a single transaction.

Mass Copy: A feature that 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: A feature that 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: A feature that 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.

match rule: A set of rules that determines which records are matches for an input record. A match rule consists of an acquisition portion to determine potential matches, a scoring portion to score the potential matches, and thresholds that the scores are compared against to determine actual matches.

matching: In Oracle Cash Management, the process where batches or detailed transactions are associated with a statement line based on the transaction number, amount, currency and other variables, taking Cash Management system parameters into consideration. In Cash Management, matching can be done manually or automatically. See also clearing, reconciliation.

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

matching tolerances: The acceptable degrees of variance you define for matched invoices and purchase orders. Payables 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, Validation places the invoice on hold.

maturity date: In Oracle Receivables, a date that determines when funds for an automatic receipt can be transferred from your customer's bank account to your bank account. See also Bill of Exchange.

maturity date: In Oracle Payables and Oracle Cash Management, the date your bank disburses funds to a supplier for a future dated payment. Payables displays the maturity date on the future dated payment document to inform your supplier and bank when the bank should transfer funds to the supplier's bank. You can update the payment status from Issued to Negotiable on or after the maturity date.

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: An area where you write as many notes as you need regarding your conversation with a customer.

merchant ID: A unique identification number used for credit card processing. The merchant ID identifies your business to iPayment, to your customer's electronic payment system and credit card vendor, and to your remittance bank.

message distribution: A line at the bottom of the toolbar that displays helpful hints, warning messages, and basic data entry errors.

message line: A line on the bottom of a window that displays helpful hints or warning messages when you encounter an error.

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: (Magnetic Ink Character Recognition number) A number that appears on a receipt and associates your customer with 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. These segments correspond to the Bank Branch Number and the Bank Account Number fields in the Banks and Bank Accounts windows.

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, for example, .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).

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 Payables does not pay interest on an overdue invoice. Payables 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.

miscellaneous receipts: A feature that lets you record payments that you do not apply to debit items, such as refunds and interest income.

model invoice: An invoice used as a template that you copy to create new invoices.

monetary account: Monetary accounts, such as the Cash, Banks, Receivables, or Payables accounts, are accounts that remain the same through different periods. Monetary accounts are not adjusted for inflation, but these accounts do generate inflation gain or loss. See also non-monetary account

multi-org: See multiple organizations.

multiple organizations: The ability to define multiple organizations and the relationships among them within a single installation of Oracle Applications. These organizations can be sets of books, business groups, legal entities, operating units, or inventory organizations.

Multiple Reporting Currencies: A unique set of features embedded in Oracle Applications that allows you to maintain and report accounting records at the transaction level in more than one functional currency.

N

NACHA: National Automated Clearing House Association. Payment format that allows users to make electronic payments within the Automated Clearing House (ACH), the largest standardized electronic payment system in the United States.

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.

nesting: The act of grouping calculations to express the sequence of routines in a formula. Traditional mathematical nesting uses parenthesis and brackets. Oracle General Ledger 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.

node: An instance of an activity in an Oracle Workflow process diagram as shown in the Process window of Oracle Workflow Builder. See also process.

non-invoice related claim: A claim that is due to a discrepancy between the billed amount and the paid amount, and cannot be identified with a particular transaction.

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-monetary account: Non-monetary accounts, such as fixed assets and most expense and revenue accounts, are accounts that are revalued due to inflation or deflation effects. Non-monetary accounts must be adjusted at each period-end to reflect balance changes. See also monetary account

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

O

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.

offsets: Reversing transactions used to balance allocation transactions with the source or other project.

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 Transactions window or using 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.

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

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

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 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.

Oracle8 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 Oracle8 tables to store the information you need to run your business.

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

organization

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. See also business group.

organization hierarchy: An organizational hierarchy illustrates the relationships between your organizations. A hierarchy determines which organizations are subordinate to other organizations. The topmost organization of an organization hierarchy is generally the business group.

organization structure: See organization hierarchy.

original budget

The budget amounts for a project at the first successful baselining of the project.

other receipts: See miscellaneous receipts.

out of balance batch: The status of a batch when the control count or amount does not equal the actual count or amount.

Overapplication: A Transaction Type parameter that, if enabled, lets you apply a transaction to a debit item even if it will reverse the sign of the debit item (for example, from a positive to a negative balance). Overapplication applies to debit items such as debit memos, deposits, guarantees, credit memos, and on-account credits. See also Natural Application Only.

overflow record: A type of bank file record that stores additional payment information that could not fit on the payment record. Each overflow record must have a payment record as a parent. Typically, an overflow record will store additional invoice numbers and the amount of the payment to apply to each invoice.

Overtime Calculation Program: A program that Oracle Projects provides to determine which kind of overtime to award an employee based on the employee's compensation rule and hours worked. If your company uses this automatic overtime calculation feature, you may need to modify the program based on the overtime requirements of your business.

overtime cost: The currency amount over straight time cost that an employee is paid for overtime hours worked. Also referred to as Premium Cost.

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.

parallel allocation: A set of allocation rules that carries out the rules in an autoallocation set without regard to the outcome of the other rules in the set. See also autoallocation set, step-down allocation.

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 (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 General Ledger uses parent segment values to create summary accounts, to report on summary balances, and in MassAllocations and MassBudgeting. You can create parent segment values for independent segments, but not for dependent segments.

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

Q

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

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

Quick Check: See Quick payment.

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

Quick Release: A feature you can use to release all user-assigned and many system-assigned invoice holds. You can define and apply unlimited validation 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: A feature that lets you enter receipts quickly by providing only minimal information. After using QuickCash to enter your receipts, you can post your payment batches to your customer accounts by running Post QuickCash. See also Post QuickCash.

QuickCodes

An Oracle Assets feature that 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.

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.

realized gain or loss: The actual gain or loss in value that results from holding an asset or liability over time. Realized gains and losses are shown separately on the Income Statement. See also: foreign currency realized gain/loss.

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. 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 Payables uses this to recalculate invoice scheduled payments. You specify receipt acceptance days when you define your Financials options.

receipt batch: In Oracle Receivables a group of payments that you enter together to reduce data entry errors, share various default values, and to group them according to a common attribute. For example, you might add all payments from the same customer to a batch. Payments within the same batch share the same batch source and batch name. Receivables displays any differences between the control and actual counts and amounts.

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 currency: The currency in which an expense report item originates.

receipt grace days: A specific number of 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: Payment received in exchange for goods or services. 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 also cross site and cross customer receipts, cross currency receipt.

receivable activities: Predefined Receivables 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 receivables activities during the setup process to create accounting distributions for cash and miscellaneous receipt payments, receivables adjustments, discounts, receivables accounts, and finance charges.

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

reconciliation: In Oracle Receivables, an analysis that explains the difference between two balances. If you are using Cash Management to reconcile receipts, payments are reconciled when they are matched to a bank statement line.

reconciliation: In Oracle Payables, 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 Payables inserts a cleared date and amount for all payments that your bank reports as cleared.

reconciliation: The process of matching bank statement lines to appropriate batches and detail transactions and creating all necessary accounting entries. See also reconciliation tolerance, AutoReconciliation.

Reconciliation Open Interface: This interface lets you reconcile with payments and receipts from external systems.

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 type: A bank file is made up of many different rows or records. Each record must have a type. For example, a record may store information about a payment record or a batch record. Record types help Oracle Receivables determine where different types of data are stored in your bank file.

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: A feature that lets you create invoices for an expense that occurs regularly and is not usually invoiced. Monthly rents and lease payments are examples of typical recurring payments. You define recurring invoice templates and Payables 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, General Ledger 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.

reexpression coefficient: The reexpression coefficient (revaluation rate or correction factor) is the factor used to adjust cost, accumulated depreciation, and depreciation expense amounts for inflation. Historical amounts are multiplied by the reexpression coefficient to calculate the inflation-adjusted amounts.

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.

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. Regions in Release 11i and higher are defined by Tabs.

R.E.I. account: The R.E.I. account (Resultado por Exposicion a la Inflacion or Result of Exposure to Inflation) is the inflation adjustment gain or loss account. The balance of this account shows the net gain or loss from inflation adjustment journal entries.

reimbursement currency: The currency in which an employee chooses to be reimbursed for an expense report. See also transaction currency

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.

relationship group: A mechanism for grouping similar relationship roles and phrases together. As a general rule, this grouping is used to determine which relationship roles and phrases are displayed in application user interfaces but can also be used to group roles and phrases for other functional uses.

relationship phrase: Defines the role of the subject of a relationship. For example, if an organization is an employer of a person, the Employer Of role describes the subject.

relationship type: A categorization that defines the rules and characteristics of a 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 x 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.

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

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 Payables provides.

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

report: an organized display of information drawn from Oracle Applications that can be viewed online or printed. Most applications provide standard and customizable reports. Oracle General Ledger's Financial Statement Generator lets you build detailed financial reports and statements based on your business needs.

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 detailing general information about the report such as set of books, date, etc.

report option: See report parameter.

report parameter: Submission options in Oracle Applications that allow you to enter date and account ranges. You can also sort, format, select, and summarize the information displayed in your reports. Most standard reports require you enter 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 or Multiple Reporting Currencies 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.

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

Reserve for Encumbrance: A portion of fund balance you use to record anticipated expenditures. When you create and post encumbrances automatically in Oracle Financials, General Ledger automatically creates a balancing entry to your Reserve for Encumbrance account.

Reserve for Encumbrance account: The account you use to record your encumbrance liability. You define your Reserve for Encumbrance Account when you define your set of books.

responsibility: A level of authority set up by your system administrator in Oracle Applications. A responsibility lets you access a specific set of windows, menus, set of books, reports, and data in an Oracle application. Several users can share the same responsibility, and a single user can have multiple responsibilities.

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 code: In Oracle Workflow, the internal name of a result value, as defined by the result type. See also result type, result value.

result type: In Oracle Workflow, the name of the lookup type that contains an activity's possible result values. See also result code, result value.

result value: In Oracle Workflow, the value returned by a completed activity, such as Approved. See also result code, result type.

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 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.

In Oracle Assets, a feature that 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.

revaluation: In Oracle Receivables and Oracle General Ledger, a process that restates assets or liabilities denominated in a foreign currency using exchange rates that you enter. Changes in exchange rates between the transaction and revaluation dates result in revaluation gains or losses.

revaluation gain/loss account: An income statement account you define that records net gains and losses associated with the revaluation of foreign currency-denominated accounts, in functional currency units. You select the appropriate gain/loss account in the Revalue Balances window.

revaluation journal entry: A journal entry that is automatically created when you revalue foreign currency-denominated accounts. The revaluation process creates a batch of revaluation journal entries reflecting changes in market rates for each revalued currency and directs the gain or loss amount to the gain/loss account that you specify.

revaluation status report: A report that summarizes the results of your revaluation. Oracle General Ledger 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 General Ledger 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 point at which revenue is recorded. The concept of revenue recognition is central to accrual-basis accounting. Revenue recognition schedules detail the points at which percent amounts of a sale are recognized as revenue.

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 General Ledger creates by reversing an existing journal entry. You can reverse any journal entry and post it to any open accounting period.

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

rollforward: The process of taking the beginning balance of a period and then accounting for the transactions within that period by attempting to equate the beginning balance with the ending balance for the 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 that is the topmost node of a hierarchy. When you define a hierarchy using the Account Hierarchy Manager or Applications Desktop Integrators Account Hierarchy Editor, 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.

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: An optional Financial Statement Generator report component that lets you control how the order of rows and account segments appear in a report.

row set: A Financial Statement Generator tool that lets you define the format and content of the rows in an FSG 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.

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

rules: A concept that provides an easy way to export, import, or update translation schemes. Rules let you store the entire translation scheme information in one place. Rules are not needed for the compilation. They are also not needed for the translation or transfer to General Ledger tables.

rules tables: See rules

Run Journal Import: A step that imports accounting entries into General Ledger. Run Journal Import is the same as a manual Journal Import and lets you query entries in the Journal Entry window.

Run Post Journal: A step that is the same as the Journal Post in General Ledger.

S

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 Receivables 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 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. See also payment terms.

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.

Secure Posting: A feature that enforces the default parameters of the Posting Manager. You cannot override any values other than Submit: Yes/No. For example, you can ensure that Translate Events, Transfer to General Ledger, Run Journal Import, and Run Post Journal are done in one step.

security rules: (Order Management) 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.

segments: The building blocks of your chart of accounts in Oracle General Ledger. You define the structure and meaning of individual segments when customizing a flexfield. Each account is comprised of multiple segments. Commonly used segments include company, cost center, department, account, and product. See also: Account Combination.

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.

segment value security: An Oracle Applications feature that lets you exclude a segment value or ranges of segments values for a specific user responsibility.

selection options: For each report, Oracle Receivables provides you with parameters you can choose to make your report as brief as possible. For example, on the Aging - 4 Buckets report, you can specify that you want to review the report for a range of customers or only the aging information for one customer. This feature saves time and lets you retrieve data in different ways.

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.

senior tax authority: The first tax location in your sales tax structure. This segment does not have a parent location. For example, in the sales tax structure 'State.County.City', State is the senior tax authority.

sequence type: Receivables provides two types of sequences: Automatic and Manual. Automatic numbering sequentially assigns a unique number to each transaction as it is created. Manual numbering requires that you manually assign a unique number to each transaction when you create it. 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. See also document sequence.

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: Defined in Oracle General Ledger, an organization or group of organizations that share a common chart of accounts, calendar, and currency. A set of books is associated with one or more responsibilities.

To use Multiple Reporting Currencies, you must create a primary set of books and separate reporting sets of books for each reporting currency.

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 prescribes U.S. national accounting standards for the translation, revaluation, and reporting of foreign currency-denominated amounts. Oracle General Ledger conforms to SFAS 52 (U.S.) standards. SFAS 52 (U.S.) guidelines require the use of period-end exchange rates to translate monetary asset and liability accounts and weighted-average exchange rates to translate revenue and expense accounts. Historic rates are used to translate non-monetary asset and liability accounts and equity accounts. Foreign currency-denominated accounts are revalued using period-end rates.

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 Payables 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 date: The date upon which a shippable item is shipped.

Ship To Address: The address of the customer who is to receive products or services listed on the invoice or order.

ship via: See freight carrier.

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 that is used to categorize your customers by industry.

sign-on: An Oracle Applications user name 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. Import sources for the Payables Open Interface include Invoice Gateway, Oracle Assets, Oracle Property Manager, Credit Card, EDI Gateway (e-Commerce Gateway), ERS, RTS (Return to Supplier), and Internet Supplier Portal. You can define other sources in Payables for invoices you import from other accounting systems. Import sources for the Expense Report Open Interface are Payables Expense Report for invoices you enter in Payables or Internet Expenses, and Oracle Projects for invoices from Oracle Projects.

source pool: The combination of all the source amounts defined by an allocation rule. See also allocation rule

source transaction

For related transactions, the identifying source transaction from which the related items are created.

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: A 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 amount due.

spot exchange rate: A daily exchange rate you use to perform foreign currency conversions. 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 General Ledger.

staged dunning: A dunning method in which letters are based on the dunning levels of past due debit items. This method lets you send dunning letters based on the number of days since the last letter was sent, rather than the number of days items are past due. For each dunning letter, you specify the minimum number of days that must pass before Receivables can increment an item's dunning level and include this item in the next dunning letter.

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 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 memo lines: A type of line that you assign to an invoice when the item is not an inventory item (for example, 'Consulting Services'). You define standard memo lines to speed data entry when creating your transactions.

Standard Request Submission: A standard interface in Oracle Applications in which you run and monitor your application's reports and other processes.

Standard Costing: A standard costing method uses a predetermined standard cost for charging material, resources, overhead, period close, job close, and cost update transactions as well as valuing inventory. Any deviation in actual costs from the predetermined standard is recorded as a variance.

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 Receivables automatically updates your general ledger and re-opens the debit items you closed by reversing the original payment.

start organization: An organization that defines a set which 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 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 Payables includes the statistical quantity in the journal entries it creates for General Ledger during posting. You must use 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 General Ledger, 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 indicator or lamp informs you that the current window is in insert character mode; and the lamp appears when a list of values is available for the current field.

step-down allocation

In Oracle General Ledger, a group of allocations that are ordered so that the posted results of one step are used in the next step of the AutoAllocation set. 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.

step-down allocation: In Oracle Projects, a set of allocation rules that carries out the rules (steps) an autoallocation set serially, in the sequence specified in the set. Usually the result of each step will be used in the next step. Oracle Workflow controls the flow of the autoallocations set. See also autoallocation set, parallel allocation

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 that 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 subinventory is a subdivision of an organization that represents either a physical area or a logical grouping of items, such as a storeroom or receiving dock.

subledger: A subledger is an application other than General Ledger where accounting entries can originate.

subledger accounting entries: The Global Accounting Engine keeps its own accounting entries and reference information in the subledger tables. The accounting entries along with the reference information are needed for legal requirements, such as daily journals or customer/supplier balances.

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.

supplier: A business or individual that provides goods or services or both in return for payment.

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. You can also select one pay site as your primary pay site. See also pay site, purchasing site, RFQ only site.

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 other characteristics. 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 Oracle database is divided to hold tables.

target: A project, task, or both that receives allocation amounts, as specified by an allocation rule. See also source pool

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 that 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 that 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 Receivables, tax authority consists of all components of your tax structure. For example: California.San Mateo.Redwood Shores for State.County.City. Oracle Receivables adds together the tax rates for all of these locations to determine a customer's total tax liability for an invoice.

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, tax type, taxable basis, tax controls, and tax accounting. You can define a tax code for inclusive or exclusive tax calculation. Oracle Receivables lets you choose state codes as the tax code when you define sales tax rates for the United States. (Receivables Lookup)

tax engine: A collection of programs, user defined system parameters, and hierarchical flows used by Oracle Receivables to calculate tax.

tax exempt: A customer, business purpose, or item to which tax charges do not apply. See also exemption certificate.

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. In some countries this value is called a NIF.

tax distribution: 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 on Assets: The Tax on Assets (Impuesto al Activo or IMPAC) is a special tax that is paid in Mexico. The amount to be paid is calculated from inflation-adjusted amounts for cost, accumulated depreciation, and depreciation expense, and from Tax on Income amounts.

Tax on Income: The Tax on Income (Impuesto Sobre la Renta or ISR) is a special tax that is paid in Mexico. The amount to be paid is calculated from the inflation-adjusted amounts for cost, accumulated depreciation, and depreciation expense.

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, Invoice Validation places the invoice on hold.

tax type: A feature you use to indicate the type of tax charged by a tax authority when you define a tax name. Receivables uses the tax type during invoice entry to determine the financial impact of the tax. When you enter a tax of type Sales, Receivables creates a separate invoice distribution line for the tax amount. When you enter a tax of type Use, Receivables does not create the invoice distribution line.

TCA registry: The central repository of party information for all Oracle applications. The party information includes details about organizations and people, the relationship among the parties, and the places where the parties do business.

template: A pattern that Oracle General Ledger uses to create and maintain summary accounts. For each template you specify, General Ledger automatically creates the appropriate summary accounts.

third party: A generic term for supplier, customer, or an inventory organization.

third party subidentification: A generic term for a customer address, a supplier site, or a subinventory.

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 Payables 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: A 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. Invoice Validation uses the tolerance levels you define to determine whether to hold or validate invoices for payment. See also Matching Tolerances, Tax Tolerances.See reconciliation tolerance.

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.

TP: Translation Program. See also AX Program.

transaction code: In Oracle Payables, a 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 Payables 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 code: In Oracle Cash Management, you define transaction codes that your bank uses to identify different types of transactions on its statements. For example, your bank may use transaction codes T01, T02, and T03 to represent debit, credit, and stop payment.

transaction currency: The currency in which a transaction originally takes place. For processing purposes, the reimbursement currency in an expense report is the transaction currency.

transaction type: In Oracle Receivables, an invoice control feature that lets you specify default values for invoice printing, posting to the general ledger, and updating open receivable balances.

transaction type: In Oracle Assets, the kind of action performed on an asset. Transaction types include addition, adjustment, transfer, and retirement.

transaction type: In Oracle Cash Management, transaction types determine how Cash Management matches and accounts for transactions. Cash Management transaction types include Miscellaneous Receipt, Miscellaneous Payment, Non-Sufficient Funds (NSF), Payment, Receipt, Rejected, and Stopped.

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. See also batch source.

transaction batch sources

See batch source

foreign currency translation.

Translate Events: A program that transfers accounting entries into subledger tables.

transfer to GL: The process of transferring accounting entries from Oracle subledger applications to the GL_INTERFACE table in General Ledger. When entries are transferred from the subledgers, the subledger system marks the entries in the subledger tables as posted, even though they have not been posted in General Ledger. Entries modify General Ledger balances only when Journal Import is run and the subsequent entries are posted.

transferred date: The date on which you transfer costs, revenue, and invoices to other Oracle Applications.

transformation function: A seeded or user-defined rule that transforms and standardizes TCA attribute values into representations that can assist in the identification of potential matches.

transition: In Oracle Workflow, the relationship that defines the completion of one activity and the activation of another activity within a process. In a process diagram, the arrow drawn between two activities represents a transition. See also activity, Workflow Engine.

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 Receivables, 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 apply it to 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)

unclaimed property: In Payables, payments that have not cleared an internal bank account. Usually this happens when a payee did not receive a check payment, or received it and never deposited it.

unearned discounts: Discounts your customers are allowed to take if they pay for their invoices after the discount date. (The discount date is determined by the payment terms.) You can specify at the system level whether you want to allow customers to take unearned discounts. See also payment terms.

unearned revenue: Revenue received and recorded as a liability or revenue before the revenue has been earned by providing goods 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 Receivables retains unidentified payments for you to process further.

unit of measure: A classification created in Oracle General Ledger that you assign to transactions in General Ledger and subledger applications. Each unit of measure belongs to a unit of measure class.

For example, if you specify the unit of measure Miles when you define an expenditure type for personal car use, Oracle Projects calculates the cost of using a personal car by mileage. Or, in Oracle Payables, you define square feet as a unit of measure. When you enter invoices for office rent, you can track the square footage addition to the dollar amount of the invoice.

In Oracle Assets, a label for the production quantities for a units of production asset. The unit used to measure production amounts.

unit of measure classes: Groups of units of measure with similar characteristics. Typical units of measure classes are Volume and Length.

units of production depreciation method: A depreciation method that 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 Assets multiplies this fraction by the asset's recoverable cost.

unrealized gain or loss: The change in value, in functional currency units, of a foreign currency-denominated account, measured over an accounting period. See also realized gain or loss.

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 that 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 General Ledger does not create an invoice distribution or general ledger journal entry for the tax.

US Sales and Use tax: Levied on the end consumer, prior stages of supply are exempt by certificate awarded by the state of the recipient. Government and other organizations are exempt by statute. Many taxes may apply to a single transaction, including state, County, City, Transit, and Muni tax. Monthly returns to each state are required only if the operating company is registered for business within that state. Monthly reporting of Sales and Use tax can be on an accrual or cash basis.

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

Validation: Invoice Validation is a feature that prevents you from paying an invoice when your supplier overcharges you or bills you for items you have not received, ordered or accepted. Validation also validates tax, period, currency, budgetary, and other information. If you use budgetary control and encumbrance accounting, Validation also creates encumbrances for unmatched invoices or for invoice variances. Validation prevents payment or accounting of invoices that do not meet defined validation criteria by placing holds on the invoice. Validation also releases holds when you resolve invoice exceptions. You must submit Validation for each invoice to pay and account for the invoice. Validation was called Payables Approval in previous releases.

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 General Ledger, 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.

VAT: See value added tax.

vendor: See supplier.

View Transactions: A feature used to look at translated transactions, even before these transactions are transferred to General Ledger. You can search by account, third party, or third party subidentifier.

void check stock: A feature you use to void a range of blank check stock.

voucher: A generic term for accounting entries created from a transaction for a document, such as an invoice or credit memo.

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

weighted-average exchange rate

An exchange rate that Oracle General Ledger 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. General Ledger 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 General Ledger uses to translate your functional currency into a foreign currency for your transactions. Oracle Payables provides transaction information based on daily rates you enter in the system and rate exceptions you define for individual transactions. This transaction information allows 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 window, 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 Payables withholds tax for an invoice distribution line that has a Withholding Tax type tax name assigned to it.

word replacement: A word mapping that is used to create synonyms which are treated as equivalents for searching and matching.

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.

Workflow Engine: The Oracle Workflow component that implements a workflow process definition. The Workflow Engine manages the state of all activities, automatically executes functions, maintains a history of completed activities, and detects error conditions and starts error processes. The Workflow Engine is implemented in server PL/SQL and activated when a call to an engine API is made. See also Account Generator, activity, function, item type.

Write-off Limits: Limits that you set at the system and user levels for creating receipt write-offs. Oracle Receivables enforces the limits that you define when users write-off receipts. Users can only write off receipt balances within their user limit for a given currency and the total cumulative write-off amount cannot exceed the system level write-off limit.

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

XML: Extensible Markup Language. A system for defining, validating, and sharing document formats.

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

Zengin: The standard file format for bank transfers in Japan. You can transfer this type of bank file into Receivables using AutoLockbox. If you want to import bank files in the Japanese Zengin format into Receivables using AutoLockbox, specify in the Transmission Formats window the character set that you will use.

Zoom: A forms feature that is obsolete in GUI versions of Oracle Applications.

Oracle Apps, ADF, SOA

Monday, April 16, 2012

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

You Can Search This Blog Here

Print

Vijaya Kumar Bondada

Contact

My Sites

Demo Instances

Recommended Sites

Topics

Blog Archive

Total Pageviews