Thanks to visit codestin.com
Credit goes to www.scribd.com

0% found this document useful (0 votes)
10 views32 pages

SAP MM Common Errors For Interview

The document outlines common errors encountered in SAP MM and provides interview-ready solutions for each scenario. It includes specific transactions and steps to resolve issues related to posting periods, number ranges, exchange rates, vendor data, and more. The responses emphasize the importance of configuration checks, data validation, and ensuring proper integration across modules.

Uploaded by

dipamnath56
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
10 views32 pages

SAP MM Common Errors For Interview

The document outlines common errors encountered in SAP MM and provides interview-ready solutions for each scenario. It includes specific transactions and steps to resolve issues related to posting periods, number ranges, exchange rates, vendor data, and more. The responses emphasize the importance of configuration checks, data validation, and ensuring proper integration across modules.

Uploaded by

dipamnath56
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 32

SAP MM Common Errors – Interview-Ready Format

Q1: How would you handle this situation: "Posting period 008
2010 is not open"?
A1:
Sure, here's how I would approach it: I’d go to transaction OB52 and
adjust the posting period parameters to open the required period. I’d
make sure that under the posting variant (like 1000), period 008 is
available for posting. Once updated, I’d save and test the changes. This
ensures timely transactions without disruption.

Q2: What would you do if you see: "Number range for trans./event
type IB in the year 2010 does not exist"?
A2:
I’d use transaction OMBT to define the missing number range for event
type IB for the relevant fiscal year. After validating the configuration, I’d
save it. This step helps prevent numbering conflicts and ensures
traceability.

Q3: How do you resolve exchange rate errors like: "Enter rate
EUR/INR, rate type M for 16.12.2010"?
A3:
I’d go to transaction OB08, enter the exchange rate for EUR/INR with rate
type M, and ensure the rate is valid for the specified date. Once
confirmed, I’d save the update. Accurate exchange rate settings are
crucial for global transactions and financial consistency.

Q4: What if the system says: "Country IN does not store a hard
currency"?
A4:
I’d open transaction OY01, locate the country settings for India (IN), and
enter the hard currency — INR in this case. After saving, this ensures
proper currency valuation and compliance with financial reporting
standards.

Q5: How do you fix: "Company code not assigned to country or


country to the calculation procedure"?
A5:

Classification: Internal–All Employees


Sensitivity: Internal (C3)
I’d navigate through SPRO → Financial Accounting → General Settings →
Tax on Sales and Purchases → Basic Settings → Assign country to the
calculation procedure. I’d make sure each company code is correctly
mapped to its country and save the changes. This alignment is essential
for accurate tax calculations.

Q6: What would you do if you get a workflow error like: "Linkage
to object BUS2009 event REJECTED cannot be written"?
A6:
I’d check the workflow configuration using transaction SWE2 to ensure
the event BUS2009 (REJECTED) is properly enabled. Then I’d validate all
dependencies and trigger the workflow again. Reviewing the logs helps
confirm successful execution.

Q7: How do you prevent duplicate purchase orders for the same
requisition?
A7:
I’d configure buyer authorizations in OMET and adjust system parameters
using SU52 to enforce unique PO creation. Additionally, I’d implement
user exits or BAdIs to flag duplicates before confirmation.

Q8: How would you handle this situation: Difficulty in tracking


scrapped materials using Movement Type 551?
A8:
I’d create a separate material master specifically for scrapped items and
configure Movement Type 551 to post to a dedicated scrap account. Then
I’d use SAP standard reports to monitor scrapped stock and ensure all
configuration parameters are correctly maintained.

Q9: What would you do if MRP planning across multiple plants


doesn’t show aggregated demand?
A9:
I’d first check if special procurement keys like key 40 are correctly
configured. If needed, I’d create a new procurement key to consolidate
planning. I’d also ensure that material master settings across all plants
are synchronized for accurate planning.

Q10: How do you identify which user exit triggers before saving a
Goods Receipt document?
A10:

Classification: Internal–All Employees


Sensitivity: Internal (C3)
I’d use transaction SMOD to explore available user exits. One commonly
used exit is MB_CF001. I’d simulate a GR process to test the functionality
and ensure custom enhancements don’t interfere with standard postings.

Q11: How do you resolve pricing inconsistencies due to subtotal


configuration issues?
A11:
I’d review the pricing schema and check if subtotal fields like KZWI1 are
correctly mapped. I’d validate these settings using the Test-Pricing
function and adjust the condition records to reflect the correct pricing
structure.

Q12: What if printed purchase orders show outdated data despite


accurate master records?
A12:
I’d check the purchase group details in table T024 using
transaction SE16 and update them if needed. I’d also ensure that vendor
master data is properly integrated with PO printing templates to maintain
consistency.

Q13: How do you handle master data inconsistencies or


duplication in vendor and info records?
A13:
I’d run SAP standard data cleansing reports and use XD02, XK02,
and MM02 to reconcile vendor and material master data. I’d identify and
merge duplicates to maintain consistency across the system.

Q14: What would you do if scheduling agreement delivery dates


are mismatched?
A14:
I’d open transaction ME31L to review and correct the delivery schedule.
I’d also coordinate with vendors to ensure their master data reflects
accurate delivery dates as per the agreement.

Q15: How do you resolve discrepancies in physical inventory


counts?
A15:
I’d refine the count procedures using transactions like MI10 or MI07, align

Classification: Internal–All Employees


Sensitivity: Internal (C3)
cycle count methodologies with warehouse characteristics, and adjust
shelf-life and frequency settings. I’d investigate discrepancies immediately
and reconcile inventory records.

Q16: How would you handle this situation: "Conversion factor for
unit of measure not found"?
A16:
I’d open MM02, go to the “Units of Measure” tab, and check if the
conversion factors between base and alternate units are defined. If they’re
missing, I’d enter the correct conversion factor and save the changes. This
ensures smooth processing of material transactions.

