Maintaining Engineering Bills of Material

This chapter provides an overview of PeopleSoft Engineering bills of material (EBOMs) and discusses how to:

• Maintain EBOMs.

• Copy and transfer EBOMs.

• Delete EBOMs.

• Check the EBOM verification status.

Understanding PeopleSoft Engineering Bills of Material

Bills of material (BOMs) are structural designs that form the basis of all your item and product structures. To complete important tasks, such as material planning, allocating materials to production, or cost roll-ups, you need accurate and reliable BOMs. Also, as you modify existing products and introduce new products, you need the ability to isolate BOM changes from your production environment. With PeopleSoft Engineering, you can manage and develop EBOMs without affecting your manufacturing BOMs (MBOMs).

In the engineering environment, you can design product structures before you determine and assign all the item attributes. PeopleSoft Engineering enables you to use pending items (preapproved) defined within PeopleSoft Inventory, so that you can complete item initialization and approval independent of EBOM maintenance.

EBOMs differ from MBOMs in that:

• EBOMs are isolated from manufacturing and aren’t visible within PeopleSoft Supply Planning or PeopleSoft Manufacturing.

• EBOMs have relaxed edit checks.

  For example, you can use component placeholders on EBOMs when you don’t know the actual item number.

• You can add EBOMs for assemblies (and components) that are added in PeopleSoft Inventory, in a pending state.

If you have enabled PeopleSoft Workflow, when a change is made to MBOM or an EBOM, the system uses the BOM Change workflow to send a notification to the manufacturing engineer (or other role) that a BOM has been changed.

See Also

Delivered Workflows for PeopleSoft Engineering

Prerequisites

Before you begin defining and maintaining EBOMs, these steps might be required:

• Define assembly items with business unit attributes in PeopleSoft Inventory; you don’t need to approve them, however.

• Decide how to maintain BOMs for assembly items: by effectivity date or by revision.

• Maintain revisions for revision controlled assembly items.

• Decide whether to verify EBOMs online and define component revision settings.

• Determine multiple output BOM considerations.

• (Optional) Assign associated primary BOMs as part of defining multiple outputs.

• Decide whether to allow EBOMs to be copied to PeopleSoft Manufacturing and whether you want to delete EBOMs when they’re transferred back to PeopleSoft Manufacturing.

• Determine whether to use the embedded document management system to access revision, assembly, and component documents.

Common Elements Used in This Chapter

Prerequisites

This section discusses how to set up prerequisite tasks.

Defining Items for Use in PeopleSoft Engineering

With PeopleSoft Inventory, there is a single point of entry for all items that you use within PeopleSoft Manufacturing. Unlike your production environment, where an item must be approved before it can be accessed within the system, PeopleSoft Engineering can make use of inventory items defined in a pending or approved state, as long as item business unit attributes are defined. For example, when associating an item with a BOM, you can (within PeopleSoft Engineering) immediately access pending items on ECOs and EBOMs.

In addition to using items in a pending state, PeopleSoft Engineering enables you to use placeholder items within BOM maintenance prior to formal component item definition. Placeholder items enable you to define EBOM structure and component information before you enter component item information into the system.

To use pending items or cost component items within PeopleSoft Engineering, you must first define business unit attributes for the items.

The system won’t transfer an item from engineering to manufacturing unless the item status is Active.

Note. The content in this section is only part of what you need to know to define business unit attributes for items. Other relevant information, because it’s common to many applications, is located in the PeopleSoft Enterprise Application Fundamentals PeopleBook.

See Also

Maintaining EBOM Summaries

Maintaining BOMs by Revisions or Effectivity Dates

You can maintain item BOMs by:

• Revisions

• Effectivity dates

When you define your assembly items, use the BOM Usage group box to determine whether you manage your BOMs by using revisions.

