2026.10 B1 InterCompany (October 5) Release

  • Updated

New

Service

  • The list of SAP B1 object types tracked per company (used to filter which transactions create InterCompany events) is now automatically recalculated on Service startup/restart to match the actual scenario and master data synchronization configuration, instead of always tracking a fixed list.
  • Companies now only track what they actually need, reducing unnecessary event in the queue that would inevitably end up with the ignored status; any previously untracked type a configuration change now requires is picked up automatically as well.

Financial Consolidation

  • The "Mass trigger synchronization" button will now open a small form that allows you to specify date ranges for posting, due and doc. date.  
  • These are optional, entering no values will search amongst all journal entries.
  • It will still display the number of journal entries found and prompt for confirmation.
  • The "Mass trigger synchronization" checks the tracking table rather than the events table, this also means that the two trigger buttons did functionally the same, and so have the prompt has been trimmed down to one trigger button.

Manual

  • Added a topic for VAT Group Mapping under Mapping.

Bug fix

Scenario Configuration

  • Changing an existing scenario's type to or from Financial Consolidation could leave the header/line field configuration pointing at fields from the previous scenario type, with no indication in the field grid that anything was missing. This caused synchronization to fail immediately with a generic SAP B1 error ("At least one amount is  required in document rows"). The field configuration is now correctly reset to that type's defaults whenever a scenario's type is changed.
  • Removed the "Skip lines with zero quantity when adding/updating purchase documents" option from the Dropship, Dropship with Stock, Warehouse, Invoice to Invoice and Credit Note to Credit Note scenarios. It had no effect: zero quantity lines were always skipped regardless of this setting.

Dropship with Stock

  • The "Update Tracking Number On Delivery" option had no effect. Updating a source delivery's tracking number is now synchronized to the delivery created in the target company, matching the equivalent option on the Dropship scenario.

Warehouse Scenario

  • Additional expenses were not being synchronized to A/P Invoice and A/P Reserve Invoice.

Was this article helpful?

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.