AdvancedIFS CloudIntegration

IFS Cloud Integration Options: Projections, Connect, Events and a MES Example

Question
ifs cloud integration options

Also searched as

  • ifs cloud integration process
  • ifs cloud for mes
  • ifs connect messages
  • ifs cloud odata integration

Short answer

IFS Cloud offers four main integration routes. Projections expose data and actions as OData services for request and response, IFS Connect handles message-based and file-based exchange with transformation, business events push notifications out when data changes, and workflows orchestrate steps. For a MES, the common pattern is orders and BOMs out by projection or event, and confirmations and quantities back in through a projection or a message.

Applies to: IFS Cloud 21R1 and later, cloud or customer-hosted. Specific projection names and message formats must be checked in your release documentation.

How to choose and build an integration

  1. 1Define the data flows: what moves, which system owns it, how often and how fast it must arrive.
  2. 2For request and response over HTTP, use a projection through OData with an IAM service client.
  3. 3For asynchronous messages, files or partner formats, use IFS Connect with routing and transformation.
  4. 4For near real-time outbound notifications, use a business event that triggers a message or call.
  5. 5Plan error handling: retries, a dead-letter place, alerting and a way to replay failed messages.
  6. 6Test with production-like volume in a non-production environment before cutover.

Choosing the route

Projections are the modern default for synchronous reads and writes, since the same layer feeds the web client and respects permission sets. IFS Connect is the better fit for queued, batch or legacy formats where you need transformation, routing and a message log. Use events to avoid polling, and use workflows when a step needs conditions or human input.

Authentication for projection calls uses tokens from the IAM service. Our page on projection 401 errors covers the usual token problems.

Worked example: MES integration

A typical manufacturing execution link works like this. When a shop order is released in IFS, an event or a scheduled projection read gives the MES the order, operations, routing and material list. The MES runs the job and reports back operation start and finish, good and scrap quantities and consumed material.

Those confirmations go back through a projection call or a Connect message that posts them to the shop order. Keep IFS the owner of the order and cost, and the MES the owner of the execution. Decide up front how the MES handles an order changed in IFS after release, since that is where integrations usually break.

GET https://IFS_HOST/main/ifsapplications/projection/v1/<ProjectionName>.svc/<EntitySet>?$filter=<condition>
Authorization: Bearer <token>

Operational concerns

Treat integrations as products: name an owner, monitor message queues, version the contracts and test after every service update. Idempotent writes matter, because a retry must not post a confirmation twice.

Where data cannot leave your network, keep the integration layer and any AI or analytics beside IFS on the same private network and use read-only service clients for anything that only needs to look.

Try it here, free

IFS Cloud Projection OData URL Builder

Open full tool

Fill in host, realm, projection and entity set to generate the token request and a ready OData GET URL for IFS Cloud projections.

Common pitfalls

  • !Polling a projection every few seconds when an event would do.
  • !Using an administrator login instead of a dedicated service client.
  • !Posting confirmations twice because retries are not idempotent.
  • !Not defining what happens to released orders changed in IFS.
  • !Skipping regression tests on integrations after service updates.

How an ERP-grounded AI assistant handles this

For integrations, an on-prem assistant can read your message logs and projection responses to explain why a MES confirmation was rejected, or to compare the order in IFS with the order in the MES. Because it runs on your own hardware with a read-only service client, production data stays inside your network. It does not replace the integration layer; it helps people run it.

See ERPray

Frequently asked questions

Should I use IFS Connect or projections?

Use projections for synchronous request and response over HTTP. Use IFS Connect for message queues, files and formats that need transformation and logging. Many integrations use both.

Can IFS Cloud push data out when something changes?

Yes. Business events report changes and can trigger an action or message, which avoids constant polling by the external system.

Which system should own the shop order in a MES integration?

Normally the ERP owns the order, routing and cost, and the MES owns execution on the floor. Define clearly how changes and cancellations travel in each direction.

Is the integration different on a customer-hosted installation?

The mechanisms are the same, but network access, certificates, identity provider setup and who operates the middleware differ, so confirm each with whoever hosts your environment.

Related

Error fix

IFS Cloud OData Projection API: Fixing 401 and 403 Errors

IFS Cloud exposes its data through OData v4 projections under /main/ifsapplications/projection/v1/, secured by OAuth2 tokens from IFS IAM. A 401 almost always means the token is missing, expired or issued by the wrong realm; a 403 means the identity is authenticated but its permission sets do not grant that projection or its entity actions.

How-to

How to Set Up Business Events and Actions in IFS

IFS Business Events fire when a defined condition on a Logical Unit is met, such as a new record, an update, or a specific attribute changing, and Actions subscribe to those events to send email, invoke a workflow, or call an external service. Both are configured in Solution Manager (or the Events and Actions work area in IFS Cloud) without requiring custom PL/SQL for most standard cases.

How-to

IFS Cloud REST API Documentation: Projections, OData and How to Explore Them

IFS Cloud APIs are projections served as OData v4 REST services. General product documentation is published by IFS, but the authoritative description of the API for your environment comes from the environment itself: the projection metadata document and the API exploration tools in the client. Authenticate with a token from IFS IAM, then read entity sets with standard OData query options.

How-to

IFS Cloud Workflow Example, External File Templates, Update Analyzer and PO Status

Treat IFS Cloud configuration as a set of building blocks: workflows or business events to react to changes, external file templates to load or send flat files, an update analysis step to check what a release will touch in your customizations, and the supported database views for reading data such as purchase order status. This page shows how each fits together with a worked approval example.

Error fix

IFS Cloud: Unable to Save, Internal Server Error and Quick Report Problems

In IFS Cloud a save failure or internal server error is almost always a server-side exception returned through the projection the page calls. Read the error detail, reproduce it in the browser network tab, then check the middleware and database logs for the real cause, which is typically a business rule, a missing permission, a bad customization or a stale cache. Quick Report problems are usually a missing permission grant or mismatched bind parameters.

How-to

IFS Cloud Report Designer, Quick Reports and Crystal Reports: Which to Use

IFS Cloud has several reporting routes. Use Quick Reports for fast read-only lists of data, the report designer route for formatted operational documents such as order confirmations and pick lists, legacy Crystal-based layouts only where you already have them, and the analytical tools for dashboards. Report rules then control when and how a report is produced and sent.

AI for ERP

AI for IFS Cloud in aerospace and defense manufacturing

Add AI to IFS Cloud for aerospace and defense: projections, Aurena UX, Lobby, and engineer-to-order data, deployed on-prem or in your private cloud.

AI for ERP

AI Agents for ERP, Running On-Prem

A practical guide to on-prem AI agents for ERP: what they can safely automate, where human approval belongs, and how to design the guardrails.

Stuck on IFS Cloud?

Talk to engineers who work inside IFS Cloud every week, and who build private AI that answers these questions from your own ERP data.

Talk to an ERP engineerBrowse ERP Help
All ERP Help articles

Keep exploring

Free tools

ERP fixes and how-tos

Guides

AI on your ERP

Integrations

Software