Purchase workspace and supplier master control

The Purchase workspace starts with Overview because procurement needs a quick read of open demand, sourcing pressure, order commitments, receipt state, invoice exposure, and exceptions before choosing a transaction tab.

Teach users to treat Overview as the map, not the destination. If the signal points to supplier quality, go to Vendors. If it points to pending demand, go to Purchase Requisitions. If it points to release, receipt, or settlement, follow the corresponding tab instead of guessing from memory.

Evidence should come from supplier state, requisition context, RFQ response, quotation comparison, PO approval, receipt, invoice, debit note, or settlement posture. For Start in Overview, a strong answer names the visible cue, record, status, or reference that supports the next step and states what would pause the learner.

The Vendors tab is the supplier master for purchase execution. Supplier identity, contact details, tax or compliance posture, payment context, and active status all affect whether later RFQs, POs, goods receipts, invoices, and debit notes can be trusted.

A supplier should be reviewed before it is used for sourcing or payment. If the vendor row is incomplete or stale, the purchase flow may still move forward visually while settlement quality is already weakened.

For Vendors as controlled supplier truth, the learner should point to the specific page, record, status, or note that separates evidence from assumption before moving to the next step.

Procurement teams often feel pressure to create a requisition or PO quickly. The better habit is to confirm that supplier and operating context are usable first, then move into demand capture and sourcing. A fast PO against weak supplier data only moves the problem downstream.

Tie the section on Master data before transaction speed back to day-to-day execution. The learner should explain what changes for handoff, review, escalation, or follow-up when this concept is handled from evidence instead of memory.

Use this section to confirm the learner understands more than the page label. They should connect Master data before transaction speed to the business state, owner, and consequence behind it.

Run the lesson as a requisition-to-settlement control exercise. Start with the practical task: use Overview to understand the current procurement posture before opening a transaction tab. Ask the learner to name the role, surface, evidence, and state they would inspect before taking action.

Evidence should come from supplier state, requisition context, RFQ response, quotation comparison, PO approval, receipt, invoice, debit note, or settlement posture. The practice should end with the learner connecting the action back to the lesson summary: orient procurement users to the live Purchase workspace and show why supplier master control comes before requisition, RFQ, PO, receipt, and invoice work.

Close the exercise by asking the learner to restate the objective in operational terms: use Overview to understand the current procurement posture before opening a transaction tab. They should name what changed, what remains uncertain, and which surface or owner takes the next step.

Do not let procurement become a chain of disconnected documents. Each step should preserve supplier context, budget posture, policy evidence, and the next accountable owner. In this lesson, watch for that risk while learners work on this objective: use Overview to understand the current procurement posture before opening a transaction tab.

Do not mark the lesson complete because the learner can repeat terms. Completion means they can explain what Overview is for before opening a purchase transaction tab and describe why the lesson matters in real work.

Review the answer for skipped ownership, missing evidence, or vague next steps. If the learner cannot explain what Overview is for before opening a purchase transaction tab, keep the lesson in practice mode before marking it complete.