Copy of Material Master charac. values to the batch classif. in GR for PO

Dear gurus,
Could you please help me with the following issue. I have a material managed in batches, and it has a classification type 023 in material master. I fill one chaacteristic of this classification with some value. Now I want this value to be copied to the batch classification during the creation of new batch while making GR to production order.
Is it possible?

Hi Nikolaj,
What I am understand your requirement is like,
You want to fetch the value of Characteristic maintain in Batch class in Material master to the Batches, correct?
But my Friend if you maintain value of characteristic in Batch Class in material master then it will works as a validation.
For Example,
Suppose your Characteristic is Colour and in Material Master Batch classification view you have maintain value as Red.Then system will not allow you any other colour in Batches.You will find that value in Drop Down list.
Regards,
Dhaval

Similar Messages

Net Price - direct copy from material master into purchase order

When purchase requistions are converted to purchase orders, currently we are maintaining Net Price manually
before saving the purchase order. Is there a way where the standard price is copied from the material master {Accouting view} into the purchase order directly without manual entry
If yes, Please advice

Hi,
1. Go to SPRO > MM > Purchasing > Authorization Management > Define Function Authorizations for Buyers > Function Authorizations: Purchase Order > Here "New Entries" and define Function Authorization Key as "01" and give description.
OR use T. Code - OMET
Here under "General parameters" subscreen, cctivate "Adopt PO Price" indicator and select "Enter conditions"
In "Possible ref. objects", select "W/o reference" otherwise reference documents (for e.g. PR, RFQ, etc...) for PO creation will become mandatory.
2. Now go to SU01 > Enter User ID > Parameters Tab > Here for Parameter ID EFB i.e. Function Authorization: Purchase Order, maintain value "01" and check in PO, PR will become mandatory for that user.
3. Now during creation of PR in ME51N, under "Valuation" Tab, you will get option for PO Price Adoption as Net or Gross. Select as per your requirement and it will copy Price to PO.

Material Master Default Values

Dear All
Whenever we create a material, we want to have the same value as default for a particular field in one of the Material master views.
Is this possible and how can it be done?
Regards
Hary

Hi Hary,
Discuss with an ABAP consultant & find the user enhancement for the material master screen & then get the user exits for the fields.
Give the list of fields you need to have default values, then it can coded in the include program.
To find a user exit use T.code SMOD.
For further coding use T.code CMOD.
Regards,
Senthilkumar SD

Need a bapi r fn module to update the batch classification in the bom

hi,
iam working a exit : exit_saplcoml_001.This exit is for material quantity calculation.the materials are currently classified in the material master under the classification tab.Ans due to this the classification becomes cross plant.
To make the material classification plant specific i have decided to maintain the classification in the batch classification of bom.i am finding for a function module r a bapi to update the calculated values in to the batch classification characteristics.please help mi with this.
thanks.

Hi
U can try to use BAPI_MATERIAL_SAVEREPLICA
Max

What is the AC classification (1200 - 3200) for the AirPort Extreme?

WHat is the AC classification (1200 - 3200) for the AirPort Extreme?

Not sure that I understand your question.
The AirPort Extreme does not support AC3200 if that is what you are asking.
1300 Mbps is the theoretical maximum speed of an "ac" wireless connection on the AirPorts.

Material Master Extension to all the plants of same type

Hi
In the given scenario, we have almost 200 plants where same materials are required , now when we create material master using Tcode MM01 we want to extend this material master to all the plants of same type in one go .Is it possible , if yes , how to go about it ?? please help, this is the specific customer requirment .
ans will be rewarded
rgds
mojib

Hi,
Just go through the code
report ZMM_FERT_CREATE_EXT_PLANT
       no standard page heading line-size 255.
*include bdcrecx1.
DATA : it_bdcdata LIKE bdcdata OCCURS 0 WITH HEADER LINE,
       it_bdcmsgcoll LIKE bdcmsgcoll OCCURS 0 WITH HEADER LINE.
