Recycle a logical path for converted data

Jimbo's picture

No logical path.When creating LSMW objects of type "Standard Batch/Direct Input" it is necessary to create a Logical Filename in a Logical Path and associate it with a Physical file. The reason why is not important or necessarily known, but the system will throw the "No logical path specified for the converted data" error when the user lacks the permissions necessary to create these things.

Normally, the Specify Files step in creating an LSMW is a breeze as LSMW will automatically propose the names of .READ and .CONV files. These names tend to be just fine except when the names of LSMW projects, subprojects and objects are too long so it's seldom that any thought goes into them.

In many implementations, the data migration resources will have a very limited set of permissions, but the inability to make Logical Files or Logical Paths does not have to limit the creation of new Objects. This workaround includes three methods to find pre-existing files to recycle for the purpose of conversion.

The easiest and simplest solution is to recycle the Converted Data information from an existing LSMW object. This will work fine so long as no other resource is using the old LSMW object that is already associated with the file at the same time as the new LSMW object is being used. If another resource is using the file at the time that it is overwritten then the results can be amusing, but not catastrophic--especially if the LSMW objects are for loading different types of objects. A little coordination will eliminate even the small chance that there will be a collision.
No logical path.

The FILE transaction is another great source for finding abandoned (or seldom used) files that have already been assigned a Logical Filename in a Logical Path. It is important to refrain from using any file that even remotely looks like it is being used or may be used one day.
No logical path.
No logical path.

The last option is to look in the cross-client FILENAMECI table to find unused files. Files that start with "Z" tend to be a good bet, but files that end in .LSMW.CONV are even better.
No logical path.