Intercompany

• 1: Setup and configuration
• 1.1: Before you start
• 1.2: Basic setup
• 1.3: Step by step Project, Time, Expense, Item
• 1.4: Parties
• 1.5: Topics
• 1.6: Create a subscriptions
• 1.7: Run topics and subscriptions
• 1.8: Set up Azure Service Bus
• 2: Process
• 3: Design Details
• 3.1: Topology
• 4: Walkthroughs: Intercompany (Master) Data Management
• 5: Pryme Intercompany Release Notes
• 6:

1 - Setup and configuration

Pryme Intercompany enables seamless data sharing between Business Central companies through Messages. This system is based on three core components: Parties, Topics, and Subscriptions.

• Parties: Business Central companies that exchange data with other companies via Messages.
• Topics: Messages published by one Party and made available for other Parties to subscribe to.
• Subscriptions: Mechanisms that allow a Party to receive data from a Topic.

Configuration Differences

Both apps follow the same process for configuring Parties. However, the setup of Topics and Subscriptions differs.

Pryme Intercompany Master Data App

• Does not include pre-configured templates.
• Data exchanges require manual configuration of Topics and Subscriptions, offering increased flexibility for custom use cases.

Pryme Intercompany Project App

• Includes pre-defined templates for Topics and Subscriptions that are tailored to project-related data (e.g., time entries, expenses).
• Simplifies the setup process and accelerates implementation for project-specific data sharing.

1.1 - Before you start

Before setting up Pryme Intercompany, ensure that the following key considerations are addressed to facilitate smooth implementation and integration.

Party Code

• All companies involved must agree on a unique intercompany partner identification code, referred to as the Party Code. This code helps identify each company within the system.
• Establish a consistent and scalable naming convention. For instance, instead of using only a land code (e.g., “UK”), combine it with a number, such as “UK10,” “UK11,” and so on.

Data Conflicts

Ensure there are no data conflicts before setting up the app. Review and update existing entries to prevent issues.

Key Areas to Check:

• Project numbers
• Resource codes
• Other shared references

Master Data

Determine how master data will be managed across the group. Decide whether one company will act as the central master data provider for the entire group or if each company will manage its own master data. In the case of a centralized approach, designate one company to provide the master data to the others.

Key Considerations:

• Tables to Transfer: Identify which master data tables need to be shared.
• Field-Level Restrictions or Filters: Ensure any necessary restrictions, filters, or field-level mappings are identified and implemented.
• Code Harmonization: Check if consistent coding schemes are used across the companies for master data. If not, align and update the codes to ensure consistency throughout the group.

If Pryme Intercompany for Projects is installed, exclude projects and resources from the master data, as these are managed by the app.

Related Tables

Ensure that related tables required for importing data are included in the master data setup. This will prevent data errors due to missing or incorrect data and save time during setup.

Transfer Time, Expense, and Item Entries Between Companies

The Pryme Intercompany Project App includes two predefined templates for transferring time entries and project ledger entries. These templates can be used individually or together.

Time Entries Template

Functionality:

• Transfers time entries to the External Time Entries table when timesheets are submitted by the performing company.
• The project manager in the selling company can preview the entries, approve them, and add comments in an approval flow for informational purposes only.
• After posting, project ledger entries are created in both the performing and selling companies.

Limitations:

• Only time entries will be transferred. Entries moved between projects using Move Entries or a Project Journal will not be transferred through intercompany automation, as they do not create time entries; only project ledger entries are created.

Project Ledger Entries Template

Functionality:

• Transfers posted time, expense, and item entries to the Project Journal. When posting these entries, Project Ledger Entries are created in the selling company.

Limitations:

• Preview and Approval: Project managers in the selling company will not be able to preview time entries before posting.

Combining Templates

To preview time entries (and use the approval flow) and also transfer expenses and item entries, use the templates together.

• Time Entries → Time and Resources
• Project Ledger Entries → Expenses and Item Entries

1.2 - Basic setup

Add your Party Code

Each company must have a unique Party Code for identification. A naming strategy should be agreed upon with all companies within the group to ensure consistency in Party code naming. Follow these steps to set it up:

1. Select the 🔎 icon, enter Pryme Intercompany Setup, and choose the related link.
2. Enter a Party Code in the My Party Code field.

Exclude a Dimension in the Intercompany Data

