SAP Integration Suite · Schema
SAP Message Processing Log
Schema for a message processing log entry in SAP Cloud Integration
API ManagementCloud IntegrationEnterprise IntegrationEvent MeshiPaaSSAPSAP BTP
Properties
| Name | Type | Description |
|---|---|---|
| MessageGuid | string | Unique GUID identifier for the message processing log entry |
| CorrelationId | string | Correlation ID linking related messages across a process |
| ApplicationMessageId | string | Application-level message identifier |
| ApplicationMessageType | string | Type classification of the application message |
| LogStart | string | ISO 8601 timestamp when message processing started |
| LogEnd | string | ISO 8601 timestamp when message processing ended |
| Sender | string | Sending system, adapter, or channel identifier |
| Receiver | string | Receiving system, adapter, or channel identifier |
| IntegrationFlowName | string | Name of the integration flow that processed the message |
| Status | string | Current processing status of the message |
| LogLevel | string | Verbosity level of the log entry |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://api-evangelist.github.io/sap-integration-suite/json-schema/sap-integration-suite-message-processing-log-schema.json",
"title": "SAP Message Processing Log",
"description": "Schema for a message processing log entry in SAP Cloud Integration",
"type": "object",
"properties": {
"MessageGuid": {
"type": "string",
"description": "Unique GUID identifier for the message processing log entry"
},
"CorrelationId": {
"type": "string",
"description": "Correlation ID linking related messages across a process"
},
"ApplicationMessageId": {
"type": "string",
"description": "Application-level message identifier"
},
"ApplicationMessageType": {
"type": "string",
"description": "Type classification of the application message"
},
"LogStart": {
"type": "string",
"description": "ISO 8601 timestamp when message processing started",
"format": "date-time"
},
"LogEnd": {
"type": "string",
"description": "ISO 8601 timestamp when message processing ended",
"format": "date-time"
},
"Sender": {
"type": "string",
"description": "Sending system, adapter, or channel identifier"
},
"Receiver": {
"type": "string",
"description": "Receiving system, adapter, or channel identifier"
},
"IntegrationFlowName": {
"type": "string",
"description": "Name of the integration flow that processed the message"
},
"Status": {
"type": "string",
"description": "Current processing status of the message",
"enum": ["COMPLETED", "FAILED", "PROCESSING", "RETRY", "ESCALATED", "DISCARDED", "ABANDONED"]
},
"LogLevel": {
"type": "string",
"description": "Verbosity level of the log entry",
"enum": ["INFO", "DEBUG", "TRACE", "ERROR"]
}
},
"required": ["MessageGuid", "Status"]
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/sap-integration-suite-message-processing-log"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.