Glossary

action message: Output of the MRP process that identifies a type of action to be taken to correct a current or potential material coverage problem.

aggregate resources: The summation of all requirements of multi-department resources across all departments that use it.

allocated ATP: This term is used to describe the ability to allocate scarce supply, whether it's finished goods, or a key components or resources, to various demand channels. Whether you are performing ATP or CTP, the allocation is being considered for order promising. See Feature Highlight: Allocation.

alternate bill of material: An alternate list of component items you can use to produce an assembly.

alternate resources: Different resource or a group of different resources that can be used instead of primary resource or group of resources in the job operation. Each resource, or group of resources, can form an alternate group. Alternative scheduling is when the primary group can be replaced by an alternate group in the job operation.

alternate routing: An alternate manufacturing process you can use to produce an assembly.

alternate unit of measure: All other units of measure defined for an item, excluding the primary unit of measure.

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 it hides the implementation details.

assemble-to-order (ATO): An environment where you open a final assembly order to assemble items that customers order. Assemble-to-order is also an item attribute that you can apply to standard, model, and option class 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.

assignment hierarchy: You can assign sourcing rules and bills of distribution to a single item n an inventory organization, all items in an inventory organization, categories of items in an inventory organization, a site, and an organization. These assignments have an order of precedence relative to one another.

assignment set: A group of sourcing rules and/or bills of distribution and a description of the items and/or organizations whose replenishment they control.

ATO: See assemble-to-order.

ATO item: See assemble-to-order item.

ATO model: See assemble-to-order model.

ATP (Available to Promise): ATP (Available to Promise) typically refers to the ability to promise finished goods availability based on a statement of current and planned material supply.

ATP: See available to promise.

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

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

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

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 resources: A list of each resource and/or production line required to build an assembly, model, or option.

bottleneck resource: A resource whose capacity is less than the demand placed upon it. For example, a bottleneck machine or work center exists where jobs are processed at a slower rate than they are demanded.

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.

calendar type: The period pattern used to define a manufacturing calendar.

capable to deliver: CTD (Capable-to-Deliver) refers to consideration of the transportation resources and transportation lead time to meet your customers’ delivery needs. In this release, only transportation lead time is considered. Transportation resources will be added in a future release.

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

capacity requirements planning: A time-phased plan that compares required capacity to available capacity. It is based on a material requirements plan and department/resource information. See routing-based capacity and rate-based capacity.

component: A serviceable item that is a part or feature in another serviceable item. Your customers cannot report service requests against this type of serviceable item directly. You can reference components when you enter service requests against actual end item-type serviceable items, or products. For example, if you define three inventory items, A, B, and C, where A and B are products (end item-type serviceable items) but C is a component (non-end item-type serviceable item) of A, you can enter service requests against A and B directly, but not against C. When you enter a service request against product A, you can reference C because it is a component of A. see standard component.

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.

component yield: The percent of the amount of a component you want to issue to build an assembly that actually becomes part of that assembly. Or, the amount of a component you require to build plus the amount of the component you lose or waste while building an assembly. For example, a yield factor of 0.90 means that only 90 percent of the usage quantity of the component on a bill actually becomes part of the finished assembly.

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

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

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

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

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.

forward consumption: A mechanism used in planning during which the available future supply is consumed to meet a demand.

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.

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

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.

job routing: A snapshot of an item routing that has been assigned to a job. The routing is current on the day the job was created. Edits to a job routing do not automatically revert to the item routing.

master demand schedule: The anticipated ship schedule in terms of rates or discrete quantities, and dates. In ASCP, MDS is used as an input to the enterprise plan.

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.

multilevel supply chain ATP/CTP/CTD: This term is used to describe the task of performing a multilevel BOM availability check including finished goods, components, resource, supplier capacity and transportation lead time. See Feature Highlight: Multilevel Supply Chain ATP/CTP/CTDFor the rest of the document, we will use Multilevel ATP as a short form for this feature.

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.

operation data store (ODS): Represents all the tables that act as destinations for the collected data from each data source (both Oracle applications and legacy systems). This is the input for the snapshot portion of the planning process. When we refer to ODS-based ATP, we mean ATP based on collected data.

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.

overload: A condition where required capacity for a resource or production is greater than available capacity.

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.

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

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 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 exception set: An item attribute that the planning process uses to decide when to raise planning exceptions for the item.

planning horizon: The amount of time a master schedule extends into the future.

planning time fence: A Master Scheduling/MRP item attribute used to determine a future point in time inside which there are certain restrictions on the planning recommendations the planning process can make for the item.

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

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.

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

projected available balance: 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). 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.

refresh snapshot process: A database process during which the data stored in the database snapshots is updated with the new or changed data.

resource constrained plan: In this option, all resource constraints such as available machine hours, transportation capacity, as well as alternate resources are considered. Alternate bill of materials are considered only when optimized option is selected. Material constraints are used only to generate exceptions arising due to lack of material availability.

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.

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

schedule arrival date: The date when scheduled receipts are expected to arrive as suggested by the planning process. Also the date on which sales orders are expected to arrive at customer's location.

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.

schedule ship date: The date when you expect the supplier to ship scheduled receipts as suggested by the planning process. Also the date on which the sales order is planned for shipping to the customer.

Seiban manufacturing: A type of manufacturing environment where demand and supply are identified by Seiban numbers to peg supply to demand. This numbering system is widely used in Japan and Korea.

simultaneous resources: Two or more resources are scheduled to be working concurrently within a job operation. Each operation contains a scheduled sequence of activities and resources used in the operation. Simultaneity is implemented by having more than one resource used in an operation.

sourcing rule: Specifies how to replenish items in an organization, such as purchased items in plants.

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 start date: The date you or your suppliers expect to start to manufacture the order as suggested by the planning process.

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. See Feature Highlight: ATP for Multiple Supply Locations.

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.

time bucket: A unit of time used for defining and consuming forecasts. A bucket can be one day, one week, or one period.

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.

underload: A condition in which required capacity for a resource or production is less than its available capacity.