Main Account mask, what is this? How is this helpful? These are some regular questions that linger around when we see this field in the Chart of Accounts form on Microsoft Dynamics AX.
Let me throw some light on it. While creating a number sequence we often configure the segments. We specify the segment as AlphaNumeric and provide a value as #####. The 5 hashes indicate that there are 5 running numbers. Quite often we also && which indicates that there 2 alphabets in the Number sequence segment.
# - indicates a number & - indicates an alphabet
Main Account mask is similar to the segments in a number sequence (except that it doesn’t automatically generate numbering like number sequence) and is used for validating the Main Account code assigned against the Mask specified in the Chart of Account and if a Main account code doesn’t match the Masking guidelines, AX will throw an error indicating mismatch in the masking guidelines.
For Example:
The CFO advises all the finance team to maintain the Ledger accounts (Main accounts) to have a account code that starts with the type of main account continued with 5 digits.
This can be done by keeping the Main account mask as &##### (as below)
If the does not follow this protocol while creating a main account, then system throws error as below:
![]()
The correct Main account code to be affixed is as shown in below screen
Ax Setup Main Account Number
for similar articles on Microsoft Dynamics AX you can follow my blog @ AX4ERP.blogspot.com
We have been answering a lot of questions lately about what the setting ‘Do not allow manual entry’ really is and how it reacts in different posting scenarios.
The setting applies only when manually entering the account value using a ledger account type in the general journal. So if you have posting profiles set up that would post to this account that would be allowed.
However, depending on what is set in the General ledger parameters, you may experience different behavior when this account is used. See the below screenshot for the other parameter that will affect the behavior, “Interrupt in case of error account”.
The following table lays out the posting behavior when using “Interrupt in case of error account” and “Do not allow manual entry”.
We hope this helps with setting up your posting and accounting policies and understanding how the settings on the main account and GL parameters affects your daily processes.
We came across an issue recently where the “Default account setup” Lookup form is listing Main Accounts from all Company Accounts. We are using Microsoft Dynamics AX 2012 CU-2. The selection in some queries brought unexpected results. For example: Under Accounts payable > Setup > Vendors > Vendor groups. Then select one Vendor and click “Default account setup”. The look up will then list the Main Accounts from all Company Accounts instead of only the current active Company Account.
The results are derived as a result of the where clause selection in Data DictionaryTablesVendDefaultAccountsMethodsnotSelectedLedgerAccountList method
We worked around the issue by changing one line of code in the notSelectedLedgerAccountList method from
Huawei bootrom password recovery software. To change the BootROM password on the BootROM menu, you must connect to the console port of the switch and log in to the switch through the console port. In any view, restore the default BootROM password. HUAWEI reset boot password The password used to enter the boot menu by clicking Ctrl+B will be restored to the default password, continue? Feb 18, 2014 To reset the BootROM password through the BootROM menu, you must connect to the console port and log in to the device through the console port. In any view, restore the default BootROM password [email protected].
…
outer join RecId from dimAttributeValueCombo where
dimAttributeValueCombo.DisplayValue mainAccount.MainAccountId && dimAttributeValueCombo.LedgerDimensionType LedgerDimensionType::DefaultAccount ![]()
…
to:
…
outer join RecId from dimAttributeValueCombo where
dimAttributeValueCombo.MainAccount mainAccount.RecId && dimAttributeValueCombo.LedgerDimensionType LedgerDimensionType::DefaultAccount
…
For completeness, the full method code and modified line is shown in the highlight below:
public server static List notSelectedLedgerAccountList()
{ MainAccount mainAccount; DimensionAttributeValue dimAttributeValue; DimensionAttributeValueCombination dimAttributeValueCombo; VendLedgerAccounts vendLedgerAccounts; List notSelectedFieldList = new List(Types::Container); recId defaultAccountHierarchyId = DimensionHierarchy::getHierarchyIdByHierarchyType(DimensionHierarchyType::DefaultAccount); recId mainAccountDimAttribute = DimensionAttribute::getMainAccountDimensionAttribute();
// Allow all posting types, so long as they are not closed
// Only add the combination if it doesn’t exist or doesn’t exist as a ledger dimension on the vendLedgerAccounts table while select MainAccountId, Name, Type from mainAccount order by MainAccountId where mainAccount.LedgerChartOfAccounts LedgerChartOfAccounts::current() && mainAccount.Type != DimensionLedgerAccountType::Total outer join RecId from dimAttributeValueCombo where //dimAttributeValueCombo.DisplayValue mainAccount.MainAccountId && //original code dimAttributeValueCombo.MainAccount mainAccount.RecId && //modified Code dimAttributeValueCombo.LedgerDimensionType LedgerDimensionType::DefaultAccount outer join RecId from vendLedgerAccounts where (vendLedgerAccounts.SummaryLedgerDimension dimAttributeValueCombo.RecId || vendLedgerAccounts.ClearingLedgerDimension dimAttributeValueCombo.RecId || vendLedgerAccounts.PurchasingLedgerDimension dimAttributeValueCombo.RecId || vendLedgerAccounts.PurchasingOffsetLedgerDimension dimAttributeValueCombo.RecId) notexists join dimAttributeValue where dimAttributeValue.DimensionAttribute mainAccountDimAttribute && dimAttributeValue.EntityInstance mainAccount.RecId && (dimAttributeValue.IsSuspended true || dimAttributeValue.IsBlockedForManualEntry true) { if (!vendLedgerAccounts) { notSelectedFieldList.addEnd([mainAccount.MainAccountId, mainAccount.Name, mainAccount.Type]); } } return notSelectedFieldList; }
Disclaimer:
This programming example is for illustration purposes only. Microsoft disclaims all warranties and conditions with regard to use of the programming example for other purposes. Microsoft shall not, at any time, be liable for any special, direct, indirect or consequential damages, whether in an action of contract, negligence or other action arising out of or in connection with the use or performance of the programming example. Nothing herein should be construed as constituting any kind of warranty.
Warehouse Setup Ax 2012
We have been answering a lot of questions lately about what the setting ‘Do not allow manual entry’ really is and how it reacts in different posting scenarios.
The setting applies only when manually entering the account value using a ledger account type in the general journal. So if you have posting profiles set up that would post to this account that would be allowed.
However, depending on what is set in the General ledger parameters, you may experience different behavior when this account is used. See the below screenshot for the other parameter that will affect the behavior, “Interrupt in case of error account”.
The following table lays out the posting behavior when using “Interrupt in case of error account” and “Do not allow manual entry”.
We hope this helps with setting up your posting and accounting policies and understanding how the settings on the main account and GL parameters affects your daily processes.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |