Glossary

allocated on hand

Inventory amount posted by a trading partner indicating the quantity of inventory physically in stock that is intended for the use of the trading partner receiving the communication. The date be used by the trading partner for this order type is Actual Date. This indicates the physical inventory held by the trading partner for the intended purpose.

amount based order

An order you place, receive, and pay based solely on the amount of service you purchase.

anchor date

The start date of the first repetitive planning period. It introduces consistency into the material plan by stabilizing the repetitive periods as time passes so that a plan run on any of the days during the first planning period does not change daily demand rates.

annual carrying cost

Cost of carrying inventory, defined as a percent of the dollar value of inventory per year.

ANSI

American National Standards Institute which establishes national standards for the United States. The parent organization for X12 and also serves as the North American representative to ISO (International Standards Organization).

ANX

Automotive Network Exchange. A common, global TCP/IP network infrastructure created to meet the data communications needs of the automotive industry. Using ANX, each automotive supplier and OEM needs only a single commercial grade TCP/IP data transport connection to communicate globally with all trading partners. This network meets specific automotive industry requirements for performance, reliability, security and management.

API

An application programming interface (API) is a published interface to accomplish a business or scientific function. An API defines a contract to its users by guaranteeing a published interface but hides it's implementation details.

assemble to order (ATO) item

An item you make in response to a customer order.

assemble to order (ATO) model

A configuration you make in response to a customer order that includes optional items.

assembly

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

available to promise (ATP)

Refers to the ability to promise finished goods availability based on a statement of current and planned material supply.

ATP

See available to promise.

ATR

See available to reserve.

ATS

Authorized To Ship. This term applies to sales order lines eligible to enter the workflow processes which ultimately result in shipment of the product to the customer (such as production, departure planning, picking, and ship/confirm). It distinguishes them from sales order lines which are not eligible for any shipment related processing.

ATT

See available to transact.

attachment

Any document associated with one or more application entities. You can view attachments as you review and maintain an entity. Examples include: operation instructions, purchase order notes, item drawings, or an employee photo.

attribute

A basic data element used by Oracle Pricing to control pricing activity. For example, Pricing uses attributes to define the eligibility of a customer order to receive a particular price or modifier. In Oracle Pricing, individual attributes are obtained from data sources that are called contexts. Pricing attributes may also be used as elements of a pricing formula.

attribute collection element

A collection element that represents the outcome of a process. See collection element types.

Attribute / Domain

An Attribute, as used here, is a Web Applications Dictionary term used to describe the common properties of fields that have same semantics. For example, Customer name attribute can be reused anytime where the name of a customer need to be represented in the system. Syn. Domain. In some part of this document, the term WAD: Attribute is used instead, to avoid confusion with the generic usage of 'Object. Attribute '

authorization

The act of marking a notification as approved or not approved. This would release or confirm the Hold on an Order.

authorization check

A set of tests on a purchasing document to determine if the document approver has sufficient authority to perform the approval action.

authorized quantity

The authorized quantity is how many of an item that can be sent back to the warehouse from the customer. This is the booked quantity.

AutoAccounting

A feature used by Oracle Projects to automatically determine the account coding for an accounting transaction based on the project, task, employee, and expenditure information. 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.

autocharge

A method of charging a discrete job or repetitive schedule for the resources consumed at an operation.

autoimplement

To implement an ECO's revised item automatically on its effective date by setting the revised item status to Scheduled and running the autoimplement manager.

autoimplement manager

An Engineering program that automatically implements all ECO revised items with a status of Scheduled and whose effective date is less than or equal to the current date.

AutoInvoice

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

Automated Clearing House (ACH)

A nationwide network operated by the Federal Reserve used to connect banks together for the electronic transfer of funds.

Automatic Modifier

In Oracle Pricing, a control that allows you to specify that the Pricing Engine apply a modifier automatically to a transaction, assuming that the transactions meets the qualifier eligibility.

automatic note

A standard note to which you assign addition rules so it can be applied automatically to orders, returns, order lines, and return lines. see one time note, standard note.

automatic numbering

A numbering option Purchasing uses to assign numbers to your documents, employees, or suppliers automatically.

automatic rescheduling

Rescheduling done by the planning process to automatically change due dates on scheduled receipts when it detects that due dates and need dates are inconsistent.

automatic sourcing

A Purchasing feature which allows you to specify for predefined items a list of approved suppliers and to associate source documents for these suppliers. When you create a requisition or purchase order line for the item, Purchasing automatically provides appropriate pricing for the specified quantity based on the top ranked open source document for the supplier with the highest percentage allocation.

Automotive Address Extras

Used since Release 11 of Oracle Automotive. The Automotive Address Extras represented ship from/ship to data that was established in Oracle Automotive, and exported to Radley CARaS. Note that automotive address extras are not used in Release 11i. Instead, the ship from/ship to terms window is used to store information critical to Oracle Release Management.

autonumber

A function to automatically default engineering change order (ECO) numbers when you create a new ECO. You can define an autonumber prefix and sequence for all users across all organizations, all users in one organization, one user across all organizations, and one user in one organization.

autorelease

To automatically release the next available repetitive schedule upon completion of the current repetitive schedule.

autoschedule

You can set up a supplier/site/item to have the schedules built by the concurrent program autoschedule. The schedules are not built by the Scheduler's Workbench.

available capacity

The amount of capacity available for a resource or production line.

available to promise (ATP)

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

available to promise quantity

See available to promise (ATP).

available to promise rule

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

Available To Reserve (ATR)

The quantity of on hand stock available for reservation. It is the current on hand stock less any reserved stock.

Available To Transact (ATT)

Quantity on hand less all reservations for the item which may be transferred within or out of inventory.

average costing

A costing method which can be used to cost transactions in both inventory only and manufacturing (inventory and work in process) environments. As you perform transactions, the system uses the transaction price or cost and automatically recalculates the average unit cost of your items.

average cost variance

A variance account used to hold amounts generated when on hand inventory quantity is negative and the unit cost of a subsequent receipt is different from the current unit cost.

backflush operation

A routing operation where you backflush component items.

backflush transaction

A material transaction that automatically issues component items into work in process from inventory when you move or complete the assembly. Also known as post deduct or pull. See pull transaction.

backorder

An unfulfilled customer order or commitment. Oracle Order Management allows you to create backorders automatically or manually from released order lines. See Pick Release.

backordered lines

Unfulfilled order line details which have failed to be released at least once by Pick Release or have been backordered by Ship Confirm.

backward consumption days

A number of days backwards from the current date used for consuming and loading forecasts. Consumption of a forecast occurs in the current bucket and as far back as the backward consumption days. If the backward consumption days enters another bucket, the forecast also consumes anywhere in that bucket. When loading a forecast, only forecasts of the current date minus the backward consumption days are loaded. Therefore, you can use backward consumption days to load forecasts that are past due.

backward scheduling

A scheduling technique where you specify a production end date and Oracle Manufacturing calculates a production start date based on detailed scheduling or repetitive line scheduling.

balancing entity

An organization for which you prepare a balance sheet, represented as a balancing segment value in your accounting flexfield. This is the equivalent of a fund in government organizations. Examples include companies, strategic business units, and divisions.

balancing out

The process of monitoring and balancing production of a scheduled item as it moves into a later phase in its life cycle. The item's planned change in status may be known up to a year in advance, and is closely monitored during the last few months of the model year by both the customer and supplier.

balancing segment

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

bankers automated clearing system (BACS)

The standard format of electronic funds transfer used in the United Kingdom.

base currency

See functional currency.

Base Layer

The generic code independent of a Trading Partner. It consists of PL/SQL program units published as customizable by Oracle Development teams. Trading Partner Layers can be built only on those program units designated by an Oracle Development team as published.

base model

The model item from which a configuration item was created.

Base Price

The original price for an item obtained from the Price List; the price before any price adjustments are applied. Also known as List Price.

base unit

The unit of measure to which you convert all units of measure within one class. The base unit is the smallest or most commonly used unit of measure in the class. For example, millimeter is the base unit in the Length class. You define your base unit of measure when you create your unit class.

basic ATP

This term is used to describe the task of performing an ATP check against a given organization.

batch sources

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

behind

Quantities were not delivered in time (past due) in context of the customer's anticipated delivery date, or an under shipment occurred. The supplier must control this situation in such a way that he will deliver these quantities as soon as possible. See: ahead.

Benefits

In Oracle Pricing, modifiers that result in non monetary adjustments to an order. Types of benefits include: Item upgrade, free items, change in payment or shipment terms. See also Price Adjustments.

best discount

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

best price

The modifier which gives the lowest price or most advantageous price to the customer on the given pricing line will be applied.

best price

An alternative method to precedence which is used to determine which modifier should be selected when multiple modifiers in the same exclusivity or incompatibility group are eligible to be applied to the same pricing line within a pricing phase. The modifier which gives the lowest price or most advantageous price to the customer on the given pricing line will be applied. See also Precedence.

bill of distribution

Specifies a multilevel replenishment network of warehouses, distribution centers, and manufacturing centers (plants).

bill of lading

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

Bill of Material

A list of component items associated with a parent item and information about how each item relates to the parent item.

bill of material

A list of component items associated with a parent item and information about how each item relates to the parent item. Oracle Manufacturing supports standard, model, option class, and planning bills. The item information on a bill depends on the item type and bill type. The most common type of bill is a standard bill of material. A standard bill of material lists the components associated with a product or subassembly. It specifies the required quantity for each component plus other information to control work in process, material planning, and other Oracle Manufacturing functions. Also known as product structures.

bill of resource set

A group of bills of resources. A bill of resource set can have one or many bills of resources within it.

bill of resources

A list of each resource and/or production line required to build an assembly, model, or option.

branch

A link between a Trading Partner Layer program unit and a Base Layer program unit.

bucket days

The number of workdays within a repetitive planning period.

bucket type: daily

Bucket based on a single calendar day.

bucket type: flexible

When the customer specifies the start date and end date of the bucket, instead of using standard bucket types of daily, weekly, monthly or quarterly.

bucket type: monthly

Bucket based on a calendar month.

bucket type: quarterly

Bucket based on calendar quarters (Jan - Mar, Apr - Jun, Jul - Sep, Oct - Dec.)

bucket type: weekly

Bucket based on a weekly interval, usually Monday through Sunday.

bucket patterns

Bucket patterns can be defined to include daily, weekly, monthly, or quarterly buckets. Bucket patterns are used to bucket quantity requirements on Planning or Shipping Schedules.

Buckets: Pricing

A feature in Oracle Pricing that determines how modifier price adjustments are applied to the list price of an item to calculate the selling price. Modifiers use the previous buckets sub total for percentage calculation. Modifiers within the same bucket are Additive i.e. added together, and subtracted from the previous buckets total. The user can create an unlimited amount of buckets to calculate selling price. For example, discounts associated with bucket 0 use list price as their calculation basis. Bucket 1 prices use the subtotal resulting from subtracting bucket 0 discounts from list price as their calculation. Bucket 2 uses the subtotal remaining after subtracting bucket 1 discounts from the bucket 0 subtotal, and so forth.

budget organization

An entity, such as a department, division, or activity responsible for entering and maintaining budget data. You define budget organizations for your agency, then assign appropriate accounting flexfields to each budget organization.

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.

build sequence

The sequence of jobs within a schedule group. For example, you can use sequences to prioritize all jobs on a specific production line by customer. Similarly, you can use sequences to insure that jobs are built in reverse departure order thus facilitating truck loading. See schedule group.

bulk items

Component items on a bill of material not usually transacted directly to the job or repetitive schedule. Bulk items are usually charged to the work in process department where the item is consumed.

bulk requirement

See bulk items.

business application

Software that performs a particular business function or group of functions (accounts payable, for example).

business document

A document used for conducting business between two trading partners; a purchase order or invoice, for example.

business group

An organization which represents the consolidated enterprise, a major division, or an operation company. This entity partitions Human Resources information.

business object

An independent item of significance in the business world, such as an order.

business purpose

The function a particular customer location serves. For example, you would assign the business purpose of Ship To an address if you ship to that address. If you also send invoices to that address, you could also assign the business purpose Bill To. Bill To and Ship To are the only business purposes recognized in Oracle Order Management. Each customer location must serve at least one function.

buyer

Person responsible for placing item resupply orders with suppliers and negotiating supplier contracts.

buyer/customer and supplier/vendor

The term supplier and Vendor are used synonymously in discussions about EDI transactions. The term buyer and customer are used synonymously in discussion about EDI transactions. The business entities are the trading partners for the PO Change transaction.

by product

Material produced as a residual of a production process. Represented by negative usage in the bill of material for an assembly.

calculate ATP

An item attribute the planning process uses to decide when to calculate and print available to promise (ATP) for the item on the Planning Detail Report. The planning process calculates ATP using the following formula: ATP = Planned production - committed demand.

Calculation Engine

In Oracle Pricing the calculation engine is a part of pricing engine. It returns the price of an item/service.

Calculation Formula

One of the most important tasks of a Kanban planning system is determining the optimal number of Kanban cards. The Kanban planning software takes care of this calculation provided you enter correct values for Kanban size, average daily demand for the Kanban item, and the lead time to replenish one Kanban. We provide a package that you can use to customize the calculation. See the Oracle Manufacturing, Distribution, Sales and Service Open Interfaces Manual. By default, the standard calculation is: (C - 1) * S = D * (L + SSD) where: C is the number of Kanban cards S is the Kanban size D is the average daily demand L is the lead time (in days) to replenish one Kanban. If you think through the Kanban process, you will see why this formula works best when the demand for the Kanban item is steady. In addition to this basic formula, when the calculation program calculates Kanban size, it takes into account the values for the following order modifiers (specified in the pull sequence), in the following order: Supply Days, Minimum Order Quantity, and Lot Multiplier. For example, suppose you have specified the Minimum Order Quantity for a particular item to be 50. You want the formula to calculate the Kanban size (S), so you enter values for S, D, and L. Even though strictly based on the values you enter for C, D, and L, the formula should yield 40, the actual Kanban size will be 50 because of your order modifier, assuming the Lot Multiplier is a factor of 50.Note: The program uses order modifiers only when calculating the Kanban size. If you specify the Kanban size and want the program to calculate the number of Kanban cards, the program does not use order modifiers.

calendar type

The period pattern used to define a manufacturing calendar.

capable to promise

CTP (Capable to Promise) refers to the additional ability to determine the availability of component materials and resources to meet unplanned demands.

capacity modification

Deviation to available resources for a specific department shift.

capacity requirements planning

A time phased plan comparing required capacity to available capacity, based on a material requirements plan and department/resource information. See routing based capacity and rate based capacity.

component demand

Demand passed down from a parent assembly to a component.

component item

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

compound discounts

Discounts that are applied on top of already discounted prices. See buckets, pricing.

compression days

The number of days the planning process suggests you compress the order (in other words, reduce the time between the start date and the due date).

concurrent manager

Components of your applications concurrent processing facility that monitor and run time consuming tasks for you without tying up your terminal. Whenever you submit a request, such as running a report, a concurrent manager does the work for you, letting you perform many tasks simultaneously.

concurrent process

A task in the process of completing. Each time you submit a task, you create a new concurrent process. A concurrent process runs simultaneously with other concurrent processes (and other activities on your computer) to help you complete multiple tasks at once with no interruptions to your terminal.

concurrent queue

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

concurrent request

A request to complete a task for you. You issue a request whenever you submit a task, such as running a report. Once you submit a task, the concurrent manager automatically takes over for you, completing your request without further involvement from you, or interruption to your work. Concurrent managers process your request according to when you submit the request and the priority you assign to your request. If you do not assign a priority to your request, your application prioritizes the request for you.

confidence percent

The degree of confidence in a forecast that the forecasted item becomes actual demand. When loading schedules from a forecast, the confidence percent is multiplied by the forecast quantity to determine the schedule quantity.

config item

An item which represents a unique configuration of model (ATO) and it's classes and options. A customer will enter his choice of classes and options for a given ATO model. This valid configuration of selected items is represented by a config item. A config item goes through the manufacturing process cycle, and is a shippable item.

configuration

A product a customer orders by choosing a base model and a list of options. It can be shipped as individual pieces as a set (kit) or as an assembly (configuration item).

configuration bill of material

The bill of material for a configuration item.

configuration item

The item that corresponds to a base model and a specific list of options. Bills of Material creates a configuration item for assemble to order models.

configuration variance

For Work in Process, this quantity variance is the difference between the standard components required per the standard bill of material and the standard components required per the work in process bill of material. Currently, this variance is included with the material usage variance.

configurator

A window that allows you to choose options available for a particular model, thus defining a particular configuration for the model.

configure to order

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

consigned location

The physical location of inventories that resides on the property of buyers and sellers through a consigned agreement with the manufacturer.

consigned to (name of consignee)

Show the exact name of the receiver of the goods, whether an individual person, party, firm or corporation. Note: When tendering a "Collect on Delivery shipment, the letters C.O.D. must be inserted before the name of the consignee.

consume shortage backward

An option used to calculate ATP information by using surplus quantity from prior periods to cover a period shortage.

consume shortage forward

An option used to calculate ATP information by using surplus quantity from future ATP periods to cover a period shortage.

contact

A representative responsible for communication between you and a specific part of your customer's agency. For example, your customer may have a shipping contact person who handles all questions regarding orders sent to that address. The contact's responsibility is the contact role.

contact notifications

How will we notify given contacts when certain business conditions arise. For example, if a shipment of product to a customer is going to be late, you may wish to notify the account manager that they should call the customer and let them know the problem.

contact role

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

container

The receptacle (box, tank, etc.) in which items to be shipped are placed.

contest field prompt

A question or prompt to which a user enters a response, called 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

A data source used by Oracle Pricing to obtain attributes. For example, Oracle Pricing considers the customer order itself to be a context. Various attributes from the order, such as order date, can be used by Pricing to control the selection of a price or modifier. Oracle Pricing does not limit the number of contexts that can be defined. Any single context can supply up to 100 pricing attributes. See also Dimension.

context element

A collection element associated with a quality collection transaction. Values for context elements are automatically transferred to Oracle Quality as their parent collection transaction are entered.

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

An agreement between you and a supplier for unspecified goods or services. This agreement may include terms and conditions, committed amount, and an effective and expiration date. You reference contract purchase agreements directly on standard purchase order lines. Purchasing monitors the amount you have spent against contract purchase agreements.

conversion

