Equipment BOM using LSMW- standard batch/Direct input method - reg

hi,
I tried to upload equipment BOM using standar batch / direct input method.
I have maintained sorcue structures for BOM header and Item, maintained source fields.
Both source fields have common field as equipment number.
It is working fine upto step display read data.
At step, convert data- i am getting ABAP dump.
"Data objects in Unicode programs cannot be converted" is displayed in dump
If any one tried before or experiance similar condtion before, please help
thanks & rgards,
Kiran kumar.Kasturi

Hi,
thanks for your inputs.
In the Specify files Step ,when specifying the file from system , in separators,selected Tabulator .
and I have done already all the above while uploading my header and item file ( type tab delimited) and
still iam getting error at convert file step.
please help
thanks & regards,
Kiran Kumar.K

Similar Messages

Edit Equipment TL using LSMW Standard Batch/Direct Method

Hello all
I have created a set of Equipment TL for around 600+ Equipments uwing LSMW method of Standard Batch/ Direct Input method (0470). While creating I found that it creates only the header of the TL and not the individual operations and Components at item level. Now that the TL have been generated I am trying to chnage the TL and insert the Operations/Components gainst respective Group and counter no, but the Change mode(0002) for Direct Input method (0470) is not available.
How can I achieve this..Tried searching some of the posts in this forum but they dont seem to be an answer for my requirement.
I do not want to go thru LSMW recording method.
Please assit with any FM or BAPI to achieve the above requirements.
Thanks
Murad

If you want to load the task list, it obvious to have three files : Header, Operations and components. - You have to maintain three strcutures for each file and you need to map three of them with some common key incase if you have multiple operations.
Goodluck
Mahee

LSMW - Standard Batch/Direct Input Method.

Hi all,
I was trying to create the LSMW for MM01 using standard Batch/Direct Input Method. While I selected object as "0020- Material Master" I am not able to get the Method for Batch Input. Is there any we can create method for batch input or we have to use only direct input?

You have to use direct input method RMDATIND object 0020 to create materials. You may find batch input very complicated to create materials.

LSMW: standard batch direct input for create document & document str

hello expert .
Is there any standard batch direct input for create document (tcode: cv01n ) & document structure (cv11) using lsmw.
regards
srinivas

Hi Srnivas,
I am not able to find direct input progarm for this, but there is one standard bapi available for this with name BAPI_DOCUMENT_CREATE you can use this.
Regards
Dhirendra

LSMW for equipment creation-Standard Batch/Direct Input

Hi,
We developed an LSMW with standard batch / direct input method for creating equipment masters.
We used Object =0400 ( equipment ) and method = 0001 ( batch input)
We maintained source structures and source fileds. In the source field , we maintained only those fields that we need from table IBIPEQUI but in the order given in this structure.
Also we maintained filed mapping and field convertion rules for the above source fields.
When we run LSMW step - Display converted data , we see that
Transactions Read:                   1
Records Read:                          1
Transactions Written:                0
Records Written:                       0
Not sure what could have gone wrong?
Please provide some clues to the following questions.
1) Should the source structure be same as fields from stuc. IBIPEQUI and should it include all the fields in the source structure?
2) Is field mapping required or not ?
3) We are getting an error - transaction is not supported in direct input mode.
Thanks in advance
Rgds,
Rajesh

