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

Similar Messages

Error: In language EN, the internal unit of measure DA is not maintained.

hi
i am doing subcontracting operation and when i try to convert the PR into p.o in co02 the system gives this error
In language EN, the internal unit of measure DA is not maintained.
how can i solve this error...

Hi,
There are couple of things..
1. PR to PO Creation is not with T.Code: CO02.
2. It seems you are working on Multi Global environment.
Ask your Basis Team to do the Language imports for UOM.
Regards,
Siva

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

Units of measure

We're connecting our SRM system to another R/3 backend system. When looking at the units of measure in this backend system, I see table T006A listing the measurements in 3 languages (German, English & French), but not all measurements can be found in all three languages. Some do exist in all 3 languages but not all of them. As we try to synch these with SRM, I need to know if...
1. Do we have to have the measurements in all 3 languages in R/3 as well as in SRM in order for it to work?
2. Of the Commercial & Technical names, which one is displayed by SRM during the SC creation? I assume it's the Commercial but not sure.
My concern is that when a German or French user logs in to shop, s/he may not recognize the measurement abbreviation and will need to assistance in looking up what the abbreviation stands for. So to be able to describe what the code stands for, do we have to create them in 3 different languages?
Regards,
SN

Hi
Please go through this ->
1. Yes. Correct. using Tcode- CUNI.
2. Commercial name
UOM are stored in an internal format. At the display time, this format is converted to language dependant commercial format. If not possible *** is displayed.
Check table T006A to see maintained entries for internal unit (say PAK, etc..).
Use transaction CUNI to complete it for all langauages, English (EN), French (FR), German (DE), etc...
Your Unit of Measurement don't have description in required langauge (German, Spanish) language.
Log on to SRM and backend system in (German, French, Spanish) languages and run transaction CUNI.
Find the correpsonding Unit (say ZTO) and fill ISO Code text and Measurement unit text.
Also, Try to keep measurement unit <-> ISO code assignments unique.
Please confirm that ISO codes and especially UOM configuration have been correctly maintained in english in SRM as well as in R/3 (transaction CUNI)
You can simply maintain the same UOMs by configuring them in transaction CUNI. Additionally you can do a remote compare/adjust to synch the data in the systems if you have a large volume of changes.
You just need to make sure that the units of measure in the SAP
Enterprise Buyer system correspond to those in the backend system.
Path in the Implementation Guide (IMG):
SAP Web Application Server--> General Settings -->Check Units of Measurement
Related links to go through ->
Re: Need help on EBP unit of measure error
Re: Internal Unit of Measurement
Re: Setting up UOM's
ISO Code & Multiple UOM
Re: internal unit PAK, language EN is not maintained
Re: No price in shopping cart from catalog with non-EA order unit
Replicating UOM from ECC to SRM
Re: UNIT OF MEASAUREMENT
Additional SAP Help links -> Please refer to this link for Data replication.
http://help.sap.com/saphelp_srm50/helpdata/en/70/00c73a584611d6b21700508b5d5211/content.htm
http://help.sap.com/saphelp_srm50/helpdata/en/5d/b18139a17cd02ae10000000a11402f/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/7e/1d2b3df1e5cc40e10000000a114084/frameset.htm
Hope this will definitely help. Do let me know.
Regards
- Atul

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

How to retrieve the values from a table if they differ in Unit of Measure

How to retrieve the values from a table if they differ in Unit of Measure?