If local dimensions are used by your company (i.e., dimensions relevant only for a specific company) and should not be shared with other companies, they can be excluded from the Topic Message. Follow these steps:

1. Select the 🔎 icon, enter Dimensions, and choose the related link.
2. Set Skip for Intercompany (IDM) to On/Selected for any dimension to exclude.

Expense Payment Type

When using the Project Ledger Entries functionality to transfer expenses between companies, add an Expense Payment type to prevent expenses from posting to the general ledger. The general ledger will be updated when the Purchase Invoice is posted. This Expense Payment Type is specifically for intercompany transactions.

1. Select the 🔎 icon, enter Expense Payment Type, and choose the related link.
2. Create a new expense payment type, setting the Expense Payment Function to Company Paid and the Expense Posting to NONE.
3. Select the 🔎 icon, enter Project Expense Posting Setup, and choose the related link.
4. Create an Expense Code for each code and assign the newly created Expense Payment Type.
5. Complete the necessary fields. Hover over each field for a short description.

Permissions

Users who need to send projects to other companies must have the USER IDMYME permission.

1.3 - Step by step Project, Time, Expense, Item

When setting up Pryme Intercompany Projects, it is essential to follow a structured approach to ensure proper configuration of both sending and receiving companies for transferring projects and time entries. The process involves setting up Parties, Topics, and Subscriptions in the correct order. Below is a step-by-step guide to help with the setup process.

In Pryme Intercompany Projects, data can be transferred using two pre-defined templates. These templates can be used separately or in combination, depending on the types of data being transferred between companies. More details can be found here.

• Time Entries: This template is used for transferring time entries.
• Project Ledger Entries: This template includes time entries, as well as expenses and item entries.

For bi-directional data transfer, set up the Topics and Subscriptions in both companies.

Parties

1. Create a Party in Company A for Company B.
2. Create a Party in Company B for Company A.

Project

1. Create a Topic in Company A. Select the template for Projects.
2. Create a Subscription in Company B for Projects on the Party Code for Company A.
3. Review and update the table definitions.

Time (Alternative 1)

The pre-defined Time Entries template transfers resources and time entries. When a timesheet is submitted, the entries are transferred to External Time Entries, allowing a project manager to preview the entries. An approval flow is also available for informational purposes only.

1. Create a Topic in Company B. Select the template Time Entries.
2. Create a Subscription in Company A for Time Entries on the Party Code for Company B.
3. Review and update the table definitions.

Expense and Item Entries

If the Time Entries template is used and project ledger entries for expenses and items should also be transferred, use the Project Ledger Entries template for this purpose.

1. Create a Topic in Company A. Select the template for Project Ledger Entries.
2. Review and update the table definitions. Add a Condition on the Type field to include only G/L Account and Item in the data message.
3. Create Expense Payment Types in Company B and update the Expense Posting Groups.
4. Create a Subscription in Company B for Project Ledger Entries on the Party Code for Company A.
5. Review and update the table definitions.

Time (Alternative 2), Including Expenses and Item Entries

If project ledger entries for time, expenses, and items need to be transferred without the option for a project manager to preview the time entries, use the Project Ledger Entries template. With this template, project ledger entries are transferred to a project journal, where they can be posted.

1. Create a Topic in Company A. Select the template Project Ledger Entries.
2. Review and update the table definitions.
3. Create Expense Payment Types in Company B and update the Expense Posting Groups.
4. Create a Subscription in Company B for Project Ledger Entries on the Party Code for Company A.
5. Review and update the table definitions.

Summary Table

1.4 - Parties

A Party refers to a Business Central company that shares data with other companies. Each Party can send and receive data. All companies involved in data sharing must be set up as a Party.

Before setting up the Parties, ensure a consistent format for Party Codes is chosen. It is recommended to combine a land code with a number for uniqueness and clarity (e.g., UK10, UK11).

Set Up the Standard Party Code

1. Choose the 🔎 icon, enter Pryme Intercompany Setup, and then select the related link.
2. Enter the Party code in the My Party Code field.

Parties

Each company must have a unique Party code to identify it. Establish a consistent naming strategy and adhere to it.

1. Choose the 🔎 icon, enter Parties (IDM), and then select the related link.
2. Fill in the required fields. Hover over a field to read a short description.

Party Groups

A Party Group is a subset of parties that can be used in a Topic to restrict which companies are allowed to receive data.

