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 Server, supporting operations on various resources including Transactions. Specifically, the Transaction Rollback operation allows users to rollback (undo) a previously started transaction by providing its transaction ID. This is useful in scenarios where a series of database or service layer operations need to be reverted due to an error or business logic condition.

Practical examples:

  • If a multi-step process involving data updates fails at some point, you can rollback the entire transaction to maintain data integrity.
  • During integration workflows, if validation fails after starting a transaction, rolling back prevents partial commits.

Properties

Name Meaning
Connection Type Type of connection to use:
- Direct Database
- Service Layer
Transaction ID ID of the transaction to rollback. This identifies which transaction should be undone.

Output

The node outputs JSON data representing the response from the Unified MCP Server after attempting the rollback operation. The structure typically contains status information about the rollback request, such as success confirmation or error details.

No binary data output is involved.

Example output JSON snippet:

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

Dependencies

  • Requires an API key credential for the Unified MCP Server.
  • The node makes HTTP requests to the MCP server URL configured in credentials.
  • The MCP server must support the /api/transactions/{transactionId}/rollback endpoint for both connection types (db and sl).

Troubleshooting

  • Common issues:

    • Invalid or expired transaction ID: The rollback will fail if the transaction ID does not exist or has already been committed/rolled back.
    • Network or authentication errors connecting to the MCP server.
    • Using the wrong connection type may cause unexpected failures if the transaction was started under a different connection type.

  • Error messages:

    • "Transaction not found": Verify the transaction ID is correct and active.
    • "Unauthorized" or "Authentication failed": Check that the API credentials are valid and have proper permissions.
    • "Network Error": Ensure the MCP server URL is reachable and there are no firewall issues.

Links and References

Discussion