If no data is read
- Insure that you use internal code in SELECT statement, check via SE16 desactivating conversion exit on table T006A. ([ref|http://help.sap.com/saphelp_nw70/helpdata/en/2a/fa0122493111d182b70000e829fbfe/frameset.htm])
If no quanity in result internal table
- There is no adqntp field in the internal table, so no quantity is copied in itab ([ref|http://help.sap.com /abapdocu_70/en/ABAPINTO_CLAUSE.htm#&ABAP_ALTERNATIVE_1@1@]).
- - Remove the CORRESPONDING, so quantity will fill the first field adqntp1. ([ref|http://help.sap.com/abapdocu_70/en/ABENOPEN_SQL_WA.htm])
- - Then loop at the internal table and move the quantity when necessary to the 2 other fields.
* Fill the internal table
SELECT msehi adqntp
INTO TABLE internal table
FROM lipso2
WHERE vbeln = wrk_doc1
 AND msehi IN ('KL','K15','MT').
* If required move the read quantity in the appropriate column.
LOOP AT internal_table ASSIGNING <fs>.
CASE <fs>-msehi.
 WHEN 'K15'.
 <fs>-adqnt2 = <fs>-adqnt1.
 CLEAR <fs>-adqnt1.
 WHEN 'MT'.
 <fs>-adqnt3 = <fs>-adqnt1.
 CLEAR <fs>-adqnt1.
ENDCASE.
ENDLOOP.
- You could also create another table with only fields msehi and adqntp and then collect ([ref|http://help.sap.com/abapdocu_70/en/ABAPCOLLECT.htm]) the data to another table.
Regards,
Raymond

Unit of measurement problem

Hi,
A material has its base unit as "Number" & additional unit as "KG" while creating PR it takes only NO not KG and same follows in PO. How can that be solved?

Hello
It will take NO while creating the PR even if you change in Material master purchasing view. i.e. Ordering unit as KG and also in info record. while creating the PO, the unit will be changed to KG based on conversion factor. After Gr, the system will show the stock in NO as NO is base unit of measure. (stock keeping unit).
If you want to change the base unit of measure, then please refer the following poitns :
As per the SAP standard functionality , We want to change the base unit of measure (base unit). for material master, during the change, the system performs extensive checks in order to avoid inconsistencies in the applications which use the material master .
In particular, the following checks are performed:
The base unit must not be defined as an alternative unit of measure for the material
No International Article Number must be assigned to the base unit
No proportion/product units must be defined for the material
No configurable material must be assigned
The material must not be used as a configurable material-
Stock must neither exist for the previous period nor for the current period -
No physical inventory must be active -
No reservations or dependent requirements must exist for which the deletion indicator is not set
No planned orders must exist -
No purchase requisitions, purchase orders or scheduling agreements must exist for which the deletion indicator is not set-
No WM transfer requirements, no WM quants or no WM posting change notices must exist -
The material must not be a bill of material
The material must not be contained in a bill of material -
The material must not be used as a production resource/tool -
The material must not be used in task lists -
No standard cost estimate must exist for the current or future period
No production orders must exist
No planned independent requirements must exist
No run schedule headers must exist
If the base unit has dimensions, no serial number profile must be assigned
No sales and distribution documents must exist which have status Not processed or Partially processed
Other alternative solution in case of Urgency:
Creation of a new material master similar to the current material and using the new code for further usage.
Warm regards
Ramakrishna

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 Stock and Non-stock Item in CJ20N

When I attach Material to an activity (item Category N Non-stock item) in Project Builder (CJ20N), It is peaking its Base unit of Measure as unit. Now when I try to change it, it is showing an error
Item category N: Only base unit of measure M allowed
Message no. CO344
But for the same material if I change the item Category to L Stock item, then it allows me to change the unit.
Please guide me regarding this Behavior. Is there any customization, by doing which it will allow me do the same for Non-stock Item or It is not Possible.

firstly I am assuming that the activity is internal processing type - doesn't matter really
now to attach a material select actvity and from the template area click and drag material which will open the material detail screen in the work area
because it is a non stock item I am assuming text description - in the requirements qty you enter the qty and next to it the units - changeable
if you choose a material number maintained as material master then obviously the unit will be from the material master.
If you are using an externally processing activity then in config check OPUU for the network type and see if order unit has been populated - that might be the problem

Base unit of measure can not be changed since EAN is already assigned.

Hi,
We would like to change the UOM from EA to SET .In order to tag MM # as BOM Header and ZCEN (Serial number profile)but the error massage appears as below print screensystem is not allowing to do so ,throwing following error message:
"Base unit of measure can not be changed since EAN is already assigned."
Could you help to resolve the same.
Thanks,
Amit

Hi,
Thats correct you must be getting Error message M3 341 ,
EAN international article number is tied with material number in basic data view with EAN Category and seperate number range
EAN is a standardized unit that uniquely identifies a material relating to a unit of measure or type of packaging.
The International Article Number (EAN) is assigned by the manufacturer of the material. In this case, the EAN identifies the
manufacturer uniquely. A company can assign EANs using "in-store" numbering techniques known only to the company.
If you still want to change UOM you need to first remove the EAN assigned..please explore further if you have internal number range
for EAN or external ..etc
Thanks
Diwakar

U2018Ea unit of measure has not been created in the language ES u2018in srm

Dear Friends,
I have checked in ECC & SRM in table T006A (UOM languages). UOM "EA" is defined in ES (Spanish).
Also in comm_hierarchy also i chked for product category language maintenance and found maintained in EN,ES languages.
u2018Ea unit of measure has not been created in the language ES u2018
I have tried with sapanish (international sort,dominic,traditional sort)& rest of spanish spoken country languages but i am getting the same error.( IE- tools-general-languages & refreshed the page). u2018Ea unit of measure has not been created in the language ES u2018
Regards,
William

Hi Willam,
When are you getting this error ? i.e. while creation of shopping cart or process purchase order..
I believe this issue is due to creation of UOM..which means EA UOM should be created with EA language.
For further details please have a look on
http://wiki.sdn.sap.com/wiki/display/SI/UnitofMeasurerelatedsettingsinSAP
where they have specified that "Maintain UOM in different languages by logging to the system with different logon language"
Kindly confirm.
Thanks
Rajesh K

Unit of measure JHR not defined

Hi Friends,
What can cause this problem. I am getting this error message
"Unit of measure JHR not defined" after I am creating a Shopping card in EBP.
JHR is existing on both sides Backend and EBP in the table T006.
Regards
Marco M.

COM_PRODUCT_UNIT
you need to debug this program . JHR is not SAP or international UOM . it could be customised one
COM_PRODUCT_UNIT_READ_API
Is a unit of the product convertable into i_unit?
    CALL FUNCTION 'DIMENSIONCHECK_DIMENSIONLESS'
      EXPORTING
        meinh                       = iv_unit
      EXCEPTIONS
        dimension_not_dimensionless = 1
        t006d_entry_missing         = 2
        t006_entry_missing          = 3
        OTHERS                      = 4.
    CASE sy-subrc.
      WHEN 0.
        MESSAGE e020(com_product_unit) "unit is dimensionless
               WITH iv_unit
               RAISING unit_not_allowed.
      l_lines = l_lines + 1.
        CALL FUNCTION 'COM_PR_UNIT_CHECK_CONVERTABLE'
          EXPORTING
            i_base_unit     = ls_base_unit-unit
            i_alt_unit      = iv_unit
            i_tabix         = l_lines
            it_pr_unit      = lt_pr_unit
          IMPORTING
            e_add_const     = l_add_const
            e_numerator     = l_numerator
            e_denominator   = l_denominator
            e_unit          = l_unit
            e_sub_num       = l_sub_num
            e_sub_denom     = l_sub_denom
          EXCEPTIONS
            not_convertable = 1
            overflow        = 2
            OTHERS          = 3.
        CASE sy-subrc.
          WHEN 1.
            MESSAGE e020(com_product_unit)
                  WITH iv_unit
                  RAISING unit_not_allowed.
   CALL FUNCTION 'COM_PR_UNIT_CHECK_CONVERTABLE'
          EXPORTING
            i_base_unit     = ls_base_unit-unit
            i_alt_unit      = iv_unit
            i_tabix         = l_lines
            it_pr_unit      = lt_pr_unit
          IMPORTING
            e_add_const     = l_add_const
            e_numerator     = l_numerator
            e_denominator   = l_denominator
            e_unit          = l_unit
            e_sub_num       = l_sub_num
            e_sub_denom     = l_sub_denom
          EXCEPTIONS
            not_convertable = 1
            overflow        = 2
            OTHERS          = 3.
        CASE sy-subrc.
          WHEN 1.
            MESSAGE e020(com_product_unit)
                  WITH iv_unit
                  RAISING unit_not_allowed.
          WHEN 2.
            MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                    WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4
                    RAISING overflow.
E        COM_PRODUCT_UNIT       020     Unit of measure & is not defined for product
When do you get this error ? while ordering Internal goods and services or describe procurement?
or while procure from catalog.

Unit of measure in Material Master after PO's created

Hello Everyone,
I know that we can't change the material measure unit once PO's and other documents are created.
What can I do with the PO so i can change the material measure unit?
Thanks in Advance.

From OSS note 138767
Within the material master record maintenance, you want to change the base unit of measure (base unit). During the change, the system performs extensive checks in order to avoid inconsistencies in the applications which use the material master.
In particular, the following checks are performed:
The base unit must not be defined as an alternative unit of measure for the material
No International Article Number must be assigned to the base unit
No proportion/product units must be defined for the material
No configurable material must be assigned
The material must not be used as a configurable material
Stock must neither exist for the previous period nor for the current period
No physical inventory must be active
No reservations or dependent requirements must exist for which the deletion indicator is not set
No planned orders must exist
No purchase requisitions, purchase orders or scheduling agreements must exist for which the deletion indicator is not set
No WM transfer requirements, no WM quants or no WM posting change notices must exist
The material must not be a bill of material
The material must not be contained in a bill of material
The material must not be used as a production resource/tool
The material must not be used in task lists
No standard cost estimate must exist for the current or future period
No production orders must exist
No planned independent requirements must exist
No run schedule headers must exist
If the base unit has dimensions, no serial number profile must be assigned
No sales and distribution documents must exist which have status Not processed or Partially processed.
Solution
If necessary, all reasons mentioned above must be eliminated by archiving the objects listed.

Creation of new unit of measurment

Gurus
How to crete the new unit of measurment which can be used for conversion and what are the tcode.
Atul Kulkarni

Hi,
You can create UoM's by using transaction CUNI.
Check for the right dimension under which the new UoM falls under..e.g.Assign the SI unit (In each dimension, a unit is defined as the SI unit. This is the basis for the conversion from one unit to another.) to the dimension if required.
Create a ISO code.The ISO code is important for EDI. It is used to convert the internal SAP measurement units into standard measurement units.
Define UoM: Be aware to give the correct commercial as well as Technical unit,the commercial unit is used in SAP whereas technical unit you can use in EDI,IDoc.You can assign the ISO code while defining UoM's.Hope this helps!
BR,
Sandeep

Conversion of Unit of Measure in ALV Grid

Hi all,
I am using function 'REUSE_ALV_GRID_DISPLAY' to display some records in ALV grid. The record displays material, the quantity of the material consumed and the unit of measure (UoM) of the quantity. I am fetching the data from the table AUFM and the field I am using for UoM is ERFME.
The problem is that when the UoM is displayed in the ALV, it is displayed as KAR but when i print the report or check the print preview, the UoM is displayed as CAR. I want to display CAR also in the ALV.
I have tried using the function 'CONVERSION_EXIT_CUNIT_OUTPUT' which converts the KAR to CAR in the ALV, but when I print it or check the print preivew , it shows asterisks (*) in the UoM field.
Can anyone tell me why this is happening and how I can solve this problem? Any help will be greatly appreciated.
Regards,
Hamza

Hi Ozkar,
I tried the function 'CONVERSION_EXIT_CUNIT_OUTPUT', it worked fine when displaying the UoM in the ALV, meaning it displayed CAR instead of KAR, but when I printed the list or chicked the print preview, it displayed stars (***) in the UoM field.
Anyway, I tried something else and now it is working fine. I am writing below what I did so that if anyone else has this problem, they can also do what I did.
As I said before, the UoM field was showing KAR instead of CAR in the ALV. So after passing the data to an internal table which would be used to display the data in the ALV, I called the function 'CONVERSION_EXIT_CUNIT_OUTPUT' and converted KAR to CAR. this displayed CAR in the ALV.
Now, to also get CAR in the print out and print preview,I declared variables gt_event_exit and lt_event_exit.
DATA: gt_event_exit TYPE STANDARD TABLE OF slis_event_exit,
           lt_event_exit TYPE slis_event_exit.
The variable will 'lt_event_exit' will contain the function codes of the Print(&RNT) and Print Preview (&RNT_PREV) buttons on the ALV. In the form where I am calling the function 'REUSE_ALV_GRID_DISPLAY', I pass the function codes to lt_event_exit and append it to the internal table gt_event_exit.
lt_event_exit-ucomm = '&RNT'.
lt_event_exit-before = 'X'.
APPEND lt_event_exit TO gt_event_exit.
lt_event_exit-ucomm = '&RNT_PREV'.
lt_event_exit-before = 'X'.
APPEND lt_event_exit TO gt_event_exit.
Next I pass this table to the parameter 'IT_EVENT_EXIT' of 'REUSE_ALV_GRID_DISPLAY'. I also create a form USER_COMMAND and pass this form to the parameter 'I_CALLBACK_USER_COMMAND' of 'REUSE_ALV_GRID_DISPLAY' as shown below.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
   EXPORTING
             I_CALLBACK_USER_COMMAND = 'USER_COMMAND '
             IT_EVENT_EXIT                          = gt_event_exit
What the above does is that, when a user clicks on the print or print preview button, the system instead of printing the list, it passes the control to the form USER_COMMAND. After the form is processed, it prints the list.
In the form, I placed a loop on the internal table containing the data to be shown and simply converted the CAR back to KAR. The code is given below.
FORM user_command USING r_ucomm LIKE sy-ucomm
                          rs_selfield TYPE slis_selfield .
    CASE r_ucomm .
      WHEN '&RNT' OR '&RNT_PREV'.
        LOOP AT i_final .
          CALL FUNCTION 'CONVERSION_EXIT_CUNIT_INPUT'
             EXPORTING
               input = i_final-erfme
               language = sy-langu
             IMPORTING
               output = i_final-erfme
             EXCEPTIONS
               unit_not_found = .
          MODIFY i_final.
        ENDLOOP.
   WHEN .
   WHEN OTHERS.
    ENDCASE.
I hope this is helpful to anyone who has the same problem as I did. Now what I cant figure out is why the system automatically converts KAR to CAR when displaying print preview or when printing the list.
Well, thanks anyway for the suggestion Ozkar.
Regards,
Hamza

Internal Unit of measurement in J1ILIC01

Similar Messages

Maybe you are looking for