Skip to content

Enterprise Suite - Intercompany

Enterprise Suite - Intercompany for Business Central Cloud

  • Released version: 1.4.1.0

Two new read-only API pages have been introduced to enable cross-company status checks before performing critical operations. The Purchase Order Status Read API allows the warehouse company to verify the status of a linked IC Purchase Order in the sales company, and the Sales Order Status Read API exposes the status and IC status of a Sales Order for cross-company validation.

What has been done:

  • Added IC PO Status Read API XTE — a read-only API exposing Purchase Order number and status (Open/Released) for cross-company queries
  • Added IC SO Status Read API XTE — a read-only API exposing Sales Order number, status, and IC Status for cross-company queries
  • Both APIs are read-only (no insert, modify, or delete allowed) and follow the standard OData/API pattern

Usability notes:

  • The warehouse company can now safely check whether a linked IC Purchase Order is Released before attempting to delete a warehouse Sales Order, preventing accidental data loss
  • The Sales Order status API enables the sales company to expose order state to partner companies without granting broad data access
  • No configuration required — the APIs are available immediately after upgrade

[Feature] Warehouse Sales Order Cascade Deletion

Section titled “[Feature] Warehouse Sales Order Cascade Deletion”

A new API endpoint has been added to the warehouse company that allows the sales company to trigger deletion of a linked warehouse Sales Order as part of a cascade deletion flow. The API validates that the Sales Order is in Open status before deleting, preventing deletion of Released orders.

What has been done:

  • Added IC Whse SO Delete API XTE — a POST-based API that receives a warehouse SO number, validates its status, and deletes it if Open
  • Added IC Whse SO Delete Buffer XTE — a temporary buffer table used by the delete API to pass the warehouse SO number and return a result message (Deleted, NotFound, or error)
  • The API returns a clear error message if the warehouse Sales Order is in Released status, instructing the user to reopen it first

Usability notes:

  • Users can now delete a Sales Order in the sales company and have the corresponding warehouse Sales Order automatically deleted in the warehouse company — eliminating the need for manual cleanup across companies
  • If the warehouse Sales Order has already been Released, the deletion is blocked with a clear error message, protecting data integrity
  • The cascade deletion respects the order lifecycle — only Open orders can be deleted remotely

A new codeunit handles the creation of Intercompany Return Orders via API. When a Sales Return Order is created in the sales company, the system can automatically create a corresponding Purchase Return Order in the partner (warehouse) company using the existing IC Partner API infrastructure.

What has been done:

  • Added IC Return Handler XTE codeunit that creates IC return orders via the partner API using OAuth2 authentication
  • The handler looks up the active IC link from the original Sales Order, acquires an access token, builds the return order JSON payload, and posts it to the partner’s Purchase Order API endpoint
  • Full telemetry logging is included for traceability

Usability notes:

  • Return order processes are now automated across IC partner companies, reducing manual re-entry and the risk of mismatched return documents
  • The return order creation follows the same secure OAuth2 authentication pattern as all other IC API operations
  • Users receive a confirmation message with the created return order ID upon successful creation

[Feature] Cross-Company Inventory Lookup with Item Availability by Event

Section titled “[Feature] Cross-Company Inventory Lookup with Item Availability by Event”

A comprehensive cross-company inventory visibility feature has been introduced. Users can look up real-time inventory levels and lead times from IC partner companies directly from Sales Order lines. A dedicated Item Availability by Event page provides a full timeline view of partner inventory, including planned receipts and demand.

What has been done:

  • Added IC Inventory Lookup XTE codeunit with caching (30-second TTL) for efficient cross-company inventory queries, supporting both standard items and item variants
  • Added IC Item Avail. by Event XTE page — a custom worksheet page that wraps the standard Business Central Item Availability by Event calculation pipeline, supporting cross-company URL-based opening
  • Added IC Avail Page Buffer XTE table — a per-user buffer table that stores item context for the availability page, solving the BC platform limitation where URL filters cannot be applied to temporary source tables before OnOpenPage runs
  • Added Inventory Page Data XTE table extension — adds an Item No. field to the standard Inventory Page Data temporary table to enable URL filter parameter passing
  • Added IC Avail Buffer API XTE page and IC Avail Buffer Cleanup XTE codeunit for buffer management and stale record cleanup
  • Added IC Availability Helper XTE codeunit for coordinating availability lookups