You can indicate that you automatically generate revisions for the item. While you can define at the business unit level that all items in your business unit use automatic revisions by default, you can at the item level change that setting for specific items. Prior to using automatic revisions, you must set up a revision scheme with the Manufacturing Options component.

See Also

Maintaining BOMs by Revisions or Effectivity Dates

Maintaining Revisions

You can maintain revisions, including associated text, documents, and attachments. The item revisions that you create apply to EBOMs and MBOMs.

See Also

Defining and Maintaining Revisions

Verifying EBOMs Online and Defining Component Revision Settings

You can choose how to handle EBOM Online Verification and define component revision default settings on the MFG Business Unit Options page.

Note. When EBOMs are complex and deep, you should select Never Verify Online to improve EBOM maintenance performance, and then run the EBOM verification process from the Engineering BOM Verification page.

See Also

Setting Up Manufacturing Business Unit Production Options

Checking EBOMs for Loops

Multiple Output BOM Considerations

There are some conceptual differences between single-output BOMs (one primary item) and multiple output BOMs (at least one co-product is defined). When you create a multiple output BOM with a primary and at least one co-product, consider these points regarding single-output and multiple output BOMs.

Single-Output BOMs

BOM quantity is a scaling device field that enables you to enter a product structure when the assembly specifications are in a base greater than one unit. With BOM quantity, you determine the assembly quantity to which the component’s quantity per assembly (QPA) or per order is applied:

• If the BOM quantity is greater than 1, enter the component quantity in terms of the BOM quantity.

• If the BOM quantity is set to 1, the component quantity is the amount of the component required to make one unit.

Use BOM quantity for batched bills or when you know that you will only make a certain quantity of an item at a time.

Multiple Output BOMs

When you define multiple outputs (co-products) for a BOM, you are indicating that:

• At least two end-items are coming out of production, one of which is the primary item.

• The item ID that is specified for the BOM represents a batch item, in addition to representing the primary item to be completed.

This BOM structure is defined for item ID 6000, or, in other words, item ID 6000 is a batch item. The output for batch item 6000 includes primary item 6000, as well as co-product 6001, recycle by-product 6007, and waste by-product 6008.

BOM with multiple outputs

When used on a multiple output BOM, BOM quantity represents the in-process quantity for the BOM item ID as a batch item (as opposed to the item ID as a primary item).

For example, when the BOM structure has a BOM quantity defined as 150, the in-process units of the batch are 150. This also indicates that routing times (planning and costing), as well as rates, are in terms of a single batch unit.

Also, when creating production (IDs or schedules), you must also define the production quantity in terms of batch units. For example a production ID is added for 150 of the batch item 6000 to produce 60 gallons of 6000 and 30 pounds of 6001.

Multiple Output BOMs: Using Yield by Operation

This BOM example illustrates the effect of yield by operation with a 50 percent yield for one operation.

Note. When using yield by operation, the ending quantities for the by-products (recycle or waste) are based on the operation start quantity, not the BOM (batch) quantity.

BOM with multiple outputs (using yield by operation)

Assigning Associated Primary BOMs

Assign associated primary BOMs if you plan to define BOM co-products.

See Prerequisites.

Defining Engineering Copy and Delete Options

Copy and delete options control copying engineering BOMs (EBOMs) and engineering routings (ERTGs) to manufacturing.

See Setting Engineering Options.

Using Document Management

If you plan to use the Documentum embedded document management system to access revision, assembly, and component documents, use the Component Options page to define which function buttons are available on the EBOM document management pages.

See Also

Managing Documents

Maintaining Engineering Bills of Material

To define engineering BOMs, use the Engineering BOM Maintenance (EBOM_MAINTENANCE) component.

With the Engineering BOMs maintenance pages, you can create and maintain the product structure for the engineering version of a manufactured item at a summary or detailed level.

Note. You can view, but not modify or add, MBOMs from these pages. Make changes to MBOMs by transferring or copying EBOMs to MBOMs or by maintaining MBOMs directly within PeopleSoft Manufacturing.

