1. SCM with Vendor Scorecard
  2. Data model
Reference

The tables behind SCM with Vendor Scorecard

SCM with Vendor Scorecard ships with 10 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.

Tables
10
Features
6
Change it
Add fields and tables in Proto

How the model is organised

Demand and Suppliers

Purchase requests references Organizations, team members through Owner and Suppliers through Counterparty. Suppliers and team members each belong to an Organization; team members.User identifies the platform account.

Commitment Review

Purchase requests carries Revision, approved at, order reference and Status. Review decisions links Parent to purchase requests and Reviewer to team members, retaining source revision, Decision and operation key.

Receipt Acceptance

Purchase lines belongs to purchase requests through Parent. Requested quantity, accepted quantity and accepted at describe the line's requested and accepted scope.

Invoice Matching

Purchase lines.invoice reference identifies the invoice context used with accepted scope and unit price USD. Operation receipts retains the corresponding action, revision and effect evidence.

Supplier Scorecards

Supplier assessments belongs to purchase requests and Organizations. Supplier, period end, on time percent and acceptance percent describe the assessment, with Revision, Status and decision at for its review path.

Evidence and Corrections

Record attachments belongs to purchase requests and identifies uploaded by in team members. Operation receipts retains result state, external reference, effect references and failure reason under the same parent.

Every table, by feature

Demand and Suppliers

8 tablesAbout this feature
  • Purchase requests

    Demand records carrying requested amount, lifecycle status and supplier counterparty.

    Linked to Organizations, Team members, Suppliers
  • Purchase lines

    Line items under a purchase request with requested and accepted quantities.

    Linked to Purchase requests
  • Suppliers

    Approved supplier parties eligible for purchase commitments.

    Linked to Organizations
  • Organizations

    Operating organizations that own procurement records and supplier relationships.

  • Team members

    Authenticated platform users mapped to an organization with a business role.

    Linked to Organizations, Users
  • Users

    Users

    Linked to Users
  • Record attachments

    Evidence files attached to a purchase request with visibility scope.

    Linked to Purchase requests, Team members
  • Operation receipts

    Idempotent receipts for guarded operations and their downstream effects.

    Linked to Purchase requests

Commitment Review

6 tablesAbout this feature
  • Purchase requests

    Demand records carrying requested amount, lifecycle status and supplier counterparty.

    Linked to Organizations, Team members, Suppliers
  • Purchase lines

    Line items under a purchase request with requested and accepted quantities.

    Linked to Purchase requests
  • Review decisions

    Independent approver decisions recorded against a purchase request revision.

    Linked to Purchase requests, Team members
  • Operation receipts

    Idempotent receipts for guarded operations and their downstream effects.

    Linked to Purchase requests
  • Record attachments

    Evidence files attached to a purchase request with visibility scope.

    Linked to Purchase requests, Team members
  • Suppliers

    Approved supplier parties eligible for purchase commitments.

    Linked to Organizations

Receipt Acceptance

5 tablesAbout this feature
  • Purchase lines

    Line items under a purchase request with requested and accepted quantities.

    Linked to Purchase requests
  • Purchase requests

    Demand records carrying requested amount, lifecycle status and supplier counterparty.

    Linked to Organizations, Team members, Suppliers
  • Operation receipts

    Idempotent receipts for guarded operations and their downstream effects.

    Linked to Purchase requests
  • Record attachments

    Evidence files attached to a purchase request with visibility scope.

    Linked to Purchase requests, Team members
  • Suppliers

    Approved supplier parties eligible for purchase commitments.

    Linked to Organizations

Invoice Matching

6 tablesAbout this feature
  • Purchase lines

    Line items under a purchase request with requested and accepted quantities.

    Linked to Purchase requests
  • Purchase requests

    Demand records carrying requested amount, lifecycle status and supplier counterparty.

    Linked to Organizations, Team members, Suppliers
  • Operation receipts

    Idempotent receipts for guarded operations and their downstream effects.

    Linked to Purchase requests
  • Review decisions

    Independent approver decisions recorded against a purchase request revision.

    Linked to Purchase requests, Team members
  • Record attachments

    Evidence files attached to a purchase request with visibility scope.

    Linked to Purchase requests, Team members
  • Suppliers

    Approved supplier parties eligible for purchase commitments.

    Linked to Organizations

Supplier Scorecards

7 tablesAbout this feature
  • Supplier assessments

    Vendor scorecard assessments measuring on-time delivery and acceptance performance.

    Linked to Purchase requests, Organizations
  • Purchase requests

    Demand records carrying requested amount, lifecycle status and supplier counterparty.

    Linked to Organizations, Team members, Suppliers
  • Purchase lines

    Line items under a purchase request with requested and accepted quantities.

    Linked to Purchase requests
  • Suppliers

    Approved supplier parties eligible for purchase commitments.

    Linked to Organizations
  • Record attachments

    Evidence files attached to a purchase request with visibility scope.

    Linked to Purchase requests, Team members
  • Review decisions

    Independent approver decisions recorded against a purchase request revision.

    Linked to Purchase requests, Team members
  • Operation receipts

    Idempotent receipts for guarded operations and their downstream effects.

    Linked to Purchase requests

Evidence and Corrections

7 tablesAbout this feature
  • Operation receipts

    Idempotent receipts for guarded operations and their downstream effects.

    Linked to Purchase requests
  • Review decisions

    Independent approver decisions recorded against a purchase request revision.

    Linked to Purchase requests, Team members
  • Record attachments

    Evidence files attached to a purchase request with visibility scope.

    Linked to Purchase requests, Team members
  • Purchase requests

    Demand records carrying requested amount, lifecycle status and supplier counterparty.

    Linked to Organizations, Team members, Suppliers
  • Purchase lines

    Line items under a purchase request with requested and accepted quantities.

    Linked to Purchase requests
  • Supplier assessments

    Vendor scorecard assessments measuring on-time delivery and acceptance performance.

    Linked to Purchase requests, Organizations
  • Team members

    Authenticated platform users mapped to an organization with a business role.

    Linked to Organizations, Users

Keys and references

Preserve the table-specific identifiers such as purchase request ID, purchase line ID, assessment ID and operation receipt ID. Record number supplies the human purchasing reference. Supplier Code and the Counterparty reference identify the actual business party.

Supplier assessments.Supplier is text. Resolve the supplier relationship through its Parent and purchase requests.Counterparty, and check that the label agrees with the intended party. Review decisions also links to the purchase request; use operation key and the actual effect references to identify the assessment decision rather than associating every parent decision with every assessment.

Keep the assessment Revision and parent request Revision distinct. Source revision and expected revision must retain the meaning assigned by their guarded action. My Requests resolves the authenticated user through team members.User to purchase requests.Owner. Users.User is a self-reference in the platform account model and follows that account setup.

Migration order

  1. Establish Organizations and Users, then team members with real account links, organization scope and active state.
  2. Load Suppliers with their organization, code and eligibility information. Confirm the intended Counterparty before preparing requests.
  3. Load purchase requests and their purchase lines, preserving requested values, quantity meaning and existing revision history.
  4. Preserve actual accepted quantity, accepted at and invoice reference evidence without regenerating receipt or financial outcomes from current status.
  5. Load supplier assessments with the correct Parent, Organization and period evidence. Retain original measure definitions and distinguish absent observations from measured zero values.
  6. Preserve record attachments, review decisions and operation receipts with their original parent, actor and operation identity. Reconcile imported effects before relying on their completion claims.

Set up SCM with Vendor Scorecard your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started