Transport LSMW

Hi,
When we do LSMW system does'nt prompt for the request then,
how to transport LSMW.
Rgds,
fattesingh

Hi,
There are two methods for this. Can choose any one.
1)Extras>Export Projects>(Give the Project name)
In next screen(Choose what subproject, routines, etc.. you wan to copy then, Export Rules-->Export((Will prompt for file name)
A text file will be downloaded.
In the Target System
Goto LSMW Extras-->Import Projects and give the text file done.
2)Extras-->Generate Change Request
Assign a change request can then transport.
Regards,
AS

Similar Messages

Problem in Transporting LSMW project

Hi,
We created LSMW project in development environment. Then we created Transport request through menue Extras -> Create Change Request
We successfully transported this request to test environment. When status is checked through STMS_IMPORT everything was fine. However when we tried to open project through LSMW, it didn't exist.
Can anyone suggest, what could have gone wrong ?
Nishad

Hi,
if your problem is not allready solved.
You can not transport LSMW-Project - I do not know what this icon is for.
You have to export the project and than import on the new system.
use these icons.
best regards

How to Transport LSMW to development server to Prodution server

Hi all,
I would like to know how we transport LSMW(project, sub-project, Object) from development server to Production server.
Thanks
Vipin Nagpal

Hi Vipin,
Actually, it depends based upon the requirement. There are some advantages and disadvantages with both of the methods.
See the following documentation. I think this would be helpful for you and based upon your requirement you proceed further.
Transport LSMW Projects
The LSM Workbench provides data transport for a project via both the SAP transport system and down-/upload. (Excluded are the presettings for IDoc inbound processing. These presettings should be manually created in every SAP system and every client.)
1. Generate Change Request
Choosing this function creates an SAP change request containing all information about an LSMW project. This SAP change request can be exported / imported with the usual means of SAP correction and transporting. You can find this function in the initial screen under Extras -> Create change request.
When transporting LSMW data this way, you can trace the transports any time in SAP correction and transporting.
Note 1: When importing such a request, the complete project is deleted from the target system first. It is then created again.
Note 2: When exporting the transport request, all changes to the selected project made until the time of export are entered (not only until the time of creation of the transport request.)
2. Export Project
In the initial screen, select Extras  Export project. This first displays the structure tree of the selected project. Via Select / Deselect you can select whether the entire project or parts of the project are exported. Then select Export. The program then creates an ASCII file.
Note: The selected elements are exported together with their documentation
3.Import ProjectThe exported mapping and rules can be imported into another SAP system.
On the selection screen, select Extras -> Import. The program then prompts you to enter the name of the PC file. The file is imported and the contents are analyzed. After the analysis, a list of the subprojects and objects found is displayed.
You can now mark the objects to be imported. Project data existing already are check-marked. They are overwritten by the import.
You can prevent a project already existing in the target system from being overwritten by using function "Import under different name".
Note: The selected elements are imported together with their documentation.
If you feel this is helpful, don't forget to reward points.

Transporting LSMW without creating transport request( from quality to prodn

Hi All,
I have created an LSMW in quality, I need to transport it to production with out creating any transport request.
Kindly let me know the procedure for the same.
Please help!!!
Vivek Gupta

Hi,
In the transaction LSMW, from the menu:
From your Quality system give your lsmw name and then do:
Extras->Export Project
This will export your lsmw created to an local path.
Then after logging into Production you can import
that lsmw from the lsmw transaction only:
Extras->Import Project
Hope it helps
Regards
Mansi

Error when transport LSMW project

Error description:
When set up LSMW project in develop system, it is all right. But when transport to production system, its file path shows wrong. It looks the same as in Develop system. Now We delete the file path in P-System and re-create new file path the same as before, it can work. How could we solve this problem?
Thank you.

Hi,
LSMW is a transaction, which will let you mass upload almost any other transaction (FB01, FD01, AS91, etc.). You do it in the following way:
1. Enter into transaction LSMW (no menu path), possibly in a development / test system
2. First, define a project, subproject and object (relatively formal task).
3. On the horizontal menu, go to Goto -> Recordings. Click on "Create recording".
4. Enter the name and description of recording (freely definable).
5. I cannot simulate this now in my system, but SAP will ask you about transaction code (AS02) and will take you into the AS02 transaction. In this step, do the change manually. Make sure you "touch" (change / write something) in all fields which you want to update.
6. Once you are done, save the recording and return on the start page of LSMW. Click "Execute".
7. You will see a list of tasks. Do them one by one. They should be relatively simple (and I cannot help you with them). Important is step 3 (maintain source fields) - here you define the columns of your excel (csv) file in the particular order. In step 5 (field mapping and conversion rule), you assign file columns to SAP fields (note that you will see only those fields which you "touched" during recording). You need to go through all the steps. In the end, you get (and run) a batch session.
8. If you did this in a development system, transport the LSMW object (menu Extras - Export project, Extras - Import project). You have to do it via file, not via standard transports of configuration (it is perhaps more simple). 
Make sure you test it first in development or quality system!
Pls reward points if useful.
Regards,
Ameet

Transporting LSMW single object instead of entire project

Dear Experts,
When I am selecting LSMW object and then selecting Generate Change Request from Extras, then it is creating Transport request for entire project instead of a single object.
How can i transport single LSMW Object instead of entire project.
Please help me.
Thanks & Regards
Rangababu

Hi,
when you are on the first screen of LSMW, can't you go via Extras->Export Project. Then you can select on detailed level what you want to export to a flat file.
On your other system you can import this flat file (and you can even rename stuff while importing). Not sure, but it might be that the import functionality is blocked on your other system. If not, I think this is the way to go.

How to transport LSMW project

Can LSMW project be transported? If the answer is yes, how ?

<a href="http://help.sap.com/erp2005_ehp_02/helpdata/en/da/a22506a3291b418b759524b278dcde/frameset.htm">Steps are here!</a>
Step 1 Create a request SE10
Step 2 Export from client where LSMW is recorded
Step 3 Import in the client where LSMW is to be transported to.

I want to upload om data through lsmw. how can i create transport request for lsmw data.

can anyone help me?

Hi Anand,
There are 2 ways for transporting LSMW data from a system to another.
1) Export/import this method gives you the opportunity to select the subprojects or objects you want to transfer. Hence you don't transfer the object a colleague might have created and that should stay in development system. LSMW -> Extras -> Export project
2)Transport request with this method, you can transport a LSMW project in full (you cannot select the objects you want). With this method, the project will be transported as any other SAP object in a transport order.
LSMW -> Extras -> Create change request
For more information, refer below link Steps to copy LSMW from one client to another
Thanks
KH

