Create Logical Path and File for LSMW

There are certain LSMW Direct Input programs that require you to specify a logical path & file when constructing
your LSMW. Youll find this is required in the Specify Files step of the LSMW.
The program for creating purchasing info records (object 0060 / method 0000 / program RM06IBI0) is a good
example.

The details of the rest of the LSMW are not pertinent to this discussion, so lets skip directly to the step Specify
Files.

This is the status in display mode. Switch to change mode and youll see that the system proposes values
for Imported Data and Converted Data. The values in these fields are limited to 45 characters for technical reasons,
so check that the proposed values do not exceed this length. The system will prevent you from saving if either of
the fields do not meet the criteria.

Drill into the Converted Data proposal and you can see that two additional fields are necessary for this LSMW: logical
path and logical file. Unfortunately, these cannot be created on the fly. You must exit LSMW and create them

before assigning. Before leaving, however, make a note of the file name on the screenshot above. We will assign
this specific file to the logical file we create below.
Use transaction FILE to start the process of creating the logical path and logical file. You should be aware that this is
a cross-client table the system will warn of this fact. In this transaction, well execute two steps to define the path
and file. Once complete, that data will be saved in a Workbench transport. With that in mind, you will need to be
working in a client where you have authority to create such a transport and are able to modify cross-client settings.

To start, use the folder labeled Logical File Path Definition. Although you can copy from existing, Ill show the
process to create from scratch to help understand all aspects. Click on the button New entries.

Enter an appropriate path name, up to 60 characters. The appropriate namespace for this entry includes names
starting with Y or Z. Additionally, type a description for this new entry. Press enter or click the green checkmark to
validate your new entry.

Highlight the new entry and double-click on the subfolder labeled Assignment of Physical Paths to Logical Path. In
this section, youll assign a placeholder.

Click on New Entries.

Ive always used the Syntax group Unix. Recognizing that Ive always been in SAP environments where Unix was
used, I cannot say if this is the only value that should ever be used. Looking at the dropdown, it is obvious that
there are other possibilities. Use what is appropriate for your environment. For the Physical path, use
<FILENAME>. Looking at the help for this field, youll find there are several other identifiers that could be added
here. From my experience, this suffices.

After validation, your new entry should look something like the screenshot above. The next step is to create the
logical file which has a link to the logical path. In order to do that the path has to be recorded in the database that
is, you need to save first.
Once the logical path is saved, you can continue. Double-click on the folder labeled Logical File Name Definition
and click on New Entries.

In the field Logical file, I use an identifier similar to the logical path above, replacing PATH with FILE. In Name, I
use the same description as used in the logical path. InPhysical file, youll need to use the file name that was
mentioned above in the LSMW. InData format and Applicat.area, I use the values ASC (ASCII data type) and BC
(Basis Components/SAP NetWeaver), respectively. Finally, in Logical path, use the logical path identifier created
above. You can see that there are dropdowns for the last three fields, but Physical file is free-form text. Be aware
that there is no system validation on this field. Be certain that you use the same value in the LSMW.

Above is the completed new entry after validation. Save again. If you did not leave the transaction between
creation of the logical path and logical file, the system should store this new entry in the same transport request.
Go back to the LSMW and the Specify Files step. Switch to change mode and drill into the Converted

Data proposal. You can now assign your recently created logical path and logical file.