Material Creation without MM01

Dear All,
           My requirement is Matearial should be created with all views with out using the MM01.Material type should be 'SPARES'.
   I already used 'BAPI_MATERIAL_SAVEDATA' for material extension. in this I passed Refrence material number as material number. it is working fine but now I want to create material with out using the referece material number.
Will 'BAPI_STANDARDMATERIAL_CREATE'   allow me to create material with All VIEWS.
Pls provide me the solution.
regards,
Prashanth Maturu.

Hello
You can fetch the material number(internal) using MATERIAL_NUMBER_GET_NEXT and then pass it on to BAPI_MATERIAL_SAVEDATA. Hope this fulfills your requirement.
Avishek

Similar Messages

Material creation without specifying plant

can i create a material without specifying a plant or storage location?is it possible.?what are differnt types of stocks in gr.

Dear Kunal,
You would need to give plant for plant relevant views. However, you would not need to give plant for views like Basic Data which is valid for entire organization.
Different Stocks:
1. Unrestricted Use of Stock
2. Quality Inspection Stock
3. Blocked Stock
Special stocks and special procurement types are divided into the following areas:
· Consignment
· Subcontracting
· Stock transfer using stock transport order
· Third-party processing
· Returnable transport packaging
· Pipeline handling
· Sales order stock
· Project stock
Regards,
Naveen.

Material creation without user intervention

i have to create a material without user intervention. i am using BAPI_MATERIAL_SAVEDATA for this. it is not showing any error. but the return is having the message 'No description found'. how to transfer the description to this bapi.
this is the code i am trying:
DATA: mnum like zmara01-mno,
       mat_data like BAPIMATHEAD,
       plantx_data like BAPI_MARCX,
       salesx_data like BAPI_MVKEX,
       sale_data like bapi_mvke,
       plant_data like bapi_marc,
       mate_data like bapi_makt,
       E1BP_MAKT like E1BP_MAKT,
       cli_data like bapi_mara.
DATA: E_RETURN LIKE BAPIRET2.
data: MATERIALDESCRIPTION like BAPI_MAKT
                  occurs 0 with header line.
*data: m(18) type c.
CALL FUNCTION 'NUMBER_GET_NEXT'
        EXPORTING
          NR_RANGE_NR                  = '01'
          OBJECT                       = 'ZMNUMBER'
         QUANTITY                      = '1'
       IMPORTING
         NUMBER                        = mnum.
message i003(zmsg) with mnum.
mat_data-material = mnum.
mat_data-ind_sector = 'I'.
mat_data-matl_type = 'DIEN'.
mat_data-basic_view = 'X'.
cli_data-base_uom = 'EA'.
cli_data-base_uom_iso = 'X'.
sale_data-sales_org = 'EISO'.
sale_data-distr_chan = 'SR'.
salesx_data-sales_org = 'EISO'.
salesx_data-distr_chan = 'SR'.
plant_data-plant = 'EIHO'.
plantx_data-plant = 'EIHO'.
CALL FUNCTION 'BAPI_MATERIAL_SAVEDATA'
EXPORTING
    HEADDATA                   = mat_data
   CLIENTDATA                 = cli_data
CLIENTDATAX                =
   PLANTDATA                  = plant_data
   PLANTDATAX                 = plantx_data
FORECASTPARAMETERS         =
FORECASTPARAMETERSX        =
PLANNINGDATA               =
PLANNINGDATAX              =
STORAGELOCATIONDATA        =
STORAGELOCATIONDATAX       =
VALUATIONDATA              =
VALUATIONDATAX             =
WAREHOUSENUMBERDATA        =
WAREHOUSENUMBERDATAX       =
   SALESDATA                  = sale_data
   SALESDATAX                 = salesx_data
STORAGETYPEDATA            =
STORAGETYPEDATAX           =
FLAG_ONLINE                = ' '
FLAG_CAD_CALL              = ' '
NO_DEQUEUE                 = ' '
IMPORTING
   RETURN                     = E_RETURN
TABLES
   MATERIALDESCRIPTION        = MATERIALDESCRIPTION
UNITSOFMEASURE             =
UNITSOFMEASUREX            =
INTERNATIONALARTNOS        =
MATERIALLONGTEXT           =
TAXCLASSIFICATIONS         =
RETURNMESSAGES             =
PRTDATA                    =
PRTDATAX                   =
EXTENSIONIN                =
EXTENSIONINX               =
loop at materialdescription.
message I004(I) with materialdescription-matl_desc.
endloop .
MESSAGE I004(I) WITH E_RETURN-TYPE.
    if sy-subrc = 0.
     message i005(zmsg).
    elseif sy-subrc <> 0.
     message e006(zmsg).
    endif.
