SAP B1 Service Layer 12 - Gestion de Proyectos icon

SAP B1 Service Layer 12 - Gestion de Proyectos

Interact with SAP B1 Service Layer 12 - Gestion de Proyectos

Actions5

Overview

This node interacts with the SAP B1 Service Layer 12 specifically for managing projects ("Gestion de Proyectos"). It supports operations such as creating, updating, deleting, retrieving, and canceling projects within SAP Business One.

A typical use case is automating project management workflows by integrating SAP B1 project data into an n8n workflow. For example, you can update project details automatically when triggered by external events or create new projects based on input data from other systems.

The Update operation allows modifying an existing project by specifying its unique identifier (DocEntry) and providing the updated content in JSON format.

Properties

Name Meaning
DocEntry The unique numeric identifier of the project to operate on. Required for update actions.
JSON Body A JSON object containing the fields and values to update in the specified project.

Output

The node outputs an array of items corresponding to each input item processed. Each output item contains a json field with the response from the SAP B1 Service Layer API:

  • For successful updates, the json contains the updated project data returned by the API.
  • In case of errors, the json includes an error field with the error message.

No binary data is produced by this node.

Dependencies

  • Requires connection credentials to the SAP B1 Service Layer API, including:

    • Base URL of the SAP B1 Service Layer
    • Username
    • Password
    • Company database name

  • The node authenticates by sending a login request to obtain session cookies used in subsequent requests.

  • The node uses HTTP methods (GET, POST, PATCH, DELETE) to interact with the SAP B1 API endpoints.

Troubleshooting

  • Authentication failures: If login credentials are incorrect or the service URL is unreachable, the node will fail to authenticate. Verify credentials and network connectivity.

  • Invalid DocEntry: Providing a non-existent or incorrect DocEntry will cause the API to return an error. Ensure the DocEntry corresponds to an existing project.

  • Malformed JSON Body: The JSON Body must be valid JSON matching the expected schema for project updates. Invalid JSON or unsupported fields may cause API errors.

  • API Errors: The node returns error messages from the SAP B1 API in the output. Review these messages to identify issues such as permission problems or invalid operations.

  • SSL Issues: The node disables SSL certificate verification (rejectUnauthorized: false). If your environment requires strict SSL validation, adjust accordingly.

Links and References

Discussion