📘 Screen: Mapping - Integration
The mapping is the translation dictionary between the name that comes from outside and the
upCampo record. The external system calls the field TH-014; in upCampo it is
Talhão 14 - Boa Vista. The scale's spreadsheet brings the variety as M8210; in the
record it is M 8210 IPRO. Without this translation, every import stops at "not found";
with it, the system finds the match on its own.
It is a behind-the-scenes screen: it is used by whoever handles the integration with the ERP, the scale or the technology partner, not by day-to-day crop work.
📍 Location in the system
Menu: File > Mapping - Integration
🧩 Main function
Store, for each upCampo record, the equivalent name and code in the external system, so that data imports find the right record even when the names do not match.
📝 Main fields
| Field | Description |
|---|---|
| Code | Required. Identifies the mapping line. |
| Supplier | Which external system this translation comes from. It is what lets you have, for the same record, one translation for each partner. |
| Active | Only active lines are considered during import. Unchecking is the way to turn off a translation without deleting it. |
| Table | What kind of record is being translated: Field, Variety, Product class, Product, Fleet type, Fleet or Field Work Order. |
| upCampo table · upCampo description · upCampo ID | This side: the upCampo record, with its name and identifier. When you choose the record in the field matching the table, all three fill in automatically. |
| External table · External description · External ID | The other side: what the same item is called in the outside system. The external description is the key piece: it is what the import searches by. The external table field accepts typing a new value, besides the ones already used. |
The list repeats these columns (Code, upCampo table, upCampo description, upCampo ID, External table, External description, External ID, Supplier and Active), with search on each one.
🔎 Where the translation is used
The most visible case is importing harvest load tickets from a spreadsheet, on the Inbound Load Ticket. When reading the spreadsheet, the system first looks for the field and the variety by the exact name in the record; if it does not find them, it looks in the mapping for an active line whose External description equals the one in the spreadsheet (ignoring upper and lower case) and uses the record that line points to. Only if both searches fail does the line go into the problem list as "not found".
The other translations serve the integrations that use these records. If you do not have an integration in place, this screen stays empty, and that is how it should be.
- Spreadsheet imports stop flagging fields and varieties as "not found"
- Different names in the two systems no longer require renaming records
- Each partner has its own translation, without one getting in the way of the other
When the integration is with the Operations Center, it is worth seeing how the upCampo integration with John Deere works.
❓ Frequently asked questions
The load ticket import says "field not found". What do I do?
Compare the field name in the spreadsheet with the one in the record. If they differ and you do not want to rename either, register a line here: the upCampo field on one side, the name that comes in the spreadsheet in the External description field on the other, with Active checked. On the next import the system finds it.
Do I need to fill in this screen?
Only if the farm exchanges data with another system (ERP, scale, technology partner) and the names do not match. A farm that enters everything inside upCampo does not use this screen.
Can I have more than one translation for the same field?
Yes: one line per external system, identified in the Supplier field. What you should avoid is two active lines with the same external description pointing to different records: in that case the import uses the first one it finds.