| Description |
Details:
We had an issue on performance issue of 'Add Payables' screen. See AP-5790 for more info.
The curren data source of the 'Add Payables' screen is the 'vyuAPReceivedItems' which contains different sql view of integrated module.
Solution:
We created a separate table 'tblAPVoucherPayable' which every module will insert their data to voucher and show it on 'Add Payables' screen.
1. *uspUpdateVoucherPayableQty* - use this if you will insert or update the the data in tblAPVoucherPayable.
2. *uspAPRemoveVoucherPayable* - use this if you will remove the data on tblAPVoucherPayable
3. Use new *uspAPCreateVoucher* instead of uspAPCreateBillData.
I have implemented the new approach on 'Purchase Order' screen.
Here's how I implemented it.
1. Created *fnAPCreatePOVoucherPayable* to build the data for tblAPVoucherPayable.
2. Created *uspPOUpdateVoucherPayable* and use the fnAPCreateVoucherPayable to pass on *uspAPUpdateVoucherPayableQty* and *uspAPRemoveVoucherPayable*
3. I am calling the uspPOUpdateVoucherPayable upon saving of 'Purchase Order' screen. This will be depend on your scenario when you want to show your payables on 'Add Payables' screen either when posted/unposted/saved.
|