Q17: What would you do if the inspection lot fails to create during
goods receipt?
A17:
I’d check the Quality Management settings in SPRO under Quality
Inspection → Inspection Lot. Then I’d verify that the material master has
the quality inspection indicator active in MM02. I’d also ensure MM-QM
integration is properly configured and test the GR to confirm inspection lot
creation.

Q18: How do you resolve the error: "Valuation type not


determined for material"?
A18:
I’d review the material’s valuation data in MM02, especially the
Accounting view. Then I’d go to SPRO under Valuation and Account
Determination to ensure valuation classes and types are correctly
assigned. If needed, I’d update the valuation grouping and retest the
transaction.

Q19: What if a Purchase Requisition (PR) is not found even


though it exists?
A19:
I’d double-check the PR number in ME51 or ME52, and verify it hasn’t
been deleted or replaced. I’d also check the document flow and status
logs. If necessary, I’d recreate the PR, ensuring all mandatory fields are
filled correctly.

Q20: How do you fix batch expiry dates not updating in batch-
managed materials?

Classification: Internal–All Employees


Sensitivity: Internal (C3)
A20:
I’d go to MM02 and inspect the batch management data. Then in SPRO,
under Batch Management, I’d confirm that the expiry date field is enabled
and configured. I’d test by creating a new batch to ensure the expiry date
populates correctly.

Q21: What would you do if you get a data lock error while
changing a material master?
A21:
I’d use MM02 and ensure only one user is editing the record at a time. If
concurrent access is needed, I’d implement a user-exit or BAdI for conflict
resolution. Scheduling changes during low-traffic periods also helps avoid
such issues.

Q22: How do you resolve a vendor down payment request error


due to a missing due date?
A22:
I’d check the header data in the down payment request screen and ensure
the due date field is filled. In SPRO, under Financial Supply Chain
Management → Down Payments, I’d update the configuration to make the
due date mandatory. Then I’d reprocess the request.

Q23: What if material consumption is posted with the wrong


costing key?
A23:
I’d verify the costing key in the material master using MM02. Then I’d
check the account determination settings in SPRO under Valuation and
Account Determination to ensure the correct costing key is linked. I’d
adjust it if needed and reattempt the posting.

Q24: How do you fix invoice verification blocks due to tolerance


settings?
A24:
I’d go to SPRO, under Invoice Verification, and review the tolerance limits
for price and quantity differences. I’d adjust them to match company
policy and then revisit the invoice in MIRO to complete the posting.

Classification: Internal–All Employees


Sensitivity: Internal (C3)
Q25: What would you do if a goods movement reversal fails?
A25:
I’d check the original document using MB03 to understand its status.
Then I’d verify that reversal indicators are active in the movement type
configuration via SPRO. Finally, I’d use MBST to initiate the reversal after
confirming all prerequisites.

Q26: How would you handle this situation: A purchase order


doesn’t pull the correct price due to source list issues?
A26:
I’d check the source list using ME01 to ensure the correct vendor and
validity dates are maintained. Then I’d verify the pricing conditions in the
purchase info record via ME13. If needed, I’d adjust the entries and
reprocess the PO.

Q27: What if you encounter a batch classification error due to


missing characteristics?
A27:
I’d use MSC2N to review and update the batch master. Then I’d check the
classification setup in CL30N to ensure all required characteristics are
defined and assigned. After updating, I’d test the batch creation to confirm
successful classification.

Q28: How do you resolve an authorization error like “Not


authorized to post material document”?
A28:
I’d immediately check SU53 to identify missing authorizations. Then I’d
update the user’s roles in PFCG to include the necessary permissions for
transactions like MB1A or MB1B. After that, I’d ask the user to log off and
back in to test.

Q29: What would you do if automatic conversion from PR to PO


fails?
A29:
I’d review the configuration in SPRO under Purchase Requisition settings.
I’d ensure the PR has all required fields like release strategy and quantity.
If needed, I’d update the settings and retry the conversion or handle it
manually.

Classification: Internal–All Employees


Sensitivity: Internal (C3)
Q30: How do you fix GR/IR clearing errors due to account
determination issues?
A30:
I’d inspect the account determination settings in SPRO under Valuation
and Account Determination. I’d confirm that the correct accounts are
linked to the relevant movement types. Then I’d update number ranges
and account keys and test with a sample posting.

Q31: What if custom material fields aren’t visible in reports?


A31:
I’d check the Data Dictionary using SE11 to ensure the fields are
integrated. Then I’d use SQ01/SQ02 to adjust the selection screens in
custom reports. I’d also confirm that the enhancements are transported
across system views.

Q32: How do you resolve consignment stock posting errors due to


sale/return settings?
A32:
I’d review the consignment settings in the material master via MM02.
Then in SPRO, I’d check the valuation and account determination
parameters to ensure sale/return postings are enabled. After updating, I’d
test the consignment posting.

Q33: What would you do if batch expiry dates aren’t updating


properly?
A33:
I’d inspect the batch management data in MM02 and verify expiry date
settings in SPRO under Batch Management. I’d test by creating a new
batch and ensure the expiry date is populated correctly.

Q34: How do you fix data lock errors during material master
changes?
A34:
I’d ensure only one user is editing the material at a time using MM02. If
concurrent access is needed, I’d implement a user-exit or BAdI. Scheduling
changes during low-traffic hours also helps avoid conflicts.

Classification: Internal–All Employees


Sensitivity: Internal (C3)
Q35: What if vendor down payment requests fail due to missing
due dates?
A35:
I’d check the header data in the down payment request screen and ensure
the due date is filled. In SPRO, I’d update the configuration
under Financial Supply Chain Management → Down Payments to make the
due date mandatory.