1. Choose the 🔎 icon, enter Party Groups (IDM), and then select the related link.
2. Fill in the required fields. Hover over a field to read a short description.
3. Enter the code of the Parties that should be grouped under the Parties subpage.

1.5 - Topics

Topics are used for publishing data to other parties. Topics themselves do not send data directly but act as a notification system that alerts subscribers to pull data.

The Topic defines the types of data (tables and fields) that are available to be transferred to other parties. Conditions can be added to filter and control which data should be transferred.

Topic card

1. Choose the 🔎 icon, enter Topics (IDM), and select the related link. Fill in the fields as necessary. Hover over a field to read a short description. Some of the most important fields are as follows:

2. Open the Topic Tables action under Related.

Transfer time entries

Two predefined templates are provided for transferring time entries: Time entries and Project ledger entries.

Time entries

This template transfers both time and resources. Once time entries are submitted, they are transferred to the External Time Entries table in the receiving company. This enables project managers in the selling company to preview the entries. Additionally, an approval flow is included for informational purposes.

When time entries are posted in the performing company, project ledger entries are automatically created in both the selling and performing companies.

Project ledger entries

This template transfers time (excluding resources), expenses, and item entries. It creates transactions in a project journal, and when posted, project ledger entries are generated in the selling company. Unlike the Time Entries template, this option does not include preview or approval functionality when the timesheet is submitted in the performing company.

Both templates cannot be used simultaneously for time entries, as this will result in duplicate project ledger entries. However, the templates can be used in combination for different purposes:

• Time Entries: For transferring time and resources.
• Project Ledger Entries: For transferring expenses and item entries (add a Condition to only include Type g/l account and Item).

Topic tables

There is a difference between the two intercompany apps when setting up Topic tables:

• Pryme Intercompany Masterdata - Tables and table definitions must be added manually. By default, all fields are included in the data message unless specified otherwise.
• Pryme Intercompany Project - Predefined templates are available, with tables and table definitions already populated.

1. Select New and search for the table to add.
2. Fill in the fields as necessary. Hover over a field to read a short description. Some of the most important fields are as follows:

3. Go back to the Topic card and Set status to Ready.
4. Restart the company. The changelog will be updated with new and updated entries that will generate Topic records for the subscribers.

Transfer all entries in a table

The intercompany apps only transfer new and updated entries. To ensure consistency across all subscribing companies, transfer all entries in a table using the Topic Table -> Create Messages function. Key points to remember:

• Use this for Master data tables after setting up the Topic to synchronize data across companies.
• This action adds and updates entries but does not delete records in subscribing companies.
• If invalid records exist in subscribing companies, manual cleanup may be required.

Update a topic with new fields

To add a new field to an existing Topic, follow these steps:

1. Choose the 🔎 icon, enter Topics (IDM), and select the related link.
2. Set the Topic to On hold.
3. Open the Topic Tables action under Related.
4. Click on Included fields. Message Data Content (IDM) will open.
5. Go back to the Topic card and Set status to Ready.
6. Restart the company.
7. Add the field in the Subscription. See Updating a Subscription after changing the Topic.

1.6 - Create a subscriptions

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:

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)

Job Task (Table 1001 – Job Task)

Permissions (Table 14045676 - Permissions PM)

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

Time (Table 156 – Resource)

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)

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).

1.7 - Run topics and subscriptions

Once the Topics and Subscriptions are set up, data transfer can be done manually or automatically using a Job queue. In a sandbox environment, it is recommended to run Topics and Subscriptions manually, as the Job queue is set to On hold after each run.

Run Topics

The Schedule run on Changelog value in the Topic determines whether it should be run. If set to FALSE, the Topic must be started manually using Action -> Run Topic or scheduled through a Job queue.

1. Choose the 🔎 icon, enter Topics, and select the related link.
2. Go to Actions – Create Job Queue Entry.
3. Fill in the fields as necessary. Hover over a field to read a short description.
4. Set Status to Ready.

Run Subscriptions

Manually

1. Choose the 🔎 icon, enter Subscriptions (IDM), and select the related link.
2. Choose the Subscription to run and select Run Subscription under the Home action.
3. If a prompt appears about updating values, always choose the selected answer.

Job Queue