How to transport the report object from development clint to quality clint

any body knows different ways of transferring report object from development clint to quality clint.pse send ...

Hi..
LSMW:
There are 2 ways for transporting LSMW data from a system to another.
Export/import this method gives you the opportunity to select the subprojects or objects you want to transfer. LSMW -> Extras -> Export project
Transport request with this method, you can transport a LSMW project in full (you can not select the objects you want). With this method, the project will be transported as any other SAP object in a transport order. LSMW -> Extras -> Create change request
Program variants
If you have several program variants in a development system that you want to transport, use the following method to transport them:
Execute program 'RSTRANSP' (via se38) and inform the program and/or variant names (you can transport variant of several programs in one shot).
Layout
In some transactions, one can save layout of the screen (sort, filter, ... criteria).
These layouts can be transported: In the required transaction, when your layouts have been saved, go to Settings -> Layout -> Layout Management. Select the desired layouts and go to Layout -> Transport... There you can add your layouts in existing TO or create a new one.
Database data
In some unusual cases, you might have to transport data of a SAP table.
Go to transaction SE16, select your entries and go to Table entry -> Transport entries. It's only possible for some tables...
If you cannot do it that way,you have to create a Workbench transport order with transaction SE10. When created, click on it, go in menu Request/task -> Object list -> Display object list.
Go in modification mode and add a new line with:
PgmID = R3TR
Obj = TABU
Object name = Name of your table
Double-click on the created line and, depending on your need, put '*' in the key field or double-click on it and select the key you need to transport.
Queries
Queries, datasets and user groups can be exported/imported between the systems using the Program RSAQR3TR.
Report template (ALV variants)
There is a button or somewhere in the menu Change/Select/Save/Manage Layout.
Go to Manage Layout, than Layout menu/ Transport.
SAPSCRIPT Files Transport
Use the program RSTXSCRP to upload and Download the SAPSCRIPT files to different systems
Transport SAPSCRIPT
Use the Program RSWBO052 to create the Transport Request for a SAPSCRIPT, In the Selection screen of the program, give R3TR FORM Give the Form name and press Execute button, it will ask the Development Class and the transport Request No.
Standard texts
Standard texts used in SAPScript(created with transaction SO10) can be included in transport orders. You have to create a Workbench transport order with transaction SE10. When created, click on it, go in menu Request/task -> Object list -> Display object list. Go in modification mode and add a new line with:
PgmID = R3TR
Obj = TEXT
Object name = TEXT,,ST,
Example :
R3TR / TEXT / TEXT,YMM_MEDRUCK_MAIN_16_EC,ST,F
Reward if useful
~Lakshmiraj~

