Pulse measurement Error

I used the Pulse measurement 1 Chan VI in my project and could see that the VI pops up an error in few cases (Error -20308 occurred at "NI_MAPro.lvlib:ma_ptmFetch.vi:2" when called from "NI_MAPro.lvlibulse Measurements 1 chan.vi:1").
I have attached the data cluster of a failed case. Please let me know, wat is going wrong?
Attachments:
Pulse Measurement.vi ‏16 KB

HI
The data you are passing to pulse measurement vi is very small because of that it is giving the error.
Please find attached image for more detail. I have just appended the same siganl four times
Hope this helps
Regards
Santosh
Attachments:
data.JPG ‏232 KB

Similar Messages

Buffered freq/pulse measurement that can tolerate oversampling

I would like to synchronize a buffered freq or pulse measurement to a continuous AI task using the shared ai scan clock.
The problem is that there maybe times were there are slow to no pulses to measure and the DAQmx driver will throw an error
indicating that multiple samples clocks were received before any pulse measurements could be made. What I would like is to have
the sample clock default to a measurement of 0 and this value would be placed into the task buffer so that it will always be sync'd
to the other tasks.

Duplicate count prevention is a pretty interesting (and probably poorly named) property. With duplicate count prevention disabled, the sample is latched in on the rising edge of the source. If the gate is faster than the source, you could miss the samples that you might expect to read 0 (i.e. imlpicitly-timed buffered period measurement).
This isn't exactly what's happening on the X Series (Duplicate Count Prevention is always "True" for frequency measurements on X Series). The problem is that there is no sample available in the counter FIFO on the edge of the sample clock. I believe the error is thrown by the hardware and there isn't much that NI could change in the driver to correct for it, but I'll investigate a bit more just in case.
In the meantime, you might have to resort to counting edges of your external signal sampled from the AI Sample Clock. If your external signal is high frequency, this would be suitable, but I think it's probably more likely that your external signal is relatively slow so doing this would introduce a very large error. I'll think about this some more and post back if I think of a workaround.
Best Regards,
John Passiak

Can pulse measurement.vi measures 2M points with 10ns time interval?

Hi,
I used pulse measurement.vi to measure the pulse duration of waveforms when the waveforms exceed certain threshold level. The data file has 2 millions data points with 10ns time interval. But I got error message saying that
"The waveform did not cross the mid reference level enough time to perform this measurement. Check the signal length, mid reference level, and reference level unit."
I was wondering if pulse measurement.vi is capable of handling such large file or it was due to my paramenter errors.
Thank you for your help in advance.

I realized that I can't really modify the percent level settings or specfication of the pulse measurement.vi. For instance, I changed the percent level setting to peak instead of the default auto select. After running the VI unsuccessfully and I reopened the pulse measurement.vi, I saw the percent level setting was set to auto select again instead of peak method. I have attached the image of the block digram and a very small part of the waveform data. I hope you can open both.
Thank you.
Attachments:
pulse measurement.doc ‏45 KB
example.txt ‏2 KB

Is my idea feasible?(pulse measurements.vi)

Dear All,
I am using the "Pulse measurements.vi" to analyse the waveform get by DAQ card. And it need at least 1.5 periods of
waveform data. Due to the unknown frequency of the signal, I don't know how to set the sample rate which is too fast
that one time of N sample acquisition won't obtain the enough period for the vi, while too slow that the high
frequency signal will not be get.
So I am wondering that if the sample rate can be adjust dynamic. For example, at beginning a high sample rate is
initialed while if the pulse measurements.vi give error that "the waveform did not cross the mid reference level
enough times to perform the measurement", a lower sample rate will be adjust until the error is not absent.
I don't know if it is feasible or someone have done some experience of this.
If some example vi is absent, would you please attach it? Or if there is some other good way to solve it?
Thank you very much.
Hugo

Lynn,
       Thank you!
       I have modified your vi which runs better
       In the zero case of the inner shift register I wired the new data to it which can measure the waveform dynamicly when I change the frequency during it running
      Thank you for your help!
Hugo
Attachments:
frequency2.2.vi ‏31 KB

Huey Pro calibrator- error message display measurement Error

i am using this huey pro calibration.. it had been a year without problem... but now i am trying to calibrate my apple cinema display LCD 30 inch it keep saying error message- display measurement error.. and huey support never answer my e-mail. any idea? how can i fix it.. i did re install software many times but same thing happen.. so right now i can;t calibrate my monitor.. any help please

>a nice NVidia card... Please help Adobe!
1a - what is the model nVidia card, and what is your driver version?
1b - for instance, I have a GTX 285 and driver 296.10
2a - aside from the occassional Adobe employee, this is a user to user forum, not Adobe suport
2b - how to contact Adobe...
Adobe contact information
http://www.adobe.com/support/contact
In the US - Adobe General support 800-833-6687 M-F 5am-7pm Pacific
In the US - Adobe Install Problems 800-642-3623
In the US - Adobe Activation 866-772-3623 Open 24/7

Huey Pro Calibration Error message- measurement error

i need using this huey pro calibration for year. but now i am trying to calibrate my apple cinema display LCD 30 inch it keep saying error message- display measurement error.. and huey support never answer my e-mail. any idea? how can i fix it.. i did re install software many times but same thing happen.. so right now i can;t calibrate my monitor.. any help please?

Hi,
Which Wireless-Card you used?
Best you use the Cisco CB21AG PCMCIA Card. I had similar problems with intel wireless chipsets
Sincerely,
Frederik

Quick Question On Pulse Measurements

I was wondering what the percents are the percent of on the Pulse measurments.vi Default (10,50,90)%
I understand the low,mid, and high part of the vi. But what are the percents referencing? It it simply % of your largest pulse?
I know it isn't very clear what I am asking but Im not sure how to ask it more clearly.
Link to help doc

johnsold wrote:
Nate...,
Typically the Pulse Measurement VI used on something which looks like a rectangular pulse with a little noise, overshooot, ringing, ... Your signal is not what one would normally call a pulse by that definition.
In the first image you posted how many pulses do you count? 11? The little spikes (amplitude about 0.1 at 3.318, 3.331, 3.341, and others): Are they to be counted or rejected? Do they alwyas occur before a big spike? Some little ones are not followed by big ones but all the bigones seem to be preceeded by a small one. Is there a minimum dleay between successive pulses? Analyzing data like this can be challenging. Use all the knowledge you have about the process which generates the data to help.
Lynn
Hmm, all I had seen was sine waves before with the pulse. But, you seem to be right, rectangular pulses make a lot more sense.
Yes, I am just counting each period. I just was planning on using the pulse vi to measure the giant spikes to count how many of those occur each second. That first graph is a sound wave of a weld shorting. I want to know how often it shorts a second. I currently just have it detecting an absolute value (looking for that giant spike) and however many times it detects that I average and turn into total shorts and average shorts.
It works but it is not very elegant.
And you are correct about some of the small spikes not being followed by a big spike. That is molten slag splashing about. This short one right before the sharp spike is the sound of the arc igniting (300 Amps worth).
Can you think of any more elegant solutions to detecting the pulse? I am going to do some digging around..
Thanks Lynn!

SE30 - Unable to end the measurement (error number 5, Time limit reached)

Hello there,
I wish to perform a complete ABAP trace using SE30 for a program running for 4 hours. The system is R/3 4.6C.
However I got the error message below once I clicked "Back" button or F3 when the program finished after 4 hours.
Please note that ST12 is not available in the system I logged on.
=============================================================
Error message:
"Unable to end the measurement (error number 5, Time limit reached)
Message no. S7 068"
Meas. type           Fully aggregated
Session type         In current session
Status               Time limit reached
Error message text   Time limit exceeded. LIMIT: 1800000000, ELAPSED TIME: 1800957266
File user            XXX
User                 XXX
File ID              ATRAFILE
Release              46C
Version              6
Operating system     HP-UX
Number of processors ???
=============================================================
The ABAP trace results only managed to capture the first 45 minutes of the ABAP calls (due to timeout i think). I would need the whole and complete ABAP trace result for 4 hours, NOT the first 45 minutes. Is there any setting in SE30 can be set for this purpose? Note that there is no ABAP error for the program I traced.
The following link didn't answer my question as well. Hope you can provide clue in this case.
http://help.sap.com/saphelp_nw70/helpdata/en/c6/617cafe68c11d2b2ab080009b43351/content.htm
Runtime analysis, SE30, ERROR
Thanks,
KP

Hi Kim,
The Limit is expliced on the Doc.
http://help.sap.com/saphelp_nw70/helpdata/en/4d/4e2f37d7e21274e10000009b38f839/frameset.htm
It's 4293 Actually and you set it on SE30 by change the Measurement Restrictions, tab Duration/Type.
regards.

Pulse Measurements vi modification

Hi,
I am currently using LabVIEW 7.0.
The pulse measurements vi histogram method uses the 40% lower and upper histograms to find the low and high state levels.
My application requires me to take a look at the 10% lower and higher histograms, does anyone has a suggestion on how to modify that vi to fit my needs?
Thank you

Just to clarify, the 40% refers to the range of the histogram that is searched to find the peak histogram levels (or state levels). Then the reference levels are typically set at 10% and 90% of the resulting range defined by the two peak histogram values.
There is no way to modify the 40% histogram search range in the Pulse Measurements.vi. The alternative would be to perform a histogram separately on your input data and process it according to your requirements. The resulting reference levels can be passed into Pulse Measurements by changing the ref units input of the reference levels cluster to "absolute".