In addition to creating a primary EBOM (with a BOM code equal to 1), you can specify up to 98 alternate EBOMs, by entering additional BOM codes (greater than 1) in the page displayed prior to accessing the Define Engineering Routings pages.

When you need to do additional or repair work on a completed assembly, you can create rework BOMs. This is useful if you have a standard rework process that requires additional components. As with MBOMs, you can define a primary rework BOM and up to 98 alternates, using BOM codes.

Create rework BOMs by selecting Rework as the production type when you add a BOM on the BOM Maintenance pages. Rework BOMs are always single-level BOMs. Also, PeopleSoft Cost Management doesn’t consider rework BOMs for any type of cost maintenance.

The rework BOM doesn’t include the assembly being reworked as a component. In PeopleSoft Manufacturing, when you firm up or release the rework production ID, the system copies the rework BOM to create a component list, and then adds the assembly being reworked. Rework BOMs can’t include multiple outputs; the system automatically includes the assembly being reworked as an output when production is created.

This section discusses how to:

• Maintain EBOM summaries.

• Specify assembly attachments.

• Define EBOM outputs.

• View the vendor access list.

• Maintain EBOM component details.

• Specify component attachments.

• Add substitute components.

See Also

Displaying Engineering Bills of Material

Pages Used to Maintain Engineering Bills of Material

Maintaining EBOM Summaries

Access the Engineering BOMs - Summary page.

Assembly Item Information

Note. Maintaining BOM information is less restrictive in PeopleSoft Engineering than in PeopleSoft Manufacturing because you can use pending, released, or nonexistent items. PeopleSoft Engineering ensures, however, that all items exist and are approved prior to transferring or copying the BOM back into PeopleSoft Manufacturing for use in manufacturing.

Component Information

Entering Component IDs

You can add a placeholder for a component item that doesn’t yet exist or for which the item number isn’t yet known. Do this by entering any value in the Component ID field. The system displays the item description placeholder. Placeholder items exist only on the EBOM and aren’t automatically added to the inventory item files.

You can maintain placeholder component information, such as effectivity dates or revisions, QPA, reference designators, and documents on the EBOM. When you determine the true item number, replace the placeholder by typing over the placeholder ID. If the placeholder item ID eventually becomes the permanent item ID, you don’t need to take any action. Once added, the system displays the item’s real description.

These restrictions apply to entering items and components:

• You can’t generate costs for a placeholder item.

• A component can’t be the same as its parent, and you can’t have overlapping effectivity dates for the same component.

• While you can create 99 MBOMs per assembly, Production BOM Code 1 is always the primary MBOM.

• You can’t create an EBOM for a non-inventory item or an item that has a source code of Floor Stock or Expense.

• While components can be nonowned items, assemblies cannot.

• The system doesn't allow staged date controlled items and configured items as components on BOMs.

Components can, however, have any source code except Planning.

Note. When adding a component with an item status of Hold or Discontinue, you receive a warning message. Similarly, when updating components with an item status of Hold or Discontinue, you receive a warning message at save time. In both cases, the message doesn’t prevent you from performing the action. However, if you try to add an inactive item, the system prevents you from adding the item.

Defining the Operation Sequence

You define the operation sequence on the item’s routing by using the Routing Definition Summary page. When maintaining the EBOM, you can select any operation on the assembly item’s routing, even if you haven’t defined the routing. Once you establish the routing, you can select the valid operation sequences for all corresponding routing codes and types by clicking the Op Seq Detail button. For MBOMs, the system displays operation sequences only for production routings. For rework BOMs, the system displays operation sequences only for rework routings.

Note. If a master routing is in use, then valid operation sequences include all engineering and manufacturing sequences associated with the item’s master routing.

