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

Similar Messages

Adding Alternative Unit of Measure to Outbound idoc

Hi gurus,
I need to add alternative unit of measure information to an outbound ORDERS idoc for each line item segment. How do I know what segments and qualifiers to use?
Thanks!
Will

Hi Will
Unit of measure at item level is in
Segment --> E1EDP01 : IDoc: Document Item General Data
Field --> MENEE : Unit of measure
Do you want to convert the Unit of measure in outbound idoc?
Use conversion rules for this...
or
do you want send Unit of measure and secondary unit of measure ??
extend the idoc type and write user exit to populate date in extended segment...
i hope above info helps you
Thanks
RAMESH

Adding Alternative Unit of measure as part of attributte of material

Hi gurus,
In our source system each material has alternative unit of measure which contain info on converting the base unit of measure (CAR) to MT and PAL.
I need to add this info as part of material attribute
e.g.
Material "A" 10CART = 1 PAL & 100CART = 1MT
This information captured in MM table "MARM" with material code as the
As part of 0MATERIAL_ATTR , i need to have additional field that capture the info as below
CARTPAL = 0.1 (1/10)
CARTMT = 0.01 (1/100)
Please help to advice on how to enhance the extractor to cater the above requirement.
Your help highly appreciated
Thank you

hi,
According to me you can enhance the 0Material_attr to bring the required information from ECC.
But before enhancing anything ask func consultant or business below ques.
1) will these unit entry will get created in MARM for any material at the creation of material or it will get updated later on
2) will this unit value get change for any material during its entire life
If any of above que ans is yes then how wud u manage in transaction data if unit get changed.
For that u need to apply feedback concept in transaction dso.
Regards,
Ashish

Adding alternative unit of measure field in Internal Goods/services link

Hi Experts,
I have a requirement to display an Alternative unit of measure in the Add Internal Goods and services link of ADD ITEM tab in Shopping Cart which comes when user clicks the product id hyperlink of INTERNAL/GOODS AND SERVICES.The Alternative unit should be displayed beside the field Quantity unit .
If anyone has worked on this, Could you kindly help me out on how to proceed further ?
Thanks in advance,
umabalam.

Dear Poster,
As no response has been provided to the thread in some time I must assume the issue is resolved, if the question is still valid please create a new thread rephrasing the query and providing as much data as possible to promote response from the community.
Best Regards,
SDN SRM Moderation Team

Adding Alternate Unit of Measure to MB5B tcode

Hi,
We need an AUM option in selection screen & Output of MB5B.
Users can know what was available in stock on a prior day when trying to re-concile inventory?
Is there any Standard setting to do this kind of things or will it be possible only with Z REPORT?
We still have some standard reports like this for which users are asking like MC.A,MC.B etc..This is because recently we went live globally.
Any ideas?
Regards
Vara

Hi Vara,
I am not quite sure but hope if u use tcode MASS and then use BUS1178001(mass maintenance)and give ur UOM..so tht u can change the AUM for all materials u need...
sry if it doesnt work...its just an idea...
sony

Is it possible to manage 3 units of measure (not just 2) using IS CWM

Our customer requirement is to handle the stock in 3 different units of measure.
We have read that with the EHP7 CWM (Catch Weight Management) this is possible but we are not sure if it's possible with 3 units of measure.
If not any other alternative?
Many Thanks
You can contact me at: [email protected]

CWM supports only one parallel unit of measurement as the valuation unit of measure. It however allows adding several unit of measure as in standard ERP system.
Hope this helps.
Baseer

Order forecast Monitor screen will it pick base UOM or any other unit of measure?

Hi All,
In OFM screen showing only qty against key figures but UOM not showing.
I would like to know in OFM screen whether always qty will show in base UOM or any other unit of measure?
please can you suggest on this.
Regards

Venkat,
SNC supports multiple UOM (Base UOM and Document UOM) only for the below Screens:
● Detail screen for purchase orders
● Detail screen for replenishment orders
● Detail screen for invoices
● Detail screen for advanced shipping notifications (ASNs)
● Query To Be Confirmed for the purchase order worklist
Ref :
http://help.sap.com/saphelp_snc700_ehp02/helpdata/en/46/9c3cff7ded371ae10000000a11466f/content.htm?frameset=/en/46/827d1…
So, OFM screen data will always be in Base UOM only.
Regards,
Bharath

My new apple ipad 2 screen jumping all over the place and adding extra letters to stuff