Usability notes:

  • Sales order processors can now view real-time inventory availability at the IC partner (warehouse) company without leaving Business Central or switching companies
  • The Item Availability by Event page shows a full timeline of supply and demand at the partner, enabling better promise dates and order decisions
  • Inventory data is cached for 30 seconds to balance performance with freshness — repeated lookups within the cache window are instant
  • Variant-aware lookups are supported, so companies using item variants get accurate availability per variant

[Feature] Advanced Mapping Engine with Full UI

Section titled “[Feature] Advanced Mapping Engine with Full UI”

A complete mapping management system has been introduced, providing a structured way to define and manage item, customer/vendor, and dimension mappings between IC partner companies. The mapping engine is accessible through dedicated list and card pages.

What has been done:

  • Added IC Mapping XTE table and IC Mapping Dimensions XTE / IC Mapping Variants XTE sub-tables for storing item, customer/vendor, dimension, and variant mappings
  • Added IC Mapping Engine XTE codeunit for resolving mappings during IC order processing
  • Added IC Mapping List XTE and IC Mapping Card XTE pages for managing mappings through the Business Central UI
  • Added IC Mapping Var. Subpage XTE for managing variant-level mappings within the mapping card

Usability notes:

  • Administrators can now define and maintain all IC mappings (items, customers, vendors, dimensions, variants) through a dedicated UI — no manual table editing required
  • The mapping engine automatically translates item numbers, customer/vendor codes, and dimensions when creating IC orders, ensuring data consistency across companies
  • Variant mappings allow companies with different variant structures to exchange orders without manual translation

[Feature] Linked Orders Management and PO Flow

Section titled “[Feature] Linked Orders Management and PO Flow”

A full linked order management system has been introduced, providing complete lifecycle management of intercompany order relationships. This includes automated Purchase Order creation, Sales Order creation at the warehouse company, and custom data storage for extended order information.

What has been done:

  • Added ICLinkedOrder XTE table for tracking relationships between Sales Orders and Purchase Orders across companies
  • Added IC Order Creator XTE and IC SO Creator XTE codeunits for automated creation of linked IC orders
  • Added IC PO Flow Manager XTE codeunit for managing the full Purchase Order flow lifecycle (Auto, Manual, and Requisition modes)
  • Added IC Purchase Grouping Buffer XTE table for grouping purchase lines during order creation
  • Added IC Custom Data Mgt XTE codeunit and IC Link Details FactBox XTE page for storing and displaying extended order data
  • Added RunCheckOnStatus XTE codeunit — a singleton flag that allows internal processes to skip status validation checks when needed

Usability notes:

  • The full order link lifecycle is now managed automatically — from Sales Order release through Purchase Order creation, status synchronization, and deletion
  • Three PO creation modes are supported: Auto (PO created automatically on SO release), Manual (user-initiated), and Requisition (via requisition worksheet)
  • The IC Link Details FactBox provides at-a-glance visibility of linked orders directly on the Sales Order and Purchase Order pages
  • Custom data storage allows partners and developers to attach additional context to IC order links without modifying core tables

[Feature] Role-Based Security with Four Permission Sets

Section titled “[Feature] Role-Based Security with Four Permission Sets”

A complete role-based security model has been implemented with four permission sets following the principle of least privilege.

What has been done:

  • Added IC ADMIN XTE — full administrative access to all IC configuration, setup, and data
  • Added IC USER XTE — operational access for day-to-day IC order processing
  • Added IC VIEW XTE — read-only access for monitoring and reporting
  • Added IC AUDIT XTE — access to audit logs and telemetry data
  • Added XTE All XTE — combined permission set for development and testing environments

Usability notes:

  • Administrators can now assign the appropriate permission set to each user role, ensuring users only have access to the IC functionality they need
  • The four-tier model (Admin, User, View, Audit) maps to common organizational roles and simplifies permission management
  • Existing users should be assigned the appropriate permission set after upgrade
  • No breaking changes — upgrading from 1.3.2.0 to 1.4.1.0 is straightforward
  • After upgrade, assign the new IC permission sets to users according to their role (IC ADMIN XTE, IC USER XTE, IC VIEW XTE, or IC AUDIT XTE)
  • The new mapping UI is available immediately — existing mappings configured via other means should be reviewed and migrated to the new mapping tables
  • The IC Avail Page Buffer cleanup job runs automatically; no manual configuration is required