Shipping Information from the Requisition Added to the PO Punchout Process
In order to add additional context to the PO Punchout Process, Certify AP has added the Shipping Location from the Purchase Requisition to the Place Order Electronically via Punchout screen. This should make it easier for you to select the correct shipping location when placing the PO via Punchout.
There are two possible ways that the Shipping Location On Requisition is determined:
- If the user manually set the shipping location in the header of the Requisition, the Shipping Location On Requisition for the line item will reflect that location.
- If the user did not manually set the shipping location in the header of the Requisition, the Shipping Location On Requisition for the line item will show the recorded shipping address of the Department selected for the line item on the Requisition.
The location will be displayed as [DepartmentName]: [Address1],[Address2],[City],[State],[Zip],[Country]
Bug Fix Notes
Issue | Description |
CAP-6851 | InvoiceOCR: invoice not visible in CreateInvoice page | An issue was found where invoices created via InvoiceOCR were not visible on the Create Invoice page. This has been resolved. |
CAP-6858 | Unable to autogenerate inv# | An issue was found where if a vendor had a longer APvendorID than the company preference, the invoice submitter was not able to generate random unique invoice number. This has been resolved. |
CAP-7173 | Dashboard.aspx: Charge Status not updated when invoice is deleted | An issue was found where the charge status wasn't getting updated correctly when a draft invoice with a matched charge was deleted from the homepage dashboard. This has been resolved. |
CAP-7213 | Vendor List not sorted alphabetically | An issue was found where the vendor list on the Create Invoice page is not sorted by alphabetically when the vendor/dept restriction was configured. This has been resolved. |
CAP-7313 | Incorrect vendor list on CreateInvoice page | An issue was found where on the Create Invoice page, the vendor list was missing vendors associated at sub-level departments when vendor/dept restriction was configured. This has been resolved. |