Resources · Make integration

SAP S/4HANA Make integrationAutomate SAP S/4HANA with Make.

Can Make move orders and invoices in and out of your ERP without a line of code? The SAP S/4HANA Make integration gives you 54 modules, 6 of them triggers. This guide covers the connection, a first scenario and what each module is good for.

Enterprise app This app is reserved to Make's Enterprise plan.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the SAP S/4HANA Make integration do?

The SAP S/4HANA Make integration links your SAP S/4HANA Public Cloud account to Make, a visual tool where you build scenarios (automations made of chained blocks) by clicking instead of coding. Each block, called a module, reads or changes sales orders, purchase orders, supplier invoices, payment advices, credit memo requests or business partners.

Supplier invoices that never sit unnoticed. Watch Supplier Invoices spots each new invoice, Get a Supplier Invoice pulls its details, and your accounts payable team hears about it in the tool they already use.

Orders typed once, not twice. When a deal is signed in another app, Create a Sales Order opens the order in SAP and Add a Sales Order Item fills in the lines. The same logic works on the buying side with Create a Purchase Order.

Approvals handled where the decision happens. Release a Sales Order Approval Request and Reject a Sales Order Approval Request let a manager's answer flow back into SAP without anyone logging in.

Two limits to know first. The app is reserved to the Make Enterprise plan, so the free tier and the smaller paid plans cannot use it. And all 6 triggers are scheduled: Make checks SAP on the scenario's schedule, nothing reaches Make the second it happens. Before you commit, the Make pricing page explains the plans, and n8n vs Make helps if you are still choosing a tool. To learn the editor itself, see Make training.

Connect

How do you connect SAP S/4HANA to Make?

  1. 01

    Add an SAP S/4HANA module

    In a scenario, click the +, search for SAP S/4HANA and pick any of its modules. Then click Create a connection. A connection is your SAP account linked to Make once, then reused by every SAP module you add later.

  2. 02

    Name the connection

    This step is optional, but a clear name helps when you run a test system and a live one side by side. Something like SAP production or SAP sandbox saves you from picking the wrong account in a hurry.

  3. 03

    Authorize and save

    Follow what the connection window asks: either sign in and authorize Make on SAP's page, or paste the key SAP gives you. Click Save. Make then lists the SAP objects it can read, so you pick values instead of typing them.

First scenario

Your first scenario with SAP S/4HANA

GoalWhen an order comes in through another app, Make opens a sales order in SAP S/4HANA and adds its line item.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Add the module of the app where orders arrive first, such as your form or your shop.

  2. 02

    Add Create a Sales Order

    Click the + to the right of that first module, search SAP S/4HANA and choose Create a Sales Order. Click Create a connection if this is your first SAP module.

  3. 03

    Map the order data

    Fill the module fields with values from the first module: click a field and pick the value it received instead of typing it. Make shows the SAP values it can read once the connection works.

  4. 04

    Add the line item

    Place Add a Sales Order Item right after it. Map the sales order number from Create a Sales Order and the line details from the first module, so the line lands on the order you just created.

  5. 05

    Test with Run once

    Click Run once and send a test order through the first app. Each module shows the bundles it received (a bundle is one item passing between modules), so you can check the order in SAP.

  6. 06

    Schedule and switch on

    Open the clock on the first module: a new scenario runs every 15 minutes by default. Adjust it if your plan allows, then switch the scenario on. Each module run counts as one operation on your plan.

Triggers

What can start a scenario in SAP S/4HANA?

6 modules start a scenario when something happens in SAP S/4HANA. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by SAP S/4HANA as soon as it happens.

SAP S/4HANA1Watch Business Partners

Watch Business Partners

Scheduled trigger

In MakeTriggers when a business partner is created or updated.

Watch Business Partners starts your scenario whenever a business partner is created or changed in SAP, so the customer and supplier records in your other tools stop drifting away from the ERP.

How it fires
scheduled, Make checks SAP on the scenario's schedule rather than hearing from SAP directly.
When to use it
sales edits a customer's address in SAP and your CRM should show the same address.
Watch out
updates fire it too, so if the same scenario writes back to that partner with Update a Business Partner, it can wake itself up again.
SAP S/4HANA2Watch Credit Memo Requests