Sales Order Creation using LSMW IDOC method.. ( Custome Interface)

Hi ABAP'rs,
                 Please provide me LSMW steps for creating Sales Order using IDOC method.
                        Thanks and Regards,
                                              Param.

LSMW-IDOC in General
LSMW Step by Step Guide: Legacy System Migration Workbench is an R/3 Based tool for data transfer from legacy to R/3 for one time or periodic transfer.
Basic technique is Import data from Spreadsheet / Sequential file, convert from source format to target format and import into R/3 database. LSMW not part of standard R/3, if we need this product email [email protected]
Advantages of LSMW:
Most of the functions are within R/3, hence platform independence.
Quality and data consistency due to standard import techniques.
Data mapping and conversion rules are reusable across projects.
A variety of technical possibilities of data conversion.
Generation of the conversion program on the basis of defined rules
Interface for data in spreadsheet format.
Creation of data migration objects on the basis of recorded transactions.
Charge-free for SAP customers and partners.
Working With LSMW:
Use TCODE LSMW
Objects of LSMW:
Project ID with max of 10 char to Name the data transfer project.
Subproject Used as further structuring attribute.
Object ID with max of 10 Characters, to name the Business object .
Project can have multiple sub projects and subprojects can have multiple objects.
Project documentation displays any documentation maintained for individual pop ups and processing steps
User Guide: Clicking on Enter leads to interactive user guide which displays the Project name, sub project name and object to be created.
Object type and import techniques:
Standard Batch / Direct input.
Batch Input Recording
   o If no standard programs available
   o To reduce number of target fields.
   o Only for fixed screen sequence.
