Oracle Work in Process and Discrete Manufacturing Quiz

In Oracle Bills of Material (BOM), each routing operation must be assigned to a department. This department determines the resources (such as machines and personnel) available for use in that operation. The other options describe resource groups or impact analysis rather than the direct purpose of the department field on routing.

A product family is a grouping of items that are planned and produced together. When designing a production line, you define the line for the product family as a group, not for individual items. Model and option classes are used for configurations, and standard refers to single standard bills.

The 'Mutually Exclusive' attribute applies to option class bills of material and controls whether a customer can select only one or multiple options within that option class during configuration.

Oracle Work in Process supports two primary types of discrete jobs: Standard discrete jobs (used for regular production) and Non-standard discrete jobs (used for repairs, prototypes, or experimental work).

The statement is incorrect because Oracle Work Order-less Completions allows overriding with any valid schedule group, not restricted to Flow schedules. The restriction mentioned doesn't exist in the actual Oracle functionality.

Lot Selection Method in Oracle WIP backflush parameters offers three valid options: Expiration Date selects lots soonest to expire (FEFO), Manual allows user selection, and Receipt Date selects oldest received lots first (FIFO).

Oracle WIP parameters serve two purposes: defining operational modes and default values for work in process functions, and each inventory organization can have only one set of these parameters, ensuring consistency across the organization.

Bulk supply type components in Oracle WIP are not backflushed - they require explicit manual issue transactions. Backflushing applies to Push or Assembly Pull supply types, not Bulk components which must be issued manually.

The WIP parameter 'Allow Creation of New Operations' for move transactions enables adding new routing operations on-the-fly during discrete job moves, commonly needed for unplanned rework steps that weren't in the original routing.

Backflush transactions in Oracle WIP are controlled by multiple parameters: Supply Subinventory defines where components are pulled from, Supply Locator specifies the exact location, and Lot Selection Method determines how lots are chosen (FEFO, FIFO, or manual).

Oracle WIP assigns lot numbers to discrete jobs using two methods: automatically based on the job name/number, or according to inventory organization lot numbering rules. Both approaches are valid depending on configuration.

Oracle WIP provides multiple Open Interfaces for importing transactions: Move Transaction Interface for move transactions, Material Transaction Interface for component issues/returns and assembly completions, and Resource Cost Transaction Interface for resource and labor transactions from external systems.

In Oracle WIP, engineering change orders (ECOs) are actually implemented on both standard and non-standard jobs using similar functionality. The system applies ECOs to job components and routings regardless of whether the job is standard or non-standard, so the statement claiming differential treatment is incorrect.

When reservation is set at the Subinventory level, materials cannot be transferred between subinventories because they are locked to the original subinventory. Changing the profile option to 'Items' level allows transfers since reservation only applies to the item itself, not its location. This is common when moving items from inspection subinventory to sales subinventory.

Engineer to Order (ETO) is the correct strategy for products built to customer specifications that require engineering work to incorporate those requirements. Make to Stock produces to forecast, Make to Order assembles to order from standard components, and Assemble to Order configures from standard modules without engineering.

Setting the 'Respond to sales order changes' parameter to 'Never' ensures that changes to a sales order (like placing it on hold or de-linking) will not automatically place the corresponding WIP work order on hold.

Discrete manufacturing involves producing distinct, identifiable, countable items (like cars or computers) in batches or lots. The other options describe configuring option classes or general assembly rules rather than the fundamental definition.

The 'Build in WIP' item attribute determines whether an item can be manufactured in WIP as a discrete job or a repetitive assembly. The other options describe default subinventories or generic component definition attributes.