Watch Credit Memo Requests

Scheduled trigger

In MakeTriggers when a credit memo request is created.

Every new credit memo request becomes a starting point: this trigger hands each one to the next module, which lets you warn finance or log the request before anyone has to go looking for it.

How it fires
scheduled, Make polls SAP at the interval set on the scenario.
When to use it
a customer disputes a delivery, a request is raised in SAP, and the account manager should hear about it.
Watch out
it reacts to creation only, so a request edited later will not start the scenario a second time.
SAP S/4HANA3Watch Payment Advices

Watch Payment Advices

Scheduled trigger

In MakeTriggers when a payment advice is created.

Your team learns about incoming payment advices without opening SAP: each newly created advice arrives in the scenario as a bundle, ready to be sent to a channel, a sheet or a reconciliation step.

How it fires
scheduled, Make asks SAP for new advices on the scenario's schedule.
When to use it
treasury wants a note each time a customer announces a payment, to match it against open items.
Watch out
changes to an existing advice do not trigger it; pair it with Get a Payment Advice if you need the latest version later.
SAP S/4HANA4Watch Purchase Orders

Watch Purchase Orders

Scheduled trigger

In MakeTriggers when a purchase order is created.

Purchasing keeps a trail of new orders outside SAP: this trigger catches each purchase order once it is created and passes it on, so suppliers, budgets or project boards can be updated from it.

How it fires
scheduled, Make checks SAP for new purchase orders at the scenario's interval.
When to use it
a project manager wants every purchase order for the site listed in a shared table.
Watch out
only creation counts; if buyers often change orders afterward, add Get a Purchase Order in a later scenario to read the current state.
SAP S/4HANA5Watch Sales Orders

Watch Sales Orders

Scheduled trigger

In MakeTriggers when a sales order is created or updated.

Sales orders feed your other tools the moment Make sees them: new orders and edited ones both start the scenario, which keeps delivery, invoicing or reporting tools in step with SAP.

How it fires
scheduled, Make looks for new or updated sales orders on the scenario's schedule.
When to use it
the warehouse team works from a shared board and needs each order and each change to it.
Watch out
since an update fires it again, avoid ending the same scenario with Update a Sales Order on the order you just received.
SAP S/4HANA6Watch Supplier Invoices

Watch Supplier Invoices

Scheduled trigger

In MakeTriggers when a supplier invoice is created.

Accounts payable stops chasing new supplier invoices: this trigger passes each invoice created in SAP to the next module, where you can read its details, notify someone or start an approval.

How it fires
scheduled, Make queries SAP for new supplier invoices at the scenario's interval.
When to use it
invoices above a certain value need a second look from the controller before payment.
Watch out
it only sees creation, so an invoice released or cancelled later will not show up here; use Search Supplier Invoices to review those.
Modules

What can Make do in SAP S/4HANA?

SAP S/4HANA gives you 48 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

SAP S/4HANA1

Add a Purchase Order Item

Action

In MakeAdds an item to a purchase order by the purchase order number.

A late request no longer means a second purchase order: this module appends one line to an order that already exists, found by its purchase order number.

When to use it
a technician asks for an extra part and the buyer wants it on the order already open with that supplier.
Watch out
you need the purchase order number; if you only know the supplier, run Search Purchase Orders first to find it.
SAP S/4HANA2

Add a Sales Order Item

Action

In MakeAdds an item to a sales order by the sales order number.

Customers who add to an order get it on the same sales order: the module attaches a new line to an existing order, identified by its sales order number.

When to use it
right after Create a Sales Order, to add each product line of an order received in another app.
Watch out
one run adds one item, so an order with several lines needs one bundle per line coming into this module.
SAP S/4HANA3

Cancel a Supplier Invoice

Action

In MakeReverses a supplier invoice by the supplier invoice number and fiscal year.

A wrong supplier invoice gets reversed without a trip into SAP: the module cancels it using the invoice number and the fiscal year together.

When to use it
a supplier sends a corrected invoice and the original must be reversed so it is not paid twice.
Watch out
the fiscal year is required along with the number; pass both from the module that found the invoice, not a year typed by hand.
SAP S/4HANA4

