This article is a reference guide for which Ironclad property data types can be populated with data from SAP Ariba when configuring workflow field mappings.
Use Case
Use this table to check whether a given property data type is supported, and to catch the exceptions (e.g., addresses requiring specific fields) before you set up a field mapping.
Prerequisites
| Features | Workflows, Launch Forms, Integrations |
| Connected Systems |
|
| Packages |
SAP Data Foundation or SAP Procurement Automation |
| Permissions |
Admins or users with Integrations Management permissions. |
Supported Data Types
The table below lists each Ironclad property data type and whether it can be mapped from SAP Ariba supplier or requisition data. Review the Notes column for types that are conditionally supported or require additional configuration.
| Data Type | Supported | Notes |
|---|---|---|
| String | Yes | – |
| Number | Yes | – |
| Yes | – | |
| Boolean | Yes | – |
| Date | Conditional | SAP Ariba returns dates (for requisitions and suppliers) as milliseconds since epoch (a number). A transformer is required to convert this value to an Ironclad date property. Without a transformer, the value can be mapped to a number or string field instead. |
| Address | Yes |
Non-US addresses must map at least one address line, the locality (city), and the country.
US addresses must provide at least one address line, the locality (city), the region (state), the postcode, and country. |
| Monetary Value | Yes | Must map both the amount and the currency. |
| Duration | Yes | – |
| Entity | No | – |
| Related/Parent/Child Record | No | – |
| File | No | – |
| Tables | Yes | – |
| Single/Multi Picklist | No | Support for this data type is in progress. |
Resources
Explore articles, courses, and support options to get the most out of Ironclad.