Reciprocal exchange rate in same legal entity

In some D365 FinOps implementations, we face scenarios where there is a requirement for reciprocal exchange rate between currencies. Out of the Box, D365 FinOps calculates B to A rate when A to B rate is configured and does not allow set up of B to A when A to B rate is configured. To achieve the requirement, we can make a small customization /extension to allow configuration of exchange rate B to A, while having A to B configured in the same exchange rate type.




                                                                                                                                                               



The below extension to the table "ExchangeRateCurrencyPair", enables the setup of reciprocal currency exchange rate.


[ExtensionOf(tableStr(ExchangeRateCurrencyPair))]
public final class NDSExchangeRateCurrencyPair_T_Extension
{
public boolean validateWrite()
    {
        boolean                  ret = next validateWrite();        
        ErrorMsg                 msg;
        int                      infoLineNum;
        
        if (!ret && this.FromCurrencyCode != this.ToCurrencyCode)
        {
            infoLineNum = infologLine();
// Find if the error @SYS340385 is thrown due to reciprocal currency setup and undo the validation error and clear message
            msg = strFmt("@SYS340385", this.FromCurrencyCode, this.ToCurrencyCode);

            if (infolog.text(infoLineNum) == msg)
            {
                infolog.clear(infoLineNum-1);
                ret = true;
            }
        }

        return ret;
    }
}

No other code changes required for Exchange rate pickup for transactions, D365 FinOps standard code first checks for exchange rate "A to B", if not found, then looks for "B to A" to calculate the reciprocal value.

Happy DAXing :)

Comments

Post a Comment

Popular posts from this blog

Invoicing multiple Sales order using code in AX 2012

Wondering how to post invoice for multiple Sales orders?? Below is the solution. SalesFormLetter salesFormLetter;     QueryRun queryRun;     Query query;     str strSalesTable = "000630,000631,000643";     ;     salesFormLetter = SalesFormLetter::construct(DocumentStatus::Invoice);     query = new Query(QueryStr(SalesUpdate));     query.dataSourceTable(tablenum(SalesTable)).addRange(fieldnum(SalesTable, SalesId)).value(strSalesTable);     queryRun = new QueryRun(query);     salesFormLetter.chooseLinesQuery(queryRun);     salesFormLetter.transDate(systemdateget());     salesFormLetter.specQty(SalesUpdate::All);     salesFormLetter.printFormLetter(true);             salesFormLetter.chooseLines();       salesFormLetter.run();
Read more

External Code unique value limitation D365FO

Out of the box, D365FO provides External codes feature to capture external references for Customers and Vendors. This could be an external system reference of Customer or Vendor accounts. Standard D365FO External codes data model limits an external code value to be linked to only one account per type - meaning when customer "C0001" has an external code "MemberId" with value "M0001", system will not allow another customer "C0002" to have external code "MemberId" with value "M0001". This limitation is implemented at the table index level. However, there will be scenarios where the business requires same external code value to be allocated to multiple customer accounts. One such is multiple customer accounts linked to one dealer or some businesses having multiple accounts for same customer segregated by state or other criteria. In such cases, the out of the box index limitation will not allow same external code value to be alloca...
Read more