Query on LSMW

Hai all,
I have to create pricing conditions by using LSMW .
Can you suggest which method is good to do this [ Direct input / Batch input recording / BAPI / IDOC] .
Thanks,
Nagaraju

Hi
see the sample code for BDC for VK11 (pricing conditions Upload)
report ZSDBDCP_PRICING no standard page heading
       line-size 255.
include zbdcrecx1.
*--Internal Table To hold condition records data from flat file.
Data: begin of it_pricing occurs 0,
       key(4),
       f1(4),
       f2(4),
       f3(2),
       f4(18),
       f5(16),
      end of it_pricing.
*--Internal Table To hold condition records header .
data : begin of it_header occurs 0,
         key(4),
         f1(4),
         f2(4),
         f3(2),
       end of it_header.
*--Internal Table To hold condition records details .
data : begin of it_details occurs 0,
        key(4),
        f4(18),
        f5(16),
       end of it_details.
data : v_sno(2),
       v_rows type i,
       v_fname(40).
start-of-selection.
refresh : it_pricing,it_header,it_details.
clear : it_pricing,it_header,it_details.
CALL FUNCTION 'UPLOAD'
      EXPORTING
           FILENAME                = 'C:\WINDOWS\Desktop\pricing.txt'
           FILETYPE                = 'DAT'
      TABLES
           DATA_TAB                = it_pricing
      EXCEPTIONS
           CONVERSION_ERROR        = 1
           INVALID_TABLE_WIDTH     = 2
           INVALID_TYPE            = 3
           NO_BATCH                = 4
           UNKNOWN_ERROR           = 5
           GUI_REFUSE_FILETRANSFER = 6
           OTHERS                  = 7.
WRITE : / 'Condition Records ', P_FNAME, ' on ', SY-DATUM.
OPEN DATASET P_FNAME FOR INPUT IN TEXT MODE.
if sy-subrc ne 0.
    write : / 'File could not be uploaded.. Check file name.'.
    stop.
endif.
CLEAR : it_pricing[], it_pricing.
DO.
    READ DATASET P_FNAME INTO V_STR.
    IF SY-SUBRC NE 0.
      EXIT.
    ENDIF.
write v_str.
translate v_str using '#/'.
    SPLIT V_STR AT ',' INTO it_pricing-key
                            it_pricing-F1 it_pricing-F2 it_pricing-F3
                            it_pricing-F4 it_pricing-F5 .
    APPEND it_pricing.
    CLEAR it_pricing.
ENDDO.
IF it_pricing[] IS INITIAL.
    WRITE : / 'No data found to upload'.
    STOP.
ENDIF.
loop at it_pricing.
    At new key.
      read table it_pricing index sy-tabix.
      move-corresponding it_pricing to it_header.
      append it_header.
      clear it_header.
    endat.
    move-corresponding it_pricing to it_details.
    append it_details.
    clear it_details.
endloop.
perform open_group.
v_rows = sy-srows - 8.
loop at it_header.
    perform bdc_dynpro      using 'SAPMV13A' '0100'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'RV13A-KSCHL'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '/00'.
    perform bdc_field       using 'RV13A-KSCHL'
                                  it_header-f1.
    perform bdc_dynpro      using 'SAPMV13A' '1004'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'KONP-KBETR(01)'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '/00'.
    perform bdc_field       using 'KOMG-VKORG'
                                  it_header-f2.
    perform bdc_field       using 'KOMG-VTWEG'
                                   it_header-f3.
**Table Control
    v_sno = 0.
    loop at it_details where key eq it_header-key.
      v_sno = v_sno + 1.
      clear v_fname.
      CONCATENATE 'KOMG-MATNR(' V_SNO ')' INTO V_FNAME.
      perform bdc_field       using v_fname
                                    it_details-f4.
      clear v_fname.
      CONCATENATE 'KONP-KBETR(' V_SNO ')' INTO V_FNAME.
      perform bdc_field       using v_fname
                                    it_details-f5.
      if v_sno eq v_rows.
        v_sno = 0.
        perform bdc_dynpro      using 'SAPMV13A' '1004'.
        perform bdc_field       using 'BDC_OKCODE'
                                 '=P+'.
        perform bdc_dynpro      using 'SAPMV13A' '1004'.
        perform bdc_field       using 'BDC_OKCODE'
                                 '/00'.
      endif.
    endloop.
*--Save
    perform bdc_dynpro      using 'SAPMV13A' '1004'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=SICH'.
    perform bdc_transaction using 'VK11'.
endloop.
perform close_group.
Regards
Anji

Similar Messages

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

Query on LSMW for Actions & Org. Assignment data

I have peculiar problem. I wrote an LSMW script to upload Actions (000) & Org. Assignment (0001) data to the database. The script is working correctly on one client, but the same script is not working on another client (not updating the database) and it is not giving any error message also. What could be the reason? Please help me.
-Kalpana

Hi,
Check whether Number range is Configured properly.
Also try to run LSMW in foreground ,so that you can find out the error.
Regards
MJ

Query in LSMW

In LSMW, how do to convert dd/mm/yyyy format in flat file to SAP date format..?

use the same format 23.03.1979 like that no need to convert
step : process one transaction manually and find how the system is accpeting the dat.
then accordingly give the input in flat file.
why date is required are you doing any transaction through LSMW???
SK

Query regarding LSMW.

How can we update the purchasing Org.(KOMG-EKORG), Condition group with Vendor(KMOG-EKKOL)and price(KONP-KBETR) form an excel sheet to the condition type table A892 using LSMW?The transaction used is MEK2.

HI,
just check it is sufficient.....
http://www.scmexpertonline.com/downloads/SCM_LSMW_StepsOnWeb.doc
and Iam giving the 13 steps document bellow
Using Tcode MM01 -- Maintain the source fields are
1) mara-amtnr char(18)
2) mara-mbrsh char(1)
3) mara-mtart char(4)
4) makt-maktx char(40)
5) mara-meins char(3)
the flate file format is like this as follows
MAT991,C,COUP,Srinivas material01,Kg
MAT992,C,COUP,Srinivas material02,Kg
AMT993,C,COUP,Srinivas material03,Kg
MAT994,C,COUP,Srinivas material04,Kg
MAT995,C,COUP,Srinivas material05,Kg
goto Tcode LSMW
give Project Name
Subproject Name
object Name
Press Enter -
Press Execute Button
It gives 13 radio-Button Options
do the following 13 steps as follows
1) select radio-Button 1 and execute
Maintain Object Attributes
select Standard Batch/Direct Input
give Object -- 0020
Method -- 0000
save & Come Back
2) select radio-Button 2 and execute
Maintain Source Structures
select the source structure and got to click on create button
give source structure name & Description
save & Come Back
3) select radio-Button 3 and execute
Maintain Source Fields
select the source structure and click on create button
give
first field
field name matnr
Field Label material Number
Field Length 18
Field Type C
Second field
field name mbrsh
Field Label Industrial Sector
Field Length 1
Field Type C
Third field
field name mtart
Field Label material type
Field Length 4
Field Type C
fourth field
field name maktx
Field Label material description
Field Length 40
Field Type C
fifth field
field name meins
Field Label base unit of measurement
Field Length 3
Field Type C
save & come back
4) select radio-Button 4 and execute
Maintain Structure Relations
go to blue lines
select first blue line and click on create relationship button
select Second blue line and click on create relationship button
select Third blue line and click on create relationship button
save & come back
5) select radio-Button 5 and execute
Maintain Field Mapping and Conversion Rules
Select the Tcode and click on Rule button there you will select constant
and press continue button
give Transaction Code : MM01 and press Enter
after that
1) select MATNR field click on Source filed(this is the field mapping) select MATNR and press Enter
2) select MBRSH field click on Source filed(this is the field mapping) select MBRSH and press Enter
3) select MTART field click on Source filed(this is the field mapping) select MTART and press Enter
4) select MAKTX field click on Source filed(this is the field mapping) select MAKTX and press Enter
5) select MEINS field click on Source filed(this is the field mapping) select MEINS and press Enter
finally
save & come back
6) select radio-Button 6 and execute
Maintain Fixed Values, Translations, User-Defined Routines
Create FIXED VALUE Name & Description as MM01
Create Translations Name & Description as MM01
Create User-Defined Routines Name & Description as MM01
after that delete all the above three just created in the 6th step
FIXED VALUE --MM01
Translations --MM01
User-Defined Routines --MM01
come back
7) select radio-Button 7 and execute
Specify Files
select On the PC (Frontend) -- and click on Create button(f5)
give the path of the file like "c:\material_data.txt"
description : -
separators as select comma radiao- button
and press enter save & come back
8) select radio-Button 8 and execute
Assign Files
Save & come back
9) select radio-Button 9 and execute
Read Files
Execute
come back
come back
10) select radio-Button 10 and execute
Display Imported Data
Execute and press enter
come back
Come back
11) select radio-Button 11 and execute
Convert Data
Execute
come back
Come back
12) select radio-Button 12 and execute
Display Converted Data
Execute & come back
13) select radio-Button 13 and execute
Start Direct Input Program
select the Program
select continue button
go with via physical file
give the lock mode as 'E'
and execute
KIshore...

