Ifs Parts Worksheet

Working with Ifs Parts Worksheet in Practice

The Ifs Parts Worksheet is your go-to view when you need to manage bill of materials structures, compare alternative part configurations, or do bulk updates across a group of related items. It lives inside the Parts module and gives you a spreadsheet-style layout where you can see components, quantities, effective dates, and replacement relationships all at once. You open it from the Parts Work Order screen or directly through the Parts worksheet search page. Most people who know the system use it daily; most people who don't know the system try to skip it and immediately regret that decision. I've spent enough time in IFS Cloud and the earlier E-Business versions to know where this thing actually helps and where it quietly breaks your week. Let me walk through how it works, what trips people up, and what I do differently after making the same mistakes a few too many times.

Ifs Parts Worksheet Setup and Navigation

To get to the Parts Worksheet, you start from the Parts main form or navigate directly to the Parts Worksheet menu path. The interface loads with a default filter that usually shows all active parts. That default is almost never what you want. I always narrow the search before doing anything else — by part class, supplier, project, or business unit. Loading five thousand rows and then waiting for the grid to render is a waste of time you won't get back. The worksheet layout has several columns you can toggle on and off. The essential ones are Part No, Description, Alternative Part, Effective Date, From Date, To Date, Quantity, and Status. There are also hidden columns like Scrap Ratio, Unit of Measure, and BOM Line No that matter more than most people realize. I keep the BOM Line No visible because it tells you immediately if a line is out of sequence or if you've got duplicate entries in the same parent structure. When you open a parent part, the children appear in a hierarchical tree on the left and the detail rows fill the grid on the right. This is where the worksheet earns its name — you're working with a parts breakdown in a way that looks like a spreadsheet but functions like a structural editor.

Creating and Updating BOM Structures

The most common use case is building a new BOM from scratch or editing an existing one. You click Add Row, fill in the child part number, set the quantity, and save. The system validates the child part exists, checks that the unit of measure is compatible, and verifies the part is active. If any of those checks fail, you get an error that isn't always as clear as it should be. I've seen the "Invalid child part" message appear when the real issue was that the child part had been marked as inactive in a different organization code. Here's something most documentation doesn't emphasize: the difference between an Alternative Part and a Regular Child Part in the worksheet. An alternative part means the system can substitute one for the other during manufacturing or procurement. A regular child is mandatory. Mixing these up in a worksheet bulk update is a quick way to introduce phantom substitution paths into your BOM that nobody intended. I learned this the hard way when a client tried to bulk-load fifty alternative parts into a motor assembly worksheet and ended up with procurement triggering buy decisions for components that were only ever meant to be optional spares. The fix was to export the affected BOMs, cross-reference them against the original part master, and manually correct the alternative flags on each row. Took about three hours for fifty lines because there's no reverse-bulk operation for alternative flags. For bulk quantity changes across multiple child rows, the worksheet supports inline editing. Double-click the Quantity cell, type the new value, move to the next row. It saves on each individual cell change if your IFS configuration has auto-save enabled, which most sites do. That's convenient until you realize you made a systematic error — say, you typed 0.5 instead of 5.0 for half the rows. The correction workflow there is to undo the last action from the Edit menu or close the worksheet without saving and reopen it. The undo history in the Parts Worksheet goes back about ten operations, not further than that, so plan your edits in logical batches.

Dealing with Effective Dating and Version Control

Effective dating is where the Parts Worksheet gets powerful and where it gets dangerous at the same time. Every BOM line can have a From Date and optionally a To Date. When you're in the worksheet, these fields let you establish when a particular component becomes required or when it stops being used. This is critical for manufacturing parts that have engineering change orders associated with them. The trap most people fall into is assuming that setting an effective date in the worksheet automatically creates a lifecycle event. It doesn't. The worksheet edits are just data changes. If your organization requires ECO approval workflows, you still need to route those through the appropriate change management process. I've worked on sites where the Parts Worksheet was used to push out effective dates for revised components without going through the ECO board, and the audit trail came back six months later asking questions that couldn't be answered because the worksheet doesn't log who changed what beyond the standard IFS audit fields. One practical tip that isn't obvious: when you copy a BOM structure from one part to another using the worksheet's copy function, the effective dates don't carry over by default. You have to manually adjust them on the destination lines or the system treats them as active from today, which can cause conflicts with already-scheduled production orders that reference those components.

