Order Acknowledgement Mapping

Update to Order Acknowledgement Scanning to be able to map your OA items to PO items

A
Written by Alex Lewis
Updated over a week ago

Overview

The new Order Acknowledgement (OA) mapping product comes with a enhancements that improve the overall OA scanning product.

The main changes with this product are:

  1. Background scanning of Order Acknowledgement (OA) documents, allowing you to upload and scan documents without needing to monitor the process on your screen

  2. A revised import screen that makes it clearer what data will be imported

  3. A new mapping screen that allows you to map OA items to the Purchase Order (PO) thus ensuring data is accurate and traceable in Kojo

Key Features

Background Scanning

Previously, you would, after uploading OA documents to the attachments tab for an Order, scan in that OA and wait anywhere between 10-30 seconds for the scanning to finish.

This was disruptive and led to wasted time.

Now, with background scanning, you can scan in a document and continue to do other work in Kojo. When the scan is complete, you'll receive a notification in the notification banner alerting them that the scan is complete.

Revised Import Screen

We’ve only made slight modifications to the import screen, but our hope is that they streamline the experience for users and center them in this two step workflow.

Changes we’ve made:

  1. Updated Header: Updated the header to reflect that this is the first step

  2. Updated Footer & Settings: Call out in the bottom left of the modal which columns will be imported, and we maintain this in the mapping screen to ensure the user always understands what data they’ll be importing. If they select the settings, they can adjust which columns they’d like to import into their PO

  3. Success & Failure Banners: Added clearer success and error banners to ensure the users understand what data we were or were not able to import

(New) Mapping Screen

The new mapping screen is critical to ensuring the data you import does not cause accounting errors and maintains line item traceability between the various objects within our system, such as corresponding requisition and PO items.

This mapping screen is nearly identical to our RFQ and Invoice mapping screens with a few slight changes:

  1. (New) Header: similar to the import screen, we have a new header that centers the user in this two step workflow

  2. (Same) Options Button: this is the same as our other mapping products, and gives the user the ability to map items according to their preference.

  3. (New) Footer: We are leveraging the same new footer as in the Import Screen, which highlights the columns that will be imported

FAQ

  1. Do you support many OA items to one PO item mapping? What about many PO to OA item mappings?

    1. At the moment we do not but we have plans to support this in the future

  2. Will you scan and display unit prices or unit of measure?

    1. No we will not

    2. We have plans to support this soon

Did this answer your question?