Changes in Microsoft Dynamics NAV in 5.0 SP1

Changes Made in Microsoft Dynamics NAV 5.0 SP1

This document describes the changes between Microsoft Business Solutions–Navision IN 4.0 SP3 and Microsoft Business Solutions–Navision IN 5.0 SP1.

Table of Contents 1 Localization Changes........................................................................................................2

1.1 Sales.......................................................................................................................... 21.2 Purchase.................................................................................................................... 41.3 Manufacturing.............................................................................................................61.4 Sales Tax.................................................................................................................... 61.5 Excise......................................................................................................................... 71.6 Tax Deducted at Source.............................................................................................91.7 Tax Collected at Source...........................................................................................111.8 Value Added Tax......................................................................................................121.9 Service Tax...............................................................................................................141.10 Fringe Benefit Tax.................................................................................................171.11 Financial Management..........................................................................................18

document.doc2 Page 1 of 18 22-12-2005

1 Localization Changes

1.1 Sales

Errors fixed

L1) Error message given for fixed asset and capital item in case of trading transaction should be included in test reports of sales and purchase documents.

Error

In case of trading and fixed asset, error is generated. This error should also be displayed in the test reports.

This has been corrected

Report 202 Sales Document – TestReport 402 Purchase Document – TestCodeunit 80 Sales-PostCodeunit 90 Purch.-Post

L2) Sales Order Test Report, Include PIT Calculation error displayed is wrong. Total amount is not displayed properly.

Error

In Sales Order Test Report, total amounts are not populated correctly. Moreover, the error displayed for Include PIT calculation is wrong.


Report 202 Sales Document – Test

L3) Test report- Sales Order - if G/L account is used warning is coming that Structure should have Include PIT Calculation = Yes

Error


In Sales Order Test Report, if G/L Account is used, then error is generated that the Structure used should have “Include PIT Calculation” as “Yes”.


Report 202 Sales Document – Test

L4) Cess is not being calculated in Sales when Cesss Calculation formula is blank.

Error

Cess is not being calculated in Sales when Cesss Calculation formula is blank.


Table 37 Sales Line

L5) Nature of Service field not displayed on Customer Card and is not flowing on Sales Header.

Error

The "Nature of Service" Field is not displayed on Customer Card and is not flowing on Sales Header.


Table 36 Sales Header Form 21 Customer Card

L6) ST Pure Agent Field as Option Field

Error

ST Pure Agent field is a Boolean field on Sales Order whereas in this database it is a Option field (No/ Yes).


Form 42 Sales Order L7) Trading check mark not flowing through Company information in Sales order.

Error

In Company Information, Trading is checked. While creating the Sales Order, Trading check is not flowing on the header.



Table 36 Sales Header

1.2 Purchase

Errors fixed

L8) Credit Memo is created by copying posted invoice. On Posting Inconsistency error comes as "Transaction No. Serv. Tax’ " is copied on Purchase Invoice.

Error

Purchase Invoice Posted with applied Service Tax Advance Payment. Using Copy document, Credit Memo is created by copying posted invoice. On Posting Inconsistency error comes as "Transaction No. Serv. Tax’ " is copied on Purchase Invoice.


Codeunit 6620 Copy Document Mgt.

L9) Tick Mark on Trading field for PO

Error

On purchase order, trading field should allowed to changed only when status is Open.


Table 38 Purchase Header

L10) Inconsistency error while posting transfer order

Error

Inconsistency error while Posting transfer order.


Table 5741 Transfer Line

L11) While Trading Boolean is true in location card it is not flowing on Purchase Header

Error


When Trading Boolean is True on Location card, and the same location is selected on Purchase Header, the trading information is not flowing on Purchase Header.


Table 38 Purchase HeaderReport 402 Purchase DocumentCodeunit 90 Purch.-Post

L12) In subcontracting all rejection fields are not accepting any figure (quantity) after receiving the material (finished goods) using receipt tab.

Error

In the form Order Subcontracting Details, Qty to Reject fields do not allow any quantity to be input, after the materials have been received using Receipt tab.


Codeunit 90 Purch.-Post

L13) Wrong G/L Entry and Excise Amount.

Error

The system is not calculating correct G/L Entry and Excise Amount in case of CVD and ADC in Purchase Order. Before posting calculates the different Excise Amount and after posting calculates the different Excise Amount and G/L entry value.