Abap query regarding lsmw

hi ,friend ,i am taking matnr vaue from user and check the value of matnr coming from flat file ,if both are same then i want to skip the row ,but whern i use skip_record it is just replacing the vaue of matnr by'/'in allthe recoreds ,not escaping that par row.
i want some sugg .
thanks

hi Andreas,
the code let i am wr.
p_in ;value in flat flie.
w_matnr the value i have given.
if p_in = w_matnr.
skip_record.
endif.
matnr   mbrsh      mtart
/       s            03
/        p             04
it is doing in this way but i want if matnr is 20 in flat file and the value i have given match , it should take that row ,but it is taking olny by replacing the value of matnr by '/'

Issue during BOM LSMW changes...

Hello,
We have created BOM through LSMW but now we have an issue.
The base quantity was incorrectly uploaded as 100 EA instead of 1 EA.
Now we we try to change it though the LSMW it does not changes as it might have to go to 2 screens.
Is there a way where we can do a mass changes/LSMW to that field to change it 1 EA.
Let me know
Thanks
SAP Fans...

Hi,
If u know the BOMs that have been created with incorrect quantity then u can do a recording using CS02 to change the quantity and upload the file with BOM and changed quantity.
Else if u want to upload the same file that you have used to create the BOM for changing, then u need to have a select query in LSMW in Maintain field mapping and conversion rules step at the event __BEGIN_OF_PROCESSING__ and use the CS02 recording.
Hope it is clear.
Regards,
Asif Ali Khan

Lsmw for xk01

hello ,
I have a query in lsmw for xk01.
while doing lsmw for xk01, after executing step 1 the system ask for tcode , i gave xk01 there.
The next screen shown contains title field which belong to structure sza1_d0100 and field name is Title_medi whose length is 30.
But when i directly give tcode xk01 in command field. The screen opened contains title field which belongs to
table lfa1 and field name is ANRED whose length is 35.
Why this diffence is ? .

use below first LSMW method
Object               0040   Vendor master
Method               0001   Standard
Program Name         RFBIKR00
Program Type         B   Batch Input

LSMW Validation

Hi Friends,
I have a query in LSMW.
I am creating Materials using the recording of MM01.
I need to check a material already exists in SAP , before the session is called .
If material exists then that particular record from Excel should not be processed. I dont want to see the log for non processed items.It should be skipped at the LSMW level.
Please advice
Thanks and Regards,
Anoop

LSMW==> Maintain field mapping and conversion rules => For the session there is an event __BEGIN_OF_TRANSACTION__.
You could write your select * from mara where matnr = source-matnr. and validate the material exist or not.
If exists you can skip that loop using continue.
Hope this helps you.
Best wishes,
TM

