Skip to main content

Generate Number Series from one Company and use it in another company

When dealing with Number Series where the Intercompany Documents are created automatically using the code, using standard number series generation Codeunits cause problems. In this blog, I'll be explaining why this issue is caused and how to resolve such issues.

  • Microsoft Dynamics NAV / Business Central
  •  VS Code 
  • AL Language Extension

  • Issue:
Let's say I'm logged in as user of Company B. When I create Sales Order in current company, I need to create Purchase Order in target company say Company A.
When I use the Number Series declared on Company B's Purchase and Payable Setup for Purchase Order, the system either gives an error that Number Series does not exist or number generated is out of sync as Number Series are stored on Per Company basis. This results in overlapping of next PO number to be generated.

  • Cause of the Issue:
NoSeriesManagement Codeunit 396 works only with the No. Series for the current company. Because of this if the No. Series with same code is present, the system generates No. Series which is completely different than that of the Company B. Also, there is no synchronization mechanism available out of the box to do the Intercompany No. Series sync.

Create the same Number Series in both the entities:
The Number Series is to be created in the primary company(Company A). The code mentioned below will automatically create the number series in the target company(Company B) from Company A.

Code to automatically Insert No. Series 

Prior to Creating Number Series

After the creation of Number Series

Modifying the Number Series back to Company A from Company B:
Using this function, I modified the newly created number series back to the original company.

Declare the Number Series and CompanyName to be used in Setup:
In Company A, I've created Number Series in General Ledger Setup. Using this No. Series declared in Company A use this No. Series to create Purchase Order in the same company through Company B.

Use ChangeCompany() to the target company(Company B) where you want to create the document. Modify the Number Series Line from Company B in Company A using a function.

Code to copy number series from Company A to Company B, generate the new number series and modify the number series back in Company A from Company B

In this way, we can generate a number series for one company from another company.


Anonymous said…
Maybe it is easy and more correct if you could copy the GetNextNo3 function and SetNoSeriesLineFilter copy to your local report or code unit and u could change the tables changecompany property and then managed it easily rather than searching and filtering data manually table level.
The task to accomplish is to have number series in both the companies to be in sync.
Importantly, if I create PO from company A with PO No. PO0001 and when I generate intercompany PO from Company B into Company A, it is needed for me to continue with the number series. Secondly, GetNextNo3 only work when you have Number Series defined in the Company B and without the No. Series in sync, there will be an error saying that the number already exists in Company A.

Popular posts from this blog

Understanding and How to use APIs Business Central - 2

Introduction: In my last blog post ( Business Central API -1 ) on Creating API in Business Central, we discussed all the commonly used properties of the page, query, and controls like field and data-item. In today's blog, we will be diving deeply into the validation of the data passed through the API endpoint, how it enters into the source tables and is manipulated to be inserted/modified into single or multiple tables. Also, I will be demonstrating how APIs are to be used. Pre-requisites: Microsoft Dynamics Business Central (SaaS) VS Code( ) AL Language Extension( ) API V1 from Business Central On-Premise DVD Books & References: API V1 from Business Central On-Premise DVD API(V1.0) for Business Central ( Click Here ) API(Beta) for Business Central ( Click Here ) Theory: Understanding API in Business Central 1. BINDSUBSCRIPTIONS: Use to trigger IntegrationEvent for the Codeunit stated

Enum Object in Business Central - How to create and how to extend!

Introduction: Since the dawn of Business Central Era (2nd April 2018 - Today), there are many new data types introduced by Microsoft. One such data type is Enum(Enumeration). Essentially, what enumeration is having a single select value with multiple options at a given time! Well, I know what your thinking what about the 'Option' data type. Anyways, enough of talking let's just dive in! Disclaimer:   The knowledge in this blog is true and complete to the best of authors and publishers knowledge. The author and publisher disclaim any liability in connection with the use of this information. Pre-requisites: Microsoft Dynamics Business Central (SaaS or On-Premise) VS code with AL Language extension Code: 1. Enum as an Object: Just like Tables and Pages, Enum behaves like an Object. Enum Object Note that Extensible means that the Enum Object can be extended in another module. By default, this property is set to TRUE. Enums created in a module(App), ca

Creating APIs in Business Central - 1

Introduction: While writing a blog on Automated Testing in Business Central, I was going through sample apps provided by Microsoft and realized that the complexity is nowhere close to what examples Microsoft has provided on In this blog, I will try to explain how APIs work and how to be creative with the implementation. Also, an API which were in beta are finally out with version V1.0 in the April 2019 release let's see some important key things from development aspects. This blog is going to be theoretical one kindly bear with me. Pre-requisites: Microsoft Dynamics Business Central (SaaS) VS Code( ) AL Language Extension( ) API V1 from Business Central On-Premise DVD Books & References: API V1 from Business Central On-Premise DVD API(V1.0) for Business Central ( Click Here ) API(Beta) for Business Central ( Click Here ) Solution: Key Requirements: API source table