LSMW Material Master by Bapi Method Part 2

SAP ERP - Logistics Materials Management
(SAP MM): LSMW Material master by BAPI

method - Part 2
Posted by Juergen L Dec 27, 2012
This blog is in continue to the LSMW Material master by BAPI method - Part 1
I would like to show how BAPI method is used to create and change material master.
As an example I use a real business case:
existing material masters need to be updated with new material descriptions and sales text
not all materials have a sales text view
Text needs to be maintained in German and English language, English text is identical to German text
Text is provided in a Excel spreadsheet
Annotation: Our material numbers are set as Lexicographical, no leading zeros
We have to use a certain path to store the .read and .conv files
The homepage of LSMW can be found here in SCN at http://scn.sap.com/docs/DOC-26158

In that document you can find the links to the general documentation in help.sap.com too:
http://help.sap.com/saphelp_nw70/helpdata/en/4d/455035082e2271e10000009b38f889/frameset.htm
Step 1 - Maintain object attributes

Here you define if your LSMW object is for a one-time data transfer or if you want use it permanently as a
periodic transfer.
Migrations are usually one-time data transfers, even you do it many times until you are satisfied with the result
The periodic transfer gives you an option to create a program ready to be used by end-users.
Generated by Jive on 2016-08-10Z

1
SAP ERP - Logistics Materials Management (SAP MM): LSMW Material master by BAPI method - Part 2
Please make use of F4 search help to get the parameters for the import objects.
in this example we are using standard material (industry) as BAPI import method: BUS1001006, method
SAVEREPLICA and Basic type MATMAS_MASS_BAPI03
Step 2 - Maintain source structure

I just have one Excel file with the source data and each line looks equal, so there is no hierarchy no different
structures per line

2
Hence the source structure to be defined is as well a simple flat structure.

Click the create icon enter a name for the source structure and a description.
Don't create a too complex and long name, as you may need to type it in the mapping rules if you have to add
some ABAP coding in the Mapping rules later.
Step 3 - Maintain source fields

In this step you have to enter all the fields that are contained in your source file per structure. I recommend to
use the same sequence as it is in the source file.
There are various options to maintain the source fields as you can see in the pop-up after clicking the "CopyButton"
you can upload the fields from a text file, or copy it from another LSMW object, or you copy it from data
dictionary (I will explain this in more detail later in another blog), or you can copy it from the first line of your
data file (but as you do not have the field length in the first line you need to complete it anyway manually).

3
For such small files like in this business case I usually do it manually. Move the cursor onto the structure line,
then click the table icon (right from the copy icon). This is more convenient than defining field by field via the
create button.
I usually use the field names, its type and length from data dictionary in SAP, but if you want identify the values
from your source based on field names (instead of position in field sequence), then you need to make sure that
the fields names are identical with your source file.

4
Step 4 - Maintain structure relations

In this step you can see that a BAPI or IDOC structure is much more complex than a structure that you get
from a recording.
But don't panic, you do not need to care about any part, just about the parts that are needed for your migration
case.
You move the cursor onto the structure that you need and click the create relationship button. As your source
structure has just one structure it is assigned automatically. In case of a multi-structure source you would need
to select the source structure that need to be assigned to the corresponding target structure.
We have fields that are used in many target structures in just one source structure, so we assign this source
structure to all needed target structures.
In our example it is the header segment (it always needs to be assigned), the header segment with control
information, the material description and the long text.

5
Step 5 - Maintain field mapping and conversion rules

After you assigned your source structure to the target structure in step 4, in this step you assign your source
fields to the target fields, and you define how the values will be. Whether they are just moved from source
field to target field or if they need to be translated via rules, or fixed value assignment for mandatory or just
necessary fields that are not in your source file.
My first choice is Auto field mapping. You get it from menu Extras > Auto-field Mapping
you will then get a screen to define the rules for this auto field mapping:
Here you control whether you do this for all fields or just for empty fields
I usually choose the 100% match as there are too many fields with similar names that could get a wrong
assignment if you use a lower percentage.
If you have not yet define reusable rules then you can only apply the MOVE rule to the fields. You can change
it anyway later.
And as I want to see what SAP does I choose "with confirmation", SAP will then show me each assignment
and I click only okay to continue.
With my example the auto field mapping does not work as my source field names are different from the BAPI
field names.
This happens often with BAPIs, as they do not use the table field names. With IDOC import method this auto
field mapping is a big success if your source field names are defined like the SAP table fields.