1. Choose the 🔎 icon, enter Subscriptions (IDM), and select the related link.
2. Go to Actions – Create Job Queue Entry.
3. Fill in the fields as necessary. Hover over a field to read a short description.

Schedule jobs to run automatically.

1.8 - Set up Azure Service Bus

When using multiple Business Central environments, you can use Azure Service Bus to transfer data between the companies. Azure Service Bus is a cloud-based messaging service that enables you to send messages between applications and services. Azure Service Bus supports a set of cloud-based, message-oriented middleware technologies including reliable message queuing and durable publish/subscribe messaging. For more information, see Azure Service Bus.

Before configuring the connection to Azure Service Bus in Business Central, a namespace must be created in Azure Service Bus. The namespace is the container for all messaging components in Azure Service Bus. The namespace is created in the Azure portal.

To create a namespace in Azure Service Bus

1. Register an application for API connection: Register an application (MS Learn)
   • Save the Application (client) ID for later
   • Create a Client Secret and save the secret value for later.
2. Create service bus namespace, see Create a namespace (MS Docs). It must be Standard tier or better.
   • Save the Name of the namespace for later
   • Save the Subscription Id where the Namespace was created for later
   • Under Access control (IAM), add the registered application from step 1 as Role, Azure Service Bus Data Owner: Authenticate and authorize an application (MS learn)

After completion you will have the following values to insert into Business Central:

• Directory (tenant) ID from Azure AD
• Application (client) ID from the created App Registration.
• Client Secret from the created App Registration.
• Subscription Id where the ASB Namespace was created
• Azure Service Bus Namespace name from the created Azure Service Bus Namespace

To set up Azure Service Bus in Business Central

1. Choose the 🔎 icon, enter Azure Service Bus (IDM), and then select the related link.
2. Fill in the fields as necessary. Hover over a field to read a short description.

To set parties to use Azure Service Bus

1. Choose the 🔎 icon, enter Parties (IDM), and then select the related link.
2. Select the party to set up for Azure Service Bus.
3. Select Azure Service Bus in the Data Transfer Type field.

2 - Process

Once Topics and Subscriptions are configured, intercompany transactions can be transferred automatically.

Projects

An intercompany project is created the same way as any other project. The project is only transferred when the companies to which the project should be sent are selected, even if the Topic publishes to all companies.

Steps to Send a Project to Another Company:

1. Choose the 🔎 icon, enter Project list, and select the related link.
2. Select the project to send. Navigate to Send to company under the Action tab.
3. Select the companies to which the project should be transferred.

Unmarking a company will stop updates to that company but will not delete the project.

Troubleshooting Missing Companies in the List:

1. Verify the receiving company is set up as a Party.
2. Confirm the Topic allows projects for that party.
3. Update the Subscription (IDM) in the receiving company.

If Allowed On-Demand Publish is set to FALSE on the Topic, all projects will transfer automatically without selection.

Time and expenses

The app provide two Topics/Subscription for transfering of time entries; Time entries and Project ledger entries. These can be used separately or in combination. If you use them in combination, time entries are transferred with Time entries, and expenses and item entries with Project ledger entries.

Time Entries

When submitting a time sheet in the performing company, time entries are transferred to the External Time Entries table. This table is for informational purposes only. All changes to entries must be made in the performing company.

Viewing External Time Entries:

1. Navigate to Project list -> Related -> IDM -> External Time Entries.
2. Navigate to Project Plan -> External time (Not posted) column.
3. Search for External Time Entries. This option allows viewing all External Time Entries for projects where the user is the project manager or responsible person.
   • Project executives can view all transactions across all projects (with filtering options to restrict the view).

Approval status and comments in External Time Entries are transferred and visible when approving time in the performing company. When entries are approved and posted in the performing company, project ledger entries are created in both companies.

Project ledger entries

This feature is in preview mode and should be tested in a Sandbox environment. Contact support if it is needed in a production environment.

This feature transfers time, expense, and item entries and enters them into a project or job journal. The journal can be posted automatically or manually when the Subscription is run.

There is no approval process for these entries, unlike Time Entries.

3 - Design Details

Intercompany (Master) Data Management enables Business Central Companies to share data. Data is serialized to Messages and organized in Topics by the Publisher. The Subscriber can then setup Subscriptions on the Topics thereby receive the data.

This section will cover the underlying thoughts and architecture behind IDM.

Messaging pattern

