Create a subscriptions

Learn how to setup Subscriptions, used for receiving data from other Business Central companies.

After setting up the Topic, create a Subscription for each Party in the receiving company or companies. Each Subscription corresponds to a Party from which data is received.

In a multiple Business Central environment using Azure Service Bus, run the Topic in the sending company before setting up the Subscription.

Subscription Card

  1. Select the 🔎 icon, enter Subscriptions (IDM), and select the related link.
  2. Enter the Party code for the sending company and select the related Topic.
  3. Pryme Intercompany Project only:
    • Inv. Setup template defines the default invoice template for intercompany projects. Leave blank to add templates manually.
    • Res. price template specifies the transfer pricing list for projects.
  4. Review and adjust tables under Subscription Tables. Delete tables that should not be imported. Re-add deleted tables if needed (limited to tables present in the Topic).
  5. Use Subscription Fields to modify field-level data processing, mapping, and rules.

Subscription Fields

Subscription fields control how data is imported and processed. When importing a table, field-level mapping is possible, provided the field is included in the Topic message.

When changing or mapping a field, use the Comment field to document the changes. The Relation Table Caption specifies the related table. If a related table exists, the imported value must be present in the receiving company’s table; otherwise, the record will not be imported.

A field can be mapped in four different ways:

TypeDescription
ValueOne-to-one mapping.
FilterConditional updates based on filters.
FixedAssigns a fixed value to all imported transactions.
CurrencyManages local currency conversions.

Currency Mapping

Currency mapping ensures proper handling of differing local currencies (LCY) between companies. Setup requires configuring the Currency Code for each Party and the LCY Code in the General Ledger Setup.

  • If the currency code in the subscription message is blank, the Currency Code from the Party code will be used.
  • If the currency code in the subscription message matches the Currency Code on the Party code, the currency field will be set to blank.

Subscription Fields in Pryme Intercompany Project

In the Pryme Intercompany Project app, specific fields must be mapped to ensure correct values in the receiving company’s projects.

Project (Table 167 – Job)

Target Field NoTarget Field NameMapping ValueComment
5Bill-to Customer No.FixedAlways map to the sending company’s customer number in the receiving company.
20Person ResponsibleVerify if it matches the sending company.
23Job Posting GroupVerify if it matches the sending company.
1011Invoice Currency CodeCurrencyUse Currency if an intercompany transfer pricing list exists in another currency.
2000Sell-to Customer No.FixedIf the customer table is not part of Master Data, map to the sending company’s customer number.
14045651Resource Invoice TypeValueMap to T&M if a fixed price agreement exists.
14045655Item Invoice TypeValueMap to T&M if a fixed price agreement exists.
14045656Expense Invoice TypeValueMap to T&M if a fixed price agreement exists.
14045674Project Manager PGSVerify if the resource matches the sending company.
14045753Timesheet Currency CodeCurrencyUse Currency if an intercompany transfer pricing list exists in another currency.

Job Task (Table 1001 – Job Task)

Target Field NoTarget Field NameMapping ValueComment
14045764Contract Type PGSValueMap to T&M if a fixed price agreement exists.
14045709Project Manager PGSVerify if the resource matches the sending company.

Permissions (Table 14045676 - Permissions PM)

This table is not mandatory. If permission from the sending company is unnecessary, delete the table.

Target Field NoTarget Field NameMapping ValueComment
1NoVerify if the resource matches the sending company.

Time (Table 156 – Resource)

Target Field NoTarget Field NameMapping ValueComment
51Gen Prod Posting GrpVerify if it matches the sending company.
58VAT Prod Posting GrpVerify if it matches the sending company.

Project Ledger Entries (Preview Feature)

This feature transfers resource, expense, and item ledgers between companies. Testing should be conducted in a Sandbox environment before production use. Contact support to enable it in a production environment.

Job Journal Line (Table 210)

Target Field NoTarget Field NameMapping ValueComment
1008Currency CodeCurrencySee Currency Mapping.
14045810Expense Payment TypeValueMap expense payment types for intercompany transactions.

Test the Setup

After creating the Topic and corresponding Subscription, test the setup:

  1. Send one entry from the sending company.
  2. Run the subscription manually in the receiving company using Run Subscription.
  3. When successful, configure a Job Queue for automated subscription processing.

For details on job queue setup, see Set Up Job Queues.

Update a Subscription After Changing the Topic

If changes are made to the Topic field definitions, update the Subscription manually:

  1. Select the 🔎 icon, enter Subscriptions (IDM), and select the related link.
  2. Navigate to Update Source Fields under the Action tab.
  3. Open the Subscription Card.
  4. Select Subscription Fields in the table to update.
  5. Locate the field to add.
  6. In Source Field No, add the Table No (same as Target Field No).