Table 39 Purchase LineCodeunit 90 Purch.-Post

L14) Overflow under type conversion in Purchase line.

Error

Creation of Purchase Order using the CVD setup gives the Error Message:

“Underflow type conversion Text to Text.Value: CIF AMOUNT + BCD AMOUNT + AED AMOUNT + BED AMOUNT + SED AMOUNT SAED AMOUNT + SHECESS AMOUNT + ECESS AMOUNT + CUST. ECESS AMOUNT + CUST. SHECESS AMOUNT”



Table 39 Purchase Line

L15) Wrong Excise Base Amount on Purchase Line in case of CVD transaction

Error

The calculation for Excise Base Amount is wrong in Purchase Line, in case of CVD Transactions.



1.3 Manufacturing

Errors fixed

L16) In Subcontracting Worksheet if Gen. Prod. Posting Group is not defined in work centre, the program must stop or give error.

Error

Program must stop or give error message on execution of Carry Out Action Message from Subcontracting Worksheet if Gen. Prod. Posting Group is not defined in work centre.


Report 493 Carry Out Action Msg. - Req.

1.4 Sales Tax

Errors fixed

L17) While posting Sales order/invoice with blnak location code in case of VAT/CST, it is calculating VAT/CST correctly but it is not taking state code in Detailed Tax Entry Table. It has to pick the State Code from Company Information.

Error


If location code is blank on Sales Order/Invoice, then in Detailed Tax Entry table state code is not populated. The state code in this case should be picked up from Company Information.


Codeunit 80 Sales-Post

1.5 Excise

Errors fixed

L18) Excise Posting Set up for Documents

Error

The Excise Posting Setup form opened from Line - > Excise Posting Setup should be non-editable. Moreover, “Excise Posting Setup” should be renamed as “Excise detail”.


Table 37 Sales Line Table 39 Purchase Line Form 42 Sales OrderForm 43 Sales InvoiceForm 44 Sales Credit Memo Form 50 Purchase Order Form 51 Purchase Invoice Form 52 Purchase Credit Memo Form 6630 Sales Return Order Form 6640 Purchase Return Order

L19) Excise Invoice Printing

Error

While printing the excise invoice, system is giving error for Key definition


Table 13798 Posted Str Order Line Details


L20) Modifeid Values of Excise Components not considered with other Taxes on posting of Purchase Order.

Error

On Modifiying the excise component values in Purchase Order while calculating VAT and Excise the "Excise Amount" is not considered in this case.



L21) Creation of Sales Order with check mark on the Direct Debit to PLA/RG gives the error Excise Cenvat claim already exists.

Error

Create a Sales Order and place a check mark on Direct Debit to PLA/RG. After that go to Functions and click Direct Debit to PLA/RG. It gives an error message:

“Excise Cenvat Claim already exists.”


Table 36 Sales HeaderTable 39 Purchase Line

L22) Excise Duty Rate not generated in Excise Invoice report.

Error

After posting the Sales Order, where ADC VAT is charged, the correct value is not generated in the Excise Duty Rate Column in Excise Invoice Report.


Table 37 Sales Line

L23) Excise Duty Rate not generated in Excise Transfer Invoice report.

Error

System is not generating the value in Excise Duty Rate Column, in Excise Transfer Invoice Report in Posted Transfer Shipment.



Table 5741 Transfer Line

1.6 Tax Deducted at Source

Errors fixed

L24) Challan Register Fields should not be editable.

Error

On Challan Register form, fields should be non-editable.


Form 16506 Challan Register

L25) Getting Inconsistency error While posting Bank Receipt Voucher in case of TDS Receivable from Customer.

Error

Getting Inconsistency error While posting Bank Receipt Voucher in case of TDS Receivable from Customer.


Codeunit 12 Gen. Jnl.-Post Line L26) Wrong TDS Amount is Populated in Purchase Statistics Window while

calculating TDS

Error

While creating purchase order for calculating TDS, wrong amount is populated in "Purchase Statistics Window" (F9) before posting the Purchase Order. This bug can be replicated in 5.1database.


Form 403 Purchase Order Statistics


L27) Error Message not displayed correctly while posting Purchase Order in case of calculating TDS.

Error

In order to post Purchase order with a posting date which is not specified in Income Tax Period setup. the error message displayed is not correct.