Create a Business Partner

Action

In MakeCreates a new business partner.

New customers and suppliers reach SAP without retyping: this module creates the business partner record from data collected elsewhere.

When to use it
a supplier finishes an onboarding form and procurement wants the partner ready in SAP before the first order.
Watch out
run Search Business Partners before it, otherwise a form submitted twice leaves you with two copies of the same company.
SAP S/4HANA5

Create a Credit Memo Request

Action

In MakeCreates a new credit memo request.

Refund requests start in SAP as soon as they are approved elsewhere: the module opens a new credit memo request so billing can issue the credit.

When to use it
customer service accepts a return in its helpdesk and the credit should be requested without a separate email to finance.
Watch out
it creates a new request each time it runs, so make sure the scenario only reaches it once per approved return.
SAP S/4HANA6

Create an Entity

Action

In MakeCreates a new entity.

Objects that have no named module here can still be created: Create an Entity is the generic version, working on an SAP entity rather than on an order or an invoice.

When to use it
the record you need is not one of the six business objects covered by dedicated modules.
Watch out
the doc does not say which entities are available; check the list Make shows once your connection works.
SAP S/4HANA7

Create a Payment Advice

Action

In MakeCreates a new payment advice.

Payment notices from customers can land in SAP straight away: the module records a new payment advice so the cash team can plan with it.

When to use it
a customer announces a transfer through a portal or an email parser, and treasury wants the advice in SAP.
Watch out
each run creates one advice; keep a unique reference in the scenario so a repeated notice does not create a duplicate.
SAP S/4HANA8

Create a Purchase Order

Action

In MakeCreates a new purchase order.

Approved purchase requests turn into real orders on their own: this module creates the purchase order in SAP from the data your request tool collected.

When to use it
a manager signs off a request in a form or a project tool and purchasing no longer copies it by hand.
Watch out
it creates the order header; add the lines with Add a Purchase Order Item, mapping the new purchase order number.
SAP S/4HANA9

Create a Sales Order

Action

In MakeCreates a new sales order.

Orders taken outside SAP get entered once: the module opens a new sales order from the data of your shop, CRM or order form.

When to use it
a deal moves to won in the CRM and the order should exist in SAP before delivery planning starts.
Watch out
if the source can send the same order twice, check it with Search Sales Orders before this module runs.
SAP S/4HANA10

Create a Supplier Invoice

Action

In MakeCreates a new supplier invoice.

Supplier invoices captured elsewhere reach SAP without manual entry: the module creates the invoice record ready for your usual checks.

When to use it
invoices arrive through a scanning or extraction tool and accounts payable wants them posted in SAP.
Watch out
a wrong entry is not deleted the same way once posted; Delete a Supplier Invoice only works before posting, Cancel a Supplier Invoice after.
SAP S/4HANA11

Delete a Credit Memo Request

Action

In MakeDeletes a credit memo request by the credit memo request number.

Requests raised by mistake disappear from SAP: this module deletes a credit memo request identified by its request number.

When to use it
a return is withdrawn in the helpdesk and the matching request should not stay open in billing.
Watch out
deleting cannot be undone from Make; test with Run once on a request you created for testing, never on a live one.
SAP S/4HANA12

Delete an Entity

Action

In MakeDeletes an entity by its key(s).

Any entity reachable through the generic modules can be removed with this one, using the key or keys that identify it.

When to use it
you created a test record with Create an Entity and want the scenario to clean it up afterward.
Watch out
a wrong key deletes the wrong record, so read it with Get an Entity first and map the key from there rather than typing it.
SAP S/4HANA13

Delete a Payment Advice

Action

In MakeDeletes a payment advice by its ID.

A payment advice that turned out to be wrong can be removed by its ID, which keeps treasury's view of expected cash accurate.

When to use it
a customer cancels an announced transfer and the advice created earlier should go.
Watch out
the module needs the advice ID; get it from Search Payment Advices or from the module that created the advice.
SAP S/4HANA14

Delete a Purchase Order

Action

In MakeDeletes all items of a purchase order that has been posted by the purchase order number.