Q36: How would you handle this situation: Conflicting validity


dates in purchase info records?
A36:
I’d open ME13 to review the info record and check for overlapping or
conflicting validity periods. I’d adjust the dates to ensure smooth price
determination and test the changes with a sample transaction.

Q37: What if MRP doesn’t trigger planned orders despite


demand?
A37:
I’d verify the MRP type and planning parameters in the material master
using MD02 or MD03. I’d also check the control parameters in the MRP
views to ensure planned orders are enabled. Then I’d run a test to confirm
planned orders are generated.

Q38: How do you resolve a batch management error due to


missing storage location?
A38:
I’d open MM02, go to the Warehouse Management view, and ensure a
valid storage location is assigned. If needed, I’d update the batch
management settings and test the process using MSC1.

Q39: What would you do if a quality info record is missing during


QM integration?
A39:
I’d use QP01 or QP02 to create or update the quality info record for the
material. I’d ensure it’s correctly linked to the material master and test a
transaction to confirm proper QM integration.

Q40: How do you fix an inactive material master record error?


A40:
I’d check the material’s status in MM02 to see if it’s marked inactive or

Classification: Internal–All Employees


Sensitivity: Internal (C3)
flagged for deletion. Depending on the situation, I’d either reinstate the
material or proceed with archiving. Then I’d update the necessary fields
and test the transaction.

Q41: What if freight charges aren’t calculated in purchase orders?


A41:
I’d examine the pricing conditions in the purchase info record
using ME13 and ensure the freight condition type (like KF00) is assigned
and maintained. I’d update the condition records and test a PO to confirm
freight charges are applied.

Q42: How do you resolve unit conversion errors in MRP?


A42:
I’d check the conversion factors in the material master via MM02 under
the Units of Measure tab. I’d correct any discrepancies and rerun MRP to
ensure planned quantities are calculated correctly.

Q43: What would you do if goods issue doesn’t update stock in


production orders?
A43:
I’d review the goods issue movement type configuration in SPRO and
ensure proper mapping. I’d also confirm that integration between PP and
MM is active. Then I’d revalidate the production order and test if stock
updates correctly.

Q44: How do you fix stock determination errors due to missing


plant assignment?
A44:
I’d open MM02 and check the plant settings in the organizational levels.
I’d ensure the plant is correctly linked to inventory management settings
and update the configuration as needed.

Q45: What if vendor returns fail due to missing inbound delivery


creation?
A45:
I’d verify the vendor return configuration in purchasing settings and
ensure inbound delivery creation is activated in the WM integration. I’d

Classification: Internal–All Employees


Sensitivity: Internal (C3)
update the return procedure and simulate a return transaction to confirm
it works.

Q46: How would you handle this situation: Duplicate physical


inventory documents causing reconciliation issues?
A46:
I’d use transactions MI07 or MI10 to review existing inventory count
documents. I’d identify and remove or merge duplicates, then reinitialize
the inventory cycle to ensure unique document creation.

Q47: What if vendor invoicing is blocked due to duplicate invoice


detection?
A47:
I’d check the duplicate invoice criteria in MIRO and adjust the tolerance
limits or detection settings in the configuration. I’d revalidate the invoice
and guide vendors on proper submission procedures.

Q48: How do you resolve batch determination failure during


production?
A48:
I’d verify the batch determination criteria in MSC2N and adjust
classification parameters using CL30N to include necessary
characteristics. Then I’d test a production order to confirm proper batch
selection.

Q49: What would you do if the GR/IR clearing run doesn’t process
automatically?
A49:
I’d open transaction F.13 or check the GR/IR clearing settings in SPRO. I’d
verify that scheduling parameters are correctly configured, trigger a
manual run to test, and then re-establish automation.

Q50: How do you fix consignment down payments not linking to


invoices?
A50:
I’d review consignment and down payment configurations in MM and SD.
I’d check vendor down payment settings in OBPY or related transactions
to ensure proper linkage. Then I’d simulate both down payment and
invoice posting to confirm.

Classification: Internal–All Employees


Sensitivity: Internal (C3)
Q51: What if vendor master updates fail due to missing
mandatory fields?
A51:
I’d use XK02 to update the vendor master record, ensuring all mandatory
and complementary fields are filled. I’d run a consistency check and save
the record after validation.

Q52: How do you resolve material price update failure when open
POs exist?
A52:
I’d identify open POs using ME2M, coordinate with the purchasing team to
close or complete them, and then update the material price. I’d confirm
the update with a test transaction.

Q53: What if the last purchase price doesn’t update in the vendor
info record?
A53:
I’d open ME13 and inspect the update settings for the last purchase price.
I’d check for custom enhancements or blocking parameters, manually
update the price if needed, and monitor future transactions.

Q54: How do you handle duplicate material master record


creation?
A54:
I’d search for duplicates using MM01/MM02 and run data consistency
reports. I’d merge duplicates per SAP guidelines and enforce stricter
validation during material creation to prevent recurrence.

Q55: What would you do if the archiving process for obsolete


materials fails?
A55:
I’d check archiving settings in SARA, ensure the material master is
flagged correctly, and validate configuration rules. I’d run a test archive
job to confirm successful processing before executing the full dataset.

Q56: How would you handle this situation: MRP doesn’t consider
safety stock, leading to understocking?
A56:

Classification: Internal–All Employees


Sensitivity: Internal (C3)
I’d open the material’s MRP view using MD02 or MD03, verify that the
safety stock value is correctly maintained, and adjust it if needed. Then I’d
run a test planning run to confirm that safety stock is now factored into
the requirement.

Q57: What if purchase orders fail due to incorrect delivery


