Q: 8
How does SUM recognize modification adjustment transports from predecessor systems?
Options
Discussion
Its D, only if umodauto.lst actually exists in the right dir, otherwise no detection.
I don't think it's B. D is the one where SUM technically reads the umodauto.lst file to identify the adjustment transports. The SAP_ADJUST project thing is more about grouping, not recognition. Let me know if anyone saw it work differently.
D , SUM checks the umodauto.lst file to recognize those mods. Saw a similar question on practice and it was always D, not B or C.
Probably D. SUM checks the
umodauto.lst file to actually recognize the relevant transports. B is tempting since SAP_ADJUST is used, but that's for grouping, not recognition. Seen similar in practice questions, so pretty confident unless there's some edge case I'm missing.Seriously SAP never makes this stuff easy, always some cryptic file name. D
Had something like this in a mock, definitely D.
D not totally sure since B sounds reasonable too but pretty confident SUM uses umodauto.lst when actually importing. Let me know if you have different experience.
I've seen similar questions and went with B.
D is the one I've seen in SAP official materials, SUM checks the umodauto.lst file for these transports. If you're prepping, reviewing the upgrade docs and doing a couple of practice runs in sandbox really helps. Think that's right but open to a better source if anyone disagrees.
D that's what the official guide and SAP practice sets point to for this. Worth reviewing SUM upgrade documentation too if unsure.
Be respectful. No spam.
