Describe the app your ERP is missing.

Say what the app is for in plain words. NgageCode builds it for web and phone on IBM Maximo, IFS and SAP, and a person reviews the code before it merges.

  • Built for
  • IBM Maximo
  • IFS
  • SAP
  • Your homegrown systems

Try one

It runs on

We build it with you on your scenario, in a safe test setup.

A parts app from one sentence

Four steps from the request to an app your technicians use. An illustrative run on a test landscape, with assets in IFS and stock in SAP.

NgageCode 4 steps

Build a parts request app for our field technicians.

  1. 1 Describe the app in one sentenceAsked who approves: the site supervisor You
  2. 2 Generate the screens and the ERP callsTwo screens, assets from IFS, stock from SAP IFS and SAP
  3. 3 A person reads the code before it mergesSecret scan and static analysis passed Review
  4. 4 Ship it to the web and to phonesEach technician signs in as themselves Live
Parts request app, ready for site 100 Web Phone
Illustrative example. Every landscape is different.
  1. 1

    Describe

    You, in plain words

    Say what the app is for and who uses it. NgageCode asks a question only when it needs one.

  2. 2

    Generate

    NgageCode, on your ERP

    It finds the right records and actions, then builds the screens and the calls to your ERP.

  3. 3

    Review

    A person, before merge

    A person reads the code before it merges. Every commit is scanned for secrets.

  4. 4

    Ship

    Your teams, on web and phone

    Technicians open it on a phone at the site. Supervisors approve from a desk.

The parts app it built, for desk and phone

Supervisors see every request in a browser. Technicians raise one on a phone at the site. Assets come from IFS, stock from SAP.

Illustrative example on a test landscape. Values are samples.

Read the code it writes

One read from the parts app: the stock of a part at a plant, from SAP. A person reviews code like this before it merges.

src/api/stock.tsExample
const STOCK = 'https://erp.example.com/sap/opu/odata/sap/API_MATERIAL_STOCK_SRV';
const quote = (v: string) => `'${v.replace(/'/g, "''")}'`;

// Stock for one part at one plant, read as the signed-in user.
export async function stockAtPlant(material: string, plant: string, userToken: string) {
  const filter = `Material eq ${quote(material)} and Plant eq ${quote(plant)}`;
  const url = `${STOCK}/A_MatlStkInAcctMod?$filter=${encodeURIComponent(filter)}`
    + '&$select=Material,Plant,StorageLocation,MatlWrhsStkQtyInMatlBaseUnit&$format=json';
  const res = await fetch(url, { headers: { Authorization: `Bearer ${userToken}` } });
  if (!res.ok) throw new Error(`SAP stock read failed: ${res.status}`);
  const { d } = await res.json();
  return d.results;
}
  1. Line 1

    SAP’s released stock API, an official OData service.

  2. Line 2

    Quoted for OData, so a part number cannot change the query.

  3. Line 9

    The user’s own token, so SAP applies their permissions.

Shortened for this page. erp.example.com stands in for your SAP host.

What ERP teams ask first

See all questions

What can it build?

Web and mobile apps: forms, checklists, reports, dashboards and approval inboxes.

See what you can build

Which teams is it for?

Six teams, each with an example app built from one sentence.

Which ERPs does it work with?

IBM Maximo, IFS and SAP work out of the box, and one app can use two of them. For any other application, including a homegrown one, we teach Ngage how it works in weeks.

Does it touch the database?

Never. Apps read and write through each ERP’s official interfaces.

Whose permissions does an app use?

The signed-in user’s own, never a shared service account.

Read about security

Start with one app your team needs

Describe it in a sentence. We build it with you on your scenario, in a safe test setup.

  1. Describe the app

    One sentence: what it is for, who uses it and the ERP it runs on.

  2. We build it with you

    On your own scenario, against a test environment of your ERP.

  3. A person reviews it

    Nothing merges before that. Then your teams use it on web and phone.

Describe your app

On IBM Maximo, IFS or SAP, how soon it runs depends on access to your test environment and on the scope. On any other application, we first teach Ngage how it works, which takes weeks.