data : p_filex type string .
types: BEGIN OF t_mm01,
        matnr(018),
        MAKTX(040),
        mtart(004),
        matkl(009),
        WGBEZ(020),
        bklas(004),
        vprsv(001),
        werks(004),
        vkorg(004),
        vtweg(002),
        sktof(001),
        versg(001),
        kondm(002),
        ktgrm(002),
        meins(003),
        gewei(003),
        j_1ichid(012),
        j_1isubind(001),
        j_1icapind(001),
        j_1igrxref(001),
        tragr(004),
        ladgr(004),
        mtvfp(002),
        xchpf(001),
        mtpos_mara(004),
        mtpos(004),
        ekgrp(003),
        BWTTY(010),
        meins1(003),
        meins2(003),
        meins3(003),
        sales_txt(040),
        purc_txt(040),
        mbrsh(001),
        verpr(015),
        peinh(006),
        stprs(015),
        brgew(017),
        ntgew(017),
        j_1ivalass(018),
        umrez1(006),
        umren1(006),
        umrez2(006),
        umren2(006),
        umrez3(006),
        umren3(006),
        lgort(004),
        TAXKM1(001),
        TAXKM2(001),
        HERKL(003),
        HERKR(003),
        J_1IMOOM(018),
      end of t_mm01.
DATA : it_mm01 type table of t_mm01 with header line initial size 0.
*Selection Screen                                              *
SELECTION-SCREEN BEGIN OF BLOCK B WITH FRAME TITLE text-001.
            PARAMETERS: p_file like IBIPPARMS-PATH obligatory.
SELECTION-SCREEN:END OF BLOCK B.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file .
PERFORM get_filename.
*START-OF-SELECTION
START-OF-SELECTION.
   PERFORM upload_data.
   PERFORM fill_data.
*&      Form upload_data
*       text
* --> p1        text
* <-- p2        text
form upload_data .
p_filex = p_file.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
    filename                      = p_filex
    FILETYPE                      = 'ASC'
    HAS_FIELD_SEPARATOR           = '#'
*   HEADER_LENGTH                 = 0
*   READ_BY_LINE                  = 'X'
*   DAT_MODE                      = ' '
*   CODEPAGE                      = ' '
*   IGNORE_CERR                   = ABAP_TRUE
*   REPLACEMENT                   = '#'
*   CHECK_BOM                     = ' '
*   NO_AUTH_CHECK                 = ' '
* IMPORTING
*   FILELENGTH                    =
*   HEADER                        =
tables
    data_tab                      = it_mm01
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.
endform.                    " upload_data
*&      Form get_filename
*       text
* --> p1        text
* <-- p2        text
form get_filename .
CALL FUNCTION 'F4_FILENAME'
               EXPORTING
                 PROGRAM_NAME        = SYST-CPROG
                 DYNPRO_NUMBER       = SYST-DYNNR
*                 FIELD_NAME          = p_file
               IMPORTING
                 FILE_NAME           = p_file .
               if sy-subrc NE 0 .
                  write : / 'Enter File Name'.
               endif.
endform.                    " get_filename
*&      Form fill_data
*       text
* --> p1        text
* <-- p2        text
form fill_data .
*perform open_group.
loop at it_mm01.
clear it_bdcdata.
refresh it_bdcdata.
perform bdc_dynpro      using 'SAPLMGMM' '0060'.
perform bdc_field       using 'BDC_CURSOR'
                              'RMMG1-MTART'.
perform bdc_field       using 'BDC_OKCODE'
                              '=ENTR'.
perform bdc_field       using 'RMMG1-MATNR'
                               it_mm01-matnr.
*                              '116100'.
perform bdc_field       using 'RMMG1-MBRSH'
                              'C'.
perform bdc_field       using 'RMMG1-MTART'
                              'FERT'.
perform bdc_dynpro      using 'SAPLMGMM' '0070'.
perform bdc_field       using 'BDC_CURSOR'
                              'MSICHTAUSW-DYTXT(16)'.
perform bdc_field       using 'BDC_OKCODE'
                              '=ENTR'.
perform bdc_field       using 'MSICHTAUSW-KZSEL(03)'
                              'X'.
perform bdc_field       using 'MSICHTAUSW-KZSEL(05)'
                              'X'.
perform bdc_field       using 'MSICHTAUSW-KZSEL(06)'
                              'X'.
perform bdc_field       using 'MSICHTAUSW-KZSEL(07)'
                              'X'.
perform bdc_field       using 'MSICHTAUSW-KZSEL(09)'
                              'X'.
perform bdc_field       using 'MSICHTAUSW-KZSEL(10)'
                              'X'.
perform bdc_field       using 'MSICHTAUSW-KZSEL(13)'
                              'X'.
