Create Logical Path and File for LSMW _ SAP Tribal Knowledge

10/3/2014 Create Logical Path and File for LSMW | SAP Tribal Knowledge

http://saptribalknowledge.wordpress.com/2011/07/13/create-logical-path-file-for-lsmw/ 1/7

SAP Tribal Knowledge

Useful Information for SAP Power Users2011/07/13

Create Logical Path and File for LSMW

Posted by feimster under LSMW, SAP | Tags: classification, Converted Data, FILE, goods movement,

logical file, logical path, LSMW, material BOM, namespace, planned independent requirements,Purchasing Info Records, RCSBI010, RM06IBI0, RM07MMBL, RM60IN00, SAP |

[13] Comments 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 proposesvalues 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 preventyou 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 thisLSMW: 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 thescreenshot 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 executetwo 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 atransport 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 Newentries.

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 orclick 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 environmentswhere 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 . Looking at the help for this field, youll find there are severalother 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 tocreate 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



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 withFILE. In Name, I use the same description as used in the logical path. In Physical file, youll need to

use the file name that was mentioned above in the LSMW. In Data format and Applicat.area, I use the

values ASC (ASCII data type) and BC (Basis Components/SAP NetWeaver), respectively. Finally, inLogical 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 thisfield. 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 transactionbetween 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 theConverted Data proposal. You can now assign your recently created logical path and logical file.

Other examples of load programs that require a logical path and file:



creating material BOMs(object 0030 / method 0001 / program RCSBI010)

posting goods movements(object 0110 / method 0000 / program RM07MMBL)

updating classification(object 0130 / method 0000 / program RM07MMBL RCCLBI03)

creating planned independent requirements

(object 0180 / method 0000 / program RM60IN00)

Your input is welcome for other examples you come across.

Edit 2014/02/04: the program name identified for updating classification was incorrect. It should havebeen RCCLBI03. The requirement for a logical path and file is still valid.

13 Responses to Create Logical Path and File for LSMW

1. [email protected] Says:

2012/03/21 at 14:11very good article..you saved my day..thanks.

Reply

2. Ivana Says:

2012/07/03 at 21:00

Very good article. Thank you very much!!

Reply3. Aravind Says:

2013/01/07 at 18:12Thank you very much. Its very helpfull and saved a lots of time for us.

Reply

4. Melynessa Says:

2013/03/08 at 03:16Great Job.. ^-^

Reply

5. devendra vella Says:

2013/06/26 at 11:33



after doing this it is displaying as logicalpath does not exist.

Reply

1. feimster Says:

2013/06/27 at 14:03Can you describe exactly what steps you followed and where you are seeing the error message?

Reply

6. Sudheer Says:

2013/07/20 at 10:18

HI

Followed the process, but logical path doesnt exist error is comingBut in F4 of logical path it is showing path I created.

Reply

1. feimster Says:

2013/07/21 at 02:46

Im not sure exactly how to respond. As you can see from other comments, several others havesuccessfully followed the process. If you can provide more details perhaps we can discover where

things went wrong.

Reply7. ManojKumar Says:

2013/09/01 at 09:00

Yes for me also,showing logical path does not exist after did the whole process as above

Reply1. feimster Says:

2013/09/02 at 18:39When you say showing the logical path, do you mean within LSMW or within the

transaction FILE?

Reply8. Giorgi Says:

2013/11/18 at 12:22Hi,

i had the same problem. If you want solve it you must change the syntax group. The syntax groupfor me was WINDOWS_NT.



PS: Sorry for my english.

Reply

1. feimster Says:

2013/11/18 at 12:57This highlights the point I tried to make in the original post with respect to the syntax group.

Check with your Basis team to see what type of underlying file system is being used. This willhelp you make the correct choice and avoid issues like the file not being found.

Reply2. gut Says:

2013/11/27 at 08:52

Thank you, that worked for me.I checked the system status entries and changed the syntax group according to that (it was WINNT)

Reply

Blog at WordPress.com. The Connections Theme.

Follow

Follow SAP Tribal Knowledge

Powered by WordPress.com

Documents

Create Logical Path and File for LSMW _ SAP Tribal Knowledge