SAP B1 Service Layer 2 - Finanzas icon

SAP B1 Service Layer 2 - Finanzas

Interact with SAP B1 Service Layer 2 - Finanzas

Actions10

Overview

This node integrates with the SAP Business One Service Layer (Finance module) to perform various operations on financial data entities. Specifically, for the Journal Entries resource and the Get by Key operation, it retrieves a single journal entry identified by a unique key from the SAP B1 system.

Typical use cases include:

  • Fetching detailed information about a specific journal entry for auditing or reporting.
  • Integrating SAP B1 journal entries into other systems or workflows.
  • Automating retrieval of financial transaction details based on known keys.

For example, a user might provide the key of a journal entry to retrieve its full details, such as posting date, lines, amounts, and references.

Properties

Name Meaning
Key The unique numeric identifier of the journal entry to retrieve. This is required to specify which journal entry to fetch.

Output

The node outputs JSON data representing the journal entry retrieved from SAP B1. The structure corresponds directly to the SAP B1 Journal Entry object, typically including fields like:

  • Entry number (key)
  • Posting date
  • Document type
  • Lines with account codes, debit/credit amounts
  • References and remarks

If the request fails, the output JSON will contain an error field with the error message.

No binary data output is produced by this operation.

Dependencies

  • Requires connection credentials to the SAP Business One Service Layer API, including:
    • Base URL of the SAP B1 Service Layer endpoint.
    • Username and password for authentication.
    • Company database name.
  • The node performs a login POST request to obtain session cookies before making the GET request.
  • The environment must allow HTTPS requests to the SAP B1 Service Layer.
  • No additional external dependencies beyond the configured SAP B1 API credentials.

Troubleshooting

  • Authentication errors: If login fails, verify that the username, password, and company database are correct and that the SAP B1 Service Layer is accessible.
  • Invalid key errors: Providing a non-existent or incorrect journal entry key will result in an error response from SAP B1. Confirm the key exists.
  • Network issues: Ensure the node can reach the SAP B1 Service Layer URL and that SSL certificates are valid or properly handled.
  • Permission issues: The authenticated user must have rights to read journal entries.
  • Error messages: The node returns error messages from the SAP B1 API in the output JSON under the error field. Use these messages to diagnose issues.

Links and References

Discussion