Data is transferred between Companies in so called Messages. A Message that is made available in a Topic by a Publisher is referred to as a Topic Message and a Message that has been received by a Subscriber is known as a Subscription Message.

IDM has been built with inspiration from the Publish-Subscribe pattern as well as the Client-Server pattern making it a hybrid that benefits from strengths in both models. The main sequence for new data to be published is as follows.

1. User changes some data.
2. Data change is registered by Publisher.
3. Publisher serializes changed data into Messages.
4. Publisher notifies Subscriber about new Messages.
5. Subscriber requests new Messages from Publisher.
6. Publisher returns new Messages to Subscriber.
7. Subscriber saves each received Message.
8. Subscriber registers information about consumed Messages with Publisher.
9. Subscriber deserializes and processes each Message.

The above flow is illustrated in the following sequence diagram.

The main sequence is a hybrid of Publish-Subscribe and Client-Server and the following table lists key features from each model which have been implemented in the general Messaging Pattern.

Publish-Subscribe

Messages are organized in Topics that are made available to multiple Subscribers. A Publisher posts new messages to the Topic and notifies Subscribers as illustrated on the following flow chart.

This allows for a decoupling between publishing new data and consumption, where Subscribers will receive the new data. Data is serialized and stored as Topic Messages before notifying Subscribers which has the following benefits.

• Messages can quickly be returned to Subscribers when needed as no further processing is required.
• Messages can be marked to only be published to a subset of Subscribers.

Each Topic can have multiple Subscribers and the Publisher does not necessarily need to know each Subscriber beforehand.

Client-Server

Data is only transferred when Subscribers requests new Messages from Publisher as shown the below illustration.

In this way the Subscriber can decide when data transfer should take place. The Topic is placed in the Publisher system to allow for the Topic to contain full information about the communications protocol which is managed by the Message Broker.

Message Broker

Functionality in IDM is grouped into the following three main areas.

IDM has been implemented with extensibility in mind and functions involving these three areas are placed in Codeunit Message Broker IDMYME. In this way it is possible to use any of the predefined interfaces as well as have a partner implement new ones to fit your specific needs while still making use of the overall IDM framework. Each implementation consists of a number of explicitly required functions defined by the AL interface as well as implicitly required Subscriber functions which allows for additional features and differentiations to be implemented with fallback to default functions.

The following sections will describe each of the three interfaces in detail.

Data Serialization

In Business Central data is stored as records in tables and can not be directly transferred to other Companies. Therefore when data is saved as Messages by the Publisher it is first serialized to text and when Messages are processed by the Subscriber it is deserialized back from text to data.

Serialization can be performed in a number of ways and the key point is that serialization and deserialization should be done in more or less the same way when both Publisher and Subscriber is a Business Central Company. IDM therefore provides an interface for Serialization that can both be defined on Topic and Subscription to ensure consistency during integration.

The technical name for the Data Serialization interface is IData Serialization IDMYME and the following table outlines it from a programming point of view.

IDM comes with a default Json Serialization but the Data Serialization interface can be extended to match your specific needs.

Data Transfer

In IDM, Data Transfer consists of three areas:

In all three areas, both Publisher and Subscriber must request and respond accordingly to ensure consistency. To help this along Data Transfer has been implemented in a single interface, IData Transfer IDMYME, that is defined on Parties (IDM) in by both Publisher and Subscriber.

and the following table outlines it from a programming point of view.

Message Processing

Each Subscription Message is processed by the Subscriber and the default behaviour is to map tables and fields more or less 1:1 resulting in data from Publisher being replicated to Subscriber. However, you might require some specific Message Processing where underlying data or procedures are taking into use and to support this the Message Processing interface has been provided.

The technical name for the Message Processing interface is IMessage Processing IDMYME and the following table outlines it from a programming point of view.

Enum Message Processing Type

The Role of the Publisher

A Publisher is a Party where a Topic has been created in the its company. The Publisher posts data to a Topic and notifies Subscribers about new Messages. When Subscribers requests new Messages then it is the Publisher that responds to those requests and returns new Topic Messages to Subscribers as well as Topic Metadata.

Topic

Published data is organized in Topics which have the following key features.

The Role of the Subscriber

A Party where a Subscription has been created in its company is considered as being a Subscriber. The Subscriber requests new Messages from a Topic at a Publisher and each Message is then saved and later on processed. When receipt is completed then the Subscriber register receipt of Messages back to the Publisher.

