Comments
Here is a view you can use to create an empty SmartList out of
CREATE VIEW [dbo].[EFT]
AS
select
a. vendorid,
a. VENDNAME,
b. adrscode,
CASE b. efttransfermethod
WHEN 5 THEN 'Foreign Account'
when 4 then 'Personal Account'
when 3 then 'Corporate Account'
when 2 then 'Business Account'
when 1 then 'Not Specified'
END AS efttransfermethod
FROM SY06000 b JOIN PM00200 a
on a. vendorid= b. vendorid
where efttransfermethod = '5' or efttransfermethod='4' or efttransfermethod='1'
go
grant select on [EFT] TO DYNGRP
We do have a similar problem, the setup : "allow depreciation when placed in service and disposal are in the same fiscal year" could help us but it is necessary to make this set up it manually on each fixed asset. We found that the setup does exists in Asset parameters :
1. Go to Fixed Assets/Setup/Fixed Asset parameters
a. Personalize the general tab. By right-click/personalize
b. Click +add field and select “allow depreciation when placed in service and disposal are in the same fiscal year”
Note, the parameter is in and it is set to “Yes”
2. Go to AP/Purchase Orders/all Purchase orders, create a new one
- Vendor = 1001
- Click OK
a. In the PO line enter
- Item = 1000
- Site = 1
- Warehouse = 11
- Unit price = 10899
b. Go to line details, tab Fixed assets and enter
- New fixed asset = Yes
- Fixed asset group = VEHC
c. Confirm the PO
d. Go to Invoice/invoice
- Change default from = ordered quantity
- Invoice number = 555
- Invoice date = today
- Update match status
But then this "Personalized Fixed Asset Parameter" value is not defaulted in the book as it should be :
3. Go to Fixed Assets/Fixed assets/Fixed assets, select the newly created fixed asset and go to books, open tab. depreciation
Actual Result
Parameter “Allow depreciation when placed in service and disposal are in the same fiscal year” is set to “No”
IT WOULD BE VERY NICE TO BE ABLE TO DEFAULT THIS SETUP AS IT IS THE ACCOUNTING CHOICE / RULE FOR SOME CUSTOMERS / COUNTRIES.
Update:
It appears this idea shall be implemented on BC17 (2020 wave 2):
"The Payment Reconciliation journal will support application against employee ledger entries, allow one-to-many matching, have preview posting enabled, separate number series, and user-defined document numbers."
Source:
https://docs.microsoft.com/en-us/dynamics365-release-plan/2020wave2/smb/dynamics365-business-central/bank-reconciliation-improvements
Update:
It seems this idea shall be implemented on BC17 (2020 wave 2):
"The Payment Reconciliation journal will support application against employee ledger entries"
Source:
https://docs.microsoft.com/en-us/dynamics365-release-plan/2020wave2/smb/dynamics365-business-central/bank-reconciliation-improvements