Because a work center is associated with the routing’s operation, PeopleSoft Manufacturing uses the operation information to determine the work center to which to deliver the component. A storage area is assigned to every work center. When the component’s issue method is Issue or Replenish, the component is issued to the work center and stocked in and consumed from the work center’s WIP location storage area. When the component’s issue method is Kit, the work center is still the indicator for material delivery. The production ID, however, is charged directly for the component and is not consumed from the WIP location.

For kit components, when the operation sequence is set to zero, it’s assumed that the component item is kitted at the first operation.

If you enter the BOM before the routing, you can return to the BOM Summary page and add the relevant operation sequence after entering the routing.

Note. If the EBOM assembly has a reference or master routing other than itself, then the Op Seq fields reflect the master routing operations on this page and others in this component.

Quantity Precision Rules

To provide greater flexibility when defining EBOMs, the Quantity field need not follow the quantity precision rules defined for the item. The system issues a warning if you define a decimal quantity value for an item whose quantity precision value is a whole number.

Not enforcing quantity precision for quantity gives you flexibility that you might need. For example, suppose that one B0004 component is required to make two assembly A0001s. When defining the BOM, the QPA for B0004 is 0.5. If you apply the rounding rules for precision to the QPA, then the system rounds the QPA for B0004 to 1, and thereby inflates the production costs.

You can maintain quantity per with a precision of four places to the right of the decimal. Depending on the installation setting, a calculated QPA (calculated by dividing the quantity per by the BOM quantity) can be defined with a precision from 4 to 10 decimal places. Calculated QPA is determined as: Component QPA/BOM Qty.

For example, if a calculated QPA results in 6.54321, and the installation setting is set to 4 places, the system recognizes this as 6.5432. The system uses this calculated QPA to determine the cost of the assembly items and to plan and schedule components.

See Also

Verifying EBOMs Online and Defining Component Revision Settings

Understanding Component Issue Methods

Defining Master Routings

Quantity Rounding Exceptions in PeopleSoft Manufacturing

Specifying Assembly Attachments

Access the Engineering BOMs - Header: Assembly Attachments page.

Assembly Attachments

Note. You must set up file extensions on the File Locations page.

Attachments have no integration or relation to the embedded document management functionality. They are most useful when you aren’t using the document management functionality.

Defining EBOM Outputs

Access the Engineering BOMs - Header: Outputs page.

The detail portion of the page minimally contains the end item as the primary item, and you can’t delete this. As a result, if you aren’t maintaining multiple outputs, you can bypass this page, and the primary item is defined as the only output.

When there is only a primary output for an EBOM, all fields in the row are unavailable for entry or selection. The default settings are:

• Effectivity dates: Beginning to the end of time

• Percentage fields: 100 percent

• Output Qty: 1

If you insert another co-product (not by-product), then the primary’s output quantity, allocation percentage, and cost percentage become available. Conversely, if you delete all the co-products from the EBOM, then all the fields on the primary item become unavailable and are set to the defaults.

If you are maintaining a rework BOM, the Output Summary page lists only the reworked item as the end item. You can’t define co-products or by-products with rework.

Restrictions for Output Type and Output Item

These restrictions apply to the Output Type and Output Item fields:

• An item cannot be a co-product and by-product on the same BOM.

• A primary item can’t be added to or deleted from an EBOM.

The system always adds the assembly or end item for which the BOM is created as the primary output item.

• By-product items must have a Buy source code.

• co-product items must have a Make source code.

• co-product items can’t be a phantom or configured items.

• A co-product item can’t be the same as the primary item.

• An item can’t be both a co-product and a component on the same EBOM.

However, an item can be both a by-product and a component on the same EBOM.

• As long as the effectivity dates don’t overlap, the item can exist as a by-product more than once on the BOM at different operations or at the same operation.

• An item can’t be both a waste and a recycle by-product on the same EBOM.

• Additional outputs can’t be added to rework BOMs, phantom EBOMs, or configured item EBOMs.

Attributes tab