perform bdc_field       using 'MSICHTAUSW-KZSEL(16)'
                              'X'.
perform bdc_dynpro      using 'SAPLMGMM' '0080'.
perform bdc_field       using 'BDC_CURSOR'
                              'RMMG1-VTWEG'.
perform bdc_field       using 'BDC_OKCODE'
                              '=ENTR'.
perform bdc_field       using 'RMMG1-WERKS'
                               it_mm01-werks.
*                              '9010'.
perform bdc_field       using 'RMMG1-LGORT'
                               it_mm01-lgort.
*                              'F901'.
perform bdc_field       using 'RMMG1-VKORG'
                               it_mm01-vkorg.
*                              '1000'.
perform bdc_field       using 'RMMG1-VTWEG'
                               it_mm01-vtweg.
*                              '03'.
perform bdc_dynpro      using 'SAPLMGMM' '4000'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'MAKT-MAKTX'
                                it_mm01-maktx.
*                              'Test ACEPHATE TECHNICAL 50kg'.
perform bdc_field       using 'BDC_CURSOR'
                              'MVKE-MTPOS'.
perform bdc_field       using 'MVKE-VERSG'
                                it_mm01-versg.
*                              '1'.
perform bdc_field       using 'MVKE-KONDM'
                                it_mm01-kondm.
*                              '03'.
perform bdc_field       using 'MVKE-KTGRM'
                               it_mm01-ktgrm.
*                              '01'.
perform bdc_field       using 'MVKE-MTPOS'
                                it_mm01-mtpos.
*                              'NORM'.
perform bdc_dynpro      using 'SAPLMGMM' '4000'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'MAKT-MAKTX'
                                it_mm01-maktx.
*                              'Test ACEPHATE TECHNICAL 50kg'.
perform bdc_field       using 'MARC-MTVFP'
                               it_mm01-mtvfp.
*                              '01'.
perform bdc_field       using 'MARC-XCHPF'
                               it_mm01-xchpf.
*                              'X'.
perform bdc_field       using 'BDC_CURSOR'
                              'MARC-LADGR'.
perform bdc_field       using 'MARC-LADGR'
                               it_mm01-ladgr.
*                              '0003'.
perform bdc_dynpro      using 'SAPLMGMM' '4004'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'MAKT-MAKTX'
                                it_mm01-maktx.
*                              'Test ACEPHATE TECHNICAL 50kg'.
perform bdc_field       using 'MARC-HERKL'
                               it_mm01-HERKL.
*                              'IN'.
perform bdc_field       using 'MARC-HERKR'
                               it_mm01-HERKR.
*                              '01'.
perform bdc_field       using 'BDC_CURSOR'
                              'J_1IASSVAL-J_1IVALASS'.
perform bdc_field       using 'J_1IMTCHID-J_1ICHID'
                               it_mm01-J_1ICHID.
*                              '2913 00 90'.
perform bdc_field       using 'J_1IMTCHID-J_1ISUBIND'
                                it_mm01-J_1ISUBIND .
*                              'X'.
perform bdc_field       using 'J_1IMTCHID-J_1ICAPIND'
                                it_mm01-J_1ICAPIND.
*                              'F'.
perform bdc_field       using 'J_1IMTCHID-J_1IGRXREF'
                                 it_mm01-J_1IGRXREF .
*                              '2'.
if it_mm01-J_1IVALASS <> '0'.
perform bdc_field       using 'J_1IASSVAL-J_1IVALASS'
                                it_mm01-J_1IVALASS.
*                              '0'.
endif.
perform bdc_dynpro      using 'SAPLMGMM' '4000'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'MAKT-MAKTX'
                               it_mm01-maktx.
*                              'Test ACEPHATE TECHNICAL 50kg'.
perform bdc_field       using 'BDC_CURSOR'
                              'MARC-EKGRP'.
perform bdc_field       using 'MARC-EKGRP'
                               it_mm01-ekgrp.
*                              '002'.
perform bdc_field       using 'MARC-XCHPF'
                               it_mm01-xchpf.
*                              'X'.
perform bdc_dynpro      using 'SAPLMGMM' '4000'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'BDC_CURSOR'
                              'MAKT-MAKTX'.
perform bdc_field       using 'MAKT-MAKTX'
                               it_mm01-maktx.
