SAP Materials
Category: EHR & Practice Mgmt
Node id: sap-materials
Standards: SOC2
Integrates with SAP MM for healthcare materials and supply chain management including stock, materials, and purchase orders
What it does
- SAP MM material master data retrieval
- Stock level and inventory queries
- Purchase order management
- OData-based SAP Materials Management integration
Use cases
- Query medical supply inventory levels from SAP
- Track purchase orders for pharmaceutical supplies
- Material master data sync for supply chain management
- Inventory monitoring for hospital warehouse automation
Runtime
- Performance tier:
variable
Input ports
| Name | Type | Required | Description |
|---|---|---|---|
material_id | text | No | Material ID for get_material and check_stock operations |
plant | text | No | Plant code for check_stock filtering |
purchase_order_data | json | No | Purchase order data for create_purchase_order operation |
vendor | text | No | Vendor/supplier ID for filtering purchase orders |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
materials | json | No | List of materials |
material | json | No | Single material record |
stock | json | No | Stock levels for a material |
purchase_order | json | No | Created purchase order |
purchase_orders | json | No | List of purchase orders |
http_status | number | No | HTTP status code from SAP |
Settings
Basic
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| SAP URL | sap_url | string | Yes | Base URL of the SAP MM instance | ||
| Operation | operation | enum | No | get_materials | get_materials, get_material, check_stock, create_purchase_order, get_purchase_orders | Materials management operation to perform |
Auth
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Auth Token | auth_token | secret | No | Bearer token for SAP authentication | ||
| API Key | api_key | secret | No | SAP API key |
Advanced
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Material Type | material_type | string | No | Filter materials by product type | ||
| SAP Client | sap_client | string | No | 100 | SAP client number |
Errors
| Code | Description |
|---|---|
SAP_URL_REQUIRED | SAP system URL must be configured |
AUTH_FAILED | Authentication to SAP system failed |
SAP_REQUEST_FAILED | HTTP request to SAP system failed |
UNSUPPORTED_OPERATION | Operation not recognized |
Runtime notes
- Only one output key is populated per execution depending on the operation
- material_id is required for get_material and check_stock; plant is an optional filter for check_stock
- get_materials can be filtered by material_type via config; returns all materials if unset
- Output shape comes directly from SAP OData response; structure varies by S/4HANA version
See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.
Something unclear? Send documentation feedback by email.