The Res % and Cost % fields enable you to distribute resource allocation and cost differently for each co-product. For each percentage, the total of all co-product percentages must add up to 100 percent. For the primary item, a value of 100 appears by default as both of these percentages. You can’t set the resource and cost percentages to 0.

For example, in this BOM structure, the primary output (6000) equals 60 gallons and co-product (6001) equals 30 pounds. The resource allocation percentages for the primary and co-products don’t need to be proportional to the output quantity; you can set them to any percentage as long as the percentages total 100. For this structure, the percentages are set to 60 percent for item 6000 and 40 percent for Item 6001:

Viewing resource allocation percentage

When completing against the co-products, the system can use the resource allocation percentage to determine what proportion of the batch quantity is consumed. In this case, if you did a partial completion of 15 pounds of 6001, then the proportion of the batch quantity completed is:

(15/30) x (40%) = 20% of the batch

This translates into a consumption of 25 percent of the components, earned labor hours, and so on. The system also uses the resource percentage to show, on BOM inquiries, how much material each output uses when exploding down the levels.

The resource allocation percentage enables the outputs to be in different UOMs, because the percentage specifies the relationship between the co-products, the primary, and the batch quantity.

Viewing the Vendor Access List

Access the Engineering BOMs - Header: Vendor Access List page.

BOM Access by Vendor	Click to access the BOM Access by Vendor page.
Send Email to Vendors	Click to send email. The email contains two URLs): A URL that sends the recipient to the Engineering BOM Maintenance - Summary page. A URL that sends the recipient to the Bill of Material inquiry page in PeopleSoft Engineering.

See Also

Defining Vendor Access Lists

Sending Email to Vendors

Maintaining EBOM Component Details

Access the Engineering BOMs - Components: Component Details page.

Component

If a component is a revision-controlled assembly, you can’t enter a revision for the item. The field isn’t accessible, and the system always uses the current revision. This ensures consistency with PeopleSoft Cost Management and PeopleSoft Supply Planning, which use the current assembly revision when exploding assemblies.

Note. When adding a component with item status of Hold or Discontinue, you receive a warning message. Similarly, when updating components with an item status of Hold or Discontinue, you receive a warning message at save time. In both cases, the warning message doesn’t prevent you from performing the action.

Subcontracting

EBOMs can handle all subcontracting or non-subcontracting scenarios including scenarios in which:

• You do your manufacturing in-house and you supply all components.

• A subcontractor supplies some components, where outside processing is performed.

• Your customer supplies some components, and you are the subcontractor.

In some instances, you may want to maintain the full product structure of the assembly item, even though you aren’t providing all the components necessary to manufacture the item.

Here’s a typical scenario:

1. You send a partially completed assembly to a subcontractor.

2. The subcontractor adds a component.

3. The subcontractor returns the altered assembly to you.

This scenario has implications for PeopleSoft Supply Planning, PeopleSoft Manufacturing, and PeopleSoft Cost Management, once the EBOM is copied to manufacturing.

When exploding demand for components stemming from an assembly requirement, the system doesn’t include subcontracted supplied components. Scheduling components for production also excludes subcontracted supplied components. These subcontracted components aren’t included in the production picking plan and they aren’t issued to a WIP location storage area. For the purposes of costing, subcontracted supplied components aren’t included in the assembly cost.

Here’s a list of valid subcontractor supply and nonowned field combinations:

See Also

Maintaining EBOM Summaries

Verifying EBOMs Online and Defining Component Revision Settings

Defining Items by SetID

Quantity Rounding Exceptions in PeopleSoft Manufacturing

Specifying Component Attachments

Access the Engineering BOMs - Components: Attachments page.

Attachments

Note. You must set up file extensions on the File Locations page in Set Up Financials/Supply Chain, Common Definitions.

Attachments have no integration or relation to the embedded document management functionality. They are most useful if you aren’t using the document management functionality.

Adding Substitute Components

Access the Engineering BOMs - Components: Substitutes page.

