I noticed that Business Central’s Purchase Order module is not simple and therefore could be a deterrent for certain users. Since our finance staff have committed to using Business Central, having procurement use the BC inherent PO module would make life easier in terms of data centralization and end-to-end PO to PI auditing.
I noticed that in BC, once we create a PO and receive + post it, it transitions into a PI. We can always reference the PO number through a posted purchase receipts; however, the ability to see all the archival information of a PO would be beneficial. As such, I think creating a custom PO archive (headers and lines w/ associated configurations) should allow for a user to:
- use BC’s base PO module to create/receive/post PO.
- When posted, it then recording that into a PO archive with headers and line items.
The only inefficiency I saw was the creation of items and associating them to GLs. This would need to be done for us to use Items in POs.
I went about creating custom tables, list pages and codeunits to seed data. For larger datasets, I used configuration packages to import data into custom tables via csv.
Once the data was imported in, I created a custom page that allowed for a header with line item view of purchase order headers and lines.
Once confirmed, I want to hook into the receiving and posting of BC base purchase orders and then create new purchase headers and lines in my archive table according to the base bc event.