Clearing out a whole purchase order takes one module: it deletes all the items of a posted order, found by its purchase order number.

When to use it
a project is cancelled and every line of its order should be removed at once.
Watch out
it hits every item, not a single line; to remove just one, use Delete a Purchase Order Item instead.
SAP S/4HANA15

Delete a Purchase Order Item

Action

In MakeDeletes an item in a purchase order by the purchase order number and item number.

One line comes off a purchase order while the rest stays untouched: the module needs the purchase order number and the item number.

When to use it
a supplier can no longer deliver one product and the buyer drops that line only.
Watch out
item numbers are easy to mix up; read them with Search Purchase Order Items before deleting.
SAP S/4HANA16

Delete a Sales Order

Action

In MakeDeletes all items of a sales order that has been posted by the sales order number.

When a customer cancels everything, this module removes every item of the posted sales order in one go, using the sales order number.

When to use it
an order is cancelled in the shop and SAP should reflect it before the warehouse picks anything.
Watch out
for a partial cancellation, Delete a Sales Order Item is the right module; this one leaves no line behind.
SAP S/4HANA17

Delete a Sales Order Item

Action

In MakeDeletes an item in a sales order by the sales order number and item number.

Partial cancellations stay partial: the module removes a single line from a sales order, found by the order number and the item number.

When to use it
a customer drops one product from an order but keeps the others.
Watch out
map the item number from Search Sales Order Items or Get a Sales Order Item; a guessed number can remove the wrong product.
SAP S/4HANA18

Delete a Supplier Invoice

Action

In MakeDeletes a supplier invoice that has not been posted by the supplier invoice number and fiscal year.

Drafts entered by mistake can go before they count: the module deletes a supplier invoice that has not been posted, using its number and fiscal year.

When to use it
an invoice was captured twice by your extraction tool and the duplicate is still unposted.
Watch out
once the invoice is posted, this module is not the tool; reverse it with Cancel a Supplier Invoice.
SAP S/4HANA19

Get a Business Partner

Action

In MakeRetrieves the details of a business partner by its ID.

Need the full record behind a partner ID? This module returns the details of one business partner, ready to map into the next steps.

When to use it
an order carries only a partner ID and your email to the customer needs their name and address.
Watch out
it expects the exact ID; if you start from a name or an email, go through Search Business Partners.
SAP S/4HANA20

Get a Credit Memo Request

Action

In MakeRetrieves the details of a credit memo request by its ID.

The current state of one credit memo request, fetched by its ID, gives you what you need to answer a customer or update a ticket.

When to use it
a customer asks where their credit stands and support wants the answer inside the helpdesk.
Watch out
one ID, one request; to review several at once, Search Credit Memo Requests fits better.
SAP S/4HANA21

Get an Entity

Action

In MakeRetrieves an entity by its key(s).

For objects outside the named modules, this generic reader returns one entity found by its key or keys.

When to use it
a scenario must check a record that none of the order, invoice or partner modules cover.
Watch out
fill every key the entity uses, mapped from an earlier module, rather than typing them by hand.
SAP S/4HANA22

Get a Payment Advice

Action

In MakeRetrieves the details of a payment advice by its ID.

Treasury gets the details of one payment advice, looked up by its ID, without opening SAP to read it.

When to use it
Watch Payment Advices fired earlier and a later scenario needs the advice as it stands today.
Watch out
keep the ID from the trigger or from Create a Payment Advice; this module has no search by amount or customer.
SAP S/4HANA23

Get a Purchase Order

Action

In MakeRetrieves the details of a purchase order by the purchase order number.

Buyers can pull a purchase order's details from its number and send them wherever they are needed, a supplier email or a project sheet.

When to use it
a supplier asks about an order and the reply should quote what SAP holds right now.
Watch out
it reads the order; for its lines one by one, use Get a Purchase Order Item or Search Purchase Order Items.
SAP S/4HANA24

Get a Purchase Order Item

Action

In MakeRetrieves the details of an item in a purchase order by the purchase order number and item number.

One line of a purchase order, with its details, comes back when you give the order number and the item number.

