1. What is the difference between standard and consumable procurement?
Ans:
Standard procurement generally involves materials managed as inventory, with stock quantities updated through goods movements. Consumable procurement covers items purchased for direct use by a department or business activity, often requiring an account assignment such as a cost centre or internal order. The appropriate process depends on the material and accounting requirements.
2. How does a purchase order account assignment affect procurement?
Ans:
Account assignment identifies where the cost of a purchasing item should be charged. Depending on the requirement, the destination may be a cost centre, asset, internal order, or another supported object. Correct assignment ensures that purchasing transactions are associated with the appropriate business expense or investment and supports accurate financial reporting.
3. How would you investigate an incorrect purchasing organisation assignment?
Ans:
- Review the purchasing organisation entered in the document.
- Check the relevant company code and plant assignments.
- Verify supplier purchasing data and organisational extensions.
- Inspect any system message related to the assignment.
- Correct the data through the approved change process and retest.
4. What is the role of company code integration in SAP MM?
Ans:
The company code represents an organisational unit for which financial statements are maintained. SAP MM purchasing and inventory transactions can connect with the assigned financial structure when accounting-relevant postings occur. Proper organisational assignments help ensure that inventory values, expenses, and related financial entries are recorded for the correct legal entity.
5. How would you investigate a purchase order that has not been delivered?
Ans:
I would review the order delivery date, supplier confirmations, open quantities, and any delivery schedule information. I would check whether the order was transmitted correctly and contact the supplier or buyer for an updated status. I would document the delay, assess its business impact, and follow the organisation's escalation process.
6. What is the significance of tolerance limits in purchasing and invoice processing?
Ans:
Tolerance limits define acceptable differences for specified transaction checks, depending on the configured process. In invoice verification, they can help determine whether price or quantity variances require warnings or blocking. Proper settings support consistent financial controls, reduce unnecessary manual reviews, and ensure that significant discrepancies are investigated before further processing.
7. How would you document an SAP MM business requirement?
Ans:
I would describe the business objective, current workflow, expected outcome, stakeholders, and relevant SAP transactions. I would identify required master data, organisational dependencies, validation rules, exceptions, and reporting needs. I would also define acceptance criteria and test scenarios so that the proposed solution can be reviewed and validated by the business team.
8. What is the importance of testing master data changes?
Ans:
Master data changes can affect purchasing, inventory, planning, and accounting activities. Testing confirms that updated values behave as expected and do not create unintended process issues. I would validate the changed fields, relevant organisational views, and representative business transactions, then document the results and resolve any unexpected behaviour before release.
9. How can duplicate supplier records affect procurement?
Ans:
Duplicate supplier records can create inconsistent purchasing histories, fragmented reporting, and confusion during supplier selection or invoice processing. I would compare available supplier identifiers and relevant master data, follow the organisation's duplicate-checking procedure, and coordinate any approved consolidation or record correction with the responsible master data team.
10. How would you prepare for SAP MM user acceptance testing?
Ans:
I would review the approved requirements, identify business users, and prepare test cases covering normal processing and important exceptions. I would arrange suitable test data, define expected outcomes, and record actual results. Any defects would be logged with supporting details, retested after correction, and signed off by the appropriate stakeholders.