*                              'Test ACEPHATE TECHNICAL 50kg'.
perform bdc_field       using 'MARC-STEUC'
                               it_mm01-J_1ICHID.
*                              '2913 00 90'.
perform bdc_field       using 'MARC-HERKL'
                                it_mm01-HERKL.
*                              'IN'.
perform bdc_field       using 'MARC-HERKR'
                               it_mm01-HERKR.
*                              '01'.
perform bdc_field       using 'J_1IMTCHID-J_1ICHID'
                               it_mm01-J_1ICHID.
*                              '2913 00 90'.
perform bdc_field       using 'J_1IMTCHID-J_1ISUBIND'
                                it_mm01-J_1ISUBIND.
*                              'X'.
perform bdc_field       using 'J_1IMTCHID-J_1ICAPIND'
                               it_mm01-J_1ICAPIND.
*                              'F'.
perform bdc_field       using 'J_1IMTCHID-J_1IGRXREF'
                                it_mm01-J_1IGRXREF.
*                              '2'.
perform bdc_dynpro      using 'SAPLMGMM' '4000'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'BDC_CURSOR'
                              'MAKT-MAKTX'.
perform bdc_field       using 'MAKT-MAKTX'
                               it_mm01-maktx.
*                              'Test ACEPHATE TECHNICAL 50kg'.
perform bdc_field       using 'MARC-XCHPF'
                                it_mm01-xchpf.
*                              'X'.
*perform bdc_field       using 'MARA-IPRKZ'
*                              'D'.
perform bdc_dynpro      using 'SAPLMGMM' '4000'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'MAKT-MAKTX'
                                it_mm01-maktx.
*                              'Test ACEPHATE TECHNICAL 50kg'.
perform bdc_field       using 'BDC_CURSOR'
                              'MBEW-STPRS'.
perform bdc_field       using 'MBEW-BKLAS'
                                it_mm01-bklas.
*                              '7930'.
perform bdc_field       using 'MBEW-VPRSV'
                                it_mm01-vprsv.
*                              'S'.
perform bdc_field       using 'MBEW-PEINH'
                                it_mm01-peinh.
*                              '1'.
perform bdc_field       using 'MBEW-VERPR'
                                it_mm01-verpr.
*                              '273.75'.
perform bdc_field       using 'MBEW-STPRS'
                               it_mm01-stprs.
*                              '207'.
perform bdc_dynpro      using 'SAPLSPO1' '0300'.
perform bdc_field       using 'BDC_OKCODE'
                              '=YES'.
CALL TRANSACTION 'MM01' USING it_bdcdata
                                MODE 'A'
                                UPDATE 'A'
                                MESSAGES INTO it_bdcmsgcoll.
CLEAR it_mm01.
endloop.
*perform bdc_transaction using 'MM01'.
*perform close_group.
endform.                    " fill_data
*&      Form bdc_dynpro
*       text
*      -->P_0297   text
*      -->P_0298   text
form bdc_dynpro USING prog scr.
CLEAR it_bdcdata.
it_bdcdata-program = prog.
it_bdcdata-dynpro = scr.
it_bdcdata-dynbegin = 'X'.
APPEND it_bdcdata.
endform.                    " bdc_dynpro
*&      Form bdc_field
*       text
*      -->P_0687   text
*      -->P_IT_MM01_VPRSV text
form bdc_field USING fnam fval.
CLEAR it_bdcdata.
it_bdcdata-fnam = fnam.
it_bdcdata-fval = fval.
APPEND it_bdcdata.
endform.                    " bdc_field
Regards,
Madhu.

Create Material Master using BAPI_MATERIAL_SAVEDATA - just the basic view

Hi,
I want to create new material master ( just the basic view ) using BAPI_MATERIAL_SAVEDATA.
No error found in the return parameter, but the material was not created.
Here is my code :
DATA : ld_headdata LIKE bapimathead,
       lt_return LIKE bapiret2 OCCURS 0 WITH HEADER LINE,
       lt_return_comit LIKE bapiret2 OCCURS 0 WITH HEADER LINE,
       lt_return_cl LIKE bapiret2 OCCURS 0 WITH HEADER LINE,
       ld_datum(10),
       ld_uzeit(10).
DATA: ld_matdesc LIKE bapi_makt OCCURS 0 WITH HEADER LINE,
      ld_clientdata LIKE bapi_mara.