Component

Click the Copy BU Substitute Items button to copy business unit level substitutes to the BOM level.

Substitute Items

Copying and Transferring EBOMs

You can easily copy or transfer EBOMs. Copying EBOMs is useful when you want to copy an existing item’s BOM to a different item’s BOM. It also allows same as except type functionality. PeopleSoft Engineering transfers are most useful for transferring several BOMs that are associated with a change between manufacturing and engineering.

This section discusses how to:

• Copy EBOMs.

• View the copy EBOM details.

• Copy EBOM outputs.

• Transfer EBOMs.

Pages Used to Copy and Transfer EBOMs

Copying Engineering BOMs

Access the Copy Engineering BOMs page.

Source BOM

During the copying process, you can include or exclude certain components and substitutes. Using Define Engineering Routings pages, you can then change the new structure as needed.

Note. The BOM type of the target BOM (BOM2) and the source BOM must be the same. You don’t enter the BOM type in the Target BOM (BOM2) group box.

To enter the target BOM (BOM2):

1. Enter as the target BOM (BOM2) the business unit, item ID, and BOM code to which you are copying.

   The item must be a valid Make or Buy item in the target business unit. You can’t copy a BOM to a Floor Stock or Expensed item.

2. (Optional) Select the Copy Engineering BOM Detail tab to copy assembly and component text, documents, and attachments.

   If you are copying a source assembly or end item that’s revision-controlled to a target that’s a non-revision-controlled item, then the system uses the source component’s revision effectivity dates to determine the effectivity and obsolete dates of the target item’s components. The target BOM also updates with any component revisions specified on the source bill.

   Note. You can copy assembly and component documents for the same item from one BOM code to another. You can’t, however, copy assembly and component documents for different items: in this latter case, the Copy Documents fields are unavailable for entry or selection.

3. Click the Save button.

   If the specific BOM already exists at the target business unit, a message asks whether to overwrite the existing BOM with the information that you are copying. If you overwrite the existing BOM, the system deletes the BOM in the target business unit and adds the source BOM.

   Note. You can’t copy a BOM to a target business unit or item ID if the assembly item or any of its components isn’t defined in the target. If one or more components don’t exist in the target business unit, you can cancel the selection for those components, and then add the balance of the BOM. Then, you can add the missing components in the target business unit and use the BOM maintenance pages to complete the BOM structure.
   
   You can’t copy a BOM to itself.

4. Click the Edit BOM button to access the appropriate BOM Summary page, where you can edit attributes on the target BOM (BOM2).

See Also

Maintaining EBOM Summaries

Viewing the Copy EBOM Details

Access the Copy Engineering BOM Detail page.

Data on this page appear by default from the Copy Engineering BOMs page, and the fields operate the same as the fields on that page.

You can copy any assembly and component text, attachment, or document.

Note. You can copy documents only if you select identical source BOM and target BOM (BOM2) item IDs. When you copy a BOM, the system creates an audit of the copy including date, time, and user who performed the copy.

See Also

Transferring BOMs and Routings

Copying EBOM Outputs

Access the Copy Outputs page.

Data on this page appears by default from the Copy Engineering BOMs page. Fields on this page operate the same as fields on the page and fields on the Copy Engineering BOM Detail pages.

Component Details

Transferring EBOMs

While the copy BOM functionality is useful when same as except copies are required, it copies only one BOM at a time. Using the engineering transfers BOMs functionality enables you to transfer at once multiple single-level BOMs within a business unit. You can transfer BOMs:

• As part of the ECO process.

• By assembly items: Either a list or range of items.

You can transfer BOMs from engineering to manufacturing or from manufacturing to engineering. Transferring BOMs from engineering to manufacturing requires that all BOM items exist and are approved. So, while you can set up an item as pending, or even use placeholders when you design an EBOM, the item must be defined and approved before it’s transferred to manufacturing.

Deleting EBOMs

