Skip to main contentSkip to footer

Time Fences in IFS Cloud: Demand and Planning Time Fence

How the demand and planning time fences work in IFS Cloud: what each protects, who sets the values, and how master scheduling and MRP react.

Independent IFS Cloud practice · Planning design Know where the plan is frozen and where the system may still change it The planning time fence and the demand time fence in IFS Cloud divide the planning horizon into periods in which master scheduling and MRP treat supply and demand differently. A planner who expects…

Read more

Master Production Schedule Level 1 in IFS Cloud Explained

How Master Production Schedule Level 1 works in IFS Cloud: Level 0 and Level 1 parts, the proposals it creates, dependent demand and time fences.

Independent IFS Cloud practice · Master scheduling design Describe the Level 0 and Level 1 structure before planners read the proposals Master Production Schedule Level 1 is the level of the IFS Cloud master schedule where you plan long-term demand for parts that are manufactured or purchased. Its calculation creates…

Read more

IFS Cloud Intraday Availability: Supply and Demand Timing

How IFS Cloud analyses short-term supply and demand down to the minute: the horizon, firm or non-firm items, balance fields and projected quantity.

Independent IFS Cloud practice · Short-term planning Check projected stock down to the minute for the next days IFS Cloud intraday availability is the analysis of the short-term supply and demand situation for inventory parts, considering the timings within the day down to minute level. It runs on the Inventory Parts…

Read more

Master Scheduling ATP in IFS Cloud: How Promising Works

How Master Scheduling Available to Promise works in IFS Cloud: the master schedule as data source, generic and customer-dimension checks, and set-up.

Independent IFS Cloud practice · Order promising design Decide what the master schedule promises before customer orders depend on it Master Scheduling Available to Promise (ATP) is a promising method in IFS Cloud that uses the master schedule (MPS) as the data source for customer order promising. A promise date from…

Read more

IFS Cloud Material Requisition: Statuses, Reserve, Issue

How IFS Cloud material requisition works for internal demand: statuses, reservation before issue, partial issue and closing a line.

Independent IFS Cloud practice · Internal demand design Decide who reserves, who issues and who closes before requisitions pile up An IFS Cloud material requisition is the document through which material is requested for internal demand, and it runs through its own flow: request, reservation, issue and closure. If the…

Read more

IFS Cloud Routing Lead Time: Fixed, Variable and Overlap

How IFS Cloud routing lead time is calculated: fixed and variable time, standard lot size, parallel operations and overlap, with worked examples.

Independent IFS Cloud practice · Manufacturing planning design Check your routing data against the calculation that produces the planned lead time IFS Cloud routing lead time is the lead time of a manufactured part calculated from its routing, and the page states that MRP and Master Scheduling use it. If the…

Read more

IFS Cloud Email Customer Documents: Set-Up Rules

IFS Cloud email customer documents: how the contact is found, what each of invoice, quotation and order confirmation needs, and the invoice lock.

Independent IFS Cloud practice · Sales output design Check the contact, the document and the event before customers say they never got the invoice To make IFS Cloud email customer documents reach customers, each document needs its own set-up: an invoice, a quotation and an order confirmation each have their own page…

Read more

IFS Cloud Lead Time: Purchase, Manufacturing and Expected

IFS Cloud lead time: how purchase, manufacturing and expected lead time are defined, where each is calculated and which one MRP reads.

Independent IFS Cloud practice · Planning data design Know which lead time a function reads before you fill the fields IFS Cloud lead time lives in several fields, and each field has its own meaning. If purchase, manufacturing and expected lead time are filled without knowing which one a function reads, planned dates…

Read more

IFS Cloud Multi-Supplier Ordering: How Splits Work

IFS Cloud multi-supplier ordering splits a requisition by percentage, rounds to standard multiples and warns against double sourcing. What to test.

Independent IFS Cloud practice · Purchasing design Split a requirement between suppliers on purpose, and check the quantities before the orders go out IFS Cloud multi-supplier ordering divides the quantity of one purchase requisition between suppliers by percentage. One supplier cannot or should not carry the whole…

Read more
A detailed guide on implementing centralized purchasing in IFS Cloud, including technical prerequisites, workflow automation, and integration with Data Mesh for real-time data synchronization.

Core Concept: Consolidate Demand, Decentralize Delivery

Centralized purchasing separates the transactional flow (ordering) from the physical flow (delivery):

  • Transactional Flow: Local purchase requisitions are consolidated into a single Purchase Order (PO) by a central purchaser. This PO is issued to the supplier as a unified order.
  • Physical Flow: The supplier delivers goods directly to the demand site, eliminating internal inventory transactions and reducing logistical complexity.

Key Benefit: No internal inventory transactions are required between the demand site and the ordering site, as receipt and arrival registration occur at the demand site.