Regards,
Hary
ld_headdata-material = 'MATERIAL-01'.
ld_headdata-ind_sector = 'M'.
ld_headdata-matl_type = 'ERSA'.
ld_headdata-basic_view = 'X'.
ld_matdesc-matl_desc = 'TEST MATERIAL'.
ld_matdesc-langu = sy-langu.
APPEND ld_matdesc.
ld_clientdata-base_uom = 'PC'.
CALL FUNCTION 'BAPI_MATERIAL_SAVEDATA'
EXPORTING
    headdata                    = ld_headdata
    clientdata                  = ld_clientdata
   clientdatax                 =
PLANTDATA                   =
PLANTDATAX                  =
FORECASTPARAMETERS          =
FORECASTPARAMETERSX         =
PLANNINGDATA                =
PLANNINGDATAX               =
STORAGELOCATIONDATA         =
STORAGELOCATIONDATAX        =
VALUATIONDATA               =
VALUATIONDATAX              =
WAREHOUSENUMBERDATA         =
WAREHOUSENUMBERDATAX        =
SALESDATA                   =
SALESDATAX                  =
STORAGETYPEDATA             =
STORAGETYPEDATAX            =
FLAG_ONLINE                 = ' '
FLAG_CAD_CALL               = ' '
NO_DEQUEUE                  = ' '
NO_ROLLBACK_WORK            = ' '
IMPORTING
   return                      = lt_return
TABLES
   materialdescription         = ld_matdesc
UNITSOFMEASURE              =
UNITSOFMEASUREX             =
INTERNATIONALARTNOS         =
MATERIALLONGTEXT            =
TAXCLASSIFICATIONS          =
RETURNMESSAGES              =
PRTDATA                     =
PRTDATAX                    =
EXTENSIONIN                 =
EXTENSIONINX                =
NFMCHARGEWEIGHTS            =
NFMCHARGEWEIGHTSX           =
NFMSTRUCTURALWEIGHTS        =
NFMSTRUCTURALWEIGHTSX       =
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
WAIT          =
IMPORTING
   return        = lt_return_comit

hi
Hope it will help you.
<REMOVED BY MODERATOR>
REPORT z34332_bdc_create_material .
data: la_headdata type BAPIMATHEAD,
la_clientdata type BAPI_MARA,
la_CLIENTDATAX type BAPI_MARAX,
la_return type BAPIRET2.
data: i_materialdescription type table of BAPI_MAKT,
wa_materialdescription like line of i_materialdescription.
la_headdata-MATERIAL = '000000000000000004'.
la_headdata-IND_SECTOR = 'M'.
la_headdata-MATL_TYPE = 'FERT'.
la_clientdata-BASE_UOM = 'FT3'.
la_CLIENTDATAX-BASE_UOM = 'X'.
la_clientdata-MATL_GROUP = '01'.
la_CLIENTDATAX-MATL_GROUP = 'X'.
wa_materialdescription = 'TEST'.
append wa_materialdescription to i_materialdescription.
clear: wa_materialdescription.
CALL FUNCTION 'BAPI_MATERIAL_SAVEDATA'
EXPORTING
headdata = la_headdata
CLIENTDATA = la_clientdata
CLIENTDATAX = la_CLIENTDATAX
* PLANTDATA =
* PLANTDATAX =
* FORECASTPARAMETERS =
* FORECASTPARAMETERSX =
* PLANNINGDATA =
* PLANNINGDATAX =
* STORAGELOCATIONDATA =
* STORAGELOCATIONDATAX =
* VALUATIONDATA =
* VALUATIONDATAX =
* WAREHOUSENUMBERDATA =
* WAREHOUSENUMBERDATAX =
* SALESDATA =
* SALESDATAX =
* STORAGETYPEDATA =
* STORAGETYPEDATAX =
* FLAG_ONLINE = ' '
* FLAG_CAD_CALL = ' '
IMPORTING
RETURN = la_return
TABLES
MATERIALDESCRIPTION = i_materialdescription
* UNITSOFMEASURE =
* UNITSOFMEASUREX =
* INTERNATIONALARTNOS =
* MATERIALLONGTEXT =
* TAXCLASSIFICATIONS =
* RETURNMESSAGES =
* PRTDATA =
* PRTDATAX =
* EXTENSIONIN =
* EXTENSIONINX =
write: la_return-TYPE, ',', la_return-MESSAGE.
clear: la_headdata, la_return, la_clientdata, la_clientdatax.
Edited by: Alvaro Tejada Galindo on Feb 19, 2008 3:23 PM