i am trying to give direct entries to test it . please help in this issue immediately.

Hi dear,
welcome on board!
If you want an answer immediately I think you have to post your question in a more appropriate forum...
take a look to https://www.sdn.sap.com/sdn/collaboration.sdn and choose one of the available forums !
Good luck!
Roberto

Prob in material creation in mm01

Hi All,
I am facing problem while i am creating material in MM01 transaction.
my material name was created along with that material type,for example
if i created material with name as mat1 and material type is coupons.
then my material was created as coupmat1.
why it happening like this.......
Thanks$ Regards,
raji.

Check the code in related user exits for MM01 which are active... but best will be to ask your functional Person about it as this must be your clients requirement.

Screen Exit for MM01 Material Creation

Hi,
The requirement is to add 2 new field in the Material Creation transaction (MM01) in the General Plant / Storage Location View.
I was trying to find the Screen exit in the MGA Package but there was no screen exit for material. So, i tried by SPRO- IMG, iam able to attach my designed screen and its viewable in MM01 but the data is not being updated in the relevant table for the custom fields (The custom fields are appended in the MARC table).
So, can you please help me about the coding part for the updation of the custom field data.
Thanx

Hi,
Check these:
MGA00001 - Material Master (Industry): Checks
and Enhancements
MGA00002 - Material Master (Industry): Number
Assignment
MGA00003 - Material Master (Industry and
Retail): Number Display
Check with 'BADI_MATERIAL_REF'
Refer
http://www.****************/Tutorials/ExitsBADIs/MM/MM01.htm
https://forums.sdn.sap.com/click.jspa?searchID=7217830&messageID=3313524
Regards
Kiran

Blocking material creation

I have ea requirement wherein I must block the material creation (transaction mm01) daily when my program runs.
How do I achieve this?
Thanks.

You could use BDC to achieve this. The quicker solution is to change the corresponding entry in table TSTC: set field CINFO to "20" to lock the transaction.
Regards,
John.

SRM Product / Material creation - Data flow to SAP MDM

Dear SAP friends,
I need your help with 2 issues. Thanks in advance for your collaboration.
Our client needs to create products and make them available to purchase almost immediately.
The scenario we had working for the last 2 years was: product creation in SRM (fields: short description / product category / measure unit), that would then be sent to SAP MDM for data enrichment, through BBP_CCM_TRANSFER_CATALOG (JOB running every 1 minute). This solution worked well for the last 2 years.
Recently, we are having some problems with this job. We noticed that, sometimes SRM doesn´t send the new products to MDM, and we think it´s a report performance problem. The report doesn´t maintain is normal behavior when executed every 1 minute.
SAP advice is to only run this report once a day. That would obviously require having a minimum time frame of 1 day between product creation and its availability (purchase), which isn´t acceptable in this client business model.
Question 1: Did anyone have a client with similar requirement? What was the implemented solution?
Because of report performance problems, we are running it (BBP_CCM_TRANSFER_CATALOG) every 5 minutes. It happens that sometimes, more than one catalog manager creates products in that time frame, and MDIS when importing the products to MDM, creates one unique workflow JOB making it impossible to assign it to both catalog managers for enrichment.
Question 2: How can we ensure that SRM sends only one product per xml files sent to XI / PI ? Or, perhaps, ensure that XI / PI splits the xml file sent from SRM into several files with one product each.
Thank you very much for your help in advance,
Best Regards,
João S. Carvalho

Hi meka
In product costing values flows as follows;
In product cost calculation raw material prices are costed which comes from material master in MM01
Product operations: i.e material BOM and master receipe or routings from PP module.From PP module operation costs comes in product costing.
In CO module: In Tcode KP26 we maintain activity\cost center planning for activities like machine hours, set up hours, labour hours etc.Here we define plan quantity and plan prices.
In Cost Sheet (KZS2) we maintain base cost elements & overheads and While order creation we calculate planned cost of that particular material.and then check the variances after getting actual cost of product.
Hope this will help you and if found useful assign points.
Let me know if you need more information.
Regards
Nilesh.

Material creation process in SRM-MDM

Dear All,
I am new to SRM. Please correct me about material creation procedure in SRM if I am wrong:
Normally in classic/extended classic scenario, material first created in MM and then it replicated to SRM. Base on configuration setting for number range, system either create the product ID same as material number number in SRM when it replicated into SRM. In final steps, the product information will upload into MDM either XI integration or manually via excel upload.
My question:
+ Is it possible to automatic create product without XI via T.Code - MDMGX in MDM.
+ If the replicated product ID of SRM is different then MM material number, which number we should consider for creating product
MDM.
Thanks in advance.
BR
Jennifer