1. Source fields are( same as IBIPEQUI structure ; the tab delimited file matches with these fields)
TCODE                          C(020)    Transaction Code
RECORDNAME                     C(008)    Record name
EQUNR                          C(018)    Equipment
DATSL                          C(008)    Valid On
EQTYP                          C(001)    Equipment category
EQKTX                          C(040)    EQKTX
BEGRU                          C(004)    Authorization Group
EQART                          C(010)    Technical obj. type
GROES                          C(018)    Size/dimensions
INVNR                          C(025)    Inventory number
BRGEW                          C(017)    Gross Weight
GEWEI                          C(003)    Weight unit
ELIEF                          C(010)    Vendor
ANSDT                          C(008)
ANSWT                          C(017)    Acquisition Value
WAERS                          C(005)    Currency
HERST                          C(030)    Manufacturer
HERLD                          C(003)    Country of manufact.
BAUJJ                          C(004)    Construction year
BAUMM                          C(002)    Construction month
TYPBZ                          C(020)    Model number
SERGE                          C(030)    ManufSerialNumber
MAPAR                          C(030)    ManufactPartNo.
GERNR                          C(018)    Serial number
GWLEN                          C(008)    Warranty end date
KUND1                          C(010)    Customer
KUND2                          C(010)    End customer
KUND3                          C(010)    Operator
SWERK                          C(004)    Maintenance plant
STORT                          C(010)    Location
MSGRP                          C(008)    MSGRP
BEBER                          C(003)    Plant section
ARBPL                          C(008)    Work center
ABCKZ                          C(001)    ABC indicator
EQFNR                          C(030)    Sort field
BUKRS                          C(004)    Company Code
ANLNR                          C(012)    Asset Number
ANLUN                          C(004)    ANLUN
GSBER                          C(004)    Business Area
KOSTL                          C(010)    Cost Center
PROID                          C(024)    PROID
DAUFN                          C(012)    Standing order
AUFNR                          C(012)    Order
TIDNR                          C(025)    Technical IdentNo.
SUBMT                          C(018)    Construction type
HEQUI                          C(018)    Superord. Equipment
HEQNR                          C(004)    Position
EINZL                          C(001)    Single installation
IWERK                          C(004)    Planning plant
INGRP                          C(003)    Planner group
GEWRK                          C(008)    Main work center
WERGW                          C(004)    Plant for WorkCenter
RBNR                           C(009)    Catalog profile
TPLNR                          C(030)    Functional Location
DISMANTLE                      C(001)    DismIndic.
VKORG                          C(004)    Sales Organization
VTWEG                          C(002)    Distribution Channel
SPART                          C(002)    Division
MATNR                          C(018)    Material
SERNR                          C(018)    BOM explosion number
WERK                           C(004)    WERK
LAGER                          C(004)    LAGER
CHARGE                         C(010)    CHARGE
KUNDE                          C(010)
KZKBL                          C(001)    Load records
PLANV                          C(003)    PLANV
FGRU1                          C(004)    FGRU1
FGRU2                          C(004)    FGRU2
STEUF                          C(004)    Control key
STEUF_REF                      C(001)    STEUF_REF
KTSCH                          C(007)    Standard text key
KTSCH_REF                      C(001)    Std text referenced
EWFORM                         C(006)    EWFORM
EWFORM_REF                     C(001)    EWFORM_REF
BZOFFB                         C(002)    Ref. date for start
BZOFFB_REF                     C(001)    BZOFFB_REF
OFFSTB                         C(007)    Offset to start
EHOFFB                         C(003)    Unit
OFFSTB_REF                     C(001)    OFFSTB_REF
BZOFFE                         C(002)    Ref. date for finish
BZOFFE_REF                     C(001)    BZOFFE_REF
OFFSTE                         C(007)    Offset to finish
EHOFFE                         C(003)    Unit
OFFSTE_REF                     C(001)    OFFSTE_REF
WARPL                          C(012)    Maintenance Plan
IMRC_POINT                     C(012)    Measuring point
INDAT                          C(008)    Inverse date
INTIM                          C(006)    Processing time OC Workbe
INBDT                          C(008)    Start-up date
GWLDT                          C(008)    Guarantee
AULDT                          C(008)    Delivery date
LIZNR                          C(020)    License number
MGANR                          C(020)    Master warranty
REFMA                          C(018)    REFMA
VKBUR                          C(004)    Sales Office
VKGRP                          C(003)    Sales Group
WARR_INBD                      C(001)    Inbound warranty
WAGET                          C(001)    Warranty inheritance poss
GAERB                          C(001)    Indicator: Pass on warran
ACT_CHANGE_AA                  C(001)    ACT_CHANGE_AA
STRNO                          C(040)    STRNO
DATLWB                         C(008)    Date Last Goods Movmnt
UII                            C(072)    UII
IUID_TYPE                      C(010)    IUID Type
UII_PLANT                      C(004)    Plant Responsible for UII
2, source structure is assigned to target structure IBIPEQUI
3. In the assign files step - all settings given above are correctly maintained.
4. Field mapping
TCODE                        Transaction Code
                    Rule :   Default Settings
                    Code:    IBIPEQUI-TCODE = 'IE01'.
