Skip to content
Tutorials Center
My learning

Topics

Lesson 5 of 36 ยท Getting Started

Key Terms, Roles and Master Data

Learn the vocabulary every ERP and CRM project uses: master data versus transaction data, documents, organisational units, users, roles, permissions and the people who run the system.

Every field has a vocabulary that insiders use without explaining. ERP and CRM are no different: people say "master data", "posting", "document flow", "role" and "tenant" as if everyone knew. This lesson gives you the working vocabulary you will meet in every later chapter, so that implementation meetings, vendor demos and documentation make sense.

Master data versus transaction data

The most important distinction in any business system:

  • Master data describes the long-lived things the business deals with: customers, vendors, products (items), employees, accounts in the chart of accounts. It changes rarely.
  • Transaction data records events that happen: a sales order, a goods receipt, an invoice, a payment, a support case. There are many of them and each one refers to master data.

Two kinds of data

Master data Customers, items, vendors
Transactions Orders, invoices, payments

Transactions point at master data

1 / 2

A wrong price on one item record will corrupt every future order for that item. That is why companies guard master data with approval workflows.

Python Transactions referring to master data

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Documents, posting and document flow

ERPs think in documents: a quotation, a sales order, a delivery note, an invoice. A document has a header (customer, date) and lines (items, quantities). When a document is posted (also "released", "confirmed" or "booked", depending on the product), it takes effect: stock moves, ledger entries are created. Posted documents are normally not edited; you correct them with a reversing document, such as a credit note.

The chain from one document to the next is the document flow: quotation, order, delivery, invoice, payment. Each document refers to its predecessor, so you can trace any invoice back to the order that caused it.

flowchart LR
  Q["Quotation"] --> SO["Sales order"] --> DN["Delivery"] --> INV["Invoice"] --> PAY["Payment"]

Each document points back to the one before it.

Organisational structure

ERPs model the company's shape so reports and permissions follow it:

  • Company / legal entity: a registered business with its own books.
  • Business unit, plant, warehouse, cost centre: subdivisions used for reporting and responsibility.
  • Fiscal year and period: the accounting calendar.
  • Currency and tax setup: local currency, exchange rates, tax codes.

CRMs have their own structure: teams, territories (regions or segments assigned to salespeople) and hierarchies (who reports to whom, which decides who sees which records).

Users, roles and permissions

A user logs in. A role is a bundle of permissions such as "Sales representative" or "Accounts payable clerk". Giving roles instead of individual rights keeps access manageable. A good design follows least privilege: people get only what their job needs, and segregation of duties: the person who creates a vendor should not also approve payments to it.

Python Roles and permission checks

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The last loop is a miniature segregation-of-duties audit; real ERPs ship tools for this.

People around the system

  • Executive sponsor: a senior leader who funds and champions the project.
  • Process owner: accountable for how a process (for example order-to-cash) works.
  • Business analyst: turns needs into requirements.
  • Functional consultant / administrator: configures the system.
  • Developer: builds extensions and integrations.
  • Data steward: keeps master data clean.
  • Key users and end users: test, train and use it every day.

Other words you will meet: configuration (changing settings) versus customisation (writing code), tenant (one customer's isolated space in a cloud product), instance or environment (development, test, production), and go-live (the day the system starts real use).

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which of these is master data?

    Items, customers and vendors are long-lived master data; orders, invoices and payments are transactions.
  2. 2. Why are posted documents usually corrected with a reversing document?

    Reversal keeps history intact so the accounting trail stays complete.
  3. 3. What is segregation of duties?

    Separating, for example, vendor creation from payment approval reduces fraud risk.
  4. 4. Configuration differs from customisation because configuration

    Configuration uses built-in options; customisation adds code and carries upgrade risk.

Summary

  • Master data is long-lived; transactions record events and refer to master data.
  • Documents are posted, and corrected by reversal; they form a document flow.
  • ERPs model companies, units, calendars, currencies; CRMs model teams, territories and hierarchies.
  • Roles bundle permissions; least privilege and segregation of duties limit risk.
  • Know the project roles and the words configuration, customisation, tenant and go-live.

Next: Order to Cash