Query on pricing Scales in LSMW

Hai,
I have a problem on scales, In LSMW through recording method i am creating pricing condition using XK15 transaction. But my problem is if material has 2 or 3 scales, at end of batch input session i am getting last scale value
Ex : Matnr      Amount
        P-100            500
Scales: 1        500
             10      300
             20      100.
After end of batch input session, it is showing only 20    100 scale for P-100 material.
Could any body help me.
Thanks,
Raju.

Hi,
I think you need to push 'Inset Line' - green plus button and enter the scales. This would create an additional blank line which would enable you to create the new dataset in a blank line in the tablecontrol.
But I prefer to load the data using LSMW in either of the following methods:
Object               0070   Condition record
Method               0000
Program name         RV14BTCI
Program type         B   Batch input
or
Message type         COND_A                      Conditions: Master data for price determination
Basic type           COND_A02                    ALE condition records
Hope this helps.
Best Regards, Murugesh AS

LSMW - BAPI method query

Hi All,
I am working on data migration activity for transactional data (CONTRACTS).
I am using the LSMW tool for data migration from legacy to SAPCRM system.
The scenario is as thus:
Migration of transactional data(contract data) from legacy system to SAPCRM system.
The structure of the data is as Header Data, Parent Item Level, Sub Item Level Data.
I tried migrating data using Batch Input Recording method, but this method was not capturing the item level data.
I require inputs and suggestions if anyone have successfully migrated TRANSACTIONAL DATA involving header, main item and sub item level data using the methods of LSMW.
Can anyone please give me the step by step approach to migrate transactional data using BAPI method?
Early response would be appreciated. U can also mail me at [email protected]
Thanks and Regards,
Praveen

if it's mandatory in Dialog mode, it's mandatory for the BAPI. no exceptions that I can think of.

LSMW Query

Hi
1) WHY LSMW does not support call transaction method?
2) How to create one customer or one vendor with multiple bank details in LSMW?Is there any coding?What is it?
Thank you

Tehre is no problem.
in second stage of lsmw declare.
heirarchical structure.
SVENDOR VENDORS HEADER
SBANKS Banks.
prepare two files with the same key. one for vendor master data one for vendor banks. it will automaticaly proces all record from second file with the same key as in firs file.
BR, JAcek

Query related to LSMW

I am using lsmw for recording transaction pa30 .In LSMW when I click on MAINTAN FIELD MAPPING & CONVERSION RULE (step 5)
the screen shows fields ,under that tabname and tcode .
nowhere i can find the actual field names which i had recorded using batch i/p recording using step1.
actual field name is required for mapping corresponding field with source fields.
how should i proceed ???