Converts foreign currency transactions to your functional currency. See foreign currency conversion.

conversion formula

The number that, when multiplied by the quantity of one unit of the source base unit, gives you the quantity of one unit of the destination base units in the interclass conversion. The number is also the conversion between units for standard unit conversion or item specific conversion.

copy

An AutoCreate option that lets a buyer designate a specific requisition line as the source of information that Purchasing copies to the purchase order or RFQ line.

corporate exchange rate

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

cost base

The grouping of raw costs to which burden costs are applied.

cost breakdown category

Breakdown of a project or task budget to categorize costs. You can categorize by expenditure category, expenditure type, job, or expenditure organization.

cost distribution

Calculating the cost and determining the cost accounting for an expenditure item.

cost element

A classification for the cost of an item. Oracle Manufacturing supports five cost elements: material, material overhead, resource, outside processing, and overhead.

cost group

An attribute of a project which allows the system to hold item unit costs at a level below the inventory organization. Within an organization, an item may have more than one cost if it belongs to multiple cost groups. Item costing can be specific to a single project if each project has a distinct cost group, or specific to a group of projects if all projects in that group are assigned to the same cost group.

Cost of Goods Sold Account

The general ledger account number affected by receipts, issuances and shipments of an inventory item. Oracle Order Management allows dynamic creation of this account number for shipments recording using the OE Account Generator item type in Oracle Workflow. See Account Generator.

cost sub element

A subdivision of cost element. You can define unlimited cost subelements for each cost element.

cost transaction

The financial effect of your material, resource, overhead, job, and period example, each material quantity transaction may have several cost accounting entries, and each accounting entry is a cost transaction.

cost type

A set of costs for items, activities, resources, outside processing, and overheads. You may have unlimited cost types for each organization, but only one is used to record cost transactions. The Frozen Standard cost type is used for standard costing; the Average Costs type is used for Average costing. Others could be defined for simulation or temporary purposes.

cost variance

The difference between the actual and expected cost. Oracle Manufacturing and Payables supports the following cost variances: invoice price, resource rate, and standard cost variances.

cotermination

Setting the same end date for all ordered or renewed service programs.

count point operation

A default operation to move to and from where you record move and charge resource transactions. Also known as pay point.

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. See credit profile class, credit check rule.

credit check rule

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

credit memo

A document that partially or fully reverses an original invoice amount.

credit memo reasons

Standard explanations as to why you credit your customers. See return reason.

credit order type

This is any header level transaction type that allows for return lines. The type is used to specify defaulting values for this credit order and an associated workflow.

Critical Attributes

Optional Matching Attributes should always have a value as turnaround data, regardless of what schedule type is associated with the demand. If this flag is on and the attribute does not have a value, the Demand Processor will issue a warning exception identifying it.

critical path

The series of operation start and completion dates and times that result from the detailed scheduling algorithm.

cross reference

A user defined link from an item number to another piece of information.

CRP planner

A process that may optionally be run as part of the planning process. The CRP planner calculates capacity requirements for resources and production lines using the material requirements calculated by the planning process.

CSR

Customer Service Representative

CUM

Total received for a supplier site, item, and organization within a CUM Period.

CUM entity

The identifier of the customer's business entity applicable for CUM Management when the supplier ships to a particular customer location. This may be the Ship To Location, Deliver To Location or Bill To Location, depending on the CUM Entity Type assigned to the Ship To/Ship From Terms relationship.

CUM entity type

The customer's business entity type applicable for CUM Management when the supplier ships to a particular customer location. The valid CUM Entity Types are: Ship To/Ship From, Bill To/Ship From, Deliver To/Ship From, Ship To/All Ship Froms, Bill To/All Ship Froms, Deliver To/All Ship Froms.

CUM key

The set of attribute values applicable to accumulation of shipments and CUM adjustments of a Customer Item in a Ship To / Ship From relationship. The applicable attributes are determined by the CUM Management Type and CUM Entity selected for the Ship To / Ship From relationship; the applicable values are captured at the time the CUM Key is created.

CUM management type

The style of CUM Management applicable to a customer/supplier relationship. One of six styles of CUM Management may be associated with a customer/supplier relationship: No CUM Management, CUM By Date, CUM By Date/Record Year, CUM By Date/PO, CUM By Purchase Order, CUM Until Manual Reset at Item.

CUM period

A defined period of time during which cumulative shipment, requirement, and resource authorization quantities are calculated, e.g. Record keeping year, Calendar Year, or life of Purchase Order. In the automotive industry, the CUM Period typically coincides with a customer's scheduled plant shutdown for record keeping year tooling changeovers. All ship from locations to the same customer destination will share the same CUM Period.

CUM Rule

The definition of how the CUM is to be calculated for Customer Items under Release Management within a specific Ship To/Ship From relationship. The rule consists of the following components: CUM Management Type, CUM Entity, CUM Start Date, Shipment Inclusion Rule.

cumulative discounts

Discounts whose percentages are summed up before applying the discount are referred to as Cumulative Discounts.

cumulative manufacturing lead time

The total time required to make an item if you had all raw materials in stock but had to make all subassemblies level by level. Bills of Material automatically calculates this value. Purchased items have no cumulative manufacturing lead time.

cumulative received quantity

The total quantity of goods (e.g. shipped or received) during a defined period of time, e.g. Model Year. This can be used by suppliers to represent year to date shipped and by trading partners as year to date received.

cumulative total lead time

The total time required to make an item if no inventory existed and you had to order all the raw materials and make all subassemblies level by level. Bills of Material automatically calculates this value.

cumulative yield

Product of the yields at each operation, process, or event on a flow line.

current aggregate repetitive schedule

The sum of all current work in process repetitive schedules for an item for all lines for a given period in terms of a daily rate, and a start and end date. Current aggregate repetitive schedules can be firm or partially firm. If all current repetitive schedules for an item are firm, then the current aggregate repetitive schedule for the item is also firm. If some, but not all the current repetitive schedules for an item are firm, then the current repetitive schedule is partially firm.

current average cost

The current weighted average cost per unit of an item before a transaction is processed. See new average cost.

current date

The present system date.

current on hand quantity

Total quantity of the item on hand before a transaction is processed.

current projected on hand

Quantity on hand projected into the future if scheduled receipts are not rescheduled or cancelled, and new planned orders are not created as per recommendations made by the planning process. Calculated by the planning process as current supply: (nettable quantity on hand + scheduled receipts) gross requirements. Note that gross requirements for projected on hand does not include derived demand from planned orders. Note also that the planning process uses current due dates rather than suggested due dates to pass down demand to lower level items.Seeprojected available balance.

customer

The organization which is in the process of placing an order with the company.

customer address

A location where your customer can be reached. A customer may have many addresses. You can also associate business purposes with addresses. Also known as customer location. See customer site.

customer agreement

See agreement.

customer agreement type

See agreement type.

customer bank

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

customer business purpose

See business purpose.

customer class

A method to classify and group your customers. For example, you could group them by their business type, size, or location. You can create an unlimited number of customer classes.

customer control number

AIAG term for an external customer's order number for a finished good, e.g. a vehicle, apart from job numbers assigned in the production process.

customer family agreement

An agreement for a specific customer, available to any related customer. see agreement, generic agreement.

customer interface

A program that transfers customer data from foreign systems into Oracle Receivables.

customer interface tables

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

customer item

Allows you to define specific attributes for items per customer class, customer and ship to/bill to location. Demand Tolerance is an example for such an attribute.

customer/item model

Allows you to define specific attributes for items per customer class, customer and ship to/bill to location. The loading order forward/reverse inverted/non inverted is an example of this attribute.

customer item number

Item Number used only by a particular customer, and it represents the item's name used in the customer's organization.

customer item Vs. supplier item

In Oracle Order Management, the term 'item' refers to the supplier's item. In Oracle Order Management, the term ' customer item' refers to the item as in the customer's application.

customer item/order item

In Oracle Order Management the term 'item' refers to the supplier's item. In Oracle Order Management the term 'customer item' is exactly that.

customer job number

The number customers assign to jobs on their production line. These numbers are arbitrarily assigned and not sequential.

customer line number Vs. supplier line number

The term 'customer line number' represents the line sequence number as defined in the Purchasing application. Once this number or code is assigned to a line in the Purchase Order, it should not be changed. The general term 'supplier line number' or Oracle Order Management's 'order line number' represents the line sequence number as defined in the Order Management application. Once this number or code is assigned to a line in the sales order, it should not be changed.

customer location

See customer address.

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 model serial number

In the Automotive industry, this is the Vehicle Identification Number (VIN).

customer phone

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

customer product

An entity that identifies a serviceable item or customer product. The customer product identifies not only the product and the customer, but also the product quantity, the product's serial number (if the product is under serial number control and has been assigned a serial number), the location of the product, the various contacts, such as service administration, support, and bill to associated with the product. A customer may have several of the same customer products.

customer product line number

A customer (trading partner) may have several production lines at their manufacturing facility. The production line number identifies a specific production line, where goods should be delivered to as per the customers specifications.

customer production line number

The identifier for the customer's production line, i.e. the line on which they are building the product. This can affect the delivery and departure if, for example, the customer wants all items for production line A123 to be on the same delivery.

customer production sequence number

A customer (trading partner) may have a particular sequence in which items are built into an assembly. For example, the customer may specify that the front axle of a car has a production sequence 45 assigned to it, while the production sequence of the rear axle is 46. see loading order sequence, planning production sequence number.

customer profile

A method used to categorize customers based on credit information. Oracle 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

These allow for grouping of customers with similar credit worthiness, business volume, and payment cycles. For each profile class you can define information such as credit limits, payment terms, statement cycles, invoicing, and discount information. The customer profile class when assigned to a customer provides the default values for this information.

customer relationship

An association that exists between customers that allows you to share agreements and bill to and ship to addresses.

customer site

A specific area or place, such as a building or a floor on a building, at a customer address. A customer address may have one or more related customer sites.

customer specification

See specification type.

customer status

The Active/Inactive flag you use to deactivate customers with whom you no longer do business. In Oracle Order Management, you can only enter orders, agreements, and returns for active customers, but you can continue to process returns for inactive customers. In Receivables, you can only create invoices for active customers, but you can continue collections activities for inactive customers.

Customs Invoice

An electronic or paper document for international shipments similar to a Ship Notice/Manifest, but including additional information to satisfy all customs requirements of the borders through which the shipment must pass, such as the value of the shipment, VAT code and amounts, tariff and duty information, port information, customs broker identification, exporter identification, import license information, and letter of credit information.

cutoff date

An indication of the last date to be included in a plan or horizon.

cycle counting

An inventory accuracy analysis technique where inventory is counted on a cyclic schedule rather than once a year.

daily line capacity

The daily production rate of assemblies on a production line. This is equal to the line speed (in hours) times the line production hours.

daily quantity

See daily rate.

daily rate

The number of completed assemblies a repetitive schedule plans to produce per day. Also known as production rate. See repetitive rate

data group

Specifies an ORACLE ID (user) and determines to which schema a responsibility's windows connect.

database diagram

A graphic representation of application tables and the relationships among them.

database view

Provides access to an underlying database table. You do not need to know how the data is stored to use a database view. There are two types associated with Oracle Quality: the collection plan results and the collection import results database views.

date

Attributes are used to communicate date values.

date effectivity

Method to control the configuration of an assembly by assigning date ranges for the parent/component relationships. Component selection by MPS and MRP is based upon which components are valid for the date the components are required.

days off

The number of consecutive days off a shift has before a day on.

days on

The number of consecutive days that a shift works before a day off.

deal

A Modifier List type in Oracle Pricing that is a child of the modifier list type Promotion. A Deal is a group of modifiers that share the same header level qualifications and are reported together. A Deal is tied to a Promotion for reporting purposes only.

decimal precision

Decimal precision is the number of digits after the decimal point that will be displayed (with rounding).

default material task

Task to which project material costs are allocated if no matching rules are found for material task assignment. It is a rule with no material task assignment criteria specified.

default resource task

Task to which project resource costs are allocated if no matching rules are found for resource task assignment. It is a rule with no resource task assignment criteria specified.

defaulting

Defaulting refers to the supply of a value for a field that has no value.

defaulting

Used in Oracle Pricing to identify the supply of a value for an attribute. See sourcing.

defaulting condition

Defaulting condition is a Boolean condition built as a composite of defaulting criteria attribute validations, which will determine at run time how an object attribute should be defaulted.

defaulting condition

Used in Oracle Pricing to refer to the context/dimension name as well as the source system. Each attribute is defaulted differently according to which context is being defaulted.

defaulting criteria attributes

Defaulting criteria attributes are object attributes, that you can use to build defaulting conditions.

defaulting value

Information Oracle Order Management automatically enters depending on other information you enter.

delayed service order

An order for service against existing customer products. The service order is 'delayed' because service is ordered later than the product is ordered.

delete entity

An item, bill of material or routing you choose to delete.

delete group

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

delete subentity

A component or operation you choose to delete.

deletion constraint

A business rule that restricts the entities you can delete. A deletion constraint is a test that must succeed before an item, bill, or routing can be deleted.

delivering carrier

This information should be supplied where shipments may be interlined with other carriers.

deliver to contact (Ultimate Consignee)

How will we record or default the name of the person who will ultimately receive the goods. The goods may not be under the responsibility of the Sold From organization when they are delivered. This information may be needed by onward carriers after the sold from organization has fulfilled its obligations to the customer.

deliver to location

A location where you deliver goods previously received from a supplier to individual requestors.

delivery

Internal delivery of items to requestors within your organization.

delivery

A set of order lines to be shipped to a customer's ship to location on a given date in a given vehicle. Multiple deliveries can be grouped into a single departure. A single delivery may include items from different sales orders and may include backorders as well as regular orders.

delivery assignment

Defines the relationship of deliveries and child deliveries through consolidations as well as the relationship between delivery details and itself to track containerization of items.

delivery date

The date on which the product is to arrive at the Ship To Location. This date is either specified by the customer on a delivery based demand transaction, or calculated by applying in transit lead time to a customer specified Shipment Date.

delivery detail

Contains items to be shipped out of a warehouse. This may be a sales order line, an RMA line, a WIP line or a PO line. They can be referred to as deliverables.

Delivery Instruction (DELINS)

The Delivery Instruction Message is sent by a buyer to provide information regarding details for both short term delivery instructions and medium to long term requirements for planning purposes according to conditions set out in a contract or order.

delivery lead time

Time (in days) is takes for items to reach the customer once it is shipped. It accounts for any non working days in between.

delivery leg

A single segment of a delivery. Every delivery consists of at least two legs, when the delivery is picked up and dropped off, but may travel through several intermediate legs.

delivery line

A shippable and booked line from the planning pool which has been allocated to a delivery. After allocation, the line is no longer available in the planning pool. After the delivery is closed, the delivery line will also be considered closed.

Delivery Shipping Notice Outbound (DSNO)

An Advanced Ship Notice generated by Oracle e Commerce Gateway for a shipped delivery.

demand

Current or future product need communicated by the customer to the supplier, via EDI or other means. Sources of demand include Purchase Orders, Planning Schedules, Shipping Schedules, and Sequenced Production schedules.

demand class

A classification of demand to allow the master scheduler to track and consume different types of demand. A demand class may represent a particular grouping of customers, such as government and commercial customers. Demand classes may also represent different sources of demand, such as retail, mail order, and wholesale.

demand history

Historical inventory issue transactions against an item.

demand interface

A data collection point that collects and stores all sales order demand and reservation information.

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 Processor

The Oracle Release Management program that resolves items from an Oracle open interface demand schedule file, validates demand data against Oracle Applications information, then passes the demand into Oracle Order Management to create or replace sales order lines or into Oracle Planning (Oracle Master Scheduling/MRP and Oracle Supply Chain Planning) to create or replace forecasts.

demand schedule

A planning, shipping, or sequenced production schedule received by a supplier from a customer, usually in an EDI file format.

Demand Time Fence

Item attribute used to determine a future time inside which the planning process ignores forecast demand and only considers sales order demand when calculating gross requirements for an item. Use this attribute to identify a time fence inside which you wish to build to sales order demand only to reduce the risk of carrying excess inventory. A value of Cumulative manufacturing lead time means Master Scheduling/MRP calculates the demand time fence for the item as the plan date (or the next workday if the plan is generated on a non workday) plus the cumulative manufacturing lead time for the item. A value of Cumulative total lead time means Master Scheduling/MRP calculates the demand time fence for the item as the plan date (or the next workday if the plan is generated on a non workday) plus the total manufacturing lead time for the item. A value of Total lead time means Master Scheduling/MRP calculates the demand time fence for the item as the plan date (or the next workday if the plan is generated on a non workday) plus the total lead time for the item. A value of User defined time fence means Master Scheduling/MRP calculates the demand time fence for the item as the plan date (or the next workday if the plan is generated on a non workday) plus the value you enter for Planning Time Fence Days for the item.

Demand Time Fence Days

Item attribute used when you set the Planning Time Fence attribute to User defined time fence. Master Scheduling/MRP calculates the demand time fence for the item as the plan date (or the next workday if the plan is generated on a non workday) plus the value you enter here.

department

An area within your organization that consists of one or more people, machines, or suppliers. You can also assign and update resources to a department.

department class

A group of departments.

departure

A set of order lines that will be shipped in a specific vehicle on a given date/time. The departure may include multiple deliveries if items being shipped are destined for different customers or customer ship to locations.

departure order

The order of jobs within a schedule group. Jobs are normally sequenced within a schedule group in the order that they must be loaded onto the truck for shipment. see schedule group and build sequence.

departure planned lines

Scheduled delivery lines that have been planned for a specific departure.

departure planning

The process of planning the necessary vehicles and grouping the scheduled shipments that will be included in a given departure. Planning the departure requires consideration of vehicle load capacities, container capacities and, in the case of 866 (sequenced) transactions, the loading order required to satisfy the customer's specified unload order.

departure planning mandatory

A flag that indicates whether a scheduled shipment line must be departure planned before it can be pick released. The value of this flag is set for the customer/item. Also known as planning mandatory.

departure planning pool

All of the scheduled shipment lines available to be departure planned. These include scheduled shipment lines that have not been shipped and are not currently part of a planned departure. Also known as planning pool.

Departure Planning Workbench (DPW)

Related windows that manage departures and deliveries. These integrated windows are presented to the user as a workbench.

dependencies