Strategic Configuration and Prerequisites

To implement centralized purchasing effectively, enforce the following data consistency rules:

1. Purchase Part Standardization

All sites must use identical:

  • Part Numbers: Ensure the same part number is used across all locations.
  • Unit of Measure (UoM): Standardize the purchase UoM and conversion factors to inventory UoM.
  • Catalog Alignment: The central purchasing site’s catalog must include all parts from demand sites.

Failure to standardize: Leads to order errors, delayed deliveries, and increased operational costs.

2. Site Basic Data Setup

Configure site-level rules to define interactions between central and local entities:

  • Validity Periods: Define time intervals for default purchasing sites.
  • Pricing Logic: Choose whether prices are fetched from the Purchasing Site (PO Header) or Demand Site (PO Line).
  • Strategic Note: Using «Demand Site» pricing simplifies part administration by limiting basic data setup to the demand site.

Operational Workflow

From Requisition to Order

The transition from local requisition to central order can be automated or manual:

  • Automatic Detection: The «Central Order» option is enabled automatically if the demand site has valid centralized basic data.
  • Manual Selection: Buyers can manually select the central order option and specify the site and part pricing method.
  • Consolidation: Buyers can add lines to existing POs, converting normal POs to centralized POs.

Receipt and Arrival

Receipt and arrival registration are handled entirely by demand sites:

  • No central action is required for part arrivals.
  • Inventory transactions are recorded locally as usual.
  • For direct customer deliveries, the end customer’s address is saved on the PO line, and the process is managed by the demand site.

Risk Mitigation and Data Integration

Data Consistency Risks

Inconsistent part data across sites can disrupt centralized purchasing. Mitigate risks by:

  • Conducting a pre-implementation audit of part numbers, UoM, and catalogs.
  • Using Data Mesh and OData projections for real-time data synchronization.

Testing Scenarios

Before go-live, test the following scenarios:

  • Multi-site orders to a single supplier.
  • Direct deliveries to end customers.
  • Manual override of automated central order detection.

Frequently Asked Questions (FAQ)

How does the system determine the price for a centralized order?
A centralized order retrieves price-related information from either the Purchasing Site (PO Header) or the Demand Site (PO Line), based on configuration.
Are internal inventory transactions required between the central site and local sites?
No. Receipt and arrival registration at the demand site eliminate the need for internal inventory transactions.
What happens if centralized basic data is missing during requisition conversion?
The «Central Order» option will not enable automatically. However, buyers can manually select it and specify part pricing and site details.
Must part numbers be identical across all sites?
Yes. Parts must have the same number, UoM, and conversion factors across all sites to ensure seamless processing.
How can Data Mesh improve centralized purchasing?
Data Mesh enables real-time data synchronization across decentralized locations, ensuring consistency and reducing errors in multi-site procurement.

Implementation Checklist

Use this checklist to ensure a successful centralized purchasing implementation:

  1. Audit part numbers, UoM, and catalogs for consistency across all sites.
  2. Configure validity periods and pricing logic for each site.
  3. Test automated and manual central order processes.
  4. Simulate direct deliveries to end customers.
  5. Integrate Data Mesh for real-time data synchronization (if applicable).
  6. Train procurement teams on new workflows and error handling.

Key Performance Indicators (KPIs)

Measure the success of your centralized purchasing implementation with these KPIs:

  • Reduction in the number of purchase orders by X%.
  • Decrease in order processing time by Y days.
  • Cost savings from bulk purchasing and improved supplier terms.
  • Reduction in order errors and delivery delays.

Centralized Purchasing FAQ

How does the system determine the price for a centralized order?

A centralized order retrieves price-related information from either the Purchasing Site (PO Header) or the Demand Site (PO Line). This depends entirely on your specific configuration preferences for pricing logic.

Are internal inventory transactions required between the central site and local sites?

No. One of the key benefits of this model is that receipt and arrival registration occur directly at the demand site, effectively eliminating the need for complex internal inventory transactions.

What happens if centralized basic data is missing during requisition conversion?

The system is designed for safety; the «Central Order» option will not enable automatically if data is missing. However, buyers can intervene by manually selecting the option and specifying the necessary part pricing and site details.

Must part numbers be identical across all sites?

Yes, this is a strict prerequisite. For seamless processing, parts must share the same Part Number, Unit of Measure (UoM), and conversion factors across all participating sites.

How can Data Mesh improve centralized purchasing?

Data Mesh architecture facilitates real-time data synchronization across decentralized locations. This ensures consistency (e.g., matching part numbers) and significantly reduces errors inherent in multi-site procurement strategies.

×
Need Expert Guidance?
We've helped hundreds of businesses succeed. Get a free consultation to discuss your project requirements.
Get Free Consultation
17Years Experience
50Implementations
PRINCE2Certified
100%Success Rate

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.