BAPI
IDOC
o Settings and preparations needed for each project
Preparations for IDOC inbound processing:
Choose settings -> IDOC inbound processing in LSMW
Set up File port for file transfer, create port using WE21.
Additionally set up RFC port for submitting data packages directly to function module IDoc_Inbound_Asynchronous, without creating a file during data conversion.
Setup partner type (SAP recommended US) using WE44.
Maintain partner number using WE20.
Activate IDOC inbound processing.
Verify workflow customizing.
Steps in creating LSMW Project:
Maintain attributes choose the import method.
Maintain source structure/s with or without hierarchical relations. (Header, Detail)
Maintain source fields for the source structures. Possible field types C,N,X, date, amount and packed filed with decimal places.
Fields can be maintained individually or in table form or copy from other sources using upload from a text file
Maintain relationship between source and target structures.
Maintain Field mapping and conversion rules
For each Target field the following information is displayed:
o Field description
o Assigned source fields (if any)
o Rule type (fixed value, translation etc.)
o Coding.
o Some fields are preset by the system & are marked with Default setting.
Maintain Fixed values, translations, user defined routines Here reusable rules can be processed like assigning fixed values, translation definition etc.
Specify Files
o Legacy data location on PC / application server
o File for read data ( extension .lsm.read)
o File for converted data (extension .lsm.conv)
Assign Files to defined source structures
Read data Can process all the data or part of data by specifying from / to transaction numbers.
Display read data To verify the input data being read
Convert Data Data conversion happens here, if data conversion program is not up to date, it gets regenerated automatically.
Display converted data To verify the converted data
Import Data Based on the object type selected
Standard Batch input or Recording
o Generate Batch input session
o Run Batch input session
Standard Direct input session
o Direct input program or direct input transaction is called
BAPI / IDOC Technique:
IDOC creation
o Information packages from the converted data are stored on R/3 Database.
o system assigns a number to every IDOC.
o The file of converted data is deleted.
IDOC processing
o IDOCS created are posted to the corresponding application program.
o Application program checks data and posts in the application database.
Finally Transport LSMW Projects:
R/3 Transport system
o Extras ->Create change request
o Change request can be exported/imported using CTS
Export Project
o Select / Deselect part / entire project & export to another R/3 system
Import Project
o Exported mapping / rules can be imported through PC file
o Existing Project data gets overwritten
o Prevent overwriting by using
Import under different name
Presetting for Inbound IDOC processing not transportable.
Reward if useful.
regards
santhosh reddy

Lsmw with idoc

Hi all, Can any one send me the steps for upload material data using LSMW-IDoc method

hi,
Working With LSMW:
Use TCODE LSMW
Objects of LSMW:
Project ID with max of 10 char to Name the data transfer project.
Subproject Used as further structuring attribute.
Object ID with max of 10 Characters, to name the Business object .
Project can have multiple sub projects and subprojects can have multiple objects.
Project documentation displays any documentation maintained for individual pop ups and processing steps
User Guide: Clicking on Enter leads to interactive user guide which displays the Project name, sub project name and object to be created.
Object type and import techniques:
Standard Batch / Direct input.
Batch Input Recording
 o If no standard programs available
 o To reduce number of target fields.
 o Only for fixed screen sequence.
 BAPI
 IDOC
 o Settings and preparations needed for each project
Preparations for IDOC inbound processing:
 Choose settings -> IDOC inbound processing in LSMW
 Set up File port for file transfer, create port using WE21.
 Additionally set up RFC port for submitting data packages directly to function module IDoc_Inbound_Asynchronous, without creating a file during data conversion.
 Setup partner type (SAP recommended US) using WE44.
 Maintain partner number using WE20.
 Activate IDOC inbound processing.
 Verify workflow customizing.
Steps in creating LSMW Project:
 1) Maintain attributes choose the import method.
 2)Maintain source structure/s with or without hierarchical relations. (Header, Detail)
 3) Maintain source fields for the source structures. Possible field types C,N,X, date, amount and packed filed with decimal places.
 Fields can be maintained individually or in table form or copy from other sources using upload from a text file
 4) Maintain relationship between source and target structures.
 5) Maintain Field mapping and conversion rules
 For each Target field the following information is displayed:
 o Field description
 o Assigned source fields (if any)
 o Rule type (fixed value, translation etc.)
 o Coding.
 o Some fields are preset by the system & are marked with Default setting.
 6) Maintain Fixed values, translations, user defined routines Here reusable rules can be processed like assigning fixed values, translation definition etc.
 6) Specify Files
 o Legacy data location on PC / application server
 o File for read data ( extension .lsm.read)
 o File for converted data (extension .lsm.conv)
 7) Assign Files to defined source structures
 8) Read data Can process all the data or part of data by specifying from / to transaction numbers.
 9) Display read data To verify the input data being read
 10) Convert Data Data conversion happens here, if data conversion program is not up to date, it gets regenerated automatically.
 11) Display converted data To verify the converted data