My ipad won't let me sign into my itunes account because it keeps adding extra letters to my username and password making them invalid also when I try to use apps it jumps between screens and loads different apps and pages by its self.

Resetting, rebooting, same thing really. Hold down the home key (the circular one on the bottom front) and the sleep key (the power button on the upper right edge) together for about 20 seconds. You'll see the screen go black then a silver apple. Once you see the silver apple, release the buttons and let it reboot. See if that helps.

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

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

Material Ledger Unit Of Measurement different from Material Master

Dear Team,
In my client, there is a difference between unit visible in CKM3N and MM03. The base unit of measurement in MM03 is MT. Other than that, there are some other units maintained (not M3) in additional data tab in material master. In CKM3N, the visible unit is M3. M3 is not present anywhere in MM03.
Why would such unit flow in material ledger table? (CKMLPP has unit M3). Please advise.
One more observation is that when there is some price change document in Material Ledger, the proper UoM (MT) is being captured. Only in the basic price determination structure visible unit for each head is M3. Please check the attached screen shot.
Any help would be appreciated.
Thanks.
Jay Shah.

Hi..
Refer to Data Inconsistency of BUOM in Material Ledger Tables

Unit of Measurement Field showing Gray while created asset master

Dear All,
When I am try to create the asset sstem is showing the Quantity Filed but the Unit of Measurement is showing in Gray.
I also check the screen layout rule but still it not coming as an input field.
Kindly help me out to resolve this ASAP.
Regards,
Sandeep

Hi,
Please check the screen layout assigned to the asset class under which you are creating the assets and then check the screen layout rules of that screen layout whether the field "Unit of measurement" is optional or not.
Thanks Monoj

Unit of Measurement is blank - Text material in Sales Order -

Dear Experts,
We need to trigger a PR from a text item in sales order.
Only problem we are facing is an error message saying "Enter Order Unit". But there is no value in F4 help for order unit. There
is no permissible value for unit of measure in F4 help, as it is derived from material master.
Thanks
Shri..

Dear Expert,
Here is the exact requirement. We want to trigger a PR for procurement of services from a sales order. To trigger a PR for services and use service entry sheet for service confirmation we need to use item category D-Services in the PR and PO. Item category D does not allow a material to be entered as there will be no invetory tracking for this services. This is standard SAP property for item category D in the PR.
Just to add. If the item category has schedule lines allowed field marked it will not grey out the quantity and UOM field in sales order.
I tried adding the UOM in the debuggin mode and everything is working fine. Need to know if there is any standard setting to achive this.
So to trigger a PR only with a text line from a sales order you need to have a sales order line item only with the text and trigger a schedule line category with the order type NB, Item category as D and account assignment category as R.
Thanks
Shri..

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 for calculation type C must be completed

Hi All
When releasing some contracts in SRM , we are getting the error message as above.
The error message doesn't specify any particular part and the contract has more than 3000 parts.
There are no conditions at header or item level.
There is no Target quantity also. Just a Target value for the contract and prices for individual items are maintained.
We are using extended classic scenario and the contract is manually created in SRM.
I have checked the OSS notes for this error, but they are mostly for contract creation in Bidding and not for a manually created SRM contract.
We checked the UOMs for all the contract parts with the UOMs ( Base and Purchasing) in ECC Material Master and they are OK.
In our scenario , MM changes in ECC are replicated to SRM in real time
Any pointers towards pin pointing the error will be rewarded!
Regards
Kedar

Hi,
We encountered this error message and resolved the problem by applying the following 3 SAP Notes:
a)     Note #1022928 - Unit of Measure for Calculation Type C Must Be Completed
        (Previously Mentioned)
b)     Note #1702484 - Unit of Measure for Calculation Type C Must Be Completed
c)     Note #1517648 - Default Conditions Added for Product Category Item Type
Although the contract required is similar to a "Limit" item, but had to be placed for bid, then the RFX PS Item Type was set to "Service" to receive the bid responses. After accepting the bid response, then we created a contract from the bid response. Since it was to be a "Limit" type contract, then we immediately removed the data from the following fields:
Remove the Quantity
Remove the Unit of Measure
Remove the Price
Remove the Price Condition
After removing the values from these fields, then we switched the PS Item Type from "Service" to "Product Category". We added the Guaranteed Minimum and account assignment data to encumber the funds. We were able to "Release" the contract successfully.
Bob Zinsmeister

Adding extra unit of measure to LS26 screen

Similar Messages

Maybe you are looking for