Mastering CTO

TL;DR: Key Takeaways

Seamless Integration: IFS Cloud handles Configure-to-Order (CTO) by passing configuration IDs directly from Customer Orders to Purchase Orders, ensuring suppliers receive exact specifications.
Traceability: Configurations are view-only in the purchasing module to maintain data integrity with the parent demand (Sales Quotation, CO, or DOP).
Inter-site Logic: Special handling is required for internal supply chains (IPD/IPT) to ensure price and configuration synchronization between manufacturing and sales sites.
EDI/MHS Mandates: Using EDI for configured parts requires strict adherence to Order Response (ORDRSP) flows to validate pricing and configuration receipts.
Limitation Awareness: Subcontracting and Consignment stocks have specific constraints when paired with configured parts that Solution Architects must plan for.

What Problem Does This Solve?

In complex manufacturing environments, the disconnect between Engineering, Sales, and Procurement is a common source of costly errors. When selling complex, configurable products (like specialized machinery, electronics, or automotive components), the specific attributes selected by the customer must flow accurately to the supply chain.

This article solves the challenge of managing data integrity for Configure-to-Order (CTO) flows within IFS Cloud Purchasing. It addresses how to ensure that the variable characteristics defined during the sales process are accurately communicated to suppliers, how to handle inter-site transfers of these configurations, and how to troubleshoot common EDI issues. For IFS Cloud customers, mastering this flow is critical to reducing scrap, improving vendor relationships, and automating the procurement of bespoke components.

Deep Dive: CTO in IFS Cloud Purchasing

The Configure-to-Order (CTO) functionality within IFS Cloud’s Purchasing module is not a standalone feature; it is the critical execution arm of a unified supply chain strategy. Its primary development focus is to support the purchase of configured products throughout the Internal Order Flow and external procurement.

When we talk about "configured parts" in IFS, we are referring to parts linked to a Configuration Specification. In a standard flow, this configuration travels seamlessly through the message handling system between sites (for multi-site implementations) and appears on external purchase order documents (PDFs) or digital messages (EDI).

Critical Constraint: While IFS Cloud allows full visibility of the configuration throughout the purchasing lifecycle, it generally restricts the modification of the configuration within the purchasing module itself. This design is intentional to prevent a "desynchronization" between what the customer ordered (the Demand) and what is being purchased (the Supply).

Handling Configured Parts within Procurement

In the IFS Cloud ecosystem, a configured part in procurement never exists in a vacuum. It is always the child of a demand source. Understanding the origin of this demand is crucial for troubleshooting and process optimization.

The creation of a purchase line for a configured part typically stems from:

Sales Quotations: Early-stage estimation where vendor quotes are needed for bespoke items.
Customer Orders (CO): The most common trigger, creating direct demand.
Dynamic Order Processing (DOP): Complex, multi-level pegged orders used in Project manufacturing or complex A&D environments.
Material Requisitions: Internal consumption needs.

Visibility vs. Editability

Regardless of the origin, traceability is key. When a user navigates to a Purchase Requisition Line, Purchase Order Line, or Request for Order Quotation Line, the system flags the part as configured. By selecting the line and accessing View Configuration, procurement officers can see the exact characteristic values (e.g., Color: Red, Voltage: 220V, Material: Steel) that generated that specific part number revision.

"The inability to change the configuration on the PO is a safety mechanism. If a supplier states they cannot provide 'Red', the change must be driven from the Customer Order or DOP Header to ensure the Sales team and the End Customer agree to the deviation." — Senior IFS Solution Architect

Demand Inheritance and Order Conversion

The lifecycle of the configuration data is persistent. When a demand originates from a Customer Order (OE) or a DOP Order, it carries a unique Configuration_ID.

When a Purchase Requisition is converted into a Purchase Order or a Request for Order Quotation, the system does not "copy" the data; it inherits the reference. This ensures that if the configuration is updated at the source (before the PO is released), the purchasing documents reflect the latest reality.

The Role of Supply Codes

The automation of this process is governed heavily by the Supply Code defined on the Customer Order Line or the Sales Part. This is a critical setup step during the implementation phase:

Supply Code: PO Direct / PO Transit

This setting triggers the creation of a Purchase Requisition first. This allows the purchasing department to consolidate requirements, vet suppliers, or aggregate demand before creating the final Purchase Order. It adds a layer of human control suitable for high-value configured items.

Supply Code: Internal PO Direct / Internal PO Transit

This setting bypasses the requisition stage and creates a Purchase Order immediately. This is typically used in Inter-site flows (e.g., a Sales Site buying from a Manufacturing Site within the same company). Speed and automation are the priorities here.

Operational Constraints: Deletion and Copying

While automation is robust, manual intervention has rules. You can delete lines with configured parts on a Purchase Order. However, IFS Cloud will issue a warning. This is because deleting the supply (PO) leaves the demand (CO or DOP) unfulfilled ("orphaned demand"). The best practice is to manage cancellations from the demand source downwards.