Hi,
Place the Cursor on the field and then press the MAP button then the Recorded structure will open then select the desired field to map and [place the cursor on that field and select ok, then the fields will be mapped with MOVE statment.
if the Source fields and the Recoring structure fields names are same then you can directly MAP in a Single shot, you will have a Icon there to MAP in single shot, press that one
Regards
Ashok Reddy

Query on BAPI -LSMW

Hi All,
I have a requirement on LSMW, Can any body send me step-by-step procedure
to create SD-pricing conditions by using BAPI in LSMW.
Thanks,
Naga

hi naga,
FOR BAPI/IDOC METHOD, WE NEED TO MAINTAIN IDOC INBOUND PROCESSING EXPLICITLY. IN THE INITIAL TRANSACTION OF LSMW, GO TO SETTINGS AND CLICK IDOC INBOUND PROCESSING. WE NEED TO PERFORM THE FOLLOWING STEPS.
     DEFINE OR SELECT A FILE PORT FOR TRANSPORTING THE FILE. OPTIONALLY, YOU CAN ALSO CREATE A TRFC PORT.
     THE PARTNER TYPE HAS TO BE DEFINED OR SELECTED.
     THE PARTNER NUMBER HAS TO BE DEFINED OR SELECTED.
     IDOC INBOUND PROCESSING MUST BE ACTIVATED AND THE WORKFLOW CUSTOMIZING MUST BE CHECKED. BOTH OF THESE TASKS ARE PERFORMED ONCE IN EACH SYSTEM.
EXPORTING AND IMPORTING
EXPORTING - IT IS A GOOD IDEA TO PERFORM THE MIGRATION FROM A LEGACY SYSTEM TO THE SAP SYSTEM IN A TEST SYSTEM FIRST. THIS FUNCTION IS USED TO TRANSFER THE FIELD ASSIGNMENTS DEVELOPED TO THE PRODUCTION SYSTEM.
IMPORTING - IMPORT THE MAPPING AND FIELD ASSIGNMENTS INTO A DIFFERENT SAP SYSTEM.
1) MAINTAINING OBJECT ATTRIBUTES
SPECIFY WHETHER THE DATA IS TO BE TRANSFERRED ONCE OR PERIODICALLY. AND THEN SPECIFY WHICH METHOD YOU GONNA USE FOR THE DATA TRANSFER.
2) MAINTAING SOURCE STRUCTURE
WE CAN CREATE SOURCE STRUCTURES EITHER AT THE SAME LEVEL OR AT THE LOWER LEVEL.
3) MAINTAINING SOURCE FIELDS
WE CAN DIRECTLY CREATE THE SOURCE FIELDS. OR WE CAN COPY THE FIELDS USING THE FOLLOWING METHODS.
     UPLOAD TAB DELIMITED TEXT
     COPY FROM OTHER OBJECT
     COPY FROM DATA REPOSITORY FROM A STRUCTURE OF ABAP DICTIONARY.
     FROM DATA FILE.