tolerance settings?
A57:
I’d go to SPRO, navigate to Materials Management → Purchasing →
Purchase Order → Define Tolerance Limits, and correct or update the
default delivery tolerance values. I’d verify the changes by creating a
sample PO.

Q58: How do you resolve errors in releasing physical inventory


documents?
A58:
I’d use MI31 or MI07 to check the status of inventory documents. I’d
ensure that physical inventory parameters are correctly configured and
clear any pending locks manually before reinitiating the release process.

Q59: What would you do if third-party order processing fails


during PR to PO conversion?
A59:
I’d review the configuration in SPRO → Materials Management →
Purchasing and ensure that all necessary data like vendor, pricing, and
delivery conditions are maintained in the purchase info record. I’d correct
any missing details and retest the conversion.

Q60: How do you fix automatic account determination errors for


scrap material?
A60:
I’d check the account determination settings in SPRO → Valuation and
Account Determination and confirm that the scrap movement type is
linked to the correct G/L account. I’d update the configuration and
simulate a scrap posting to verify.

Q61: What if inventory valuation isn’t reflected correctly in


material documents?

Classification: Internal–All Employees


Sensitivity: Internal (C3)
A61:
I’d open MM02, review the Accounting view, and ensure that valuation
class and price determination settings are complete and accurate. I’d
update the data and test postings to confirm correct valuation.

Q62: How do you resolve transport request locking errors during


material master updates?
A62:
I’d check for locked transport requests using SE09 or SE10. If locked, I’d
release it or create a new transport request for the update. Then I’d retry
the material master update in MM02.

Q63: What would you do if standard price doesn’t update


correctly during revaluation?
A63:
I’d verify the revaluation process and pricing settings in the material
master’s Accounting view using MM02. I’d check custom revaluation rules
and authorized roles in SPRO, then run the revaluation and confirm the
updated standard price.

Q64: How do you fix errors caused by missing quality certificates


during inspection lot creation?
A64:
I’d audit the QM settings in SPRO → Quality Inspection, ensure the
certificate settings are integrated with the material’s QM view in MM02,
and test the inspection lot creation to validate certificate assignment.

Q65: What if batch selection fails during material issue in batch-


managed processes?
A65:
I’d verify batch determination criteria in MSC2N and adjust selection
parameters in CL30N to include necessary characteristics. Then I’d run a
test issue to confirm correct batch selection.

Q66: How would you handle this situation: Duplicate vendor


master records causing procurement errors?
A66:
I’d run a system-wide check using data consistency reports or
transaction XK02 to identify duplicates. Then I’d consolidate them
following SAP guidelines and enforce stricter data entry controls to

Classification: Internal–All Employees


Sensitivity: Internal (C3)
prevent recurrence. This ensures vendor data is consistent across
purchasing and invoicing.

Q67: What if unit of measure conversion factors are inconsistent


in the material master?
A67:
I’d open MM02, go to the Units of Measure tab, and verify that all
conversion factors between base and alternate units are accurate. I’d
correct any discrepancies and test a transaction to ensure proper
conversion.

Q68: How do you resolve MRP forecast data discrepancies?


A68:
I’d use MD04 to review MRP results and check the forecast profiles in the
material’s MRP view via MM02. I’d adjust the profiles to reflect realistic
consumption trends and rerun the forecast planning to validate the
corrected data.

Q69: What would you do if custom fields aren’t showing in


standard reports?
A69:
I’d verify the custom field setup in the Data Dictionary using SE11, then
update selection variants in SQ01/SQ02 to include those fields. I’d test
the reports to ensure the fields are now integrated.

Q70: How do you fix wrong storage status errors during stock
transfers?
A70:
I’d check the storage type and status configuration in MM02 and
in SPRO under Inventory Management. I’d update the mapping between
storage locations and statuses and re-run the transfer posting to confirm
the correct status is applied.

Q71: What if supplier evaluation data is outdated and affecting


vendor selection?
A71:
I’d review evaluation records in ME61, update weights and rating criteria,

Classification: Internal–All Employees


Sensitivity: Internal (C3)
and set up scheduled reviews to keep data current. I’d validate the
changes by testing a new PO to ensure accurate evaluations are reflected.

Q72: How do you resolve plant-specific material consumption


configuration errors?
A72:
I’d open MM02 and verify plant-specific settings like consumption posting
groups. Then I’d review SPRO under Inventory Management for plant-
specific rules, correct any misconfigurations, and simulate a posting to
ensure compliance.

Q73: What would you do if vendor sourcing is inconsistent during


material sourcing?
A73:
I’d inspect purchase info records using ME13 to ensure vendor data is
consistent. I’d update or consolidate vendor sources and verify proper
source list entries in ME01. Then I’d run a sourcing simulation to confirm
consistency.

Q74: How do you fix missing user authorizations for critical MM


transactions?
A74:
I’d use SU53 to identify missing authorizations and update user roles
in PFCG. After updating, I’d ask the user to log off and back in, then test
the transaction to confirm access.

Q75: What if SAP MM fails to integrate with external EDI systems?


A75:
I’d review EDI interface settings and mapping in the middleware system.
I’d verify that SAP MM transaction data (via IDocs) matches the expected
EDI format. Then I’d update the configuration and run an end-to-end test
to confirm integration.

Q76: How would you handle this situation: Valuation price fails to
update during price changes due to open posting periods?
A76:
I’d check the posting periods using OB52 to ensure they’re correctly open
or closed. Then I’d verify the pricing view in the material master
via MM02. If needed, I’d manually update the valuation price and test a
posting to confirm accuracy.

Classification: Internal–All Employees


Sensitivity: Internal (C3)
Q77: What if BOM creation fails due to incomplete material
hierarchy?
A77:
I’d use CS03 to check the BOM structure and ensure all required
components are assigned. Then I’d update the material master via MM02,
making sure hierarchical fields are filled. I’d re-run BOM explosion to
confirm everything is correctly displayed.