Hi Jennifer,
Answer1) You can only replicate Product Groups, Currencies and Unit of Measures through t-code MDMGX. XI/PI is required for Contract and Product Catalogs.
Answer 2) If the replicated product ID of SRM is different then MM material number, you should enter MM material number and in External Web Service Configuration for that internal catalog, uncheck "Do not check Product" indicator so that SRM will not check the Product ID and when item goes to backend system, it will have correct MM material number.
Thanks,
Anshuk Saxena

Error in pipeline material creation

hi,
we want to create one pipeline material as per our new requirement for showing gas consumption.during material creation with mat type PIPE, it's showing an error:The field Profit Center is defined as a required field; it does not contain
an entry.
Procedure
If the field is the material group or unit of weight, and the field is not ready for input, check whether the material is locked. If it is locked, you cannot extend the Purchasing view or the Sales view. If either of these views needs to be extended, the material must first be unlocked. This can be done only by a user with special authorization.
thanx,
sheetal

Hi
In your client if Profit center accounting(PCA) is activated ,then you need to maintain the Profit center for the material.
Option 1: goto OMS2, got details of pipleine material & select the Costing View of the material.
Now goto MM01 in creation of pipeline material & maintain the profit center in Cotsing 1 View.
Deactivating the field from mandatory to optional will not serve your purpose as PCA will get affected.
Thanks & Regards
Kishore

Is it possible to Create Material Master without Profit Center ?

Hai,
      1) Is it possible to Create Material Master without Profit Center ?
      2) How SAP System Validate Profit Center in material master. ? is it material Type wise ?
      3) Whether PO Order Creation,GRN & MIRO Possible for those material Master without Profit Center.?
Kindly Explain me clearly..
Thanks & Regards,
Swetha

Hi,
Profit center is at the plant level.
You can create material master even with out a profit center.This field will be there in the costing view and and general sales/plant data.
while creation of the materila master if do not select these views system will not ask for that.Normally it is pertaining to the costing analysis.
A profit center manager is held accountable for both revenues, and costs (expenses), and therefore, profits. What this means in terms of managerial responsibilities is that the manager has to drive the sales revenue generating activities which leads to cash inflows and at the same time control the cost (cash outflows) causing activities. This makes the profit center management more challenging than cost centre management. Profit center management is equivalent to running an independent business because a profit center business unit or department is treated as a distinct entity enabling revenues and expenses to be determined and its profitability to be measured.
Business organizations may be organized in terms of profit centers where the profit center's revenues and expenses are held separate from the main company's in order to determine their profitability. Usually different profit centers are separated for accounting purposes so that the management can follow how much profit each center makes and compare their relative efficiency and profit. Examples of typical profit centers are a store, a sales organization and a consulting organization whose profitability can be measured.
For more info,please refer
http://help.sap.com/erp2005_ehp_04/helpdata/EN/cc/36428094f311d2b47a006094b9b0a5/frameset.htm,
Regards,

Process flow of material creation

hi sap gurus,myself rekha
i want to know the process flow of material creation-FERT

Check below link .You have to use transaction MM01 to create material.
https://www.google.com.au/search?q=process+flow+for+material+creation&oq=process+flow+for+material+creation&aqs=chrome..69i57.9710j0j8&sourceid=chrome&espv=210&es_sm=122&ie=UTF-8#q=process+flow+for+material+creation%2Bsap

Key performance indicators (KPI) for material creation

Dear all,
I need to define some Key Performance Indicators (KPI’s) to measure the data quality during the material creation (MM01) process. The objective is to get concrete statistics about data quality/accuracy for fields related to material from all views created with MM01 (basic data, classification, unit of measure...).
I would like to get your expertise on how to measure these KPI’s : which transactions, table (...) to use ?
I have already few ideas :
-Table CDHDR
-Transaction MM04
-Create “checkpoints“ into the workflow for material creation (ZWF01)
Do you have any other idea in mind?
I am open for all advices: transaction, table, process, approach…
Thanks in advance for your help !

I have a few ideas, but the accuracy of the master data is based on your system config.
Some things that are helpful in most of the cases:
- If material type is HAWA (trading goods) your procurement indicator should always be External procurement (check those for other material types if you have it uniformed). You can also check purchasing group based on material type if you have it distinct by material type.
- Check if sales views are opened in all org.levels
- Check if storage loc.views are opened for all SLoc
All in all, you need to have a link of two or more data in material master to be able to check it in some way automatically, otherwise you won't be able to determine if the data is correct or not.
E.g. How would you every know if lot size of 120.000 PCS is OK or not for a specific material or if you need to assign a specific purchasing group to your material.
You know the logic behind your material master data best so you can create the best rules to check for your KPI.
Regards.