IN MATERIAL MASTER RECORD WHAT IS THE USE OF CLASS TYPE(CLASSIFICATION VIEW

Hi Guys,
Can you please explain what are the different critiria to use different class type and what exactly meaning of the each class type with respect to Material classification.
Any material available on this to study. Please give link.
Thanks,
Dhanu

Hi,
Purpose
The classification system allows you to use characteristics to describe all types of objects, and to group similar objects in classes u2013 to classify objects, in other words, so that you can find them more easily later.
You then use the classes to help you to find objects more easily, using the characteristics defined in them as search criteria. This ensures that you can find objects with similar or identical characteristics as quickly as possible.
Integration
The classification system allows you to classify all types of object. First, you must define certain settings in Customizing for the classification system. For more information, see Customizing for the Classification System.
SAP has predefined a number of object types (for example, materials, and equipment). The settings for these object types have already been defined in Customizing, so you can start to set up your classification system for these object types without defining further settings.
Features
Before you can use classification functions, you need to set up your classification system.
The there are three steps to setting up a classification system:
Defining the Properties of Objects
You use characteristics to describe the properties of objects. You create characteristics centrally in the SAP R/3 System.
See the SAP Library, Characteristics (CA-CL-CHR).
Creating Classes
You need classes to classify objects. These classes must be set up. During set up you must assign characteristics to the classes.
Assigning Objects
Once you have created the classes you require for classification, you can assign objects to these classes. You use the characteristics of the class to describe the objects you classify.
This completes the data you require to use your classification system. You can then use your classification system to find objects that match the criteria you require.
Once you have set up the classification system you can use it to find certain objects. To do this:
Find a class in which objects are classified
Find the object(s) you require in the class
When you use classification to find objects, you use the characteristics as search criteria, and the system compares the values you enter with the values of the classified objects.
Uts
Award if helpfull

Make field in Material master mandatory based on the material group

Hello all,
I need to make the field "post to inspection flag" mandatory based on the material group while creating the Material master.
I found options for making the field mandatory based on Material type,Industry sector and plant NOT based on the material group.
Could anyone please provide suggestions on setting up the field as mandatory based on material group while creating material master
Thanks,
Sre

Hi Sre,
You can make Material Group field as Mandatory while Creating Material Master.
SPRO>Log General>Material Master>Field Selection>Maintain Field Selection for Data Screens
Select Screen # 48
In the Field selection (Field Ref.) of (MARA - MAKTL) screen , Change the settings from Optional to Required Entry for T Codes MM01, MM02 or you can select the Material Type ;
Please note this by choosing this selection the fields of Profit Center and Division will also become Mandatory.
Hope this helps,
Best regards
Amit Bakshi

Material Master data distribution using the Classifications

Hi All,
I am attempting to cater for a business scenario where we wish to distribute material master records via IDOCS by assigning a class to each material we wish to send out.
We have a new classtype (Z01) which is setup for distribution purposes (the status for this class type has been maintained). I have defined a filter using classes in BD60.
The next step was to setup the distribution model for my message type and partner. I added the filter group in the distribution model for the message type (filter group "dependant on class membership"). The final step after generating the partner profile was to assign a new class that I created to the material master.
We are using change pointers and BD21 to create the IDOCs. I am managing to create the outbound IDOC but I am getting a 29 Status with an error message "Class type Z01 , receiving system ZFR001 : no list maintained". ZFR001 is the name of the external partner. The name of the class that has been assigned to the material master is also ZFR001. There are no characteristics assigned to the class.
Has anyone setup a similar scenario? I'd appreciate any guidance as I have hit a bit of a wall.
Best regards,
James.

Hi,
The message type to send HR data is HRMD_A, i don't think that filtering this only message you achieve what you describe.
In this message type, yo can define filters to send only the relevant infotypes that you need, but all of them will be send in the same idoc, for one employee.
So I think to achieve what you want, you should create customer Message types (Z's) as reductions of HRMD_A standard message type and then in BD64 create one different Model for each one. So in each model you can put only the infotypes you want. You should very carefull with the updating in your destination system, because if you process all the message type at the same time, there will be a lot of blocking in employee objects.
It is weird what you want to do, but this could be the solution.
Regards,

Delet Material Master Record but not the range

HI experts,
I have more material master records in production data base; now i need to delete them but at the same time don't remove the range numbering.
I.E.
there are 10 master record with range number from 1 to 10.
now, deleting these 10 master records, i would like to avoid that the numbering starts from 11.
thanks in advance
C.

Hi Jurgen,
I've gone through the data archiving project in the past. I was actually hoping I don't have to go through this big exercise for this minor situation.
The storage locations in the SAP system are fine. The problem is that when I came in to this organization, I found out that the procurement users have accidentally extended material master record to those storage location irrelevant to them. Those users don't post any stock to those accidentally extended storage location. They admit that it was a mistake. So, I don't really have to do stock movement or GI out from those affected storage location because there's nothing in them.
Now that I've initially flag for deletion (MM06) of those mistakes done by those procurement users over the few years counting to 2000+ material master records affected. But the standard behavior of the SAP system allows change to proceed in MM02 except for that warning message MM081. So, I was actually asking around to explore if there's actually an option to make it an error prompt instead and stop the whole change process at MM02 transaction level.
If I may re-confirm, what I've done so far via flaging for deletion of material master record at storage location level - is this the only correct solution available?
Hope this clarifies my intention of opening this thread. Sometimes, users are quite tough in accepting the results from standard SAP system behavior.
Thanks for the time in explaining.
Steven

I want to read the values of the inside accelerometer on Kinect for Windows v2 sensor.

I had used the inside accelorometer on Kinect for Windows v1. So I want to use it for Kinect for Windows v2 application. However I can't find any function or method on Kinect for Windows SDK v2.0. But it is near the Ir camera of K4W v2. I found the Kionix
chip. Do you have any plan to access this chip?

I just went through the slides of "Programming Kinect for Windows v2 Jump Start" of the MS Virtual Academy, and in slide #11 of slide deck #07 (Advanced Topics: Skeletal Tracking and Depth Filtering,
http://www.microsoftvirtualacademy.com/training-courses/programming-kinect-for-windows-v2-jump-start), it says:
Align the y-axis to gravity
–Tilt correct with
FloorClipPlane.xyz
•Falls back to accelerometer when no floor is found
•Rotate
scene such that “up” is (0,1,0)
So, just to make sure I understand, you are saying that the information provided in the slide deck (and in the video) is erroneous and we cannot access the accelerometer info?

Want to update Moving or Standard price from material master to ***.Value ?

Hai Experts,
As per Subcontract Logic, 1.1 % of the standard price should be update in J1ID Asseable value..
so I need to update Standard price value should be automatically update in Assesable value whenever it price changes..
Kindly guide me

Hi,
I think its not possible to shiftf from th MAp to J1Id assessable value.
Need to maintina in the field place of J1ID.
Regards,
Andra

Recorded results value against the batches.

Hi experts,
                  my requirment is i need Recorded results against batches in tabular form anybody haviing any std. t code or table ?
Like Batches    MIC 1 MIC2 MIC3
         X             25        26    27
          Y            65        56    58   like wise.
Cheers

Dear
There is no std report as per my knowledge but either use me53n
or
Use tables like QALS & QAMR in SQVI .
Regards

During LTP material master values need to be modified

Hi ,
We are implementing LTP process in company. while LTP Run it pick the MRP1234 values for Simulative order creation. We have requirement to change the MRP1234 only during LTP run. Were as the MRP run will run with normal material master(MRP1234) values.
The values need to be changed are during LTP run are MRP group , Lox size etc., '''

Thank you.. Almedia and köller..
We are already using this badi MD_MRP_PARAMETERS. We are facing the following problem
For example
header ATEST
component BCOMP
We need to switch off the bulk indicator and phantom for the component.
We are using the above bapi its manipulation only the header (ATEST) material master data but in LTP run during creation of header simulative planned. Component simulative dep requirement values are copied from material master. In this above bapi we are manipulating only header values.
When the next loop during component simulative planned order generation time the above parameters(bulk and phantom) are copied from component simulative dep requirement. Hence the switching of bulk indicator and phantom assembly is not working during ltp using this badi. This problem is happening for multi level components too.
Is there any suggestion for this issue..

Copy of Material Master charac. values to the batch classif. in GR for PO

Similar Messages

Maybe you are looking for