Codeunit 12 Gen. Jnl.-Post Line

L28) Error Message not displayed correctly while posting Purchase Order in case of calculating TDS.

Error

Incorrect Error message is displayed in order to post a Purchase Order with a posting date which is not specified in Income Tax period Setup while calculating TDS.

Error Message displayed is :-"Posting date does not lie in TCS period setup."



L29) Include TDS Base Calculation Field in Structure card is not being Considered while Calculating Service Tax with TDS.

Error

While calculating Service Tax with TDS, the "Include TDS Base Calculation" field in Structure card (Service Tax) is not being Considered in Purchase Order.There is no effect in amount if the "Include TDS Base Calculation" field in Structure is true or not.


Table 38 Purchase HeaderTable 39 Purchase LineForm 54 Purchase Order Subform

L30) TDS Base Amount not displayed in Amount Paid column for Form 27A and e TDS files

Error


The TDS Base Amount is not displayed in the Amount Paid column of the Form 27 A and the eTDS text file generated. The scenario occurs when the Threshold limit for the TDS Party / Vendor is unchecked in the NOD lines and there are transactions which had amounts less than the Threshold limits. When the Threshold limit is crossed, TDS is deducted on the Total Amount but in the Form 27A and e TDS text file in the Amount Paid column only the amount from the transaction in which the Threshold limit was crossed and TDS was deducted is shown.


Report 16505 Form 26Q Report 16506 Revised Form 26Q Report 16507 Generate 27AReport 16508 Generate e-TDS 26Q Report 16509 Revised 26Q

1.7 Tax Collected at Source

Errors fixed

L31) In form 27EQ education cess amount is not including SHE cess amount but total tax amount is total of TCS,Surcharge,eCess and SHEcess,It also has to be updated for eTDS of 27EQ.

Error

In all reports of TCS, eCess amount should also include SHECess amount.


Report 16514 TCS Entries Report 16515 Generate 27B Report 16516 TCS Challan RegisterReport 16518 Form 27EQ Report 16519 TCS 27D Report 16521 Form 27EQ Correction Report 16524 Generate e-TCS 27EQ Report 16526 Generate revised e-TCS 27EQReport 16529 Issued TCS certificates L32) Tcs Certificate is not generated,

Error

TCS Certificate is not geenrated ,as TCS type field is blank in the NOD/NOC Line.



Table 13785 NOD/NOC Lines

1.8 Value Added Tax

Errors fixed

L33) Inconsistency Error in Purchase Order - Fixed Asset with VAT

ErrorGetting Inconsistency error on posting Purchase order with Fixed Asset while calculating VAT.In this case VAT is calculated and deferments are also created, but while posting it gives an inconsistency error. The bug can be replicated in 5.1 database.



L34) VAT Settlement - Refund Account asking even if not doing refund.

ErrorIn case of VAT settlement, it asks for Refund account, even if we are not doing refund.


Report 16544 VAT SettlementTable 16523 VAT SettlementTable 16569 VAT Opening Journal

L35) In VAT Settlement there was refreshing problem in fields 7,8,9,18.

ErrorIn VAT Settlement there was refreshing problem in fields 7,8,9,18.



L36) In Case of CST- VATpayable value not populated in field Input VAT Credit (Normal Sales) -- Field No 3 in Vat Settlement Form

ErrorIn VAT Settlement, if CST was involved then VAT Payable value was not populated.




L37) Negative payment in Net Vat Payable

ErrorNegative payment in Net Vat Payable



L38) Trading Error on Posting Sales Order in case of VAT Calculation

ErrorIn Case of VAT calculation if Trading is true in Location Card and that flows on Sales Header, it gives an error while posting the Sales Order.


Report 202 Sales Document - Test Codeunit 80 Sales-Post

L39) Mismatch of result in VAT Settlement form

ErrorTheir is a mismatch of amount in VAT Settlement form on setting off the carried forward amount and Input VAT(Export) amount against VAT and CST.


Table 16523 VAT Settlement Table 16569 VAT Opening Journal Form 16542 VAT Settlement Form 16543 VAT Settlement Subform Report 16544 VAT Settlement Codeunit 16503 VAT Management

L40) Overflow Error when doing VAT Adjustment Entry