Q78: How do you resolve incorrect material group assignments


affecting reporting?
A78:
I’d open MM02, review the basic data view, and validate the material
group. If discrepancies are widespread, I’d update or reassign them in
batch. I’d confirm the changes using reports like SQ01.

Q79: What would you do if user-defined fields don’t appear in


purchase orders?
A79:
I’d check the field catalog in SE11 to ensure the field is integrated. Then
I’d adjust the PO creation settings in ME21N to include the field. I’d
simulate PO creation to confirm the field propagates correctly.

Q80: How do you fix movement type errors when using multiple
valuation areas?
A80:
I’d review movement type settings in SPRO under Inventory
Management. I’d ensure valuation areas are correctly assigned in the
material master for each plant. Then I’d update account determination
and test the posting.

Q81: What if automatic BOM explosion fails for variant


configuration?
A81:
I’d check variant configuration settings in CU41 and ensure all variant-
dependent BOM components are configured. Then I’d validate the
material master in MM02, confirming variant profiles and characteristics.
I’d test a production order to verify BOM explosion.

Classification: Internal–All Employees


Sensitivity: Internal (C3)
Q82: How do you resolve failure in creating supplementary POs
due to agreement issues?
A82:
I’d check outline agreements using ME31K or ME32K and validate the
validity dates. I’d update the agreement conditions and search criteria in
the PO release procedure. Then I’d retry supplementary PO creation.

Q83: What would you do if PR approval workflow is delayed?


A83:
I’d review the workflow configuration in SWDD and ensure triggering
events are active. I’d also confirm that agents have the necessary
authorizations via PFCG. Then I’d simulate a new PR and track the
approval flow.

Q84: How do you fix AR/GR discrepancies in cross-company stock


transfers?
A84:
I’d check intercompany settings in SPRO under Financial Accounting and
MM integration. I’d validate that the stock transfer process follows
intercompany rules. Then I’d update account determination and test the
AR/GR clearing.

Q85: What if requisition creation fails due to missing budget


limits?
A85:
I’d verify budget configuration in the Controlling module and update
available limits. I’d check ME51N to ensure budget checks are integrated.
If needed, I’d adjust the budget or configure workflow notifications for
approvals.

Q86: What if BOM explosion fails for variant materials?

A86:
I’d check variant configuration in CU41 and ensure all dependent
components are set. I’d validate the material master in MM02 for correct
variant profiles and characteristics. Then I’d test a production order to
confirm BOM explosion.

Q87: Why do supplementary purchase orders fail to generate?

Classification: Internal–All Employees


Sensitivity: Internal (C3)
A87:
I’d review outline agreements in ME31K/ME32K and check validity dates.
I’d update agreement conditions and retry PO creation after ensuring all
prerequisites are met.

Q88: What causes delays in PR approval workflows?

A88:
I’d check workflow triggers in SWDD and ensure agents have proper roles
in PFCG. I’d simulate a PR to verify the workflow sequence and fix any
missing events.

Q89: How do you fix AR/GR discrepancies in cross-company stock


transfers?

A89:
I’d check intercompany settings in SPRO under Financial Accounting and
MM integration. I’d validate that the stock transfer process follows
intercompany rules. Then I’d update account determination and test the
AR/GR clearing.

Q90: What if requisition creation fails due to missing budget


limits?

A90:
I’d verify budget configuration in the Controlling module and update
available limits. I’d check ME51N to ensure budget checks are integrated.
If needed, I’d adjust the budget or configure workflow notifications for
approvals.

Q91: What if serial number assignment fails during goods receipt


for high-value materials?

A91:
I’d check the serial number profile in MM02 and ensure it’s activated. I’d
update the profile settings and test the GR process to confirm serial
numbers are generated.

Q92: How do you resolve system lag during batch processing of


material documents?

Classification: Internal–All Employees


Sensitivity: Internal (C3)
A92:
I’d analyze performance using ST03N, schedule batch jobs during off-
peak hours, and optimize background jobs via SM37. If needed, I’d
consider database tuning or hardware upgrades.

Q93: What causes errors when copying material masters?

A93:
I’d use MM01 with “Copy from” and ensure all mandatory views are
selected. I’d check the source material in MM02 for missing fields and
validate the new record after copying.

Q94: Why does Plant Maintenance material data fail to sync with
MM?

A94:
I’d review integration settings in SPRO between MM and PM. I’d update
the material master to include PM-specific views in MM02 and test with a
maintenance order.

Q95: What triggers errors in cross-module data replication (MM,


SD, FI)?

A95:
I’d validate synchronization settings in SAP Landscape Transformation
(SLT) or middleware. I’d ensure master data consistency across modules
and test an integrated transaction.

Q96: What if tax codes are incorrectly determined in purchase


orders?

A96:
I’d check vendor master data in XK02 for correct tax category. I’d verify
tax procedure settings in SPRO and reprocess the PO to confirm correct
tax code assignment.

Q97: Why is there a delay in canceling unwanted purchase


orders?

A97:
I’d check pending workflows using SWI1 and clear them. I’d look for

Classification: Internal–All Employees


Sensitivity: Internal (C3)
system locks via SM12 and remove them. Then I’d cancel the PO
using ME22N and verify status updates.

Q98: What if archive jobs for material records don’t trigger?

A98:
I’d review archive settings in SARA and update job parameters. I’d ensure
material master data meets archival criteria and run a test archive job
manually.

Q99: How do you reconcile stock differences during inventory?

A99:
I’d use MI07 to identify discrepancies, investigate causes like miscounts,
and adjust inventory records. I’d re-run the inventory count to ensure
alignment.

Q100: What if dynamic reassignment of storage locations fails?