When to use it
goods arrive for a single line and the receiving team wants to compare them with what was ordered.
Watch out
both numbers are required; if you only have the order number, list its lines with Search Purchase Order Items.
SAP S/4HANA25

Get a Sales Order

Action

In MakeRetrieves the details of a sales order by the sales order number.

Customer service can quote any sales order from its number: the module returns the order's details for a reply, a ticket or a report.

When to use it
a customer writes in with an order number and the helpdesk should show the order next to the message.
Watch out
a mistyped number fetches the wrong order or none at all; map it from the ticket or from a search instead of letting someone type it.
SAP S/4HANA26

Get a Sales Order Item

Action

In MakeRetrieves the details of an item in a sales order by the sales order number and item number.

This module zooms in on a single line of a sales order, found by the order number and the item number, when the whole order is too much.

When to use it
a delivery issue concerns one product and support needs only that line's details.
Watch out
it returns one line; to go through every line of an order, Search Sales Order Items is the right choice.
SAP S/4HANA27

Get a Supplier Invoice

Action

In MakeRetrieves the details of a supplier invoice by the supplier invoice number and fiscal year.

Accounts payable reads a supplier invoice's details from its number and fiscal year, ready to send for approval or to compare with an order.

When to use it
right after Watch Supplier Invoices, to pass the invoice details to the controller.
Watch out
number and fiscal year go together; a number alone will not identify the invoice.
SAP S/4HANA28

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

When no listed module does what you need, this one reaches any endpoint of the SAP API with the connection you already set up.

When to use it
you need an SAP object or an operation that the 54 modules do not offer.
Watch out
you write the request yourself, so you need SAP's API documentation at hand; the doc points to the OData v2 API catalogue.
SAP S/4HANA29

Reject a Sales Order Approval Request

Action

In MakeRejects an approval request of a sales order by the sales order number.

A manager's no reaches SAP without them logging in: the module rejects the approval request attached to a sales order, by the order number.

When to use it
approvals are answered in a chat or a form, and a refusal there should stop the order in SAP.
Watch out
route only real refusals here; a scenario that mixes up the answers could reject orders that were meant to go through.
SAP S/4HANA30

Release a Sales Order Approval Request

Action

In MakeReleases an approval request of a sales order by the sales order number.

Approved orders move on as soon as the manager says yes: this module releases the approval request of a sales order, found by its number.

When to use it
a manager approves a discounted order from a message and the order should continue in SAP.
Watch out
pair it with Reject a Sales Order Approval Request in the same scenario, one branch per answer, so no request stays waiting.
SAP S/4HANA31

Release a Supplier Invoice

Action

In MakeReleases a blocked supplier invoice by the supplier invoice number and fiscal year.

Blocked supplier invoices get unblocked from outside SAP: the module releases one using its invoice number and fiscal year.

When to use it
the controller clears a disputed invoice in the approval tool and payment can go ahead.
Watch out
it only applies to invoices that are blocked; a new, unblocked invoice has nothing to release.
SAP S/4HANA32

Update a Business Partner

Action

In MakeUpdates a business partner by its ID.

Changes made in your CRM or supplier portal reach SAP's business partner record, found by its ID, so both sides stay aligned.

When to use it
a supplier updates its details in a portal and procurement wants SAP to match.
Watch out
paired with Watch Business Partners on the same partner, it can start the scenario again after each update.
SAP S/4HANA33

Update a Credit Memo Request

Action

In MakeUpdates a credit memo request by the credit memo request number.

A credit memo request keeps up with the conversation: the module changes an existing request by its number when what was agreed with the customer changes.

When to use it
after a second look at a return, customer service agrees to a different credit and billing should see it.
Watch out
Watch Credit Memo Requests reacts to creation only, so this change will not reach scenarios that rely on that trigger.
SAP S/4HANA34

Update an Entity

Action

In MakeUpdates an entity by its key(s).

Generic records get edited the same way named ones do: Update an Entity changes an SAP entity identified by its key or keys.

When to use it
a value on a record not covered by the order, invoice or partner modules has to follow a change made elsewhere.
Watch out
read the entity first with Get an Entity to be sure the keys point to the right record.
SAP S/4HANA35