Import Data Based on the object type selected
 Standard Batch input or Recording
 o Generate Batch input session
 o Run Batch input session
 Standard Direct input session
 o Direct input program or direct input transaction is called
BAPI / IDOC Technique:
 IDOC creation
 o Information packages from the converted data are stored on R/3 Database.
 o system assigns a number to every IDOC.
 o The file of converted data is deleted.
 IDOC processing
 o IDOCS created are posted to the corresponding application program.
 o Application program checks data and posts in the application database.
Finally Transport LSMW Projects:
 R/3 Transport system
 o Extras ->Create change request
 o Change request can be exported/imported using CTS
 Export Project
 o Select / Deselect part / entire project & export to another R/3 system
 Import Project
 o Exported mapping / rules can be imported through PC file
 o Existing Project data gets overwritten
 o Prevent overwriting by using
 Import under different name
for more information follow this link.
http://help.sap.com/saphelp_nw04s/helpdata/en/87/f3ae74e68111d1b3ff006094b944c8/content.htm
regards,
Ashokreddy

LSMW Copy Object

Hi,
In LSMW we have Project, SubProject, Object in this,
When I copied the Object Which is having Batch Input Method the Recording is not copied to my destination Object can any one please help out.
To Copy the Object I went Tcode: LSMW -> All Objects of the Project
You will get the list of the Object under the Project there click on the Object u wants to copy and go with (Ctrl+F4).

hi
r u looking to transfre the lsmw project to development server if so fallow the lines
Actually, it depends based upon the requirement. There are some advantages and disadvantages with both of the methods.
See the following documentation. I think this would be helpful for you and based upon your requirement you proceed further.
Transport LSMW Projects
The LSM Workbench provides data transport for a project via both the SAP transport system and down-/upload. (Excluded are the presettings for IDoc inbound processing. These presettings should be manually created in every SAP system and every client.)
1. Generate Change Request
Choosing this function creates an SAP change request containing all information about an LSMW project. This SAP change request can be exported / imported with the usual means of SAP correction and transporting. You can find this function in the initial screen under Extras -> Create change request.
When transporting LSMW data this way, you can trace the transports any time in SAP correction and transporting.
Note 1: When importing such a request, the complete project is deleted from the target system first. It is then created again.
Note 2: When exporting the transport request, all changes to the selected project made until the time of export are entered (not only until the time of creation of the transport request.)
2. Export Project
In the initial screen, select Extras  Export project. This first displays the structure tree of the selected project. Via Select / Deselect you can select whether the entire project or parts of the project are exported. Then select Export. The program then creates an ASCII file.
Note: The selected elements are exported together with their documentation
3.Import ProjectThe exported mapping and rules can be imported into another SAP system.
On the selection screen, select Extras -> Import. The program then prompts you to enter the name of the PC file. The file is imported and the contents are analyzed. After the analysis, a list of the subprojects and objects found is displayed.
You can now mark the objects to be imported. Project data existing already are check-marked. They are overwritten by the import.
You can prevent a project already existing in the target system from being overwritten by using function "Import under different name".
Note: The selected elements are imported together with their documentation.
If you feel this is helpful, don't forget to reward points.
if u find it useful plz mark the points
Regards,
Naveen

Two questions about the query and lsmw .

Hi Experts ,
Could you tell me how to download the query to local driver ? is it possible to do that ?
I hear somebody introduce lsmw this t-code . it can transfer the data from non-sap/r3 system ? has somebody can fully expain this t-code ?
Many thanks !!!
Best Regards,
Carlos Z

Hi,
      LSMW Step by Step Guide: Legacy System Migration Workbench is an R/3 Based tool for data transfer from legacy to R/3 for one time or periodic transfer.