4) MAINTAING STRUCTURE RELATIONS
HERE WE ARE ESTABLISHING THE STRUCTURE RELATIONSHIPS BETWEEN THE PROJECT AND THE SAP SYSTEM.
5) MAINTAIN FIELD MAPPING AND CONVERSION RULES
HERE WE ARE MAINTAINING THE FILED RELATIONSHIP BETWEEN THE SOURCE AND TARGET STRUCTURE.
AUTO FIELD MAPPING
AUTO FIELD MAPPING IS USEFUL IN CASE IF FIELDS WITH IDENTICAL OR SIMILAR NAMES/DESCRIPTIONS EXIST IN THE SOURCE AND TARGET STRUCTURES. THIS IS PARTICULARLY THE CASE IF DATA IS TRANSFERRED FROM ONE SAP SYSTEM TO ANOTHER SAP SYSTEM.
CONVERSION RULES
THE DEFAULE CONVERSION RULE IS TRANSFER (MOVE).
INITIAL, CONSTANT, TRANSFER (MOVE), PREFIX, SUFFIX, CONCATENATION, TRANSFER LEFT- ALIGNED, ABAP CODE, X FIELD, MOVE WITH LEADING ZEROS, [(R) FIXED VALUE, TRANSLATION AND USER-DEFINED ROUTINE].
THERE IS A CHECKBOX ONLY IF SOURCE FIELD NOT INITIAL.
GLOBAL VARIABLES
WE CAN USE THESE GLOBAL VARIABLES IN ABAP CODE.
G_PROJECT     CURRENT PROJECT
G_SUBPROJ     CURRENT SUBPROJECT
G_OBJECT     CURRENT OBJECT
G_RECORD     CURRENT TARGET STRUCTURE
PROCESSING TIMES
__BEGIN_OF_PROCESSING__     BEFORE PROCESSING OF DATA IS STARTED.
__BEGIN_OF_RECORD__     BEFORE THE CONVERSION RULE FOR A SOURCE STRUCTURE IS APPLIED.
__END_OF_RECORD     AFTER THE CONVERSION RULE FOR A SOURCE STRUCTURE HAS BEEN APPLIED.
__END_OF_TRANSACTION__     AFTER PROCESSING OF THE TRANSACTION HAS BEEN COMPLETED.
__END_OF_PROCESSING__     AFTER PROCESSING OF DATA HAS BEEN COMPLETED.
__BEGIN_OF_TRANSACTION__     BEFORE PROCESSING OF DATA FOR A TRANSACTION IS STARTED
GLOBAL FUNCTIONS
TRANSFER_RECORD.     THE CURRENT RECORD (THAT IS, THE RECORD FOR THE CURRENT TARGET STRUCTURE) IS TRANSFERRED TO THE OUTPUT BUFFER.
TRANSFER_THIS_RECORD '...'.     A RECORD OF A DIFFERENT TARGET STRUCTURE IS TRANSFERRED TO THE OUTPUT BUFFER. THE NAME OF THE TARGET STRUCTURE HAS TO BE SPECIFIED AS ARGUMENT BETWEEN QUOTATION MARKS.
AT_FIRST_TRANSFER_RECORD.     THE CURRENT RECORD IS TRANSFERRED TO THE OUTPUT BUFFER IF IT IS THE FIRST TRANSACTION INVOLVED.
ON_CHANGE_TRANSFER_RECORD.     THE CURRENT RECORD IS TRANSFERRED TO THE OUTPUT BUFFER IF IT HAS CHANGED AS COMPARED TO THE LAST RECORD.
TRANSFER_TRANSACTION.     THE CURRENT TRANSACTION IS WRITTEN TO THE OUTPUT FILE. THIS TRANSFERS ALL THE RECORDS OF THE OUTPUT BUFFER TO THE OUTPUT FILE.
SKIP_RECORD.     THE CURRENT RECORD IS NOT TRANSFERRED TO THE OUTPUT BUFFER.
SKIP_TRANSACTION.     THE CURRENT TRANSACTION IS NOT WRITTEN TO THE OUTPUT FILE.
6) MAINTAIN FIXED VALUES, TRANSALTIONS, USER-DEFINED ROUTINES
REUSABLE RULES ALLOW YOU TO DEFINE CONVERSION RULES THAT CAN BE USED SEVERAL TIMES.
7) SPECIFY FILES
WE CAN SPECIFY FILES IN PC OR IN APPLICATION SERVER. IN CASE YOUR DATA IS STORED IN MULTIPLE SETS OF FILES, YOU CAN SPECIFY A WILDCARD (*) FOR THE NAME OF YOUR FILE. A WILDCARD CAN BE USED EVERY TIME THE FILES FOR SEVERAL IMPORT RUNS COME FROM DIFFERENT FILES; WITH THE FILE NAME BEING DIFFERENT IS SOME CHARACTERS ONLY.
FOR READ DATA, THE FILE NAME IS IN THE FORMAT OF PROJECT_SBPROJ_OBJ.LSMW.READ
FOR CONVERTED DATA, THE FILE NAME IS IN THE FORMAT OF PROJECT_SBPROJ_OBJ.LSMW.CONV
8) ASSIGN FILES
ASSIGNS THE FILES ALREADY DEFINED TO THE SOURCE STRUCTURES.
CONVERSION PROGRAM - /1CADMC/SAP_LSMW_CONV_OBJN.
9) READ DATA
THE FILES MUST HAVE BEEN SPECIFIED BEFORE AND MADE KNOWN TO THE LSMW. IN THIS STEP, THE DATA IS READ INTO THE APPLICATION SERVER.
WE CAN READ THE SELECTED DATA BY GIVING TRANSACTION NUMBER.
10) CONVERT DATA
THE FILE OF READ DATA IS TRANSFERRED TO THE FILE OF CONVERTED DATA DURING MIGRATION.
WHEN THE LSMW OBJECT IS BASED ON A BAPI OR AN IDOC, ADDITIONAL SELECTION PARAMETERS ARE AVAILABLE ON THE SELECTION SCREEN OF THE DATA CONVERSION PROGRAM:
CREATE IDOCS DIRECTLY:     IDOCS ARE COLLECTED AND THEN PASSED FOR IDOC GENERATION PACKAGE BY PACKAGE.
NO. OF IDOCS PER PACKAGE:     THE DEFAULT IS 50 (THIS VALUE CAN BE CHANGED).
THE ABOVE MENTIONED STEPS ARE COMMON FOR ALL THE TYPES OF IMPORTING METHODS IN LSMW.
IN THE CASE OF STANDARD BATCH INPUT/ BATCH INPUT RECORDING, CREATING BATCH INPUT SESSION AND PROCESSING THAT.
IN THE CASE OF STANDARD DIRECT INPUT, START A DIRECT INPUT SESSION.
IN THE CASE OF BAPI/ IDOC,
     STARTING IDOC GENERATION
     STARTING IDOC PROCESSING
     CREATING AN IDOC OVERVIEW
     STARTING IDOC POSTPROCESSING