A100:
I’d check storage location data in MM02 and ensure reassignment criteria
are set in SPRO. I’d update distribution strategies and test a goods
movement to validate reassignment.

Q1: Can you walk me through a full-cycle SAP MM implementation


project you’ve worked on?

A1:
Certainly. I was part of a full-cycle SAP MM implementation for a
manufacturing client. The project followed the ASAP methodology. My
responsibilities included:

 Business Blueprinting: Conducted workshops with procurement


and inventory teams to understand AS-IS processes and define TO-
BE processes.

 Configuration: Set up material types, purchasing document types,


release strategies, number ranges, and automatic account
determination in OBYC.

 Master Data: Created templates for material master and vendor


master uploads using LSMW.

Classification: Internal–All Employees


Sensitivity: Internal (C3)
 Integration Testing: Coordinated with FI and SD teams to validate
end-to-end processes like third-party procurement and GR/IR
postings.

 Training & Go-Live: Delivered user training, created SOPs, and


supported cutover activities including stock uploads and open PO
migration.

Post go-live, I was involved in hypercare support and resolving initial user
issues.

🔹 Q2: What kind of integration have you handled between SAP


MM and other modules?

A2:
I’ve worked extensively on MM-FI, MM-SD, MM-QM, and MM-WM
integrations:

 MM-FI: Ensured correct account postings during GR and IR by


configuring OBYC. Resolved issues related to valuation class
mismatches and missing G/L accounts.

 MM-SD: Supported third-party sales order processing where MM


handled procurement and SD managed billing. Ensured correct
linkage between SO, PO, and delivery.

 MM-QM: Configured inspection types and ensured inspection lots


were created during GR. Worked with QM team to align quality info
records and vendor evaluations.

 MM-WM: Integrated WM for bin-level stock management.


Configured transfer orders and ensured seamless movement
between MM and WM.

Each integration required close coordination with respective module


consultants and thorough testing.

🔹 Q3: How do you handle change requests in a support project?

A3:
In support projects, change requests typically arise from evolving business
needs. My approach includes:

1. Impact Analysis: I assess the impact on existing configurations


and processes.

Classification: Internal–All Employees


Sensitivity: Internal (C3)
2. Documentation: I prepare a Functional Specification (FS) detailing
the requirement, proposed solution, and test scenarios.

3. Configuration & Testing: I implement the change in the


development system, perform unit testing, and support UAT with
business users.

4. Transport Management: I coordinate with the BASIS team to


move transports through the landscape.

5. Post-Implementation Review: I monitor the change post-


deployment to ensure stability.

For example, I once implemented a new release strategy for PRs based on
material group and value thresholds, which required changes in
classification and workflow.

🔹 Q4: Describe a challenging issue you faced and how you


resolved it.

A4:
One challenge was during GR posting where users received an error:
“Account determination not possible.” After analysis, I found that the
valuation class was missing in the material master and the OBYC settings
didn’t have a G/L account mapped for the transaction key.

Resolution Steps:

 Updated the material master with the correct valuation class.

 Mapped the valuation class to the appropriate G/L account in OBYC.

 Tested the GR process and confirmed successful posting.

I also created a checklist for master data validation to prevent recurrence.

🔹 Q5: How do you ensure data consistency during cutover?

A5:
During cutover, data consistency is critical. I follow these steps:

 Master Data Validation: Ensure material and vendor masters are


complete with mandatory fields.

 Open PO Migration: Use LSMW or BAPI to upload open POs,


ensuring correct document types and account assignments.

Classification: Internal–All Employees


Sensitivity: Internal (C3)
 Stock Uploads: Use transaction MB1C or MIGO with movement
type 561 for initial stock uploads.

 Reconciliation: Cross-check uploaded data with legacy system


reports.

 Dry Runs: Conduct mock cutovers to identify gaps and refine the
process.

I also maintain a cutover checklist and coordinate with cross-functional


teams to ensure smooth transition.

Q6: Have you worked on any custom developments in SAP MM?


Can you explain one?

A6:
Yes, I’ve worked on several custom developments. One notable example
was a custom report for tracking vendor performance based on
delivery timelines and quality scores.

Scenario:
The client wanted a report that consolidated vendor delivery performance,
GR delays, and quality inspection results.

My Role:

 I gathered requirements from the procurement and quality teams.

 Created a Functional Specification (FS) detailing the logic, data


sources (EKPO, MSEG, QALS), and layout.

 Coordinated with the ABAP developer to build the report using ALV.

 Conducted testing and validation with users.

Impact:
The report helped procurement teams make informed decisions during
vendor negotiations and improved vendor accountability.

🔹 Q7: How have you configured workflows in SAP MM?

A7:
I’ve configured release strategies for Purchase Requisitions and
Purchase Orders using workflows.

Steps Taken:

 Defined characteristics (e.g., document type, value, material group)


in CL20N.

Classification: Internal–All Employees


Sensitivity: Internal (C3)
 Created classes and assigned them to release groups.

 Configured release codes and strategies in SPRO.

 Integrated with workflow events using SWE2 and SWDD.

Example:
For a client, I set up a multi-level approval workflow for PRs above ₹5
lakhs. The workflow triggered notifications to department heads and
finance controllers.

Challenge:
Initially, the workflow didn’t trigger due to missing event linkage. I
resolved it by enabling the correct event in SWE2 and testing with
simulated PRs.

🔹 Q8: Do you have exposure to SAP Ariba or EWM?

A8:
I’ve had functional exposure to SAP Ariba during a sourcing
integration project.

Ariba Experience:

 Participated in mapping vendor master and material


master between SAP MM and Ariba using CIG (Cloud Integration
Gateway).

 Supported testing of PO replication from Ariba to SAP MM.

 Helped resolve issues related to unit of measure