Basic technique is Import data from Spreadsheet / Sequential file, convert from source format to target format and import into R/3 database. LSMW not part of standard R/3, if we need this product email [email protected]
Advantages of LSMW:
    Most of the functions are within R/3, hence platform independence.
   Quality and data consistency due to standard import techniques.
   Data mapping and conversion rules are reusable across projects.
   A variety of technical possibilities of data conversion.
   Generation of the conversion program on the basis of defined rules
   Interface for data in spreadsheet format.
   Creation of data migration objects on the basis of recorded transactions.
   Charge-free for SAP customers and partners.
Working With LSMW:
Use TCODE LSMW
Objects of LSMW:
Project   ID with max of 10 char to Name the data transfer project.
Subproject   Used as further structuring attribute.
Object   ID with max of 10 Characters, to name the Business object .
Project can have multiple sub projects and subprojects can have multiple objects.
Project documentation displays any documentation maintained for individual pop ups and processing steps
User Guide: Clicking on Enter leads to interactive user guide which displays the Project name, sub project name and object to be created.
Object type and import techniques:
Standard Batch / Direct input.
Batch Input Recording
      o If no standard programs available
      o To reduce number of target fields.
      o Only for fixed screen sequence.
    BAPI
    IDOC
      o Settings and preparations needed for each project
Preparations for IDOC inbound processing:
    Choose settings -> IDOC inbound processing in LSMW
    Set up File port for file transfer, create port using WE21.
    Additionally set up RFC port for submitting data packages directly to function module IDoc_Inbound_Asynchronous, without creating a file during data conversion.
    Setup partner type (SAP recommended US) using WE44.
    Maintain partner number using WE20.
    Activate IDOC inbound processing.
    Verify workflow customizing.
Steps in creating LSMW Project:
    Maintain attributes choose the import method.
    Maintain source structure/s with or without hierarchical relations. (Header, Detail)
    Maintain source fields for the source structures. Possible field types C,N,X, date, amount and packed filed with decimal places.
    Fields can be maintained individually or in table form or copy from other sources using upload from a text file
    Maintain relationship between source and target structures.
    Maintain Field mapping and conversion rules
    For each Target field the following information is displayed:
      o Field description
      o Assigned source fields (if any)
      o Rule type (fixed value, translation etc.)
      o Coding.
      o Some fields are preset by the system & are marked with Default setting.
    Maintain Fixed values, translations, user defined routines Here reusable rules can be processed like assigning fixed values, translation definition etc.
    Specify Files
      o Legacy data location on PC / application server
      o File for read data ( extension .lsm.read)
      o File for converted data (extension .lsm.conv)
    Assign Files to defined source structures
    Read data Can process all the data or part of data by specifying from / to transaction numbers.
    Display read data To verify the input data being read
    Convert Data Data conversion happens here, if data conversion program is not up to date, it gets regenerated automatically.
    Display converted data To verify the converted data
Import Data Based on the object type selected
    Standard Batch input or Recording
      o Generate Batch input session
      o Run Batch input session
    Standard Direct input session
      o Direct input program or direct input transaction is called
BAPI / IDOC Technique:
    IDOC creation
      o Information packages from the converted data are stored on R/3 Database.
      o system assigns a number to every IDOC.
      o The file of converted data is deleted.
    IDOC processing
      o IDOCS created are posted to the corresponding application program.
      o Application program checks data and posts in the application database.
Finally Transport LSMW Projects:
    R/3 Transport system
      o Extras ->Create change request
      o Change request can be exported/imported using CTS
    Export Project
      o Select / Deselect part / entire project & export to another R/3 system
    Import Project
      o Exported mapping / rules can be imported through PC file
      o Existing Project data gets overwritten
      o Prevent overwriting by using
    Import under different name
    Presetting for Inbound IDOC processing not transportable.
Regards

Function module to convert currency to USD

Hi All,
I need the function module to convert the currency to USD and the mandatory fields to be passed to the function module.
Thanks & Regards
Suresh