Dependencies, as used here, means that cached values in the database, identified by table and column, are related to one or more other values, also identified by table and column. The dependency of the latter values to the former causes the latter values to be set to Missing if the former value is changed. Cascading Dependencies result when there are values dependent on one or more of the values changed to Missing, and they in turn are also made to be Missing.

dependent demand

Demand for an item that is directly related to or derived from the demand for other items. See independent demand .

deposit

A monetary amount charged to a customer, but returnable to a customer at a later date. For example security deposit on a container, or a deposit awaiting contract signature.

descriptive flexfield

A feature used to collect information unique to your business. You determine the additional information you need and descriptive flexfield lets you customize your application to your needs without additional programming.

destination base unit

The unit of measure to which you are converting when you define interclass conversions. Your destination base unit is the base unit of a unit class.

destination city

The city or unincorporated community name is important as freight charges are based on the actual destination of the shipment.

destination county

Some states have more than one city, town, or community with the same name. It is necessary to pinpoint the actual destination in these cases by indicating the county in which the destination is located.

destination forecast

The forecast you load into when copying a forecast into another forecast.

destination organization

An inventory organization that receives item shipments from a given organization.

destination street

The destination street name and number are very important. The consignee is extremely difficult to locate without the exact and proper street address to which the shipment is to be delivered. Therefore to avoid additional delivery charges and possible delays, it is imperative that this information be furnished.

destination zip

The zip is required to determine the exact location of the shipping point. Zip codes are the basis for many carriers freight charges. Presented to the user as a workbench.

detail container

Inner container that is enclosed within the master container. See master container.

detailed message action

A message representing one exception. Oracle Alert inserts the exception values into the text of the message.

detailed scheduling

A method of scheduling production that considers minute to minute resource availability information as well as exact resource requirements from routings.

dimension sourcing

Provides the rules for finding attribute values that have been defined in qualifier and pricing dimensions. For a given transaction, the Pricing Engine must receive all the values of the attributes defined in the qualifier and pricing dimensions (contexts) in order to determine which prices and/or benefits the transaction is qualified for. See context.

direct receipt

The receipt of an item directly to its final destination (either directly to the person who requested the item or directly to the final inventory location). It differs from a standard receipt in that it is received into a receiving location and delivered in one transaction, rather than received and delivered in two separate transactions.

disable date

A date when an Oracle Manufacturing function is no longer available for use. For example, this could be the date on which a bill of material component or routing operation is no longer active, or the date a forecast or master schedule is no longer valid.

discount amount

This is the difference between the list price and the selling price for the item. If the discount was specified as an "amount" discount, then this value will not change even if the price list changes. For example, if Item A's list price is $10, and we have a 20% discount, then the discount amount is $2. If we then change price lists, and Item A will cost $20 on the new price list, the discount amount for that same 20% discount now becomes $4. If however, the discount was not a percentage and was an "amount" discount of $2, then whether the list price for the associated price list is $10, $20, or $5, the discount amount will always be $2.

discount percent

This is the selling price/list price (multiplied by 100 to make it a percentage). If the discount was specified as a "percent" discount, then this value will not change even if the price list changes. For example, if Item A's list price is $10, and we have a 20% discount, then the discount amount is $2. If we then change price lists, and Item A will cost $20 on the new price list, the discount amount for that same 20% discount now becomes $4, but the percentage is still 20%. If however, the discount was not a percentage and was an "amount" discount of $2, then whether the list price for the associated price list is $10, $20, or $5, the discount amount will always be $2. In that case, the percentage would be different for every price list.

discounts

Is a Modifier type in Oracle Pricing that creates Pricing Adjustments which allows Pricing Engine to extend a reduced price for an order, specific line item, or group of lines.

discrete job

A production order for the manufacture of a specific (discrete) quantity of an assembly, using specific materials and resources, in a limited 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.

iscrete job

Discrete jobs are used to manufacture assemblies using specific materials and resources within a start and end date. (Also known as work order or assembly order).

discrete manufacturing

A manufacturing environment where you build assemblies in discrete jobs or batches. Different from a repetitive production environment where you build assemblies on production or assembly lines at a daily rate.

dispatch report

A report that prioritizes planned production work based on operation schedule dates and times.

disposition

Directions that describe how to dispose of inventory affected by an ECO. Engineering uses ECO disposition for informational purposes only.

distribution account

An account where you record material, material overhead, resource, outside processing, and overhead charges incurred by a discrete job or repetitive assembly. In a standard costing system, this is where you record your standard costs.

distribution list

A predefined list of electronic mail IDs that you can use rather than entering individual mail IDs (To, Cc, and Bcc) when defining mail message alert actions in Oracle Quality.

distribution resource planning (DRP)

Application of replenishment inventory calculations to assist in planning of key resources contained in a distribution system, such as sourcing and transport. DRP is an extension of distribution requirements planning, which applies MRP logic to inventory replenishment at branch warehouses.

dock date

The date you expect to receive a purchase order.

document

Any document that furnishes information to support a business object or an action on the business object. Examples include: a purchase order document, an invoice document, a word processing file listing receiving instructions, CAD files citing an item's specifications, or video instructions of an assembly operation.

document category

Document category is a document attribute that is used to control where a document can be viewed or maintained. Oracle Applications will seed some document categories to correspond with previous functionality. You can maintain document categories and the functions which can use them as necessary

document reference

A message that precisely identifies the document or part of document you want to describe using standard or one time notes.

document sets

A grouping of shipping documents you can run from the Confirm Shipments window.

Down time

Time when a resource is scheduled for operation but is not producing for reasons such as maintenance, repair, or setup.

drop shipment

A method of fulfilling sales orders by selling products without handling, stocking, or delivering them. The selling company buys a product from a supplier and has the supplier ship the product directly to customers.

dropship item

An item which is going to be sourced externally from the vendor directly to our customer.

DRP

See distribution resource planning.

DSNO

Transaction code assigned to outbound electronic Departure Based Ship Notice/Manifest transaction in the Oracle e Commerce Gateway, based on information processed through the Oracle Departure Planning application.

Dual Card Kanban

A demand pull signal that uses a "move" and "produce" communication method. Generally, "move" cards are collected and when the "produce" lot size is reached, the "produce" card is used to create the replenishment. This procedure is generally used when a minimum order quantity is required as a result of long set up times or economic order cost.

due date

The date when scheduled receipts are currently expected to be received into inventory and become available for use.

dunning letters

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

duplicate

An exception Oracle Alert located for the same action set during a previous alert check. Oracle Alert does not consider a detail action to contain a duplicate exception until Oracle Alert sends the final action level to a specific action set, and then locates the same exception for the same action set again. For example, if on Monday Oracle Alert notifies a buyer that a supplier shipment is overdue, then on Tuesday Oracle Alert finds the shipment is still overdue, you can choose whether Oracle Alert should re notify the buyer or suppress the message.

dynamic distribution

You can use output variables to represent electronic mail IDs. When you define mail message alert actions in Oracle Quality, the message is sent to all defined mail IDs.

dynamic insertion

Automatically creates new accounting flexfield combinations as you enter them. If you do not use dynamic insertion, you create new accounting flexfield combinations with a separate window.

dynamic lead time offsetting

A scheduling method that quickly estimates the start date of an order, operation, or resource. Dynamic lead time offsetting schedules using the organization workday calendar.

dynamically defined serial number

Creating and assigning serial numbers as you need them, instead of creating serial numbers before their assignment.

EDI

See Electronic Data Interchange (EDI).

EDIFACT

Electronic Data Interchange for Administration, Commerce, and Trade is the current acronym for standards developed within Working Party 4. See WP4.

effective date

Date when an Oracle Manufacturing function is available for use. For example, this could be the date a bill of material component or routing operation becomes effective, or the date you anticipate revised item changes become part of a bill of material and can no longer be controlled by an ECO.

effectivity

Effectivity is used to control the addition or removal of a component or an operation from a bill of material or an assembly process. Effectivity control may be managed by model/unit number (also known as serial number effectivity) or by date.

effective dates

Start date and end date that a price, discount, surcharge, deal, promotion, or change is active.

efficiency

A productivity measure that focuses on actual performance against a standard. Expressed in a percentage figure, it is calculated by dividing actual resource time charged to a task by the standard resource requirements for the same task.

efficiency variance

A quantity variance defined as the difference between the amount of a resource (typically in hours) required at standard and the actual amount used to manufacture an assembly.

elapsed time

The clock time between start and completion. For example, if the build time of a resource is 10 hours, but you only schedule 5 hours of work a day, the elapsed time is 29 hours.

electronic commerce

Conducting business via an electronic medium. This includes methods of exchanging business information electronically, such as Electronic Data Interchange (EDI), FAX, email, and eforms.

Electronic Data Interchange (EDI)

Exchanging business documents electronically between trading partners. EDI subscribes to standard formats for conducting these electronic transactions as stated by various standards.

electronic funds transfer

A method of payment in which your bank transfers funds electronically from your bank account into another bank account. In Oracle Payables, funds are transferred from your account into that of a supplier. This information is sent to the bank in a file.

elemental variance

A work in process variance between the standard of an assembly and the actual charges to a standard job or repetitive schedule distributed by cost element.

employee supervisor hierarchy

An approval routing structure based on employee/supervisor relationships. See position hierarchy.

encumbrance

See purchase order encumbrance.

encumbrance type

An encumbrance category that allows you to track your expenditures according to your purchase approval process and better control your planned expenditures. You can set up separate encumbrance types for each stage in your purchasing cycle to track your spending at each level. Examples of encumbrance types are commitments (requisition encumbrances) and obligations (purchase order encumbrances).

end assembly pegging

A Pegging item attribute option the planning process uses to decide when to calculate and print end assemblies for the item on the Planning Detail Report. Even if you do not select this option, you can still calculate and view end assemblies for the item online.

end date

Signifies the last date a particular quantity should be forecast on a forecast entry. From the forecast date until the end date, the same quantity is forecast for each day, week or period that falls between that time frame. An entry without an end date is scheduled for the forecast date only.

end item

Any item that can be ordered or sold. See finished good and product.

end item unit number

End Item Unit Number, sometimes abbreviated as Unit Number, uniquely identifies which bill of material to be used for building a specific Model/Unit Number Effectivity controlled item.

engineer to order

An environment where customers order unique configurations for which engineering must define and release custom bills for material and routings. Oracle Manufacturing 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.

engineering change order department

A group of users that use the engineering change order system. You assign users to an ECO department to control access to your ECOs.

engineering change order reason

The purpose of an ECO.

engineering change order status

A classification you can use to track and control an ECO's life cycle. ECO statuses include: Open, Hold, Release, Schedule, Implement, and Cancelled.

engineering change order type

An ECO field that identifies the originating ECO department and the items you can include on an ECO (manufacturing or engineering).

engineering item

A prototype part, material, subassembly, assembly, or product you have not yet released to production. You can order, stock, and build engineering items.

entity

A data object that holds information for an application.

Evaluated Receipts Settlement (ERS)

A Payment on Receipt system, a process whereby Trading Partners generate payment obligation transactions in their accounts payable system upon receipt of a shipment of goods, eliminating the need for invoices or invoice transactions. This system combines information from the electronic Advance Shipment Notice (ASN), the receipt, and the purchase order. It ensures accurate and timely data processing. Also known as Self Billing.

event alert

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

events

An event is an identifiable point in time among a set of related activities. Graphically, an event can be represented by two approaches: (1) in activity on node networks, it is represented by a node; (2) in activity on arc networks, the event is represented by the arc. In flow manufacturing, events are the lowest level of activities in a flow routing. Resources are assigned to events. Events can be grouped into processes and operations.

exception

An occurrence of the specified condition found during an alert check. For example, an alert testing for invoices on hold may find five invoices on hold, or none. Each invoice on hold is an exception.

exception message

A message received indicating a situation that meets your predefined exception set for an item, such as Items that are overcommitted, Items with excess inventory, and Orders to be rescheduled out.

exception reporting

An integrated system of alerts and action sets that focuses attention on time sensitive or critical information, shortens your reaction time, and provides faster exception distribution. Exception reporting communicates information by either electronic mail messages or paper reports.

exchange rate

A rate that represents the amount of one currency you can exchange for another at some point in time. Oracle Applications use the daily, periodic, and historical exchange rates you maintain to perform foreign currency conversion, re evaluation, and translation. You can enter and maintain daily exchange rates for Oracle Automotive to use to perform foreign currency conversion. Oracle Automotive multiplies the exchange rate times the foreign currency to calculate functional currency.

exchange rate type

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

Exchange Rate Variance (ERV)

The difference between the exchange rate for a foreign currency invoice and its matched purchase order.

exclusivity

A feature in Oracle Pricing that determines if an order qualifies for multiple modifiers on an order , and if one of the modifiers is exclusive, then only the exclusive modifier is applied.

expected receipts report

A printed report of all expected receipts for a time period and location you specify.

expenditure

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

expenditure category

An implementation defined grouping of expenditure types by type of cost.

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 types include: IPV, ERV, Tax, Freight, and Miscellaneous.

expenditure type class

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

expense item

Anything you make, purchase, or sell including components, subassemblies, finished products, or supplies and that does not carry a cost. Also known as a non asset item.

expense subinventory

Subdivision of an organization, representing either a physical area or a logical grouping of items, such as a storeroom where no value exists but the quantities may be tracked.

explode

An AutoCreate option that lets a buyer split a single requisition line for an item into one or more requisition lines for different items. Use this option to expand a requisition line for an item that your company purchases in component parts.

exploder

The first of the three processes that comprise the planning process under the standard planning engine. The exploder explodes through all bills of material and calculates a low level code for each item. The low level codes are used by the planner to ensure that net requirements for a component are not calculated until all gross requirements from parent items have first been calculated. The exploder runs before the snapshot and planner. Under the memory based planning engine, the memory based snapshot performs exploder functions.

export paper

A document required by governmental agencies that provides information on goods shipped out of or into a country.

export licenses

A government license to supply certain products to certain countries that would otherwise be restricted.

express delivery

An option that lets you deliver the entire quantity of a receipt without entering quantities for each shipment or distribution.

express receipt

A site option that lets you receive an entire purchase order or blanket purchase agreement release with one keystroke.

express requisitions

To create requisitions quickly from predefined requisition templates. You only need to provide an accounting flexfield and quantities to create a requisition for commonly purchased items.

extended line amount

Oracle Order Management prints the extended order line amount for each order line.

extended price

The extended price is the cost of the line. This is computed by multiplying the selling price per unit by the number of units ordered on that line. Thus, if two of item A cost $10.00 each, the extended price is $20.00 for the line.

extensible order contacts model

How will we specify contacts for the order for any purpose relevant to your business.

external forecast

This is the forecast that is created based on the customers transmitted "forecasted" demand for a specific time horizon. The transmission of this forecast is predominantly via EDI. In Release Management any forecast information that is interfaced to MRP by the Demand Processor is considered external forecast.

external system

Any application outside of the Oracle environment.

factor list

In Oracle Pricing Formulas, factor lists may be linked to multiple pricing attributes or range of these attributes. For example, a glass with thickness between 0.1 to 0.3 mm will have a factor of 3 and a glass with thickness between 0.4 to 0.8 mm will have a factor of 5. The choice of factors from the factor list is made by the Pricing engine at the time the formula is computed. See formula.

FAS

Final Assembly Schedule. A discrete job created from a custom configuration or a standard configure to order item and linked to a sales order.

FBO

Feature Based Ordering (FBO), also known as Feature Based Releasing (FBR) and Attribute Based Releasing (ABR), is a business process of ordering and releasing product by specifying a feature or group of features rather than the traditional upper level identifier or item number.

FBR

Feature Based Releasing. This is an alternate acronym for FBO or ABR, used by Ford and others.

Feeder Line

A production line designed to feed sub assemblies to a line producing higher level assemblies.

Feeder Line Synchronization

A concurrent process that allows you to synchronize sub assembly flow schedules sequence with the parent assembly line flow schedule sequence.

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.

FIFO costing

Costing method where it is assumed that items that were received earliest are transacted first.

final assembly order

A discrete job created from a configuration or an assemble to order item and linked to a sales order. Also known as final assembly schedule.

final close

A purchase order control you can assign to prevent modifications to or actions against completed documents, lines, and shipments by final closing them. Final closed documents are not accessible in the corresponding entry windows, and you cannot perform the following actions against final closed entities: receive, transfer, inspect, deliver, correct receipt quantities, invoice, return to supplier, or return to receiving.

financial EDI

The exchange of machine readable financial documents between a corporation and its financial institution. The exchange includes both collections and disbursements in the form of credit and debit transfers, related bank balance, banking transactions, and account analysis.

finished good

Any item subject to a customer order or forecast. see product.

firm

A purchase order control. When you firm an order, Master Scheduling/MRP uses the firm date to create a time fence within which it does not suggest new planned purchase orders, cancellations, or reschedule in actions. It continues to suggest reschedule out actions for orders within the time fence. If several shipments with different promised or need by dates reference the same item, Master Scheduling/MRP sets the time fence at the latest of all scheduled dates.

firm demand

Inbound demand that Oracle Release Management passes as Authorized To Ship (ATS) to a sales order in Oracle Order Management.

firm fence

An optional Release Management setup feature which defines a range of days either from the beginning of the demand schedule horizon or following the optional frozen fence. The firm fence instructs the Demand Processor to override the demand status on the schedule with a Firm status when updating the sales order lines.

firm flag

Denotes a job that cannot be modified by the planning or rescheduling process. See Oracle Master Planning/MRP User's Guide or Oracle Supply Chain Planning User's Guide.

firm planned order

An MRP planned order that is firmed using the Planner Workbench. This allows the planner to firm portions of the material plan without creating discrete jobs or purchase requisitions. Unlike a firm order, a MRP firm planned order does not create a natural time fence for an item.

firm scheduled receipt

A replenishment order that is not modified by any planning process. It may be a purchase order, discrete job, or repetitive schedule. An order is firm planned so that the planner can control the material requirements plan.

first unit completion date

The date and time you plan to complete production of the first assembly on a repetitive schedule. This date equals the first unit start date plus the lead time.

first unit start date

The date and time you plan to begin production of the first assembly on a repetitive schedule. This date equates to the start of your lead time.

Fixed Days Supply

An item attribute the planning process uses to modify the size and timing of planned order quantities for the item. The planning process suggests planned order quantities that cover net requirements for the period defined by the value you enter here. The planning process suggests one planned order for each period. Use this attribute, for example, to reduce the number of planned orders the planning process would otherwise generate for a discretely planned component of a repetitively planned item.