RECORDNAME                   IBIP: Name of the Data Transfer Record
                    Rule :   Default Settings
                    Code:    IBIPEQUI-RECORDNAME = 'IBIPEQUI'.
EQUNR                        Equipment Number
                    Source: ZIE01_002_SOURCE-EQUNR (Equipment)
                    Rule :   Transfer (MOVE)
                    Code:    if not ZIE01_002_SOURCE-EQUNR is initial.
                               IBIPEQUI-EQUNR = ZIE01_002_SOURCE-EQUNR.
                             endif.
DATSL                        Date valid from
                    Source: ZIE01_002_SOURCE-DATSL (Valid On)
                    Rule :   Transfer (MOVE)
                    Code:    if not ZIE01_002_SOURCE-DATSL is initial.
                               IBIPEQUI-DATSL = ZIE01_002_SOURCE-DATSL.
                             endif.
EQTYP                        Equipment category
                    Source: ZIE01_002_SOURCE-EQTYP (Equipment category)
                    Rule :   Transfer (MOVE)
                    Code:    if not ZIE01_002_SOURCE-EQTYP is initial.
                               IBIPEQUI-EQTYP = ZIE01_002_SOURCE-EQTYP.
                             endif
When I read data with 1 record uploaded ( in the assign fields step , I did not choose "fields names at start of file" and also saved the file with tab delimited text format without field names), it shows as
Transactions Read:                    2
Records Read:                         2
Transactions Written:                 2
Records Written:                      2
I uploaded only one record but it reads as 2 records and can not figure out why 2 records?
Also when I checked display converted data , it shows 2 records .
First record shows
TCODE         Transaction Code                                             IE01
RECORDNAME    IBIP: Name of the Data Transfer Record                       IBIPEQUI
EQUNR         Equipment Number
DATSL         Date valid from                                              05072010
EQTYP         Equipment category                                           H
EQKTX         Description of technical object                              PNEUMATIC PIPE BENDER
BEGRU         Technical object authorization group
EQART         Type of Technical Object                                     MECH-PRESS
GROES         Size/dimension                                               1000X500X1500MM
INVNR         Inventory number
BRGEW         Gross Weight     : IBIP Character Structure                  50
GEWEI         Weight Unit                                                  KG
ELIEF         Vendor number
ANSDT         Acquisition date
ANSWT         Acquisition Value: IBIP Character Structure
All the fields following this , are blank.
2nd record shows
TCODE         Transaction Code                                             IE01
RECORDNAME    IBIP: Name of the Data Transfer Record                       IBIPEQUI
EQUNR         Equipment Number                                             2009
DATSL         Date valid from
EQTYP         Equipment category                                           S
EQKTX         Description of technical object                              1006324
BEGRU         Technical object authorization group
EQART         Type of Technical Object
GROES         Size/dimension                                               20100406
uploaded values are jumbled in 1st and 2nd record.
Hope to receive your valuable ideas for finding out the reason and corrective action required.
Rgds,
Rajesh
I
Edited by: Rajesh63 on Jul 6, 2010 10:37 PM

Customer Master using LSMW standard batch

Hi All,
I am uploading the customer master data using LSMW standard batch input method. When i process the session created using this i am getting an error that input data that "No batch input data for screen SAPMF02D 0310". This is happening when it reachs the sales area screen. All the remaining screens are processed correctly.
Please help me in this regards,
Thanks & Regards,
Sudheera

Hi,
Refer
https://forums.sdn.sap.com/click.jspa?searchID=9408057&messageID=4828875
Regards
Kiran Sure

Error in the LSMW for vendor master using standard batch/direct input