hi,
Working With LSMW:
Use TCODE LSMW
Objects of LSMW:
Project ID with max of 10 char to Name the data transfer project.
Subproject Used as further structuring attribute.
Object ID with max of 10 Characters, to name the Business object .
Project can have multiple sub projects and subprojects can have multiple objects.
Project documentation displays any documentation maintained for individual pop ups and processing steps
User Guide: Clicking on Enter leads to interactive user guide which displays the Project name, sub project name and object to be created.
Object type and import techniques:
Standard Batch / Direct input.
Batch Input Recording
o If no standard programs available
o To reduce number of target fields.
o Only for fixed screen sequence.
BAPI
IDOC
o Settings and preparations needed for each project
Preparations for IDOC inbound processing:
Choose settings -> IDOC inbound processing in LSMW
Set up File port for file transfer, create port using WE21.
Additionally set up RFC port for submitting data packages directly to function module IDoc_Inbound_Asynchronous, without creating a file during data conversion.
Setup partner type (SAP recommended US) using WE44.
Maintain partner number using WE20.
Activate IDOC inbound processing.
Verify workflow customizing.
Steps in creating LSMW Project:
1) Maintain attributes choose the import method.
2)Maintain source structure/s with or without hierarchical relations. (Header, Detail)
3) Maintain source fields for the source structures. Possible field types C,N,X, date, amount and packed filed with decimal places.
Fields can be maintained individually or in table form or copy from other sources using upload from a text file
4) Maintain relationship between source and target structures.
5) Maintain Field mapping and conversion rules
For each Target field the following information is displayed:
o Field description
o Assigned source fields (if any)
o Rule type (fixed value, translation etc.)
o Coding.
o Some fields are preset by the system & are marked with Default setting.
6) Maintain Fixed values, translations, user defined routines Here reusable rules can be processed like assigning fixed values, translation definition etc.
6) Specify Files
o Legacy data location on PC / application server
o File for read data ( extension .lsm.read)
o File for converted data (extension .lsm.conv)
7) Assign Files to defined source structures
8) Read data Can process all the data or part of data by specifying from / to transaction numbers.
9) Display read data To verify the input data being read
10) Convert Data Data conversion happens here, if data conversion program is not up to date, it gets regenerated automatically.
11) Display converted data To verify the converted data
Import Data Based on the object type selected
Standard Batch input or Recording
o Generate Batch input session
o Run Batch input session
Standard Direct input session
o Direct input program or direct input transaction is called
BAPI / IDOC Technique:
IDOC creation
o Information packages from the converted data are stored on R/3 Database.
o system assigns a number to every IDOC.
o The file of converted data is deleted.
IDOC processing
o IDOCS created are posted to the corresponding application program.
o Application program checks data and posts in the application database.
Finally Transport LSMW Projects:
R/3 Transport system
o Extras ->Create change request
o Change request can be exported/imported using CTS
Export Project
o Select / Deselect part / entire project & export to another R/3 system
Import Project
o Exported mapping / rules can be imported through PC file
o Existing Project data gets overwritten
o Prevent overwriting by using
Import under different name
for more information follow this link.
http://help.sap.com/saphelp_nw04s/helpdata/en/87/f3ae74e68111d1b3ff006094b944c8/content.htm

Urgent :Getting error "No ALE scenario active in Profit Center Accounting"

Hi Experts
I am working on a LSWM project ,which uses BAPI BAPI_PROFITCENTER_CREATE for upload of data,but I am facing a strange problem during the IDOC posting the error "No ALE scenario active in Profit Center Accounting" is shown and the status of IDOC goes to 51.
I have done all the ALE setting required for LSMW like File port ,partner type and partner number.
Please help me to solve this error.
Thanks
-Mitesh
Message was edited by:
 Mitesh Parekh