fixed lead time

The portion of the time required to make an assembly independent of order quantity, such as time for setup or teardown.

Fixed Lot Size Multiplier

An item attribute the planning process uses to modify the size of planned order quantities or repetitive daily rates for the item. For discretely planned items, when net requirements fall short of the fixed lot size multiplier quantity, the planning process suggests a single order for the fixed lot size multiplier quantity. When net requirements for the item exceed the fixed lot size multiplier quantity, the planning process suggests a single order with an order quantity that is a multiple of the fixed lot size multiplier quantity. For repetitively planned items, when average daily demand for a repetitive planning period falls short of the fixed lot size multiplier quantity, the planning process suggests a repetitive daily rate equal to the fixed lot size multiplier quantity. When average daily demand for a repetitive planning period exceeds the fixed lot size multiplier quantity, the planning process suggests a repetitive daily rate that is a multiple of the fixed lot size multiplier quantity.

fixed order quantity

An item attribute the planning process uses to modify the size of planned order quantities or repetitive daily rates for the item. When net requirements fall short of the fixed order quantity, the planning process suggests the fixed order quantity. When net requirements for the item exceed the fixed order quantity, the planning process suggests multiple orders for the fixed order quantity. For discretely planned items, use this attribute to define a fixed production or purchasing quantity for the item. For repetitively planned items, use this attribute to define a fixed production rate for the item. For example, if your suppliers can only supply the item in full truckload quantities, enter the full truckload quantity as the fixed order quantity for the item.

fixed price discount

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

flexfield

A field made up of segments. Each segment has a name you assign and a set of valid values. see descriptive flexfield and key flexfield.

flexfield segment

One of the parts of your key flexfield, separated from the other parts by a symbol you choose (such as -, /, or \). Each segment typically represents a cost center, company, item family, or color code.

flexible tolerance fences

Shown as the percent increase or decrease over daily production rate available from a given supplier for a set amount of time.

flow charging

A repetitive transaction method where you charge material, move, resource, and overhead transactions to a specific assembly on a line rather than a specific repetitive schedule. See repetitive allocation.

flow line

The physical location where you manufacture a flow assembly, usually associated with a routing(s). You can build many different assemblies on the same line at the same time. Also known as assembly line or flow shop.

flow manufacturing

Manufacturing philosophy utilizing production lines and schedules instead of work orders to drive production. Mixed models are grouped into families and produced on lines balanced to the takt time.

flow routing

A sequence of manufacturing events that you perform to manufacture an assembly. In the flow routing, these events can be grouped in processes and balanced operations. A routing consists of an item, a series of events, processes and/or operations, a operation sequences, operation effective dates, and a flow routing network. You can also perform operation time, yield and total product cycle time calculations in the flow routing.

Flow Routings and Sequence of Events

Flow Routings define the production process of an assembly on the production line. You can use Flow Routings to define the processes and the sequence of events within each process. You can specify the setup, run, and move times for each event by associating the required resources.

flow routing network

A process map of your processes and operations where you specify the primary path, alternate paths, feeder lines and rework loops within your flow line.

flow schedule

A schedule for your flow line that represents the volume and mix of products to be produced. Scheduling can be done based on customer orders and scheduling rules, with an objective of matching the customer orders as closely as possible while establishing an achievable pace and consistent flow of products through the flow line. Schedules DO NOT produce work orders.

flow workstation

The assigned location on a flow line where a worker performs the job. It could be a machine or a workbench.

FOB

See freight on board.

focus forecasting

A simulation based forecasting process that looks at past inventory activity patterns to determine the best simulation for predicting future demand.

folder

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

forecast

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

historical sales

Used by a customer to communicate to supplier the actual sales for a given item, location, and period combination. The date that used by the customer is the Actual Date, as an indication of when the sale actual took place.

forecast all

For a Planning Schedule. This indicates that schedule forecast requirements include Unimplemented Planned Orders, Approved Requisitions, and Approved Supply Agreement Releases.

forecast consumption

The process of subtracting demand generated by sales orders from forecasted demand thereby preventing demand being counted twice in the planning period.

Forecast Control

An item attribute used to determine the types of demand you place for the item. Master Scheduling/MRP uses the option you choose here to guide the behavior of the key processes involved in two level master scheduling: forecast explosion, forecast consumption, planning, production relief, and shipment relief. This attribute is only appropriate for items that are models, option classes, options, or mandatory components of models and option classes. A value of Consume means you forecast demand for the item directly, rather than exploding forecast demand to the item using the forecast explosion process. A value of Consume and derive means you forecast demand for the item directly, or you explode forecast demand to the item using the forecast explosion process, or you use a combination of both methods to forecast demand for the item. A value of None means you place sales order demand but do not forecast demand for the item.

forecast date

The date for a forecast entry for an item. A forecast for an item has a forecast date and an associated quantity.

forecast demand

A part of your total demand that comes from forecasts, not actual sales orders.

forecast end date

A forecast end date implies that until that date, the same quantity is scheduled for each day, week, or period that falls between the forecast date and the end date. A forecast date with no forecast end date is the quantity for that particular day, week, or period, depending on the bucket size.

forecast end item

The parent item for components that receive exploded forecasts during forecast explosion. Used to identify the highest level planning or model item from which forecasts for a component can be exploded.

forecast entry

A forecast for an inventory item stated by a date, an optional rate end date, and quantity.

forecast explosion

Explosion of the forecast for planning and model bills of material. The forecasted demand for the planning or model bill is passed down to create forecasted demand for its components. You can choose to explode the forecast when loading a forecast.

forecast fence (OM)

An optional Release Management setup feature which defines a range of days from the beginning of the demand schedule horizon or following the optional Frozen and firm fences. The Forecast Fence instructs the Demand Processor to override the demand status on the schedule with a Forecast status when updating the sales order lines.

forecast fence (MRP)

An optional Release Management setup feature which defines a range of days from the beginning of the demand schedule horizon or following the optional Frozen, Firm, and OM Forecast Fences. The MRP Forecast Fence instructs the Demand Processor to override the demand status on the schedule with a Forecast status and update MRP Planning rather than the sales order. When the demand is scheduled to be shipped later than the ending day of MRP Forecast Fence, the demand is not updated to MRP Planning.

forecast level

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

forecast load

The process of copying one or more source forecasts into a single destination forecast. When copying forecasts, you can choose to overwrite all or a subset of existing entries in the destination forecast, specify whether to explode the source forecast, and specify whether to consume the source forecast. You can choose to modify the source forecast by a modification percent, or roll the source forecast forward or backward by a specified number of carry forward days. You can also load compiled statistical and focus forecasts from Inventory, and you can use the forecast interface table to load forecasts into Master Scheduling/MRP from external sources.

forecast only

For a Planning Schedule, indicates that the schedule forecast requirements include Unimplemented Planned Orders and Approved Requisitions.

forecast set

A group of complementing forecasts. For each forecast set, you specify a forecast level, consumption use, update time fence days, outlier update percents, disable date, default time bucket and demand class. A forecast set can have one or many forecasts within it.

foreign currency

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

FORMs

References to Application forms which can be used to either view additional information about the work item, or perform the activity requested by the notification. The Notification Viewer will allow the responder to launch these forms.

formula

A mathematical formula used in Oracle Pricing to define item pricing or modifier adjustments. You create a pricing formula by combining pricing components and assigning a value to the components.

forward

An action you take to send a document to another employee without attempting to approve it yourself.

forward consumption days

A number of days forward from the current date used for consuming and loading forecasts. Consumption of a forecast occurs in the current bucket and as far forward as the forward consumption days. If the forward consumption days enters another bucket, the forecast consumes anywhere in that bucket, as well.

forward scheduling

A scheduling technique where you specify a production start date and Oracle Manufacturing calculates a production end date using either detailed scheduling or repetitive line scheduling.

four way matching

Purchasing performs four way matching to verify that purchase order, receipt, inspection and invoice quantities match within tolerance.

freeze

You can freeze a purchase order after printing. By freezing a purchase order, you prevent anyone from adding new lines or changing the purchase order. You can continue to receive goods and be billed on already existing purchase order lines. The ability to continue receiving against the purchase order is the difference between freezing and cancelling.

Freight and Special Charges

Freight and special charges can be entered with the original order. The functionality of Freight and Special Charges for Order Management is not yet finalized. The layout of this report should eventually include display of the Freight and Special Charges.

freight on board (FOB)

The point or location where the ownership title of goods is transferred from the seller to the buyer.

freight carrier

A commercial company used to send item shipments from one address to another.

freight charges

A shipment related charge added during ship confirmation and billed to your customer.

freight terms

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

from city

The city or unincorporated community name is important as freight charges are based on the actual origin of the shipment.

from street

A street name and number are necessary as some companies have more than on shipping location in the same city, town or community. The actual pick up point is essential for tracing purposes.

from zip

The zip is required to determine the exact location of the shipping point. Zip codes are the basis for many carriers freight charges.

frozen

Term to describe the independence of the Archive data from the standing data.

frozen costs

Costs currently in use for an operation, process, or item including resources, material and overhead charges. Under standard costing, you use the frozen costs for your cost transactions.

frozen fence

An optional Release Management setup feature which defines a range of days from the beginning of the demand schedule horizon. The frozen fence instructs the Demand Processor to leave existing sales order demand intact if the schedule indicates changes to demand within this time.

fulfilled quantity

In the Order Management schema, the accepted quantity was the number of items received from the customer on a given line that are approved to issue credit for. In Order Management, the accepted quantity is referred to as the fulfilled quantity.

fulfillment

Fulfilled sales order lines have successfully completed all Workflow processing activities up to the point of becoming eligible for invoicing.

fulfillment method

Fulfillment method is an activity which will be considered as a prerequisite before a line or a group of lines can be fulfilled. The fulfillment method must be associated with one and only one work flow activity. In this document fulfillment method and fulfillment activity have been used in the same context. If no fulfillment activity has been set in a flow for a line which is not part of any fulfillment set or PTO/KIT, the line will not wait at the fulfillment.

fulfillment set

Items in a fulfillment set will be available for scheduling and shipping only when all the items are available and ready to be scheduled/shipped. Fulfillment sets can be complete only, or partially allowed but in proportions. ATO model, and a PTO Ship model Complete will be in a fulfillment set.

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

function activity

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

functional acknowledgment

The acknowledgment to indicate the results of the syntactical analysis of electronically encoded documents. Applies to a functional group and can include detail.

functional currency

Currency you use to record transactions and maintain your accounting information. The functional currency is generally the currency used to perform most of your company's business transactions. You determine the functional currency for the set of books you use in your organization. Also called base currency.

funds available

The difference between your budget, less encumbrances of all types and actual expenditures.

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, the transaction amount is compared with your funds available, and you are notified whether funds are available for your transaction. Checking funds does not reserve funds for your transaction.

funds reservation

The creation of requisition, purchase order, or invoice encumbrance journal entries. Purchasing immediately updates your funds available balances and creates an encumbrance journal entry in which you can post in your general ledger. This is also the process of reserving funds available. You can reserve funds when you enter actual, budget, or encumbrance journals. When you reserve funds, the amount of your transaction is compared with your funds available and you are notified online whether funds are available.

general ledger transfer

The process of creating a postable batch for the general ledger from summarized inventory/work in process activity for a given period. Using Journal Import in General Ledger, you can create a postable batch in your general ledger. After running Journal Import, you can post your journal using the General Ledger posting process.

General Services Administration

See GSA.

generic agreement

An agreement without a specified customer, so it is available to all customers. see agreement, customer family agreement.

goods

The value before tax is calculated. The value on which tax is calculated.

goods or services.

This document also lists any tax, freight charges, and payment term.

GRN (Goods Received Note)

Goods Received Note. Synonym for receipt or material receipt.

gross requirements

The total of independent and dependent demand for an item before the netting of on hand inventory and scheduled receipts.

gross weight

The weight of the fully loaded vehicle, container, or item, including packed items and packaging material.

Group API

An API intended for use by other Oracle Application modules that have been authorized by the owning module. This form of API is less strict in its controls as compared to the Public API.

group number

The group no. for conditions that should together evaluate to TRUE (AND conditions).

GSA (General Services Administration)

GSA (General Services Administration): a customer classification that indicates the customer is a U.S. government customer. For products on the GSA price list, a fixed price must be used, defined on the GSA contract. The items contained on the GSA price list cannot be sold to commercial customers for the same or less price than the government price. In other terms, the price offered to the government must be the minimum in the market.

GSA Discounts

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

guarantee

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

hard reservation

Sales order demand that you firm by reserving selected inventory for the purposes of material planning, available to promise calculations, and customer service issues.

hazard class

A category of hazardous materials. Most hazardous materials belong to only one hazard class. Some materials belong to more than one hazard class and some materials do not belong to any. If a material belongs to more than one hazard class, you should list these classes in a specific order.

hidden collection plan

A collection plan that consists entirely of context elements. Data collection for these collection plans occurs in the background and requires no user intervention.

hierarchical levels

The nesting of information within an electronic Ship Notice/Manifest. Each hierarchical level is identified with its own unique sequence number and, if nested, the sequence number of its parent hierarchical level.

hierarchical structure

Defines the actual layout of different hierarchical levels indicating the nesting of information in an electronic Ship Notice/Manifest transaction.

hit/miss tolerance

A limit you define for the difference between the on hand quantity and the actual cycle count quantity. You express positive and negative hit/miss tolerances as percentages of the on hand quantity.

hold

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

hold criteria

A criterion used to place a hold on an order or order line. A hold criteria can include customers, customer sites, orders, and items.

hold source

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

hold type

Indicates the kind of hold you place on an order or order line.

immediate dispatch

Used in conjunction with department or resource job filter criteria. Includes jobs where there is quantity in an operation assigned to the selected department or resource.

implement

To make an ECO active so that no further changes can be made to that ECO. Usually, the day you implement an ECO is also the effective date for component changes. After that date, you must make further changes through a new ECO or directly to the bill.

implementation date

The date a component becomes part of a bill of material and is no longer controlled through an ECO. Implementation date does not necessarily equal the effective date.

Inbound/Outbound Lines

In the Order Management schema, lines on a header are either ALL outbound; meaning sales order lines, in which material on the header is leaving the warehouse to go to a customer, or they are ALL inbound; meaning return lines, in which material on the header is arriving at the warehouse to be credited back to the customer. In Order Management, headers can be 'RETURN' (all inbound), 'ORDER' (all outbound), or 'MIXED' (both inbound and outbound lines).

Inbound Purchase Order

Inbound Purchase Order refers to the action of receiving purchasing information from customers and creating valid sales orders within Oracle Order Management.

incident

An entry logged in Oracle Service to record a customer's request for product service. You can log a different incident for each issue a customer reports including questions about products, problems using the products, requests for preventive maintenance, and requests for service contract renewals.

included item

A standard mandatory component in a bill, indicating that it ships (if shippable) whenever its parent item is shipped. Included items are components of models, kits, and option classes.

Incompatibility

A feature in Oracle Pricing that allows you to define groups of modifiers where the modifiers in a group are incompatible with each other. Modifiers in the same incompatibility group may not be used together on the same transaction. See Precedence.

Industry Attributes

Elements specific to an individual industry. An example of an industry attribute for the automotive industry would be the model year.

independent demand

Demand for an item unrelated to the demand for other items.

initialization

Defines cycle count classes and items, based on an already existing ABC compile.

INO

Transaction code assigned to outbound electronic Invoice transaction in the Oracle e Commerce Gateway, based on information processed through the Oracle AutoInvoice application.

inspection

A procedure you perform to ensure that items received conform to your quality standards. You can use inspections to prevent payment for goods and services that fail to meet your quality standards.

Installation or Installation

Detail Information about where your customers install product.

Installed Base

A collective noun to describe the sum total of all products that a company has responsibility to provide service for at customer sites.

intangible item

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

inter organization transfer

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

interclass conversion

The conversion formula you define between base units from the different unit classes.

intercompany invoice

An automatically generated statement that eliminates intercompany profit. This transaction may occur between organizations in the same or different legal entities.

intermediate ship to

The delivery point for a shipment prior to an ultimate destination.

internal forecast

The forecast information created by the planners. It differs from the external forecast which is fed into MRP by transmissions from the customer.

internal item number

The internal representation of Item's Name within your organization.

internal order

A sales order in the Order Management system that is generated from an internal requisition in the Purchasing system and loaded into OM through Order Import.

internal requisition

A requisition in the Purchasing system that will directly result in the generation of a sales order in the Order Management system through the Order Import process in OM.

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.

intraoperation steps

The particular phases within an operation. There are five intraoperation steps in Work in Process: Queue, Run, To Move, Reject, and Scrap.

inventory allocation

The act of assigning on hand inventory to specific orders.

inventory controls

Parameter settings that control how Inventory functions.

inventory item

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

inventory organization

An organization that tracks inventory transactions and balances, and/or that manufactures or distributes products.

inventory parameters

The set of controls, default options, and default account numbers that determine how Inventory functions.

inventory transaction

A record of material movement. The basic information for a transaction includes the item number, the quantity moved, the transaction amount, the accounting flexfields, and the date. See material transaction.

invoice

A document you create in Oracle Receivables that lists amounts owed for the purchases of goods or services. This document may list any tax and freight charges. A summarized list of charges, including payment terms, invoice item information, and other information that is sent to a customer for payment.

invoice amount

Oracle Order Management prints the invoice amount for each order listed on this report.

invoice batch

A group of invoices you enter together to ensure accurate invoice entry. Invoices within the same batch share the same batch source and batch name. Receivables displays any differences between the control and actual counts and amounts. An invoice batch can contain invoices in different currencies. A Payables feature that allows you to enter multiple invoices together in a group. You enter the batch count, or number of invoices in the batch, and the total batch amount, which is the sum of the invoice amounts in the batch, for each batch of invoices you create. You can also optionally enter batch defaults for each invoice in a batch. When you enable you batch control system option, Multiple Organization in Oracle Applications automatically creates invoice batches for Payables expense reports, prepayments, and recurring invoices, and all standard invoices.

invoice charges

Includes Invoice Price Variance (IPV), Exchange Rate Variance (ERV), Freight, Tax, and Miscellaneous Charges. Since Release 11i the invoice charges are transferred from Oracle Payables to Oracle Projects for each project using the invoice charge transfer process.

invoice item

Oracle Order Management prints the name or/and description of the item on the invoice, depending on your selection for the Item Display parameter.

