Subscriptions

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

After setting up the Topic, the next step is to create a Subscription for each Party in the receiving company/companies. You must create one Subscription per Party (sending company) you are receiving data from.

If you are setting up a Subscription in a multiple Business Central environment, using Azure Service Bus, you must run the Topic in the sending company before you are setting up the Subscription

Subscription card

  1. Choose 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 you do not wish to import. 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 allows you to control how data is imported and processed.

When you import a table, you can mapp a field to change the value in it. This is only possible if the field is included in the Topic message.

If you change or mapp a field, we recommend you use the Comment field to document your changes. The field Relation Table Caption specifies the table that is related to the field. If you have values in these fields, the value you import must exist in the related table in the receiving company.

You can map a field four ways, by Value, Filter, Fixed or Currency.

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

Currency mapping

Ensures proper handling of differing local currencies (LCY) between companies. Requires setup of 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 and mapped into the field.
  • 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 there are fields you must map to get the correct values on the projects in the receiving company.

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 ResponsibleIs it the same as in the sending company?
23Job posting groupIs it the same as in the sending company?
1011Invoice currency codeCurrencyIf you have an intercompany transfer pricing list in another currency than your LCY, always change the Mapping value to Currency. Read more about Currency mapping here.
2000Sell-to Customer No.FixedIf you don’t have the customer table as Master data, map to the sending company’s customer number in the receiving company.
14045651Resource Invoice typeValueIf the selling company have fixed price agreement with the customer, and the performing company need to maintain regular intercompany billings, mapp this field to T&M
14045655Item Invoice typeValueIf the selling company have fixed price agreement with the customer, and the performing company need to maintain regular intercompany billings, mapp this field to T&M
14045656Expense Invoice typeValueIf the selling company have fixed price agreement with the customer, and the performing company need to maintain regular intercompany billings, mapp this field to T&M
14045674Project Managerx PGSIs it the same resource as in the sending company?
14045753Time sheet currency codeCurrencyIf you have an intercompany transfer pricing list in another currency than your LCY, always change the Mapping value to Currency. Read more about Currency mapping here.
Table 1001 – Job task
Target Field NoTarget Field NameMapping valueComment
14045764Contract Type PGSValueIf the selling company have fixed price agreement with the customer, and the performing company need to maintain regular intercompany billings, you must map this field to T&M
14045709Project Manager PGSIs it the same resource as in the sending company?
Table 14045676 - Permissions PM

This table is not mandatory to transfer. If you don’t need the permissions from the sending company, you can delete the table.

Target Field NoTarget Field NameMapping valueComment
1NoIs it the same resources as in the sending company?

Time

Table 156 – Resource
Target Field NoTarget Field NameMapping valueComment
51Gen Prod Posting GrpIs it the same as in the sending company?
58VAT Prod Posting GrpIs it the same as in the sending company?

Project ledger entries

This is a preview feature that transfer resource, expenses and item ledgers between companies. It is to be tested in a Sandbox environment. Please contact support if you want to use it in a production environment.

Table 210 – Job jounal line
Target Field NoTarget Field NameMapping valueComment
1008Currency codeCurrencyRead more about Currency mapping here.
14045810Expense Payment TypeValueMapp the expense payment types you have in the sending company to the one you created for Intercompay purpose.

Test the setup

When you have created a topic and the corresponding subscription, try to send one entry in the sending company. In the receiving company you can run the subscription manually from the action Run subscription. When everything is working, you can set up a job queue that runs the subscription automatically.

Read more about setting up job queues here.

Update a Subscription after changing the Topic

If you have changed the field definitions on the Topic you must manually update the Subscription.

  1. Choose the 🔎 icon, enter Subscriptions (IDM), and select the related link.
  2. Go to Update Source fields on the Action tab.
  3. Open the Subscription card.
  4. Click on Subscription fields on the table you want to update.
  5. Go to the field you want to add.
  6. In Source field No you add the Table No (same number as in Target field No).