Independent IFS Cloud practice · Master data design
Design the part status set before parts are linked to it
An IFS Cloud part status is a master data record that describes the different phases of a part and controls the extent to which the system can use the part. Its parameters cannot be modified once the record is created, and a code linked to any part cannot be removed, so the set has to be designed before parts are linked. This article follows the 26R1 page on adding or modifying a part status.
Key takeaways
- A part status has three columns: Quantity On Hand, Demand and Supplies, and each column carries one setting per status code.
- If inventory still exists for a part, it cannot have a part status of Onhand Not Allowed.
- An inventory part must have the setting Demands Allowed to be used as a sales part, and parts linked to a code with Supplies Allowed can be purchased and received.
- The predefined status code is A, Active, with Onhand Allowed, Demands Allowed and Supplies Allowed; it cannot be deleted or modified and is the default for new inventory parts.
- Once a record is created, its parameters cannot be modified, and a code linked to any part cannot be removed.
1.What is a part status in IFS Cloud, and where is it set?
Part status describes the different phases of the parts, and this controls the extent to which the part can be used by the system. The status is set for each part on the Inventory Part page. Defining the status codes is a task for a system administrator or an equivalent person.
2.What do the three columns control?
Each status code carries one setting in each of three columns, with the effects and defaults below.
| Column | What the page says | Default |
|---|---|---|
| Quantity On Hand | Indicates whether or not a part can have a quantity on hand; if inventory still exists for a part, it cannot have a part status of Onhand Not Allowed | Onhand Allowed |
| Demand | Indicates whether or not demands are allowed; an inventory part must have the setting Demands Allowed for it to be used as a sales part | Demands Allowed |
| Supplies | Indicates whether or not supplies are allowed; with Supplies Allowed, parts linked to the code can be purchased and received, otherwise they cannot | Supplies Allowed |
3.What is the predefined status?
The predefined status code is A, Active, and this code cannot be deleted or modified. The default settings for Active part status are Onhand Allowed, Demands Allowed and Supplies Allowed. The system installed part status A, Active, defaults for each new inventory part record, and the status of a part can be changed on the Inventory Part page.
4.Which rules limit changes to statuses?
Once a status record is created, the parameters cannot be modified. If any parts are linked to a part status code, that code cannot be removed. A wrong combination in a created status therefore cannot be corrected by editing it, and the set has to be agreed before parts are linked. The loading of parts is planned in the IFS Cloud data migration plan, with a checklist in the data migration checklist.
5.How can combinations model a part lifecycle?
The page states that you could set up codes, for example, for experimental, obsolete or replacement parts. As an example for obsolete parts, it describes reducing the quantity of obsolete parts by allowing demand but no longer allowing supplies.
The page adds one effect outside the three columns: MRP and PMRP will consider the demands only when the On Hand Qty, Demand and Supplier parameters of the part are set to Onhand Allowed, Demands Allowed and Supplies Allowed respectively. Part numbering is a separate master data decision, covered in the IFS Cloud part numbering scheme, and the place of master data in a project is described in the IFS Cloud ERP implementation guide.
6.Which decisions belong to master data owners, sales and purchasing?
Three decisions need a named owner. The master data owner decides which status codes exist, because a created code cannot be modified. Sales and purchasing decide with the master data owner which phases of a part need a code, because Demands Allowed controls use as a sales part and Supplies Allowed controls purchase and receipt. The administrator, or an equivalent person, enters the codes, and the master data owner decides who may assign a status to a part on the Inventory Part page. A status is a separate setting from the availability control, which acts on stock records and is covered in part availability control settings.
7.How do you test the statuses before go-live?
Test each status with one part and the function it restricts, and write down the expected block or permission before each attempt.
| Scenario | Expected result | Owner |
|---|---|---|
| Part with inventory, change to a status with Onhand Not Allowed | Not possible while inventory exists | Master data owner |
| Part with a status without Demands Allowed, use as a sales part | Not allowed; the part must have Demands Allowed | Sales |
| Part with a status without Supplies Allowed, purchase and receive | Not possible; parts can be purchased and received only with Supplies Allowed | Purchasing |
| Modify the parameters of a created status | Not possible | Administrator |
| Remove a status code that has parts linked | Not possible | Administrator |
| Create a new inventory part | Status A, Active, is the default | Master data owner |
8.What does a part status checklist contain?
The part status set is ready for go-live when each check below has a record behind it.
- The status codes that exist are written down, with the setting of each of the three columns.
- Each code is agreed with sales and purchasing before parts are linked to it.
- Someone is named to assign statuses on the Inventory Part page.
- The use of status A, Active, as default for new inventory parts is accepted.
- The six test scenarios are recorded with evidence.
9.Frequently asked questions
What is a part status in IFS Cloud?
A part status in IFS Cloud describes the different phases of a part and controls the extent to which the part can be used by the system. Each status code has three settings: Quantity On Hand, Demand and Supplies.
Why can I not give a part with stock the status Onhand Not Allowed?
In IFS Cloud, if inventory still exists for a part, the part cannot have a part status of Onhand Not Allowed. The Quantity On Hand column indicates whether or not a part can have a quantity on hand.
What does Demands Allowed control?
Demands Allowed in an IFS Cloud part status indicates that demands are allowed for the part. An inventory part must have the setting Demands Allowed to be used as a sales part. MRP and PMRP consider the demands only when the part is set to Onhand Allowed, Demands Allowed and Supplies Allowed.
Can I change a part status record after it has been created?
Once a part status record is created in IFS Cloud, its parameters cannot be modified. If any parts are linked to a part status code, that code cannot be removed. The status of an individual part can be changed on the Inventory Part page.
What is the default part status for a new inventory part?
The default part status for a new inventory part in IFS Cloud is A, Active, which is installed by the system. Active allows Onhand, Demands and Supplies, and the code cannot be deleted or modified.
10.About the author
Dariusz Myśliwiec: 18 years hands-on with IFS, including IFS Cloud. Based in Kraków, delivering remotely across Europe and globally through an independent practice. You talk to the consultant who does the work, not a sales layer.
IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.
Are parts blocked and nobody knows which status does it?
A review of the status set against the part lifecycle your business uses shows which flags block which parts.
