Mass creation of Material

Any transaction that can help with masscreation of materials, I have to create around 20 000 new materials and need a mass creation function.

Hi
[http://www.saptechnical .com/Tutorials/LSMW/Longtext/Material.htm]
[http://www.sap-img.com/general/lsmw-steps-for-data-migration.htm]
Best way LSMW or BDC.
SAM
Edited by: Saminathan Gopalan on Jun 8, 2010 5:24 PM

Similar Messages

Mass creation of Material Master Records

Hi all,
I have to create 50.000 materials the first time and then, once a month, I have to manage the update of 50/100 materials.
What do you suggest ?
Direct input the first time and Idoc (Matmas) to manage the updating?
Thanks in advance
Bye

Hi
Use LSMW Direct Input Method/Manually code it to imitate LSMW Direct Input Method .
or
Use BAPI to Create Materials .
if u are going for BAPI u can use the following code.
REPORT Z_NEW_PROGRAM2 .
*TO CREATE MATERIAL USING BAPI.
               STRUCTURE DECLARATIONS                             *
TABLES: BAPIMATHEAD, "Headerdata
        BAPI_MARA,    "Clientdata
        BAPI_MARAX,   "Clientdatax
        BAPI_MARC,    "Plantdata
        BAPI_MARCX,   "Plantdatax
        BAPI_MAKT,    "Material description
        BAPI_MBEW,    "VALUATION DATA
        BAPI_MBEWX,
        BAPI_MARM,
        BAPI_MARMX,
        bapi_mean,
        BAPIRET2.     "Return messages
DATA:V_FILE TYPE STRING.   "input data file
DATA:
BEGIN OF LSMW_MATERIAL_MASTER,
    MATNR(018) TYPE C, "Material number
    MTART(004) TYPE C, "Material type
    MBRSH(001) TYPE C, "Industry sector
    WERKS(004) TYPE C, "Plant
    MAKTX(040) TYPE C, "Material description
    DISMM(002) TYPE C, "Extra Field Added In the Program as itsrequired
    MEINS(003) TYPE C, "Base unit of measure
    MATKL(009) TYPE C, "Material group
    SPART(002) TYPE C, "Division
    LABOR(003) TYPE C, "Lab/office
    PRDHA(018) TYPE C, "Product hierarchy
    MSTAE(002) TYPE C, "X-plant matl status
    MTPOS_MARA(004) TYPE C, "Gen item cat group
    BRGEW(017) TYPE C, "Gross weight
    GEWEI(003) TYPE C, "Weight unit
    NTGEW(017) TYPE C, "Net weight
    GROES(032) TYPE C, "Size/Dimensions
    MAGRV(004) TYPE C, "Matl grp pack matls
    BISMT(018) TYPE C, "Old material number
    WRKST(048) TYPE C, "Basic material
    PROFL(003) TYPE C, "DG indicator profile
    KZUMW(001) TYPE C, "Environmentally rlvt
    BSTME(003) TYPE C, "Order unit
    VABME(001) TYPE C,
    EKGRP(003) TYPE C, "Purchasing group
    XCHPF(001) TYPE C, "Batch management
    EKWSL(004) TYPE C, "Purchasing key value
    WEBAZ(003) TYPE C, "GR processing time
    MFRPN(040) TYPE C, "Manufacturer part number
    MFRNR(010) TYPE C, "Manufacturer number
    VPRSV(001) TYPE C, "Price control indicator
    STPRS(015) TYPE C, "Standard price
    BWPRH(014) TYPE C, "Commercial price1
    BKLAS(004) TYPE C, "Valuation class
    bwkey(004) type c,
END OF LSMW_MATERIAL_MASTER.
               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_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.
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.
*ELSE.
*DELETE IT_MATMASTER INDEX 1.
ENDIF.
               DATA POPULATIONS                                    *
LOOP AT IT_MATMASTER.
*HEADER DATA
BAPIMATHEAD-MATERIAL = IT_MATMASTER-MATNR.
BAPIMATHEAD-IND_SECTOR = IT_MATMASTER-Mbrsh.
BAPIMATHEAD-MATL_TYPE = IT_MATMASTER-Mtart.
BAPIMATHEAD-BASIC_VIEW = 'X'.
BAPIMATHEAD-PURCHASE_VIEW = 'X'.
BAPIMATHEAD-ACCOUNT_VIEW = 'X'.
*CLIENTDATA
BAPI_MARA-MATL_GROUP = IT_MATMASTER-MATKL.
BAPI_MARA-DIVISION = IT_MATMASTER-SPART.
BAPI_MARA-DSN_OFFICE = IT_MATMASTER-LABOR.
BAPI_MARA-PROD_HIER = IT_MATMASTER-PRDHA.
BAPI_MARA-PUR_STATUS = IT_MATMASTER-MSTAE.
BAPI_MARA-ITEM_CAT = IT_MATMASTER-MTPOS_MARA.
BAPI_MARA-NET_WEIGHT = IT_MATMASTER-NTGEW.
BAPI_MARA-PO_UNIT = 'KG'.
BAPI_MARA-UNIT_OF_WT_ISO = 'KG'.
BAPI_MARA-UNIT_OF_WT = 'KG'.
BAPI_MARA-PACK_VO_UN = 'KG'.
BAPI_MARA-BASE_UOM_ISO = 'KG'.
bapi_mara-size_dim = it_matmaster-groes.
BAPI_MARA-MAT_GRP_SM = IT_MATMASTER-MAGRV.
BAPI_MARA-OLD_MAT_NO = IT_MATMASTER-BISMT.
BAPI_MARA-BASE_UOM = IT_MATMASTER-MEINS.
BAPI_MARA-BASIC_MATL = IT_MATMASTER-WRKST.
BAPI_MARA-HAZMATPROF = IT_MATMASTER-PROFL.
BAPI_MARA-ENVT_RLVT = IT_MATMASTER-KZUMW.
BAPI_MARA-PO_UNIT = IT_MATMASTER-BSTME.
BAPI_MARA-VAR_ORD_UN = IT_MATMASTER-VABME.
BAPI_MARA-PUR_VALKEY = IT_MATMASTER-EKWSL.
BAPI_MARA-MANU_MAT = IT_MATMASTER-MFRPN.
BAPI_MARA-MFR_NO = IT_MATMASTER-MFRNR.
BAPI_MARAX-MATL_GROUP = 'X'.
BAPI_MARAX-DIVISION = 'X'.
BAPI_MARAX-DSN_OFFICE = 'X'.
BAPI_MARAX-PROD_HIER = 'X'.
BAPI_MARAX-PUR_STATUS = 'X'.
BAPI_MARAX-ITEM_CAT = 'X'.
BAPI_MARAX-NET_WEIGHT = 'X'.
BAPI_MARAX-UNIT_OF_WT = 'X'.
BAPI_MARAX-UNIT_OF_WT_ISO = 'X'.
bapi_maraX-size_dim = 'X'.
BAPI_MARAX-MAT_GRP_SM = 'X'.
BAPI_MARAX-OLD_MAT_NO = 'X'.
BAPI_MARAX-BASE_UOM = 'X'.
BAPI_MARAX-BASE_UOM_ISO = 'X'.
BAPI_MARAX-BASIC_MATL = 'X'.
BAPI_MARAX-MFR_NO = 'X'.
BAPI_MARAX-HAZMATPROF = 'X'.
BAPI_MARAX-ENVT_RLVT = 'X'.
BAPI_MARAX-PO_UNIT = 'X'.
BAPI_MARAX-PACK_VO_UN = 'X'.
BAPI_MARAX-VAR_ORD_UN = 'X'.
BAPI_MARAX-PUR_VALKEY = 'X'.
BAPI_MARAX-MANU_MAT = 'X'.
BAPI_MARAX-MFR_NO = 'X'.
*PLANT DATA
BAPI_MARC-PLANT = IT_MATMASTER-WERKS.
BAPI_MARC-PUR_GROUP = IT_MATMASTER-EKGRP.
BAPI_MARC-BATCH_MGMT = IT_MATMASTER-XCHPF.
BAPI_MARC-GR_PR_TIME = IT_MATMASTER-WEBAZ.
BAPI_MARCX-PLANT = IT_MATMASTER-WERKS.
BAPI_MARCX-PUR_GROUP = 'X'.
BAPI_MARCX-BATCH_MGMT = 'X'.
BAPI_MARCX-GR_PR_TIME = 'X'.
*VALUATION DATA
BAPI_MBEW-PRICE_CTRL = IT_MATMASTER-VPRSV.
BAPI_MBEW-STD_PRICE = IT_MATMASTER-STPRS.
BAPI_MBEW-COMMPRICE1 = IT_MATMASTER-BWPRH.
BAPI_MBEW-VAL_AREA = IT_MATMASTER-BWKEY.
BAPI_MBEW-VAL_CLASS = IT_MATMASTER-BKLAS.
BAPI_MBEWX-PRICE_CTRL = 'X'.
BAPI_MBEWX-STD_PRICE = 'X'.
BAPI_MBEWX-COMMPRICE1 = 'X'.
BAPI_MBEWX-VAL_AREA = IT_MATMASTER-BWKEY.
BAPI_MBEWX-VAL_CLASS = 'X'.
IT_MATERIALDESC-LANGU = 'EN'.
IT_MATERIALDESC-MATL_DESC = IT_MATMASTER-MAKTX.
append IT_materialdesc.
IT_UOM-GROSS_WT = IT_MATMASTER-BRGEW.
IT_UOM-ALT_UNIT = 'KG'.
IT_UOM-ALT_UNIT_ISO = 'KG'.
    IT_UOM-UNIT_OF_WT = IT_MATMASTER-GEWEI.
    APPEND IT_UOM.
IT_UOMX-GROSS_WT = 'X'.
IT_UOMX-ALT_UNIT = 'KG'.
IT_UOMX-ALT_UNIT_ISO = 'KG'.
IT_UOMX-UNIT_OF_WT = 'X'.
APPEND IT_UOMX.
it_mean-unit = 'KD3'.
append it_mean.
it_mltx-langu = 'E'.
it_mltx-text_name = it_matmaster-matnr.
APPEND IT_MLTX.
CALL FUNCTION 'BAPI_MATERIAL_SAVEDATA'
    EXPORTING
      headdata                   = BAPIMATHEAD
      CLIENTDATA                 = BAPI_MARA
      CLIENTDATAX                = BAPI_MARAx
     PLANTDATA                  = BAPI_MARc
     PLANTDATAX                 = BAPI_MARcx
    FORECASTPARAMETERS         =
    FORECASTPARAMETERSX        =
    PLANNINGDATA               =
    PLANNINGDATAX              =
    STORAGELOCATIONDATA        =
    STORAGELOCATIONDATAX       =
     VALUATIONDATA              = BAPI_MBEW
     VALUATIONDATAX             = BAPI_MBEWX
    WAREHOUSENUMBERDATA        =
    WAREHOUSENUMBERDATAX       =
    SALESDATA                  =
    SALESDATAX                 =
    STORAGETYPEDATA            =
    STORAGETYPEDATAX           =
    FLAG_ONLINE                = ' '
    FLAG_CAD_CALL              = ' '
   IMPORTING
     RETURN                     = IT_RETURN
   TABLES
     MATERIALDESCRIPTION        = IT_MATERIALDESC
     UNITSOFMEASURE             = IT_UOM
     UNITSOFMEASUREX            = IT_UOMX
     INTERNATIONALARTNOS        = it_mean
    MATERIALLONGTEXT           = IT_MLTX
    TAXCLASSIFICATIONS         =
    RETURNMESSAGES             =
    PRTDATA                    =
    PRTDATAX                   =
    EXTENSIONIN                =
    EXTENSIONINX               =
read table it_return with key TYPE = 'S'.
if sy-subrc = 0.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
    WAIT          =
IMPORTING
    RETURN        =
*else.
*CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'
IMPORTING
RETURN        =
endif.
WRITE:/    IT_RETURN-TYPE,
        2   IT_RETURN-ID,
        22 IT_RETURN-NUMBER,
        25 IT_RETURN-MESSAGE.
           IT_RETURN-LOG_NO,
           IT_RETURN-LOG_MSG_NO,
           IT_RETURN-MESSAGE_V1,
           IT_RETURN-MESSAGE_V2,
           IT_RETURN-MESSAGE_V3,
           IT_RETURN-MESSAGE_V4,
           IT_RETURN-PARAMETER,
           IT_RETURN-ROW,
           IT_RETURN-FIELD,
           IT_RETURN-SYSTEM.
ENDLOOP.
This will Create Mass .

Mass Creation of Material Group Purchase info record

Dear All
Currently we are developing a custom transaction in SAP to mass upload Purchase Info records from a flat file (excel)
We are using the standard Function Module ME_POST_INFORECORD to create the PIR s
We use two different number ranges for Material and Material Group PIR s. This is set up already in SPRO>MM>PIR>Define Number Ranges
Purchasing info record for stock material (Group - IL ) have a number range X
Purchasing info record for material group (non-stock mat.)(Grpup -IN) have number range Y
So when we create a Material PIR manually in SAP it picks X number range and Y number range for Material Group PIR
But when we create Material Groups PIR via the new custom transaction it creates PIR s with Number range X.
Upon checking understood that the standard FM ME_POST_INFORECORD is always defaulting the Number Range Group as IL internally . Seems like a harcoding done by SAP
Wanted to know
- Is there any another FM we should consider while creating Material Group PIR s. Any other Function module provided by SAP for that ?
- Or what can be other way to resolve this ?
Please let me know your views on this.
Regards
Shyam

Hi,
For mass upload from flat files you can consider LSMW with different options e.g. IDoc:
Message Type INFREC
Basic Type INFRECMASS01
or simply via recording of transaction (this should be using exactly the same NR as you have when doing this manually).
Regards,
Tomek

Reg:Bapi for mass creation of production order/confirmation

Dear Experts,
I wanted to know with the following BAPI is it possible to create Multiple production orders for different semifinshed Materials along with material availability check and other functions similar to CO01 transaction.
I knew there are standard transactions for mass confirmation for production orders. But i need a confirmation on this BAPI . As i am planning to go-ahed with ,mass creation of production order creation / Order confirmation in single custom transaction.Need back flush activity even supported.
BAPI_PRODORD_CREATE to create the orders.
BAPI_PRODORD_RELEASE to release the orders.
BAPI_PRODORDCONF_GET_TT_PROP to get the default data for the confirmation.
BAPI_PRODORDCONF_CREATE_TT to ost the confirmation of production order.
Along with this BAPI do i need to commit any other BAPI to carry out back flush for components.
Need your suggestions to take it further.
Regards,
Daya.

Dear SAP Daya
If the issue has been solved, please close this thread.
You have already mentioned that the issue has been resolved, thefore, you should not ask for help on another thread before closing this one, as it looks like you are trying to force people to answer your threads.
Users are always trying to answer as many threads as possible on good will we don't need this kind of "incentive".
Please read carefully the The SCN Rules of Engagement, especially point 8:
Be responsive. If an SCN member has answered your question, please mark the answer as "helpful” or “correct”. Mark the discussion as “answered,” so that other members can find the answers more easily
Also, I checked your old threads and I could observe that there is only one closed. Please review your old threads and close those already solved.
BR
Caetano

Mass creation of planned order

Hello,
is there a way to mass creat a planned order for a finished product? having same FG mat, plant and prod version.
Thanks

Dear
1.Goto MD61 with User parameters like Plant , Requirement type , Version and Planning Date .Then Select the Material Radio Buttion with FG item code .
2.Enter the FG qty as required in each month as demand
3.GotO MD02-Single Item ,Multi Level with indicator : NETCH , 2,1,3,3,2 and Execute the MRP to create the Planned order for FG
4.Check the result in MD04
There is no SAP Standard Traction to Mass creation of Planned Order .That is possible in Demand Creation and MRP run .
Regards
JH

Quality info record mass creation

Hello Guys,
Can we able to do mass creation of quality info records thru QI06 ? I want to load bunch of QIR as a manual load.
I tried using qi06 in add option but I am getting a warning message that QIR is not changed.
Is that only we can change it ? Pls help.
Akash

Hi
For QI06:
Read follwoing
You can use this program to make mass changes to quality information records. When adding records, you can enter one or several materials. As a rule, the only materials used for processing are those for which QM in Procurement is active in the material master and a vendor release or quality assurance agreement is required by the control key.
You can also select the materials using the material class.
You can enter one or more vendors, for whom a quality information record is to be created.
Using the selection criterion 'Only for purchasing info records', you can create quality information records for all possible material-vendor combinations, provided that purchasing information records already exist for these combinations.
That means first of all you must enter Procurement key in QM view of that Material
Second if you select multiple vendor for a material or maultiple materials with single Vendor.
if you execute this then You will get the list of all possible vendor material combination for which QI can be maintained.
by selecting line you can save them.
The quality info records printed in the list have a traffic light indicator which denotes the following:
Green light: - All data is O.K.
Yellow light: - Ordered quantity is greater than released quantity
        - There is no quality assurance agreement
        - Lock function is active
        - Validity period of QM system has expired
Red light:    - Deletion flag is set
You can select the "Set deletion flag"
function using the menu
Regards
Sujit

What are the mandatory fields while creation of material master in differen

what are the mandatory fields while creation of material master in different views?

Hi Gopi,
This is purely depends on the function configuration, which would be done MM consultants. Kindly check with them.
thanks & regards
Kishore Kumar Maram

MASS CREATION OF INFOOBJECTS IN BI 7.0

Hello Gurus,
Here is my scenario:
we have more than 100 new Z fields in R/3 (Tables: KONV, KONP, VBRP) and we are populating those. We maintained the Datasources with that fields. Now we need to develop new infoobjects in BW for those Z fields. Is there any possible way for mass creation of infoobjects.
I searched about this, but most of them were used only for 3.5 data source.(eg: CTBW_META - transaction for mass creation of infoobjects in bw 3.5)
Please anyone help me in solving this !
Thanks in advance .

Hi,
One option I thought of, but never applied in practice. Create an excel with all the field related information in the structure of table,
RSDIOBJ Directory of all InfoObjects
RSDCHABAS Basic Characteristics (for Characteristics,Time Characteristics, and Units)
*RSKYF Key Figures
RSDTIM Time Characteristics
RSDUNI Units*
And upload this table with the flat using function module etc.
But then you would need to update below tables to with relevant details.
RSDIOBJT Texts of InfoObjects
RSDIOBJ Directory of all InfoObjects
RSDIOBJT Texts of InfoObjects
RSDATRNAV Navigation Attributes
RSDATRNAVT Navigation Attributes
RSDBCHATR Master Data Attributes
RSDCHABAS Basic Characteristics (for Characteristics,Time Characteristics, and Units)
RSDCHA Characteristics Catalog
RSDDPA Data Package Characteristic
RSDIOBJCMP Dependencies of InfoObjects
RSKYF Key Figures
RSDTIM Time Characteristics
RSDUNI Units
Edited by: Parth Kulkarni on Jun 22, 2011 4:56 PM

Automatic creation of Material Master at the time raising the PO !!!

Hello All,
I am stuck in a scenario of our client which should be implemented (or mapped) in SAP.
Scenario: At the time of creating the PO (in there legacy system -in house developed) they can choose the items from the existing master data or/and they can also add a new item (which is not present in the master data records at the time of creating the PO).
Now as soon as the system realise that a new item is inserted into the PO, it will create that item record automatically in the backend (database) and the master data will be present from there on.
The items they are dealing with are all fashion accessories and they generate order on the following basis:
1. Demand of particular item in market.
2. List of items provided by the vendor.
3. Based on the requirement in there outlets.
So for them its very difficult to fix there master data records, as it can be changed daily or monthly as per the market conditions. At the same time every time they order, its almost around 100 different items (some time 80 of them are new) in a single PO so they cannot create 80 records manually each time.
These items are not consumable material so obviously they are maintaining the stock for them. They are also not going to use IS Retail.
I am not at all sure how can we map this particular practice in SAP, it would be really appreciated if any one could help me on this problem.
Please let me know if you need any other details from my side.

Hi,
As you have two different systems one in house developed and another SAP, and the PO creation part starts from Legasy system which creats the PO in SAP, you can do some development as per below
1: While Passing the details from legasy to SAP, use two columns in legasy one will contain the Material Code of ECC (for laready exist material ) and another for deescription of material.
2: In case material is new for which there is no material master in ECC pass only description from legasy systems.
3:While getting triggred from Legasy to ECC to create the PO, first check whehter all the material code exists or not in ECC.
4:If some material are not created (only description present) for those material first create the Material Code using BAPI 'BAPI_MATERIAL_SAVEDATA'.
5: Aftre creation of Material code create the PO using BAPI ' BAPI_PO_CREATE1'.
6:For the new created material , trnasfre the master record from ECC to Legasy systemso that next time user can see that material in your legasy system.
Regards,
Zafar

Creation of material master

Dear all,
While entering of MM01, MM02, MM03 T codes, The system showing the error message - "Record Y1 01 does not exist in Table T133A" - for this what do I do, Plz suggest.
reg
Vishnu.Ch

Hi Madhu,
Thanks for your reply. But, I have one more doubt. For non stock materials, we
will specify the cost centre and G/L account at the time of creation of Purchase order. Then, do we have to specify the valuation class at the time of creation of
Material Master since there is no automatic account determination?
Regards
Yoga

MARA-GEWEI is not overtaken during creation of material from cdesk

Hi, we work in ENV SAP R3 4.71 and create material in background out from
cdesk.
Therefore we defined in the customizing of CAD Desktop that in case of
creation of material MARA-GEWEI determination type = constant and
determination parameter is "ST" for "piece"
Every other parameter works fine during creation of material ==> as soon as
we fill a weight into the corresponding fields SAP tells us a message
"ENTER the unit of weight for the net weight" ==> if you press "continue action then" SAP ends creation of material an nothing happens....
ANY ideas?
(will enter this message for sure as well into the oss....)

Hi Gerhard,
have u put
EXP_MARA-BRGEW           Gross weight
EXP_MARA-NTGEW            Net weight
from Inv side in config...
Also check in cdesk_cus under create material
<b>Base Unit of Measure               Constant     ST
Net Weight               File Attribute     Physical_Properties_MassValue</b>
hope this helps

Mass creation of PO from excel sheet

Dear all
Kindly let me know the method for Mass creation of PO from excel sheet
Regards
Chandra mohan

Hi, check these links....
/people/hema.rao/blog/2006/09/14/lsmw--step-by-step
http://www.sap-img.com/sap-data-migration.htm
get more from first thread.........

Creation of Material Master for a material with Material Type NLAG

Hello Sirs,
I have to create a material which will be consumed directly. I would use the
material type NLAG (Non stock material). If I create a material with this material type, will it contain an Accounting view where in I can maintain the price of the
material? If it contains an Accounting view, which type of Price control should be
used (Moving average or Standard)? Further, can we maintain an info record for
a material with material type NLAG?How the price updation happens?
Regards
Yoga

Hi Madhu,
Thanks for your reply. But, I have one more doubt. For non stock materials, we
will specify the cost centre and G/L account at the time of creation of Purchase order. Then, do we have to specify the valuation class at the time of creation of
Material Master since there is no automatic account determination?
Regards
Yoga

Creation of material Documents for RMPM adjustments using BAPI

Hi
can any one help me Creation of material Documents for RMPM adjustments using BAPI...
i should be grateful to you...
advance thank you
with regards
venkat

You can check MB_CREATE_GOODS_MOVEMENT which has mkpf as inporting parameter.

Mass creation of common folders for different user groups

Hello Experts,
We are using Portal 7.0 SP12 and we have 10 different user groups created in Portal.
Based on this group structure, we need to create two common folders in each of the user's personnel documents in KM.
Is there is any way to achieve this kind of requirement ?
Can we do mass creation of these two common folders which will be assigned to all of the groups. This needs to be done in user's personnel documents and not in Public documents.
Any help in this context would be highly appreciated. points assured.
Thanks in advance,
Anil Kumar.

For every user a folder is created in userhome. One approach is to capture this folder creation event and create the folder structure you need. You need to develop a portal service which will listen to events from userhome repository.
1. Capture folder creation event for user home
2. Create the folder structure you want in this event handler
Check this documentation on how to do this.
https://media.sdn.sap.com/html/submitted_docs/nw_kmc/howto/rf/client_api/rf_client_api.html
Regards,
Prasanna Krishnamurthy

Mass creation of Material

Similar Messages

Maybe you are looking for