Subledger entries are not transferred to ledger Dynamics 365 F&O, but doesnt reflect in the Subledger entries not yet transferred

 There have been several instances in D365 FO where the "sub-ledger entries not yet transferred" form is empty but the ledger entry has not got posted yet.

In order to identify such cases Microsoft has provided the below temporary fix through an SQL query. Good news according to Microsoft is that versions after PU37 will not have this subledger issues any longer. 

--IDENTIFY THE VOUCHERS THAT WERE MARKED FOR TRANSFER BUT THE BATCH JOB FAILED IN MIDDLE OF TRANSFER --

SELECT * FROM SUBLEDGERJOURNALENTRY SJE WHERE SJE.TRANSFERID != 0
AND NOT EXISTS(SELECT NULL FROM SUBLEDGERVOUCHERGENERALJOURNALENTRY SJV WHERE SJV.VOUCHER = SJE.VOUCHER AND SJV.VOUCHERDATAAREAID = SJE.VOUCHERDATAAREAID)

--FIX THE ENTRIES THAT ARE STUCK --

UPDATE AE
SET AE.STATE = 2
FROM ACCOUNTINGEVENT AE
JOIN SUBLEDGERJOURNALENTRY SJE ON SJE.ACCOUNTINGEVENT = AE.RECID AND SJE.TRANSFERID != 0
AND NOT EXISTS(SELECT NULL FROM SUBLEDGERVOUCHERGENERALJOURNALENTRY SJV WHERE SJV.VOUCHER = SJE.VOUCHER AND SJV.VOUCHERDATAAREAID = SJE.VOUCHERDATAAREAID)

 

UPDATE SJE
SET SJE.STATUS = 0,
SJE.TRANSFERID = 0
FROM SUBLEDGERJOURNALENTRY SJE WHERE SJE.TRANSFERID != 0
AND NOT EXISTS(SELECT NULL FROM SUBLEDGERVOUCHERGENERALJOURNALENTRY SJV WHERE SJV.VOUCHER = SJE.VOUCHER AND SJV.VOUCHERDATAAREAID = SJE.VOUCHERDATAAREAID)

Automatic allocations from GL in D365

Most of you are aware of Allocation rules in AX 2012/ Dynamics 365. Instead of an allocation journal at the month/ period end, it can be automated in the system to allocate a specific percentage across GL accounts and Dimension segments. An allocation rule can be setup and attached right in the Main account setup itself.

For example, All the audit related expenses are debited to ‘Audit expense’ in the normal accounting process and it needs a re-allocation to ‘Audit-Tax’ and ‘Audit-Financial’ based on some criteria. Instead of manual re-allocation or running allocation at month-end it can be setup to allocate simultaneously.

Add Legal entity overrides in the Main account form for the Company in discussion

Flag Allocation check box on Legal entity overrides

Once flagged Allocation terms button on the ribbon above it will get enabled

Click on Allocation terms to create allocation rule:

You will see

-        Percentage of allocation

-        Source criteria setup and

-        Destination criteria setup

To continue with the example, allocate to Audit expense to 70% to Audit-Financial and 30% to Audit-Tax.

70% to Audit-Financial

30% to Audit-Tax

Close the form to complete setup.

Post a transaction to see the postings

Post an amount of $1000 to Audit expense

Verify the voucher after posting. It posts to the above account and then allocates within the same voucher. See the allocations 70% to Audit-Financial and 30% to Audit-Tax

How to attach files/ documents after posting Journal (General, Invoice, Payments and Expense) in Dynamics 365 (D365)

General functionality available in Dynamics 365 (D365):

D365 provides a feature to attach documents of various business types when a journal is created from any module. Click on the paper clip button as shown below to open attachments work space

Attachments option is available as long as the journal is not posted

Once the journal is posted, New button in attachments form gets disabled

Most of the business will require to attach documents even after posting journals for Audit purposes. In order to do this, respective journal tables have to be enabled in Active documents tables. Follow the steps to enable journals for attachments even after posting

1. Navigate to Organization and administration > Document management > Active document tables, Click to add required table names in the list. Table names for journals are
            a. LedgerJournalTable
            b. LedgerJournalTrans

2. Flag "Always enabled" check box

Once the setup is complete, Attachments get enabled even after posting journals

D365 error "The number of dimension values specified is different from the number set up in the active format for data entities"

Data management errors in D365:

In AX 2012 Source data format setup contained Financial dimension format for data imports. However in Dynamics 365 (D365), Data management doesn't have any setup for dimensions format. It has to be setup in General ledger > Chart of accounts > Dimensions > Financial dimension configuration for integrating applications

Select "Ledger dimensions integrations" as shown in the image. In Financial dimensions grid select dimensions from the list and arrange in the required format.

Check the order and use dimensions in the same order in source files for data imports.

This setup will resolve the error

Finally fixed: Product Receipt cannot be cancelled if a line has multiple Batch numbers

This is one peculiar issue that has been bothering us quite some time now. It was present in AX 2012 and well into Microsoft Dynamics 365 for operations.

When a purchase is made and the product has multiple batch numbers, we use the split functionality in the Item arrival journal to split the quantity and assign batch number.

The problem comes when we want to cancel the Product receipt. When we try to cancel the product receipt with a line that has a split, The product receipt cancels only partially.

Finally, we reported the issue with Microsoft and our dedicated friends at Microsoft decided to fix this issue outright. Enclosed below is the Repro steps of the issue that we reported with Microsoft Dynamics team