Furthermore, copying a Purchase Order for a configured part is restricted. Since a configuration is unique to a specific demand instance (a specific customer's requirements), copying a PO would create supply without a linked demand, breaking the CTO logic. The only exception is creating a replacement order derived from a DOP structure, where the system understands the pegging relationship.

Subcontracting and Consignment Limitations

For organizations utilizing outside processing (subcontracting), the CTO flow encounters specific architectural boundaries in IFS Cloud.

Subcontracted work in purchasing is not modified to handle configured parts in the standard core. The technical reason lies within the DOP (Dynamic Order Processing) logic. DOP supports functionality strictly for "Charge" or "No Charge" regarding supplier material shipping. It does not natively support the complexity of passing variable configuration characteristics to a subcontractor via the standard purchasing flow in the same way it does for internal manufacturing.

Similarly, Consignment Stock for configured parts is not a supported combination. Configured parts are, by definition, unique or distinct. Consignment stock relies on standard, interchangeable inventory. Mixing these concepts creates valuation and tracking paradoxes that the system prevents to maintain financial integrity.

MHS and EDI: Digitalizing the Configured Supply Chain

In modern Industry 4.0 implementations, PDF purchase orders are being replaced by EDI (Electronic Data Interchange) and MHS (Message Handling System). IFS Cloud supports this robustly for CTO.

Outgoing Messages (ORDERS / ORDCHG)

When sending a Purchase Order (message type `ORDERS`) or a Change Order (`ORDCHG`), the configuration information—specifically the Characteristic Codes and their Values—is embedded in the XML/EDI message. This allows the supplier's ERP system to automatically read the specifications without human data entry.

Consultant Tip: Not all suppliers are capable of parsing configuration data. If a supplier treats your "Configured Part X" as a standard "Part X" (perhaps they only make one variant for you), sending the configuration data might cause their EDI import to fail. You can disable this via the Transfer Configuration Characteristics toggle in the Supplier for Purchase Part / General tab.

The Pricing Paradox in Internal Flows

A nuanced behavior occurs in Inter-site trade (Internal Order Flow). The outgoing message from the Purchasing Site includes both the Price and the Description. However, when the Manufacturing Site (Seller) receives this message, it ignores the incoming price.

Why? Because the Manufacturing Site calculates its price based on its own Customer Order pricing logic (which might involve cost-plus logic based on the configuration). This prevents the Purchasing Site from dictating the transfer price incorrectly. However, if your business rules dictate that the PO price should override the CO price, you can utilize the Send Order Price flag on the Supplier/Part setup.

The Mandatory Order Response (ORDRSP)

One of the most frequent support tickets we see relates to the "Arrival" step for configured parts. In IFS Cloud, if you buy configured parts via MHS/EDI, the use of Order Response (ORDRSP) is mandatory.

The system performs a hard validation during the Register Arrival step. It checks if an Order Response has been received. If not, the user is blocked (or warned, depending on strictness settings).

The Logic Behind the Restriction:

A Purchase Order for a configured part is often created with a Price of 0 (zero) initially, because the final price depends on the supplier's evaluation of the configuration.
The Supplier receives the order, calculates the cost of the specific configuration, and sends back an ORDRSP with the correct, confirmed price.
IFS updates the PO Line with this confirmed price.
Only then is the system ready to receive the goods at the correct inventory valuation.

This check is ubiquitous—it triggers during Dispatch Advice reception and Direct Delivery registration as well.

Receipt and Inventory Management

Once the goods hit the dock, the complexity doesn't end. In the Receipt process, warehouse staff can view the configuration to verify the physical goods against the specs (e.g., "Does this motor actually have the Red casing requested?").

Upon entering inventory, the configured part maintains its link to the configuration ID. This is visible in the Inventory Part Unit Cost page. This is vital for tracking actual costs versus estimated costs for specific projects.

Configuration of the Print Output

Not all configuration characteristics are relevant for the supplier. You might have internal characteristics (like "Sales Margin Category") that the supplier doesn't need to see. IFS Cloud offers granular control over document outputs.

Global Control: Use the Configuration Characteristic page to flag specific characteristics as "Print on Order" or "Print on Return."
Supplier Specific Control: In Supplier for Purchase Part, you can suppress the entire configuration printout for specific vendors who don't need that level of detail.

Frequently Asked Questions (FAQ)

Can I change the configuration of a part directly on a Purchase Order in IFS Cloud?

No, generally you cannot change the configuration directly on the PO line. The configuration is inherited from the demand source (Customer Order or DOP). To change it, you must modify the source demand, which will then update the purchase line. This ensures synchronization between what is sold and what is bought.

Why do I get a warning about "Order Response" when trying to receive a configured part?

When using EDI/MHS for configured parts, IFS mandates an Order Response (ORDRSP). This is because the initial PO usually has a zero price, and the system relies on the supplier's confirmation (ORDRSP) to update the correct price before the goods are received into inventory valuation.

Does IFS Cloud support subcontracting for configured parts?

Standard IFS Cloud Purchasing does not fully support the "configured part" logic within the Subcontracting flow, primarily due to limitations in DOP regarding material shipping logic. Workarounds exist but require careful solution architecting.

How do I prevent internal characteristics from printing on the Supplier PDF?

You can control this at two levels: globally via the "Configuration Display Information" on the Characteristic setup, or per supplier/part via the "Transfer Configuration Characteristics" toggle in the "Supplier for Purchase Part" settings.

Need help optimizing your IFS Cloud Supply Chain?

Configuring the procurement flow for CTO requires deep knowledge of both the Purchasing and Manufacturing modules. We specialize in tuning IFS Cloud for complex manufacturing.

Blog