Pick up new fields from SAP Business One
When someone creates a field in SAP Business One, Xchange does not know about it right away: the field structure is fetched once and used from then on. Until it is fetched again, the field is missing from every field picker — in the mapping, in the data filter, in the additional data. This guide walks the way from the new field to its first mapping.
The running example: Cambira introduces a disposal fee that has to be shown in the web shop. The user field U_ECOFEE has been created on the item master for it, and it is to be mapped in the route Artikel-Export Webshop.
The field structure is fetched in a single place: on the System status page, for the whole installation. It belongs to the source system, not to an individual route — which is why, once it is fetched, the field pickers of all routes show the new state.
What you need
- The System permission at level Full — the action is only available with it.
- The field already exists in SAP Business One.
- The ability to restart the Service Layer (or someone who does it for you).
The Service Layer restart is an action on the server, not something you operate in the interface. Arrange it with the person who looks after your SAP Business One environment. This guide marks the step but does not instruct it.
Create the field in SAP Business One
User fields, user tables and user objects are created in the SAP Business One desktop client, not in Xchange. For Cambira that is U_ECOFEE on the item master.
Only once the field exists there do the next two steps make sense — before that there is nothing to fetch.
Restart the Service Layer
The Service Layer keeps the field structure on its own side and learns about a new field only through a restart. It is the way Xchange reads SAP Business One — as long as it does not know the field, Xchange cannot fetch it either.
Have the Service Layer of your SAP Business One environment restarted. This step comes before the next one, not after it.
Fetch the field structure
Open the System status page. The Operating state area holds the action Fetch field structure, and below it the time of the last fetch.
- Click Fetch field structure. There is no confirmation prompt — the operation is not destructive and can be repeated as often as you like.
- Xchange fetches the field structure from SAP Business One again and reports Field structure fetched.
- The time below the operating state then shows the new fetch.
The action is available in every operating state, not only during an incident: fields can be created in SAP Business One at any time.
If the dialog Field structure unchanged appears instead, Xchange fetched the same structure as last time. After a fresh change in SAP Business One this almost always means the Service Layer has not been restarted yet and is still serving the old state. Have it restarted and fetch the field structure again.
If Xchange reports that the field structure could not be fetched, the Service Layer was not reachable. Make sure it is running and repeat the action.
Use the field
The new field is now available in the field pickers. For Cambira: open the route Artikel-Export Webshop, tab Mapping, and create a mapping row with U_ECOFEE as the source field — see Create a mapping.
The fetch itself is not a configuration change and does not need to be activated. The mapping you build with it does: Activate configuration changes.
Fields of an external system
For the field structure of a connected external system it is not the system status that is responsible, but the connection itself: Connections → the connection → Field structure area → Fetch field structure. The fetch always takes it fresh from the external system and picks up the new state as it does. So if Cambira's web shop has gained a field, Fetch field structure on the connection Cambira B2B-Shop is the right step — not the action of the same name on the system status page.
What comes next
Once the field is in the mapping, check the route with real data before you activate: Test a route before you activate.