mismatches and vendor ID mapping.

EWM Exposure:

 Worked with EWM consultants during stock transfer and bin-level


inventory integration.

 Ensured MM movement types were correctly mapped to EWM


processes.

 Supported testing of inbound deliveries and putaway


strategies.

While I haven’t configured Ariba or EWM directly, I understand their


integration touchpoints and can collaborate effectively with respective
teams.

Classification: Internal–All Employees


Sensitivity: Internal (C3)
🔹 Q9: How do you handle difficult clients or stakeholders during a
project?

A9:
Handling clients requires a mix of technical clarity, empathy, and
proactive communication.

Example Situation:
During an implementation, a stakeholder was unhappy with the PO
approval process being too rigid.

My Approach:

 Scheduled a one-on-one session to understand their concerns.

 Explained the compliance and audit benefits of the release strategy.

 Proposed a flexible threshold-based approval matrix and


demonstrated it in the sandbox.

 Documented the change request and got it approved through CAB


(Change Advisory Board).

Outcome:
The stakeholder appreciated the responsiveness, and the revised process
was adopted company-wide.

🔹 Q10: How do you ensure successful communication across


cross-functional teams?

A10:
I use structured communication and collaboration tools like:

 RACI Matrix to define roles and responsibilities.

 Weekly sync meetings with SD, FI, PP teams to track


dependencies.

 Issue tracker dashboards to log and monitor open items.

 Functional documentation with clear process flows and test


cases.

I also ensure that technical jargon is translated into business language


when speaking with non-technical stakeholders.

Interviewer: Can you briefly introduce yourself and your SAP MM


experience?

Classification: Internal–All Employees


Sensitivity: Internal (C3)
🧑‍💼 Candidate (Dipam):
Sure. I’m Dipam Nath, currently working as an Associate Manager with 3
years of experience in SAP MM. I’ve worked on one full-cycle
implementation and two support projects. My expertise includes
procurement processes, inventory management, release strategies, and
integration with FI, SD, and QM modules. I’ve also handled master data
governance and participated in workflow configuration and testing.

🎤 Interviewer: Tell me about a full-cycle implementation project


you’ve worked on.

🧑‍💼 Candidate:
I was part of a greenfield implementation for a manufacturing client. My
role involved:

 Requirement Gathering: Conducted workshops with procurement


and warehouse teams.

 Blueprinting: Documented AS-IS and TO-BE processes.

 Configuration: Set up document types, number ranges, release


strategies, and OBYC for account determination.

 Testing: Performed unit testing and supported UAT.

 Cutover & Go-Live: Managed stock uploads, open PO migration,


and post-go-live support.

One challenge was aligning the release strategy with complex approval
hierarchies, which I resolved by using classification and workflow triggers.

🎤 Interviewer: What integrations have you handled in SAP MM?

🧑‍💼 Candidate:
I’ve worked on MM-FI, MM-SD, MM-QM, and MM-WM integrations.

 MM-FI: Configured OBYC for automatic postings during GR/IR.


Resolved issues like missing G/L accounts and valuation class
mismatches.

 MM-SD: Supported third-party order processing where MM handled


procurement and SD managed billing.

 MM-QM: Ensured inspection lots were created during GR and linked


quality info records.

Classification: Internal–All Employees


Sensitivity: Internal (C3)
 MM-WM: Coordinated with WM consultants to manage bin-level
inventory and transfer orders.

These integrations required close collaboration and thorough testing


across modules.

🎤 Interviewer: Have you worked on any custom developments?

🧑‍💼 Candidate:
Yes. One example is a custom vendor performance report that
consolidated delivery timelines, GR delays, and quality scores.

I created the functional spec, identified data sources (EKPO, MSEG, QALS),
and worked with ABAP developers to build the report. It helped
procurement teams improve vendor selection and accountability.

🎤 Interviewer: How do you handle change requests in a support


environment?

🧑‍💼 Candidate:
I follow a structured approach:

1. Impact Analysis – Assess configuration and process impact.

2. Documentation – Prepare FS and get stakeholder sign-off.

3. Configuration & Testing – Implement in DEV, test, and support


UAT.

4. Transport Management – Coordinate with BASIS for deployment.

5. Post-Go-Live Monitoring – Ensure stability and user adoption.

For example, I implemented a new PR release strategy based on material


group and value thresholds.

🎤 Interviewer: How do you manage stakeholder expectations?

🧑‍💼 Candidate:
I maintain transparency and proactive communication. I use:

 Weekly status updates

 RACI matrix for role clarity

 Functional documentation with visuals

 Workshops to demo solutions

Classification: Internal–All Employees


Sensitivity: Internal (C3)
In one case, a stakeholder was resistant to a new PO approval process. I
addressed their concerns, proposed a flexible matrix, and gained buy-in
through sandbox demos.

🎤 Interviewer: Have you worked with SAP Ariba or EWM?

🧑‍💼 Candidate:
I’ve had functional exposure to both:

 Ariba: Participated in integration testing via CIG, mapped vendor


and material data, and resolved UoM mismatches.

 EWM: Supported inbound delivery and bin management


integration. Ensured MM movement types aligned with EWM
processes.

Though I haven’t configured them directly, I understand their touchpoints


and collaborate effectively with respective teams.

🎤 Interviewer: What are some common errors you’ve resolved in


SAP MM?

🧑‍💼 Candidate:
Some frequent ones include:

 Account assignment mandatory error – Resolved by updating


material type and valuation settings.

 Source list not maintained – Fixed via ME01 and info record
creation.

 Posting period not open – Resolved using OB52.

 GR/IR mismatch – Handled via F.13 and OBYC review.

I maintain a knowledge base of recurring issues and resolutions for faster


support.

Interviewer: Can you describe your experience with SAP MM in a


