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, specifically supporting operations on data stored either via direct database access or through the Service Layer API. The "Delete" operation for the "Data" resource allows users to remove records from a specified table or entity.

Common scenarios include:

  • Removing obsolete or incorrect records directly from a database table.
  • Deleting business objects such as business partners, items, orders, or invoices via the Service Layer.
  • Automating cleanup tasks in SAP Business One environments by deleting data based on specific conditions.

For example, you might use this node to delete customer records that meet certain criteria or remove outdated inventory items from the system.

Properties

Name Meaning
Connection Type Type of connection to use:
- Direct Database (db)
- Service Layer (sl)
Table (Direct Database only) Name of the database table from which to delete data
Condition (Direct Database only) WHERE condition string specifying which rows to delete (e.g., ID = @id)
Condition Parameters (Direct Database only) JSON object providing parameters for the WHERE condition

Output

The node outputs an array of JSON objects representing the response from the MCP server after attempting the delete operation.

  • For Direct Database connection type, the output JSON typically contains the result of the delete request, such as success status or affected rows count.
  • For Service Layer connection type, the output JSON reflects the response from the SAP Business One Service Layer API, indicating whether the deletion was successful or if any errors occurred.

No binary data is produced by this node.

Dependencies

  • Requires an active connection to a Unified MCP Server endpoint.
  • Needs credentials containing the MCP API URL and an authentication token/session ID.
  • For Service Layer operations, a valid session must be maintained (login/logout handled separately).
  • Uses HTTP requests to communicate with the MCP server's REST API endpoints.

Troubleshooting

  • Invalid or missing credentials: Ensure the MCP API URL and authentication details are correctly configured.
  • Incorrect table name or condition: For direct database deletes, verify the table exists and the WHERE condition is valid SQL syntax.
  • Session expired (Service Layer): If using Service Layer connection, ensure the session is active; re-login if necessary.
  • Malformed JSON in condition parameters: Confirm that the JSON provided for condition parameters is well-formed.
  • API errors: Check the response JSON for error messages returned by the MCP server to diagnose issues like permission problems or invalid requests.

Links and References

Discussion