I am facing the problem in the LSMW for the Vendor master data. The vendor is initially created for the company code 350 by using LSMW. NOw when I try to uploasd the same vendor using the same LSMW for the company code 450 then I get the error in the Bach input creation as follows:
Batch Input Interface for Vendors
FB012                    Session 1 : Special character for 'empty field' is /
FB007                    Session 1 session name VNDR_CREATE_ was opened
FB104                    Trans. 2 XK01 : Acct already exists; general area not being processed
FB125                    ... Data in table BLFA1 cannot be processed
FB016                    ... Last header record ...
FB014                    ... BLF00-STYPE 1
FB014                    ... BLF00-TCODE XK01
FB014                    ... BLF00-LIFNR 300951
FB014                    ... BLF00-BUKRS 402
FB014                    ... BLF00-EKORG /
FB014                    ... BLF00-KTOKK VEND
FB017                    ... Last data record ...
FB014                    ... BLFA1-STYPE 2
FB014                    ... BLFA1-TBNAM BLFA1
FB014                    ... BLFA1-ANRED /
FB014                    ... BLFA1-NAME1 SAVOIE AUTOMATISME DEXIS
This is because when we use XK01 to create the vendor by using the

Please check this answered link:
Re: LSMW for Vendor Master
LSMW Upload vendor master data
Edited by: Afshad Irani on May 5, 2010 12:42 PM

Problem while writing the data (LSMW direct input method for Creating BOM )

Hi all ,
I am unable to create a BOM using LSMW standard dirrect input mehtod .
While i going through the *Read data * step , it is reading the data but unable to write the data .
My input text files are correct , Is it a problem with respect to the Logical Path or Logical File ......
Please let me know the Possibilities of arising this problem .
Regards,
Raj

Hi,
Check this document:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90d90895-68dd-2a10-f096-bf8cf2e2f65b
cheers
Aveek

Reg LSMW-Batch/Direct Input

Hi All,
I have small issue , I am using LSMW-Batch/Direct Input method i this method am using some fields and as per those fields i maintain flat file data.
in 7th step i specify file name , while saving that one am getting this Error message i.e.
File Name 'Converted Data': Max. 45 Characters. Remaining data saved. so please could you help me abt that .
Thanks & Regards,
SHAIK.

Hi Shaik,
In specify files step -> Files -> converted data the filename will be automatically proposed by system.
<Project name><Subproject name><Object name>.lsmw.conv
this file name should not exceed 45 characters. so please cut short the names of Project name / Subproject name/Object name or
double click on proposed file name and change it.
Regards,
Savitha

Call transaction in Direct input method

Hi All
how do i use call transaction in direct input method.
thanks all

Hi,
Direct input is different and Call transaction is different.
In Direct input method,the data will be uploaded directly into the table.
In call transaction you can change the data before uploading into dictionary table by using tcode
Ex for Direct input method
TABLES: kna1.
DATA: BEGIN OF itab1 OCCURS 0,
      str(255),
      END OF itab1.
DATA: itab2 TYPE kna1 OCCURS 0 WITH HEADER LINE.
CALL FUNCTION 'WS_UPLOAD'
EXPORTING
    filename                = 'D:\ABAP EVE\ffile1.txt'
    filetype                = 'ASC'
TABLES
    data_tab                = itab1
EXCEPTIONS
    conversion_error        = 1
    file_open_error         = 2
    file_read_error         = 3
    invalid_type            = 4
    no_batch                = 5
    unknown_error           = 6
    invalid_table_width     = 7
    gui_refuse_filetransfer = 8
    customer_error          = 9
    no_authority            = 10
    OTHERS                  = 11.
IF sy-subrc <> 0.
WRITE:/ 'sorry'.
ELSE.
LOOP AT itab1.
    SPLIT itab1-str AT ',' INTO itab2-kunnr itab2-name1.
    APPEND itab2.
ENDLOOP.
IF sy-subrc = 0.
    LOOP AT itab2.
      WRITE:/ itab2-kunnr,itab2-name1.
      INSERT INTO kna1 VALUES itab2.
    ENDLOOP.
    IF sy-subrc = 0.
      WRITE:/ 'inserted'.
    ELSE.
      WRITE:/ 'not inserted'.
    ENDIF.
ELSE.
    WRITE:/ 'fail'.
ENDIF.
ENDIF.
Flat file:
10001,Sadney
10003,Yogesh
20005,Madan
Ex for Call transaction
DATA: BEGIN OF itab OCCURS 0,
      str(255),
      END OF itab.
DATA: BEGIN OF itab1 OCCURS 0,
      lifnr LIKE lfa1-lifnr,
      name1 LIKE lfa1-name1,
      ort01 LIKE lfa1-ort01,
      END OF itab1.
