1. How do you create and maintain a material master in SAP MM?
Ans:
A material master contains essential information about materials used in purchasing, inventory, planning, and accounting. Creation involves selecting the appropriate material type, maintaining descriptions, units of measure, material groups, and required organisational views. Accurate data helps ensure consistent transactions and reliable reporting across business functions.
2. How would you manage an urgent material requirement from a business department?
Ans:
First, verify the requested material, required quantity, delivery date, and available stock. If replenishment is necessary, review approved suppliers, existing contracts, and purchasing conditions before initiating the appropriate procurement process. Coordinate with stakeholders to obtain approvals, monitor delivery progress, and communicate any potential delays.
3. What is the purpose of a purchasing information record?
Ans:
A purchasing information record stores purchasing-related details for a particular material and supplier. Depending on the maintained data, it can include prices, delivery information, supplier material references, and purchasing conditions. This information supports purchasing document creation and helps buyers apply consistent commercial terms during procurement.
4. How do you investigate incorrect stock quantities in SAP?
Ans:
Compare the reported stock balance with the relevant plant, storage location, and stock category. Review material documents, goods receipts, goods issues, and transfer postings to identify missing or incorrect transactions. Verify the physical stock and obtain the necessary authorisation before correcting discrepancies through the approved inventory process.
5. What is the purpose of a scheduling agreement?
Ans:
A scheduling agreement establishes an ongoing purchasing arrangement with a supplier for materials or services. Delivery schedules communicate quantities and required delivery dates over the agreement period. This approach supports recurring procurement, improves supply coordination, and reduces the need to create separate purchasing agreements for every delivery.
6. How does SAP MM support procurement cost control?
Ans:
SAP MM helps control procurement expenditure through purchasing conditions, approved supplier arrangements, purchase order monitoring, and document-based verification. Buyers can compare negotiated prices with order values and investigate unexpected charges. Integrating procurement records with financial accounting improves expense visibility and supports purchasing decisions based on accurate information.
7. How would you resolve an error during goods receipt posting?
Ans:
Review the displayed error message and verify the purchase order, material, plant, storage location, quantity, and delivery information. Check whether the order is valid for receipt and whether any required fields or settings are missing. Correct the identified issue through the authorised process and confirm that the material document posts successfully.
8. Why is supplier evaluation important in procurement?
Ans:
Supplier evaluation helps organisations assess vendors using relevant factors such as delivery reliability, product quality, pricing, and service performance. Maintaining accurate purchasing history and reviewing supplier performance supports informed sourcing decisions. The results can help procurement teams identify risks, improve supplier relationships, and maintain dependable material availability.
9. How do you maintain data consistency between purchasing documents?
Ans:
Verify that purchase requisitions, purchase orders, goods receipts, and supplier invoices contain consistent material, quantity, pricing, and organisational information. Review document history and investigate mismatches before proceeding with subsequent activities. Standardised master data, validation controls, and regular reconciliation help minimise inconsistencies throughout the procurement cycle.
10. How would you handle a recurring SAP MM transaction failure?
Ans:
Collect the error message, transaction details, affected documents, and steps required to reproduce the problem. Determine whether the cause relates to master data, configuration, authorisations, or integration. Test the proposed correction in the appropriate environment, document the results, and monitor subsequent transactions to confirm that the problem has been resolved.