ErrorAn error message appears as: “Overflow under type conversion of Text to Text. Value: VAT Adjustment Entry for Document No.”, when the making adjustments to a Posted Invoice with VAT.



Form 16539 VAT Adjustment Journal

L41) Input VAT Credit (Export Sale) value not populating automatically in the carry forward field of VAT Settlement form.

ErrorIn VAT Settlement window an inconsistency error is thrown, when there is value in the Input VAT Credit (Export Sales) .The value in this field is not populating automatically in the carry forward field (Sl. No 21) of VAT Settlement window.


Table 16523 VAT Settlement

1.9 Service Tax

Errors Fixed

L42) Service Tax Advance Payment - Service Tax calculation when TDS is also involved.

ErrorWhen TDS is involved Service Tax calculation is wrong.


Form 54 Purchase Order SubformTable 38 Purchase HeaderTable 39 Purchase Line

L43) Inconsistence while Distributing the Input Service

ErrorWhen Input Service distribution is done, inconsistency error is generated.


Codeunit 16507 Service Tax Cr Distribution

L44) Input Service Tax Distribution

ErrorOn deletion of the line from Service Tax Distribution, system is not updating the “Total Applied Amount”, because of that system is not showing the entry in the second Service Tax Distribution entry



Table 16578 Distribution Line

L45) Error in Creating Service Tax Distribution Form

Error

While creating Service Tax Distribution Form, press F3 in No field it gives an error of "Overflow under type conversion of code to code".


Table 16577 Distribution Header

L46) Getting Key Error while generating Service Tax Credit register Report

Error

On generating Service Tax Credit Register Report the system is giving error regarding the Key.


Table 16474 Service Tax Entry DetailsTable 16570 ST as Excise Utilisation

L47) Getting Key error on posting Service tax Payment Form

Error

While posting Service Tax Payment form the system is giving key error.


Table 16476 Service Tax Payment Buffer Codeunit 16471 Service Tax Management

L48) ST Rounding Field is not populated in Service Tax entry and Service Tax entry details

Error

In case of G/L to G/L transaction with service tax through General Journal, the ST Rounding field is not get populated in Service Tax Entry and Service Tax Entry Detail, where ST Rounding is defined as 1 in General Ledger Setup under Tax Information.



Form 39 General Journal Codeunit 16471 Service Tax Management

L49) Service Tax Rounding Precision and type is not flowing in Service Tax Opening form if Transaction No. is not Selected.

Error

Service Tax Rounding Precision and Service Tax RoundingType are defined in General Ledger Setup under Tax Information as

Service Tax Rounding Precision: 1Service Tax Rounding : Nearest

Service Tax Rounding Precision and Service Tax RoundingType is not flowing in Service Tax Opening form if Transaction No. is not selected.


Table 16550 Service Tax Opening

L50) Service Tax Calculation in case of ST Pure Agent.

Error

Program is calculating service tax amount in case of invoice if we place a check mark on ST Pure Agent, while posting through General Journal.


Table 81 Gen. Journal Line

L51) Service Tax Calculation in case of Nature of Service.

Error

Program is Calulating Service Tax , if the Export or Exempted is defined as nature of service in customer card


Table 81 Gen. Journal Line

L52) "Posting No. Series" in Distribution Header is not flowing from GL Setup

Error


On creation of Service Tax Distribution in Periodic Activities, "Posting No. Series" in Distribution Header is not flowing from GL Setup after insertion in the table


Table 16577 Distribution Header

L53) Overflow error in Distribution Line table

Error

Overflow error in Distribution Line table on creation of Document No. greater than 10 in Distribution Header.


Table 16578 Distribution Line16579 Posted Distribution HeaderTable 16580 Posted Distribution Line

1.10 Fringe Benefit Tax

Errors Fixed

L54) FBT Setup

Error

Use the word “Set Up” in FBT instead of Rate as we are following set up word throughout the product


MenuSuite 30 Country


1.11 Financial Management

Errors Fixed

L55) FA not belonging to the filter can also be selected, in the Retrospective Effect of Depreciation form

Error

In Retrospective Effect of Depreciation form, only those FA are displayed in FA Nos. filter, which belong to the filter set. But on pressing “Show All” button, any other FA which does not belong to the filter set can also be selected. Whereas in such a case, the system should generate an error.


Table 16527 Proposed Depr Method Header