DATA: jtab LIKE bdcdata OCCURS 0 WITH HEADER LINE.
DATA: ktab TYPE TABLE OF bdcmsgcoll,
      wa TYPE bdcmsgcoll.
CALL FUNCTION 'WS_UPLOAD'
EXPORTING
    filename                = 'D:\ABAP EVE\ffile4.txt'
    filetype                = 'ASC'
TABLES
    data_tab                = itab
EXCEPTIONS
    conversion_error        = 1
    file_open_error         = 2
    file_read_error         = 3
    invalid_type            = 4
    no_batch                = 5
    unknown_error           = 6
    invalid_table_width     = 7
    gui_refuse_filetransfer = 8
    customer_error          = 9
    no_authority            = 10
    OTHERS                  = 11.
IF sy-subrc <> 0.
WRITE:/ 'no file exist'.
ENDIF.
LOOP AT itab.
SPLIT itab-str AT ',' INTO itab1-lifnr itab1-name1 itab1-ort01.
APPEND itab1.
ENDLOOP.
LOOP AT itab1.
PERFORM prginfo USING 'SAPMZBDCCT' '123'.
PERFORM fldinfo USING 'i01' itab1-lifnr.
PERFORM fldinfo USING 'i02' itab1-name1.
PERFORM fldinfo USING 'i03' itab1-ort01.
CALL TRANSACTION 'ZCSBDCCT' USING jtab
                                    MODE 'N'
                                    MESSAGES INTO ktab.
ENDLOOP.
--- Display the Status messages ---
LOOP AT ktab INTO wa WHERE msgtyp = 'E'.
WRITE:/ wa.
ENDLOOP.
*&      Form prginfo
      text
     -->PRGNAME    text
     -->SCRNUMBER text
FORM prginfo USING prgname scrnumber.
CLEAR jtab.
REFRESH jtab.
jtab-program = prgname.
jtab-dynpro = scrnumber.
jtab-dynbegin = 'X'.
APPEND jtab.
ENDFORM.                    "prginfo
*&      Form fldinfo
      text
     -->FLDNM      text
     -->FLDVAL     text
FORM fldinfo USING fldnm fldval.
CLEAR jtab.
jtab-fnam = fldnm.
jtab-fval = fldval.
APPEND jtab.
ENDFORM.                    "fldinfo
MPP CODE.
TOP-INCLUDE.
DATA: OK_CODE TYPE SY-UCOMM.
DATA: I01(10),I02(20),I03(26).
DATA: WA TYPE LFA1.
PAI
CASE OK_CODE.
   WHEN 'INSERT'.
     MOVE I01 TO WA-LIFNR.
     MOVE I02 TO WA-NAME1.
     MOVE I03 TO WA-ORT01.
     INSERT INTO LFA1 VALUES WA.
     IF SY-SUBRC = 0.
       MESSAGE I001(ZCSMSG).
     ELSE.
       MESSAGE I002(ZCSMSG).
     ENDIF.
   WHEN 'EXIT'.
     LEAVE PROGRAM.
ENDCASE.
Reward,if useful.
Thanks,
Chandu

Problem while Creating BOM using LSMW Direct Input

Hi all ,
I am trying to create the BOM Using LSMW Direct Input Method .
I am getting problem at step 9 that is Read Data.
It is able to read the values from header and item files .
but it is not able to write , so the Written is 0 always .
I put the field names first in the flat file and correcponding values below it with tab delimited.
Please let me know where the Problem would be.... I am trying this from long time ..
Regards ,
Raj

hi ,
Yes i am specify files i am attaching 2 files .
ones is header and the other is line item data .
my strucure is :
Hi ,
I am still getting problem while for writing the records after reading the data .....
my header structure :
STYPE
MATNR
WERKS
SELAL
STLAN
DATUV
ZTEXT
my item structure :
STYPE
MATNR
WERKS
SELAL
POSTP
MENGE
my header data :
STYPE     MATNR     WERKS     SELAL     STLAN     DATUV     ZTEXT
1     388     0110     20     1     06.01.2009     SAMPLE ZTEXT
my item data :
STYPE     MATNR1     WERKS     SELAL     POSTP     MENGE
1     388     0110     20     N     1234
1     382     0110     20     N     12345
Above text files are delimited by tabulator.
Please guide me . The files are reading but unable to write .....
Regards,
Raj

