Unified MCP icon

Unified MCP

Interact with SAP Business One via Unified MCP Server

Actions7

Overview

This node allows interaction with SAP Business One via a Unified MCP Server, supporting both direct database connections and Service Layer API calls. Specifically, for the Transaction - Commit operation, it commits an ongoing transaction identified by a transaction ID. This is useful in scenarios where multiple operations are grouped into a single transaction to ensure atomicity, and you want to finalize those changes permanently.

Practical examples include:

  • Committing a batch of database changes after successful validation.
  • Finalizing a transaction session started earlier when using the Service Layer API.

Properties

Name Meaning
Connection Type Type of connection to use: "Direct Database" or "Service Layer"
Transaction ID The unique identifier of the transaction to commit

Output

The output is a JSON object representing the response from the MCP server after attempting to commit the transaction. It typically contains success status and any relevant data or error messages returned by the server.

No binary data output is produced by this operation.

Example output structure (simplified):

{
  "success": true,
  "data": {
    // details about the committed transaction
  }
}

Dependencies

  • Requires access to a Unified MCP Server URL configured in credentials.
  • Requires an API key credential for authentication with the MCP server.
  • For Service Layer connection type, a valid session ID must be maintained and updated as needed.
  • Uses the axios HTTP client library internally to make requests.

Troubleshooting

  • Common issues:

    • Invalid or expired transaction ID: Ensure the transaction ID corresponds to an active transaction.
    • Session expiration (for Service Layer): If the session ID is invalid or expired, login again to obtain a new session.
    • Network or connectivity errors: Verify MCP server URL and network accessibility.

  • Error messages:

    • Errors returned from the MCP server will appear in the JSON output under an error message field.
    • If the node fails due to request errors, enabling "Continue On Fail" can help process subsequent items without stopping the workflow.

Links and References

Discussion