Measure period and pulse duration of ttl level continuously

Hello,
i want measure the period and pulse duration continuously of two signals with an usb-6009. Every 8s there is a high pulse for 15ms. I want to measure length of the pulse and  pause. Can someone help me? I can`t get a start up with this problem.
The four measurements (two channels two measurements per channel) are a dataset. This dataset should be stored in a textfile continuously. But this not a problem.
thankyou
Schwede

 Hi Schwede,
Thanks for the update - Im now back in the office!
I have some bad news, your using the wrong device - you need a device with at least two counters - to acquire for two signals. But, secondly,(see specs), the counter measurements support by the USB 6009 doesn't include pulse or width measurements.
The specs for the USB 6009:
Counter
Number of counters ................................1
Resolution...............................................32 bits
Counter measurements ...........................Edge counting (falling-edge)
 To acheive the functionality you require I would recommend a USB 621x: 
Number of counter/timers ............... 2
Resolution ....................................... 32 bits
Counter measurements.................... Edge counting,
pulse,
semi-period,
period,
two-edge separation
Also, this link is rather useful also:
How Many Counters Does Each Type of Counter Input or Output Task Take?
http://forums.ni.com/t5/forums/replypage/board-id/170/message-id/363123
Please let me know if you have any other questions.
Kind Regards,
Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help!

Similar Messages

  • How to measure the pulse duration of a TTL signal using AI?

    Hi there.
    I would like to know how to measure the pulse duration of a TTL signal using an Analog input.
    These TTL signals comes from an ultrasonic sensor's output. The pulse width of the signal is
    proportional to the distance of the object the sensor detected.
    I have tried using the example "Measure Pulse Width.vi" which uses a counter to measure the
    pulse duration instead. It provides me with correct results.
    However, i will like to know how can i do it using the AI instead.
    I tried it by using the example "Acq&Graph Voltage-Int Clk.vi" which i modified by including a
    timing and transistion measurement vi. Pulse duration was selected as the output. A graph indicator was also added at the output of the pulse duration to monitor the incoming TTL signals.
    However, everytime the TTL signals was detected on the graph indicator, the numeric indicator always produce a "zero" reading.
    I have attached my vi for your reference.
    Can anybody advice me what i have done wrongly?
    Regard.
    Attachments:
    Acq&Graph Voltage-Int Clkv1.vi ‏190 KB

    Hi Paul,
    Today i tried using 2 different methods to read the pulse duration of my sensor signal.
    Both methods use "Acq&Graph Voltage-IntClk" vi as a guide.
    Method1:
    Add a filter vi(lowpass/bandpass) and a timing and transition measurements vi.
    Pulse duration is selected as the output. With some numeric conversion, a centimeter
    reading indicator was created. However, the reading always remains as "zero"
    Method2:
    Add a Mask and Limit Testing vi and a timing and transition measurements vi.
    By adjusting my upper and lower limits, i manage to "filter" a single pulse out from the actual signal.
    However, like the earlier case, the cm reading still remains at "zero"
    I have attached both the methods resulted waveforms for your reference.
    Are there anything that you can advice on?
    Regard.
    Attachments:
    Results_Waveforms.doc ‏141 KB

  • How to make a PWM period of 20 ms and a pulse duration 0,8-2,0 ms

    Hi
    How to make a PWM period of 20 ms and a pulse duration 0,8-2,0 ms. deskret pulse length 0.01 ms. for MCB2300. Are there examples of such implementation?
    thanks

    Sergiv,
    I see you as having two options (if you want finer resolution):
    1) Lower the period of the PWM (such that the percentage values would be of finer resolution with regards to the overall PWM period).
    2) Alter the duty cycle of the PWM with an Inline C node.
    From what I understand, LabVIEW simply calls into the PWM driver distributed by Keil (for the MCB2300).  You can call into the PWM driver directly and/or change register values on the chip if you want in order to do whatever you want.  Both would require you to look through/program in C code.
    Kevin S.
    Applications Engineer
    National Instruments

  • Pulse duration measurement of a single, non-periodic pulse

    New to Labview. I'm trying to measure pulse duration of a single, Power- On-Reset, pulse using waveform data. The Pulse measurements VI requires two consecutive mid ref level crossings in the same direction. I have only one positive going mid ref level crossings & one negative in the waveform data. Am I missing something easy in the Waveform Measurements palette or do I need to use counters to accomplish this task? I would like to use waveform data. 
    Labview 8.6 Professional. 

    You could use the Transition measurement.vi twice, as shown on the attachment.
    Message Edité par chilly charly le 09-01-2008 07:04 PM
    Chilly Charly    (aka CC)
             E-List Master - Kudos glutton - Press the yellow button on the left...        
    Attachments:
    Pulse duration.vi.zip ‏16 KB
    Pulse duration_BD.png ‏11 KB

  • Measuring period of a pulse

    Hi
    I m measuring period of a pulse coming from a magnetic proximity sensor. There r two porblems.
    1. I want to monitor the data coninuosly in a while loop but the moment it waits for pulse it doesn't stop and hangs for some time....
    2. While monitoring the data , sometimes high values appear ....... but these values are unwanted. Once if i want to filter out thse values and see only the exact pattern , how to make it...
    PLz. do answer these queries at earliest......
    Thanks and regards
    GNS

    Hi,
    To monitor data continuously without hanging:
    1. Configure your counter to do "buffered period measurement"
    2. In your loop, query the counter for "available points" using "Counter Get Attribute.vi"
    3. When == 0, do nothing. When > 0, read that # of points from the counter buffer. This way, you're never asking for any data that isn't already there and your loop won't ever have to hang and wait for it.
    4. Accumulate/store/graph your data according to the needs of your app.
    To filter out unwanted high values:
    First, I'm assuming that your "high values" are high frequencies, thus small periods. If so, these may be caused by sensor and/or electrical noise. The best thing to do first is try to reduce/eliminate the noise at its source. Failing that, there *may* be a way to make good estimates of the correct data, but it could get pretty tricky. Here's an outline of a way to think about and deal with the simplest case -- where you know the expected measured frequency and it's very nearly constant over time.
    The characteristic of such a noise glitch would be a a pair of transitions in rapid succession, either low-->high followed by high-->low or vice versa. Either way, you'll pick up one of those transitions in your buffered period measurement. The trouble is that it may happen anywhere within the nominal period, possibly more than once.
    Let's first look at a case where the nominal period is 1 msec +/- 20% and there is one glitch of duration 0.1 microsecond, occurring at the 70% point of the real period. The measurement should show one period of duration 1.0 msec, but the noise glitch will cause you to receive instead two periods of duration 0.7, and 0.3 msec.
    The simplest correction would be to simply trash all measurements outside the acceptable range of [0.8, 1.2] msec, including these two. Note however that a noise glitch occurring at the 90% point would lead you to trash the 0.1 msec measurement, but believe and keep the 0.9 msec measurement. Note also that if noise glitches are distributed randomly in time, you would end up keeping 40% of such erroneous data (glitches in either the first 20% or final 20% of the real period).
    Another correction would be to estimate the period interrupted by the glitch. Start by assuming no more than one glitch per legitimate period. Since the glitch subdivides the true period into a pair, you can re-create the true interval by summing the pair of periods. The catch is to identify which pair needs summing.
    The smaller of the pair will show a period <= 50% of the real period, and can be identified. However, the larger of the pair cannot always be identified. The larger of the pair can be anywhere from 50%-99.999% of the real period and may located either right before or right after the smaller of the pair. If you wish to recreate the real period, you'll need to make a mathematically educated guess about which adjacent period to consider as the "larger of the pair."
    This is tricky enough as a post-processing exercise, but it's even worse when you process the data as it comes in. Then there will be times where the last element in the buffer is the "smaller of the pair" and you don't yet have the "larger of the pair" data. There will also be (rarer) times when the last element is the "larger of the pair" but you can't yet know that it needs to be summed with the next "smaller of the pair" measurement.
    Now consider a case where there could be two or more glitches inside true period. You'll need to evaluate the best choice of summing any two, three, four, etc. consecutive periods to reconstruct the real period. {note that for n glitches and a +/-20% acceptance criteria, then (2/5)^n of the glitched intervals will produce one measurement within the +/-20% bounds.} In such a scenario, I would advise working *really hard* on eliminating the glitches at the source.
    Whew, that's a mouthful and a half! Reply if you'd like an outline for an alternate approach, involving buffered semi-period measurement...

  • Measure the Pulse duration by using NI PCI6250 counter module

    Hai All,
    For my application i need to measure the pulse duration from encoder signal.Encoder PPR is 1024. Maximum speed is 4500 rpm.Encoder signal is connected with NI PCI6250 card Counter input. If i configured my NI DAQ task as a Pulse duration measurement icant able to get prober pulse duration. Pulse duration some times reads as zero or near to zero and values also varies. I dont want average pulse duration. I need each pulse duration.Can any one help me to solve my problem?...
    Regards,
    Vijay.  

    Can any one Help me to solve the above problem
    Regards,
    Vijay

  • Low frequency pulse duration measurement

    We have low frequncy pulse duration measurement to be done . We have tried with pulse measurement but it shows error for the frequency bellow 1.5 Hz. We have input signal of frequency varie from 0.5hz to 3 hz .Please suggest us is there any other method that can be used for mesureing the pulse width with low frequency mentioned above .If this can be done using tick count , please send us the example .
    Regards,
    Sharanu

    Hello Sharanu,
    I'm not sure you will be able to measure a frequency below 1.5 Hz in
    the traditional way.  However, I would like to ask you some more
    questions about your system.
    1) What hardware are you using?
    2) What is the error you are receiving (please include the exact error text)?
    Eric
    DE For Life!

  • Keithley 2636 measures current and 2400 offers a 3 volt pulse synchronized in a labview program

    Hello,
    I am not very familiar with labview and I neet a program to realize keithley 2636 measuring current and 2400 offering a 3 volt pulse synchronized.
    It means that when 2636 measure one times, 2400 give a pulse. When 2636 measure 100 times, 2400 offers 100 pulses synchronized.
    The Channel A of 2636 is used for measuring and Channel B is used for another works.
    The attatchment is the labview program I created and it can not be run synchronized.
    Thanks for your help!
    email:[email protected]
    Attachments:
    repeat04.vi ‏38 KB

    Hi Lin,
    I did not talk about a GPIB (or similar) cable to connect both devices with a PC, I did talk about the special cable for synchronizing both devices with each other called TriggerLink!
    Please read the user manual of your K2400, (chapter 11 on triggers, or figure 1-2 for a view of the rear panel). It describes the TriggerLink capabilities of Keithley devices!
    RTFM!
    Best regards,
    GerdW
    CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
    Kudos are welcome

  • Measure Period with error out.vi

    I am using LV6.0. Can Measure Period With Error Out be found in the functions panel? If not where it is? If not there can it be imported into LV6.0?

    labview1958,
    Are you looking for a specific VI called Measure Period with Error Out.vi or are you asking about any general function that can be used to measure the period of a signal and includes error handling? If you are looking for a specific VI, I'm unaware of it, so I won't be much help there. If you're looking for any function to do it, have you looked at the VIs called Measure Pulse Width or Period.vi or Pulse Width or Period Meas Config.vi? They are located in the Data Acquisition>>Counter palette. The Measure Pulse Width or Period.vi does not include error handling, but it would be extremely easy to add it. The Pulse Width or Period Meas Config.vi DOES contain error handling, but it only configures the counter to measure the period, it doesn't actually measure it. These, of course, are for TTL signals coming into your hardware device. If you are reading waveform data from a file and want to calculate the period of that signal, these won't do much for you. So what exactly are you wanting to take a period measurement on, a physical signal, physical signal data points from a file, or some other method?
    Tyler S

  • Measuring point and characteristics

    what are the measuring points and characteristics to be created for the thermal power station , sap plant maintenance

    Hi,
    Its based on the equipments in Power Station & Parameters to be measured for the Equipments. For example, for Boiler, Temperature, Pressure, Water Level, etc., will be measured.
    So here we need to create Characteristics for all these. For Boilers, Measuring points will be created for these characteristics.
    Equipments under Thermal Power stations could be Boilers, Transformers, Electric Generators, Coal Turbines, Condensers, etc., For each equipment, there will be different critical parameters to be measured on periodical basis.
    Create Measuring points for all of them.
    Regards,
    Maheswaran.

  • BPC 7.5 Periodic and QTD issue on YTD Application

    All,
    Our BPC 7.5 SP 6 YTD BPC application has an issue when running EVDRE reports using Periodic or QTD measures.  YTD EVDRE reports produce correct results.  The Periodic and QTD measures work just fine as long as there is data in every period but as soon as no data is found in a subsequent period the system can not do the calculation.   It does not know how to take 'nothing' and then subtract a prior period value.  It somehow needs to treat the non existance of a record as 0 but it does not do that.  For example if the YTD May balance was 100 and YTD June was 500, if you request the periodic value for June it will take 500 - 100 and give you a 400 result which is correct.  In my second example, let's say YTD May balance was 100 but the balance went to 0 in June.  BPC does not load 0 amount so there is no record in June.  If you run a report requesting the June periodic value you will get no result as it can not handle the situation where there is no record in June.
    A while ago I worked with SAP on this and was advised to install OSS note 1405993 which FIXED that problem.  Great news until at a later date our periodic reports stopped finishing and would give the message 'EVDRE encountered an error reading data from the web server'.  It would retry in 30 seconds and error over and over never finishing.  I again reported this to SAP who gave me more efficient Periodic and QTD formulas via note 1505778.  I installed the more efficient formulas and the EVDREs now finished but it brought back the original problem where Periodic/QTD reports would produce incorrect results if there was not data in all periods.  I again reported this to SAP without success.  I have been advised to do the calculation myself in the front end (e.g.EXCEL) which just seems unaccepable.
    I have found another thread http://scn.sap.com/thread/3203570 <http://scn.sap.com/thread/3203570 where this same problem occurs in BPC 10.0 - very sad to hear that!  In that thread people have talked about using 'custom' formulas and say they work.  The formulas I have in place are the ones found in note 1505778 to calculate periodic and QTD.  Yes, I created the formulas for the Periodic and QTD measures but I did it based on direction from SAP.  Is that what everyone refers to as a 'custom' measure?  Does anyone have other formulas where they somehow tell the system how to handle the issue if there is no data found in a subsequent period when trying to run periodic or QTD reports on a YTD system?  If so I would be most grateful if you could share them or any other details you have on the subject.  Thank you.
    Thank you,
    Vicki Shrontz

    Easy, just remember that my TIME dimension name is PERIODS and my ACCOUNT dimension name is INACCT:
    For YTD cube (in my sample) we have 3 measures:
    YTD:
    MEMBER [MEASURES].[YTD] AS 'IIF(([%INACCT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="INC" OR [%INACCT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="LEQ"),-([MEASURES].[/CPMB/SDATA], CLOSINGPERIOD([%PERIODS%].[LEVEL02])), ([MEASURES].[/CPMB/SDATA], CLOSINGPERIOD([%PERIODS%].[LEVEL02])))' SOLVE_ORDER=3
    PERIODIC:
    MEMBER [MEASURES].[YTD] AS 'IIF(([%INACCT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="INC" OR [%INACCT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="LEQ"),-([MEASURES].[/CPMB/SDATA], CLOSINGPERIOD([%PERIODS%].[LEVEL02])), ([MEASURES].[/CPMB/SDATA], CLOSINGPERIOD([%PERIODS%].[LEVEL02])))' SOLVE_ORDER=3
    MEMBER [MEASURES].[PERIODIC] AS 'IIF(([%INACCT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="INC" OR [%INACCT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="EXP") AND NOT ([%PERIODS%].CURRENTMEMBER.PROPERTIES("2/CPMB/PERIOD")="TOTAL" OR  [%PERIODS%].CURRENTMEMBER.PROPERTIES("2/CPMB/PERIOD")="Q1"  OR [%PERIODS%].CURRENTMEMBER.PROPERTIES("2/CPMB/PERIOD")="JAN" ), [MEASURES].[YTD]-([MEASURES].[YTD],[%PERIODS%].LAG(1)), [MEASURES].[YTD])' SOLVE_ORDER=3
    QTD:
    MEMBER [MEASURES].[YTD] AS 'IIF(([%INACCT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="INC" OR [%INACCT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="LEQ"),-([MEASURES].[/CPMB/SDATA], CLOSINGPERIOD([%PERIODS%].[LEVEL02])), ([MEASURES].[/CPMB/SDATA], CLOSINGPERIOD([%PERIODS%].[LEVEL02])))' SOLVE_ORDER=3
    MEMBER [MEASURES].[PERIODIC] AS 'IIF(([%INACCT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="INC" OR [%INACCT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="EXP") AND NOT ([%PERIODS%].CURRENTMEMBER.PROPERTIES("2/CPMB/PERIOD")="TOTAL" OR  [%PERIODS%].CURRENTMEMBER.PROPERTIES("2/CPMB/PERIOD")="Q1"  OR [%PERIODS%].CURRENTMEMBER.PROPERTIES("2/CPMB/PERIOD")="JAN" ), [MEASURES].[YTD]-([MEASURES].[YTD],[%PERIODS%].LAG(1)), [MEASURES].[YTD])' SOLVE_ORDER=3
    MEMBER [MEASURES].[QTD] AS 'IIF(([%INACCT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="INC" OR [%INACCT%].CURRENTMEMBER.PROPERTIES("2/CPMB/ACCTYPE")="EXP"),IIF([%PERIODS%].CURRENTMEMBER.PROPERTIES("2/CPMB/TILEVEL")="QUARTER",[MEASURES].[PERIODIC],IIF([%PERIODS%].CURRENTMEMBER.PROPERTIES("2/CPMB/TILEVEL")="MONTH" OR [%PERIODS%].CURRENTMEMBER.PROPERTIES("2/CPMB/TILEVEL")="WEEK" OR [%PERIODS%].CURRENTMEMBER.PROPERTIES("2/CPMB/TILEVEL")="DAY",SUM(PERIODSTODATE([%PERIODS%].CURRENTMEMBER.PARENT.LEVEL, [%PERIODS%].CURRENTMEMBER),[MEASURES].[PERIODIC]),NULL)),[MEASURES].[YTD])' SOLVE_ORDER = 3
    B.R. Vadim

  • Pulse duration in labview FPGA

    Dear 
    can one help to built a lv FPGA to measure the pulse duration 
    my first start lv  VI is shown below for Spartan 3E kit the but its fail to work
    is thei rany modify make it work??
    for the case structure in false case the old value is moved instead of tick counter
    best regards
    hi ?Q>
    Solved!
    Go to Solution.

    40MHz inverted is 0.000000025  This is how many seconds a single tick takes.  If your tick counter is a U32 (the largest it goes to without extra work) you have 2^32 values which is 4294967296.  Multiply these two numbers and you get 107.3741824.  This means after 107 seconds your U32 counter will roll over.  For this to work long term you will need some way of keeping track of the amount of time passed.  I've seen some example 64 bit counters here, or here.
    Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
    If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

  • Counter roll-over when measuring period

    Hi,
    I'm using PCI-6251 counter 0 to continuously measure the period of a signal, and I notice there are occasionally  error readings. Since the counter can roll over when it reaches 2^32-1, I need to know what will happen to the period measurement when counter roll overs. Would anyone please help me?
    Thanks.
    David

    The count value will simply wrap-around back to 0 and then continue to increment.  I can think of a few ways to handle this:
    1. Specify a slower timebase for the measurement.  If you go from, say, 80 MHz to 100 kHz, it'll take 800 times as long a period to cause rollover.  This method is pretty simple to implement, but not all apps can accept the loss in precision.
    2.  You can use a 2nd counter to be sensitive to the 1st counter's "terminal count".  This gets a bit complex, so you may need to do more research on some of the terms that follow.
    An internal pulse signal is generated on the board when the 1st counter rolls over from 2^32-1 back to 0.  It's commonly known as "terminal count" or TC.  You'll need to configure a 2nd counter that also measures periods of your external signal, but which uses those TC pulses as its timebase signal.  You may need to fiddle with the "Duplicate Count Prevention" property on the 2nd counter so that it will buffer values of 0 during the majority of intervals where no TC pulse occurs.  During the intervals where rollover happens, the 2nd counter will count how many times it happens.
    You would further need the 2 counters to be started off a common "arm start" trigger to keep their data sync'ed.
    3.  Software method.  You can query the DAQmx Channel property "Counter Input -> General Properties -> More -> Terminal Count Reached".  When you get a 'True' output, the property resets such that subsequent calls will return 'False' until the next rollover occurs.  The problem here is trying to correlate this software-detected rollover with a specific period in the 1st counter's measurement buffer.  You'd probably also need to be querying and tracking the DAQmx Read property for Total Samples Acquired both before and after the TC event.  Even then you might not always be able to determine unambiguously which interval had the TC event.
    -Kevin P.

  • Dunning Key and minimum amount per dunning level

    Dear Friends,
    Can any one please explain the dunnig key functions?
    While defining the minimum amout their is two terms one is open item and another one is total amount.
    The definintion of total amount is all the items in an account means the items which are paid also? because I am confuse to understand the differece between total amount and open items. Please expain the both the terms.
    Thanks in advance,
    Regards,
    Mahendra Dev

    Dear Rajeev,
    Lots of thanks for your reply.
    as per my understanding on behalf of your explanation.
    Total Open item can be total of item in grace period and also the item which is in dunning level
    and the total item only the total of item which is in dunning level.
    I am in the mid of chapter of Minimum amount per dunning level.
    and want to clear the term the relation between the total amount and the total open items be greater than a minimum percentage.
    Please confirm. Lots of thanks in advance.
    Regards,
    Mahendra Dev

  • Using fiscal period and Fiscal quarter reporting seemlessly in a BI Query

    Hi,
    We have a very specific issue. Reporting the Fiscal Period( in our
    case we have 53 fiscal periods) and Fiscal Quarter( we have 4 quarters)
    in the same query seamlessly as we would have done using Calander Month
    and Calander quarter in other reports that uses SAP delivered standard
    time dimensions.
    However unlike the Calander time dimension (SAP provided all
    possible...0CALDAY, 0CALWEEK, 0CALMONTH, 0CALQUARTER, 0CALYEAR) where you have all of these inside your info provider, you can get
    aggregation on week, month, quarter etc in your query seamlessly, The Fiscal Year/Period offers a problem in doing report seamlessly.
    When we delve into Fiscal realm, SAP only provided with 0FISCVARNT,
    0FISCPER, 0FISCYEAR and a special period 0FISCPER3. It doesn't provide
    anything like 0FISCQUARTER etc and rightly so, because you can have
    only one 0FISCVARNT in the Time dimension and can have related periods
    (0FISCPER) only for a Row of data in your infocube. For example if you need to model as per the Fiscalweek, you can create a custom Fiscal year variant (Say z1) and can configure to have only 53 periods (Mapped to 0FISCPER) representing
    53 Fiscal WEEK. Similarly for mapping Fiscal Quarter you can create
    another fiscal year variant (Say Z2) and have only 4 periods (mapped to
    0FISCPER also in this case) to represent the 4 Fiscal Quarter. However
    the issue is that for one record you can only map either of those and
    not both since you can only have one Fiscal year variant in one row of
    data in the info provider.
    For example
    If I have two rows OF DATA coming from different sources (One FOR
    Fiscal Week and another for Fiscal Quarter) I can have the following in
    my info provider.
    1> Example data in Fiscal
    Char1 Char2 0CALDAY 0FISCVARNT 0FISCPER Quantity
    X  ......  y .....10/22/07 ....Z1 ....           43’2007 .......10
    X .......  Y .....10/22/07 ....Z2 ....          Q3’2007 .......20
    The issue is how do I report the Quantity in a query in Quarter Q3 as
    (10 + 20 = 30) since both the rows corresponds to FISCAL Q3’2007?
    (Please note that Fiscal week 43’2007(For VARIANT Z1 ) actually is
    Fiscal Quarter Q3’2007( For Fiscal Variant Z2) as per our
    configuration of Fiscal Year Variant configuration Z1 and Z2)
    The same is very simple when I have infoprovider with CALENDAR Time
    dimensions , for example if we don’t have any fiscal reporting
    requirement and just report on calendar time dimension the record in
    the info provider would look like the following ( example)
    2> Example Data in CALENDAR DIMENSION
    Char1 Char2 0CALDAY 0CALWEEK 0CALQUARTER Quantity
    X ........ y .......10/22/07 .......43’2007 .......Q3’2007 .......10
    X ........Y .......10/22/07 ....... 44’2007 .......Q3’2007 .......20
    Here we can use both 0CALQUARTER and get the data aggregated on the
    quarter level in addition to the 0CALWEEK.
    To solve this issue, One option that we are thinking of Using 0CALQUARTER to represent the
    Fiscal Quarter and use Update rule to populate this one. For example
    THE example 1 can be as follows.
    1A> Example of using 0CALQUARTER along with 0FISCVARNT and 0FISCPER
    Char1 Char2 0CALDAY 0FISCVARNT 0FISCPER 0CALQUARTERE Quantity
    X .......y .......10/22/07 ..............Z1 .......43’2007 .......Q3’2007 ..............10
    X .......Y .......10/22/07 ..............Z2 .......Q3’2007 .......Q3’2007 ..............20
    In this case we would populate the 0CALQUARTER by the actual Fiscal
    Quarter and then can use both as per example 2 above. But this is not a
    smooth option since we have various other info providers to join and
    report based on solely Fiscal Quarter etc…
    I am certain that this issue have already been solved by somebody as this bound to happen in any finance application.
    Would appreciate if we can get some light on this regarding the data modelling, reporting etc.
    Thanks
    Arun G.

    You have yourself suggested a solution, which is fine,
    Other option is to have a new characteristic Fiscal Qtr in all the infoproviders ans update the same using a routine in the updaterule depending on the fiscal year variant.
    for eg. for transaction with variant Z1 in one case you can say if fiscal week 01 between 01 to 13 the Fiscal Qtr should be update with1 and if it is between 14 to 26 then update fiscal qtr with 2 and so on.
    For other Variants Z2 you write a different login in the routine ans so on.
    so for all the data irrespective of the variant you will have the qtr as either 1 or 2 or 3 or 4 and you can report on this fiscal qtr.
    assign points if it helps.
    regards
    Venkata Devaraj

Maybe you are looking for