LSMW direct input method - Equipment BOM

Hi Experts,
We have already written program for equipment BOM master in LSMW direct input method. I do not know about this direct input method.
Here they have maintained 2 source structures and relavant source fields. one for BOM header and other for BOM items. The first field they maintained is LINK in both the source fields. I really do not know what that field is all about. I checked in step specify files and found that they have previously mentioned two files, one for BOM header and other for BOM items. but when I tried to save in this step it gives me error that " No logical path specified". Can anybody tell me what is this error is all about.Please heip me to get out of this problem.
Thanks and best regards,
Praveen

Hi praveen,
LSMW does not accept two files.
In the step create source strcture
crte one structure with BOM header like with ZBOM_H.
Under that create another structure for item ZBOM_I.
ZBOM_H
ZBOM_I like this structure will will be.
In the step source fields.
crate onne variable with indicatoe header.While creating the variable we have field 'identify field content ' field in pop up screen 'H'.
assign all header files under identifier 'H'.
then under ZBOM_I create identifier with 'I'.
Assign all the item fields to this.
then map the fields.
In the file should be H header fields.
                              I item fields.
                              I
                              I.
Then Header .It should be like this.
in saptechnical u will get the examples go though them once.
Thanks

Difference between batch input method and direct input method in LSMW.

Hi all,
what is difference between batch input method and direct input method in LSMW. are they same?if differences are there tell me with details?

Hi,
Here are few differences bw Batch Input and Direct Inputs methods.
Batch Input: Uses classical BDC approach, but doesn't required an ABAP program to be written to format the BDC DATA. The user has to format the data using predefined structures and store it in a flat file. Yet it is a slower updation method.
Direct Input: Works similar to Batch Input programs. The difference is, instead of processing screens they validate fields and directly load the data into tables using standard function modules. Much faster and suits for large volume of data.
Thanks.
DhanaLakshmi M S

LSMW Standard Batch Input Program

Hi,
I have one requirement on creating BOM.
I have to upload data from legacy system to SAP for T-Code ' CS01'
I have to use the Standard Batch input Program 'RCSBI010'.
I have source structure and Target Structure.
In Source structure i have Header and item data.
In Header i have 11 fields and in Item i have 23 fields.
In Target Structure i have upto 130 fields.
In the Standard program who have 4 structures and each structure have fields.
So How many fields i have to map with Standard structure. and in my source structure i dont have the fields like T-code, session name, user name,and xkeep.
So how to pass these fields (T-code, session name, user name,and xkeep) to the standard structure. and is it necessary to pass these fields to the standard batch input program.
Advance thanks,
Kumar A

Hi,
Hi,
Record type 0: one session record (structure BGR00) per session..
The session header contains general administrative data on the batch input session to be created. All records that follow the header in the sequential file are assigned to the current session, until the next header occurs in the file.
Record type 1: one session record (structure BICSK) for each BOM
The BOM header record contains the transaction code (for example, CS01 Create material BOM) and the header data
Record type 2: one item record (structure BICSP) per item
All BOM item records are assigned to the preceding BOM header, until the next BOM header or session header occurs in the sequential file
Record type 3: one sub-item record (structure BICSU) per sub-item
All BOM sub-item records are assigned to the preceding BOM item, until the next item header, BOM header, or session header occurs in the sequential file
and x-line which will be used as index while retreiveing
and the file to be imported should contain values in this format
BGR00 data will be in first line (0-stype)
BICSK in second line (1 stype)
BICSP in 3rd line
BICSU in 4th line
e.g:
0 sessname 800
1 CS01 123
2 values req
3 values req
Hope this gives u some idea...
<b>Reward points</b>
Regards

Upload sales text for material master using LSMW direct input method

