I want to upload material master (MM01) using LSMW with BAPI method
I want to upload material master (MM01) using LSMW with BAPI method and also later on I may need to change the updated data.
Which business object and Method I should use so that i can do both.
Thanks
kumar n
Hi,
The business object is BUS1001.
Thanks,
Murali
Similar Messages
-
hi experts,
by using bapi_po_create, i have to upload the data by using lsmw.please help me.what are the step to upload the data?
thank you
with regards,
rohitRefer these links:
1. BAPI And LSMW and
2. Getting BAPIs into LSMW?
Regards,
Ravi -
Problem in uploading material master data using BDC?
Hi all,
I am using BDC call transaction method to upload material data. Here i am facing a problem that a value in the flat file is going to the wrong screen field . But my recording done properly.
In recording, after entering the data in the view BASIC DATA1 and trying to enter the text . For this i need to scroll down the scroll bar and after that i am clicking on basic data text and entering the text. Here i am not touching the languge field.
But the problem is the text to be entered into the basic data text is storing in language and giving error.
Please help me by specifying the reason and solution for this problem? Whether i did any mistake in recording in scrolling?
Thanks,
Vamshi.Hi
Go with BAPI for such huge transactions and screens. Use BAPI: BAPI_MATERIAL_SAVEDATA.
Regards,
Vishwa. -
Problem in uploading material master data using BAPI?
Hi all,
I am using BAPI_MATERIAL_SAVEDATA to upload materail master data. Here i have to pass moving average price values in two currenices(using account_view and valuationdata in BAPI). But i found only one field for moving average price i.e moving_pr in valuationdata.
Please help me on how to upload the moving average price in two currencies?
Thanks,
Aravind.Hi
There is function module BAPI_MATERIAL_SAVEREPLICA where
VALUATIONDATA parameter is in the tables tab.
But I didn't test it. Try, may be it works as you need. -
Getting error while uploading gl master data using LSMW batch input data
Hi Experts,
I am getting error while uploading the GL master data through lsmw using batch input recording.
After completion of all steps at the time of running batch input session error i am getting is "maintain EN language discription"
and Pls tell me is it possible to upload transactional data using lsmw? if yes pls explaing briefly.Hello,
Kindly post in the FI forum to get a better response.
Regarding the issue you might check whether the correct column is being picked up where you have maintained the description.
Kind Regards // Shaubhik -
Transferring MATERIAL MASTER DATA USING lsmw
I am using LSMW to transfer material master data from text file using direct input program RMDATIND. The problem is that the field WRKST in screen is of 48 characters while the batch data structure BMMH1 of field WRKST contains 14 characters. How can we transfer the full 48 characters in text file to THE FIELD BMMH1 IN DIRECT INPUT PROGRAM. Can we write any translation or routines . If yes, how is it possible. I can do the same using BDC but our client is already using the LSMW , only the new field WRKST for material has to be inserted. It is picking only 14 characters.
Regards
DebopriyoHi
Kindly use the sap note 351557 it is applicable for your release
if you have any further clarifications let me know
Regards
Damu -
Re:Uploading of material master data using lsmw-idoc method
Hi friends,
While processing each idoc one log on window is opening,and status of idoc is 51,eventhough i am passing material description to maktx of e1maktm,it is showing an 'No description is passed'.
Colud you please tell me how to correct these errors,i am new to this lsmw-idoc method.
Thanks in advance,
Anusha.Thank you for reply.
Actually I am uploading the data in flat file from file port to sap.
In idoc inbound processing of lsmw i have created a file port and iam giving the logical system name of the same client.
is this the correct procedure.
Every time when i process each idoc one new logon window is opening and it is showing idoc status as 51.
could you please tell me how to correct this one. -
Upload Vendor master data using LSMW
Hi All,
i am working on LSMW for uploading the Vendor master data (XK01),
when i execute the 13 th step (Create batch input session), i got a message like
"Editing was terminated" .
Could you please tell me why that message is comming.
Regards,
Amjad.hi
good
try with these links
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/abap/abap%20code%20samples/smartforms/smartform%20in%20abap.pdf
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/abap/abap%20code%20samples/smartforms/tutorial%20with%20code%20sample%20on%20smart%20forms.pdf
thanks
mrutyun^ -
Upload Material master with long text using LSMW
Hello,
i want ot upload material master data via MM01 using LSMW in following views: basic data 1 ,2, purchasing, purchase order text, plant data 1,2.
i have to upload long text in purchase order text with length more then 132 char. (approx 700 char long text). and i have text file in which long text is maintained in a single row. then how can i do it without formating text file or anyother possible solution.
please help.ca u clarify how can i do it.
suppos i have longtext "Air cooled type air-conditioning unit complete with following components & distance between indoor & outdoor unit is 10 RMT. A).Indoor evaporating unit comprising of cooling coils,insulated drain tray,20 micron HDPE washable filters,blower,motor,electical junction box etc. B).Outdoor condensing unit comprising of hermatic/semiharmetic compressor's.condenser coils,propeller/axial fans,motors,pressure switches/cutout etc.C).Charging of refrigerant gas & oil.D).Inter connecting refrigerating piping of copper duly insulated with EXPANDED POLYETHYLENE tubing.E).Complete electical power wiring of AL.&Control wirng of copper required from indoor & outdoor units.Earthing of the complete system with 8 G G.I.wire. F).Electrical panel will be completed with necessary starter,fuses,switches,timers,over-load relays,contactors,push button and indicating lamps,single phasing preventer etc..and also with remote control with cording. G).The panel should have 1 no.potential free contactor to connect with central fire detection system.The panel should have voltage scanner to ensure stabilized power input to the machine.H).Outdoor unit shall be mounted on MS angle base frame structure duly black painted with synthetic epoxy paint.I).The frame structure shall be mounted on MS plate & serrated rubber pads."
then what i have to do changes in lsmw.? -
How to upload different views of customer master data using LSMW-IDOC
I need to upload customer master data using LSMW Idoc method for my client. Now customer will have different views like main view, Sales data, Company code data, Partner function data etc. And except main data all other data can be multiple for each customer. We are going to upload data from tab delimited .TXT file. Should I propose different LSMW for upload different views for the customer from different .TXT files? or we can upload all the customer related data (like main view data and partner function data )from a single .TXT file. Kindly suggest which one in convenient and how we can prepare the data file in both cases.
convinient is the method that you can handle.
but as the guy who loads the data you have to load the data like they are available, like it is convinient for others to prepare the data.
In general there is no problem to use an IDOC method to load a customer master with multiple comany codes and several sales orgs in one shot.
the data can be in one source file, but need then to be maintained in a certain way
Example1: all data in 1 structure
GD1 - CC1 - SO1
GD1 - CC2 - SO2
GD1 - CC2 - SO3
in this case the GD (general data) is redundand in each line which has different Company code data or different Sales Org data
Example2: all data in 3 sturcures but one file
GD1
.CC1
.CC2
..SO1
..SO2
..SO3
Example3: data delivered in 3 files - you join the files in LSMW, they must have a common identifier like the old customer number in the beginning of each file
FILE General data:
GD1
GD2
GD3
file Compamy code data:
CC1
CC2
CC3
file Sales org data:
SO1
SO2
SO3
LSMW is flexible and can handle each of this scenarios, are you flexible too? -
Export materials master data using LSMW?
Hello gurus,
is it possible to export material master data using LSMW? Or are there other ways to do this (apart from manually selecting the desired data from the DB tables?)
It would be great if anyone could point me to some documentation on this.
We would like to export the master data from one SAP system and import it in another one.
Thanks in advance
AliciaWhat I usually do is transferring the data via ALE (BD10) as IDOC to a file (instead of a different system). This file can even be located in an shared folder that can be accessed from both SAP systems
Then I use LSMW in target system, map IDOC to IDOC (almost done automatically) and import the data from this file, and beeing able to exchange field values if necessary. -
Sales order Using LSMW and BAPI BUS2032
Hi Guys,
I am trying to use LSMW for creating sales order through BAPI.
Business Object BUS2032
Method CREATEFROMDAT2
Message Type SALESORDER_CREATEFROMDAT2
Basic Type SALESORDER_CREATEFROMDAT202
I can do it using a BDC program.
I want to know how the sales order flat file will look like (one header and multiple line item)if i am using LSMW with BAPI and how it is mapped for multiple line items.
Thanks in Adv.
AkhilSee if you can get something out of this.
One simple step by step example
Complete the step one (you are using the correct BAPI )
insetp 2(Maintain Source Structures) create source structures like with the header and details hierarchy
5 ZCFOF0021_HDR Header
ZCFOF0021_PARTNER Partner
ZCFOF0021_ITM Item Detail
In Step 3(Maintain Source Fields) create the fields for all source structures like below example
5 ZCFOF0021_HDR Header OLDNR C(008) Legacy JDE Sales Order Number
VKORG C(004) Sales Organization
VTWEG C(002) Distribution Channel
SPART C(002) Division
AUART C(004) Sales Document Type
VDATU C(008) Requested delivery date
BSTKD C(020) Customer purchase order number
BSARK C(004) Customer purchase order type
BSTDK C(008) Customer purchase order date
INCO1 C(003) Incoterms (part 1)
INCO2 C(028) Incoterms (part 2)
ZTERM C(004) Terms of payment key
LIFSK C(002) Delivery block (document header)
FAKSK C(002) Billing block in SD document
WAERK C(005) SD document currency
KURSK C(009) Exchange Rate for Pricing and Statistics
AUTLF C(001) Complete delivery defined for each sales order
VSBED C(002) Shipping conditions
ZOTC_PATNAME C(035) Patient Name
ZOTC_PATREFNO C(035) Patient Reference Number
ZOTC_IMPDATE C(008) Implant Date
BNAME C(030) Branching name
TAXK1 C(001) Alternative tax classification
5 ZCFOF0021_PARTNER Partner
OLDNR C(008) Legacy JDE Sales Order Number
PARVW C(002) Partner function
KUNNR C(010) Sold To
NAME1 C(035) Name 1
STRAS C(035) House number and street
STR_SUPPL1 C(040) Street 2
LAND1 C(003) Country Key
PSTLZ C(010) Postal Code
ORT01 C(035) City
REGIO C(003) Region (State, Province, County)
AUART C(004) Sales Document Type
5 ZCFOF0021_ITM Item Detail
OLDNR C(008) Legacy JDE Sales Order Number
MATNR C(018) Material Number
WERKS C(004) Plant
LGORT C(004) Storage Location
VRKME C(003) Sales unit
KSCHL2 C(004) Condition type
KBETR2C C(011) Condition rate with decimal places and minus sign
KWAER2 C(005) Currency key
WMENGC C(013) Order qty in sales units - 00009001 corresponds to 9.001
CHARG C(010) Batch Number
In Step 4 (Maintain Structure Relations) assign source structures to target strucutres like below
E1SALESORDER_CREATEFROMDAT2 Header Segment <<<< ZCFOF0021_HDR Header
E1BPSDHD1 Communication Fields: Sales and Distribution Document Header <<<< ZCFOF0021_HDR Header
E1BPSDHD1X Checkbox Fields for Sales and Distribution Document Header
E1BP_SENDER Logical System of Sender
E1BPSDLS SD Checkbox for the Logic Switch
5 E1BPSDITM Communication Fields: Sales and Distribution Document Item <<<< ZCFOF0021_ITM Item Detail
E1BPSDITM1 Communication Fields: Sales and Distribution Document Item
E1BPSDITMX Communication Fields: Sales and Distribution Document Item
E1BPPARNR Communications Fields: SD Document Partner: WWW <<<< ZCFOF0021_PARTNER Partner
E1BPSCHDL Communication Fields for Maintaining SD Doc. Schedule Lines <<<< ZCFOF0021_ITM Item Detail
E1BPSCHDLX Checkbox List for Maintaining SD Document Schedule Line
E1BPCOND Communication Fields for Maintaining Conditions in the Order <<<< ZCFOF0021_ITM Item Detail
E1BPCONDX Communication Fields for Maintaining Conditions in the Order
E1BPCUCFG CU: Configuration Data
E1BPCUINS Instances of Several Configurations
E1BPCUPRT Part_of Entries of Several Configurations
E1BPCUVAL Characteristic Values of Several Configurations
E1BPCUBLB BLOB Internal Configuration Data (SCE)
E1BPCUVK Variant Condition Keys in Configurations
E1BPCUREF CU: Reference Order Item / Instance in Configuration
E1BPCCARD Communication Table: Means of Payment Order/Billing Document
E1BPSDTEXT Communication Fields: SD Texts
E1BPSDKEY Key in Sales and Distribution Document
E1BPPAREX Ref. Structure for BAPI Parameter EXTENSIONIN/EXTENSIONOUT <<<< ZCFOF0021_ITM Item Detail
5 E1BPADR1 BAPI Reference Structure for Addresses (Org./Company) <<<< ZCFOF0021_PARTNER Partner
E1BPADR11 BAPI Reference Structure for Addresses (Org./Company) <<<< ZCFOF0021_PARTNER Partner
In Step 5(Maintain Field Mapping and Conversion Rules) assign source fields to target fields
Map each filed to the target fields. -
How to upload material master using BAPI
I have a flat file with 3 fields MATNR,MAKTX,MEINS and I want to create material master with 2 views basic data1 & basic data2 with three fields using BAPI
Can anyone tell me how to do this only using three fields and 2 views
and also i want to know what is the exact difference between session call transaction BAPI and LSWM methods.
Thank you,
Pradeep Reddy M.Hi Pradeep Reddy Miriyala,
This a example you can use, the views are related with each table only have to adapt to your case.
Best regards
Jaime Cordeiro
*& Report ZMM01_BAPI_01 *
REPORT ZMM01_BAPI_01 .
STRUCTURE DECLARATIONS *
TABLES: BAPIMATHEAD, "Headerdata
BAPI_MARA, "Clientdata
BAPI_MARAX, "Clientdatax
BAPI_MVKE, "SalesData
BAPI_MVKEX, "SalesDatax
BAPI_MARC, "Plantdata
BAPI_MARCX, "Plantdatax
BAPI_MBEW, "ValuationData
BAPI_MBEWX, "ValuationData
BAPI_MLGN, "Storage
BAPI_MLGNX, "StorageX
BAPI_MAKT, "Material description
BAPI_MARM,
BAPI_MARMX,
bapi_mean,
BAPI_MLAN,
BAPIRET2. "Return messages
DATA: BEGIN OF LSMW_MATERIAL_MASTER,
> Initial Data
matnr(18),
mtart(4),
WERKS(4),
VKORG(4),
VTWEG(2),
LGNUM(3),"retirar
> Basic Data 1
MAKTX(40),
MEINS(3),
MATKL(9),
BISMT(18),
SPART(2),
PRDHA(18),
BRGEW(17),
NTGEW(17),
GEWEI(3),
VOLUM(13),
VOLEH(3),
EAN11(18),
NUMTP(2),
> Sales 1
DWERK(4),
TAXKM(1),
> Sales 2
KTGRM(2),
PRODH(18),
MTPOS(4),
> Sales: General/Plant
MTVFP(2),
TRAGR(4),
LADGR(4),
PRCTR(10),
> Purchasing
Novas entradas
EKGRP(3),
KAUTB(1),
XCHPF1(1),
EKWSL(4),
WEBAZ(3),
INSMK1(1),
KORDB(1),
> Foreign Trade
STAWN(17),
MTVER(4),
HERKL(3),
HERKR(3),
> Purchase Order Text View
Identificar Campos
TextoEN(100),
TextoPT(100),
TextoPL(100),
TextoES(100),
> MRP1
DISGR(4),
DISMM(2),
DISPO(3),
DISLS(2),
BSTMI(18),
BSTRF(13),
> MRP2
BESKZ(1),
RGEKZ(1),
LGPRO(4),
LGFSB(4),
EPRIO(4),
WEBAZ1(3),
PLIFZ(3),
FHORI(3),
> MRP3
PERKZ(1),
STRGR(2),
VRMOD(1),
VINT1(3),
VINT2(3),
> MRP4
ALTSL(1),
FEVOR(3),
> Work Sch
INSMK(1),
XCHPF(1),
UEETO(3),
> Plant Storage 1
MHDRZ(4),
MHDHB(4),
> Plant Storage 2
PRCTR1(10),
EPRIO1(4),
> WM 1 S01 comum a todos
LTKZA_S01(3),
LTKZE_S01(3),
LGBKZ_S01(3),
> WM 1 SHV
LTKZA_SHV(3),
LTKZE_SHV(3),
LGBKZ_SHV(3),
> WM 1 SQW
LTKZA_SQW(3),
LTKZE_SQW(3),
LGBKZ_SQW(3),
> WM 2
LHMG1(13),
LHME1(3),
LETY1(3),
LHMG2(13),
LHME2(3),
LETY2(3),
LHMG3(13),
LHME3(3),
LETY3(3),
> Accounting 1
BKLAS(4),
VPRSV(1),
VERPR(23),
PEINH(5),
END OF LSMW_MATERIAL_MASTER.
DATA:V_FILE TYPE STRING.
DATA:VolumUnitConv(3).
DATA:UnitConv(3).
INTERNAL TABLE DECLARATIONS *
*to store the input data
DATA:
BEGIN OF it_matmaster OCCURS 0.
INCLUDE STRUCTURE LSMW_MATERIAL_MASTER.
DATA:
END OF it_matmaster.
*for material description
DATA:BEGIN OF IT_MATERIALDESC OCCURS 0.
INCLUDE STRUCTURE BAPI_MAKT .
DATA:END OF IT_MATERIALDESC.
*FOR gross wt
data: begin of it_uom occurs 0.
include structure BAPI_MARM.
data:end of it_uom.
DATA: BEGIN OF IT_UOMX OCCURS 0.
INCLUDE STRUCTURE BAPI_MARMX.
DATA:END OF IT_UOMX.
data:begin of it_mean occurs 0.
include structure bapi_mean.
data:end of it_mean.
DATA: BEGIN OF it_MLAN OCCURS 0.
include STRUCTURE BAPI_MLAN.
DATA: END OF it_MLAN.
DATA:BEGIN OF IT_MLTX OCCURS 0.
INCLUDE STRUCTURE BAPI_MLTX.
DATA:END OF IT_MLTX.
*to return messages
DATA:BEGIN OF IT_RETURN OCCURS 0.
INCLUDE STRUCTURE BAPIRET2.
DATA:END OF IT_RETURN.
DATA : imat TYPE TABLE OF bapimatinr WITH HEADER LINE.
DATA: text LIKE bapi_mltx OCCURS 0 WITH HEADER LINE.
DATA: matnrAct(18),oldMart(4).
SELECTION SCREEN
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-002.
PARAMETERS:P_FILE LIKE RLGRAP-FILENAME OBLIGATORY.
SELECTION-SCREEN END OF BLOCK B1 .
AT SELECTION SCREEN
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE.
CALL FUNCTION 'F4_FILENAME'
EXPORTING
PROGRAM_NAME = SYST-CPROG
DYNPRO_NUMBER = SYST-DYNNR
FIELD_NAME = 'P_FILE'
IMPORTING
FILE_NAME = P_FILE.
TO UPLOAD THE DATA *
START-OF-SELECTION.
V_FILE = P_FILE.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
filename = V_FILE
FILETYPE = 'ASC'
HAS_FIELD_SEPARATOR = 'X'
HEADER_LENGTH = 0
READ_BY_LINE = 'X'
DAT_MODE = ' '
IMPORTING
FILELENGTH =
HEADER =
tables
data_tab = IT_MATMASTER
EXCEPTIONS
FILE_OPEN_ERROR = 1
FILE_READ_ERROR = 2
NO_BATCH = 3
GUI_REFUSE_FILETRANSFER = 4
INVALID_TYPE = 5
NO_AUTHORITY = 6
UNKNOWN_ERROR = 7
BAD_DATA_FORMAT = 8
HEADER_NOT_ALLOWED = 9
SEPARATOR_NOT_ALLOWED = 10
HEADER_TOO_LONG = 11
UNKNOWN_DP_ERROR = 12
ACCESS_DENIED = 13
DP_OUT_OF_MEMORY = 14
DISK_FULL = 15
DP_TIMEOUT = 16
OTHERS = 17
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
check sy-subrc eq 0.
DATA POPULATIONS *
LOOP AT IT_MATMASTER.
IF IT_MATMASTER-MATNR EQ '' .
oldMart = IT_MATMASTER-Mtart.
CALL FUNCTION 'MATERIAL_NUMBER_GET_NEXT'
EXPORTING
MATERIALART = IT_MATMASTER-Mtart
IMPORTING
MATERIALNR = matnrAct
RETURNCODE =
EXCEPTIONS
NO_INTERNAL_INTERVAL = 1
TYPE_NOT_FOUND = 2
OTHERS = 3
if sy-subrc = 0.
BAPIMATHEAD-MATERIAL = matnrAct.
endif.
ELSE.
BAPIMATHEAD-MATERIAL = it_matmaster-matnr.
ENDIF.
Preenchimento dos dados do ecrã inicial
BAPIMATHEAD-MATERIAL = IT_MATMASTER-MATNR.
BAPIMATHEAD-IND_SECTOR = 'M'.
BAPIMATHEAD-MATL_TYPE = IT_MATMASTER-Mtart.
"declaration of views
BAPIMATHEAD-BASIC_VIEW = 'X'.
BAPIMATHEAD-MRP_VIEW = 'X'.
BAPIMATHEAD-STORAGE_VIEW = 'X'.
BAPIMATHEAD-WAREHOUSE_VIEW = 'X'.
BAPIMATHEAD-ACCOUNT_VIEW = 'X'.
If IT_MATMASTER-Mtart EQ '31'.
BAPIMATHEAD-SALES_VIEW = 'X'.
BAPIMATHEAD-WORK_SCHED_VIEW = 'X'.
ENDIF.
If IT_MATMASTER-Mtart EQ '51'.
BAPIMATHEAD-SALES_VIEW = 'X'.
BAPIMATHEAD-WORK_SCHED_VIEW = 'X'.
ENDIF.
If IT_MATMASTER-Mtart EQ '65'.
BAPIMATHEAD-PURCHASE_VIEW = 'X'.
ENDIF.
Preenchimento de dados relativos a MARA
BAPI_MARA-BASE_UOM = IT_MATMASTER-MEINS.
BAPI_MARA-MATL_GROUP = IT_MATMASTER-MATKL.
BAPI_MARA-OLD_MAT_NO = IT_MATMASTER-BISMT.
BAPI_MARA-DIVISION = IT_MATMASTER-SPART.
BAPI_MARA-PROD_HIER = IT_MATMASTER-PRDHA.
BAPI_MARA-NET_WEIGHT = IT_MATMASTER-ntgew.
BAPI_MARA-UNIT_OF_WT = IT_MATMASTER-GEWEI.
BAPI_MARA-TRANS_GRP = IT_MATMASTER-tragr.
> Novas Entradas
IF IT_MATMASTER-Mtart EQ '65'.
BAPI_MARA-BATCH_MGMT = IT_MATMASTER-XCHPF1.
BAPI_MARA-PUR_VALKEY = IT_MATMASTER-EKWSL.
BAPI_MARAX-PUR_VALKEY = 'X'.
ELSE.
BAPI_MARA-BATCH_MGMT = IT_MATMASTER-XCHPF.
ENDIF.
> Novas Entradas
BAPI_MARA-MINREMLIFE = IT_MATMASTER-MHDRZ.
BAPI_MARA-SHELF_LIFE = IT_MATMASTER-MHDHB.
BAPI_MARAX-MATL_GROUP = 'X'.
BAPI_MARAX-OLD_MAT_NO = 'X'.
BAPI_MARAX-BASE_UOM = 'X'.
BAPI_MARAX-DIVISION = 'X'.
BAPI_MARAX-PROD_HIER = 'X'.
BAPI_MARAX-NET_WEIGHT = 'X'.
BAPI_MARAX-UNIT_OF_WT = 'X'.
BAPI_MARAX-TRANS_GRP = 'X'.
BAPI_MARAX-BATCH_MGMT = 'X'.
BAPI_MARAX-MINREMLIFE = 'X'.
BAPI_MARAX-SHELF_LIFE = 'X'.
Preencimento de dados Relativos a MKVE
BAPI_MVKE-DELYG_PLNT = IT_MATMASTER-DWERK.
BAPI_MVKE-SALES_ORG = IT_MATMASTER-VKORG.
BAPI_MVKE-DISTR_CHAN = IT_MATMASTER-VTWEG.
BAPI_MVKE-PROD_HIER = IT_MATMASTER-PRODH.
BAPI_MVKE-ITEM_CAT = IT_MATMASTER-MTPOS.
BAPI_MVKE-ACCT_ASSGT = IT_MATMASTER-KTGRM.
BAPI_MVKEX-SALES_ORG = IT_MATMASTER-VKORG.
BAPI_MVKEX-DISTR_CHAN = IT_MATMASTER-VTWEG.
BAPI_MVKEX-PROD_HIER = 'X'.
BAPI_MVKEX-ITEM_CAT = 'X'.
BAPI_MVKEX-DELYG_PLNT = 'X'.
BAPI_MVKEX-ACCT_ASSGT = 'X'.
Preencimento de dados Relativos a MARC
BAPI_MARC-PLANT = IT_MATMASTER-WERKS.
BAPI_MARC-AVAILCHECK = IT_MATMASTER-MTVFP.
BAPI_MARC-LOADINGGRP = IT_MATMASTER-LADGR.
BAPI_MARC-PROFIT_CTR = IT_MATMASTER-PRCTR.
IF NOT IT_MATMASTER-Mtart EQ '51'.
BAPI_MARC-COMM_CODE = IT_MATMASTER-STAWN.
BAPI_MARC-COUNTRYORI = IT_MATMASTER-HERKL.
BAPI_MARC-REGIONORIG = IT_MATMASTER-HERKR.
BAPI_MARCX-COMM_CODE = 'X'.
BAPI_MARCX-COUNTRYORI = 'X'.
BAPI_MARCX-REGIONORIG = 'X'.
ENDIF.
BAPI_MARC-MRP_GROUP = IT_MATMASTER-DISGR.
BAPI_MARC-MRP_TYPE = IT_MATMASTER-DISMM.
BAPI_MARC-MRP_CTRLER = IT_MATMASTER-DISPO.
BAPI_MARC-LOTSIZEKEY = IT_MATMASTER-DISLS.
BAPI_MARC-MINLOTSIZE = IT_MATMASTER-BSTMI.
BAPI_MARC-ROUND_VAL = IT_MATMASTER-BSTRF.
BAPI_MARC-PROC_TYPE = IT_MATMASTER-BESKZ.
BAPI_MARC-BACKFLUSH = IT_MATMASTER-RGEKZ .
BAPI_MARC-ISS_ST_LOC = IT_MATMASTER-LGPRO.
BAPI_MARC-DETERM_GRP = IT_MATMASTER-EPRIO.
BAPI_MARC-SM_KEY = IT_MATMASTER-FHORI.
BAPI_MARC-PERIOD_IND = IT_MATMASTER-PERKZ.
BAPI_MARC-PLAN_STRGP = IT_MATMASTER-STRGR.
BAPI_MARC-CONSUMMODE = IT_MATMASTER-VRMOD.
BAPI_MARC-BWD_CONS = IT_MATMASTER-VINT1.
BAPI_MARC-FWD_CONS = IT_MATMASTER-VINT2.
BAPI_MARC-ALT_BOM_ID = IT_MATMASTER-ALTSL.
BAPI_MARC-PRODUCTION_SCHEDULER = IT_MATMASTER-FEVOR.
IF NOT IT_MATMASTER-Mtart EQ '65'.
BAPI_MARC-IND_POST_TO_INSP_STOCK = IT_MATMASTER-INSMK.
BAPI_MARC-OVER_TOL = IT_MATMASTER-UEETO.
BAPI_MARCX-IND_POST_TO_INSP_STOCK = 'X'.
BAPI_MARCX-OVER_TOL = 'X'.
ENDIF.
> Novas Entradas
IF IT_MATMASTER-Mtart EQ '65'.
BAPI_MARC-PUR_GROUP = IT_MATMASTER-EKGRP .
BAPI_MARC-AUTO_P_ORD = IT_MATMASTER-KAUTB .
BAPI_MARC-GR_PR_TIME = IT_MATMASTER-WEBAZ .
BAPI_MARC-IND_POST_TO_INSP_STOCK = IT_MATMASTER-INSMK1 .
BAPI_MARC-SOURCELIST = IT_MATMASTER-KORDB .
BAPI_MARC-EXPIMPGRP = IT_MATMASTER-MTVER .
BAPI_MARCX-PUR_GROUP = 'X'.
BAPI_MARCX-AUTO_P_ORD = 'X'.
BAPI_MARCX-GR_PR_TIME = 'X'.
BAPI_MARCX-IND_POST_TO_INSP_STOCK = 'X'.
BAPI_MARCX-SOURCELIST = 'X'.
BAPI_MARCX-EXPIMPGRP = 'X'.
ENDIF.
> Novas Entradas
BAPI_MARCX-PLANT = IT_MATMASTER-WERKS.
BAPI_MARCX-AVAILCHECK = 'X'.
BAPI_MARCX-LOADINGGRP = 'X'.
BAPI_MARCX-PROFIT_CTR = 'X'.
BAPI_MARCX-MRP_GROUP = 'X'.
BAPI_MARCX-MRP_TYPE = 'X'.
BAPI_MARCX-MRP_CTRLER = 'X'.
BAPI_MARCX-LOTSIZEKEY = 'X'.
BAPI_MARCX-MINLOTSIZE = 'X'.
BAPI_MARCX-ROUND_VAL = 'X'.
BAPI_MARCX-PROC_TYPE = 'X'.
BAPI_MARCX-BACKFLUSH = 'X'.
BAPI_MARCX-ISS_ST_LOC = 'X'.
BAPI_MARCX-DETERM_GRP = 'X'.
BAPI_MARCX-SM_KEY = 'X'.
BAPI_MARCX-PERIOD_IND = 'X'.
BAPI_MARCX-PLAN_STRGP = 'X'.
BAPI_MARCX-CONSUMMODE = 'X'.
BAPI_MARCX-BWD_CONS = 'X'.
BAPI_MARCX-FWD_CONS = 'X'.
BAPI_MARCX-ALT_BOM_ID = 'X'.
BAPI_MARCX-PRODUCTION_SCHEDULER = 'X'.
Preencimento de dados Relativos a MLGN
BAPI_MLGN-WHSE_NO = 'S01'.
BAPI_MLGN-WITHDRAWAL = IT_MATMASTER-LTKZA_S01.
BAPI_MLGN-PLACEMENT = IT_MATMASTER-LTKZE_S01.
BAPI_MLGN-STGESECTOR = IT_MATMASTER-LGBKZ_S01.
BAPI_MLGN-L_EQUIP_1 = IT_MATMASTER-LHMG1.
BAPI_MLGN-L_EQUIP_2 = IT_MATMASTER-LHMG2.
BAPI_MLGN-L_EQUIP_3 = IT_MATMASTER-LHMG3.
BAPI_MLGN-LEQ_UNIT_1 = IT_MATMASTER-LHME1.
BAPI_MLGN-LEQ_UNIT_2 = IT_MATMASTER-LHME2.
BAPI_MLGN-LEQ_UNIT_3 = IT_MATMASTER-LHME3.
BAPI_MLGN-UNITTYPE_1 = IT_MATMASTER-LETY1.
BAPI_MLGN-UNITTYPE_2 = IT_MATMASTER-LETY2.
BAPI_MLGN-UNITTYPE_3 = IT_MATMASTER-LETY3.
BAPI_MLGNX-WHSE_NO = 'S01'.
BAPI_MLGNX-WITHDRAWAL = 'X'.
BAPI_MLGNX-PLACEMENT = 'X'.
BAPI_MLGNX-STGESECTOR = 'X'.
BAPI_MLGNX-L_EQUIP_1 = 'X'.
BAPI_MLGNX-L_EQUIP_2 = 'X'.
BAPI_MLGNX-L_EQUIP_3 = 'X'.
BAPI_MLGNX-LEQ_UNIT_1 = 'X'.
BAPI_MLGNX-LEQ_UNIT_2 = 'X'.
BAPI_MLGNX-LEQ_UNIT_3 = 'X'.
BAPI_MLGNX-UNITTYPE_1 = 'X'.
BAPI_MLGNX-UNITTYPE_2 = 'X'.
BAPI_MLGNX-UNITTYPE_3 = 'X'.
Preencimento de dados Relativos a MBEW
BAPI_MBEW,
BAPI_MBEWX,
BAPI_MBEW-VAL_CLASS = IT_MATMASTER-BKLAS.
BAPI_MBEW-PRICE_CTRL = IT_MATMASTER-VPRSV.
BAPI_MBEW-STD_PRICE = IT_MATMASTER-VERPR.
BAPI_MBEW-PRICE_UNIT = IT_MATMASTER-PEINH.
BAPI_MBEW-VAL_AREA = 'CLPS'."IT_MATMASTER-BWKEY.
BAPI_MBEWX-VAL_AREA = 'CLPS'."IT_MATMASTER-BWKEY.
BAPI_MBEWX-VAL_CLASS = 'X'.
BAPI_MBEWX-PRICE_CTRL = 'X'.
BAPI_MBEWX-STD_PRICE = 'X'.
BAPI_MBEWX-PRICE_UNIT = 'X'.
---------------------------------------------------> Material Descrition
IT_MATERIALDESC-LANGU = sy-langu. "'EN'.
IT_MATERIALDESC-MATL_DESC = IT_MATMASTER-MAKTX.
APPEND IT_materialdesc.
Gross Weight, Volume and EAN
*Volume é preciso uma rotina de conversão
CALL FUNCTION 'CONVERSION_EXIT_CUNIT_INPUT'
EXPORTING
INPUT = IT_MATMASTER-VOLEH
LANGUAGE = SY-LANGU
IMPORTING
OUTPUT = VolumUnitConv
EXCEPTIONS
UNIT_NOT_FOUND = 1
OTHERS = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CALL FUNCTION 'CONVERSION_EXIT_CUNIT_INPUT'
EXPORTING
INPUT = IT_MATMASTER-MEINS
LANGUAGE = SY-LANGU
IMPORTING
OUTPUT = UnitConv
EXCEPTIONS
UNIT_NOT_FOUND = 1
OTHERS = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
IT_UOM-GROSS_WT = IT_MATMASTER-BRGEW.
IT_UOM-ALT_UNIT = UnitConv.
IT_UOM-ALT_UNIT_ISO = IT_MATMASTER-GEWEI.
IT_UOM-UNIT_OF_WT = IT_MATMASTER-GEWEI.
IT_UOM-EAN_UPC = IT_MATMASTER-EAN11.
IT_UOM-EAN_CAT = IT_MATMASTER-NUMTP.
IT_UOM-VOLUME = IT_MATMASTER-VOLUM.
IT_UOM-VOLUMEUNIT = VolumUnitConv.
IT_UOM-VOLUMEUNIT_ISO = IT_MATMASTER-VOLEH.
APPEND IT_UOM.
IT_UOMX-ALT_UNIT = IT_MATMASTER-MEINS.
IT_UOMX-ALT_UNIT_ISO = IT_MATMASTER-GEWEI.
IT_UOMX-GROSS_WT = 'X'.
IT_UOMX-UNIT_OF_WT = 'X'.
IT_UOMX-EAN_UPC = 'X'.
IT_UOMX-EAN_CAT = 'X'.
*Volume
IT_UOMX-VOLUME = 'X'.
IT_UOMX-VOLUMEUNIT = 'X'.
IT_UOMX-VOLUMEUNIT_ISO = 'X'.
APPEND IT_UOMX.
CALL FUNCTION 'BAPI_MATERIAL_SAVEDATA'
EXPORTING
headdata = BAPIMATHEAD
CLIENTDATA = BAPI_MARA
CLIENTDATAX = BAPI_MARAx
PLANTDATA = BAPI_MARc
PLANTDATAX = BAPI_MARcx
VALUATIONDATA = BAPI_MBEW
VALUATIONDATAX = BAPI_MBEWX
WAREHOUSENUMBERDATA = BAPI_MLGN
WAREHOUSENUMBERDATAX = BAPI_MLGNX
SALESDATA = BAPI_MVKE
SALESDATAX = BAPI_MVKEX
IMPORTING
RETURN = IT_RETURN
TABLES
MATERIALDESCRIPTION = IT_MATERIALDESC
UNITSOFMEASURE = IT_UOM
UNITSOFMEASUREX = IT_UOMX
MATERIALLONGTEXT = text
TAXCLASSIFICATIONS = it_MLAN.
if it_return-type eq 'S'.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
endif.
WAIT UP TO 10 SECONDS.
WRITE : / IT_RETURN-MESSAGE.
CLEAR: IT_MATERIALDESC[],
IT_UOM[],
IT_UOMX[],
it_MLAN[],
IT_RETURN,
text,
BAPIMATHEAD,
BAPI_MARA,
BAPI_MARAx,
BAPI_MARc,
BAPI_MARcx,
BAPI_MBEW,
BAPI_MBEWX,
BAPI_MLGN,
BAPI_MLGNX,
BAPI_MVKE,
BAPI_MVKEX
ENDLOOP. -
Unable to use SCAT to upload material master in ECC 6
HI
I am unable to use SCAT to upload material master in ECC 6,
an error is triggering
"Releases higher than 6.40 are not permitted
Message no. TT005
Diagnosis
With Web Application Server Release 6.40, you cannot create new automated CATT test cases. However, you can create manual CATT test cases"
canany body please help me to use SCAT
Sreeramyou have to read yourself:
http://help.sap.com/erp2005_ehp_04/helpdata/EN/1b/e81c3b84e65e7be10000000a11402f/frameset.htm
I certainly do not use SCAT or SECATT to load master data, especially not material master.
A material master has dynamic screens, based on the material type the view selection will be different, based on entries made in MRP view fields become hidden or mandatory. Such things canot be done with a static recording.
SAP provides batch input programs and BAPIs for material master load and additonally loading per IDOC in LSMW (which offers as well batch input and Bapi methods) -
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 NHello 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
Maybe you are looking for
-
Material BOM mass change error
Hi gurus, When doing mass change of BOM via tcode CS20, i'm getting below error result. The following messages were displayed: Material BOM 00016478 : Delete Item(s) 19
-
Hello, We are having trouble with our hp Scanjet 7000. When we scan colored documents, they turn out with a yellow tint and some thin black lines. However, when we scan in pure black and white, our documents come out in crisp black and white color.
-
my itune wont open.i got error itune librery.itl it cannot be read,becuase it was created by a newer version
-
Hello Mates, Am getting a very rare type problem while I implement the aCL on 3850 switch I do get hit matches when I put a log keyword in the ACL 102 SW#sh ip access-lists Extended IP access list 102 5 permit tcp 192.168.0.0.0 0.0.255.255 196.1
-
Revision: 4521 Author: [email protected] Date: 2009-01-14 06:01:28 -0800 (Wed, 14 Jan 2009) Log Message: Fix for - Override information missing for properties and methods in DITA XML output of ASDoc QE Notes: None Doc Notes: None Bugs: SDK-18681 test