FOR DIRECT INPUT METHOD, WE CAN USE EITHER THE PROGRAM RMDATIND OR THE TRANSACTION BMV0.
STARTING IDOC GENERATION FIRST, THE FILE WITH THE CONVERTED DATA IS READ. THE PACKETS OF INFORMATION IN THIS FILE ARE THEN SAVED TO THE SAP DATABASE IN IDOC FORMAT, BUT NOT TO THE DATABASE OF THE CORRESPONDING APPLICATION. THE SYSTEM ASSIGNS A NUMBER TO EACH IDOC. THE FILE WITH THE CONVERTED DATA IS THEN DELETED.
STARTING IDOC PROCESSING THE IDOCS CREATED IN THE FIRST STEP ARE SENT TO THE ASSOCIATED APPLICATION PROGRAM. THIS APPLICATION PROGRAM CHECKS THE DATA AND UPDATES IT IN THE APPLICATION DATABASE, IF NECESSARY.
Pls reward if helpful.

LSMW...new query

First profound thanks to Dittakavi Srinivas, Rajesh Banka, Chandru and others who guided me for LSMW.
I have the following new queries:
1. I have uploaded the customer master from the legacy using the 'Recording 'method. The first customer has got repeated twice. How do I delete this customer record? OR VD06 is the only solution?
2. 2 fields were left out while uploading. One of them Credit Control area is a standard constant value. and Other one Terms of payment in the sales area data
Now if I use the Direct Input Object method then at the Step 6 I should be able to give the constant fixed value for CCA? how do I do it? any screen shot?
3. For the Terms of payment I will have to make separate tabdelim file which would have the customer name and terms of payment against this name?
OR only ZTERM column is enough.
4. I tried to do it but it gave funny values for the record so I abandoned the process and now shall again resume from step 7 after I receive advice from you guys.
5. For Individual customer Limit do I use FD32 and upload it as direct input object and with constant value at step 6?? How is it?
Await your urgent guidance.
Adi

1. I have uploaded the customer master from the legacy using the 'Recording 'method. The first customer has got repeated twice. How do I delete this customer record? OR VD06 is the only solution?
I suppose you are usung internal number range for Customer Master. In that case, the same customer must have been created with different Customer Number. You can block one of the customer Code through T.Code VD05.
Similarly, if you are using external number range, even in that case the customer must have been created with different Customer Code. Soyou can block one of the Customer Code through VD05.
2. 2 fields were left out while uploading. One of them Credit Control area is a standard constant value. and Other one Terms of payment in the sales area data
Now if I use the Direct Input Object method then at the Step 6 I should be able to give the constant fixed value for CCA? how do I do it? any screen shot?
3. For the Terms of payment I will have to make separate tabdelim file which would have the customer name and terms of payment against this name?
OR only ZTERM column is enough.
Create a new LSMW for Customer Master in Change mode with only 2 left out fields & also include Customer Code, Company Code & Sales Area. Upload the new LSMW with relevant information.
5. For Individual customer Limit do I use FD32 and upload it as direct input object and with constant value at step 6?? How is it?
Maintain it directly through FD32. If the volume is high, ctreate LSMW.
Regards,
Rajesh Banka
Reward points if helpful.

Query on LSMW

Similar Messages

Maybe you are looking for