Measurement error in reading Encoder Pulses

I am using PCI-6601 card to read a Linear Encoder which gives 2000 pulses per mm of distance.The accuracy of the Linear encoder is 2Microns.In my application I am measuring a distance of 7mm.But the card is reading with an error of 30 to 50 Microns error.We had checked up all the factors related to mechanical and Encoder.In fact the same application was earlier working with Advantech Encoder card which has provisons to connect the A,B,A Bar,B Bar inputs from Encoder.There was an accuracy of 0 to 5Microns.But the application was replaced with NI Card because of the continuous problem of the Digital I/O Card used from Advantech.
Mail me the possible causes and also the troubleshooting procedures for correcting the above problem

Hi,
What I think is happening is there might be some noise on your signal lines. The PCI-6601 counters are capable of detecting a pulse as small as 20ns. If the Advantech card can't detect pulses at that small a resolution, it might be ignoring "noisy" pulses that shouldn't be there. Are you reading more pulses than you should be or less?
There are a couple things I might be able to suggest to clean up your signal. The counters support several different encoder modes. Try using X4 Encoders. An X4 encoder counter increments or decrements on each edge of channels A and B. Whether the counter increments or decrements depends on which channel leads the other. Each cycle results in four increments or decrements. I believe this X4 mode is more noise resi
stant than the standard mode.
Another thing you might want to consider is applying a filter to the input signals (debounce or deglitch filters). Each PFI line coming from the I/O connector can be passed through a simple digital filter. The filter operates off a filter clock and a fast internal sampling clock. It samples the signal on the PFI line on each rising edge of the sampling clock. A change in the signal is propagated only if it maintains its new state for at least the duration between two consecutive rising edges of the filter clock (one filter clock period). The frequency of the filter clock determines whether a transition in the signal may propagate or not.
6601/6602 User Manual
http://digital.ni.com/manuals.nsf/webAdvsearch/DD0DBB6404BC139886256721007CF16D?OpenDocument&vid=niwc&node=132100_US
Hopefully one of these suggestions will do the trick. Have a good day.
Ron

High freq pulsing and error message

while recording or in playback i hear a pulsing high freq and soon after a message pops up that reads "
error while trying to sync audio and midi". my interface is a motu traveler and there tech support doesn't seem to be responding to the same question to them. everything is set at 44.1hz, i've tried rebooting and a lot of other stuff. does anyone out there know how to fix this problem?

Your MOTU unit needs a reset!
This is for an 828MkII but works on the traveler as well.
* Disconnect the firewire cable from the 828mkII
* Press the Setup knob
* Turn the Setup knob all the way to the right
* Press the Select knob
* Press the Value knob
* Power off the interface and plug the firewire cable back in
* Power the interface back on
pancenter-

System Measurement - Error while exporting to LAW file

Hi all,
We have the SAP ERP 6.0. We started the system measurement on our ECC landscape with the aim to consolidate the results with LAW in Solution Manager. We performed the measurement in our production server and we select System Measurement - Export to Law File and execute, we are having the following error:
Last measurement was not successfully performed (see USMM)
We are having the error despite doing the measurement afresh
Grateful if you could suggest what to do.
regds

Hi all
thanks for all your comments.
We have tested in other system with Basis 14 and it works there. So we are presuming that the error is due to Basis being level 13.
Still, we have informed SAP about the error.
thanks all.

Unit of measurement error

i
hi guys
crested po with unit of measure kg and also made migo,miro and RFQ but now when i change unit of measurement from kg to pc in material master there is error
the base unit of measure cannot be changed choose display errors
1 if there are no stock of the material in the current period and in the previous period if there are stock in the previous period you can clear them as follow
-post the stock in the previous period to the current period so that the stock for the previous period is the same as the stock for the current period
-clear the stock with the posting date in the previous period
-if no purchase order exist for the material
i have already made po migo,miro, RFQ , please can you guide me step by step how to change the unit of measurement
thanks in advance

Hi
Goods issue the particular material to some cost center. Then there will not be any stock for the particular material. Then change the UOM.
It will work out.
Then reverse the Goods Issue.
Regards,
Raman

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 Error in Purchase order

Hi Gurus,
While saving the Purchase order i am getting the Error message
"Unit of measure KG not defined for language GB."
We are trying to place this PO outside the US .PR already created and released.But when i am converting the PO and saving it gives me this error .
Thanks a lot in Advance
Edited by: Metroid01 on Jul 23, 2009 12:55 AM

How do i create the UOM in CUNI for the specific language? I can see the below
Int meas unit---->KG
Display
Commercial--->KG
Technical----> Kg(in Po it is taking g is lower case)
in ALE/EDI--->ISO Code is EA.
Can you check this if it is the right set up in config.
Thanks a lot for the help.

Pulse measurement Error

Similar Messages

Maybe you are looking for