This section discusses how to delete EBOMs.

Page Used to Delete EBOMs

Deleting EBOMs

Access the Delete EBOMs page.

Search	Click to display the list of production or rework BOMs for the assembly items that you are deleting.
	Click the Select All button to select each Delete? check box next to each assembly.
	Click the Deselect All button to clear each Delete? check box next to each assembly.

You can delete production or rework BOMs.

For each assembly, the system deletes all EBOM components regardless of effectivity date or revision. All assembly EBOMs scheduled for deletion have header, outputs, related text, attachments, components, and reference designators deleted.

If you leave the BOM Code field blank, then the system deletes all BOMs, regardless of code. To delete only a specific BOM code, enter a value in the BOM Code field.

The Delete Engineering BOMs process checks and warns you of these conditions:

• BOM is used in a production area.

• Production exists in the Entered status.

• Production is planned, but a BOM and routing haven’t yet been frozen for production.

• Assembly item is present on pending or approved ECOs that haven’t been released to manufacturing.

Checking the EBOM Verification Status

This section discusses how to:

• Check EBOMs for loops.

• Delete EBOM verification rows.

• Display EBOM verification status summaries.

• Display EBOM verification status details.

Pages Used to Check the EBOM Verification Status

Checking EBOMs for Loops

Access the Engineering BOM Verification page.

The EBOM verification COBOL SQL process (ENPBEXPV) checks for loops within EBOM structures only. Once you copy the EBOM to manufacturing, run the BOM verification within PeopleSoft Manufacturing to verify the BOM within manufacturing.

Instead of running this process, you can use Online BOM Verification to check for loops. You set the Online BOM Verification option at the manufacturing business unit level with the MFG Business Unit Options page. However, to improve BOM maintenance performance when BOMs are complex and deep, use the scheduled verification process and set Online BOM Verification to Never Verify Online.

Engineering BOM Verification looks at just the primary EBOM and routing, when exploding at levels greater than 1. If there is more than one way to make a specific co-product output, tell the system which EBOM is the primary way to make that co-product and, therefore, which EBOM to verify for that co-product. To tell the system which EBOM to verify, select an associated primary BOM on the Define Business Unit Item - Manufacturing: General page.

Note. Both MBOMs and EBOMs use the same associated primary; there isn’t one specific to MBOMs.

Output Example

In this example, B is an output on two different processes:

BOM output example

Consider the two structures:

• In the first structure, A is the primary (item), with B as the co-product, and X, Y, and Z are components.

• In the second structure, D is the primary, and B and E are co-products, with F and G as the components.

Because there are two ways to make the same product (B), you need to decide which structure to use when exploding to lower levels. Therefore, you need to signify a primary structure associated with each item that may exist as a co-product, but not as a primary. To do this, assign an associated primary EBOM.

When exploding to lower levels, the system checks whether there is an associated primary defined for this item. If there is an associated primary item, the system uses it to explode to lower levels.

If exploding EBOM code 2 for the co-product, and an associated primary was defined, then the system uses EBOM code 2 for the associated primary, also.

For instance, if the system is exploding B (in the diagram) for EBOM code 2, and A is the associated primary, then the system looks for an item with an EBOM code 2 to explode. If EBOM code 2 doesn’t exist for A, then the explosion stops for this item, and the system generates an error. This same logic is used for BOM verification, inquiries, and costing.

You receive a message only if the system finds a looping BOM. You can view the results of the verification process by using the BOM Verification Status page.

See Also

Assigning Associated Primary BOMs

Deleting EBOM Verification Rows

Access the Delete EBOM Verification Rows page.

The verification request process adds a series of records to the BOM Explosion table. These records take up space and are useless if there are no looping BOMs. You can use this page to delete these records by process instance.

Displaying EBOM Verification Status Summaries

Access the EBOM Verification Status page.

Displaying EBOM Verification Status Details

Access the EBOM Verification Detail page.