Skip to main contentSkip to footer

IFS Cloud Implementation Rescue: Diagnose, Decide, Recover

IFS Cloud implementation rescue for stalled projects: a diagnostic, a keep, repair or rebuild decision per area, and a dated recovery plan.

IFS Cloud implementation rescue · Independent IFS Cloud practice A stalled IFS Cloud project needs a diagnosis, a decision per area and dated gates The go-live…

Read more

IFS Cloud Reporting Tools: Quick Reports to Lobbies

IFS Cloud reporting tools in six layers: Quick Reports, Business Reporter, Lobbies, Power BI, Analysis Models and OData, and when to use each.

Independent IFS Cloud practice · Reporting From the weekly Excel export to a Lobby your team opens first Key takeaways IFS Cloud reporting tools fall into six…

Read more

Purchase Order Received but Not Closed in IFS Cloud

A purchase order line received in full can stay open in IFS Cloud. It lingers on open-PO reports and clutters them until someone closes it.

Independent IFS Cloud practice · Procurement The purchase order you received, and the line that never closed The goods arrived, the receipt matched, and every…

Read more

Purchase Order Short Receipt Left Open in IFS Cloud

Part of a purchase order arrives and the line stays open in IFS Cloud. An open remainder can keep counting as supply that is not coming.

Independent IFS Cloud practice · Procurement The purchase order that arrived half full and stayed open You ordered a hundred. Sixty arrived, the receipt was…

Read more

Purchase Order Over-Receipt in IFS Cloud

Goods can arrive in excess of the purchase order in IFS Cloud and pass inside a wide tolerance. How to list over-receipts before you pay for them.

Independent IFS Cloud practice · Procurement The delivery that brought more than you ordered, and nobody stopped it You ordered a hundred. A hundred and twenty…

Read more

Purchase Orders Priced Off Contract in IFS Cloud

A purchase order can be placed at a price the active agreement never authorised. The gap may surface only on the invoice. How to list it in IFS Cloud.

Independent IFS Cloud practice · Procurement The price you negotiated, and the order that ignored it There is an active blanket agreement on the part. Someone…

Read more

Purchase Order Currency Mismatch in IFS Cloud

A purchase order can carry a currency or rate that differs from the supplier default, so landed cost is off in IFS Cloud before the goods arrive.

Independent IFS Cloud practice · Procurement The order looked right in one currency, and cost the wrong number in another A purchase order in IFS Cloud carries…

Read more

Purchase Order Confirmation Mismatch in IFS Cloud

A supplier can confirm a purchase order at another quantity, price or date and the line still reads confirmed. How to list those gaps in IFS Cloud.

Independent IFS Cloud practice · Procurement The order you placed, and the confirmation that quietly changed it You raise a purchase order for a batch of…

Read more

Open Backorders After a Partial Delivery in IFS Cloud

A partial delivery ships and the rest is backordered in IFS Cloud. The open line can age with no new promised date until the customer asks.

Independent IFS Cloud practice · Sales The half that shipped, and the half nobody chased A customer orders ten and six are in stock, so six go out. The order…

Read more
Abstract illustration on a navy background with the article title: “Distribution orders between sites in IFS Cloud”

IFS Cloud supply chain · Independent IFS Cloud practice

Move stock between sites with a customer order and a purchase order behind it

Distribution orders in IFS Cloud move inventory parts from a supply site to a demand site. On release, each one creates a customer order line on the supply site and a purchase order line on the demand site. Use it when the move is internal trade, including between sites of different companies; use a shipment order when the move stays inside one company and needs no trade documents.

Key takeaways

  • The demand site must be set up as an internal customer and the supply site as an internal supplier before a distribution order can use them.
  • Release decides the commitment: a released distribution order cannot be deleted, only changed manually or cancelled, so the release point is a planning decision owned by the coordinator.
  • Planned distribution orders are entered manually or created automatically by eight processes, MRP and Distribution Allocations among them.
  • A distribution order goes to Stopped when its purchase order line or customer order line cannot be released, for example because of a purchase authorization rule or a credit limit on the internal customer that the customer order exceeded.
  • Automatic receipt books the goods into the demand site at the moment of delivery from the supply site, which suits short moves and misleads planners on long ones.

IFS Cloud has three ways to move stock between locations, and choosing the wrong one shows up later as master data nobody wanted or stock that is in no warehouse. A transport task moves stock inside one site. A shipment order moves goods between sites and remote warehouses of one company, as described in IFS Cloud Shipment Order: Move Stock Between Sites. This article covers the third tool, the distribution order, which carries a customer order and a purchase order and is the documented route when the two sites belong to different companies. Every product statement below comes from the IFS Cloud 25R2 documentation pages linked in the text.