Subscription

When a Subscriber wishes to receive data from a Topic a Subscription is created meaning there is a direct correlation between a Topic from a Publisher and a Subscription. Subscription has the following key features.

3.1 - Topology

Single environment

Hub and spoke

flowchart TB
    Contoso --> Fabricam
    Contoso --> Northwind
    Contoso --> ProseWare

Mesh

flowchart LR
    Contoso <--> Fabricam
    Contoso --> Northwind 
    Fabricam --> ProseWare   
    Northwind <--> ProseWare
    Northwind --> Fabricam
    Contoso --> ProseWare

flowchart TB
    Contoso --Chart of Accounts--> Fabricam
    ProseWare --Items--> Northwind 
    Contoso --Chart of Accounts--> Northwind     
    Fabricam --Items--> ProseWare       
    Northwind --Resources--> ProseWare    
    Northwind --Resources--> Fabricam    
    Contoso --Chart of Accounts--> ProseWare    
    ProseWare --Items--> Contoso 

Multiple Environments

flowchart TB
    subgraph BC_Env_US
        direction LR
        Contoso 
        Fabricam
    end
    subgraph BC_Env_GB
        direction LR
        Northwind 
        ProseWare
    end
    ASB[(Azure Service Bus)]    
    Contoso<-->ASB
    Fabricam<-->ASB
    Northwind<-->ASB
    ProseWare<-->ASB

4 - Walkthroughs: Intercompany (Master) Data Management

Create Party

This video shows how to create a Party to allow Business Central companies to interact

Create Topic

This video shows how to create a Topic to publish data to Subscribers

Create Subscription

How to create a Subscription to receive data from a Publisher

Transfer Data

How to transfer data between two Business Central companies

Publish Data Manually

How to publish existing data manually without the need for any data to change

Process failed Message

How to process a failed Subscription Message and two ways of solving validation errors

5 - Pryme Intercompany Release Notes

3.0 (June 2024)

Application enhancements

External time approval

When external time entries are received, someone in the receiving company must review the entries before final approval in the performing company. An approval status and comment can be set on the external time entry. This will then be transferred back to the original time entry, so the approver of that time entry will know if the time entry can be approved or needs changes.

Fixes and minor adjustments

• #118 Let the user if you have not filled in the options in Project ledger Entries subscription
• #123 Error when you send a project without having the admin permission set

2.7 (May 2024)

Application enhancements

Automatic currency mapping

When sending records between companies with different currencies, the system can automatically map the local currency codes.

The mapping type Currency can be used on subscription fields related to currency. The system will then automatically map a blank currency code to the local currency code of the sending party. Records with a currency code matching that of the receiving party will be mapped to blank.

The field “Currency Code” on each party must be defined as well as the “LCY Code” on the general ledger setup.

Fixes and minor adjustments

• #101 Time sheet currency code is not used when creating the PLE

2.6 (April 2024)

Application enhancements

Easier creation of parties

The Parties page have been restructured. When creating a new party, the system will suggest a name based on the company name.

A new field “My Party Code” have been added to the Pryme Intercompany Setup page. This field is used to set the default party code for the company. The party code is used to identify the company in intercompany transactions.

Conditions for sending records

Previously, the conditions on a topic limited which records were sent to the receiving company when using the “Create Messages” action.

Now the conditions always control which records are sent. If a record has passed the conditions and thus have been sent, it will always be sent in the future even if it no longer passes the conditions. This is needed to support scenarios like conditions based on a status field that is updated after the record is sent.

Easy update of subscription fields

When fields are added to a subscription, the corresponding topics will often need to have the fields added as well. Previously it was not obvious how to do that.

A new action “Update Subscription Field” have been added to the Subscriptions page, the Subscription page and the Subscription Tables page. This action will add the fields to the topics.

Transfer project ledger entries (PREVIEW)

Project Ledger Entries can now be transferred between companies. A topic set up with “Project Ledger Entries processing type will transfer the entries to the company where the project originated. The entries are either automatically posted or created as journal lines for manual review and posting.

Conditions can be set up to control which entries are transferred, like only expense or items. By default, the entries are transferred with the price becoming the cost.

Note that the Time Entries process will still post project ledger entries to the receiving company. So if the Time Entries process is used, the Project Ledger Entries process should not be used for resource entries. In a future version there will be an option to not post external time entries to the project ledger.

