SAP Business One and Jira integration

What moves between them

The main flow is from SAP Business One into Jira. When purchase orders are created or updated in SAP Business One, ml-connector reads them via OData polling and creates or updates matching issues in Jira, tagged with the vendor name and PO number. Invoice and incoming payment records from SAP Business One flow the same direction, mapped to Jira issue fields so that operations teams see when suppliers are paid. The reverse flow from Jira back to SAP Business One is limited: comments and status changes in Jira can be read and logged in SAP Business One's notes or linked documents, but financial data never flows from Jira into SAP Business One because Jira has no accounting entities. Polling runs on a schedule you control, typically once per hour or after each batch of business transactions.

How ml-connector handles it

ml-connector stores both credential sets encrypted and maintains the SAP Business One OData session token, refreshing it when the 30-minute inactivity timeout expires or error code -5002 is returned. On the Jira side, it refreshes OAuth2 bearer tokens when a call returns 401, and it proactively refreshes webhooks 5 days before their 30-day expiry to prevent gaps in event delivery. Because SAP Business One is on-premise with no shared base URL, ml-connector accepts the full customer Service Layer URL (hostname, port, protocol) as a configuration parameter and validates all entity requests against that instance. Purchase orders, invoices, and payments are fetched via OData with $filter and $expand parameters to retrieve related vendor and line-item data in a single call, reducing round-trips. Custom fields in Jira are identified by their instance-specific ID, which ml-connector maps during initial setup. On the Jira side, issue descriptions are built as Atlassian Document Format (ADF) structures rather than plain strings. Because SAP Business One uses self-signed TLS certificates on many on-premise instances, TLS certificate pinning or validation may need to be configured per customer. Every record carries a full audit trail, so if a Jira webhook fails to deliver or SAP Business One is temporarily unreachable, the transaction can be replayed.

A real-world example

A mid-sized industrial distributor runs SAP Business One for purchasing, inventory, and financial reporting, and uses Jira to manage warehouse operations, supplier quality issues, and receiving workflows. Before the integration, the procurement team created purchase orders in SAP Business One and then manually created corresponding tasks in Jira for the warehouse and receiving teams to track shipments and inspect goods. When invoices arrived, the information did not automatically flow to Jira, so receiving teams had to look up invoices separately in SAP Business One if they needed to dispute or reconcile items. With SAP Business One and Jira connected, each new PO in SAP Business One automatically generates a Jira issue in the Receiving project, with the vendor, PO number, line items, and expected delivery date pre-populated. When goods are received and invoiced, Jira shows the payment status, so receiving and procurement can see the full lifecycle of each order without switching systems.

What you can do

• •Create and update Jira issues from SAP Business One purchase orders, with vendor, line items, and expected delivery dates pre-populated.
• •Sync invoice and incoming payment records from SAP Business One into Jira so operations teams see when suppliers are paid.
• •Refresh SAP Business One OData session tokens when they expire or time out, and refresh Jira webhooks before 30-day expiry to prevent gaps.
• •Map SAP Business One chart of accounts and profit centers to Jira custom fields so financial dimensions are visible to operations teams.
• •Poll SAP Business One on a schedule you control, with full retry logic and audit trails for every purchase order and invoice.

Questions

Which direction does data move between SAP Business One and Jira?

The main flow is from SAP Business One into Jira. Purchase orders, invoices, and payments in SAP Business One create or update issues in Jira so that operations teams see the same transactions. Comments and status changes in Jira can be logged back, but financial data never flows into SAP Business One because Jira has no accounting entities.

How does the integration handle SAP Business One's session token timeout and OData refresh?

ml-connector stores the OData session token encrypted and automatically refreshes it when the 30-minute inactivity timeout expires or SAP returns error code -5002. Transactions are retried under the same token or a fresh one, so temporary timeouts do not cause data loss.

What happens if a Jira webhook expires before ml-connector can refresh it?

Jira webhooks expire 30 days after creation or last refresh and must be refreshed via REST API. ml-connector proactively refreshes all webhooks 5 days before expiry, so gaps in event delivery are prevented. If a refresh fails, an alert is surfaced so the webhook can be manually renewed before it stops working.