Hi,
Refer This SDN Blog, which gives you steps in detail....
LSMW Step by Step Guide: Legacy System Migration Workbench is an R/3 Based tool for data transfer from legacy to R/3 for one time or periodic transfer.
Basic technique is Import data from Spreadsheet / Sequential file, convert from source format to target format and import into R/3 database. LSMW not part of standard R/3, if we need this product email [email protected]
Advantages of LSMW:
 Most of the functions are within R/3, hence platform independence.
 Quality and data consistency due to standard import techniques.
 Data mapping and conversion rules are reusable across projects.
 A variety of technical possibilities of data conversion.
 Generation of the conversion program on the basis of defined rules
 Interface for data in spreadsheet format.
 Creation of data migration objects on the basis of recorded transactions.
 Charge-free for SAP customers and partners.
Working With LSMW:
Use TCODE LSMW
Objects of LSMW:
Project ID with max of 10 char to Name the data transfer project.
Subproject Used as further structuring attribute.
Object ID with max of 10 Characters, to name the Business object .
Project can have multiple sub projects and subprojects can have multiple objects.
Project documentation displays any documentation maintained for individual pop ups and processing steps
User Guide: Clicking on Enter leads to interactive user guide which displays the Project name, sub project name and object to be created.
Object type and import techniques:
Standard Batch / Direct input.
Batch Input Recording
 o If no standard programs available
 o To reduce number of target fields.
 o Only for fixed screen sequence.
 BAPI
 IDOC
 o Settings and preparations needed for each project
Preparations for IDOC inbound processing:
 Choose settings -> IDOC inbound processing in LSMW
 Set up File port for file transfer, create port using WE21.
 Additionally set up RFC port for submitting data packages directly to function module IDoc_Inbound_Asynchronous, without creating a file during data conversion.
 Setup partner type (SAP recommended US) using WE44.
 Maintain partner number using WE20.
 Activate IDOC inbound processing.
 Verify workflow customizing.
Steps in creating LSMW Project:
 Maintain attributes choose the import method.
 Maintain source structure/s with or without hierarchical relations. (Header, Detail)
 Maintain source fields for the source structures. Possible field types C,N,X, date, amount and packed filed with decimal places.
 Fields can be maintained individually or in table form or copy from other sources using upload from a text file
 Maintain relationship between source and target structures.
 Maintain Field mapping and conversion rules
 For each Target field the following information is displayed:
 o Field description
 o Assigned source fields (if any)
 o Rule type (fixed value, translation etc.)
 o Coding.
 o Some fields are preset by the system & are marked with Default setting.
 Maintain Fixed values, translations, user defined routines Here reusable rules can be processed like assigning fixed values, translation definition etc.
 Specify Files
 o Legacy data location on PC / application server
 o File for read data ( extension .lsm.read)
 o File for converted data (extension .lsm.conv)
 Assign Files to defined source structures
 Read data Can process all the data or part of data by specifying from / to transaction numbers.
 Display read data To verify the input data being read
 Convert Data Data conversion happens here, if data conversion program is not up to date, it gets regenerated automatically.
 Display converted data To verify the converted data
Import Data Based on the object type selected
 Standard Batch input or Recording
 o Generate Batch input session
 o Run Batch input session
 Standard Direct input session
 o Direct input program or direct input transaction is called
BAPI / IDOC Technique:
 IDOC creation
 o Information packages from the converted data are stored on R/3 Database.
 o system assigns a number to every IDOC.
 o The file of converted data is deleted.
 IDOC processing
 o IDOCS created are posted to the corresponding application program.
 o Application program checks data and posts in the application database.
Finally Transport LSMW Projects:
 R/3 Transport system
 o Extras ->Create change request
 o Change request can be exported/imported using CTS
 Export Project
 o Select / Deselect part / entire project & export to another R/3 system
 Import Project
 o Exported mapping / rules can be imported through PC file
 o Existing Project data gets overwritten
 o Prevent overwriting by using
 Import under different name
 Presetting for Inbound IDOC processing not transportable.
One Last thing, Check in BD64 is the Distribution model is Active for Profit Center.
Cheers...
Santosh.D
Mark All the Usefull Answers.

Transport LSMW

Similar Messages

Maybe you are looking for