Hello Experts,
I was trying to upload sales text for a material master using LSMW direct input method.
I followed the following steps for the same
Tab dlimited Text file format
MATNR           LONGTEXT                                                     LINE
MATERIAL1    LONGTEXT FOR MATERIAL MATERIAL1       1
Step1 -> Maintain object attributes
Object -> 0001
Method-> 0001
Program name -> /SAPDMC/SAP_LSMW_IMPORT_TEXTS
Program type -> D
Step2 -> Maintain Source Structure
Source structure -> LONG_TEXT            Source structure for long text
Step 3-> Maintain souce file
Source Fields
ZLONG_TEXT             Source structure for long text
                       MATNR                         C(018)    MATNR
                       LTEXT                          C(132)    LTEXT
Step 4-> Maintain structure relationship
Structure Relations
/SAPDMC/LTXTH Long Texts: Header                                           <<<< ZLONG_TEXT Source structure for long text
              Select Target Structure /SAPDMC/LTXTH .
/SAPDMC/LTXTL Long Texts: Row                                              <<<< ZLONG_TEXT Source structure for long text
             Select Target Structure /SAPDMC/LTXTL .
Step 5-> Maintain Field mapping and conversion rules
Here i have assigned constan rules to couple of them like
/SAPDMC/LTXTH                  Long Texts: Header
Fields
   OBJECT                Texts: Application Object
                                Rule :   Constant
                                Code:    /SAPDMC/LTXTH-OBJECT = 'MVKE'.
   NAME                  Name
                                Source: ZLONG_TEXT-MATNR (MATNR)
                                Rule :   Transfer (MOVE)
                                Code:    /SAPDMC/LTXTH-NAME = ZLONG_TEXT-MATNR.
   ID                         Text ID
                                Rule :   Constant
                                Code:    /SAPDMC/LTXTH-ID = '0001'.
   SPRAS                 Language Key
                                Rule :   Constant
                                Code:    /SAPDMC/LTXTH-SPRAS = 'E'.
/SAPDMC/LTXTL                  Long Texts: Row
Fields
    TEXTFORMAT     Tag column
                                Rule :   Constant
                                Code:    /SAPDMC/LTXTL-TEXTFORMAT = '/'.
    TEXTLINE             Text Line
                                Source: ZLONG_TEXT-LTEXT (LTEXT)
                                Rule :   Transfer (MOVE)
                                Code:    /SAPDMC/LTXTL-TEXTLINE = ZLONG_TEXT-LTEXT.
Step6 -> Specify file
Legacy Data          On the PC (Frontend)
             Data                           D:\Sales_Longtext.txt
Step7 -> Assign File
ZLONG_TEXT Source structure for long text
              Data D:\Sales_Longtext.txt
Step8 -> Read data
Output result
Source Structure             Read      Written        Not Written
ZLONG_TEXT              1                1              0
Transactions Read:            1
Records Read:                   1
Transactions Written:         1
Records Written:                 1
Step 8 -> Display read data
Field Name                    Field Text Field Value
MATNR                          MATNR      MATERIA1
LTEXT                            LTEXT      SALES TEXT FOR Material MATERIAL1
Step 9 -> Convert data
File Read:          ZNRD_PRJ1_ZNRD_SUBPRJ2_ZNRD_LTEXT.lsmw.read
File Written:       ZNRD_PRJ1_ZNRD_SUBPRJ2_ZNRD_LTEXT.lsmw.conv
Transactions Read:                 1
Records Read:                        1
Transactions Written:              1
Records Written:                     2
Step 10 -> Display converted data
1 /SAPDMC/LTXTH                   1MVKE      MATERIAL1                                                                   0001E
2 /SAPDMC/LTXTL                   2/ SALES TEXT FOR Material MATERIAL1
Step 11 -> Start direct input program
Output result for the same
Legacy System Migration Workbench
Project:                              ZNRD_PRJ1       ORH
Subproject:                        ZNRD_SUBPRJ2    Upload long text
Object:                               ZNRD_LTEXT      Long text tru direct input
File :                                   ZNRD_PRJ1_ZNRD_SUBPRJ2_ZNRD_LTEXT.lsmw.conv
Long Texts in Total:                                1
Successfully Transferred Long Texts: 1
Non-Transferred Long Texts:                 0
Now when i check the material master sales view -> sales text it is empty.
Please help me with the same.
Regards,
Ranjith N

