Oracle Bills of Material (BOM) and Routing Quiz - Part 9

A price list in Oracle Advanced Pricing defines the unit price of items, the currency, and can reference dynamic pricing formulas. Since it contains all of these elements to determine the final list price of products, 'All of the above' is the correct choice.

Defining a routing requires standard departments, operations, and resources to exist, which are then assigned to a specific item. Therefore, item creation, departments, and standard operations are all mandatory prerequisites before a routing can be successfully defined in Oracle BOM.

Oracle Work in Process (WIP) does not automatically include substitute items in the component pick list; only the primary components from the BOM are listed. Substitutes must be manually selected or issued during the transactions, making the statement false.

Before creating an alternate bill of materials or alternate routing, the primary bill or routing must already be defined for that item. The primary structure acts as the base template. Other options like copying or importing still require a primary reference to exist first.

The Indented BOM (multi-level BOM) comparison tool or report allows users to compare two bills side-by-side to identify similarities and differences in components, quantities, and structure. Alternates, CTO, and ATO refer to configuration options or types rather than comparison utilities.

Substitute components are configured in the Substitute Components window, which is accessed by selecting a component in the Bill of Materials window and clicking the Substitutes button. The Bill Details tab and Revisions window do not support setting up substitutes.

In Oracle Bills of Material, you cannot create a chain of common bills where one common bill references another common bill. You are restricted to referencing a primary bill directly as a common bill. Because referencing a common bill is invalid, the statement is false.

Oracle Bills of Material (BOM) allows the creation and maintenance of production bills of materials, resources, departments, routings, and lead times. Production items are defined in Oracle Inventory, but are maintained and configured within the BOM structures. Thus, all listed actions are supported.

In Oracle Bills of Material, the maximum number of levels allowed in a bill structure is hard-coded to 60. The other values (64, 66, and 70) are incorrect distractors that do not match the system limitation.

The 'Config BOM Creation Allowed' parameter controls configuration bill generation. It is checked if you manufacture or purchase configurations, but can be disabled (set to No) in validation-only organizations or where config BOMs are unnecessary, making all scenarios valid.

Reference designators are mapping identifiers (like component labels on a PCB) assigned to components of standard bills. They do not apply to planning bills, model bills, planning components, or option class bills. Since all of those lack reference designators, none of the options alone is the sole exception, making 'None of the above' correct.

To check for circular references where an assembly is mistakenly added as a component of itself or its subassemblies, you run the Check for Loops program in Oracle BOM. While cost updates or UI validation might catch errors later, this dedicated program is the primary check method.

Oracle BOM allows users to define custom deletion constraints to enforce business rules before deleting bills, components, or routing data. Therefore, the statement that it is not possible to have custom deletion constraints is false.

Deletion constraints prevent the deletion of bills of material, routings, components, or operations if they do not meet specific business conditions. Deletion constraints can be defined and applied to all of these entities, so 'All the above' is correct.

Workday calendars support standard weekly patterns. 4/4/5 and 5/4/4 are common calendar split configurations used to divide a 52-week year into 13-week quarters. Both option 1 and option 2 are valid configurations, making option 3 correct.

Oracle BOM departments support various resource types, including person, machine, currency, and miscellaneous. Since person, machine, and currency are all valid resource types, selecting all the above is the correct choice.

Resource instances in a department define the actual number of resources assigned to a particular resource group (e.g., specific machines or people). They do not refer to the number of operations or routings defined in that department, which are separate routing attributes.

When shifts are enabled for a resource in Oracle BOM, the 24 Hours Available checkbox is disabled because availability is controlled by shift schedules. Option B is incorrect because shifts being disabled would allow the 24-hour flag.

Standard operations are reusable templates that can be shared across multiple routings. In contrast, standard routing operations (referred simply as operations) are unique and specific to a particular item's routing. Option 2 incorrectly states that standard operations cannot be used by other routings.