Repro Steps for Complete Product Receipt not cancelled when split exists

The below is the Fix provided by Microsoft (Available through LCS- Hotfix# KB 3214547)

KB 3214547Partial Product Receipt cannot be cancelled if item quantity on item arrival journal is split with different batch numbers

Credits to Chandu Naresh (Me), Paul Dipankar & Nikhil Pujar for having worked together in identification of this bug in Microsoft Dynamics 365 for operations and reporting to Microsoft team.

Note: This issue and the fix is relevant to customers using tracking dimensions such as Batch Number, Serial Number or Consignment

Dynamics AX forms support multiple language scripts typing (Unicode)

Many customers often inquire if AX supports non-Latin scripts in the forms (for example: Sales order, Customer master, Product master, Fixed asset master etc.,) while using English as the primary language for the AX implementation.

YES

This is very much feasible in AX. Unicode has eased many things and fortunately Microsoft Dynamics AX supports Unicode fonts. I have checked this both in AX 2012 and Dynamics 365 for operations with expected results.

In the below screen I have created a new Fixed asset master and in the text fields as highlighted in Japanese & Telugu as a sample:

 

This helps a lot of users to write local language descriptions that help ease the pain of users.

Configuration for currencies without decimals (Zero decimal Currencies) in Dynamics AX

Most of the currencies across the globe have decimals (for ex: USD 100.99 where 100 is the dollars and 99 are cents).

 
There are a few currencies that are exception however, below is a list of some such currencies where the smallest currency unit is 1 :

CLP  - Chilean Peso
JPY   - Japanese Yen
KRW - South Korean Won
VND - Vietnamese Dong

The currencies in AX (Dynamics 365 for Operations) can be configured to restrict decimals as below.

Open the Currencies form ( General ledger > Currencies > Currencies). In the rounding rules fast tab setup the following values:

General rounding rule = 1.00
Sales order rounding rule = 1.00
Purchase order rounding rule = 1.00
Fixed asset rounding rule = 1.00

As shown in the screenshot below:

 

Print multiple Purchase Orders from AX (Dynamics 365 for operations)

It is a common requirement for many companies that the print out of the Purchase Order. The option of printing multiple purchase orders (or any other Business documents such as Sales Order, Invoice etc.,) is available in AX.

This can be achieved using the Print Management settings in AX. Below I am going to show you the setup required for the setting up Print Management to generate Purchase order as a PDF format (alternatively it can be directly sent to printer).

First things first. We need to setup the Print Management settings for the Purchase Order as below.

Go to Accounts Payable > Setup > Forms > Form setup

 

The form setup page is opened as below. Click on the Print Management button as highlighted below:

The Print Management for is opened as below. in the below form under the Purchase order select printout type (in our case : Original) and this shows the properties on the right hand side.

In the highlighted Tab "Destination", The current destination is "Default" this is where we need to change to achieve the required goal.

 

Click on the Arrow shown and it will display options as below. In the options select the "Printer Setup"  as shown below:

This will open the "Print destination settings" dialog box. This is a familiar dialog box for many of us. In this box on the left side, choose Printer (as below):

I am selecting the Printer as "Microsoft Print to PDF" as in my case, I wanted to print the Purchase order into a PDF and Click "OK"

You may choose a different printer as is required. The print management functionality can also be used to send Purchase Order via Email. You may choose different options as per your business needs.

Once the setup is done, the destination is changed to "Printer: Microsoft Print to PDF" as below

With this setup is completed. Now we need to go to the Confirmed Purchase orders, which lists down all the Confirmed POs:

Navigate to  "Procurement and sourcing >Purchase orders >Purchase order confirmation >Purchase order confirmations". This opens the Purchase order confirmations form as below

from the list, Select all the Purchase Orders to be printed:

Click on the "User Print Management" option in the screen above and that's it, the selected Purchase orders are printed as separate PDF files and the prompt asks us for the location to where the file needs to be saved.

The same process can be applied to any type of Business document and I hope this article is useful for your AX implementation

Stop Purchase / Sale or Inventory adjustments for a Product (Item) in Microsoft Dynamics AX

Companies using ERPs often have one big complaint, they cannot delete a Product (Item) having transactions. For a corporation having few thousand products, it is a key requirement that they stop a product after few years on shelves (take for example the Nokia’s 1100 model was highly successful mobile phone. Alas! The company has to stop this product as part of their market strategy)

In Microsoft Dynamics AX (Microsoft Dynamics 365 for operations), a Product can be created globally and can be released to a legal entity as per requirement. Only upon successful release, the legal entity can transact on that product (termed as “Released Product”)

A released product cannot be deleted if transactions (Purchases, sales and Inventory) exist. However, a released product can be stopped from making new purchase, sales and/ or Inventory transactions. 

It is a good idea to ensure the On-hand inventory for this released product is zeroed out before a Released product is stopped

Note that each of this needs to be done separately as explained in the below:

1. Go to Released products and select the released product to be stopped. Click on default order settings under MANAGER INVENTORY tab (as highlighted in the below screen capture) 

   

  

2. The Default order settings for the selected released product is opened as below:

3. Stop new purchases: In order to stop the new purchases, go to Purchase Order fast tab and click on the Stopped

  

4. Stop new Inventory transactions: In order to stop the new inventory transactions, go to Inventory fast tab and click on the Stopped 

 

5. Stop new Sales transactions: In order to stop the new sales transactions, go to Sales order fast tab and click on the Stopped

 

This is it. Now the released product is stopped from making any new transactions.