6
In my example we need to do the field mapping manually.

You have to tell the BAPI what views you want maintain, this is done in the header structure, where you find as
well the material number.
move the cursor onto the material field, then click the create source field icon and select the material number
from your source field definition.
Keep in mind that my material number is lexicographic, means it does not have leading zeros. If your material
number is with leading zeros, then you either need those leading zeros in the source file too, or you need
coding to add those leading zeros, otherwise the BAPI is not able to find your material for update.
For my example we need Basic data view for the material description and Sales view for the sales text.
As those fields are not among the fields in the source file we have to assign value as a constant.
Move the cursor onto the field, then click the constant button. You get a pop-up to enter the value, which is just
a X.
Use F4 to assign the value, this helps to avoid errors from typing. SAP behalves sometimes strange if the
characters expected as capital characters are entered as small characters.

7
The sales view is only needed if there is sales text in the source file. Hence we cannot assign a pure constant,
we need some coding.
Nevertheless, assign the constant first, so you need to code less yourself, then double click the coding to get to
the code editor.
Now you only need a small piece of ABAP coding to check if the sales organisation field in the source is empty.
After this is done we move forward to the Segment E1BPE1MAKT for the material description.
Here you find as well the material number field, so you assign it to your source field.(think about leading zeros!)

8
Language is not among the fields in the source file, so you assign the language as a constant. Remember we
need the text in German and English.
However, we can only assign one language here. So you could think about cerating a second LSMW object
to load with the other language, or you make it flexible with some coding. At this point we assign just the first
language. We do it for both language fields LANGU and LANGU_ISO.
LANGU is the 1 character long field, LANGU_ISO is the 2 character long field for language (see table T002 for
reference).
Just assign the language via F4 and SAP will put the right code for you (even you enter e.g. EN in the pop-up,
SAP will only enter E in the LANGU field.
And the last field in this section is the Material description which need to be assigned to your source field.
Now we need to care about the second language, which is from the text identical to the first language as our
product names are equal in all languages.
We do this with a small coding in the section __END_OF_RECORD__
By default you see the code transfer_record. This code submits the entries made in this section.
We need a second record for material description in English.We can force this in the __END_OF_RECORD__
processing time
Double click the coding line here to get to the code editor and enter the code behind the transfer_record
statement.
You only need to move the new value for the 2 language fields, all other field values are still in the memory.
so you add: E1BPE1MAKT-LANGU = 'E'.
and:
E1BPE1MAKT-LANGU_ISO = 'EN'.
followed by: transfer_record.
This way you transferred 2 records for MAKT table with a different language.

9
The same has to be done for the sales text now, but only if we have sales text, which means a few lines more
coding.
But let us start from the beginning in the sales text structure:
All long text is stored in table STXH and STXL. The key of this table is Text object (for material master sales
text: MVKE), the text ID (0001), the language, and a combination of material number, sales organisation and
distribution channel for the text name.
You can find this key if you maintain one material manually, then click the editor icon in the sales text view. In
the editor chose from menu GOTO > Header
and you will get all necessary information.
In this example you assign MVKE as a constant to the Object field, 0001 as a constant to the Text-ID field, and
again the language to the 2 language fields.
For the combination of the text name field we need to do it with coding.

10
Coding is: If MYSRCFILE-VKORG = ' '

SKIP_RECORD.
ELSE.
CONCATENATE E1BPE1MLTX-MATNR MYSRCFILE-VKORG MYSRCFILE-VTWEG
INTO E1BPE1MLTX--TEXT_NAME RESPECTING BLANKS.
Which means: if the sales organisation field is empty, then skip this this structure. If it is no empty, then
concatenate Material number (think about the leading zeros) with sales organisation and distribution channel
and bring this value into the target field .
Until here we only have the first of 2 lines sales text. So we need to take care about the second line and as we
need this sales text as well in the second language we solve this with coding in the __END_OF_RECORD__
section, similar as we did for the material description.

11
the transfer_record statement in line 1 creates a record with the first Sales text line in the German language .
in line 3 we check if there is a second line for sales text, and only if we have one then wie move the content
from the source field to the target field and transfer this record. The language and the object, text id and text
name is still in memory.
And then we repeat the same for the English language. We first move the English language to the 2 language
fields, then we move the 1st line of sales text and transfer the record. And then we do it for the second sales
text line - if present.
Step 6 - Maintain fixed values, Translations , user defined

routines
Not necessary for this business case

12
Step 7 - Specify files

In this step you have to define minimum 3 files, your source file, the read file and the conv file.
When SAP uploads and reads your source file, then it is writing the content into the READ file. The name is
automatically created by SAP using the project, subproject and object name.
When you run the conversion, then SAP reads this READ file and writes the converted data into CONV file.
This file name is as well created automatically by SAP. Here we have a restriction of a maximum length of 45
characters. if you have to write this data into a certain directory, then you may have to shorten the proposed file
name.
Your source file is completely unknown to SAP, so you have to describe it. Which means you have to tell where
it is located, whether it is on your PC drive or in the SAP's file system. In this case the source file is at the PCs
local drive.
As SAP cannot read directly from Excel, you need to save the Excel file as a comma separated file (CSV) or as
a Unicode Text file (TXT).
Keep already in mind that your file has to be closed when you execute the reading step.

13
Please use F4 to find the file on your PC, SAP is then creating the content of the FILE field itself
Enter a name of your choice
Indicate whether this file has one source structure or multiple source structures. In this case there is only one
source structure (remember the definition in step 2)
In case you saved your Excel file as unicode text you have to put the radio button to Tabulator.
As we have field names in the first line in our Excel source, we need to select the box for "Field names at Start
of File". This controls that SAP starts processing the source file at the second line.
If the sequence of fields in the source is identical to the definition made in Step 3 then you have to mark the
box "Field Order Matches Source Structure Definition". Without this indicator SAP would try to find the fields
based on the names.
Further set the radio button to "Record End Marker" and to ASCII as we are using a text file as source.

14
Step 8 - Assign files

Not much to do, as there is only one source file, SAP proposed it automatically, you only need to click SAVE
Step 9 - Read Data

In this step you read the data from your source file. SAP automatically generates the Read-Program based on
the settings made in the earlier steps.
You can process it for all your data or only for a part of it.
In case you defined amount and date fields in your source (step 3) then you have here the option for automatic
conversion. Without having amount and date fields you can ignore the defaults.
After execution you get the numbers of read records and transactions. As we have only a flat structure the
numbers for records and transactions is equal.
However, you should verify with your source file if this number is correct. It is the first indication when
something may be wrong.
I had often cases where people had deleted content from the Excel file, I mean cell content, they had not
deleted rows. For Excel those rows with erased content are still active, and they get saved as empty lines at
the end of your text file. So SAP may read many lines more than actually have data. If you have a good sense
for data then the number of read records will already tell you something.

15
Step 10 - Display Read Data

A very important step is to display the read data, because you can check if the values were moved into the
correct fields and that they fit into the fields and do not overlap with other fields ( in this case you have to
redefine your field length in step 3)
You cannot see this from the overview, you have to click the line to get into the detail.

16
However, the overview screen is important too. Here you can see in one sight if the records look equally or if
you see a kind of wave, which indicates that something with the field lengths i wrong. And if you use the icons
to go the end then you can as well check if your records have data until the last record
SAP will process even empty records in the conversion step, which certainly leads to errors. Such empty
records need to be removed from your source file, then you need to read it again.

17
Step 11 - Convert Data

Similar to the Read Data step you can convert only a selection or all data.
Important here is to set the radio button to "Create File". This way SAP writes the CONV file with the converted
data. This corresponds to the setting made for the Port in Activation of IDOC Inbound processing.
Further is gives you the last chance to check in step 12 a few individual records if the data was correct
converted.
Not to forget that you get the numbers of converted records and transactions. Those numbers will hopefully
match with your expected numbers:
I usually store this output as text file for audit purposes.

18
Step 12 - Display converted Data

Like in step 10 you can call the display for all or just for a selection. If you have more than 5000 records then
you should restrict the selection.
You get first the overview screen, similar to the Read data, and can as well go into the detail by clicking a line.
The converted data is displayed according to the target structure. Only those segments that were selected in
step 4.
The green lines are technical lines for the IDOC, The yellow line is the header segment for the transaction, the
blue lines are the individual records.
You can already see that there are 2 records with ...MAKT which holds the material description in German and
English
and another 2 records with ...MLTX for the sales text. (if we had sales text wit 2 lines, then we could see 4
records here)
Go into the detail of at least any record of one transaction to verify that each target field has the right content.
Step 13 - Start Idoc Generation

Not much to worry, you have just 2 options: Execute or leave

19
SAP proposed already the file name with the CONV file. Click execute and see the count in the status line
going up.
SAP tells you when it has finished. then leave this step and continue with the next step.
Step 14 - Start Idoc Processing

You will see a bigger selection screen, but everything needed is defaulted and you can just execute it.
If you have many thousand IDOCs, then better execute it in background (via menu Program > run in
background).
Even the IDOC posting is much quicker than batch input sessions, I have often migrations with 10 and more
hours for processing of one object.
Changing material text and sales text for about 40000 materials needed only 36 minutes.

20
When processing has finished, then SAP present an overview like you probably know it from MM17 Mass
maintenance.
You can sort it by status to get immediately an overview if you have failed IDOCs.
However, this analysis is better made from the next step.
Step 15 - Create Idoc Overview

If you ran the processing step in foreground, then the selection screen is already fully defaulted and you can
execute it like it is.
If it is not defaulted, then enter the "Created at" time and the "created on" date and enter the logical message,
here "MATMAS_MASS_BAPI" and execute.
The overview looks slightly different now.
You get a frame on the left from which you can select the IDOCs based on its status.
As we have done everything correct, only one status is shown.

21
By double click onto the IDOC number you can display the IDOC details, and eventually correct the content of
a failed IDOC and then repost the IDOC in the last step of your LSMW. I plan to describe this in more detail in
another blog later (but first I have to make something wrong, otherwise I cant get the screen shots - this will be
tough

22
18216 Views Tags: abap, port, idoc, bapi, define, lsmw, material_master, long_text,
enterprise_resource_planning, import_method, partner_profile, we20, we21,
sap_erp_logistics_materials_management
Juergen L in response to Anand Babu on page 23

Aug 4, 2016 1:00 PM
Please post a question in the forum and provide more details e.g. from your mapping in LSMW and from the
IDoc segments
Anand Babu in response to Juergen L on page 23
Aug 4, 2016 12:10 PM
Hi Juergen,
The net weight is filled in MARA segments.
Juergen L in response to Anand Babu on page 24
Aug 3, 2016 8:30 PM
you cannot have a gross weight without net weight.

23
So you have to fill as well E1BPE1MARA-NET_WEIGHT along with its units.

Anand Babu in response to Juergen L on page 24
Aug 3, 2016 6:43 PM
Hi Juergen,
Greetings.
I need your inputs on MATMAS_MASS_BAPI03.
I am trying to update Gross weight data for the material but the segment E1BPE1MARA doesn;t have the
BRGEW field to be mapped to.
But we have the gross field BRGEW in E1BPE1MARM which loads the Alternate UoM data.
When I try to mapped the Groos weight field to E1BPE1MARM, it is failing with the error "Enter the unit of
weight for the net weight". Below is the screenshot of E1BPE1MARM segment.
the corresponding X fields are set correctly.

Could you please let me know how should the segments need to be mapped for Gross weight update.
Kind regards,
Anand
Dipankar Som
Jul 30, 2016 7:06 PM
Nice document. Thanks for sharing with us
Juergen L in response to Joris Bayer on page 24
Jul 29, 2016 4:02 PM
I can't answer that without seeing screenshots from the IDOC data and from text file. Please open a discussion
in MM space and provide the details
Joris Bayer in response to Juergen L on page 24
Jul 29, 2016 3:40 PM
The IDOC posts 'green' even if I provide incorrect data on purpose in the source TXT file (e.g. material X128
instead of material 128). I guess something is wrong with the ALE part although all settings in WE20/21 seem
to be correct. Master data are not updated (MTPOS_MARA)

24

Jul 28, 2016 9:23 PM
This field is also redundant with MARM, this is valid for all fields that have been moved into MARM.
Jul 28, 2016 9:13 PM
OK, that is an important difference between LSMW Batch input and BAPI... Tried with MARA-GROES (Size/
dim) but material wasnt updated.
Jul 28, 2016 9:00 PM
we're coming closer to the root cause, MARA-GEWEI is a relic from old days, at least last millennium, this field
is redundant with the MARM-GEWEI. Online in MM01/MM02 you can enter a value to the weight field (MARAGEWEI) and it gets copied automatically to MARM-GEWEI and vica versa.
This does so not happen in IDOC and BAPI, here you have to add the same value in the MARM structure to
get a successful update.
Jul 28, 2016 8:51 PM
Hi Jurgen, I missed the 'X' value at first but have filled it now. But as mentioned no luck yet with updating the
material master (BISMT, GEWEI) in my little test.
Thanks,
Joris
Jul 28, 2016 8:43 PM
The field has to be open for maintenance, you can't change values for hidden fields
Jul 28, 2016 8:33 PM
I indeed missed the 'X' value. But still the material master field is not modified as defined in my data. Converted
data looks OK, IDOC doesnt give an error. Any other suggestions?
Jul 28, 2016 6:43 AM
the usual mistake is that you missed the X field value
Joris Bayer
Jul 28, 2016 5:46 AM
Hi Jurgen,

25
Great document. I did a quick test and all went well it seemed... Except that the material master value I wanted
to modify in my test wasnt modified by the BAPI. IDOC green, no errors. Any clue what the culprit could be?
Thanks,
Joris
Juergen L in response to Ali Dai on page 26
Mar 18, 2016 12:36 AM
I suggest to open a discussion in the EAM space and then provide some details from your source file for class
and classification as well as from the overview of Dispaly read file step in LSMW. From the target structure
itself I do not see any issue that it would only take one class with with one characteristic.
However I usually load classes and classification separately with IDoc method
Ali Dai
Mar 17, 2016 2:43 PM
Hi Jurgen,
This is once again an excellent post. I have a challenge that I would like to address and ask if you have a way
of resolving it. I need to upload master data (materials and functional locations). For Functional Locations I
use 0440 Standard Object and I can upload one class and one characteristic. However, I want to upload two
classes and more than one characteristic per class.
Do you have any idea?
BR
Mohammed Fath Elbab in response to Juergen L on page 26
Sep 10, 2015 2:25 PM
Dear Jurgen,
Many thanks for your reply.
Juergen L in response to Mohammed Fath Elbab on page 27
Sep 10, 2015 2:13 PM
Not sure if I can help, projects and WBS creation is usually not my duty so there might be something specific to
projects what you are missing.

26
You should post this as a question in the forum instead as a comment to a blog. There you can also post
screenshots of your IDOC structure and content
Mohammed Fath Elbab
Sep 10, 2015 2:05 PM
Hi Jurgen,
it is a very helpful topic.. I am trying to create a Project and WBS . i have followed all your steps and the Idoc
get green however after i checked the project it is not created.
can you help me on this why it is not created?
Abhilash Joseph in response to Juergen L on page 27
Jan 29, 2014 12:36 PM
Thanks Jurgen.Its explained well by you . I thought it should be logical to create only one file due the huge I/
O overhead this will bring if it has to create one file per each IDOC but some of the people who worked in SAP
claimed that there is single physical file per each idoc and hence I asked the question.
Juergen L in response to Abhilash Joseph on page 27
Jan 29, 2014 8:21 AM
It creates 1 file only.
It is possible to directly create IDocs and omit this file.
But this removes an extra chance to check yourself the quality before posting.
Of course it will save time if you do not go this extra step (maybe 15 minutes for 50000 Idocs)
If you tested your LSMW very well in a QA system, then there is no need for this extra step in production
system.
Abhilash Joseph
Jan 29, 2014 8:08 AM
Hi Jurgen,
What I was referring will it result exactly 12 files( one for each Idoc) being created on the server .
I was just trying to understand if it will be a performance bottleneck if there is need to use this for large volume
data set due to heavy I/O(writing a file and then reading this file for DB )
Is there a way to bypass creation of physical files by choosing "create Idocs directly" in step 11.?
Juergen L in response to Abhilash Joseph on page 27
Jan 23, 2014 11:15 AM
not sure if I understand the question correct.
LSMW step 13 converts the data from the conv file into 12 individual Idocs, and they were posted one after the
other
Abhilash Joseph
Jan 23, 2014 4:17 AM
Hi Jurgen
Example very informative.

27
In this example does that mean 12 physical documents were created in SAP Application before being moved
into the respective tables ?
Juergen L in response to Vamsi Krishna C V on page 28
Nov 22, 2013 10:24 PM
I remember that I have seen similar reaction, but I dont remember the exact root cause, must have been my
fault otherwise I would remember
Vamsi Krishna C V
Nov 22, 2013 7:02 AM
Hi Jurgen,
I've been facing a peculiar Issue with MATMAS_MASS_BAPI03.
While popualting the MARAX structure i have passed the MATERIALNUMBER field as 'X'.
(I do know that we have to pass the material number here as well, i passed X by mistake, when i checked the
status it was 53.
My concern is that this could lead to misinformation and some data might be missed to be loaded
I have checked the BAPI return messages by debugging at the BAPI's Call statement
and they provide no info whatever.
the Reason the IDOC sets status as 53 is because the BAPI return table returns message type as S(E
expected). and the IDOC logic interprets it as succesful processing)
I am creating a material with an external number range. so it is required that i pass the Material Number.
But the weird thing is the IDOC goes into status 53. But no data is uploaded into the database.
Functionality wise, the IDOC should not be in status 53, beacause no data was transferred into the database
have you ever faced a similar issue.?
i may be paranoid but just checking.
Regards,
Vamsi
Aravinda Davanam
Nov 11, 2013 1:13 PM
Hi Jurgen,
Its very informative documents, thanks for uploading it.
Aravinda

28
Juergen L in response to Stefan Upmeier zu Belzen on page 29

Sep 11, 2013 10:59 PM
No, I saw it already and had checked my objects, but neither me nor any colleague had used LSMW for
projects and wbs elements.
In general this BUS2054 or project IDOC is used for ALE distribution
I would setup a small ALE scenario and send an existing project which is similar to one that you want load with
transaction CJAL. (see my blog: LSMW migration with IDOC method and using IDOC as source Part1: Extract
by ALE )
then you can check the details of the IDOC in BD87 to evaluate if it contains all what you need. If it does then I
would try to get the same with LSMW.
Stefan Upmeier zu Belzen in response to Juergen L on page 30
Sep 11, 2013 10:43 PM
Hi Jrgen,
did you ever migrate projects and wbs elements with LSMW using BAPI? I would like to do this (see http://
scn.sap.com/thread/3418514 for details of my question)
Best regards
Stefan
Ravindra Devarapalli in response to Mahboob Rahman on page 29
Jul 28, 2013 3:13 PM
Hi Jurgen,
Thanks your sharing valuable document.
Mahboob Rahman
Jul 28, 2013 7:46 AM
Very informative indeed, thank you so much Jurgen.
With Warmest Regards,
Mahboob Rahman
yawar khan in response to Juergen L on page 29
Jan 8, 2013 7:18 AM
Thanks a lot Jurgen...................
Regards,
yawar Khan
Juergen L in response to yawar khan on page 30
Jan 3, 2013 10:07 AM
Thank you for informing me. There are already many reports of lost images in the SCN Bug Reporting space
I added a pdf copy of this blog in my google docs: Please download it from there in the meantime:

29
https://docs.google.com/open?id=0B4VGSkvGNHAyNEJZRVBoZlZvLTA
yawar khan
Jan 3, 2013 5:13 AM
Hi Jurgen,
I was not in the favour of using LSMW for Material master, This document will surely help.
but I am not able to view the screen shots from Step no 4 and latter.
Please help.
Regards
Yawar Khan
Rajen Patel
Dec 28, 2012 5:21 PM
Very informative and useful blog. Thanks for sharing.
Juergen L in response to Raju Prabhune on page 30
Dec 28, 2012 10:10 AM
This is certainly possible, e.g. for purchase orders, contracts and for bill of materials and many more
the F4 search help lists in the BAPI field lists all objects .
I plan to write a few more blogs regarding data migration, e.g. about advantages and disadvantages with
certain import methods, common errors, challenges in huge migration projects, SAP to SAP migration....
Hope I find time to do that before my next migration project goes into the busy phase.
Raju Prabhune
Dec 28, 2012 5:35 AM
Jurgan Sir,
I'm big fan of you for SAP MM.
Other than master data, transaction data also can be uploaded using BAPi?
Regards,

30

LSMW Material Master by Bapi Method Part 2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

LSMW Material Master by Bapi Method Part 2

Uploaded by

Copyright:

Available Formats

SAP ERP - Logistics Materials Management

(SAP MM): LSMW Material master by BAPI

The homepage of LSMW can be found here in SCN at http://scn.sap.com/docs/DOC-26158

Step 1 - Maintain object attributes

Generated by Jive on 2016-08-10Z

Step 2 - Maintain source structure

Generated by Jive on 2016-08-10Z

Hence the source structure to be defined is as well a simple flat structure.

Step 3 - Maintain source fields

Generated by Jive on 2016-08-10Z

Generated by Jive on 2016-08-10Z

Step 4 - Maintain structure relations

Generated by Jive on 2016-08-10Z

Step 5 - Maintain field mapping and conversion rules

Generated by Jive on 2016-08-10Z

In my example we need to do the field mapping manually.

Generated by Jive on 2016-08-10Z

Generated by Jive on 2016-08-10Z

Generated by Jive on 2016-08-10Z

Generated by Jive on 2016-08-10Z

Coding is: If MYSRCFILE-VKORG = ' '

Generated by Jive on 2016-08-10Z

Step 6 - Maintain fixed values, Translations , user defined

Generated by Jive on 2016-08-10Z

Step 7 - Specify files

Generated by Jive on 2016-08-10Z

Generated by Jive on 2016-08-10Z

Step 8 - Assign files

Step 9 - Read Data

Generated by Jive on 2016-08-10Z

Step 10 - Display Read Data

Generated by Jive on 2016-08-10Z

Generated by Jive on 2016-08-10Z

Step 11 - Convert Data

Generated by Jive on 2016-08-10Z

Step 12 - Display converted Data

Step 13 - Start Idoc Generation

Generated by Jive on 2016-08-10Z

Step 14 - Start Idoc Processing

Generated by Jive on 2016-08-10Z

Step 15 - Create Idoc Overview

Generated by Jive on 2016-08-10Z

Generated by Jive on 2016-08-10Z

Juergen L in response to Anand Babu on page 23

Generated by Jive on 2016-08-10Z

So you have to fill as well E1BPE1MARA-NET_WEIGHT along with its units.

the corresponding X fields are set correctly.

Generated by Jive on 2016-08-10Z

Juergen L in response to Joris Bayer on page 25

Generated by Jive on 2016-08-10Z

Generated by Jive on 2016-08-10Z

Generated by Jive on 2016-08-10Z

Generated by Jive on 2016-08-10Z

Juergen L in response to Stefan Upmeier zu Belzen on page 29

Generated by Jive on 2016-08-10Z

Generated by Jive on 2016-08-10Z

You might also like