Update a Payment Advice

Action

In MakeUpdates a payment advice by its ID.

Announced payments rarely stay exactly as first sent; this module edits an existing payment advice, found by its ID, so the forecast stays right.

When to use it
a customer corrects a transfer they announced earlier.
Watch out
Watch Payment Advices does not react to edits, so tell treasury through the scenario itself if they need to know.
SAP S/4HANA36

Update a Purchase Order

Action

In MakeUpdates a purchase order by the purchase order number.

Purchase orders follow the changes agreed with suppliers: the module updates an order found by its purchase order number.

When to use it
a supplier confirms a new delivery date in its portal and the order in SAP should say the same.
Watch out
it changes the order, not its lines; for one line, Update a Purchase Order Item is the module.
SAP S/4HANA37

Update a Purchase Order Item

Action

In MakeUpdates a purchase order item by the purchase order number and item number.

One line of a purchase order changes while the others stay as they are: the module needs the order number and the item number.

When to use it
the supplier can only ship part of the quantity on one product and the buyer adjusts that line.
Watch out
map both numbers from Search Purchase Order Items; a wrong item number edits the wrong product.
SAP S/4HANA38

Update a Sales Order

Action

In MakeUpdates a sales order by the sales order number.

When a customer changes their mind, the sales order in SAP follows: the module updates the order found by its number.

When to use it
a customer edits a delivery detail from the shop's account page and the order should carry it.
Watch out
Watch Sales Orders fires on updates, so a scenario that starts from it and ends here can keep restarting.
SAP S/4HANA39

Update a Sales Order Item

Action

In MakeUpdates a sales order item by the sales order number and item number.

This module edits a single line of a sales order, found by the order number and the item number, and leaves every other line alone.

When to use it
a customer raises the quantity of one product before shipping.
Watch out
to add a new product rather than change an existing one, use Add a Sales Order Item; this module only edits lines that already exist.
SAP S/4HANA40

Search Business Partners

Search

In MakeRetrieves a list of business partners filtered by criteria.

Finding partners by criteria instead of by ID is what this search is for: it returns every business partner that matches, zero, one or several.

When to use it
before Create a Business Partner, to check the company does not already exist.
Watch out
each partner found becomes its own bundle, and every module after it runs once per partner, which adds operations.
SAP S/4HANA41

Search Credit Memo Requests

Search

In MakeRetrieves a list of credit memo requests filtered by criteria.

This search pulls every credit memo request that matches the criteria you set, so a scenario can review open refund claims in one pass. Each request comes out as a separate bundle, one item handed to the next module.

When to use it
you need several requests at once, for example to copy them into a finance tracker, rather than one request whose ID you already hold.
Watch out
the search can return zero results, so plan what the next module does when nothing comes back.
SAP S/4HANA42

Search Purchase Order Items

Search

In MakeRetrieves a list of items in a purchase order filtered by criteria.

Buyers get the lines of a purchase order that fit their criteria, which lets them check what was actually ordered before anything else happens. Every matching line travels on as its own bundle.

When to use it
after Watch Purchase Orders spots a new order and you want to act on each of its lines, not on the order header.
Watch out
each returned line runs the following modules once, and every run counts as an operation on your plan.
SAP S/4HANA43

Search Entities

Search

In MakeRetrieves a list of entities filtered by criteria.

This is the generic search of the app: it returns a filtered list of records for an entity type the dedicated modules do not cover. Handy when the object you need has no module of its own.

When to use it
you work with SAP S/4HANA data outside business partners, orders, invoices, payment advices and credit memos.
Watch out
if a named search exists for your object, start there and keep the generic one for the rest.
SAP S/4HANA44

Search Payment Advices

Search

In MakeRetrieves a list of payment advices filtered by criteria.

Treasury gets back the payment advices that match its criteria, with a ready list of expected incoming payments to reconcile. Each advice becomes one bundle that later modules can read.

When to use it
you want to compare several advices with bank data in another app, instead of fetching them one by one with Get a Payment Advice.
Watch out
when nothing matches, the scenario receives no bundle, so test the criteria with Run once first.
SAP S/4HANA45

