Unit of measure in availability overview

Hi
The question is about the possibility to change the unit of measure displayed in the availability overview during a sales order creation as you can do in transaction MD04.
The problem is that if you set a quantity in the sales order in a alternative unit of measure (for instance Boxes) and if you check the availability, the systems shows the quantities in the base unit of measure (e.g. Pieces), so it is quite complicated to make the conversion, because you do not have the information on the screen.
Has anybody solved that issue?
thanks a lot!

Hi,
       Check in material master.U can go to aditional data and give as box and save the material then it will ask u how many units for a box.Then check this hope it solves ur problem.
RV

Similar Messages

  • Internal Unit of measurement in J1ILIC01

    Hi,
    While creating Deemed Export Licence thru T.Code J1ILIC01, I came across one issue that when I enter the Material Number it only pics the description of material. However, the UoM is not picked automatically.
    When I tried to put it manually, it will not accept.
    It only accept the Internal Unit of measurement instead of Commercial Unit of measurement.
    Thanks.

    Thanks Marcin,
    Just to clarify from my side,even though the error occured only for one UOM,no unit of measurement are available.
    Does your solution still apply?
    Thanks for your help.
    Best Regards.
    jayawant

  • Material unit of measure

    Hiiiiiiiiiiiiiiii Experts,
    I have a problem.When I am attaching material to an activity , it is taking base unit of measure which has been defined in material master as default.In case of stock item  as item category it allows me to change the unit.But in case of Non Stock item it's not allowing me to change the unit.
    For example I have a material A1 whose base unit of measure is defined in meter.But purchasing unit is TON.when i am adding it to activity as non stock item, it's unit appears as meter and its not allowing me to change it .It gives the error as   _Item category N: Only base unit of measure METER allowed_.
    For same material if i buy as stock item it allows me to change.
    I have to buy it as non stock item, so plz tell me how can  I change its unit of measure in component overview screen.
    Regards
    Brijesh

    Hi Brijesh,
    if you mentioning material as nonstock item that means PR against Network ....
    and consumtion is agianst base unit only..... so at the time of PR system will not allow you to use alternate unit....( since it is against Network.)
    Venkatesh

  • Internal Unit of Measurement

    Hello
    At the time of creating a shopping cart,the moment,UOM is selected ,I get the following error.
    "Internal Measurement Unit ZTO doesn´t exits in Spanish language"
    However,,just to clarify,this unit of measurement is maintained in backend as well as SRM.
    Could you help please?
    Best Regards.
    Jayawant Gokhale

    Thanks Marcin,
    Just to clarify from my side,even though the error occured only for one UOM,no unit of measurement are available.
    Does your solution still apply?
    Thanks for your help.
    Best Regards.
    jayawant

  • Stock inconsistencies due to wrong Unit of measure

    Hi,
    I am currently facing an issue, generated due to master data inconsistencies. The problem is as follows:
    I have a  material with Unit of measure " pack". A PO was supposed to be created for "100 packs" of this material, but somehow Unit of measure in PO was "each", and thus it was created for "100 each". The supplier has sent quantity as 100 packs. GR was done on the basis of PO thus 100 each was entered. Invoice has been created and settled. Stock overview is showing this material as "100 each" whereas actually the material quantity physically available is 300 (100x3, each pack has 3 pcs).
    I need to correct this situation. so that stock and accounts show the correct data.
    Is there any simple way of correcting this issue. like scrapping etc... and how??
    Thank you.

    Dear Priya,
    You have completed the complete purchase cycle.
    One way is to reverse the complete cycle, change the UOM and redo the cycle.
    Ohter way is, if you need to increase the stock you can do that by delivery free of cost (mvt. type 511) or creating a PO with free tick followed by GR.
    In this case you need to check the MAP of the material. If you need to change the MAP also then use transaction MR21.
    Before doing please check the accounting impact of all these (the price difference account or the revaluation account will get hit).
    In second option you can not change the UOM.(Maintain conversion factor between EA and PACK as 1:1)
    Cheers,
    Satish Purandare

  • Adding extra unit of measure to LS26 screen

    How do I add an extra unit of measure to the stock overview screen - LS26
    Currently when I click on this button, only KGM is aviable to choose, I wish to add TNE
    Please advise if possible
    Many thanks
    Tony

    Ignore, I have found out how to do this, by adding TNE, as the WM unit of measure on WM1 sheet of Material Masterdata
    Field MLGN-LVSME
    This unit of measure is then available for you to view using LS26, for this material

  • AffineTransform - Is there a way to glean units of measurement for pixels?

    Assuming I get a pointer to a java.awt.geom.AffineTransform from:
    java.awt.geom.AffineTransform CurTransform = ((java.awt.Graphics2D)this.getMainFrame().getGraphics()).getDeviceConfiguration().getDefaultTransform();
    Assuming I've gotten the right AffineTransform... How do I get, or can I get, the scaling factor between horizontal pixels and vertical pixels for the current screen (or whatever device). In other words I want to place components... buttons, textboxes, etc. in a dialog box so that they are "square". i.e. 10 units in x look on the screen equal to 10 units in y.
    Once I know what the "square pixel scale factor" is I can then worry about making the units relative to whatever font size.
    This question is usually posed as "How do I get dialog units?". I haven't done that because of the "legacy problems" associated with what most people think dialog units come from. It is true that way back when dialog units were derived from a textmetrics ONLY, but unless I'm mistaken, Charles Petzold, was describing something that could only be gotten that way at that time (circa 1990).... The width of the fixed system font by the height of the fixed system font ended up being as close to a unit that was 8 units high looked like 8 units wide in the screen. The object of the exercise is to most importantly get units of measurement that translate to pixels and look "square" on the screen. Secondarily, but not unimportant, is to be a unit that has some relevance to the current font size. It's been a long time dialog units in windows maybe a 2:1 ratio. I made my own cDialogUnits so long ago I can't remember what the "standard windows" dialog unit is. In windows I can very easily get the screen dpi x and y, I think it's a devicecontext but Java's "devicecontext" only gives one dimension of the dpi?
    Also this query is mute if I was "painting" on a device. The units are for pixels NOT points and are (mostly) for placing controls on the screen. I am aware of and have used the various addPreferredGap and setAutoCreateContainerGaps available in a GroupLayout... Great gizmos but, still dialog units would be very handy for setting the prefered width of a textbox/label with too much text. (Note: dialog units are NOT for calculating the height of text... )
    I did search the sun forums for an answer first... It might be here I just didn't find it. It seems to be a question either avoided like the plague or considered a dumb question in Java.

    This might be OK?
    BE AWARE!! This is NOT a painting gizmo. It is used in conjunction with the Layout gizmos. It drives me crazy that the Layout gizmos have "default" gaps and spacers of some kind and yet ALL the tutorials immediately and unabashedly trash any "device independence" by mixing in pixel measurements... Not to mention I don't like the size of the gaps and spacing provided with the Layout gizmos anyway.
    Does anyone know if this will fail? I am aware of the caveats provided... "Information about the device is only as good as has been provided." However if there is bad information in the device info I doubt using these units will do anything much different that the end user experiences with the errant device anyway.
    AGAIN... This is NOT a painting gizmo. It's a helper when Laying out controls usually in conjunction with a Layout and only for spaces and gaps.
    public class DialogUnits
        private double m_x;
        private double m_y;
        public DialogUnits( java.awt.Graphics2D g2 )
            java.awt.GraphicsConfiguration gc = g2.getDeviceConfiguration();
            java.awt.geom.AffineTransform at = gc.getDefaultTransform();
            at.concatenate( gc.getNormalizingTransform() );
            double fs = g2.getFont().getSize2D();
            m_x = at.getScaleX() * fs;
            m_y = at.getScaleY() * fs;
        public int CalcX( double units )
            return (int)Math.round( ( units * m_x ) / 8.0 );
        public int CalcY( double units )
            return (int)Math.round( ( units * m_y ) / 8.0 );
        public int ContainerGapX()
            return this.CalcX( 8.0 );
        public int ContainerGapY()
            return this.CalcY( 8.0 );
        public int FontSize2dX( int crude_columns )
            return (int)Math.round( crude_columns * m_x );
        public int FontSize2dY( int crude_rows )
            return (int)Math.round( crude_line_height * m_y );
        public int X( int units )
            return this.CalcX( units );
        public int Y( int units )
            return this.CalcY( units );
        } // end of class DialogUnits

  • Error  while creating PO --   Unit of measure not defined for lanuage  ZH

    Hi all,
    i  have created the PR with EA as UOM. Then while creating PO, i am getting error like
    '  Unit of measure not defined for lanuage ZH' .
    Then  I execute CUNI
    Then menu is GOTO > Translation > units of measure
    enter source language and target language . After this i am getting the below message
    --->  Language not available on server
    Please suggest what i should do. Thanks.
    Thanks
    pabi

    HI Pabi,
    Go to material master for material in purchase requisition, the Go to Additional data and maintained language as ZH in material master data.
    Also the other possibility, that if in your case purchase requisition are converted to purchase orders through background jobs,
    then check the background job execution in SM37 whether that background job has been triggered twice parellely in the background, which could have resulted in locking of same purchase requisition at same time and hence your are getting the Error.
    Br,
    Tushar

  • Material Master MATMAS IDOC and base unit of measurement

    Hi
    We are using SAP standard material master IDOC type MATMAS05 to trigger IDOC. Our material master is having base unit of measure as "G". We are not using ISO unit of measurement. But Material master IDOC, segment E1MARM is populating base unit of meaurement (MEINS) as "GRM".
    Any idea why IDOC is picking ISO unit of measurement instead of material master base unit of measurement.
    Any idea how to send base unit of measurememt as "G" instead of "GRM" in DOC segment.
    Thanks
    Nilesh

    There are ISO codes for country keys, currency keys, units of measure and shipping instructions. According to SAP design guidelines, you should use ISO codes for an IDoc if they are available. When you set up the IDoc, the SAP codes have to be replaced by ISO codes.
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf

  • Unit of measure

    Hi
    I want to procure same material from same vendor for different plants with different unit of measure.I tried maintaining different unit of measure in inforecord but it is not posible...
    How to maintian differnet unit of measure with plant level for same material..
    kindly need your inputs
    -Prabu

    hi,
    soory for delay,
    to create condition table and assigning to access sequence go to
    spro-mm-purchasing-condition-create contion table(in this create table in 900 ser.and enter. then double click on field u wnt eg. pur.org plant etc and then generate the table)-then go to acc. seq. in that go to change and assign that con. table before the info record table i.e. if info record acc, no. is 20 give earlier no. which is available and save it .
    then go to MEK1 t. code u will get the pop up in which u will get u r combination ok.

  • Unit of measure error in BAPI_MATERIAL_SAVEDATA

    Hi Guru's,
    i am trying to upload the material master data using BAPI...while uploading ia m getting beloow error ..please guide me anyone you..where i am doing mistake.....
    1st this error i am getting while executing:
    internal unit HR ,language EN is not maintained.
    and afetr execution in gs_return i am getting below error:
    Unit of measure ****** is not defined; check your entry
    error number :490
    dont get tence for code and all the values ae moving properly into BAPI...and
    here i am consider the unit of mesure as HR (hour)..
    here i am caliculating like ex: for employe (material) generating bill in hour basis.that is per 1hour $100.
    please let me know if my question is not clear..
    thanks in advance and will full points to reply....
    *& Report  ZERP_MATERIAL_CREATE_UPLOAD
    REPORT  zerp_material_create_upload.
    DATA:gs_bapimathead          TYPE bapimathead,
         gs_clientdata           TYPE bapi_mara,
         gs_clientdatax          TYPE bapi_marax,
         gs_plantdata            TYPE bapi_marc,
         gs_plantdatax           TYPE bapi_marcx,
         gs_forecastparameters   TYPE bapi_mpop,
         gs_forecastparametersx  TYPE bapi_mpopx,
         gs_valuationdata        TYPE bapi_mbew,
         gs_valuationdatax       TYPE bapi_mbewx,
         gs_salesdata            TYPE bapi_mvke,
         gs_salesdatax           TYPE bapi_mvkex,
         gs_storagelocationdata  TYPE bapi_mard,
         gs_storagelocationdatax TYPE bapi_mardx,
         gt_materialdescription  TYPE STANDARD TABLE OF bapi_makt,
         gwa_materialdescription TYPE bapi_makt,
         gt_taxclassifications   TYPE STANDARD TABLE OF bapi_mlan,
         gwa_taxclassifications  TYPE bapi_mlan,
         gt_prtdata              TYPE STANDARD TABLE OF bapi_mfhm,
         gwa_prtdata             TYPE bapi_mfhm,
         gt_prtdatax             TYPE STANDARD TABLE OF bapi_mfhmx,
         gwa_prtdatax            TYPE bapi_mfhmx,
         gt_unitsofmeasure       TYPE STANDARD TABLE OF bapi_marm,
         gwa_unitsofmeasure      TYPE bapi_marm,
         gt_unitsofmeasurex      TYPE STANDARD TABLE OF bapi_marmx,
         gwa_unitsofmeasurex     TYPE bapi_marmx,
         gs_return               TYPE bapiret2.
    TYPES:BEGIN OF gty_itab1,
             matnr(18),   "material
             mbrsh(1),    "industry sector
             mtart(4),    "material type
             vkorg(4),    "sales org
             vtweg(2),    "distr chan
             kondm(2),    "mat prcing grp
             ktgrm(2),    "acc asgn grp
             dwerk(4),    "plant
             meins(3),    "base uom
             tragr(4),    "tarns grp
             matkl(9),    "mat grp
             spart(2),    "division
             ntgew(13),   "net weight
             gewei(3),    "weight unit
             werks(4),    "plant
             ladgr(4),    "loading grp
             dismm(2),    "mrp type
             mtvfp(2),    "available check
             disgr(4),    "mrp grp
             dispo(3),    "mrp controller
             beskz(1),    "procurement type
             prmod(1),    "forecasting mode
             bklas(4),    "valution class
             stprs(11),   "std price
             vprsv(1),    "price control
             peinh(5),    "price unit
             lgort(4),    "storage location
             maktx(40),   "mat description
             taxkm(1),    "tax class
             planv(3),    "task list usage
             brgew(13),   "gross weight
             mtpos(4),    "gen it gross grp
          END OF gty_itab1.
    DATA:gt_itab1 TYPE STANDARD TABLE OF gty_itab1,
         gwa_itab1 TYPE gty_itab1.
    TYPES:BEGIN OF gty_itab2,
          abc(178),
    END OF gty_itab2.
    DATA:gt_itab2 TYPE STANDARD TABLE OF gty_itab2,
         gwa_itab2 TYPE gty_itab2.
    PARAMETERS:p_files TYPE string.
    *START-OF-SELECTION.
    START-OF-SELECTION.
    *using call method uploading CSV file into internal table
      CALL FUNCTION 'GUI_UPLOAD'
        EXPORTING
          filename                = p_files
          filetype                = 'ASC'
        TABLES
          data_tab                = gt_itab2
        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.
      LOOP AT gt_itab2 INTO gwa_itab2.
        gwa_itab1 = gwa_itab2-abc(178).
        APPEND gwa_itab1 TO gt_itab1.
      ENDLOOP.
      LOOP AT gt_itab1 INTO gwa_itab1.
        SPLIT gwa_itab1 AT ',' INTO
              gwa_itab1-matnr
              gwa_itab1-mbrsh
              gwa_itab1-mtart
              gwa_itab1-vkorg
              gwa_itab1-vtweg
              gwa_itab1-kondm
              gwa_itab1-ktgrm
              gwa_itab1-dwerk
              gwa_itab1-meins
              gwa_itab1-tragr
              gwa_itab1-matkl
              gwa_itab1-spart
              gwa_itab1-ntgew
              gwa_itab1-gewei
              gwa_itab1-werks
              gwa_itab1-ladgr
              gwa_itab1-dismm
              gwa_itab1-mtvfp
              gwa_itab1-disgr
              gwa_itab1-dispo
              gwa_itab1-beskz
              gwa_itab1-prmod
              gwa_itab1-bklas
              gwa_itab1-stprs
              gwa_itab1-vprsv
              gwa_itab1-peinh
              gwa_itab1-lgort
              gwa_itab1-maktx
              gwa_itab1-taxkm
              gwa_itab1-planv
              gwa_itab1-brgew
              gwa_itab1-mtpos.
    *header data
        gs_bapimathead-material                      = gwa_itab1-matnr.
        gs_bapimathead-ind_sector                    = gwa_itab1-mbrsh.
        gs_bapimathead-matl_type                     = gwa_itab1-mtart.
        gs_bapimathead-basic_view                      = 'X'.
        gs_bapimathead-sales_view                      = 'X'.
        gs_bapimathead-purchase_view                   = 'X'.
        gs_bapimathead-mrp_view                        = 'X'.
        gs_bapimathead-storage_view                    = 'X'.
        gs_bapimathead-account_view                    = 'X'.
        gs_bapimathead-cost_view                       = 'X'.
    *sales data
        gs_salesdata-sales_org                       = gwa_itab1-vkorg.
        gs_salesdatax-sales_org                      = '8888'.   "'X'.
        gs_salesdata-distr_chan                      = gwa_itab1-vtweg.
        gs_salesdatax-distr_chan                     = '88'.   "'X'.
        gs_salesdata-mat_pr_grp                      = gwa_itab1-kondm.
        gs_salesdatax-mat_pr_grp                     = 'X'.
        gs_salesdata-acct_assgt                      = gwa_itab1-ktgrm.
        gs_salesdatax-acct_assgt                     = 'X'.
        gs_salesdata-delyg_plnt                      = gwa_itab1-dwerk.
        gs_salesdatax-delyg_plnt                     = 'X'.
    *client data
        gs_clientdata-base_uom                       = 'HR '.   "gwa_itab1-meins.
        gs_clientdatax-base_uom                      = 'X'.
        gs_clientdata-trans_grp                      = gwa_itab1-tragr.
        gs_clientdatax-trans_grp                     = 'X'.
        gs_clientdata-matl_group                     = gwa_itab1-matkl.
        gs_clientdatax-matl_group                    = 'X'.
        gs_clientdata-division                       = gwa_itab1-spart.
        gs_clientdatax-division                      = 'X'.
        gs_clientdata-net_weight                     = gwa_itab1-ntgew.
        gs_clientdatax-net_weight                    = 'X'.
        gs_clientdata-unit_of_wt                     = gwa_itab1-gewei.
        gs_clientdatax-unit_of_wt                    = 'X'.
       gs_clientdata-item_cat                       = gwa_itab1-mtpos.
       gs_clientdatax-item_cat                      = 'X'.
    *Plant data
        gs_plantdata-plant                           = '8888'. "gwa_itab1-werks.
        gs_plantdatax-plant                          = '8888'.   "'X'.
        gs_plantdata-loadinggrp                      = gwa_itab1-ladgr.
        gs_plantdatax-loadinggrp                     = 'X'.
        gs_plantdata-mrp_type                        = gwa_itab1-dismm.
        gs_plantdatax-mrp_type                       = 'X'.
        gs_plantdata-availcheck                      = gwa_itab1-mtvfp.
        gs_plantdatax-availcheck                     = 'X'.
        gs_plantdata-mrp_group                       = gwa_itab1-disgr.
        gs_plantdatax-mrp_group                      = 'X'.
        gs_plantdata-mrp_ctrler                      = gwa_itab1-dispo.
        gs_plantdatax-mrp_ctrler                     = 'X'.
        gs_plantdata-proc_type                       = gwa_itab1-beskz.
        gs_plantdatax-proc_type                      = 'X'.
        gs_plantdata-period_ind                      = 'M'.   "HARD CODED FOR PERKZ peroid indicator
        gs_plantdatax-period_ind                     = 'X'.
        gs_plantdata-inhseprodt                      = '0'.   "hard coded for DZEIT inhouse production
        gs_plantdatax-inhseprodt                     = 'X'.
    *forecast parameeters
        gs_forecastparameters-plant                  = '8888'.   "gwa_itab1-prmod.
        gs_forecastparametersx-plant                 = '8888'.   "'X'.
        gs_forecastparameters-fore_model             = gwa_itab1-prmod.
        gs_forecastparametersx-fore_model            = 'X'.
    *valution data
        gs_valuationdata-val_area                   = '8888'. "gwa_itab1-bklas.
        gs_valuationdatax-val_area                  = '8888'.   "'X'.
        gs_valuationdata-val_class                   = gwa_itab1-bklas.
        gs_valuationdatax-val_class                  = 'X'.
        gs_valuationdata-std_price                   = gwa_itab1-stprs.
        gs_valuationdatax-std_price                  = 'X'.
        gs_valuationdata-price_ctrl                  = gwa_itab1-vprsv.
        gs_valuationdatax-price_ctrl                 = 'X'.
        gs_valuationdata-price_unit                  = gwa_itab1-peinh.
        gs_valuationdatax-price_unit                 = 'X'.
    *storage location dat
        gs_storagelocationdata-plant              = '8888'.  "gwa_itab1-lgort.
        gs_storagelocationdatax-plant             = '8888'.  "'X'.
        gs_storagelocationdata-stge_loc              = gwa_itab1-lgort.
        gs_storagelocationdatax-stge_loc             = '8888'.   "'X'.
    *material discription
        gwa_materialdescription-langu                = 'E'.
        gwa_materialdescription-matl_desc            = gwa_itab1-maktx.
    *tax classification
       gwa_taxclassifications-taxclass_1            = gwa_itab1-taxkm.
        gwa_taxclassifications-depcountry            = 'US '.         "HARD CODE FOR TAX
    *prt data
        gwa_prtdata-plant                        = '8888'.   "gwa_itab1-planv.
        gwa_prtdatax-plant                       = '8888'.   "'X'.
        gwa_prtdata-prt_usage                        = gwa_itab1-planv.
        gwa_prtdatax-prt_usage                       = 'X'.
    *unitsof measure
        gwa_unitsofmeasure-alt_unit                  = 'HR '.   "gwa_itab1-brgew.
        gwa_unitsofmeasurex-alt_unit                  = 'HR '.  "'X'.
        gwa_unitsofmeasure-unit_of_wt                  = 'KG'.    "gwa_itab1-brgew.
        gwa_unitsofmeasurex-unit_of_wt                  = 'X'.
        gwa_unitsofmeasurex-sub_uom                  = 'X'.
        gwa_unitsofmeasure-gross_wt                  = gwa_itab1-brgew.
        gwa_unitsofmeasurex-gross_wt                  = 'X'.
    *appending workarea to table's
        APPEND gwa_materialdescription    TO gt_materialdescription.
        APPEND gwa_taxclassifications     TO gt_taxclassifications.
        APPEND gwa_prtdata                TO gt_prtdata.
        APPEND gwa_prtdatax               TO gt_prtdatax.
        APPEND gwa_unitsofmeasure         TO gt_unitsofmeasure.
        APPEND gwa_unitsofmeasurex        TO gt_unitsofmeasurex.
    *calling FM BAPI for uploading the Material master data
        CALL FUNCTION 'BAPI_MATERIAL_SAVEDATA'
          EXPORTING
            headdata            = gs_bapimathead
            clientdata          = gs_clientdata
            clientdatax         = gs_clientdatax
            plantdata           = gs_plantdata
            plantdatax          = gs_plantdatax
            forecastparameters  = gs_forecastparameters
            forecastparametersx = gs_forecastparametersx
            valuationdata       = gs_valuationdata
            valuationdatax      = gs_valuationdatax
            salesdata           = gs_salesdata
            salesdatax          = gs_salesdatax
          IMPORTING
            return              = gs_return
          TABLES
            materialdescription = gt_materialdescription
            unitsofmeasure      = gt_unitsofmeasure
            unitsofmeasurex     = gt_unitsofmeasurex
            taxclassifications  = gt_taxclassifications
            prtdata             = gt_prtdata
            prtdatax            = gt_prtdatax.
    Check the return table.
        IF sy-subrc NE 0.
          CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
          WRITE: / 'Error occured while creating material'.
        ELSE.
          CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
          WRITE: / 'material',gwa_itab1-matnr,'created'.
        ENDIF.
      ENDLOOP.

    Hi Aparna..
    even with HUR also i am getting same error.....
    is there any changes required in the SPRO .......
    i mean in BAPI had ..unitofmeasure we have around 21 fields( here extra fields is DEL FLAG)
                          but in unitofmeasurex has only 20 fields...
    we need to anything in SPRO for avoiding DEL FLAG.....
    sorry if i am confusing u.....
    thanks for responce and send few more inputs for resolving the issuee....

  • Unit of measure with language Key

    Hello Guruz,
    WHile creationd of purchase order, there is a check kept which compares the vendor communication language which gets updated in the Po header - Communucation tab with Db table T006A which holds the Unit of measurements with Language Key and pops up an error message.
    It cheks the order unit in the PO, and the T006A whether the unit is maintained in the Language key as in the PO header - Communiction tab.
    But while creating a unit of measurement in CUNI, we dont have the option to maintain the language key for the UOM.
    In CUNI, it defaults the language key as EN in table T006A.
    I need a prompt support from you guys on this issue. Please suggest how to go about with this?
    Best Regards
    Greg.

    Hello,
    When i am trying to go for the language key in CUNI, it says that the said language is 'not available in server'. I guess it is checking whether the language patch is updated in the server.
    But it doesn't sound logical to maintain all the unit of measurements in all the vendor languages. Suppose if we are having vendors with 75 communication languages and we are having 50 units os measurements, so does that mean that we have to maintain units of measurements 75 X 50  times ?
    Kindly provide your inputs on the issue. We are facing lots of issues with this control kept in PO header checking for the T006A with the vendor communication language.
    Regards
    Greg

  • Unit of measure PCS not defined for language FR

    Dear Gurus,
    I try to raise a PO in ME21N, when saving the order, I am being prompted by the system with the following message:
    "Unit of measure PCS not defined for language FR"
    I then went to MM02 to check the material master data "Sales Text" Tab.
    There the only language available is English, so I clicked on the "Language Maintained" Tab and created a new language for French.
    The problem is that when I want to save the changes, the system prompts me with the following message:
    "Blank texts exist in the following languages: French and English, these texts will be deleted"
    Then the Material Master Data closes and no changes have been made.
    Can you please guide me through step by step of what I have to do to be able to populate the field "PCS" for pieces in French so that it is taken into account in the Material Master Data and by extension in a PO.
    Thanks for your help.
    KInd regards
    Chris

    Hi Chris,
    Goto T code CUNI. In the first screen click on GOTO-Translation-dimension.
    Enter EN in Source language and FR in Target.Maintain the entry there.

  • PM Order Operations Default Unit of Measurement

    Halo Experts,
    We have a problem in UOM for PM/CS order operations. We have defined HR as default value of UOM for operations in IMG.
    Business wants to change at the order level to H as UOM and it is manually keyed in and saved. But when we check with the F4 option for Unit of Measure " H" doesnt appear where as HR appears.
    Any restrictions in displaying all the unit of measures. Can anybody clarify why "H" is not appearing on F4 option in the work order operation line items.
    Regards,
    Selva

    Hi Rajesh,
    We are getting the default unit in operation tab and all the config of default values is available but when we execute the F4 option the unit "H" is not appearing where as if we change from HR which is a default unit to H it is getting saved at the operation Tab.
    Hope it is clear now.
    Regards,
    Selva

  • MMBE-i want display (1 box = 10 pc) in unit of measure

    Dear All,
    In MMBE t-code if we execute it,stock overview we can c as a report output.Displays Base unit of measure as(PC,EA....) here i want display (1 box = 10 pc) Which we ll give it while creating a material in mm01-purchasing.
    There is no exits for this t-code so is there any options that functional people can enable to view it in output or any developments to do here.
    Or in any other T-code we can display it.
    <removed_by_moderator>
    Edited by: Julius Bussche on Jul 28, 2008 10:29 AM

    hi,
    ask your mm consultant.....he needs to configure...

Maybe you are looking for