manufacturing or mining domain?

🧑‍💼 Candidate (Dipam):


Yes. I’ve worked on SAP MM implementation and support for a
manufacturing client in the metals sector. The procurement process was
complex due to high-value raw material sourcing, subcontracting, and
integration with production planning (PP) and plant maintenance (PM).

Classification: Internal–All Employees


Sensitivity: Internal (C3)
I configured procurement types for raw materials, semi-finished goods,
and consumables. I also supported subcontracting processes where
materials were sent to vendors for processing and returned as finished
goods.

🎤 Interviewer: How did you handle subcontracting in SAP MM?

🧑‍💼 Candidate:
Subcontracting was a key process. I configured:

 Subcontracting POs with item category L.

 BOMs for components to be issued to vendors.

 Movement types 541/543 for issuing and receiving components.

 Inventory tracking using ME2O and MB1B.

I also ensured integration with FI for correct account postings and


with PP for production order alignment.

🎤 Interviewer: What challenges did you face in integrating MM


with Plant Maintenance (PM)?

🧑‍💼 Candidate:
One challenge was ensuring that maintenance orders triggered
correct purchase requisitions for spare parts. I worked with PM
consultants to:

 Align material master views for PM usage.

 Ensure account assignment category F was used for internal


orders.

 Validate release strategy for PRs generated from PM orders.

We also created a custom report to track PRs linked to maintenance


orders for better visibility.

🎤 Interviewer: How did you manage vendor evaluation and


sourcing in a mining context?

🧑‍💼 Candidate:
Vendor evaluation was critical due to regulatory and quality standards. I
configured:

 ME61 for scoring vendors on delivery, quality, and price.

Classification: Internal–All Employees


Sensitivity: Internal (C3)
 Source lists with fixed vendors for critical materials.

 Quota arrangements to distribute procurement across approved


vendors.

I also supported Ariba integration for strategic sourcing and ensured


vendor master data was synchronized between systems.

🎤 Interviewer: What kind of reporting or analytics have you


supported in SAP MM?

🧑‍💼 Candidate:
I’ve worked on:

 Custom GR/IR aging reports to track pending invoices.

 Vendor performance dashboards using ALV reports.

 Inventory valuation reports for finance reconciliation.

I collaborated with ABAP developers to design reports and ensured they


aligned with business KPIs.

🎤 Interviewer: How do you ensure compliance and audit readiness


in MM processes?

🧑‍💼 Candidate:
I ensure:

 Release strategies are properly documented and approved.

 Segregation of duties (SoD) is maintained via role design in


PFCG.

 Change logs are enabled for master data.

 Archiving protocols are followed for obsolete materials and


documents.

I also support internal audits by providing transaction histories and


configuration documentation.

Interviewer 1 (Functional Lead): How do you lead a cross-


functional team during an SAP MM implementation?

🧑‍💼 Candidate (Dipam):


I lead by establishing clear communication, ownership, and alignment
across modules. I start with a RACI matrix to define roles and

Classification: Internal–All Employees


Sensitivity: Internal (C3)
responsibilities. During blueprinting, I ensure that MM processes are
aligned with SD, FI, PP, and PM requirements.

I conduct joint workshops, maintain a shared issue tracker, and hold


weekly sync meetings. For example, in a recent implementation, I
coordinated with SD and FI teams to streamline third-party procurement
and ensure correct account postings. I also facilitated conflict resolution
when PP and MM had overlapping responsibilities in subcontracting.

🎤 Interviewer 2 (Project Manager): How do you manage


stakeholder expectations, especially when there’s resistance to
change?

🧑‍💼 Candidate:
I approach resistance with empathy and data. First, I understand the
stakeholder’s concerns through one-on-one discussions. Then I
present business impact analysis and process simulations to show
the benefits of the proposed change.

For example, a stakeholder resisted implementing a release strategy for


PRs. I demonstrated how it would improve audit compliance and reduce
unauthorized purchases. I also proposed a flexible threshold-based
approval matrix. Once they saw the value, they became a champion for
the change.

🎤 Interviewer 3 (IT Director): What’s your approach to building a


future roadmap for SAP MM in a growing organization?

🧑‍💼 Candidate:
I start by assessing current pain points and business goals. Then I align
SAP MM capabilities with strategic priorities like cost control, supplier
collaboration, and inventory optimization.

I propose a phased roadmap:

1. Short-term: Stabilize core MM processes and improve reporting.

2. Mid-term: Integrate with Ariba for strategic sourcing and automate


workflows.

3. Long-term: Explore EWM for advanced warehouse operations and


analytics for predictive procurement.

I also recommend periodic process audits and user feedback loops to


refine the roadmap.

Classification: Internal–All Employees


Sensitivity: Internal (C3)
🎤 Interviewer 1: How do you ensure quality and compliance in
your SAP MM configurations?

🧑‍💼 Candidate:
I follow a structured QA process:

 Peer reviews of configuration and functional specs.

 Unit testing with edge cases.

 UAT with business users and sign-off.

 Documentation for audit readiness.

I also ensure compliance by enabling change logs, maintaining release


strategies, and aligning with SoD policies in role design. For example, I
once identified a risk where users could create and approve POs. I worked
with the security team to redesign roles and eliminate the conflict.

🎤 Interviewer 2: How do you mentor junior consultants or team


members?

🧑‍💼 Candidate:
I believe in hands-on mentoring. I assign them real tasks with guidance,
review their work, and explain the business context. I also encourage
them to explore SAP help documentation and attend internal knowledge-
sharing sessions.

For example, I mentored a junior consultant on configuring source lists


and info records. I walked them through the process, explained the impact
on MRP, and had them present their learnings to the team.

Classification: Internal–All Employees


Sensitivity: Internal (C3)

You might also like