This is a preview feature and to be tested in a sandbox environment. Please contact support if you want to use it in a production environment.

Fixes and minor adjustments

• External time entries now use the quantity to invoice as the quantity to post. This aligns better with the final IC invoicing.
• Fixed price tasks are now converted to chargeable T&M tasks in the receiving company.
• The External Time Entries page now filters the entries based on project permissions.
• The “Send to Company” action have been added to the Project Card and Project Plan.
• #96 Recreating a subscription with a default fixed mapping fails
• #98 Lookup in subscription mapping to wrong table
• #106 You need ADMIN IDMYME to send a project through intercompany

2.5 (February 2024)

Application enhancements

Manage subscriptions in a single card

Subscriptions can now be managed from a single card showing both general settings and the included tables. This makes it easier to see the status of a subscription and to manage the subscription. Special options for different proccessing methods are also managed on the card. The card is available from the Subscriptions page.

Apply a price template to new IC projects

When a new intercompany project is created, a price template can be applied to the project. This makes it easier to ensure that the project is set up correctly from the start. The price template is selected on the Subscription Card page.

Apply an invoice setup template to new IC projects

When a new intercompany project is created, an invoice setup template can be applied to the project. This makes it easier to ensure that the project is set up correctly from the start. The invoice setup template is selected on the Subscription Card page.

More consistent mapping of fields with better performance

The mapping of fields between the sending and receiving companies is now more consistent and has better performance. The default mapping type in subscriptions is now “None”. This relieves the system from unnecessary checking if a mapping exists and makes it easier to understand the mapping. A new mapping type “Fixed” has been added. This is used when the field is always the same receiving companies independent of the value in the sending company. Effectively this can replace the use of mapping with filter from * to a value, but will perform better.

Fixes and minor adjustments

• #68 Include “Timesheet PGS” for Resource and also way set as false.
• #85 Default retention policy in new installations set to 2 months.

2.4 (January 2024)

Application enhancements

Subscription progress

The progress of a manual subscription run is now shown from the Subscriptions page. This makes it easier to see the progress of a run and to identify any errors.

External time entries in project plan

External time entries that are not yet approved and posted should be visible to the PM directly without the need to open the list of external time entries. A column in the project plan “External Time (Not Posted)” that specifies the total amount of time on external time entries that are not yet approved and posted has been added.

Fixes and minor adjustments

• #62 Problem with dimensions on tasks
• #63 Tasks received via IC can have too many dimensions
• #64 New customer in sending company stops the subscription in the receiving company
• #53 Topics - Auto Init Subscriptions doesn’t work
• #55 External Time Entries - Filter setting is not correct in view Not Posted
• #76 Time entries on Fixed price becomes chargeable when running subscription
• #81 Copying a company with Azure Service Bus active can deactivate Azure Service Bus
• #66 Special permissions are needed to allow logging changes to the Changelog table

2.3 (November 2023)

Application enhancements

The list of data content fields now allows searching. This makes it easier to find fields in long lists.

Fixes and minor adjustments

• #34 Filter is not working correctly in Topics
• #35 General fit-n-finish. Included Fields in subscription tables is renamed to Subscription Fields. Source Data Content in subscription tables is renamed to Source Fields.

2.2 (September 2023)

Application enhancements

Skip dimensions for intercompany data

Specific dimensions can be omitted for intercompany data. This is done by setting the Skip for Intercompany (IDM) field on the Dimensions page.

Control re-publishing of intercompany data

When publishing records tables that are also in subscriptions, there is a risk that a received record is published again. This can lead to loops. To avoid this, the new default is that received records are not published again. This can be overridden using the “Allow Republishing” field on the Topic Tables page.

Fixes and minor adjustments

• #28 Can not open Topics wizard from IDM role center

2.1.1 (September 2023)

Fixes and minor adjustments

• #6 All dimensions are included for Projects, Tasks and Resources [Intercompany Project only]
• Table relations are shown for subscription fields
• Option in Changelog Setup IDM to only log modification when tracked fields are changed. Experimental

2.1 (August 2023)

Application enhancements

Intercompany Project app

New app with predefined processing for intercompany projects and time.

Fixes and minor adjustments

• Preview posting breaks when a topic table is modified during posting.

6 -