Hi Guys,
We are facing a logical error in the calculation of “BED Credit” field in RG 23 A PART II table and this is happening in the standard Navision.
Case 1 : Create a purchase order for foreign vendor with CVD in structure field, make sure that currency code is not blank
Calculate the structure values and post the invoice. Select “Receive and Invoice” (Enter CIF and BCD amount manually)
Result : Navigate to the posted invoice, you will find the BED Amount in the Excise entry table is same as “BED Credit ” in RG 23 A Part II
Case 2: Create the same purchase order, you first receive and then invoice
Result: Same as case 1
Case 3 (error): Create a purchase order for foreign vendor with CVD in structure field, make sure that currency code is not blank
Receive the purchase order from warehouse receipts
Invoice the document through purchase invoices, not through the same purchase orders
Result: Navigate to the posted receipts, you will find the system creates an extra entry which is not the same as in above cases
has any one faced this kind of error in the standard Navision or am doing any wrong posting?
0
Comments
http://ssdynamics.co.in
I will see the reply from MS, if there is nothing then I know its checkExcisepostingdiff function in c 90 that making the difference I shall correct these :-k
http://ssdynamics.co.in
They have sent me new object but it is bringing wrong calcuation in some cases, I have reverted back expecting a reply, I shall update once I receive the reply from MS
Is there any setup or we need to customise the Excise calculation in T 39?
http://ssdynamics.co.in
In the training manual, we see the Excise is 4393/- so it is nesscary to add BCD to that 4393 + (2*1000)
So should I code the BCD in the excise calculation
is there any risk in using the CESS as BCD in excise posting setup?
Cess/SED/AED was widely used by people in 3.7 and 4.0 when E-Cess and SHE-Cess was introduced so I see no problem but test the solution before deploying and also define the correct "set off" setup.
http://ssdynamics.co.in
I got the reply from MS, they said it may take 4-6 weeks to release the fix.
Thanks for your support
http://ssdynamics.co.in