Actions88
- Purchase Credit Note Actions
- Purchase Invoice Actions
- Purchase Delivery Note Actions
- Purchase Down Payment Actions
- Purchase Order Actions
- Purchase Quotation Actions
- Purchase Request Actions
- Purchase Return Actions
- Purchase Tax Invoice Actions
Overview
This node integrates with the SAP Service Layer to manage purchase-related entities, specifically here focusing on Purchase Quotations. The "Get All (OData)" operation retrieves multiple purchase quotation records using OData query parameters, allowing users to filter and select specific fields from the dataset.
Typical use cases include:
- Fetching a list of purchase quotations that meet certain criteria (e.g., total amount greater than a threshold).
- Retrieving only specific fields from purchase quotations to optimize data transfer and processing.
- Integrating SAP purchase quotation data into workflows for reporting, auditing, or further automation.
For example, you could use this node to get all purchase quotations where the total exceeds 1000 and only retrieve the document entry number, card code, and total amount fields.
Properties
| Name | Meaning |
|---|---|
| Select | Comma-separated list of fields to return from each purchase quotation record ($select). Example: DocEntry,CardCode,DocTotal |
| Filter | OData filter expression to restrict which purchase quotations are returned ($filter). Example: DocTotal gt 1000 and CardCode eq 'V1000' |
Output
The output is an array of JSON objects representing purchase quotations matching the query. Each object contains the fields requested via the Select property or all fields if none specified.
Example output structure snippet:
[
{
"DocEntry": 123,
"CardCode": "V1000",
"DocTotal": 1500.00,
...
},
...
]
No binary data is output by this node.
Dependencies
- Requires connection credentials to the SAP Service Layer API, including:
- Base URL of the SAP Service Layer endpoint.
- Username and password for authentication.
- Company database identifier.
- The node performs a login request to obtain session cookies used in subsequent API calls.
- No additional external dependencies beyond the SAP Service Layer API.
Troubleshooting
- Authentication errors: If login fails, verify the SAP Service Layer credentials and company database name are correct.
- Invalid OData queries: Malformed
$selector$filterexpressions may cause API errors. Ensure proper syntax and field names as per SAP documentation. - Network issues: Connection failures can occur if the SAP Service Layer endpoint is unreachable or SSL certificates are invalid. The node disables strict SSL verification (
rejectUnauthorized: false) but network connectivity must be ensured. - Empty results: If no records match the filter, the output will be an empty array. Adjust filters accordingly.
- Error responses: Errors from the API are returned in the output JSON under an
errorkey with the message string.
Links and References
- SAP Business One Service Layer Documentation
- OData Protocol Overview
- SAP Service Layer Purchase Quotations Entity (example link; check your SAP version docs)