Skip to content
FAST SAP SOLUTIONS®Discuss a project

START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED

What it is. Why it matters.

An integration run can finish technically while the receiving business application rejects its content. Technical delivery and business acceptance therefore need separate evidence.

Completely new to SAP?

Manufacturers use SAP to connect work such as buying components, recording inventory, planning production, shipping equipment and accounting for costs. SAP S/4HANA is an enterprise resource planning system: it connects these activities through shared business data.

SAP Business Technology Platform, or BTP, provides cloud services for applications, data and integration. A connection needs a route, an identity and permission to perform the intended task.

A transaction code, or t-code, is a shortcut to a task in classic SAP GUI. Fiori apps provide another way to work. Names and screens depend on the product and release; you do not need a live system to learn the concepts in this guide.

Original editorial vector illustration for Integration Suite says Completed, but the business action failed: What to inspect
Original FSS editorial vector illustration. Conceptual artwork, not an SAP interface or customer-system evidence.
Scope and source-review notes

Scope and evidence

Source review by FAST SAP SOLUTIONS® editorial. This badge describes our editorial review; it does not represent SAP certification or independent endorsement.

SAP Integration Suite Cloud Integration response-handling pattern. Adapter behavior and receiver contracts determine the applicable implementation.

Documentation review on 14 November 2026 using official SAP sources and indexed official excerpts where full Help text was unavailable. Scope and service or release differences are explained in the lesson. All datasets, requests and checks are illustrative; no customer SAP runtime execution or measured results are claimed.

A MANUFACTURING EXAMPLE

Explain a rejected supplier invoice after HTTP success

Technical completion is one result

Integration status: Completed. Receiver response: Unknown supplier. Business document: Not created. Review: Business acceptance evidence
What to notice: A delivered message can still be rejected by the business application.Original annotated example with illustrative values. This is not an SAP screen or a result from a customer system.
Read the example values
Integration status
Completed
Receiver response
Unknown supplier
Business document
Not created
Review
Business acceptance evidence
Words you’ll meet in this guide
Backend
The service or system doing the work behind an interface.
Destination
Named connection settings for another service.
Credential
Access information used to prove an identity.
Subaccount
A BTP scope for applications, services and access settings.
API
A defined interface through which programs exchange data or request actions.
HTTP
The request-and-response protocol used by web applications and APIs.
Preview the practical steps

SEE THE CONNECTION

See it in a simple example.

A small example to make the idea concrete.

Message delivery → Business validation → Accepted document. Conceptual diagram for Integration Suite says Completed, but the business action failed: What to inspect.
Apply the idea: A manufacturer's integration run is technically completed, but the receiver's response rejects the supplier invoice for a business reason.An illustrative example, not a live SAP screen. The connections show how to think about the topic; they are not instructions to change a system.
  1. Explain a rejected supplier invoice after HTTP success

    A manufacturer's integration run is technically completed, but the receiver's response rejects the supplier invoice for a business reason.

  2. Completed describes flow processing, not every business outcome

    A Cloud Integration message can finish Completed even though the receiver rejected the requested business action.

  3. Separate transport, integration and business evidence

    Transport evidence answers whether an HTTP exchange or other protocol operation completed.

  4. Worked case: HTTP 200 contains an unknown-supplier rejection

    Imagine a fictional receiver API accepting invoice EXT-8001 with supplier V404 and amount 120.00 EUR.

Reading map · FSS editorial. The sections below explain each part in detail.

Found this useful?

Share this guide with your network, or leave a like.

LinkedIn WhatsApp

Your like is saved in this browser.

Explore Knowledge Hub

Discuss Your SAP Project

Your enquiry is sent through this website and used only to respond to your request.