Unified MCP icon

Unified MCP

Interact with SAP Business One via Unified MCP Server

Actions7

Overview

This node enables interaction with SAP Business One through a Unified MCP (Middleware Communication Platform) Server. Specifically, for the Transaction - Rollback operation, it allows users to rollback an ongoing transaction by providing its transaction ID. This is useful in scenarios where a transaction needs to be aborted due to errors or business logic conditions, ensuring data consistency and integrity.

Practical examples include:

  • Rolling back a database transaction if a subsequent step in a workflow fails.
  • Aborting a service layer transaction when validation errors occur before committing changes.

Properties

Name Meaning
Connection Type Type of connection to use:
• Direct Database
• Service Layer
Transaction ID ID of the transaction to rollback. This uniquely identifies the transaction to abort.

Output

The node outputs JSON data representing the response from the Unified MCP server after attempting the rollback. The structure typically includes success status and any relevant messages or error details returned by the server.

No binary data output is produced by this operation.

Example output JSON might look like:

{
  "success": true,
  "message": "Transaction rolled back successfully"
}

or in case of failure:

{
  "success": false,
  "error": "Invalid transaction ID"
}

Dependencies

  • Requires access to a Unified MCP Server URL configured via credentials.
  • Requires an API key credential for authentication to the MCP server.
  • For Service Layer connection type, a valid session ID must be maintained and managed by the node.
  • The node uses HTTP requests (via axios) to communicate with the MCP server endpoints.

Troubleshooting

  • Common issues:

    • Invalid or expired transaction ID leading to rollback failure.
    • Network connectivity problems to the MCP server.
    • Missing or invalid API credentials causing authentication failures.
    • Session expiration when using Service Layer connection type.

  • Error messages and resolutions:

    • "Invalid transaction ID": Verify that the transaction ID provided is correct and corresponds to an active transaction.
    • "Unauthorized" or authentication errors: Check that the API key credential is correctly configured and has necessary permissions.
    • "Session expired" (Service Layer): Re-authenticate to obtain a new session ID before retrying.
    • Network timeouts or connection refused: Ensure the MCP server URL is reachable from the n8n environment.

Links and References

Discussion