Build brief · SAP MM
Configure a controlled supplier-choice scenario and explain why the system proposes one source over another.
Start with the business or technical outcome
Source determination is reliable only when master-data validity and business policy tell the same story. This field lab turns the topic into a small deliverable that can be built, checked and explained. A plant buys one raw material from two approved suppliers, reserves a fixed source for urgent periods and wants planned demand split under defined conditions.
Use a training client and fictional suppliers. Begin with organisational levels, material and purchasing data. A source list can control valid sources for a period, while a quota arrangement can distribute requirements among sources; exact behavior depends on configuration and process context.
Do not memorise transaction codes without tracing the business rule. Ask which purchasing organisation, plant, material, document date and requirement type are active when the proposal is made.
What to understand before opening the tool
Understand supplier and business-partner data, material purchasing views, purchasing info records, contracts or scheduling agreements, source-list validity, fixed-source indicators, MRP relevance and quota base or allocation concepts.
A “wrong supplier” proposal may be technically correct under the maintained dates and priorities. Troubleshooting should reproduce the requirement and inspect every candidate source before altering masters.
Material and Supplier Data
Use it for: provide organisational purchasing prerequisites Keep as evidence: master-data checklist
Purchasing Info Record
Use it for: hold supplier-material purchasing conditions and references Keep as evidence: valid record evidence
Source List
Use it for: control allowed, blocked or fixed sources by validity period Keep as evidence: dated source entries
Quota Arrangement
Use it for: distribute eligible requirements under configured logic Keep as evidence: quota and allocation review
The practical outcome is a source-determination test pack containing master-data map, validity cases, quota calculation evidence and exception notes. Build it with fictional, public or explicitly authorised data. Record the starting state before making changes, because a screenshot of the final screen cannot explain how the result was produced. The strongest evidence is a short chain: requirement, action, validation and one reflection on what you would improve.
Build the workflow in six controlled moves
Build one-source behavior first, then introduce a second eligible supplier and controlled date changes.
- Define the procurement ruleState approved suppliers, plant, material, validity periods and intended split.Checkpoint: Signed scenario matrix.
- Prepare master dataValidate material purchasing fields, supplier data and info records at the correct organisation levels.Checkpoint: Master readiness sheet.
- Maintain source-list casesCreate normal, fixed and blocked periods without overlapping rules accidentally.Checkpoint: Dated source-list export.
- Add quota logicMaintain eligible sources and opening quantities according to the exercise.Checkpoint: Quota arrangement record.
- Generate test demandCreate controlled requisitions or planning requirements on selected dates.Checkpoint: Requirement references and proposed sources.
- Explain every resultCompare proposal with validity, fixed source, quota and missing-master conditions.Checkpoint: Pass/fail test script with cause.
Do not rush through the successful path. Repeat one step with a controlled variation and compare the evidence. That second run reveals which inputs are important and gives you a concrete troubleshooting story for interviews.
Tools, decisions and proof
Date and eligibility conditions should be visible beside the expected supplier proposal.
| Decision or signal | Action to take | Evidence to retain |
|---|---|---|
| Single valid source | Propose the eligible supplier | Source list and requisition source |
| Fixed source in period | Prefer the fixed eligible entry as designed | Validity date and proposal |
| Supplier blocked | Exclude the blocked source | Block status and candidate list |
| Two quota sources | Distribute according to maintained values and history | Quota calculation evidence |
| No valid source | Raise or retain an exception for buyer action | Unassigned requisition and cause |
Failure tests that improve the project
Changing several master records at once makes source-determination problems difficult to explain.
- Ignoring organisational levels: A valid record in the wrong purchasing organisation or plant will not solve the scenario.
- Creating overlapping validity casually: Conflicting entries can produce proposals that look unpredictable.
- Treating quota as a random percentage: Understand the maintained base, allocated quantity and process behavior.
- Forcing a source without evidence: First inspect why the intended source is ineligible.
- Testing only today’s date: Future and boundary dates are essential for validity logic.
Turn the exercise into credible portfolio evidence
Build a five-case workbook showing one valid source, fixed source, blocked source, quota distribution and no-source exception. Add screenshots only where they prove dates or proposal results.
Draw the relationship among material, supplier, info record, source list, quota arrangement and purchase requisition. This demonstrates process understanding beyond navigation.
Explain it clearly in an interview
Explain the order in which you inspect organisational data, validity, fixed or blocked status and quota logic when a requisition proposes the unexpected supplier.
Peer review before calling the work complete
Ask another learner to inspect the result without watching you build it. Give them the original scenario—a plant buys one raw material from two approved suppliers, reserves a fixed source for urgent periods and wants planned demand split under defined conditions.—and the evidence pack, but not your intended conclusion. They should be able to trace the input, identify the main decision and locate the proof of the output. If they cannot, improve the labels, timestamps or explanation instead of adding decorative screenshots.
Use this acceptance condition during the review: Each test uses known dates and requirement inputs, candidate sources are explainable, master changes are isolated and expected results agree with the documented rule. Record one question the reviewer raised and the change you made in response. That small feedback loop makes the SAP MM source list and quota arrangement exercise more credible, easier to maintain and easier to explain under interview questioning.
Questions learners ask
What does a source list control?
It records source validity and control indicators for a material and plant or process context, subject to configuration.
What does a quota arrangement do?
It supports allocation of requirements among eligible sources using maintained quota logic and relevant quantities.
Why test validity dates?
Source eligibility is time-dependent, so a scenario can change at period boundaries without any new transaction.
Can a buyer always override the proposal?
That depends on configuration, document status and authorisation; the business control should be understood before manual change.
Use current product guidance
Menus, fields, permissions and service behavior can change between product versions or tenant configurations. Check the SAP Help Portal before applying version-sensitive steps in a live environment.
Build the complete skill path
Learn SAP MM master data, sourcing, purchasing, inventory, invoice verification and integration through complete business-process practice.
Final perspective
The real value of SAP MM source list and quota arrangement is the ability to complete a controlled task and defend the result with evidence. A learner who can show the input, explain the decision, verify the output and describe one realistic exception demonstrates far more than someone who has only memorised a menu path or definition.