OCI – Configure Fields
In the Product Fields tab, which product data is sent to the procurement system during the cart transfer is defined.
How do fields work?
Each OCI field corresponds to a data point in the transfer — for example the product description (NEW_ITEM-DESCRIPTION) or the article number (NEW_ITEM-MATNR).
For each field, where the value comes from is defined:
OCI field name Primary field Fallback 1 Fallback 2 Fixed value
NEW_ITEM-MATNR → productNumber or productEan or productOciMe or "unknown"
The connector checks sources from left to right. As soon as a value is found (not empty), it is used.
Adding Fields
In the Product Fields tab, new fields can be added. Each field has the following properties:
| Property | Description |
|---|---|
| Name | OCI field name exactly as expected by the procurement system (e.g. NEW_ITEM-DESCRIPTION) |
| Type | Standard for normal values, Long for longer texts (technical difference in the form) |
| Data field | Primary product data field (select from the data field library) |
| Fallback 1–3 | Used when the previous field returns no value |
| Fixed value | Static text as last fallback |
| Position | Sort order in the form |
Always set at least one fixed value as a safety net — this way no empty fields are transferred.
Available Data Fields
A complete overview of all data fields — including which protocols (OCI, cXML) they are available for — can be found here:
Shipping Fields (Tab: Shipping Fields)
If Append shipping is enabled in the General tab, which data is transferred for the shipping line item can be defined in the Shipping Fields tab — analogous to product fields.
The available shipping data fields are also listed in the data field overview.
Start Index
In OCI 4 transfers, fields are numbered: NEW_ITEM-DESCRIPTION[1], NEW_ITEM-DESCRIPTION[2], …
The Start index in the General tab defines at which number this counter begins (default: 1). Some procurement systems expect 0 as the starting value.