Can we mandatory Quality Management Field at time of Material Creation

Hi Gurus,
I need to Control Material Creation for every item, if we create materials in some case our user forget for tick the Quality Management .
Is it any T-code or any customisation for control the same.
thanks in advance.
Ajit

Hi Ajit,
In MM01..After entering industry sector and material type,,,when you click on enter...A window for Views will popup...
Now You select your all views including your quality view...Now you check the check box for "view selection only on request"...Now you click on default values....
Now when ever user will create material automatically Quality view will be selected.....and it wont show the views popup again..
Cheers!!!
Utsav

Problem with restriction of material creation

I have a problem regarding this code logic mention below
itz for checking the plant and profit center should be same . restrict by a message at the time of material creation .
now when we create a Alfanumeric plant and the profit center and we enter the same this message is stil comming and itz restrict the material creation .
can anybody please help me out for change the logic of this code .
break-point.
3       CALL FUNCTION 'CONVERSION_EXIT_ALPHA_OUTPUT'
4         EXPORTING
5           input         = MARC-PRCTR
6        IMPORTING
7          OUTPUT        = MARC-PRCTR
8                 .
9     *break-point.
10       if sy-tcode eq 'MM01' or sy-tcode eq 'MM02'.
11       if RMMG1-WERKS <> MARC-PRCTR and MARC-PRCTR is not initial.
12       message id 'ZS' type 'S' number 057.
13       endif.
14       endif.
15       IF ( sy-dynnr(1) = '4' OR sy-dynnr = '0060' )             "note 754457
16          AND NOT c_set IS INITIAL AND
17           ( x_win NE sy-srows OR y_win NE sy-scols )
18           and ok-code is initial and c_classification IS INITIAL.
19         bildflag = x.
20       ENDIF.

Hi,
Aren't you missing an = in the following line...
11 if RMMG1-WERKS MARC-PRCTR and MARC-PRCTR is not initial.
Shouldn't it read as follows?
11 if RMMG1-WERKS = MARC-PRCTR and MARC-PRCTR is not initial.
Regards, Andy

How to speed up fast refresh of materialized view without primary key

Thought I'd share this info, as I couldn't find anything on here to help me diagnose the issue:
I had a materialized view that was taking longer to perform a fast refresh than it took to perform a complete refresh. My mview had no primary key, as the base table had no primary key.
I created a trace file for the session and saw references to a column M_ROW$$ in my mview. Nowhere in the data dictionary could I find a reference to the m_row$$ column in my mview, but apparently it exists and is created automatically. After creating the index below, the fast refresh took 6 minutes to add 500k rows to the materialized view. (versus 4+ hours without the index) When I looked in the trace file, I noticed that for each row in the mview log, it first tries to update the mview with an UPDATE statement, then it performs an insert of the new data. Seems like it should be able to determine whether to perform an update or insert based on the DMLTYPE$$ column of the mview log. What was killing my performance was the UPDATE phase. Since I had no primary key on the mview, and no index on the m_row$$ column, the UPDATE phase was performing a full table scan of my mview for every row in the mview log. I was expecting it to be smart enough to only perform inserts, as the only transactions against the base table were inserts.
In summary: If you have a materialized view without a primary key, create an index on the m_row$$ column of the mview, even though no such column displays in the data dictionary.
ex:
CREATE MATERIALIZED VIEW mv_minidrr ...
CREATE INDEX pk_mv_minidrr ON mv_minidrr(m_row$$) ...

Well, there indeed is a column called M_ROW$$
Your MLOG$_EMP is nothing but the materialized view log on the base table.
SQL> create materialized view log on emp with rowid ;
Materialized view log created.
SQL> create materialized view emp_mview refresh fast on demand with rowid as select * from emp ;
Materialized view created.
SQL> desc mlog$_emp
Name                                                  Null?    Type
M_ROW$$                                                        VARCHAR2(255)
SNAPTIME$$                                                     DATE
DMLTYPE$$                                                      VARCHAR2(1)
OLD_NEW$$                                                      VARCHAR2(1)
CHANGE_VECTOR$$                                                RAW(255)
SQL> select table_name, column_name from user_tab_columns where column_name = 'M_ROW$$' ;
TABLE_NAME                     COLUMN_NAME
MLOG$_EMP                      M_ROW$$
1 row selected.
SQL>

Material Creation without MM01

Similar Messages

Maybe you are looking for