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 two connection types: direct database access and service layer API calls. Specifically, for the Data resource with the Delete operation, it allows deleting records either by executing a delete command directly on a database table or by calling the service layer to delete a record by its ID.

Common scenarios include:

  • Removing obsolete or incorrect data entries from SAP Business One tables.
  • Automating cleanup tasks in SAP Business One databases.
  • Deleting business objects such as business partners, items, orders, or invoices via the service layer API.

For example, you can delete a customer record by specifying its ID when using the service layer connection, or delete rows matching a condition in a database table when using the direct database connection.

Properties

Name Meaning
Connection Type Choose between "Direct Database" (db) or "Service Layer" (sl) connection methods.
Table (Direct Database only) The name of the database table from which to delete records.
Condition (Direct Database only) The SQL WHERE clause condition to specify which records to delete.
Condition Parameters (Direct Database only) JSON object providing parameters for the WHERE condition placeholders.

Output

The node outputs an array of JSON objects, each representing the response from the MCP server for each input item processed. The json field contains the server's response data, which typically includes confirmation of deletion or error details.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Unified MCP Server with valid credentials including the server URL and authentication token/session.
  • For service layer operations, a valid session ID must be maintained.
  • The node uses HTTP requests (via axios) to communicate with the MCP server endpoints.

Troubleshooting

  • Invalid or missing credentials: Ensure that the MCP API credentials are correctly configured and valid.
  • Incorrect table name or condition: When using direct database connection, verify that the table name exists and the condition syntax is correct.
  • Malformed JSON in condition parameters: The Condition Parameters property must be valid JSON; otherwise, parsing errors will occur.
  • Session expired or invalid (service layer): If using the service layer connection, ensure the session is active; re-login if necessary.
  • API endpoint errors: Check the MCP server logs or responses for detailed error messages if deletion fails.

Links and References

Discussion