The Software Update Manager (SUM) uses a specific file to automatically identify and include transport requests during an upgrade or conversion. Administrators must create a file named umodauto.lst in the /abap/var directory. This file contains a list of transport requests, including modification adjustment transports from SPDD/SPAU activities performed in the predecessor (development) system. During the PREPINPUT/MODTRPREP phase, SUM reads this file to determine which transports to import, thus ensuring that modifications are correctly applied to the target system.

A. By searching for transport requests in DIRTRANS, subdirectory "transport"

This directory is the general location for transport data files, but SUM does not scan it to identify specific adjustment transports; it requires an explicit list for automation.

B. By searching for transport requests that are assigned to project SAPADJUST

While adjustment transports are created under the SAPADJUST project in the development system, SUM does not use the project attribute to identify them for import in subsequent systems.

C. By searching for transport requests named K0

This is not a valid naming convention for transport requests. Transport request names follow a specific format, typically K9xxxxx, and K0 is not a recognized identifier.

1. SAP Official Documentation: Converting SAP Systems to SAP S/4HANA Using Software Update Manager 2.0 SP 18

Section 5.3.2.2 "Phase PREPINPUT/MODTRPREP: Enter Modification Adjustment Transports". The guide states: "If you want to include modification adjustment transports or other transports containing custom objects in the procedure

you have to create the file /abap/var/umodauto.lst. In this file

you list the transport requests that you want to be imported." (Document available on the SAP Help Portal).

2. SAP Official Documentation: Software Update Manager 2.0 Guides

"Adaption of Custom Code and Modifications". This set of guides explains the overall process where modifications are captured in a transport in the development system. For follow-on systems (QAS

PRD)

the SUM tool is informed of this transport via the umodauto.lst file to ensure consistency. (Referenced in various SUM guides on the SAP Help Portal).