invoice price variance

The difference between the purchase order price for an item and the actual invoice price multiplied by the quantity invoiced. Payables records this variance after matching the invoice to the purchase order. Typically, the price variance is small since the price the supplier charges you for an item should be the one you negotiated on your purchase order. Upon invoice approval, Oracle Payable automatically records Invoice Price Variance to invoice price variance account.

invoice set

A invoice set is a group of order lines, linked by a common number, that you want the full quantity to invoice together. Thus, one invoice will contain amounts owed for the purchase of items put in one invoice set. ATO model, and a PTO Ship model Complete will be in a invoice set. Invoice sets can be complete only, or partially allowed but in proportion.

invoice to contact

How will we record or default the name of the person to whom the invoice will be sent. This is the person that the Accounts Receivable clerk will contact in the event of invoicing or collection queries.

invoice value

The total outstanding order value that needs to be invoiced.

invoicing rules

Rules that Oracle Receivables uses to determine when you bill your invoices. You can bill In Advance or In Arrears.

issue transaction

A material transaction to issue component items from inventory to work in process.

item

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

item (item type, key)

Item identifies a specific process, document, or transaction that is managed by the workflow system. A row in the Items table is simply a proxy for the actual application item that is being workflow managed, it does not redundantly store application data in workflow tables. A workflow item is identified by its item type (e.g. "ORDER") and a "key" which is generated by the application based on a unique key of the real item (e.g. key "1003").

item activity status

Item Activity Status stores the runtime status, completion results, etc. for each activity an item encounters as a process is run (e.g. item type: "ORDER" key: "1003", PA#103 ("LEGAL_REVIEW"), state: "COMPLETE", result: "REJECTED"). Other runtime attributes such as the begin/end time for each activity and the user and notification id for outstanding notifications is also stored here. This table only contains state for active items. State information for closed items is moved to a history table.

item attribute control level

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

item attribute value (item type, key, attribute name)

An Item Attribute Value is an instance of an Item Attribute that is associated with a particular workflow item. For example, the 'TOTAL' attribute associate with the 'ORDER' item type would have a value row in this table for the specific instance of item '1003'. Using the Workflow API, Item Attribute Values can be looked up and set by any activity in the process, as well as by the external workflow managed application. Item attribute values are used to substitute runtime values into Message tokens when notifications are sent from Workflow.

item attributes

Specific characteristics of an item, such as order cost, item status, revision control, COGS account, etc.

item based resource

A resource whose usage quantity is the amount required per assembly unit you make.

item category

See category.

Item/Entity Relationship

The collection of key attributes defined by the customer which cause Planning or Shipping Schedule details to be processed together as a group. If the customer manages CUMs, it is usually the collection of key attributes on which the cumulative quantity is based. An Item/Entity consists of a unique combination of: Customer Item Number, Address entities deemed relevant to the customer, Other customer specific identifiers which separate items on a schedule, such as Purchase Order, Record Keeping Year, or Item Revision.

item flexfield

A feature that lets you define the structure of your item identifier according to your business requirements. You can define up to twenty segments for your item.

item groups

A group of related products that can be added to one or more price lists.

item master level attribute

An item attribute you control at the item master level as opposed to controlling at the organization level.

item routing

A sequence of manufacturing operations that you perform to manufacture an assembly. A routing consists of an item, a series of operations, an operation sequence, and operation effective dates. Edits to an Item Routing do not automatically update a job routing.

master production schedule (MPS)

The anticipated build schedule in terms of rates or discrete quantities, and dates.

master schedule

The name referring to either a master production schedule or a master demand schedule. See master demand schedule and master production schedule.

master schedule load

The process of copying one or more source forecasts, master schedules, or sales orders into a single destination master schedule. When copying forecasts, you can choose to include all or a subset of sales orders, specify whether to consider demand time fence, and specify whether to consume the source forecast during the load. You can also specify update options to control consumption of the source forecast during the load. When copying master schedules, you can choose to modify the source master schedule by a specified number of carry forward days. When loading sales orders, you can choose to load all or a subset of sales orders, and you can specify whether to consider the demand time fence during the load. You can use the master schedule interface table to load master schedules from external sources.

matching attributes

Data elements used by Oracle Release Management's Demand Processor to compare new demand lines on inbound demand schedules to existing demand lines on Sales Orders for the purpose of demand reconciliation, to prevent unwarranted duplication of demand.

material constrained plan

In this plan, all material constraints that can be specified in the form of a supply schedule from manufacturing plants or by statements of vendor capacity from vendors are considered. When material availability is not a concern, resource availability constraints are used only to generate exceptions arising due to over utilization or under utilization of resources.

material and resource constrained plan

In this plan, you can generate a plan that respects material, resource, and transportation constraints. However, no plan objectives are considered.

multi source

An AutoCreate option that lets a buyer distribute the quantity of a single requisition line to several suppliers whenever the buyer wants to purchase the requisition line item from more than one supplier.

multiple installations

Refers to installing subledger products (AP, AR, PO, OE) multiple times. This is no longer necessary under a Multi Org implementation.

multiple sets of books

A General Ledger concept for having separate entities for which chart of accounts, calendar, or functional currency differs.

NAFTA

North American Free Trade Association.

name of carrier

It is important that the name of the carrier issuing the bill of lading be shown in this space to identify the second party to the bill of lading provisions. It also identifies the carrier who becomes responsible for the shipment and assumes responsibility.

National Automated Clearing House Association

The NACHA is a non profit organization responsible for developing and maintaining the rules and guidelines for using the ACH network.

NATS

Not Authorized To Ship. This term applies to sales order lines which are forecast status only, not eligible to enter any workflow processes which ultimately result in shipment of the product to the customer, such as production, departure planning, picking, and ship/confirm. This distinguishes them from sales order lines which are eligible for all shipment related processing (ATS).

Need by Date

The date in the purchase order system that indicates when the item needs to be received in order for it to be of value to the requestor.

need by date

The need by date for the end item is the demand date. The need by dates for the dependent demands are calculated based on the lead time offsets that are associated to the Items and routings used.

• If a constrained plan is run, the planning process will use the planned orders and actual routings for scheduling to derive the suggested due date.

• If an unconstrained plan is run, the suggested due date will simply be the same as the need by date.

Therefore, any differences between the lead time offsets (need by date) and actual manufacturing time (suggested due date) created by the planning process, will show up in the form of multiple exception messages.

negotiated capacity

Used by a supplier to communicate to a customer the capability to produce a quantity of a certain item at a given location and time period. This capacity may be negotiated as part of a contract and is for visibility purposes. The date that the supplier uses in the document is the Ship Date to convey when the goods can ship to the customer's receiving location.

negative requirement

A requirement supplied to a discrete job or repetitive schedule instead of being consumed by it. Negative requirements can be created to support by products or other reusable components.

nervousness

Characteristic exhibited by MRP systems where minor changes to plans at higher bill of material levels, for example at the master production schedule level, cause significant changes to plans at lower levels.

net change simulation

Process used to make changes to supply and demand and re plan them.

net planning percent

Percent of product that passes through a process or line operation. It equals the sum of the product of the network percentages at each operation along each path multiplied by 1 + the rework percent.

net requirements

Derived demand due to applying total supply (on hand inventory, scheduled receipts, and safety stock quantities) against total demand (gross requirements and reservations). Net requirements, lot sized and offset for lead time, become planned orders. Typically used for rework, prototype, and disassembly.

net weight

Weight of the contained load. Commonly calculated as GROSS TARE, this includes the weight of any packing materials (paper, cardboard separators, Styrofoam peanuts, etc.).

nettable control

An Oracle Manufacturing function that lets you specify whether the MRP planning process considers the requirements of the job or schedule in its netting calculations.

network routing

Network routings in Oracle Shop Floor Management comprise a collection of operations which include primary paths and alternate paths. You are able to define a separate routing for each item, at each sector. When you create routings in the Routings window, you define all possible paths.

new average cost

Cost of an item after a transaction that affects the average cost is processed. See current average cost.

new on hand quantity

The quantity on hand immediately after the transaction is performed and saved. Equal to current on hand quantity plus total quantity. See current on hand quantity, total quantity.

node

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

non live

Term to describe orders that are no longer subject to change.

non quota sales credit

See non revenue sales credit

non replenishable kanban

A non replenishable Kanban is used to replenish a Kanban location once. This card is used typically for custom products, one time customer orders or sudden spikes in demand.

non revenue sales credit

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

Non Revenue Sales Credits Sales

Credit assigned to salespeople that is not associated to invoice lines. This is sales credit given in excess of your revenue sales credit and is not usually applied to a salesperson's quota.

non standard asset job

A type of non standard job carried as an asset during the life of the job.

non standard discrete job

A type of discrete job that controls material and resources and collects costs for a wide variety of miscellaneous manufacturing activities. These activities can include rework, field service repair, upgrade, disassembly, maintenance, engineering prototypes, and other projects. Non standard jobs do not earn material overhead upon assembly completion.

non standard expense job

A type of non standard job expensed at the close of each accounting period. Typical expense jobs include maintenance and repair.

note name

A name that uniquely identifies a standard or one time note. You use note names to locate a note you want to use or copy on a document.

Not authorized to ship

Demand that is planned to be ready on the date scheduled but not sent to the customers until some authorizing event occurs like Receipt of funds where prepayment has been requested. Credit approval for credit held orders. Customer Demand signal for Just In Time deliveries.

Notification

Activities are completed by some external entity (e.g. human). These activities have a "notification function" which is run to signal the external entity of its need to perform a task. Human notifications are associated with a Message defined in the Notification system. All notification activities may have a "time out" limit within which the activity must be performed. Process Definitions are also modeled as activities, which can then be referenced by other processes. The network of activities and transitions that define the process are maintained by in the Process Activities and Activity Transitions tables.

Notification Attributes

(notification id, attribute name) For every notification, there will be a list of Notification Attributes, which hold the runtime value for each of the message attributes. These values are used to substitute subject and body tokens, and to hold user responses.

Notifications

(notification id) Notifications are instances of messages which were actually sent to some role. The row as status flags to record the state of the notification, as well as date fields for when the notification was sent, due, and responded to. A new row is created in the Notifications table each time a message is sent to a role. The row persists even after the notification has been responded too, until a purge operation moves to closed notifications to an archive.

NUMBER

attributes are used to communicate number values.

numeric number type

An option for numbering documents, employees, and suppliers where assigned numbers contain only numbers.

object

A region in Order Entry such as order, line, or shipment schedule. You can provide Security Rules for objects.See attribute, defaulting rules, processing constraints.

object / data object

An object, as used here, is a Web Applications Dictionary term which corresponds to a database view. In some part of this document, the term data object or WAD: Object is used instead, to avoid confusion with the object technology term "Object".

object attribute / data abject

Attribute An object attribute, as used here, is a Web Applications Dictionary term used to describe an attribute that is associated with a data object (view). In simpler terms, it corresponds to a column in a database View. In some part of this document, the term Data Object Attribute is used as a synonym to object attribute, in order to avoid confusion with the object technology term "Object Attribute".

occurrence

An individual quality result. For example, a measurement that falls in or out of a specified tolerance. Occurrences can be charted using Oracle Quality.

offset percent

An operation resource field that holds the percent of total manufacturing lead time required for previous operations. For example, if all operations require a total of ten hours to perform and the offset percent for a resource is 40%, then the resource is used four hours after the start of the first operation.

offsetting account

The source or opposite side of an accounting entry. For example, when you charge resources in Work in Process you debit a resource to your work in process resource valuation account; the offset account is the credit to the resource absorption account.

omit

An AutoCreate option that lets a buyer prevent Purchasing from including certain displayed requisition lines when creating a purchase order or RFQ. If you omit a requisition line, Purchasing returns it to the available pool of requisition lines.

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 you assign to your customer's account that are not related to a specific invoice. You can create on account credits in the Transaction window or through AutoInvoice.

on hand quantity

The physical quantity of an item existing in inventory.

on hold job/schedule

A job or repetitive schedule not accepting further activity and is therefore untransactable.

one time item

An item you want to order but do not want to maintain in the Items window. You define a one time item when you create a requisition or purchase order. You can report or query on a one time item by specifying the corresponding item class.

one time note

A unique message you can attack to an order, return, order line, or return line to convey important information.

open

An open purchase order exists if the purchase order has any lines that have not been fully invoiced and are not cancelled. If you require receipt for items you order, an open purchase order exists if any lines have not been fully received and fully invoiced and are not cancelled.

open interface

A Manufacturing function that lets you import or export data from other systems through an open interface. An example is a bar code reader device accumulating data you later import into your manufacturing system for further processing.

open requirement

A WIP material requirement you have not yet transacted to a discrete job or repetitive schedule. It equates to the component quantity required less any quantity issued.

operating script action

An operating system script invoked by action rule processing in Oracle Quality.

operating unit

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

operation

A step in a manufacturing process where you perform work on, add value to, and consume department resources for an assembly.

operation code

A label that identifies a standard operation.

operation completion pull transaction

A material transaction where you backflush components from inventory to work in process as you complete the operation where the component is consumed. See backflush transaction.

operation completion transaction

A move transaction from one operation to the next where you have completed building the assembly at that operation. In this process, you can also charge resources and overheads and backflush component items.

operation data store (ODS)

It represents all the tables that acts as destination for the collected data from each of the data sources (both Oracle Applications or legacy systems). This acts as the input for the snapshot portion of the planning process.

operation instructions

Directions that describe how to perform an operation.

operation offset

Elapsed days from the start of your first operation until the beginning of your current operation.

operation overlap scheduling

A scheduling technique that allows you to schedule resource activities in the prior and next operations to overlap with the current operation.

operation sequence

A number that orders operations in a routing relative to each other.

operation time

In discrete manufacturing, operation time is the total of setup and run time for a specific task. In flow manufacturing, operation times includes the machine time, labor time, and elapsed time for events, processes, and line operations on your flow routing.

operation yield

The percent of material that passes through an operation, process or event on a flow line without being scrapped.

operational cycle time

See take Tim.

Operational Method Sheet Support

Operational Method sheets (OMS) are documents that describe the operation to be performed for an assembly. The information in the OMS often includes graphical representation of the process, material needed, and detailed work instructions. You can use attachments in Oracle Flow Manufacturing to attach OMS's to Line Operations in the Flow Routing.

optimized plan

In this plan, you can generate an optimized and executable plan based on plan objectives as well as material, resource, and transportation constraints.

order forecast

Used by a customer to communicate to the supplier the anticipated future orders for a given item, period, and location from the supplier. The date that the customer uses in the document is the Receipt Date to convey when he expects to receive the goods. Alternately, the customer can provide a Ship Date that conveys when he wants the supplier to make the shipment. When only a Ship Date is provided, Oracle Collaborative Planning will derive a Receipt Date from the in transit lead time. In the absence of a lead time, the Receipt Date is the same as the ship Date.

overload capacity

Number of resource units that are required but already committed.

overrun percentage

An item attribute the planning process uses to decide when to suggest new daily rates for the item. The planning process only suggests a new daily rate for the item if the current daily rate exceeds the suggested daily rate by more than the acceptable overrun amount. This attribute lets you reduce nervousness and eliminate minor rate change recommendations when it is more economical to carry excess inventory for a short time than it is to administer the rate change. This attribute applies to repetitively planned items only. The related attribute for discretely planned items is Acceptable Early Days. See acceptable early days.

overwrite option

Option to overwrite existing orders on an MRP plan or an MPS plan during the planning process. Without overwriting, you can keep your existing smoothed entries as well as add new ones. By overwriting, you erase the existing entries and add new one according to the current demand. The overwrite option in used with the append option. See append option.

pack slip

An external shipping document that accompanies a shipment itemizing in detail the contents of that shipment. Package level tags can appear anywhere after a "CREATE OR REPLACE" statement and before any uncommented package contents, including variables, program units, etc. For example, --<TPA_LAYER=layer name>indicates that the package belongs to the specified Trading Partner Layer.

packing instructions

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

parameter

A variable used to restrict information in a report, or determine the form of a report. For example, you may want to limit your report to the current month, or display information by supplier number instead of supplier name.

parent transaction

A transaction entered in an Oracle Manufacturing product that invokes quality data collection.

Pareto's law

Vilfredo Pareto's theory that a small percentage of a group accounts for the largest fraction of the impact for the group. For example, 90% of your inventory value may be attributed to 5% of your inventory items.

passing result

A passing result signals successful completion of an order cycle approval action. Once an order or order line has achieved an approval action passing result, it no longer appears on the approval window. see approval action, order cycle.

past due order

An order that has not been completed on or before the date scheduled. It is also called delinquent order or late order.

past due requirements

Past due requirements include Release requirements that fall before the schedule horizon start date.

payback demand

Temporary material transfer when on project borrows demand from another project.

payback supply

Temporary material transfer when one project lends supply to another project.

payment batch

A group of invoices selected for automatic payment processing via Oracle Payables AutoSelect function.

payment document

Medium used to instruct a bank to disburse funds to the account of a site location or supplier.

payment terms

The due date and discount date for payment of an invoice. For example, the payment term '2% 10, Net 30' lets a customer take a two percent discount if payment is received within 10 days, with the balance due within 30 days of the invoice date.

pegging

The capability to identify for a given item the sources of its gross requirements and/or allocations. Pegging can be thought of as active where-used information.

pending

A status where a process or transaction is waiting to be completed.

pending costs

The future cost of an item, resource, activity, or overhead. Not used by cost transactions. See frozen costs.

percent of capacity

The required hours divided by the available hours for any given department, resource, and shift combination.

period

See accounting period

period expense

An expense you record in the period it occurs. An expense is typically a debit.

period-based costing

A method of collecting and reporting costs by period rather than by some other method such as by discrete jobs. Used primarily in costing repetitive schedules and non-standard expense discrete jobs.

periodic alert

An alert that checks your database for the presence of a specific condition according to a schedule you define.

permanent transfers

See project transfers.

Phantom

It is an item or a component which is never stocked and is used as a part in building the final item. A phantom may further be made up of phantoms.

phantom assembly

An assembly Work in Process explodes through when it creates the bill of material for a job or schedule. A particular assembly can be a phantom assembly on one bill and a subassembly on another.

physical inventory

A periodic reconciliation of item counts with system on-hand quantities.

physical tags

A tool for recording the on-hand quantity for a specific item in a specific location. A tag is most commonly a slip of paper posted at the item's location.

pick list

A report that lists all component requirements sorted by supply type for a particular discrete job, repetitive schedule or production line.

pick release

An order cycle action to notify warehouse personnel that orders are ready for picking.

pick release batch

See picking batch.

pick release rule

A user-defined set of criteria to define what order lines should be selected during pick release.

pick release sequence rule

The rule for pick release that decides the order in which eligible order line details request item reservations from Oracle Inventory.

pick slip

Internal shipping document pickers use to locate items to ship for an order. If you use standard pick slips, each order will have its own pick slip within each picking batch. If you use the consolidated pick slip, the pick slip contains all orders released in that picking batch.

pick slip grouping rule

Criterion for grouping together various types of pick slips. The rule dictates how the Pick Slip Report program groups released lines into different pick slips.

pick to order

A configure to order environment where the options and included items in a model appear on pick slips and order pickers gather the options when they ship the order. Alternative to manufacturing the parent item on a work order and then shipping it. Pick to order is also an item attribute that you can apply to standard, model, and option class items.

pick to order (PTO) item

A predefined configuration order pickers gather as separately finished included items just before they ship the order. See kit.

pick to order (PTO) model

An item with an associated bill of material with optional and included items. At order entry, the configurator is used to choose the optional items to include for the order. The order picker gets a detailed list of the chosen options and included items to gather as separately finished items just before the order is shipped.

picking

The process of withdrawing items from inventory to be shipped to a customer.

picking header

Internal implementation of picking header that identifies distinct combinations of Pick Release criteria (Warehouse, Sales Order, Shipping Priority, Freight Carrier, Ship To, Backorder) in the previous product design. Picking Headers will be generated internally at Pick Release to ensure compatibility with the View Orders. However, when a delivery is closed in the Ship Confirm window, Picking Headers will be updated internally again to ensure all picking lines of a Picking Header are associated with the same delivery. The reason to maintain Picking Headers at Ship Confirm again is for the compatibility of the Update Shipment program. Update Shipment will process all Picking Headers associated with a delivery.

picking line

An instruction to pick a specific quantity of a specific item for a specific order. Each pick slip contains one or more picking lines, depending on the number of distinct items released on the pick slip.

picking rule

A user defined set of criteria to define the priorities Order Management uses when picking items out of finished goods inventory to ship to a customer. Picking rules are defined in Oracle Inventory.

pipe

Allows sessions in the same database instance to communicate with each other. Pipes are asynchronous, allowing multiple read and write access to the same pipe.

plan horizon

The span of time from the current date to a future date that material plans are generated. Planning horizon must cover at least the cumulative purchasing and manufacturing lead times, and is usually quite a bit longer.

planned order

A suggested quantity, release date, and due date that satisfies net item requirements. MRP owns planned orders, and may change or delete the orders during subsequent MRP processing if conditions change. MRP explodes planned orders at one level into gross requirements for components at the next lower level (dependent demand). Planned orders along with existing discrete jobs also serve as input to capacity requirements planning, describing the total capacity requirements throughout the planning horizon.

planned order

A suggested quantity, release date, and due date that satisfies net item requirements.

planned purchase order

A type of purchase order you issue before you order actual delivery of goods and services for specific dates and locations. You normally enter a planned purchase order to specify items you want to order and when you want delivery of the items. You later enter a shipment release against the planned purchase order when you actually want to order the items.

planner

Person responsible for deciding the time and quantity of a resupply order for an item.

planner

One of the processes that comprise the planning process, performed by the memory based planned. The planner uses the low level codes calculated by the exploder, together with the supply and demand information gathered by the snapshot, and calculates net material requirements for every planned item associated with the master schedule used to drive the planning process.

planner delete worker

An independent concurrent process, launched by the memory based planner, that removes previous plan output from the tables. It runs only when the memory based planner runs without the snapshot.

Planner Workbench

You can use the Planner Workbench to act on recommendations generated by the planning process for a plan. You can implement planned orders as discrete jobs or purchase requisitions, maintain planned orders, reschedule scheduled receipts, and implement repetitive schedules. You can choose all suggestions from an MRP plan, or only those that meet a certain criteria.

planning bill of material

A bill of material for a planning item that contains a list of items and planning percentages. You can use a planning bill to facilitate master scheduling and/or material planning. The total output of a planning bill of material is not limited to 100% (it can exceed this number by any amount).

planning data store (PDS)

It represents all the tables within Oracle ASCP which encompass those in the ODS and other output tables from planning. When we refer to PDS based ATP, we mean ATP based on planning output.

Planning Time Fence Days

An item attribute Master Scheduling/MRP uses when you set the Planning Time fence attribute to User defined time fence. Master Scheduling/MRP calculates the planning time fence for the item as the plan date (or the next workday if the plan is generated on a non workday) plus the value you enter here.

PO

See purchase order.

PO Change Request Vs. Sales Order

The term 'sales order' refers to the sales order data as stored in the base Oracle Order Entry tables. The term 'PO Change Request' or 'PO Change Request process' refers to the pending sales order data as stored and processed in this new change order process. Accepted PO Change Request result in an updated Sales Order in the base Oracle Order Management tables. There may be more than one pending change order request in the process for a given purchase order.

PO move resource

An outside resource that is automatically charged upon receipt of a purchase order. PO move resources also automatically initiate shop floor move transactions upon receipt.

PO receipt resource

An outside resource that is automatically charged upon receipt of a purchase order.

Point of Use (POU)

Inventory located at a specific operation on a flow line where it will be used. Material is pulled from these locations via a Kanban signal. These locations are in turn, supplied from either raw material stores or ideally, directly from the supplier.

pooled location

The destination in which several shipments are delivered and then grouped together to form a larger shipment.

pooled ship to

The delivery point for consolidated shipments, gathered from multiple locations, that will be shipped to an intermediate and/or ultimate ship to location.

position

A specific function within a job category. Examples of typical positions associated with the Vice President job include: Vice President of Manufacturing, Vice President of Engineering, and Vice President of Sales. See job.

position hierarchy

A structure of positions used to define management line reporting and control access to employee information.

postprocessing lead time

The time required to receive a purchased item into inventory from the initial supplier receipt, such as the time required to deliver an order from the receiving dock to its final destination.

pre approved

A document that has been approved by someone with final approval authority, but then forwarded to yet another approver for additional approval; or a document that has been authorized for approval but for which funds have not yet been reserved (if your organization uses encumbrance). A document with a status of Pre Approved does not show up as supply until its status changes to Approved.

precedence

Used by Oracle Pricing to resolve Incompatibility. Precedence controls the priority of modifiers and price lists. If a customer qualifies for multiple modifiers that are incompatible with each other, precedence determines the discount that the customer is eligible for based on the precedence level of the modifier. See also incompatibility.

predefined serial number

To define an alphanumeric prefix and a beginning number for your serial numbers before you assign them to items. Predefined serial numbers are validated during receiving and shipping transactions.

preprocessing lead time

The time required to place a purchase order or create a discrete job or repetitive schedule that you must add to purchasing or manufacturing lead time to determine total lead time. If you define this time for a repetitive item, the planning process ignores it.

prerequisite

A combination of a specific order cycle action and an associated result that must occur before an order progresses to its next action in an order cycle. See cycle action, order cycle, passing result.

previous level costs

The material, material overhead, outside processing, resource and overhead costs of the components used in the manufacture of an assembly.

price adjustment

The difference between the list price of an item and its actual selling price. Price adjustments can have a positive or negative impact on the list price. Price adjustments that lower the list price are also commonly known as discounts. Price adjustments can be for an order line or the entire order.

price adjustments

In Oracle Pricing, modifiers that result in monetary adjustments to an order. Types of benefits include: discount in %, amount or new price, discounts on other items, surcharges. See benefits.

price breaks

Discounts for buying large quantities or values of a particular item of a particular UOM, item category or any enabled pricing attribute.

price breaks

A quantity delimiters to which are associated prices or discounts by range of quantity and amount. These breaks may occur at either the line item level or at the total order level and associated with a item/ item group.

price break line

Supplier pricing information for an item or purchasing category on a quotation. The price you enter on a price break line depends on the quantity you order from your supplier. Usually, suppliers provide you with price break line structures to indicate the price you would pay for an item depending on the quantity you order. Generally, the more you order, the less expensive your unit price. Also, depending on the quantity you order, a supplier may provide you with different purchase conditions, such as advantageous payment or freight terms when you buy in large quantities.

price list

A list containing the base selling price per unit for a group of items, item categories or service offered. All prices in a price list are for the same currency.

pricing components

Combinations of pricing parameters you use when defining pricing rules. Pricing components can be made up of one or multiple pricing parameters.

pricing contracts

Used to setup a contract with associated contract lines which specifies the items that customer will purchase. Using the contract lines users will be able to setup items , their price, effective dates and price breaks for that item. Users will be able to have multiple versions of the contract and contract lines with different effective dates.

pricing date

In Oracle Pricing, the date according to which selling price will be calculated. Pricing Date can be Order Date, Ship Date or sysdate.

pricing event

A point in the process flow of a Pricing Line, e.g. Order, Contract etc. at which a call is made to the Pricing Engine to fully or partially price the Order or Contract. A pricing event is analogous to a Workflow event . Ex : Booking Order , Reprice Order, Shipping Order etc.

pricing information

Information that pricing calculation is based on such as pricing date, price list and unit price.

pricing parameters

A parameter you use to create components to be used in a pricing rule. Valid pricing parameters include segments of your item flexfield or Pricing Attributes descriptive flexfield.

Pricing Phase

A user defined control that can be applied to Price Lists, Discount Lists, Promotions, Deals, etc. In Oracle Pricing, the Pricing Engine looks at the phase when deciding which lists should be considered in a Pricing Event. See Pricing Event.

pricing request structure

In Oracle Pricing the Pricing Request Structure is the parameter information that is passed to the Pricing Engine for calculating the final price which is inclusive of all the modifiers that the customer is eligible for.

pricing rule

A mathematical formula used to define item pricing. You create a pricing rule by combining pricing components and assigning a value to the components. Oracle Order Management automatically creates list prices based on formulas you define. See pricing components.

primary and secondary locations

Primary sites are the key locations required by the Oracle application to associate the transaction to the customer site, supplier site, or other business entity that is key to identify the trading partner (owner) of the transaction. All other locations in the transaction are considered to be secondary location sites, such as a bill to location for a purchase order. Some secondary locations are not likely to be found in the transaction from the trading partner.

primary bill of material

A list of the components you most frequently use to build a product. The primary bill is the default bill for rolling up costs, defining a job, and calculating cumulative item lead times. Master Scheduling/MRP uses this bill to plan your material.

primary customer information

Address and contact information for your customer's headquarters or principal place of business. Primary addresses and contacts can provide defaults during order entry. See standard value.

primary line

See lead timeline.

primary role

Your customer contact's principle business function according to your company's terminology. For example, people in your company may refer to accounting responsibilities such as Controller or Receivables Supervisor.

primary routing

A list of the operations you most frequently perform to build a product. The primary routing is the default routing for defining a job and calculating manufacturing lead times.

primary salesperson

The salesperson that receives 100% of the sales credits when you first enter your order invoice or commitment.

primary unit of measure

The stocking unit of measure for an item in a particular organization.

prime cost

A cost which is charged directly to a work in process job or subinventory. Any labor or non labor resource or material is a prime cost; overheads are not.

priority

See line priority.

private API

An API intended to be used by the owning module only, giving maximum flexibility to other calling APIs. Calling APIs / program units are able to control execution of logic based on type of operation being performed.

private label

Where a supplier agrees to supply a customer with product labeled as the customers product. The customer is generally a retailer.

process

A set of Oracle Workflow activities that need to be performed to accomplish a business goal. see Account Generator, process activity, process definition.

Process

1) A planned series of actions or operations (e.g. mechanical, electrical, chemical, inspection, test) that advances a material or procedure from one stage of completion to another. 2) A planned and controlled treatment that subjects materials or procedures to the influence of one or more types of energy ( e.g. human, mechanical, electrical, chemical, thermal) for the time required to bring about the desired reactions or results. In flow manufacturing, processes are very generic activities on a flow routing that often consist of several events that are performed in a specific sequence. They are specific to a line and are often defined during the as is analysis on a flow line.