1.What is a distribution order in IFS Cloud?

A distribution order in IFS Cloud is an order for moving inventory parts from one site, the supply site, to another site, the demand site, according to the 25R2 page Distribution Orders. The demand and supply site can belong to the same company or to different companies.

The order itself is a planning object. When it is released, IFS Cloud creates a released customer order line on the supply site and a released purchase order line on the demand site, and the reservation, shipment and receipt processes can be reached from the distribution order. The supply site therefore sees a customer order it has to reserve and ship, and the demand site sees a purchase order it has to receive, without anyone keying in either order.

Question Shipment order Distribution order
Companies involved Sites and remote warehouses of one company Supply and demand site in the same or in different companies
Documents created Shipment and receipt, no trade orders Released customer order line on the supply site, released purchase order line on the demand site
Master data needed No sales parts, purchase parts or internal customers Internal customer, internal supplier, sales part and supplier for purchase part

If your multi-site design routes customer demand to the site that holds the stock, distribution orders are one of its building blocks. The wider design is discussed in Architecting Intelligent Distributed Fulfilment.

2.What has to be set up before the first distribution order?

A site can be entered as a demand site on a distribution order only after it has been entered as an internal customer, and the supply site has to be entered as an internal supplier. The 25R2 documentation also requires matching inventory part numbers on both sites, and the part on the demand site must be connected to a purchase part and a supplier.

  • Demand site: inventory part, purchase part and a supplier for purchase part record that points to the internal supplier.
  • Supply site: inventory part, sales part and the internal customer that represents the demand site.
  • Coordinator: every distribution order must have a coordinator, and that coordinator must be connected to a coordinator group with the distribution order prefix and number specified.

Quick registered parts are a shortcut, not a setup

When a distribution order is released, IFS Cloud creates the missing purchase and sales part records from the inventory part records, and marks the generated sales parts and supplier for purchase parts as Quick Registered Parts so they can be updated later. The release works, but prices, tax codes and delivery terms on those records are whatever the inventory part could supply. In a project I treat a quick registered part found after go-live as an open setup task with an owner, not as finished master data.

Where the coordinator comes from

The coordinator on the Supplier for Purchase Part record, General tab, is inherited by the distribution order, and the distribution order number is taken from the coordinator and its coordinator group (Enter Distribution Order Defaults). When neither the user nor the supplier record provides one, IFS Cloud uses the system coordinator, marked with an asterisk. A distribution order owned by the system coordinator is a sign that the supplier record was never completed, and nobody reviews those orders by name.

3.Which processes create distribution orders automatically?

Planned distribution orders are entered manually or created automatically, and the 25R2 Distribution Orders page names eight sources for the automatic case.

  • Material Requirements Planning (MRP)
  • Master Scheduling
  • Order Proposal
  • Next Level Demand
  • Dynamic Order Processing
  • Distribution Allocations, which create distribution orders when they are released
  • Request Task
  • Aviation Task

For automatic creation, the option Multi-site Planned Part must be enabled on the Supplier for Purchase Part record of the demand site, and that option can be selected only for internal suppliers. A planning run can then create the order when it finds a shortage and the supplier for purchase part points to an internal supplier. If the order is wrong, the fix is usually in that supplier record or in the planning parameters of the part, not in the order. Parts that reach planning without parameters are covered in Parts Missing Planning Parameters in IFS Cloud.

4.What happens when you release a distribution order?

Release turns a planned distribution order into a customer order line on the supply site and a purchase order line on the demand site, and after release the order can no longer be deleted, only changed manually or cancelled. The 25R2 page Release Distribution Order calls the release point an important decision and makes the coordinator usually responsible for balancing it. A planned order can still move with the next planning run; a released one has created orders on two sites.

The same page lists four release options that decide which customer and purchase orders receive the new lines.

Release option Effect
Auto Select and Merge Merges the distribution orders into the first available customer order and purchase order; new orders are created when none exist
Merge to CO and PO No Merges into one existing customer order and purchase order when the distribution orders share demand and supply site, order type, delivery address, forwarder, ship via, language code, delivery terms, route, automatic receipt and currency
Create New Creates a new customer order and purchase order for each released distribution order
Create New and Merge Creates new customer and purchase orders for the distribution orders that are merged into them

Orders that receive merged lines must be in Released or Reserved status. The choice affects the paperwork more than the stock: merging gives the supply site fewer customer orders to pick and ship and the demand site fewer purchase orders to receive, while Create New keeps one order pair per distribution order and makes each move easier to trace.

