Skip to main content

Number Sequences

 There are various setup that you may achieve with the number sequences.

Lets get in to detail on what functionalities we may use.

Which parameters you can setup in a number sequences: 

On number sequences, you may define various parameters;

  • You can setup number sequences as continuous.

In case of unexpected issues occur, system cannot recycle numbers automatically for continuous numbers. Run the cleanup process to recover the numbers.

  • You can set up pre allocation for performance, so number sequence will be allocated for use.
  • You can setup constant figures for smart coding.
  • You can define legal entity information for smart coding and it makes easier for reporting purposes (For consolidation etc.)

Number Sequences on journals: You can create several journal names which have different number sequences. So when you post a journal and check from the voucher transactions, you know which type of transaction is being posted.

Number sequences with date: You can setup a number sequence to be used within a date interval.

Number sequence groups: You can use the number sequence groups to differentiate numbers per processes. For example, if you select a number sequence group on an SO or PO, the invoice number can be differenciated per those PO or SO. Foe example you know which orders are internal and external directly looking at the number.

Use same number sequence: You may use the same number for similar process. For example, for better tracking, you can use the same number for the sales order invoice and its voucher. This applies not in all type of number sequences but for some specific processes like invoices and their vouchers.

Vendor Group Number Sequence: You can assign number sequences to vendor groups. 

I think what would be good is to have the number sequence setup for the item groups as well.

You may find details for number sequences from the link below:

https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/fin-ops/organization-administration/number-sequence-overview

Comments

Popular posts from this blog

Manage ERP with Success - Blockers of Success

  To manage an ERP process with success is not easy at all. Even there has been processes that have been published by companies, it is mostly depend on the people. In this blog , I am going to share the reasons I see as blockers of during the projects. This is not a scientific measure but just my opinions. Sales Team:  ERP project starts from even before the sales documents are finalized. So company needs (not user/not management etc.) need to be understood wisely and to be checked if the tools can manage these needs and details need to be documented in the contract. Expectations:  Unfortunately, ERP is a software but not a hardware. So expectation management is very important. If it was a hardware, then you will be able to return and to document specific details.  Project Team:  By project team, mostly we understand the consultancy firm but project team does consist of also from customer project managers, users, power users etc. All project team need to be well...

Allocation ways in D365 FO

 When we say allocations of expenses through accounts and dimension, there are various ways that can be used in D365 FO. In this blog you can find these ways and their differences from one to another. Cost Accounting Module:  If you do not need/require to post any transaction or you think that there will be too many transactions appear on voucher transactions, then you can use cost accounting module to report on your balances. This module works separate from the GL module. Data is transferred from GL module and you prepare your allocation rules in this module and do your reporting. also you can use this module for to report different versions. Allocation Rules : You can define allocation rules and within the period you want to use, system will allocate the balance to the relevant account and dimensions. The pros of this type is that, you can trigger and change the rules whenever you want to . The cons of this type is, you need to trigger each rule one by one, wait for the repo...

Fast Track Recognized Solution Architect

      You may be a fast track recognized solution architect. Fast track is best practices to succeed on the project.(Called Success by Design) This process is documented by the fast track solution architects. When applied to be a fast track solution architect, evaluation is done by D365 engineering team.      Earning Criteria The architect must be nominated by the partner Must have a minimum of 5 years of experience with Dynamics CRM or ERP products Must have a minimum of 3 years of experience as a solution architect Must be the lead architect on at least 2 FastTrack governed customer implementation projects Must be responsible for the architecture and design of at least 2 FastTrack governed customer implementation projects Even if you can not fill these requirements above, you are still able to read the detailed documentation from the links below to succeed. https://docs.microsoft.com/en-us/dynamics365/fasttrack/implementation-guide/overview https://www.d3...