process activity

An Oracle Workflow process modeled as an activity so that it can be referenced by other processes; also known as a subprocess. See process.

process activity (diagram icons)

A Process Activity represents an Activity that is referenced by a process. Each row specifies the usage of an activity as the child of a process (e.g. process: 'ORDER_FLOW', and child activity: 'LEGAL_REVIEW'). These instances are marked with machine generated ID's to uniquely identify multiple instances of the same activity in the same process (e.g. AND or OR activities). Rows in this table map directly to icons that appear in a process diagram, thus the rows also store the X/Y coordinates of the icon in the process diagram. Each process has one or more special 'Start' activities that identify activities which may start the process.

Process Activity Transition

(diagram arrow) Process Activity Transitions define the relationship between the completion of one process activity and the activation of another. Each row represents a transition ("arrow") from a process activity that completes with a particular result, to another process activity that is now becoming active. (e.g. PA#102 ("LEGAL_REVIEW") with result "REJECTED" transitions to PA#214 ("TERMINATE")).

process definition

An Oracle Workflow process as defined in the Oracle Workflow Builder. See process.

process item type

Workflow processes can be for different process item Types. A header flow will have a workflow process item type 'OEOH' and a line flow will have a workflow process item type 'OEOL'. Process Item Types enable high level grouping of Workflow Processes.

Process Manufacturing

Manufacturing processes that produce products (such as liquids, fibers, powders, or gases) which exhibit process characteristics (such as grade, potency, etc.) typified by the difficulty of planning and controlling yield quantity and quality variances.

process network

You can use Flow Routings to represent the network processes on your production line. This network can include alternate processes, rework loops and feeder lines. You can assign yields and planning percentages for each of these processes to determine the optimal number of resource requirements.

process volume

In the Oracle Mixed Model Map, the quantity of an assembly that must pass through an operation or process to achieve the line demand volume. It equals the (demand times * average planning percent * boost %)/average reverse cumulative yield.

processes and events

Processes are very generic activities (in other words painting) that often comprise of multiple events (in other words prepare the surface, polish the surface, paint the surface) which are performed in a specific sequence. Events are the actual physical tasks performed on the line. You can define standard processes and standard events that are used consistently across product families and production lines.

processing constraints

Constraints to making changes to data on an entity that has effected downstream activities that are difficult or costly to undo. For example, changing options on an ATO order where the Item has already been built.

Processing Constraints Framework

A generic facility that will enable you to define processing constraints for application entities and attributes(database objects and columns) and the set of APIs that will enable to you to query the existence of any constraint against the operation you wish to perform on that entity or it's attributes. See processing constraints.

processing days

See repetitive processing days.

processing lead time

The time required to procure or manufacture an item. For manufactured assemblies, processing lead time equals the manufacturing lead time.

processing status

The processing state of a row (record) in an open interface table. Common statuses include, but are not restricted to, Pending, Running, and Error. See repetitive processing days.

product

A finished item that you sell. See finished good.

product configuration

See configuration.

product family

A group of products with similar characteristics, often used in production planning. Flow product families often have similar product synchronization.

product pricing attributes

In Oracle Pricing, these define the products referenced in a deal, discount, promotion, or price list.

product structure

See production line The physical location where you manufacture a repetitive assembly, usually associated with a routing. You can build many different assemblies on the same line at the same time. Also known as assembly line.

product synchronization (Sync)

Process of defining events, processes, and operations and assigning them to a flow routing in a specific sequence in which they are performed.

productivity

An overall measure of the ability to produce a good or a service. It is the actual output of production compared to the actual input of resources. Productivity is a relative measure across time or against common entities (labor, capital, etc.).

products and parts

Products and parts are similar to items defined in Oracle Manufacturing. The item type attribute can be used to identify different types of items (for example, finished goods, spare parts, and so on).

production line

The physical location where you manufacture a repetitive assembly, usually associated with a routing. You can build many different assemblies on the same line at the same time. Also known as assembly line.

production lines

Production Lines are manufacturing work areas where you manufacture families of products. Oracle Flow Manufacturing lets you manage flow production activities by production line. You can use Flow Routings to define the production process of assemblies. You can also use the Mixed Model Map to calculate the line takt time.

production lineset

The units committed and sequenced to build in production for a specific number days at a customer's manufacturing facility.

production rate

Hourly rate of assemblies manufactured on a production line.See line speed.

production relief

The process of relieving the master production schedule when a discrete job is created. This decrements the build schedule to represent an actual statement of supply.

Production Sequence Schedule (PSQI)

An EDI document (866/CALDEL/SYNCRO & SYNPAC) used to request the order in which shipments of goods arrive, or to specify the order in which the goods are to be unloaded from the conveyance method, or both. This specifies the sequence in which the goods are to enter the materials handling process, or are to be consumed in the production process, or both. Dates are always discrete, never "bucketed".

profile option

A set of changeable options that affect the way your applications run. In general, profile options can be set at one or more of the following levels: site, application, responsibility, and user.

proforma invoice

A detailed quotation prepared as to resemble the actual Receivables invoice likely to result if the quotation is successful, which shows the buyer what the seller is willing to do, as well as his or her expectations including (but not limited to): Terms of Payment, Terms of Delivery/Terms of Sale, Price of Goods, Quantity of Goods, Freight and Special Charges. The Proforma Invoice has no accounting and no Open Receivable.

Program Unit

Any packaged PL/SQL procedure or function.Program unit level tags must appear immediately after keyword 'IS'.TPS Program Unit: --<TPA_TPS>

project

A unit of work broken down into one or more tasks, for which you specify revenue and billing methods, invoice formats, a managing organization, and project manager and bill rates schedules. You can charge costs to a project, as well as generate and maintain revenue, invoice, unbilled receivable and unearned revenue information for a project.

project blanket release

An actual order of goods and services with a project and task reference against a blanket purchase agreement.

project drop shipment

A process of having the supplier provide the items directly to your customer for a project or task. The sales order is linked to a project and task. The purchase requisition is linked to the same project and task. The procurement cost is collected on Oracle Projects.

project flow schedule

Flow schedule with project and task references.

project inventory

Any and all items and costs in both project subinventories and project work in process jobs. Inventory owned by a project or task. You can segregate inventory by project using project locators.

project job

A standard or non standard WIP job with a project reference. The valuation accounts associated with this type of job will be project work in process. Any balance remaining in such a job when it is closed will be reported as a variance.

project kiosk

Kiosk to view information related to a project for manufacturing and/or project costing activities. The manufacturing information viewed could be, WIP jobs, line schedules, procurement activities, manufacturing plans and so on. Project costing information such as expenditures, commitments can be also viewed here.

project locator

A locator with a project or project and task reference. See common locator.

project locator

A locator with project and task segment values. A project locator is a logical partition of a physical location by project and task.

project manufacturing

The type of project that uses Projects with Manufacturing to track the costs of a manufacturing related project against a project budget.

Project Manufacturing

A type of manufacturing environment where production requirements are driven by large projects. You can plan, schedule, process, and cost against a specific project or a group of projects. If Oracle Project Manufacturing is installed and the Project References Enabled and Project Control Level parameters are set in the Organization Parameters window in Oracle Inventory, you can assign project and, if required, task references to sales orders, planned orders, jobs, requisitions, purchase orders, and other entities within Oracle Manufacturing. If the Project Cost Collection Enabled parameter is also set, you can collect and transfer manufacturing cost to Oracle Projects.

Project Manufacturing Costing

A series of features in Project Manufacturing designed to support manufacturing costing in a project manufacturing environment. Project Manufacturing Costing allows you to track item cost by project or a group of projects, and transfer project related manufacturing transaction costs to Oracle Projects.

project manufacturing organization

A new organization classification added since Release 11i. Allows the organization to be setup for Project manufacturing activities. Also see project manufacturing.

project move orders

Manage project material movement between subinventories by creating (manually or automatically), approving, and transacting material(project) move orders.

Project MRP

A series of features in Project Manufacturing designed to support manufacturing planning processes in a project manufacturing environment. Project MRP allows you to segment all sources of supply and demand by project and task. This allows the planning process to net and plan supply by project and task.

project purchase order

A purchase order with a project and task reference.

project requisition

A requisition with a project and task reference.

project sales order

A sales order with a project and task reference.

project subinventory

A subinventory with a project reference into which terms can be delivered and out of which items can be issued and transferred.

project 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. You can charge costs to tasks at the lowest level only. See Work Breakdown Structure.

project transfers

Transfer of material between projects where the cost is moved with the material and there is no repayment required.

project work order less completion

A WIP transaction that you can complete assemblies for a project and task without referencing a job or repetitive schedule. Project work order less completion automatically backflushes all operation pull, assembly pull, and push components from project locators for hard pegged components and from common locators for non hard pegged components.

projected available balance (PAB)

Quantity on hand projected into the future if scheduled receipts are rescheduled or cancelled, and new planned orders are created as per recommendations made by the planning process. Calculated by the planning process as current and planned supply (nettable quantity on hand + scheduled receipts + planned orders) minus demand (gross requirements). If PAB is zero or negative, then it is a stock out situation. Note that gross requirements for projected available includes derived demand from planned orders. Note also that the planning process uses suggested due dates rather than current due dates to pass down demand to lower level items. See current projected on hand.

projected on hand

The total quantity on hand plus the total scheduled receipts plus the total planned orders.

resource offset percent

An operation resource field that represents, as a percent of the processing lead time for an item, the item when a resource is required on a routing. For example, if the processing lead time for an item is 10 days, and the resource is required on the fourth day, then the resource offset percent is 30%. Capacity uses resource offset percent to calculate setback days during the bill of resource load process.

resource requirement

A resource and quantity needed to build an assembly on a job or repetitive schedule. Discrete job and repetitive schedule resource requirements are created based on the resource requirements specified on the assembly's routing. Resource transactions fulfill resource requirements.

resource roll up

Rolls up all required resources for a end assembly based on the routing and bill of material structure.

resource sequence

The number that indicates the order of a resource in an operation relative to other resources.

resource set

A grouping of bills of resources.

resource transaction

A transaction where you automatically or manually charge resource costs to a discrete job or repetitive schedule.

resource units

The number of units of a resource available for this resource at this operation.

resource units applied

A quantity you charge to a job or repetitive schedule for work performed by a resource. The quantity is expressed in the unit of measure of the resource. For example, if the unit of measure of a resource is hours and the resource works 10 hours, you apply 10 resource units to the job or repetitive schedule.

resource UOM item

A purchasing item associated with an outside resource that you purchase using the resource's unit of measure.

responsibility

Determines the data, windows, menus, reports, and concurrent programs you can access in Oracle Applications. It is linked directly to a data group. Several users can share the same responsibility, and a single user can have multiple responsibilities.

result

See action result.

result code

In Oracle Workflow, the internal name of a result value, as defined by the result type. See result type, result value.

result type

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

result value

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

Retroactive Billing

A pricing system which can extend to shipped products. Pricing is based on customer purchase order modifications, for example, changes in commodity prices or expected production volume. The difference between the price originally billed when the product shipped and the new applicable price is calculated and applied to applicable shipped quantities. The customer is billed (or credited) for the adjustment.

return

In Purchasing, an AutoCreate option that lets a buyer return a requisition line and all other unpurchased requisition lines on the same requisition to the requisition preparer. In Order Management, it is the opposite of a sales order. It involves receipt of goods previously sold to a customer, credit to a customer, and possibly replacement with an identical or similar product.

return days

Return days are the number of days since a return is entered before it is accepted. This is calculated as the accepted date - ordered date (Note accepted = fulfilled).

return from scrap transaction

This transaction is used for returning scrapped assemblies. In this document Return from Scrap transaction will mean CFM return from scrap.

Return of Material Goods (RMG)

See Return Material Authorization.

return material authorization (RMA)

Permission for a customer to return items. Receivables allows you to authorize the return of your sales orders as well as sales made by other dealers or suppliers, as long as the items are part of your item master and price list.

return reason

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

return to supplier

A transaction that allows you to return to the supplier items from a fully or partially received purchase order and receive credit for them.

revenue recognition

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

revenue sales credit

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

reverse cumulative yield

Product of the yields at each operation, process, or event on a flow line starting with the last operation, process, or event.

reversing transaction

A transaction that reverses a previously processed material, move, resource, or overhead transaction.

revised component

Component changes to an assembly that is a revised item on an ECO.

revised item

Any item you change on an engineering change order. Revised items may be purchased items, subassemblies, finished goods.

revised item status

A classification you can use to track and control a revised item's life cycle. Revised item statuses include Open, Released, Scheduled, Hold, Implemented, and Cancelled.

revision

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

revision control

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

revision quantity control

A condition placed on an item that ensures that you always identify an item by its number and its revision. Certain items require tighter controls than other. For instance, you may want to control the quantities you have in inventory for an item by revision. For another item, you may just want to know the quantities you have on hand across all revisions. You keep track of inventory quantities by revision when an item is under revision quantity control. You keep track of inventory quantities by item when an item is not under revision quantity control.

RFQ

See request for quotation.

RMA

See Return Material Authorization.

RMG (Return of Material Goods)

See Return Material Authorization.

roll flow schedules

An Oracle Manufacturing technique where you can copy the flow schedules you did not complete into the next available day or take over completions and subtract the total from the quantities of future schedule.

roll forward

An Oracle Manufacturing technique where you can automatically take the material you over issued to a particular repetitive schedule and move it forward into the next available repetitive schedule.

rough cut capacity planning

The process of converting the master schedule into capacity needs for key resources. See routing based capacity and rate based capacity.

rough cut planner

The routine that automatically calculates required resources for rough cut capacity planning (done when running a report or inquiry).

rounding control

An item attribute the planning process uses to decide whether to use decimal or whole number values when calculating planned order quantities or repetitive rates for the item. A value of Do not round order quantities the planning process uses and displays decimal values when calculating planned order quantities and suggested repetitive rates for the item. A value of Round order quantities means the planning process rounds decimal values up to the next whole number when calculating planned order quantities and suggested daily rates for the item. Planned order quantities and suggested daily rates are always rounded up, never down. The planning process carries any excess quantities and rates forward into subsequent periods as additional supply.

route

An ordered sequence of Lane Segments, from point of Origin to point of Ultimate Destination for a shipment. The sum of all of the lane segments, i.e.: where "A" to "B" and "B" to "C" are lane segments, the route will be "A" to "C".

route sheet

A report that provides full routing, operation, resource, and material requirement details for jobs and repetitive schedules. Typically used to know how, when, where, and who builds an assembly. Also known as traveler.

routing

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

routing network

Routing network defines the flow of work from one line operation to the next. It also specifies which path in the routing is an alternate or rework path. Routing networks, line operations, and events are the only entities considered in WIP.

routing revision

A specific version of a routing that specifies the operations that are active for a date range.

routing based capacity

Capacity planning at the resource level. Required capacity, available capacity, and capacity utilization are calculated for individual resources assigned to operations on routings. Required and available capacity are stated in terms of hours per resource per week.

run

An intraoperation step where you move assemblies that you are working on at an operation.

safety stock

Quantity of stock planned to have in inventory to protect against fluctuations in demand and/or supply.

sales forecast

A projection of future sales for a given item, period and location, the sales forecast order type is used by customers to communicate what they expect to sell. Alternately, it can be used by a supplier to communicate to the customer what the supplier projects the customer to ship in the future. This sales forecast order type will be useful for the sales forecast collaboration in the CPFR business process. In both cases, the date that will be provided in the document will be the Ship Date to convey the expected date that the goods will be shipped to a customer.

Safety Stock

A quantity of stock that is planned to be in inventory to protect against fluctuations in demand or supply. In the context of scheduling, safety stock is defined as the additional inventory that is planned as a protection against forecast errors and short term changes in the order backlog. Oracle APS helps manufacturers to determine the amount of safety stock to hold at each inventory carrying location in their supply chain.

Safety Stock (item attribute)

An item attribute the planning process uses to decide whether to use fixed or dynamically calculated safety stock quantities when planning material requirements for the item. A value of MRP planned percent means the planning process plans to safety stock quantities it calculates dynamically as a user defined percentage of the average gross requirements for a user defined number of days. The user defined percentage is defined by the value you enter for the Safety Stock Percent attribute for the item. For discretely planned items, the user defined number of days is defined by the value you enter for the Safety Stock Bucket Days attribute for the item. For repetitively planned items, the planning process uses the repetitive planning period rather than Safety Stock Bucket Days. These safety stock quantities are dynamic in that they vary as a function of the average gross requirements calculated by the planning process for the item. A value of Non MRP planned means the planning process plans to safety stock quantities calculated and maintained in Inventory. These safety stock quantities are fixed in that the Snapshot loads them from Inventory before the planning process and they do not vary unless they are recalculated in Inventory.

Safety Stock Bucket Days

An item attribute the planning process uses when you set the Safety Stock attribute for the item to MRP planned percent. The planning process dynamically calculates safety stock quantities for the item by multiplying the average gross requirements for the item, over the time period defined by the value you enter for Safety Stock Bucket Days, by the value you enter for Safety Stock Percent.

Safety Stock Percent

An item attribute the planning process uses when you set the Safety Stock attribute for the item to MRP planned percent. The planning process dynamically calculates safety stock quantities for the item by multiplying the average gross requirements for the item, over the time period defined by the value you enter for Safety Stock Bucket Days, by the value you enter for Safety Stock Percent.

safety stock quantity

The quantity suggested by MRP as additional supply needed for safety stock. This quantity can change according to an effective date set in Inventory.

sales channel

A term that indicates the method used to generate a sales order, such as Telemarketing or Direct Marketing. You can use this attribute of an order to classify orders for reporting purposes.

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 non revenue sales credit, revenue sales credit.

sales order

In this document a sales order by default means an ATO sales order.

sales tax

A tax collected by a tax authority on the purchase of goods and services based on the destination of the supply of gods or services. You can set up your Sales Tax Location Flexfield structure to determine your sales tax rates and to validate your customer addresses. For example, in the United States, sales tax is usually calculated by adding the tax rates assigned to the shipping state, county, city.

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 Automotive adds together the tax rates for all of these components to determine a customer's total tax liability for an order.

salesperson

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

Salesperson

The salesperson parameter in both reports is based upon a query of the default salesperson stored on the header for each order. Although the header level salesperson may not have actually received credit for any of the lines in the order, due to line level overrides, our parameter is based upon the header information. Further, the Discount Summary report displays this header level salesperson on the report. If a user needs to truly check for salesperson level information, they should run the Salesperson Order Summary Report.

Salesperson and Ship to Country

Order Management prints the salesperson name and the Ship to Country if the line and the header level information differs from each other. If it is the same, than this information is not printed at the line level.

schedule

A transaction containing current or future product demand, communicated by the customer to the supplier via EDI or other means. Types of schedules include Planning, Shipping, and Sequenced Production schedules.

schedule and shipments

The EDI Standards refer to dates and quantities to be shipped below the item level to be 'Schedule' data (found on SCH Schedule segments). To Oracle Order Entry this data is 'Shipment' Data.

schedule arrival date

The date returned by the system on which your customer can receive the products.

schedule date

The date for a master schedule entry for an item. A schedule for an item has a schedule date and an associated quantity. For Order Management, it is considered the date the order line should be ready to ship, the date communicated from Order Management to Inventory as the required date any time you reserve or place demand for an order line.

schedule end date

For repetitive items, defines the end of the repetitive rate for a master schedule.

schedule entry

A schedule for an inventory item. For discrete items, stated by a date and quantity. For repetitive items, stated by a date, schedule end date, and quantity.

schedule group

An identifier used to group jobs for scheduling and releasing purposes. For example, you might group together all jobs that must be completed on a specific date and are being built on the same production line. Jobs within a schedule group can be sequenced. See build sequence.

schedule horizon

Consists of the dates enclosed by the Horizon Start Date and the Horizon End Date. In a customer demand schedule, demand requirements and resource authorizations will be dated on or within this date range.

schedule item

A specific Customer Item on a demand schedule associated with a specific set of business entities and important CUM related qualifiers. Demand and other information is grouped by the customer within Schedule Item.

schedule item number

The number assigned to all demand, authorizations, shipment/receipt information, and other information related to the Schedule Item. This number is not applicable to sequences schedules.

schedule purpose code

Criteria used by the Release Management Demand Processor to interpret demand for each item on a schedule within the horizon date range.

scheduled ship date

The date on which the product is scheduled to depart from the Ship From Location.

schedule smoothing

The manual process of entering quantities and dates on the master production schedule that represent a level production policy.

scheduled flow schedule

These are flow schedules that are created by planning with a specific scheduled completion date.

scheduled receipt

A discrete job, repetitive schedule, non standard job, purchase requisition, or purchase order. It is treated as part of available supply during the netting process. Schedule receipt dates and/or quantities are not altered automatically by the MRP system.

sell through forecast

See sales forecast.

single level variance

A work in process variance that is the difference between the standard cost of an assembly and the actual charges to a standard jobs or repetitive schedules distributed by structure level. This variance looks at the assembly cost for the resource and overhead standard cost at the top level and compares them to the actual resource and overhead costs charged to the standard job or repetitive schedule. All other costs material, material overhead, outside processing, resource and overhead costs from lower level assemblies are included in the material usage variance calculation.

site use

See business purpose.

snapshot

The only phase under the memory based planning engine. The snapshot takes a snapshot or picture of supply and demand information at a particular point in time. The snapshot gathers all the information about current supply and demand that is required by the planner to calculate net material requirements, including on hand inventory quantities and scheduled receipts. Under the memory based planning engine, explosion and planning occur in the snapshot phase.

snapshot delete worker

An independent concurrent process launched by the snapshot monitor that deletes planning data from the previous planning run.

snapshot monitor

A process, launched by the memory based snapshot, that coordinates all the processes related to the memory based planning engine.

snapshot task

A task performed by the snapshot or a snapshot worker during the planning process.

snapshot worker

A group of independent concurrent processes controlled by the snapshot monitor that brings information into flat files. This information comes from Work in Process, Bill of Materials, on hand quantities, purchase orders, firm planned orders, routings, and Work in Process job resource requirements.

soft pegging

A pegging item attribute value. You can peg supply to demand for items with soft pegging.

soft reservation

The planning process considers sales order demand soft reservation.

Sold to Contact

(Placed by) How will we record or default the name of the person that placed the order. This is the person that the Customer service representative will contact at the Customer Site in the event of Ordering queries.

source base unit

The unit of measure from which you are converting when you define your interclass conversions. You define the destination base unit in terms of the source base unit. Your source base unit is the base unit of a unit class.

source forecast

When loading a forecast into another forecast, the source forecast is the forecast you load from.

Source Transaction System

The source application that populates the pricing tables with information using the Pricing API's. These include: Ex : Order Management, iMarketing , Trade Management , Contracts, etc.

sourcing

Used in Oracle Pricing to refer to the supply of a value for an attribute. See defaulting and dimension sourcing.

sourcing

The action of identifying a purchasing source or supplier for goods or services. To identify the best sources for your purchases, you can create RFQs that you send to your suppliers, enter quotations from your supplier, and evaluate these quotations for each item you purchase.

sourcing externally

When a customer orders an item, we ship it from one of our warehouses. This is known as sourced internally. But we ask our vendor to ship to the customer directly, we say the item is sourced externally.

sourcing rule

Specifies how to replenish items in an organization, such as purchased items in plants.You can also use sourcing rules to override sourcing that is specified in the bill of distribution assigned to an item.

sourcing rule assignment

See assignment hierarchy.

spare part

A synonym for service part. It is an inventory item used without modification to replace an original part during the performance of maintenance or repair to a serviceable item or product.

specification

Describes the requirements of a product in Oracle Quality. You can define specifications for the key characteristics of the products you produce.

specification element

A collection element copied or assigned to a specification.

specification limits

Numeric values used to specify an acceptable range of values for a quality element. Consists of a target value, and upper and lower control limit, and an upper and lower reasonableness limit.

specification subtype

A user defined subclassifcation of the standard specification types: customer, vendor, or an item/item category. For example a customer specification can be assigned a specification subtype that indicates the customer's plant location.

specification type

A classification for specifications. Specifications can be specific to a customer, vendor, or an item/item category.

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.

spot exchange rate

A daily exchange rate you use to perform foreign currency conversion. The spot exchange rate is usually a quoted market rate that applies to the immediate delivery of one currency for another.

SPSI

Transaction code assigned to inbound electronic Planning Schedule with Release Capability transaction in the Oracle e Commerce Gateway. Data from this transaction feeds into Oracle Release Management Demand Processor.

SQL validation statement

A statement written in SQL to customize action details.

SQL script action

An SQL script invoked by action rule processing in Oracle Quality.

SSSI

Transaction code assigned to inbound electronic Shipping Schedule transaction in the Oracle e Commerce Gateway. Data from this transaction feeds into Oracle Release Management Demand Processor.

standard actions

Order Management provides a selection of predefined actions, called standard actions. Use these actions, along with those you define yourself, to create your customized order cycles. See cycle action, order cycle.

standard bill of material

A bill of material for a standard item, such as a manufactured product or assembly.

standard component

A mandatory component used to assemble an ATO (assemble to order) item or configuration.

standard comments

Standard text you can assign to discrete jobs or repetitive schedules. Special instructions or details specific to a particular job or circumstance.

standard costing

A costing method where a predetermined standard cost is used for charging material, resource, overhead, period close, job close, and cost update transactions and valuing inventory. Any deviation in actual costs from the predetermined standard is recorded as a variance.

standard discrete job

A type of discrete job that controls material and resources for standard production assemblies.

standard item

Any item that can have a bill or be a component on a bill except planning items, option classes, or models. Standard items include purchased items, subassemblies, and finished products.

standard note

A routine message you can predefine and automatically or manually attach to orders, returns, order lines, and return lines to convey important information. See one time note, automatic note.

standard note

A long note you define for Oracle Manufacturing and can later reference on as many documents as you want.

standard operation

A commonly used operation you can define as a template for use in defining future routing operations.

standard planning engine

A planning engine that drives the planning process. This planning engine consists of three phases, each of which follows a strict sequence: the exploder, the snapshot, and the planner. These phases are followed by two optional phases: CRP planner, and maintain repetitive planning periods. See memory based planning engine, planning process.

standard purchase order

A type of purchase order you issue when you order delivery of goods or services for specific dates and locations for your company. Each standard purchase order line can have multiple shipments and you can distribute the quantity of each shipment across multiple accounts. See purchase order.

standard rate

The frozen standard unit cost for a resource.

standard receipt

A receipt routing in which shipments are received into a receiving location and then delivered in a separate transaction. Standard receipts can be inspected or transferred before delivery.

standard unit conversion

The conversion formula you define between different units from the same unit class. You define your own standard conversion.

standard unit cost

The unit cost you may use to cost all material and resource transactions in your inventory and work in process system. This cost represents the expected cost for a component or assembly for a specified interval of time. The basis for standard cost may be the cost history, purchase order history, or predicted changes in future costs.

standard value

The default value Order Entry automatically places in an attribute to improve the efficiency and accuracy with which you enter an order. The standard value for an attribute is frequently based on other values in the order. See attribute, default value, object, standard value rule set.

standing data

Data that is generally independent, not subject to frequent changes, consumption or transactions, i.e.,customer data, item data, address data.

status

See customer status.

start date

The date you plan to begin production of assemblies in a discrete job.

statistical forecasting

A mathematical analysis of past transaction history, last forecast quantities, and/or information specified by the user to determine expected demand.

status check

A set of tests Purchasing performs on a purchasing document to ensure it is in a valid state before performing an approval action.

stop

A point along the route a trip makes to its final destination. This point may also have some activity associated with it. The activity might include picking up a new delivery, dropping off a delivery or both. In Pick Release, stop is a release criteria for releasing items that have initial pick up locations corresponding to the specified stop, or location.

subassembly

An assembly used as a component in a higher level assembly.

subinventory

Subdivision of an organization, representing either a physical area or a logical grouping of items, such as a storeroom or receiving dock.

sublot

A subdivision of a lot which may be used when an entire lot is more than would be used or produced at any one time, but grouping of the material into a single lot is still desired. This maintains the integrity of the overall lot, but allows it to be consumed in manageable pieces.

submission check

A set of tests on a purchasing document to ensure it is ready to be submitted for approval processing.

submit

To send a document to another employee without attempting to approve or reserve funds for it yourself.

substitute item

An item that can be used in place of a component. Master Scheduling/MRP suggests substitutes items on some reports.

substitute receipt

An option that lets you receive predefined acceptable substitutes for any item.

suggested aggregate repetitive schedule

The optimal repetitive schedule suggested by MRP to satisfy a given master schedule. The optimal schedule represents aggregated production for all lines and considers the constraints of planning periods, item lead time, firm schedules, time fence control, acceptable rate changes and overrun amounts.

suggested dock date

The date you expect to receive an order (to arrive on the receiving dock) as suggested by the planning process.

suggested due date

The date when scheduled receipts are expected to be received into inventory and become available for use as suggested by the planning process.The need by date for the end item is the demand date. The need by dates for the dependent demands are calculated based on the lead time offsets that are associated to the Items and routings used.

• If a constrained plan is run, the planning process will use the planned orders and actual routings for scheduling to derive the suggested due date.

• If an unconstrained plan is run, the suggested due date will simply be the same as the need by date.

Therefore, any differences between the lead time offsets (need by date) and actual manufacturing time (suggested due date) created by the planning process, will show up in the form of multiple exception messages.

suggested order date

The date that the planning process suggests an order for goods or services is entered. The earliest order date allowed is today and no compression days are allowed.

suggested repetitive schedule

The schedule for an individual production line for a specific item that is derived from the Suggested aggregate schedule. MRP divides the suggested aggregate schedule for a specific line and item based on the production line attributes: priority, minimum and maximum rates.

suggested start date

The date you or your suppliers expect to start to manufacture the order as suggested by the planning process.

summary

Data at master (header) level representing similar information contained in more than sources at the detail level.

summary message action

A message representing one or more exceptions. The message may include introductory and closing paragraphs separated by the exceptions listed in a columnar report format.

supply chain ATP

This term is used to describe the task of performing an ATP check against multiple sourcing organizations for a given customer request.

Supply commit

Used by a suppliers communicate to customers anticipated future shipments. The date the supplier uses in the document is the Ship Date to convey when he expects to ship the goods to the receiving location. Alternately, the supplier can provide only a Receipt Date that conveys when he expects the customer to receive the goods. When only a Receipt Date is provided, Oracle Collaborative Planning will derive a Ship Date from the intransit lead time. In the absence of a lead time, the Receipt Date is the same as the Ship Date.

supply chain planning

The development and maintenance of multi organizational distribution and manufacturing plans across a global supply chain.

supply chain sourcing rules

A set of rules that define the supplier priority rank and percentage split for the ship to organization's planning requirements or the ship from organization's demand routing.

supplier

Provider of goods or services.

supplier flex fences

Specifies capacity tolerance percentages that vary over time for each source. This allows you to represent the ability of your supplier to flex capacity upwards based on the amount of advanced notice you provide.

supplier product number

The number your supplier assigns to an item. You and your supplier can have different item naming conventions. You can identify the item with one number (Item) while your supplier identifies this item using another number (Supplier Product Number). Using and referencing supplier product numbers helps you speed up your purchasing cycle. By referencing a number your supplier knows, you can help your suppliers understand your purchase orders and RFQs better.

supplier purchasing hold

A hold condition you place on a supplier to prevent new purchasing activity on the supplier. You cannot approve purchase orders for suppliers you placed on hold.

supplier quotation list

A list of suppliers who can provide goods or services you need. You often define a supplier quotation list for an item or class of items. You can use a supplier quotation list to generate multiple copies of a RFQ automatically and to manage supplier responses.

supplier requirement

See supplier sourced component.

supplier sourced component

A component item on a bill of material supplied to work in process directly by a supplier.

supplier specification

The customer specified material requirements for a product or service.

supply

A quantity of materials available for use. Supply is replenished in response to demand or anticipated demand.

supply agreement blanket purchase order

A type of purchase order you issue before you request actual delivery of goods or services. You normally create a blanket purchase agreement to document a long term supplier agreement. A blanket purchase agreement may contain an effective date and an expiration date, a committed amount, or quantity. You use a blanket purchase agreement as a tool for specifying agreed prices and delivery dates for goods and services before actually ordering them. Blanket agreement in Oracle Purchasing with the Supply Agreement flag set on the Blanket Agreement header. Only Supply Agreement Releases are picked up by Supplier Scheduling.

supply locator

The specific location, such as shelves or containers, within a supply subinventory that you use as the default locator in a material transaction.

supply release agreements

Release shipments against a Blanket Supply Agreement.

supply reserved

A schedule status showing that Oracle Work in Process (WIP) has recognized the demand for an item or configuration and opened a work order to supply the demand. Once the work order is complete and the finished product is received in inventory, WIP transfers a reservation for the finished product to the sales order. The schedule status for the order line or order line detail is then changed to be Reserved.

supply subinventory

The subinventory you use as a primary source of supply to meet a specific material requirement in a discrete job or repetitive schedule. In Release 9, this is the backflush subinventory for pull material or the primary issue subinventory for push material.

supply type

A bill of material component field that controls issue transactions from inventory to work in process. Supply types supported by Work in Process include: Push, Assembly pull, Operation pull, Bulk, Supplier, Phantom, and Based on bill.

system items flexfield

A flexfield that allows you to define the structure of your item identifier according to your business requirements. You can choose the number and order of segments (such as product and product line), the length of each segment, and much more. You can define up to twenty segments for your item. Also known as Item Flexfield.

system linkage

An obsolete term. See expenditure type class.

Table of Denial Orders

A government restriction on exports of certain products to certain countries and organizations.

TAG

Truck Advisory Group. An association of heavy truck and off road vehicle manufacturers, suppliers, carriers, and value added networks.

takt time

Operation cycle time the rate at which products need to be manufactured on the line. Aids in establishing the daily rate for the production line. takt Time=effective resource hours available per day / Average daily demand.

tare weight

The weight of an item, excluding packaging or included items.

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 work breakdown structure.

task kiosk

Kiosk to view manufacturing information related to a project task. The manufacturing information viewed could be WIP jobs, line schedules, procurement activities, manufacturing plans and so on.

tax amount

Tax which will be calculated based upon the extended selling price and freight charges.

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

tax codes

Codes to which you assign sales tax or value added tax rates. Oracle Receivables lets you choose state codes as the tax code when you define sales tax rates for the United States.

tax condition

A feature that allows you to define and evaluate one or more conditional lines. After execution, each tax condition may have one or more actions based on how each transaction against the condition validates.

tax engine

A collection of programs, user defined system parameters, and hierarchical flows used by Order Entry and Receivables to calculate tax.

tax exclusive

Indicates that tax is not included in the line amount for this item.

tax exempt

A customer, business purpose, or item free from tax charges.

tax group

A tax group that allows you to build a schedule of multiple conditional taxes.

tax inclusive

Indicates that the line amount for an item includes the tax for this item.

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

tare weight

The weight of an item, excluding packaging or included items.

target value

A number which indicates the desired result of a given quality characteristic. Can also be used to denote the expected average of values for a quality characteristic.

teardown time

The time required to clean up or restore a machine or work center after operation.

temporary transfers

See borrow payback

territory

A feature that lets you categorize your customers or salespeople. For example, you can group your customers by geographic region or industry type.

territory flexfield

A key flexfield you can use to categorize customers and salespersons.

this level costs

The cost or value added at the current level of an assembly. Resource, outside processing and overhead costs are examples of this level costs. Material is always a previous level cost.

three way matching

Purchasing performs three way matching to verify the purchase order, receipt, and invoice information match within tolerance.

time aggregation

You can post orders to the system specifying an item, order type, due date, bucket type, customer site, and supplier site. You can specify the order quantity at the daily, weekly, or monthly level depending upon the bucket type. The system treats an order quantity based on the bucket type in the following way:

• Time bucket specification: Day

  When you specify the time bucket as Day, during posting the order quantity is considered as due or available on the calendar date specified on the order.

• Time bucket specification: Week

  When you specify the time bucket as Week, during posting the order order quantity is considered as due or available for the week that includes the calendar date specified on the order. Note that each week has a start date and an end date, and each is derived from the site specific calendar.

• Time bucket specification: Month

  When you specify the time bucket as Month, during posting the order quantity is considered as due or available for the month that includes the calendar date specified on the order. A month always has a start date and an end date, and it is derived from the site specific calendar.

time bucket

A unit of time used for defining and consuming forecasts. A bucket can be one day, one week, or one period.

unallocated onhand

Posted by a trading partner to communicate to another the quantity of inventory physically in stock that is intended for the use all trading partners who receive such communication. The date that used by the trading partner for this order type is Actual Date to indicate the physical inventory being held by the trading partner for the intended purpose.

time fence

A policy or guideline established to note where various restrictions or changes in operating procedures take place. The planning process cannot create or reschedule orders within the planning time fence. This gives the planner the ability to stabilize the plan and thereby minimizing the nervousness of the system.

time phased requirements

Requirements for resources where the need dates are offset by the lead time for those resources.

time phased safety stock requirement

Time phased safety stock requirement is calculated using user supplied information on variable demand forecast and supplier lead times. ASCP and IO generate an optimal time phased safety stock plan to protect the OEM against demand and supply fluctuations.

to move

An intraoperation step where assemblies can either be completed to a subinventory or wait to be moved to another operation.

total credits/adjustments

Oracle Order Management prints the (Originally Due Amount - Balance Due Remaining) for each order listed on this report.

total lead time

An item's fixed lead time plus the variable lead time multiplied by the order quantity. For lead time calculations, Bills of Material sets the order quantity to the item's standard or lead time lot size. The planning process uses the total lead time for an item in its scheduling logic to calculate order start dates from order due dates.

Total Product Cycle Time (TPCT)

The total time along the longest path of your flow routing. Calculated by taking the sum of the elapsed times along the longest primary path on the routing network.

total quantity accepted

The total number of accepted items for the receipt line.

total requisition limit

The maximum amount you authorize an employee to approve for a specific requisition.

TPA metadata file

Contains information extracted from the TPA repository about TPA enabled program units and layers built on top of them. This file is used to ship the TPA registry, or repository, and merge layers at the customer site. This file must be shipped with any patch that contains TPA enabled program units.

TPA package

The package containing TPA program units. This package is always generated from the TPA repository.

TPA program unit

The mirror program unit for a public program unit. For every public program unit, Oracle developers will designate a TPA program unit. TPA program units are generated by the architecture to insulate generic code from custom code. All calls to customizable generic code and custom code are made through the TPA program unit.

TPA repository

The registry which stores data required for the functioning of the Trading Partner Architecture. It includes information about public program units, TPA program units, TPS program units and complete definition of the layers including the Oracle Base Layer.

TPA tag

One line hyphen comments which appear at the beginning of a new line and provide information about customizable program units within Oracle code. The syntax for a TPA tag is:--<tag name=tag value>For example, a label is specified as follows,--<TPA_LABEL=label>

trading partner

Any company that sends and receives documents via EDI.

Trading Partner Architecture (TPA)

The framework that supports PL/SQL based layer development and deployment.

trading partner flexfield

Descriptive flexfields reserved on several base tables for capturing additional attributes applicable to specific trading partners. They are provided for most of the base tables in Oracle Release Management, Shipping and Order Management.

trading partner layer

The trading partner specific code created to replace Base Layer code. The layer consists of a set of PL/SQL program units that perform trading partner specific processing or validations in place of the generic code provided by Oracle Development.Layer Providers develop this code and populate the Trading Partner Layers by importing the trading partner specific code into the TPA repository. In this way, Layer Providers can develop Trading Partner Layers composed of trading partner specific code for various trading partners.

Trading Partner Selector (TPS)

A program unit which accepts context information for the business transaction and derives trading partner entities being processed in the current transaction instance.All TPS Program units must have the following five output (OUT/IN OUT) arguments:

trailer number

This number is used to track full truckload shipments.

transaction

Type Order and Lines can be grouped together loosely as certain Transaction Types. Accordingly, a transaction type can be used to default attributes/controls for an order or a line. Transaction Type Code determines whether the transaction type is an Order Transaction Type or a Line Transaction Type.

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

transaction cost

The cost per unit at which the transaction quantity is valued.

transaction date

The date you enter and Oracle Manufacturing maintains for any manufacturing transaction. The date must fall within an open accounting period and be greater than the release date for transactions on a discrete job or repetitive schedule.

transaction interface

An open interface table through which you can import transactions. See open interface.

transaction manager

A concurrent program that controls your manufacturing transactions.

transaction quantity

The quantity of a transaction.

transaction set

A complete business document such as an invoice, a purchase order, or a remittance advice. Synonym for document or message.

transaction set line item area

The line item area encompasses the actual business transaction set and includes information, such as quantities, descriptions, and prices.

transaction set summary area

The summary area contains control information and other data that relate to the total transaction.

transaction type

A feature that allows you to specify default values for orders and order lines including the customer, the ship to location, and internal or external orders.

transaction type code

Transaction type code determines whether the transaction type is an Order Transaction Type or a Line Transaction Type.

transaction worker

An independent concurrent process launched by a transaction manager to validate and process your manufacturing transactions.

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 activity, Workflow Engine.

transportation network

The organized substructure which defines the path and means of transportation between points of origin and points of ultimate destination. Includes Routes, Lanes, Zones, Locations.

traveler

See route sheet.

triangulation

A triangle that is created when three partners are involved in a drop shipment transaction.

trip

An instance of a specific Freight Carrier departing from a particular location containing deliveries. The carrier may make other stops on its way from the starting point to its final destination. These stops may be for picking up or dropping off deliveries.

trip planning stop

The process of planning the necessary vehicles and grouping the scheduled shipments that will be included in a given trip. Planning the trip requires consideration of vehicle load capacities, container capacities and, in certain cases, the loading order for the customer's specified unload order.

trip stop

A location at which the trip is due for a pick up or drop off.

trip stops

Represents a point along the route a trip makes to its final destination. This point may also have some activity associated with it. The activity might include picking up a new delivery, dropping off a delivery or both.

two level master scheduling

A technique that facilitates the forecast explosion of product groupings into related master production schedules. The top level MPS is usually defined for a product line, family or end product while the second level is defined for key options and components.

two way matching

Purchasing performs two way matching to verify that purchase order and invoice information match within tolerance.

ultimate ship to location

The final destination of a shipment.

UN number

An identifier for a hazardous material. Each Identification number has a description. Identification numbers are not unique. For instance, the same UN Number may correspond to 2 closely related but different types of materials.

unconstrained plan

In this plan, the system performs traditional MRP type planning and assumes infinite material availability and resource capacity. Statements of material availability and resource capacity are used to generate exceptions. Demand priorities are included during the planning run to determine the appropriate pegging relationships between supply and demand.