Export, Import, and Bulk Operations

The export function in the Parts Worksheet gives you a CSV or Excel file with all the visible columns plus the hidden ones if you've selected Show Hidden Columns from the View menu. The imported format needs to match the column headers exactly. IFS is reasonably forgiving about extra columns in the import file but not about missing required ones. The required columns are Part No, Child Part No, and Quantity. Everything else can be blank and the system will use defaults. I use a specific import pattern for seasonal inventory adjustments. Instead of updating each part individually, I build a spreadsheet with Part No, Child Part No, Quantity, and a calculated field that applies a percentage increase or decrease. I then import that as a batch update. This usually cuts what would be a four-hour manual process down to about twenty minutes of spreadsheet work plus five minutes of import time. The import validation catches syntax errors, invalid part numbers, and quantity mismatches before anything hits the database. There's a limitation worth noting here: the import doesn't validate cross-part dependencies. If your spreadsheet references a child part that's already marked for obsolescence in another module, the import will succeed but the system will flag it during the next MRP run. Always run a pre-import validation against the Parts Obsolete status report before committing a bulk load.

Known Limitations and When to Look Elsewhere

The Parts Worksheet isn't built for every scenario. It struggles with large hierarchical trees — if a single parent part has more than two hundred direct children, the worksheet becomes slow to load and nearly unusable for inline editing. In those cases, the Part Structure form gives you better performance even though the interface is less friendly. I've had to switch workflows mid-session when the worksheet started taking forty-five seconds to render a single row edit on a deeply nested assembly. Another limitation: the worksheet doesn't support concurrent multi-user editing of the same BOM. Two people opening the same parent part in the worksheet simultaneously will overwrite each other's changes silently. There's no lock mechanism that alerts users to conflicts in real time. The workaround is to communicate which parts are being edited and use the check-in/check-out feature if your site has it enabled, though not all IFS deployments have that configured for parts. Finally, the worksheet doesn't integrate with third-party PLM tools out of the box. If you're using a separate product lifecycle management system and need to sync BOM changes back and forth, you'll need a middleware integration or a custom API script. The Parts Worksheet is purely an IFS-native interface. Don't expect it to talk to SolidWorks, Teamcenter, or similar systems without additional development work.

Ifs Parts Worksheet Common Issues and Workarounds

Here are a few specific problems I've encountered and how I resolved them without involving support tickets that take weeks to close. Ghost rows appearing after import: sometimes the worksheet shows child lines that don't actually exist in the database. This happens when the browser cache holds a stale version of the worksheet session. The fix is to clear the IFS application session from the User menu and reload the worksheet. I run this as a standard step before any major bulk edit session. Quantity rounding errors: IFS stores quantities as decimals internally but the worksheet displays them rounded to the unit of measure precision. This creates a mismatch between what you see and what's actually saved. When working with precision-sensitive components like chemicals or custom-machined parts, I enable the Decimal Display option in the worksheet preferences so I can see the full stored value before committing changes.

Missing organization context: if your IFS setup uses multiple organizations and you open the worksheet without selecting an organization first, the part numbers may resolve to the default organization rather than the one you intended. I always verify the Organization field at the top of the worksheet before starting any edit session. A single wrong organization selection can propagate incorrect BOM data across an entire business unit if you're not careful. The Ifs Parts Worksheet remains one of the most practically useful screens in the IFS Parts module when you understand its behavior and its boundaries. It handles routine BOM maintenance efficiently, supports bulk operations that would be tedious through individual forms, and integrates directly with the MRP and procurement pipelines. It also has clear limitations around concurrent editing, large structures, and cross-system integration that you need to plan around from the start. Knowing what it can and can't do saves more time than any feature documentation will.