Generate New Number Sequence when Copying Journal Name

-
Rolling out entity (new company) in AX 2012 is more difficult than in 2009. There are some data that can’t be easily copied across. There are many ways of achieving this. But specifically in this article, we’re talking about copying the journal name. And yes, Journal Name can be copied across using the Standard AX Export Import binary file (not Data Import Export Framework).
The only issue with copying the Journal Name using the above method is the number sequence for the voucher series still referred to the originating company. Though it’s still working when you create journal with this name, but the next number sequence used isn't from the entity itself.


In above example, the voucher series is displayed correctly. We will find the anomaly when we perform right-click and view detail function. The company scope will be difference with the current company we working on. This is basically showing the data saved in the AOT as a result of an export import activity.
The script below is to help rectifying the issue by:
  • Create the new number sequence if the number sequence doesn’t exist in the company.
  • If the number sequence already exists in the company, then re-apply the correct record id in the journal name.
  • Ensure that the pattern of the new number sequence is the same with the originating (source) company.
static void TI_JournalNameVoucherNumSeqCreation(Args _args)
{
   NumberSequenceTable         numSeqTableFrom, numSeqTableTo;
   LedgerJournalName           journName;
   NumberSeqScope              numSeqScope;
   NumberSequenceReference     numSeqRef;
   int                         result;
   SysOperationProgress        progressBar;
   boolean compareScopeWithCompany(RecId _numSeqTable, DataAreaId _dataArea)
   {
       return NumberSequenceScope::find(NumberSequenceTable::find(_numSeqTable).NumberSequenceScope).DataArea == _dataArea;
   }
   boolean isSharedNumber(RecId _numSeqTable)
   {
       return NumberSequenceScope::find(NumberSequenceTable::find(_numSeqTable).NumberSequenceScope).DataArea == "";
   }
   ;
   ttsBegin;
   progressBar = new SysOperationProgress();
   progressBar.setCaption("Creating number sequence for journal Name");
   while select forUpdate journName
       /*where journName.JournalName == "GJ" ||
             journName.JournalName == "AJ" ||
             journName.JournalName == "BK" ||
             journName.JournalName == "CJ" ||
             journName.JournalName == "VI" ||
             journName.JournalName == "VP" ||
             journName.JournalName == "CR" ||
             journName.JournalName == "CWO" ||
             journName.JournalName == "FA" ||
             journName.JournalName == "FB" ||
             journName.JournalName == "FD" ||
             journName.JournalName == "FS" ||
             journName.JournalName == "IC" ||
             journName.JournalName == "SJ" ||
             journName.JournalName == "VA" ||
             journName.JournalName == "VR"*/ //put the filter if needed
   {
       if(!journName.NumberSequenceTable)
           continue;
       //check if the number sequence for voucher series is available for current company or if it's shared
       if( !compareScopeWithCompany(journName.RecId, curext()) && !isSharedNumber(journName.NumberSequenceTable) )
       {
           progressBar.setText(strFmt("Journal Name - %1", journName.JournalName));
           numSeqTableFrom = NumberSequenceTable::find(journName.NumberSequenceTable);
           //check if number sequence exists
           numSeqTableTo = NumberSequenceTable::findByNaturalKey(numSeqTableFrom.NumberSequence, NumberSequenceScope::findByNaturalKey(curext(), 0,0,0).RecId);
           if(numSeqTableTo)
           {
               journName.NumberSequenceTable = numSeqTableTo.RecId;
               journName.update();
               info(strFmt("Number Sequence %1 already exists, Journal name %2 is reassigned to %1", numSeqTableTo.NumberSequence, journName.JournalName));
               continue;
           }
           numSeqTableTo.initValue();
           numSeqTableTo.Format = numSeqTableFrom.Format;
           numSeqTableTo.AnnotatedFormat = numSeqTableFrom.AnnotatedFormat;
           numSeqTableTo.NumberSequence = numSeqTableFrom.NumberSequence;
           numSeqTableTo.Lowest = numSeqTableFrom.Lowest;
           numSeqTableTo.Highest = numSeqTableFrom.Highest;
           numSeqTableTo.Continuous = numSeqTableFrom.Continuous;
           numSeqTableTo.CleanInterval = numSeqTableFrom.CleanInterval;
           numSeqTableTo.Txt = strRem(numSeqTableFrom.Txt, NumberSequenceScope::find(numSeqTableFrom.NumberSequenceScope).DataArea) + curext(); //Change the number sequence description here
           numSeqTableTo.NumberSequenceScope = NumberSequenceScope::findByNaturalKey(curext(), 0,0,0).RecId;
           try
           {
             numSeqTableTo.insert();
             journName.NumberSequenceTable = numSeqTableTo.RecId;
             journName.update();
             result++;
             info(strFmt('created %1', numSeqTableTo.NumberSequence));
           }
           catch
           {
               info(strFmt("number sequence for journal name %1 can't be created", journName.JournalName));
           }
       }
   }
   ttsCommit;
   info(strFmt("%1 records created", result));
}


Comments

Post a Comment

Popular posts from this blog

Purchase Order Invoice Reversal in AX 2012

-
Image
There are couple ways of reversing the PO Invoice in AX 2009 and prior versions. However, there is a procedure that can’t be done in AX 2012. Reversing PO Invoice in AX 2009 can be done by directly entering minus quantity in “Receive now” field at the PO line that wanted to be reversed. Then proceed by posting a delivery note and invoice subsequently. This will reverse the delivery note/invoice on that positive PO line. This procedure, though has a tidy result, is no longer allowed in AX2012. User has to create separate negative PO line to do the reversal of the PO Invoice. User will get following message because both receive now and ordered quantity must have the same sign (either positive or negative). The procedure is well explained by Microsoft in following link https://technet.microsoft.com/en-us/library/hh454990.aspx
Read more

Load Ledger Transactions from Posted Journal Batch Number

-
We could easily use the load ledger transactions to retrieve transactions based on the "Journal Batch Number" in AX 2009. But that isn't the case in AX 2012. Some people found out that the Load Ledger Transactions function doesn't load anything when trying to retrieve transactions based on the journal batch number "Journal number" on above standard query doesn't refer to "Journal Batch Number". So that, the Journal batch number shouldn't be put on that field. Below shows you how to put the journal batch number query on the correct field. The field is available on the other table.
Read more

D365 Finance and Operations - REVENUE RECOGNITION FEATURE (based on IFRS 15)

-
Image
Microsoft, in Oct 2019, released Revenue Recognition feature for Finance module. I’ll give you a brief recap of what it is for and how we use the function in Dynamics 365 Finance and Operations (D365FO) Before jumping into the features, I’ll explain IFRS 15 in layman’s term (if you want to get more knowledge of IFRS 15 with accounting technical term you can google it). IFRS 15 is new reporting standard to set the new standard replacing the old accounting standard rules: IAS 18 (sale of services, sale of goods, and royalties) IAS 11 (Construction contracts) IFRS 15, became effective in Jan 2018, is expected to outline a standard rule on how the entity should recognize the revenue on the contracts. I’ll use the following examples to help me explain how the IFRS 15 works. Telstra sells a $100 plan/month for 12 months to a customer. The plan comes with a headset. Prior to IFRS 15, an entity may book (/recognize) the revenue for $100 per month over the period of 12 months. ...
Read more