Integration
SAP Business One and MDC
SAP Business One to MDC. Both directions are separate sync products, configured independently, and this page shows what the shipped catalogue sets up for this pair.
- Phase 1 · forward sync
- No Phase 2 for this pair
In plain wordsRecords from SAP Business One are pushed into MDC. There is no shipped write-back in the other direction for this pair.
Phase 1 — SAP Business One to MDC
What you getRecords from SAP Business One become unit of measure schedule, uom, price level, products, sales order, sales order detail, invoice, invoice detail, quote detail, quote in MDC. New records are created and existing ones updated.
| Group | Business outcome | Objects | Source tables and views |
|---|---|---|---|
| CRM Unit of measure schedule | The templates push unit of measure schedule to MDC. | unit of measure schedule | — |
| CRM unit of measure | The templates push uom to MDC. | uom | — |
| CRM Price level | The templates push price level to MDC. | price level | item prices |
| CRM Product | The templates push product to MDC. | product | items |
| CRM sales order | The templates push sales order to MDC. | sales order | sales order lines, e, item prices, sales orders, business partners |
| CRM sales order detail | The templates push sales order detail to MDC. | sales order detail | sales order lines, sales orders, business partners, business partner addresses |
| CRM invoice | The templates push invoice to MDC. | invoice | invoice items, e, stock items, invoices, sales ledger customers |
| CRM invoice detail | The templates push invoice detail to MDC. | invoice detail | invoice lines, AR invoice documents, business partners, business partner addresses |
| CRM quote detail | The templates push quote detail to MDC. | quote detail | quotation lines, sales quotations, business partners, business partner addresses |
| CRM Quote and Line | The templates push quote to MDC. | quote | quotation lines, e, item prices, sales quotations, business partners |
Destination objects
- unit of measure schedule
- uom
- price level
- product
- sales order
- sales order detail
- invoice
- invoice detail
- quote detail
- quote
Phase 2 — MDC back to SAP Business One
Setting up SAP Business One and MDC from the CLI
One wizard stands the tenant up, and it is the same five steps for every pair: register, capture the server IP, connect the CRM, declare the ERP connector, then import and enable the sync processes. What changes between pairs is the CRM’s connection mode and the ERP’s connector type.
1. Register the tenant
Registration creates the account, emails a verification link, and — once the Data Lake is seeded — prints a once-only bootstrap API key valid for seven days. The three consent flags are the registrant’s own decision, and the server refuses start without all three.
# which instance types sign-up accepts - run this first and use SAP Business One's code below
$ dlake register erps
# the three consent flags are the registrant’s decision - ask before passing them
$ dlake register start --generate-password \
$ --email <email> --company "<Company Name>" --phone <tel> \
$ --instance-type <code from dlake register erps> \
$ --consent-crm-backup --consent-erp-backup --consent-phone
# after the human clicks the verification link: watch for the seed and catch the key
$ dlake register status --watch
# the bootstrap key expires in 7 days - mint a durable one while it is still valid
$ dlake admin create_api_key --keyName "<tenant>-setup" --expirationDays 90
2. Connect MDC and declare SAP Business One
Steps 3 to 5 of the wizard are admin-plane tools, they are safe to re-run, and the server enforces their order — attempt the CRM step before the server IP is captured and it answers 409 naming the step you skipped.
# the authoritative answer to where a registration got to - first call when resuming
$ dlake admin registration_state
# step 3: record the server IP (a prerequisite for the CRM step)
$ dlake admin registration_capture_server_ip --ipAddress <ip>
# step 4: the catalog lists every CRM with its authMode and the fields it needs
$ dlake admin registration_crm_catalog
$ dlake admin registration_crm_select --crmName <Crm>
# an OAuth CRM: the catalog’s callbackMode says which leg this one takes
$ dlake registration oauth --crm <Crm>
$ dlake admin registration_crm_finalize
# step 5: the catalog lists the connector types and the fields each one needs
$ dlake admin registration_connector_catalog
$ dlake admin registration_connector_submit \
$ --connectorType <type from the catalog> --erpName <SAP Business One code> --fields @fields.json
$ dlake admin registration_connector_provision
$ dlake admin registration_provisioning_status
3. Review and enable the Phase 1 processes
The shipped templates listed above are what crmpro_apply_template imports. Every one of them imports its process inactive, so an imported process does nothing until an operator activates it — read the process and its field mapping first, because an object with no mapped fields pushes nothing and records no error.
# the default-template catalog, and the mapping each template carries
$ dlake admin crmpro_templates --profile <tenant>
# what exists on the tenant now, and the master sync flag
$ dlake admin crmpro_list_processes --profile <tenant>
$ dlake admin crmpro_sync_status --profile <tenant>
# read a process and its field mapping BEFORE activating it
$ dlake admin crmpro_get_process --profile <tenant> --recordId <id>
$ dlake admin crmpro_field_mapping --profile <tenant> --recordId <id>
# turn the forward sync on
$ dlake admin crmpro_set_sync_enabled --profile <tenant> --enabled true
Processes run in a fixed order, and that order is a dependency order: a process that depends on another’s records sees them only once that process has run, so a parent flows on one run and its children on the next. The full order for this pair is on the Phase 1 page.
The wizard in full, including resuming a setup days later: Setting up an integration with dlake · Registering a new Data Lake · CRMPro (forward sync).
Source on GitHub
This page is generated from the skill pages in the dlake CLI repository. Those pages are the authority; if they disagree with anything here, they are right.
SAP Business One and MDC: common questions
Which way does data move between SAP Business One and MDC?
One way. Phase 1 (CRMPro) pushes SAP Business One records into MDC. The repository ships no TxDownloaderPro write-back for this pair, so there is no supported Phase 2 from MDC back to SAP Business One.
What do Phase 1 and Phase 2 mean?
They are the two sync products the on-premises agent can run. Phase 1 is CommercientCRMPro, product 11, the forward sync from the source system into the CRM. Phase 2 is CommercientTxDownloaderPro, product 22, the write-back in the other direction. Registering a product says what to run; the Phase 1 and Phase 2 configuration says what it runs on.
What does the forward sync into MDC actually create?
The shipped catalogue carries 10 template groups for this pair: CRM Unit of measure schedule, CRM unit of measure, CRM Price level, CRM Product, CRM sales order, CRM sales order detail, CRM invoice, CRM invoice detail and 2 more. Each group sets up its own sync process, and the integration page says what each one delivers.
Which MDC objects does the forward sync write?
unit of measure schedule, uom, price level, product, sales order, sales order detail, invoice, invoice detail and 2 more. Those are the kinds of MDC record the shipped templates write for a SAP Business One source; nothing else is written unless you add templates of your own.
Does the forward sync delete anything in the CRM?
Each template group carries its own insert, update and delete flags, and the integration page lists what each group does. Read a process with dlake admin crmpro_get_process before activating it.
Is there a write-back from MDC to SAP Business One?
No. The repository ships no TxDownloaderPro page for MDC into SAP Business One, so changes made in MDC are not carried back to SAP Business One by a supported process. Only the Phase 1 forward sync exists for this pair.
View moreShow less
Can an AI agent set this up?
Yes, over the admin control plane or the CLI — the same tools either way. The crmpro_* tools cover listing, reading, creating and updating processes. They need a full-scope key that belongs to a user holding the Admin role, and every write is audited.
Where is the authoritative source for this pair?
The skill pages in the dlake CLI repository, which is where this page is generated from. The forward sync page is linked at the foot of the integration page, and the same text is readable in the terminal with dlake skills show.
Related
Every ERP and CRM integration · CRMPro (forward sync) · TxDownloaderPro (writeback sync) · AI agents & MCP
