ERP requisition triage

This module is enabled per organization. If you don't see Triage in your menu, talk to your Sourced contact.

Requisition triage is the screen that consolidates a view of every requisition synced to Sourced, in two ways:

• Pull: Sourced connects to your ERP (SAP, Oracle, JD Edwards, SAP Business One, among others) and syncs the new purchase requests or purchase orders that have been created and approved.

• Push: requisitions created through Sourced's public API.

From this screen, using a set of filters and data, the buyer selects the lines that were created and decides what to launch as a spot purchase (request for quotation), quickly and with all the data and files already synced.

The board

The columns follow each item's cycle:

• To quote: newly imported items awaiting a decision.

• Quoting: items launched in an active PR.

• Offers received: with supplier responses.

• Ready to award: comparison complete.

• Awarded: with a PO generated.

• Discarded: the ones you decided not to buy through Sourced.

• Closed: lines that are no longer open in the ERP. Sourced closes them on its own when they stop appearing in the sync, so the board does not pile up work someone already resolved on the other side. If the line shows up in the ERP again, it reopens by itself.

Above the board you can see when the last update from the ERP happened, so you know whether what you are looking at is a minute old or from yesterday.

How to work

1. Open an item's detail to see its description, quantities and ERP data, and edit whatever you need.

2. Select one or more items from To quote.

3. Use smart consolidation: the AI suggests which items are worth quoting together.

4. Launch the quotation: a spot PR is created with those items and follows the normal flow (supplier selection, sending, comparison).

5. Anything that shouldn't be purchased, discard it to keep the board clean.

Per-requisition mode

Some organizations work with atomic requisitions, that is, requisitions that must be processed in full and not line by line. In that case, selection and launching happen at the level of the complete requisition.

Traceability is maintained end to end: every PR created from triage stays linked to its source requisitions in the ERP.

ERP buyer and destination

When the requisition carries an assigned buyer or a destination (the delivery plant or branch), you see them as chips on each item and as columns in the table view. The Buyer and Destination filters in the top bar let you narrow the board down to your own lines; your selection is remembered for future visits.

When launching a package, the destination also works for you:

• If the package mixes items with different ERP destinations, the launch dialog warns you with a breakdown per destination. It is a warning, not a blocker: you can proceed anyway.

• If every item shares the same destination and one of your organization's addresses has that code configured, the delivery address is pre-selected (marked "Suggested based on ERP match"). You can always change it.

Reviewing attachments before launching

In the launch dialog, the "What the supplier will receive" section lists the files that will travel along with the request for quotation, grouped by origin so it is clear where each one comes from:

• Requisition attachments: those of the whole request, not of a specific line. They travel with every package launched from that requisition.

• Line attachments: what the ERP brought for that particular line.

• Material attachments: datasheets coming from the material master, not from this request.

• Added in this launch: the buyer's own files, uploaded on the spot. They go only with this package.

They all start checked: uncheck the ones that should not reach the supplier (for example, internal paperwork) before confirming. Hovering over a file opens a preview, so you can review it without downloading it.

Excluded files are not lost: they stay on the launched request, in the Attachments tab, under "Not sent to the supplier", where you can download them whenever needed.

What happens when you confirm the launch

When you close the supplier selection, Sourced reports what went out and what did not: how many requests had their quotations sent, how many already had their suppliers resolved, and how many were left without any send. Those last ones are completed from the request itself. If a package fails, the result says so: a launch with errors is not shown as successful.

Filters, columns and units

• The filters in the top bar (category, requester, buyer, destination, origin) let you pick several values and have their own search box, which helps when the list is long. There is also a filter by ERP creation date range.

• Active filters appear as chips in the sort-and-view row, so you can see them and remove them one by one, and they are remembered for your next visit.

• The order of the columns can be changed by dragging the header, and the position you choose is remembered.

• Units of measure are shown translated into the platform's language instead of the ERP code. Watch out for MIL: it means thousand, not a single unit.