Hello Experts, I was trying to upload sales text for a material master using LSMW direct input method.
I followed the following steps for the same
Tab dlimited Text file format
MATNR             LONGTEXT                                              LINE
MATERIAL1     LONGTEXT FOR MATERIAL MATERIAL1 1 *************************************************************************************************************
Step1 -> Maintain object attributes
Object -> 0001
Method-> 0001
Program name -> /SAPDMC/SAP_LSMW_IMPORT_TEXTS
Program type -> D
Step2 -> Maintain Source Structure
Source structure -> LONG_TEXT Source structure for long text
Step 3-> Maintain souce file Source Fields
ZLONG_TEXT Source structure for long text
MATNR C(018) MATNR
LTEXT C(132) LTEXT
Step 4-> Maintain structure relationship
Structure Relations
/SAPDMC/LTXTH Long Texts: Header <<<< ZLONG_TEXT Source structure for long text
Select Target Structure
/SAPDMC/LTXTH . /SAPDMC/LTXTL Long Texts: Row <<<< ZLONG_TEXT Source structure for long text
Select Target Structure /SAPDMC/LTXTL .
Step 5-> Maintain Field mapping and conversion rules
Here i have assigned constan rules to couple of them like
/SAPDMC/LTXTH Long Texts: Header
Fields
OBJECT            Texts: Application Object
                         Rule : Constant
                          Code: /SAPDMC/LTXTH-OBJECT = 'MVKE'.
NAME               Name
                         Source: ZLONG_TEXT-MATNR (MATNR)
                         Rule : Transfer (MOVE)
                         Code: /SAPDMC/LTXTH-NAME = ZLONG_TEXT-MATNR.
ID                     Text ID
                         Rule : Constant
                         Code: /SAPDMC/LTXTH-ID = '0001'.
SPRAS             Language Key
                         Rule : Constant
                        Code: /SAPDMC/LTXTH-SPRAS = 'E'.
/SAPDMC/LTXTL Long Texts: Row
Fields
TEXTFORMAT Tag column
                         Rule : Constant
                         Code: /SAPDMC/LTXTL-TEXTFORMAT = '/'.
TEXTLINE          Text Line
                         Source: ZLONG_TEXT-LTEXT (LTEXT)
                         Rule : Transfer (MOVE)
                         Code: /SAPDMC/LTXTL-TEXTLINE = ZLONG_TEXT-LTEXT.
Step6 -> Specify file Legacy
Data On the PC (Frontend)
             Data D:\Sales_Longtext.txt
Step7 -> Assign File ZLONG_TEXT
Source structure for long text
          Data D:\Sales_Longtext.txt
Step8 -> Read data
Output result
Source Structure            Read                Written                Not Written
ZLONG_TEXT                  1                       1                            0
Transactions Read          1
Records Read:                1
Transactions Written:      1
Records Written:             1
Step 8 -> Display read data
Field Name             Field Text                      Field Value
MATNR                    MATNR                         MATERIA1
LTEXT                     LTEXT                            SALES TEXT FOR Material MATERIAL1
Step 9 -> Convert data
File Read: ZNRD_PRJ1_ZNRD_SUBPRJ2_ZNRD_LTEXT.lsmw.read
File Written: ZNRD_PRJ1_ZNRD_SUBPRJ2_ZNRD_LTEXT.lsmw.conv
Transactions Read:    1
Records Read:           1
Transactions Written: 1
Records Written:         2
tep 10 -> Display converted data
1 /SAPDMC/LTXTH     1    MVKE        MATERIAL1 0001   E
2 /SAPDMC/LTXTL     2/   SALES TEXT FOR Material       MATERIAL1
Step 11 -> Start direct input program
Output result for the same
Legacy System Migration Workbench Project:
ZNRD_PRJ1 ORH
Subproject:   ZNRD_SUBPRJ2     Upload long text
Object:          ZNRD_LTEXT          Long text tru direct input
File :              ZNRD_PRJ1_ZNRD_SUBPRJ2_ZNRD_LTEXT.lsmw.conv
Long Texts in Total:                                1
Successfully Transferred Long Texts: 1
Non-Transferred Long Texts:                0
Now when i check the material master sales view -> sales text it is empty. Please help me with the same.
Regards,
Ranjith N

Equipment BOM using LSMW- standard batch/Direct input method - reg

Similar Messages

Maybe you are looking for