5.Why does a distribution order go to Stopped?

A distribution order receives the Stopped status when it cannot create a released purchase order line and a released customer order line, and the 25R2 page Release Stopped Distribution Orders names two causes.

  1. Purchase authorization. A purchase order authorization rule applies to the purchase order used by the distribution order. The authorization is handled in purchasing, and executing it allows the distribution order to be released.
  2. Credit limit. A credit limit is set up on the internal customer and the customer order exceeded it. The customer order has to be released from credit block, and that also releases the distribution order.

The reason for a stop is in the order history of the distribution order, and one order can be stopped twice, once for each cause. Both causes come from rules built for external trade. An authorization rule written for external suppliers and a credit limit copied onto the internal customer both catch internal orders unless the internal supplier and internal customer are deliberately excluded or given their own values. Check that during setup, because a stopped distribution order is a shortage on the demand site that no planner owns until someone opens the history.

6.Should you use automatic receipt on the demand site?

With automatic receipt, the distribution order is received at the demand site into the proposed location as soon as it is delivered from the supply site, so the arrival does not have to be registered. Without it, someone at the demand site registers the arrival. The automatic receipt parameter is described on the Release Distribution Order and Enter Distribution Order Defaults pages.

The setting fits when delivery and arrival are effectively the same moment, for example two sites in one building or on one campus. It misleads when the goods travel for days: from the moment of delivery the system shows stock available at the demand site while the truck is still on the road, and that stock can be reserved for orders it cannot yet serve. For long moves I leave receipt manual and watch the gap between delivery and arrival instead. Goods in that gap are the subject of Inventory Stuck In Transit in IFS Cloud.

When the supply site ships the customer order line through a shipment and hands it to a forwarder, the freight booking is a separate integration from the distribution order. The IFS Cloud and ROHLIG SUUS Logistics interface is one example: it sends the shipment details to the forwarder when the shipment is released and links the booking reference back to the shipment. Grouping several orders onto one truck is covered in Understanding Consolidated Shipments.

7.Frequently asked questions

Can an IFS Cloud distribution order move stock between two companies?

Yes. In an IFS Cloud distribution order the supply site and the demand site can belong to the same company or to different companies. On release the distribution order creates a customer order line on the supply site and a purchase order line on the demand site, so each company has its own order for the move.

What is the difference between a distribution order and a shipment order in IFS Cloud?

An IFS Cloud distribution order is internal trade: it needs an internal customer and an internal supplier and creates a customer order line and a purchase order line. An IFS Cloud shipment order moves goods between sites and remote warehouses of one company through shipment and receipt, with no sales parts, purchase parts or internal customers behind it.

Why is my IFS Cloud distribution order in status Stopped?

An IFS Cloud distribution order goes to Stopped when it cannot create a released purchase order line and a released customer order line. The documented causes are a purchase order authorization rule on the purchase order and a credit limit on the internal customer that was exceeded by the customer order. The reason is shown in the order history of the distribution order.

Can a released distribution order be deleted in IFS Cloud?

No. A released IFS Cloud distribution order cannot be deleted; it can be changed manually or cancelled. A planned distribution order has not yet created customer and purchase order lines, which is why the release point is treated as the moment of commitment.

Does MRP create distribution orders in IFS Cloud?

Yes. Material Requirements Planning is one of eight IFS Cloud processes that create planned distribution orders automatically, together with Master Scheduling, Order Proposal, Next Level Demand, Dynamic Order Processing, Distribution Allocations, Request Task and Aviation Task. The supplier for purchase part on the demand site must point to an internal supplier and have the option Multi-site Planned Part enabled, which can be selected only for internal suppliers.

8.About the author

Dariusz Myśliwiec: 18 years hands-on with IFS (Apps 7.5 to 10 and IFS Cloud). IFS Certified Associate Consultant. PRINCE2® 7. Independent practice based in Kraków, delivered remotely across Europe and globally. You talk to the consultant who does the work, not a sales layer.

Selected clients from my IFS work: 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.

Moving goods between sites with a forwarder in the middle?

The distribution order creates the trade documents in IFS Cloud. Booking the freight with the carrier needs an interface, and the ROHLIG SUUS Logistics interface for IFS Cloud already sends shipment details on release and brings the booking reference back to the shipment.

See the ROHLIG SUUS interface Read: Shipment Order in IFS Cloud

ROI Calculator

Calculate your return on investment

Input Values

€
€
€

Results

Annual Savings
€ 0
Payback Period
0 months
ROI
0%
Monthly Savings
€ 0

Get Detailed Report

Enter your details to receive a detailed ROI report.