Independent IFS Cloud practice · Warehouse planning design
IFS Cloud warehouse tasks are the units of work through which the floor receives picking and transport work when warehousing is used. If task types, workers and priorities are not designed, the next task a worker receives is not the one the business needs first. The order in which orders are picked and moved is then decided by set-up and not by a planner’s judgement. This article follows the documentation on the warehouse task and the page on managing warehouse tasks planning in the 25R2 tree.
Key takeaways
A warehouse task is a unit of warehouse work that a worker executes, created for a task type. The page lists six predefined warehouse task types:
The warehouse worker is connected to warehouse task types and location groups, so these are the two dimensions of what a worker can do. For a transport task the worker must be allowed to work on both the to and the from location groups and sites. The fact that tasks replace pick lists when warehousing is used is covered in warehouse data collection in IFS Cloud, and the location groups themselves in warehouse structure design.
A task has one of six statuses: Planned, Released, Started, Parked, Closed or Canceled. The Start In Status setting of the task type decides whether a task is created with an initial status of Planned or Released. A Planned task should never appear in the automatic selection of warehouse tasks for a worker, and a Released task is available to start. A task can be canceled if it has Planned, Released or Started status, and Parked means the task is temporarily on hold.
The task is ultimately assigned to a warehouse worker when it is set to Started status. Once it is Started or Closed, the task cannot be assigned to any other worker. A planner who wants to move work between workers has to do it before the task starts. It is also not possible to execute a warehouse task if stocks have been frozen for counting, which links task planning to cycle count variance reconciliation.
Priority on a warehouse task is a number valid from 1 to 99999, where the value 1 means the highest priority. The attribute is mandatory on the task type, and it is used as a default for priority on the warehouse tasks if priority is not sent from the task source.
A manager can overrule it. The manually set operative priority overrules the default priority, and only positive integers can be used to define operative priority, that is 1, 2, 3 and so on. If the same operative priority is set on more than one warehouse task, the default priority is still considered. The page does not describe the default priority as a tie-breaker, so test what order your configuration produces when two tasks share an operative priority.
The order in which a worker starts tasks depends on further factors. The priority that is set in Warehouse Task Type Setup also affects the order, and the finish date for the warehouse task decides in which order the tasks should be started. Together with the worker’s basic data, these are the inputs the page names.
The page gives three prerequisites regarding prioritisation. The task type must be Active in Warehouse Task Type Setup, which is a site setup and not a per-worker setting. The location group must be Active in Warehouse Worker/Location Group. And only warehouse tasks in the Released status can be selected.
The design consequence is that each prerequisite is a setting someone owns. A task type that is inactive for the site, a location group that is inactive for the worker, or a task left in Planned status leaves a prerequisite for prioritisation unmet, and a Planned task never appears in the automatic selection for a worker. Check these three settings first when the order of tasks is not what the planner expects. The packing and picking flows around these tasks are covered in advanced picking strategies in IFS Cloud and the packing proposal.
On the planning page the manager can prioritise the warehouse tasks by setting an operative priority in the Operative Priority column. If you select the Assigned option in the Assignment section, the Worker ID and Worker Group fields are enabled. To assign tasks to a worker group, select the tasks from the list items, open the list item context menu and select the Assign/Reassign Worker Group option; there is also an Assign/Reassign Worker option.
The same context menu changes status: select Plan, Release, Start, Complete, Park or Restart according to your requirement. The page therefore covers priority, assignment and status in one place. Decide who may use it and in which cases, because an operative priority set on one task changes the order of work for the worker who holds it.
To see the current workload and resource situation, the planning page points to the Workload per Location Group page or the Workload per Location Group Graph page. You select the Site, Task Type and Location Group that you want to see in the header.
The task types also carry time values. Each task type has a Default Time Needed, which represents the time needed to execute one line of the task type, and a Default Requested Lead Time, used as a default if no requested date finished is sent from the task source. The page gives an efficiency example: if the standard time is 2 minutes and the worker’s efficiency is 80 percent, the system calculates the expected time at 2.5 minutes. Follow-up calculations are not used automatically for new tasks but must be copied.
The 26R1 page on planning warehouse tasks adds that a planner can change the time that a worker spends on a specific task type and can change the requested date finished. It states that the system performs the correct prioritisation of the best possible task to start next for every worker, as long as the workload remains constant.
The warehouse manager owns four decisions: the default priority of each task type, which workers cover which task types and location groups, who may set an operative priority, and the time values used for workload. A default priority set by a project team and never reviewed is a decision nobody owns, and the floor works to it.
The related decision about when tasks are created as Planned and when as Released belongs with the same person, because it decides whether a task reaches a worker without a planner’s action. Receipt, which comes before put-away and picking, is covered in goods receipt, inspection and put-away in IFS Cloud.
Test the priority set-up with competing tasks and a worker who is set up for them, and write down the expected order before the test runs.
| Case | Set-up | Expected outcome | Owner |
|---|---|---|---|
| Operative priority | Two tasks, operative priority set manually on the second | The operative priority overrules the default priority | Warehouse planner |
| Equal operative priority | Two tasks with the same operative priority and different default priorities | The default priority is still considered; record the order you observe | Warehouse manager |
| Planned status | A task left in Planned status | It does not appear in the automatic selection for a worker | Warehouse planner |
| Inactive task type or location group | Task type inactive for the site, or location group inactive for the worker | A prerequisite for prioritisation is missing; record what the worker sees | Warehouse manager |
| Transport task | A worker allowed on the to group but not on the from group | The worker does not meet the page’s condition for the task | Warehouse manager |
A task planning design is ready for go-live when each of the checks below has a record behind it.
A warehouse task in IFS Cloud is a unit of warehouse work that is executed by a warehouse worker. The documentation lists six predefined task types: Customer Order Pick List, Transport Task, Shop Order Pick List, Shipment Order Pick List, Project Deliverables Pick List and Purchase Receipt Return Pick List. The worker is connected to task types and location groups.
Default priority is set on the warehouse task type, valid from 1 to 99999 with 1 as the highest, and is used when the task source sends no priority. Operative priority is set manually by a manager on the planning page and overrules the default priority. If the same operative priority is set on more than one task, the default priority is still considered.
For prioritisation in IFS Cloud, the warehouse task type must be Active in Warehouse Task Type Setup, the location group must be Active in Warehouse Worker/Location Group, and only warehouse tasks in the Released status can be selected. A task in Planned status should never appear in the automatic selection for a worker.
On the Manage Warehouse Tasks Planning page in IFS Cloud, the planner selects the tasks from the list items, opens the list item context menu and selects the Assign/Reassign Worker Group option. Selecting the Assigned option in the Assignment section enables the Worker ID and Worker Group fields. A task cannot be assigned to another worker once it is Started or Closed.
The planner uses the Workload per Location Group page or the Workload per Location Group Graph page in IFS Cloud. The Site, Task Type and Location Group to be shown are selected in the header of the page.
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.
A walk-through of task types, worker set-up and priority rules with the warehouse manager shows which rule decides the order today.
Book a task planning walk-through Read about warehouse data collection
Independent IFS Cloud practice · Inventory and finance design
IFS Cloud part ownership is, in the words of the IFS documentation, the identification of the type of ownership combined with an owner for a specific quantity of a part. Stock in the building is not always the company’s stock. If the ownership type is set wrongly, value is booked that does not belong to the company, or stock that the company owes is missing from the books. This article describes system behaviour as the page states it. Which accounting treatment applies is a decision for your finance function and your auditors.
Key takeaways
IFS Cloud lets you handle the same part number in inventory as company-owned stock, company rental asset stock, consignment stock, supplier-loaned stock, supplier-owned stock, supplier-rented stock and customer-owned stock. The table gives what the page says about the four types whose behaviour it describes in detail, and about the temporary supplier-owned type.
| Type | What the page says | Accounting effect on the page |
|---|---|---|
| Company owned | The default setting for a part’s ownership type | Accounting transactions are created for the inventory transactions, because the parts affect inventory value |
| Consignment | The company will eventually purchase the material, using an existing purchase order, when the stock is used or sold | Accounting transactions are created |
| Supplier loaned | On loan until the equivalent item that is being repaired by the supplier is returned | Accounting transactions are not created; zero inventory value |
| Customer owned | The material will be transformed (maintained, repaired, overhauled, or used as a component) and eventually returned to the customer | Accounting transactions are not created; zero inventory value |
| Supplier owned | A temporary ownership between the arrival and the receipt into stock, if the Ownership Transfer Point is set to Receipt into Inventory | See the section on postings below |
Company rental asset and supplier-rented stock are the two remaining types in the list. For them, read the page before you design, because this article does not describe their behaviour beyond the list itself.
Ownership is kept per quantity in an inventory location, and the page states that the same part can have different owners if they are kept in different inventory locations. The part ownership setting for a specific part in an inventory location applies only if the quantity of that part is greater than zero.
An inventory location cannot keep stock with different ownership types or owners for the same part. The page names a site option, Allow Multiple Owners for Inventory Part on One Location, which changes this when it is enabled. That option is a design decision, so decide it with the warehouse team and not by default. The location model is covered in warehouse structure design in IFS Cloud.
The page states that postings for the transactions are only created when they relate to company-owned or consignment parts. Stock of the other types does not create postings under that statement, and supplier-loaned and customer-owned stock additionally carry a zero inventory value.
This is the point at which finance and the warehouse have to agree. A consignment part creates accounting transactions, while a customer-owned part is physically in the building, creates none and carries a zero inventory value. Finance decides what that means for the books. The way business events become ledger entries is covered in posting control in IFS Cloud, and valuation in inventory valuation methods and cost levels. Neither is repeated here. Monitoring consignment stock that never reconciles is a separate topic.
Purchase order lines for order codes 1 and 5 (Normal and Express Order) allow you to specify all ownership types, and for supplier-loaned, supplier-rented and consignment stock the owner will be the supplier on the purchase order. The ownership and owner of the material received must match the part ownership on the purchase order line at the time of receipt, and the part ownership of the material cannot be changed at the time of receipt.
Purchase requisitions are narrower. All purchase requisitions allow only Company Owned and Company Rental Asset ownership types, except when created by a process that supports additional types. A buyer who needs consignment stock therefore sets the ownership on the order line, because a standard requisition does not allow it.
The design consequence is that the ownership decision happens at the purchase order line; ownership must match at receipt and cannot be changed there. The receipt itself is covered in goods receipt, inspection and put-away in IFS Cloud. Tracked parts add lot and serial numbers to the same step, as described in lot and serial tracking decisions in IFS Cloud.
Consignment stock is purchased and becomes company-owned stock when it is consumed, shipped or moved to a new location. You cannot move consignment stock via transit without transferring ownership. A transfer of ownership is initiated from the Inventory Part in Stock page, and the page lists transfers that are not allowed, among them consignment to any type of ownership other than company-owned.
Other functions limit which ownership they accept:
The shipment side of moving stock is described in shipment order in IFS Cloud.
Three groups each own a decision, and none can take the others’ decisions for them. Finance owns the accounting treatment of each type. Purchasing owns the ownership specified on the purchase order line, because the line is where ownership enters. The warehouse owns the location layout, including whether a location may hold more than one owner for the same part.
Opening stock needs its own decision: whether stock that is on a supplier’s consignment at go-live is loaded with an ownership type and owner, and how. The plan for that belongs in the IFS Cloud data migration plan and in the data migration checklist.
Test ownership with one scenario for each behaviour the page describes, and write down the expected value and postings before the scenario runs.
| Scenario | Expected result | Owner |
|---|---|---|
| Receive consignment stock against a purchase order line | Ownership and owner match the order line; postings are created | Buyer and finance |
| Consume consignment stock | The stock becomes company-owned | Warehouse lead and finance |
| Receive supplier-loaned stock | Zero inventory value and no accounting transactions | Finance |
| Receive customer-owned stock | Zero inventory value and no accounting transactions | Finance |
| Place two owners of one part in one location | Not possible unless the site option for multiple owners is enabled | Warehouse lead |
| Change ownership at receipt | Not possible; ownership must match the order line | Receiving clerk |
An ownership design is ready for go-live when each of the checks below has a document behind it.
Part ownership in IFS Cloud is the identification of the type of ownership combined with an owner for a specific quantity of a part. The IFS documentation lists seven types: company-owned, company rental asset, consignment, supplier-loaned, supplier-owned, supplier-rented and customer-owned stock.
Consignment stock in IFS Cloud is supplier stock that the company eventually purchases, using an existing purchase order, when the stock is used or sold, and accounting transactions are created for it. Supplier-loaned stock is on loan until the equivalent item being repaired by the supplier is returned, and the page states that no accounting transactions are created and the inventory value is zero.
No, according to the IFS Cloud documentation. Customer-owned stock is material that will be transformed (maintained, repaired, overhauled, or used as a component) and eventually returned to the customer. Accounting transactions are not created for it, and its inventory value is zero. Finance decides how the business treats this in its books.
Yes, if the stock is kept in different inventory locations. An IFS Cloud inventory location cannot keep stock with different ownership types or owners for the same part, unless the site option Allow Multiple Owners for Inventory Part on One Location is enabled. Ownership for a part in a location applies only while the quantity there is greater than zero.
Finance decides the accounting treatment of each ownership type in IFS Cloud, purchasing decides the ownership entered on the purchase order line, and the warehouse decides the location layout. The three decisions interact, because ownership set on an order line cannot be changed at receipt and postings are created only for company-owned and consignment stock.
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.
An ownership-model review with finance and the warehouse covers the types in use, how ownership is set on purchase order lines and what happens at receipt and use.
Independent IFS Cloud practice · Manufacturing and purchasing design
An IFS Cloud outside operation represents work performed by a supplier as part of a shop order routing. Production and purchasing therefore each own a piece of one flow. If the work center, the purchasing object and the reporting step are not designed together, material is shipped out and the system does not know where it is. The stake is work in progress outside the building that no record follows.
Key takeaways
An outside operation is a routing step on a shop order that a supplier performs instead of the company. The IFS documentation on outside operations describes the concept, and the page on work centers describes the work center that the operation uses. The operation is connected to an outside work center, which is a work center not owned by the company at which the manufacturing occurs.
The material sent to and received from the supplier is tracked by an outside operation item registered on the outside operation. The item is the thread through the whole flow, because it is the record that follows the material to and from the supplier. That is why it has to be designed with the work center and not afterwards. The shop order itself, with its statuses and blocks, is described in the shop order lifecycle in IFS Cloud.
When the outside operation or the shop order is released, IFS Cloud creates a purchase requisition or a purchase order for the outside operation item. The page on the purchase requisition describes the purchasing object the buyer works with.
The design consequence is about visibility. A production planner who releases a shop order has started work in the buyer’s area, and the buyer needs to know where to see it and what to do with it. Agree who sees the purchasing work, how quickly it is handled and who answers when the supplier is not yet agreed. The purchasing set-up that these records enter is described in mastering centralized purchasing in IFS Cloud, and the question of where supply comes from, for the alternative of buying instead of making, in IFS Cloud sourcing rules.
The outside operation supply type on the shop order operation decides what release creates for the outside operation item. The documentation lists three options, and each creates a different purchasing object for the buyer:
The decision belongs to purchasing and production together, because it determines who touches the supplier relationship first. Write the chosen option into the design record with its reason, and test each option that the business intends to use.
The WIP has to be reported as shipped to the supplier after the outside operation is released and before the purchase order arrival of the outside operation item can be reported. The sequence matters because the records have to show the events in the order in which they physically happened.
The Outside Operation Rpt Level controls how much of this reporting is automatic, and it has to be set before the operation is released. The three settings are Disallowed, Ship WIP to Supplier and Purchase Order Arrival. Where reporting is manual, name the person who reports the shipment and the moment they do it, for example when the goods leave the warehouse. Where it is automatic, test that the automatic step does not hide a shipment that never physically left.
When the outside operation is the last operation on the shop order, the shop order can be received with the arrived outside operation purchase order line, provided the Receive into Inventory on Last Operation option is enabled on the outside work center. The page on receiving a shop order describes the function, including receipt of a shop order with the arrived outside operation purchase order line.
Cost and accounting follow the receipt. How the cost of subcontracted work enters the part’s value is described in inventory valuation methods and cost levels in IFS Cloud, and the accounting entries that the events create in posting control in IFS Cloud. Neither is repeated here.
Six decisions cross the line between purchasing and production and need both in the room: the work center set-up, the item that carries the material, the supplier, the lead time, the cost, and the person who reports shipment. A decision taken by one side alone leaves the other side with a record it did not design.
The work center and the item belong to the master data owner of manufacturing. The supplier, the lead time and the cost belong to purchasing, which also holds the commercial agreement. The reporting person belongs to whoever physically ships the material. Ownership of the flow as a whole is a separate decision: name one role who answers when the material is somewhere and the system says otherwise. Configure-to-order purchasing is a neighbouring topic, covered in the article on CTO purchasing.
Test the subcontract flow with one scenario per step, run with purchasing and production together, and repeat the table for each supply type option that the business will use.
| Step | What to do | Expected record | Owner |
|---|---|---|---|
| Release | Release a shop order that contains an outside operation | Purchasing work created for the supplier operation, visible to the buyer | Production planner and buyer |
| Shipment | Report the material as shipped to the supplier | Material recorded as out of the building against the operation | Warehouse lead |
| Arrival | Report arrival from the supplier | Arrival accepted only after the WIP shipment to the supplier is reported | Receiving clerk |
| Finished part | Receive the shop order, at purchase order arrival where the outside operation is the last one | Finished part in the intended location | Production lead |
| Cost and posting | Compare the cost and the ledger entry with the expectation | Cost of the subcontracted work in the part value, with its entry | Finance and purchasing |
A subcontracting design is ready for go-live when each of the checks below has a record behind it.
An outside operation in IFS Cloud represents work performed by a supplier as a step of a shop order routing. It is connected to an outside work center, a work center not owned by the company at which the manufacturing occurs, and the material sent to and received from the supplier is tracked by an outside operation item registered on the operation.
When the outside operation or the shop order is released in IFS Cloud, a purchase requisition or a purchase order is created for the outside operation item. The outside operation supply type on the shop order operation decides which: Purchase Requisition, Planned Purchase Order or Released Purchase Order.
In IFS Cloud, the WIP is reported as shipped to the supplier before the purchase order arrival of the outside operation item can be reported. The Outside Operation Rpt Level, set before the operation is released, decides whether these steps are reported automatically, with the options Disallowed, Ship WIP to Supplier and Purchase Order Arrival. Where reporting is manual, name the person who reports the shipment.
The finished part is received through the Receive Shop Order function in IFS Cloud. When the outside operation is the last operation on the shop order, the shop order can be received with the arrived outside operation purchase order line, provided the Receive into Inventory on Last Operation option is enabled on the outside work center.
Name one role that owns the subcontract flow as a whole in IFS Cloud, with purchasing owning the supplier, lead time and cost, and production owning the work center, the material item and the shipment report. The owning role answers when the material is at the supplier and the system says otherwise.
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.
A subcontracting flow review follows one shop order from release to receipt and cost, with purchasing and production in the room. It shows where the record stops following the material.
Book a subcontracting flow review Read about the shop order lifecycle
Independent IFS Cloud practice · Part master data design
IFS Cloud lot tracking and serial tracking are part settings, and each tracked part asks for a lot or serial number at every receipt, issue and move that the setting covers. Tracking switched on because it might be needed burdens the floor with entries nobody reads. Tracking switched off where it is demanded leaves no way to trace a part when a customer or an auditor asks. The trade is operator effort on every transaction against the ability to trace when required, and it is settled part by part.
Key takeaways
Tracking a part means that IFS Cloud records an identity below the part number, a lot or a serial, for the stock of that part. The documentation on lot and batch tracking and the page on enabling serial tracking for a part describe the two forms.
A lot number identifies a lot of one part. IFS Cloud pairs lot numbers with part numbers, so two different parts can carry the same lot number and the system still treats them as two separate lots. A serial number identifies a single unit. A third form, tracking through a structure, is described on the shop order tracked structure page: before a parent serial or lot number is received from a shop order, its tracked structure must be complete.
Decide per part by asking who needs the trace, for which event and how far back. The answers come from the owner of the requirement: quality, a customer contract or a regulator. The owner names the demand, and the consultant does not assume it.
A part where nobody can name the event stays untracked. That keeps the floor’s effort on the parts where a trace has a user. The questions are the same for a purchased part, a made part and a returned part; for returns see RMA and customer returns in IFS Cloud.
Serial tracking is set on the part with two options, Serial Tracking At Receipt and Issue and Serial Tracking In Inventory, and the page lists the allowed combinations together with a third option, Serial Tracking After Delivery. With both options enabled, the part has full serial tracking. With At Receipt and Issue alone, the part is serial tracked at receipt and issue only. In Inventory without At Receipt and Issue is not allowed. The difference matters for the floor: the narrower form asks for the serial number when the part enters or leaves, while the wider form keeps the serial identity in stock between those events.
A part that is serial tracked may also be lot tracked, but it may not use order-based lot tracking, as the page on enabling serial tracking states. Decide the combination per part group, then record it in the matrix at the end of this article.
Tracking adds a number to each of these steps, and each number needs a source. For a lot-tracked part, the lot number is entered at arrival registration or later in the receipt function, and for an order-based part it is generated at arrival registration, as the documentation on arrival and receipt describes. Where the number is entered, decide whether it comes from the supplier’s label or from a number the company assigns. The receipt statuses themselves are covered in goods receipt, inspection and put-away in IFS Cloud.
For production, lot numbers can be generated. Decide the numbering convention before the first shop order is released, so that a lot number reads the same in every order. The page on generating lot numbers for a shop order describes the function.
For shipping, handling units interact with tracking. The documentation on handling units describes how packing works, and a test with tracked parts shows whether your packing routine keeps the trace intact. The location model that holds the tracked stock is covered in warehouse structure design in IFS Cloud.
The tracking decision is cheap to take before stock exists and needs care afterwards. Before changing the setting on a part, check the part and its stock: stock that already sits in locations was received under the old setting, so someone has to decide what identity that stock receives under the new one.
Serial tracking also interacts with costing. The interaction is described in inventory valuation methods and cost levels in IFS Cloud, which is the place to read it, and this article does not repeat it. Part numbering is a neighbouring decision: the part numbering scheme sets the identity that lots and serials sit under.
Tracking is loaded by deciding the setting for every part before its stock is loaded, because stock of a tracked part needs the lot or serial numbers that the setting expects. Agree the source of those numbers for opening stock: the old system, a physical count or a label on the item.
The planning of the load is covered in the IFS Cloud data migration plan, and the extract and load checks in the data migration checklist.
A tracking decision matrix has one row per part group, and each row records the trace requirement, the level of tracking and the owner. The rows below are illustrative, not a client record.
| Part group | Trace requirement | Level | Owner |
|---|---|---|---|
| Part with a customer recall obligation | From shipped unit back to supplier lot | Lot tracking, numbers assigned at receipt | Quality manager |
| Part with a warranty tied to the unit | Identify the single unit | Serial tracking | Service manager |
| Part with no named trace event | None named by an owner | Not tracked | Inventory lead |
Lot tracking in IFS Cloud identifies a lot of one part, and the system pairs the lot number with the part number. Serial tracking identifies a single unit of a part. With both Serial Tracking At Receipt and Issue and Serial Tracking In Inventory enabled, the part has full serial tracking; In Inventory alone is not allowed.
Yes, a serial-tracked part can also be lot-tracked in IFS Cloud, but not with order-based lot tracking. The page on enabling serial tracking lists the restriction.
Check the part and its stock before changing a tracking setting in IFS Cloud. Stock that already sits in locations needs a decision on what lot or serial identity it receives under the new setting, and the decision belongs to the owner of the trace requirement.
Lot numbers for production in IFS Cloud can be generated for a shop order; the IFS documentation has a page on generating lot or batch numbers for a shop order. Decide the numbering convention up front, so that a lot number tells a reader the same thing in every order.
Handling units in IFS Cloud interact with lot and serial tracking when tracked parts are packed. The IFS documentation on handling units describes how packing works, and a packing test with tracked parts in your own configuration shows whether your packing routine keeps the trace intact.
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.
Either answer points to a part-by-part decision that was never made. A tracking review with the quality, warehouse and finance owners in the room sorts the part groups and records the level for each.
Independent IFS Cloud practice · Warehouse design
The IFS Cloud warehouse structure is the hierarchy of warehouse, bay, row, tier and bin that defines where stock can be stored, and it is decided once, before the first part is put away. That decision shapes every pick, count and move for years. A model that is too coarse sends the operator walking the floor to find stock. A model that is too fine turns each transaction into a chore, and the effort is paid on every transaction, every day.
Key takeaways
An inventory location in IFS Cloud sits in a hierarchy: a site contains warehouses, and a warehouse contains bays, rows, tiers and bins. The IFS documentation on inventory locations and warehouse structure describes the levels and how an inventory location maps to the bin. The table gives the physical meaning of each level.
| Level | What it usually stands for on the floor |
|---|---|
| Site | An operational location, such as a plant or distribution centre, belonging to a company |
| Warehouse | A building, a hall or a separate storage area with one set of rules |
| Bay | A section of racking or floor, often an aisle or a block of racks |
| Row | A line of positions within a bay |
| Tier | A vertical level, from floor to the highest shelf |
| Bin | The smallest addressable position, where stock is counted and moved |
The page on entering inventory locations describes how a location is created. The team decides how many levels it actually uses on the floor: a warehouse can be modelled as one open area or down to the individual shelf.
The location model should be as fine as the operator needs in order to find stock without asking anyone, and no finer. Two failures mark the ends of the scale.
The method to find the right level has four steps:
Fast-moving parts and slow-moving parts are not equal here. The pallet in the corner shows what slow stock does to prime picking space, which is a layout question as much as a master-data one. The receipt side of a poor model, where goods arrive and cannot be placed, is covered in goods receipt, inspection and put-away in IFS Cloud.
Route order sets the sequence in which locations are visited; check its default and where it is maintained in your release before you rely on it. A pick list built on route order follows that sequence, so the picker’s path is only as good as the order of the IDs.
The order hurts when IDs were chosen for another reason: the order in which racks were bought, a number from the old system, or a label that makes sense to the person who typed it. The sequence then no longer matches the way a picker walks, and every pick list zigzags across the floor. The cure is to decide the walking order first, name or number the levels to match, and correct the route order where the floor has an exception such as a one-way aisle.
Shop order pick lists can be grouped by warehouse, bay, row, tier or bin, as the IFS documentation on shop order pick lists describes. The level you model therefore also decides how pick lists can be split between pickers. The setup of picking strategies themselves is a separate topic.
A put-away rule set at a higher level of the structure applies to the levels below it, and a lower level can override it. The IFS documentation on inventory put-away describes this inheritance. A rule defined on a bay therefore covers its rows, tiers and bins, and one bin in that bay can have its own rule.
The design consequence is to set the general rule high and exceptions low. A rule repeated on every bin is hard to change, and a rule scattered at random levels is hard to read. When the structure is built, copying a bin layout saves typing for repeated rows, and it also repeats any mistake in the original, so check the first row before you copy it.
What stagnant stock costs once it is stored is the subject of the anatomy of stock aging.
Four decisions come before locations are loaded, because a loaded location is hard to rename once stock sits in it.
Counting depends on the same decisions. A count schedule works on the locations you define, so a model that groups unlike stock together produces variances that are hard to trace, as described in cycle count variance reconciliation. A multi-site layout adds its own question of which warehouses belong to which site, treated in site cluster functionality.
Test the location model with the operators who will use it daily, on a mock-up of the real floor, before the data is migrated. Give a picker a pick list and ask them to walk it on a floor plan. Give a receiving clerk three deliveries and ask where each goes. A stock controller gets a count list and says whether it matches the way the shelves are laid out.
Each point at which the operator asks “where is that?” is a defect in the model, not in the person. Record it in the test log, adjust the structure, and repeat. Posting consequences of these movements are a finance topic; see posting control in IFS Cloud for how location and transaction design feeds the ledger.
A location model is ready for migration when each of these checks has evidence.
| Check | Evidence |
|---|---|
| Level of detail agreed per warehouse | A walked floor plan with the touch count, signed off by the warehouse lead |
| Naming convention written down | One page with three example locations |
| Route order matches the walking order | A pick list walked on the floor plan without backtracking |
| Put-away rules set high, exceptions low | A list of rules with the level at which each one is defined |
| Location groups defined | Each group has a purpose and a rule owner |
| Stable names identified | A list of levels referenced by labels, scanners or other systems |
| Model tested by operators | Test log with every “where is that?” question and its fix |
The warehouse team decides how many levels it actually uses on the floor. A warehouse in IFS Cloud can be modelled as one open area or down to the individual bin, so the level of detail is a design decision, taken by walking the floor.
Route order in IFS Cloud is the sequence in which warehouse locations are visited when stock is picked. Check its default and where it is maintained in your release before you rely on it. Setting it to match the physical walking order keeps pick paths short.
A put-away rule defined on a bay in IFS Cloud applies to the rows, tiers and bins below it. A lower level can carry its own rule that overrides the one inherited from above. The practical pattern is a general rule at bay level and exceptions at bin level.
A shelf deserves its own location in IFS Cloud when the operator would otherwise search for the stock on it. Decide by walking the floor: if the extra detail removes a search, keep it, and if it only adds a scan, merge the shelves into one bin. The answer differs between a fast-moving picking zone and a bulk store.
A restructuring of the warehouse in IFS Cloud after go-live needs a plan, above all where it touches locations that hold stock. Before you change anything, test the change in a non-production environment with a copy of real stock, check the IFS documentation on inventory locations for the location you are changing, and agree a stock count before and after the move.
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.
If the model came from go-live and the floor has learned to ignore parts of it, a review from the floor shows which levels to merge, rename or reorder. The warehouse team sits in the room.
Book a location-model review Read about goods receipt and put-away
Independent IFS Cloud practice · Finance and supply chain design
IFS Cloud posting control is the set of rules that turns a business event, such as a goods receipt or a delivery, into a financial transaction with accounts and code parts. It sits between operations and finance, and it belongs to both functions, so neither designs it alone. The gap shows up at month-end as an inventory value that does not tie to the ledger and as variances nobody owns, and the argument that follows starts at the ledger and ends on the shop floor.
This article describes system behaviour as the IFS Cloud documentation presents it. It gives no accounting advice. Which accounts a transaction hits is a decision for your finance function and your auditors.
Key takeaways
Posting control in IFS Cloud decides which accounting entries a business event creates. When a warehouse operator receives goods against a purchase order, issues material to a shop order or delivers against a customer order, the system creates a financial transaction through a posting type and its control types. The IFS documentation on posting control for supply chain and manufacturing lists the posting types used for these events.
Operations cares because the operator’s transaction is the trigger. A receipt booked against the wrong order, a delivery confirmed late or an adjustment entered for convenience each produce a ledger entry, whether or not the operator knows it. A warehouse team that understands which events post, and why, makes fewer corrections. The warehouse side of the same question, the location and transaction design that feeds these rules, is covered in warehouse structure design in IFS Cloud.
A posting type describes the debit and credit postings for one kind of event, and a control type supplies the data that decides the value of a code part in the account string. The documentation on posting types and system events describes how these are defined.
| Piece | Role |
|---|---|
| System event | The business event that triggers a posting, for example a receipt or a delivery |
| Posting type | The debit and credit postings created for that event |
| Control type | The data, such as a part, a site or a supplier attribute, that decides the value of a code part |
| Code part | One element of the account string, for example account or cost centre |
Each posting rule therefore answers one question: for this event, and for this kind of part or order, which value goes into each code part? Operations supplies the facts that the control types read, such as a part attribute. Finance supplies the accounts. If either side changes its data without telling the other, the postings change silently.
Preposting lets a user assign accounting values to a document line, for example on a purchase order or a purchase requisition, before the transaction posts. The IFS documentation has separate pages on entering preposting on a purchase order and on a purchase requisition.
The design question for the session is which documents use preposting and who may enter it. A buyer who enters account values on a requisition is making an accounting decision, so finance should know that this happens. Where it does not happen, the posting rules from section 2 carry the full load. Write the answer for each document type in the session record and do not leave it to habit.
Finance and operations should walk through every supply chain event that moves stock or value, one event at a time, with the standard posting types from the IFS documentation in front of them. Do not invent codes. Take the posting type from the documentation page and confirm it in your own environment.
| Event | What operations records | What finance must confirm |
|---|---|---|
| Receipt against a purchase order | Quantity, part and location at goods receipt | The entry created at receipt and its link to the later supplier invoice |
| Issue to a shop order | Material issued to the order | The entry that moves value from stock to the order |
| Delivery against a customer order | Quantity delivered and delivery date | The entry created at delivery and its link to the later customer invoice |
| Transfer between locations or sites | From and to location, quantity | Whether the move creates an entry at all, and in which company |
| Adjustment after a count | Counted quantity and reason | The account that carries the difference |
Costing is a separate subject. How a part is valued is described in inventory valuation methods and cost levels in IFS Cloud, and the gap between a delivery and its invoice is covered in delivered but not invoiced.
Test posting control by following one transaction per event from the stock record to the ledger entry. Each side has a named owner: the operator or key user who made the transaction, and the finance person who reads the entry.
The method for planning and tracking such tests is covered in testing in IFS Cloud, and the UAT test tracker template lists posting control as a test item. This article does not repeat that method.
When nobody owns posting control, two things happen at the first close. The inventory value in the stock module does not tie to the ledger, and nobody can say which event created the difference. Each side then reconciles from its own end: finance from the ledger, operations from the stock records, and the meeting ends without an owner for the variance.
The result is a recurring monthly discussion instead of a one-time fix. The cure is the table from section 4, kept as a controlled document with a named owner for each row and a review date after the first period-end close. The consequences of a late discovery at close are described in the month-end catch that comes too late.
A design session with finance and operations in the room covers six items:
The output is the table with four columns: event, expected entry, owner and test evidence. It goes into the project record next to the other decisions, as described in the IFS Cloud ERP implementation guide.
Posting control in IFS Cloud is the set of rules that turns a business event, such as a goods receipt or a customer delivery, into a financial transaction. The rules work through posting types, which define the debit and credit postings, and control types, which supply the data that decides each code part. The accounting decisions in these rules belong to finance.
A posting type in IFS Cloud describes the debit and credit postings created for one kind of event. A control type supplies the data, such as a part or site attribute, that decides the value of a single code part in the account string.
Preposting in IFS Cloud lets a user assign accounting values to a document line, such as a purchase order line or a purchase requisition line, before the transaction posts. Which documents use preposting, and who may enter it, is a design decision to record in the posting control session, because entering account values is an accounting action.
Finance should own the posting control rules in IFS Cloud, because the rules decide which accounts a transaction hits. Operations owns the events that trigger them and the master data, such as part attributes, that the control types read. Each row of the design table needs one named owner on each side.
Follow one stock movement in IFS Cloud from the stock transaction to its ledger entry and compare the entry with what finance wrote down in advance. Do this for one real transaction per event, such as a receipt, an issue, a delivery, a transfer and an adjustment. Every difference between the entry and the expectation is a defect with an owner.
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.
If it does not, or nobody can say why, a facilitated design session with finance and operations produces the first version of the event table. A review of your current setup against the documented events works the same way.
Book a posting control session Read about inventory valuation
Independent IFS Cloud practice · Business process optimisation
A shop order in IFS Cloud moves through statuses that the system sets itself, and each step from release to closing has documented conditions. The article follows the IFS Cloud documentation (25R2, Close Shop Order also compared in 26R1) and marks my own reading as such. It gives no accounting advice.
Key takeaways
The shop order lifecycle in IFS Cloud is the sequence of statuses and actions that takes a manufacturing order from planning to completion. The Manufacturing Shop Order page defines the statuses, and its wording is used throughout.
| Status | Definition on the page |
|---|---|
| Planned | A low-status order for a part you have planned but not yet decided to manufacture. You cannot reserve material or report operations. |
| Parked | An order that has been blocked and cannot or should not be processed further until the cause has been resolved. Unparking sets the status back to what it was before. |
| Released | An order released for production. |
| Reserved | At least one reserved material line, but no issued material or reported operations. |
| Started | Issued material and/or reported operations. |
| Closed | A completed order. No additional quantity can be reported or received unless it is re-opened. |
| Cancelled | An order that cannot be processed further and cannot be re-opened. |
A new order starts as Planned or Released, depending on a setting on the Site/Manufacturing page. The steps then run as follows.
Shop orders in IFS Cloud stall when a documented condition of the next step is not met, and the IFS Cloud 25R2 pages name those conditions step by step.
| Step | Condition or block the page names |
|---|---|
| Release | Status must be Planned. With the Automatic Availability Check on, the check uses the Expected Lead Time of the part and the Availability Check option in Supply and Demand Controls on the Inventory Part page. |
| Reservation | Insufficient unreserved stock. Serial numbers that are VIM, equipment or plant design objects. Outside Reserve/Backflush set to Not Allowed. |
| Issue | Status must be at least Released. Tracked parts must be reserved before automatic issue. Location hierarchy settings stop backflush. |
| Operation reporting | A Planned order cannot have operations reported. A Parked order puts its operation lines in Parked. |
| Receipt | At least one material line must exist. Serial and lot/batch numbers to receive must be reserved for the order. Without Simplified Material Check, the system verifies that enough material was issued for all lines except those with Reserve/Issue Method Manual. |
| Closing | A manual peg must be removed first. Close Operations sets the operations to Closed when the order closes. |
The 26R1 version of Close Shop Order adds a condition that the 25R2 version does not have. If WIP products received from the order are still in stock, the order cannot close unless Issue Remaining WIP Products is enabled, and the 26R1 page lists as effects that WIP products in stock are issued automatically and SOWIPISS transactions are created.
Closing also carries a cost consequence. The Cascade Update of Cost on Inventory Transactions page says the cost calculation uses an estimated cost structure at shop order receipt, updated when the order is closed. In my reading, a receipt that sits long before closing therefore carries an estimated cost for that long. In its performance section on transaction-based actual costing, the same page names the time span between receipt and cost update as a critical factor in how many transactions are affected, and for manufactured parts it gives that span as the time between shop order receipts until the shop order is finally closed.
The pages I read do not state how operation statuses roll up to the shop order status, or whether all operations must be Closed before the order closes. The Shop Order Operation page lists Planned, Released, Setup Started, Setup Complete, In Process, Partially Reported, Interruption and Closed. That list does not name Parked, although the Park Shop Order page sets operation lines to Parked.
Stalled shop orders are found by reading each status definition as a filter and asking what the order should have done by now. The pages I read do not describe a stalled-order report, so what follows is my reading of the status definitions.
| Symptom | What it suggests, in my reading |
|---|---|
| Planned, demand approaching | No decision to manufacture, or a release prerequisite from section 2 is missing. |
| Released, no reservation or issue | A short component, a location rule or a missing reservation on a tracked part. |
| Reserved, nothing issued or reported | Material is allocated and nobody has started. |
| Started, with all quantity received | Finished parts are in inventory, yet the order stays open. Check Close Code, Close Tolerance, open operations and issued material. |
For the cost side, the Transaction Revaluation Events form lists the object that triggered each cascade, execution times, the involved user and the number of inventory transactions updated. The article on read-only OData monitoring describes a check that changes nothing in IFS.
An unblocking action is chosen by the step where the order sits, using the condition that step documents.
The pages I read do not state a procedure for re-opening a closed order. The Manufacturing Shop Order page says a closed order takes no more quantity unless it is re-opened. For the valuation background, see inventory valuation methods and cost levels in IFS Cloud.
Shop orders keep moving when each step has a named owner and an age limit that someone watches. What follows is the author's practice, not an IFS procedure.
Related: sales order without coverage and the anatomy of stock aging. Primary sources (25R2): Manufacturing Shop Order, Close Shop Order and Cascade Update of Cost on Inventory Transactions.
The Manufacturing Shop Order page lists Planned, Parked, Released, Reserved, Started, Closed and Cancelled. The system sets the status automatically in response to actions, and users cannot change it manually.
Reservation needs the order at Released status or higher. Insufficient unreserved stock, serials that are VIM, equipment or plant design objects, and Outside Reserve/Backflush set to Not Allowed also stop the reservation.
Close Shop Order lists three ways: Auto Close once received quantity meets the Close Tolerance, receipt with Force Shop Order Closure enabled, or manually through Status and then Close.
For a manufactured part on weighted average with any cost level, or on standard cost with the per-serial cost level, closing uses the total work in process to update the receipt transactions, and the change cascades to later transactions. Other valuation methods are not revalued on closing.
Dariusz Myśliwiec brings 18 years of hands-on work with IFS (Apps 7.5–10 and IFS Cloud). IFS Certified Associate Consultant. PRINCE2® 7. Based in Kraków, delivering remotely across Europe and globally as an independent practice, so you talk to the consultant who builds it.
Selected clients: Fugro · LGC · BVI Medical · Betafence (PRÆSIDIAD) · Barlinek · NGK Ceramics · Newag · Oleofarm.
IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.
Tell me which status holds your oldest orders, and we will walk the steps from release to closing on a 30-minute fit call.
Independent IFS Cloud practice · Business process optimisation
Each inventory part in IFS Cloud carries a valuation method and a cost level, and that pair shapes how receipts and issues move the value of stock. This article follows the choices as the IFS Cloud documentation (releases 25R2 and 26R1) describes them. It describes system behaviour and gives no accounting advice.
Key takeaways
The valuation decision in IFS Cloud assigns a financial value to on-hand inventory through a valuation method combined with a cost level. The Inventory Valuation Methods and Cost Levels page states that the choice follows a legal or third-party requirement, or an operational measure useful for analysing inventory levels. Which one applies to you is a question for your finance team and auditors.
| Cost level | Standard cost | Weighted average | FIFO | LIFO |
|---|---|---|---|---|
| Cost per Part | X | X | X | X |
| Cost per Configuration | X | X | - | - |
| Cost per Condition | X | X | - | - |
| Cost per Lot Batch | X | X | - | - |
| Cost per Serial | X | - | - | - |
Cost per Serial sets the method to standard cost automatically, for technical reasons, the page says. In my reading each serial then has a unique value.
The same page describes the methods.
Receipt cost comes from the purchase order price, the WIP built up on the shop order, or a manually defined cost for stock received without an order. For Cost per Condition and Cost per Lot Batch, the first receipt sets the cost, and it resets once all parts of that condition code or lot batch number have been issued.
Stock value in IFS Cloud changes after receipt because several documented mechanisms revalue stock or transactions already booked.
The posting types page lists receipts, issues, returns and scrapping as separate system events.
| Movement | System event as named on the page | What the pages I read say about cost |
|---|---|---|
| Receipt of a purchase order | ARRIVAL "Receipt of Purchase Order" | Cost comes from the purchase order price. A new receipt recalculates the weighted average. |
| Issue | NISS "Issue from Inventory" | Weighted average issues use the weighted average value. A cascade gives them a variance. In the cascade update, an un-issue takes the value of its original transaction. |
| Customer return | OERETURN "Receipt of Returned Material into Inventory" | In the cascade update, RMAs are not considered new receipts. |
| Scrapping | INVSCRAP "Scrapping in Inventory" | Not stated on the pages I read. |
The pages I read do not state which cost a return or a scrapping takes under each method, and they describe no reconciliation between inventory value and the ledger. Test them on a sample part.
Two inventory values are checked by identifying the source of each figure and comparing them for one site and one point in time.
| Where to look | What the page says it gives you |
|---|---|
| Part setup | Method, cost level and Supplier Invoice Consideration decide which mechanisms in section 2 apply. |
| Transaction Revaluation Events | Trigger object, execution times, involved user and number of transactions updated. |
| Inventory Value Check Report | Two calculations compared, from transactions and from cost multiplied by quantity. Parts above the Diff Tolerance Amount are listed. |
| Inventory transaction history | Transactions of a period: issues, receipts, scrapping. |
| Posting types and system events | Debit and credit posting types per system event. |
The Inventory Value Check Report, a command on the Inventory Value per Period page, changes no data. It has prerequisites: statistic periods defined on the Statistic Periods page, transactions aggregated first (otherwise the report might show incomplete data), and a run directly after the inventory part statistics update (new transactions in the meantime can cause differences). In my reading, a ledger gap also needs the posting types and transfer timing checked. Cycle count variance reconciliation covers the quantity side.
A change of method, cost level or cost follows the rules the Inventory Valuation Methods and Cost Levels page documents.
The pages I read do not state how a method change affects earlier transactions, so test the sequence of change, receipt, issue and check on a sample part. Related reading: goods receipt, inspection and put-away and RMA and customer returns.
A valuation decision holds up when it is made per part group with a named owner and a calendar. What follows is the author's practice, not an IFS procedure.
In my reading, stock that ages without moving also carries a value worth watching. See the anatomy of stock aging. Primary sources (25R2): Inventory Valuation Methods and Cost Levels, Cascade Update of Cost on Inventory Transactions and Periodic Weighted Average.
The documentation lists standard cost, weighted average cost, FIFO and LIFO, combined with five cost levels. FIFO and LIFO are documented at Cost per Part level.
A change of method or cost level is allowed when the part has no on-hand quantity and no customer consignment quantity. For a switch between standard cost and weighted average, the page says it is "always allowed, provided that you are using the same cost level".
For a part with Supplier Invoice Consideration set to Transaction, a matched invoice updates the cost on the purchase order receipt and the change cascades to later transactions. This works for standard cost with Cost per Serial, or for weighted average at any cost level. The Transaction Revaluation Events form lists the trigger.
The Inventory Value Check Report compares a transaction-based value with cost multiplied by quantity and lists parts above the Diff Tolerance Amount. The pages I read describe no reconciliation against the ledger.
Dariusz Myśliwiec brings 18 years of hands-on work with IFS (Apps 7.5–10 and IFS Cloud). IFS Certified Associate Consultant. PRINCE2® 7. Based in Kraków, delivering remotely across Europe and globally as an independent practice, so you talk to the consultant who builds it.
Selected clients: Fugro · LGC · BVI Medical · Betafence (PRÆSIDIAD) · Barlinek · NGK Ceramics · Newag · Oleofarm.
IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.
Tell me which parts show the biggest gap. On a 30-minute fit call we can look at the method and cost level per part group and who owns each cost change.