Search Purchase Orders

Search

In MakeRetrieves a list of purchase orders filtered by criteria.

Procurement finds the purchase orders that fit its criteria and passes each one along, which helps it build a report or chase suppliers without opening SAP. You get whole orders here, not their individual lines.

When to use it
you need orders that already exist, while Watch Purchase Orders only reacts to newly created ones.
Watch out
to reach the lines of each order, chain Search Purchase Order Items after this module.
SAP S/4HANA46

Search Sales Order Items

Search

In MakeRetrieves a list of items in a sales order filtered by criteria.

Sales operations can see exactly which products a customer ordered: the module returns the lines of a sales order that meet your criteria. Each line flows on as a separate bundle.

When to use it
a scenario must treat each ordered product on its own, for example to notify a warehouse team in a chat app.
Watch out
a large order produces many bundles, and each module after this one runs once per line.
SAP S/4HANA47

Search Sales Orders

Search

In MakeRetrieves a list of sales orders filtered by criteria.

Account managers get the sales orders matching their criteria, with a way to pull a batch of orders into a spreadsheet or a CRM. Unlike Get a Sales Order, it does not need the order number up front.

When to use it
you look for orders that already sit in SAP S/4HANA, rather than waiting for Watch Sales Orders to catch changes.
Watch out
keep the criteria tight, since every returned order consumes operations in the modules that follow.
SAP S/4HANA48

Search Supplier Invoices

Search

In MakeRetrieves a list of supplier invoices filtered by criteria.

Accounts payable collects the supplier invoices that fit its criteria and can spot what needs attention across many invoices at once. Each invoice comes out as a bundle ready for the next step.

When to use it
you want to feed a list of invoices into Release a Supplier Invoice or a review sheet, not only the ones created after the scenario starts.
Watch out
with no match, the modules after it do not run at all.
Need help

Need help automating SAP S/4HANA with Make?

A person reads every message.

FAQ

Common questions about SAP S/4HANA and Make

01Is the SAP S/4HANA Make integration free?
No. SAP S/4HANA is an enterprise app in Make, and enterprise apps are reserved to the Enterprise plan. The Free plan covers 3,000+ standard apps with 2 active scenarios, a 15-minute minimum between scheduled runs and 5 minutes of execution per run, but it does not unlock this app. The paid Core, Pro and Teams plans do not either. Usage on the Enterprise plan is counted in credits, one operation per module run, so a scenario that handles many orders uses more of them.
02What do you need to connect SAP S/4HANA to Make?
Two things: an SAP S/4HANA Public Cloud account and a Make account on the Enterprise plan. The official doc lists no other prerequisite. You then add any SAP module, click Create a connection, optionally name it, authorize Make or paste the key SAP provides, and save. The doc also points to SAP's OData v2 API catalogue and notes that one connection field only serves to validate the connection. Once saved, the connection is reused by every SAP module in your scenarios.
03Does the SAP S/4HANA trigger fire instantly?
No. All 6 SAP S/4HANA triggers are scheduled: Make checks SAP on the scenario's schedule rather than being told by SAP. A new scenario runs every 15 minutes by default. On paid plans the minimum interval can go down to 1 minute. None of the triggers is instant, meaning SAP never pushes an event to Make through a webhook here. If your process needs a faster reaction, set the shortest interval your plan allows on the first module.
04What if a module is missing for what you want to do in SAP?
Use Make an API Call. It reaches any endpoint of the SAP API with the connection you already have, so an object or an operation absent from the 54 modules is still within reach. You write the request yourself, guided by SAP's OData v2 API catalogue that the doc links to. For records outside orders, invoices, payment advices, credit memo requests and partners, also look at the generic entity modules, such as Create an Entity or Search Entities, before writing a custom call.
05Should you use Make or n8n for SAP S/4HANA?
It depends on the tool your team already runs. On Make, SAP S/4HANA comes with 54 ready modules and 6 scheduled triggers, but it requires the Enterprise plan. Many apps also have an n8n node, so if your automations already live in n8n, check whether one exists for SAP before switching. Compare on facts you can verify: the modules you need, the plan they require and who will maintain the scenarios day to day.