PS Grouping Config

How to create PS groupings & define rules for them?
Rgds,
Tapan S.
Please read the forum Rules before posting the Queries  there are lot of threads which are realted to this issue please use the Search forum Help
Edited by: Moderator

Hi Mj,
You can define Saturday & Sunday is working day or not through counting rule. Then you can assign rounding rule also to absence type through countig rule. Rounding means system will round up absence while applying.
If one employee is applying leave on saturday/Sunday, then system should not allow. This can be set up while creating absence type and you can assign counting rule to absence type where saturday & Sunday will be ticked off.

Similar Messages

  • Error -10401 occurred at AI Group Config - in relation to USB-6008

    I'm attempting to run a simple vi that uses AI Aquire Waveforms.vi to input voltage data that I have coming in from the USB-6008 DAQ.  However, when I try running the program, I receive the error:
    Error -10401 occurred at AI Group Config
    Possible reason(s):
    NI-DAQ LV:  The specified device is not a National Instruments product, the driver does not support the device (for example, the driver was released before the device was supported), or the device has not been configured using the Measurement & Automation Explorer.
    And I'm not sure how to fix it.  In MAX, the device seems to be working properly and everyhting seems to work fine in the test panel, so I'm slightly at a loss.  I'm running Labview 7.1, and installed NI-DAQmx 7.5 which came with the USB-6008.

    Never mind.  I'm new to Labview, and didn't realize that I could not use the traditonal Data Aquisition components with the USB-5008 (I didn't even realize that NI-Daqmx was different).

  • How do I fix error 10001 with AI Group Config.vi

    I have written a VI which uses the AI Sample Channels.vi in it. One of the sub-sub...sub vi's of this is the AI Group Config. I keep getting error 10001 when trying to run it, regardless of the order of the channels (I have tried ascending and descending).
    Any advice would be helpful
    thanks in advance

    Hello,
    First, make sure you use the channel names and numbers as in the Measurement and Automation Explorer (MAX). If you already do, then doing the acquicition on those channels in MAX and see if that works. From there, I would then check the example vi to make sure the channel settings match those in MAX.
    Here are some documents that will help you troubleshoot this error further:
    How Do I Handle the DAQ -10001 Error?
    Error -10001 When Using Virtual Channel and Remote Device Access (RDA)
    Why do I Receive Error -10001 with the AMUX-64T when Reading Multiple Channels in LabVIEW?
    AI Group Config Error 10001 using Virtual Channels
    Hope this helps.
    Zvezdana S.
    National Instruments

  • Exception occurred: "AI Group Config"

    Recently I have gotten a problem with my LabVIEW VI, used to acquire data from a MEA-Chip. As soon as I try to change the setup of my
    PCI 6071 E I get he following error:
    Exception occurred within the external code called by a call library function Node. This might have corrupted LabVIEWs memory. Save....
    After closing the popup: The VI was stopped at node 0x214 of sub VI "AI Group Config".
    I use "AI Config" to initialize and change the setup of the PCI 6071 E. While the initialization works without any problems, an attempt to change any parameter (for example the sample rate), by resetting the device and calling "AI Config" again, leads to that particular exception. 
    Yet the actual problem is, that the VI worked perfectly for months until last week. There haven't been any changes to the measurement system, but suddenly this error pops up and I have not found any solution so far.
    I even tried the PCI 6071 E on an older PC, which had formerly been used, but the problem remains.
    The LabVIEW version is 7.1, both PC's run on windows XP, whereas the hardware components are fairly different, but that should not be a problem I suppose.
    If anyone knows what might suddenly cause this problem please let me know.
    Thanks and regards
    Robert Bestel

    Hello Robert Bestel,
    when reading your post my first guess was that a reinstallation of the traditional DAQ driver might fix this problem.
    After some research i found some similar cases in the past. Most of the time reinstalling the driver didnt fix the problem, but its worth a try.
    Other users had the same problem when their PC Hardware (RAM) got corrupt. To eliminate this possiblity i suggest to run "Memtest" and "Scandisk".
    Here is another Forum thread dealing with a different issue, but the suggestions might work here was well:
    http://forums.ni.com/t5/LabVIEW/corrupted-LabVIEW-s-memory/m-p/558031?requireLogin=False
    Its also possible that this problem might have been caused by some faulty Windows Update. So a complete reinstalltion of windows as well as all NI software could help as a last solution.
    Regards
    Moritz M.

  • Help resolving "Error 10401 occurrred at AI/AO Group Config"

    Hello, I know this is a common error but I'm unable to find a solution looking through these forums and other websites.  I am trying to convert a program wrote on an old computer running LabVIEW 6 to a new computer (with newer hardware) running LabVIEW 8.5.  I've resolved all issues that have came up so far (installing the traditional legacy drivers and such).  The only error I am getting now is a run-time error that pops up and reads:
    "Error 10401 occurred at AI Group Config" and "Error 10401 occurred at AO Group Config"
    I've already run the Measurement and Automation Explorer (MAX) and that did not help.  I'm using Windows XP and my hardware is a NI PCI-6281 M series DAQ.
    Do I have to re-write the sub-VI's, or is this fixable?  Is there an easier way to convert a program?
    If anyone can provide any help or insight what so ever it is greatly appreciated.
    Thanks,
    Alex

    Alex,
    This Developer Zone article may also be of some help to
    see the differences between Traditional DAQ and DAQmx for the most common tasks.
    Mark E.
    Precision DC Product Support Engineer
    National Instruments
    Digital Multimeters (DMMs) and LCR Meters
    Programmable Power Supplies and Source Measure Units

  • PCI-6601 - Group Config error -10444 after 9 hours running

    We developed a vi in order to acquire from the unique dma channel of the PCI-6601 counter 4 multiplexed inputs for a period measurement. We use the national VI buffered_measured_period_TIO. Each cycle the VI is supplied with one of the 4 input line.
    Everything works fine until the 32211 second of measurement (about 9 hours) and after we receive the -10444 error on the group config block and the card freezes (not the software). We need to switch off and on again the PC to start again.
    The cycle of measurement is exactly the one from the original Ni Vi and each cycle the reset is performed.
    Looking in the database we found a similar problem after a long running (10hours) and a PCI-6602.
    We suppose that after s
    everal initialization some internal counter goes in overflow (maybe the TAskID counter?).
    Does exist any explanation and workouround to solve this?
    Is it possible initialize the card only one time for the 4 channel and how?
    Regards
    Andrea Pede

    Hi Andrea,
    What is probably happening is that your memory is becoming increasingly fragmented and after 9 hours there are no continuous blocks of memory available. If you are continuously reconfiguring your counters, that is what is morelikely causing the problem. I included an example that uses all 8 counters and only needs to configure them once. A couple other suggestions:
    1) What happens when you create a larger buffer? Can you run the program for longer?
    2) Have you tried running a disk defrag program on your memory? One suggestion I found on the net was mem-turbo from a shareware site.
    3) What happens if you only use 1 counter? Does the error still occur?
    4) Some issues (including error 10444) with the NI-DAQ driver and analog input were solved
    by upgrading to NI-DAQ 6.9.3. What is your current computer configuration (software, hardware, driver version etc.)? This might help narrow the problem down.
    Simultaneous Buffered-Event Counting on All Eight Counters of the 6602 or 6608 Devices
    http://sine.ni.com/apps/we/niepd_web_display.display_epd4?p_guid=B45EACE3DC9F56A4E034080020E74861&p_node=DZ52325&p_source=External
    Hope that helps. Have a good day.
    Ron
    Applications Engineering
    National Instruments

  • AI Group Config Error 10001 using Virtual Channels

    In my LabVIEW block diagram, I usually enter in numbers, e.g. 0,1,2 for the channel string input of AI Config. When I try to use a virtual channel, I simply type in the virtual channel, e.g. 0,K Thermocouple,2. However, this causes AI Group Config Error 10001, which applies to an invalid channel string. What is the correct way to enter a virtual channel into the channel string?

    Do you have channels with virtual names of "0", and "2"?
    If not you may be confusing MAX by using both naming conventions.
    Try using only Virtual names.
    I generally will use an array of strings where each element is the vitual channel name with no problems.
    Ben
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

  • Digital Group Config.vi Channel List Question

    I am having difficulty understanding the syntax for the Digital Group Config.vi Channel List input. I am using the PCI 6507 DIO-96 card and LabVIEW 6.1.
    I would like to configure all three 8 bit ports on PPI 1,2,&3 for input using a single group. I then want to read the entire group and break out the indivual ports at that time. What would the syntax in the Channel List be to configure this group?
    Thanks in advance!

    Thanks RamziH for your help!
    I have looked at this example and understand how it works. I still am confused as to how to configure the DI0-96, though.
    The DIO-96 has four PPI's and each of these has three 8 bit ports. The examples I have looked at do not show any inputs that would control the specific PPI AND port.
    Maybe I am just missing something with this.
    Thank you very much for your help.
    Barry

  • I'm getting a syntax error (#10001) with my AI Group Config. What could be causing it?

    When I go to run my program, shortly after it starts, it spits out an error #10001 involving the AI Group Config.   This is it's suggested explanation:
    Ni-DAQ LV: An error was detected in the input string; the arrangement or ordering of the characters in the string is not consistent with the expected ordering.
    I've looked to make sure the assigned device name is the same as the expected one, so I know that's not it.   Does anyone have any idea what could be causing this?

    Hi,
    First,  i must mention that the way u put it "it spits out an error #10001" sounds horribly good!
    Now to the problem, this error is usuall given if you enter an improper channel number(a string instead of numeric)
    AI group config is a traditional daq function and channels are reperesented by numerals.
    check if you have entered channel numbers in proper syntax.
    regards
    Dev

  • AI Group Config error -10403 when using DAQPad-6070E

    I am using a DAQPad-6070E with attached device SCB-68.
    Yesterday, I was able to read in analog waveforms using the attached file. Today, without any changes made to the file, I get an error -10403 in AI Group Config.
    What could be causing this error since no changes were made in the file or in Measurement and Automation Explorer configuration?
    My system configuration is as follows:
    Windows XP
    Measurement and Automation Explorer v. 2.2.0.3010
    NI-DAQ v. 6.9.2f4
    LabVIEW v. 6.1
    Attachments:
    AIGroupConfigError.vi ‏256 KB

    I haven't been able to run your VI since I'm lacking one of the subVIs in your design, but taking a look I have a few suggestions. I noticed that the device and channels controls for AI Config are both hidden on the front panel. The default values for these controls should be checked to make sure that they agree with the device number in MAX. You could place a probe on all of the inputs to the AI Config VI and let us know what values are being sent.
    Also, try resetting the device driver through MAX, just in case another program did not release some resources that are needed by your VI.

  • Help with Error -10401 occurred at AO Group Config

    I am receiving the error: "Error -10401 occurred at AO Group Config" and have been unable to fix it. 
    Some background: This is someone else's program who has since left, so I am not very familiar with it. It was running fine a little while ago, until the PCI-GPIB card broke.  We got a new GPIB card (essentially the exact same model; the old one was 183619B-01; the new one is 183617K-01) and now this error appears every time I try to run it. 
    I believe this is being thrown by the "AO Config.vi" in my VI Hierarchy.  From reading other forums, such as this: http://digital.ni.com/public.nsf/allkb/46F78EDD19BA0CC386256CEE007201FC and this: http://forums.ni.com/t5/LabVIEW/Change-in-PCI-Device-Number/m-p/2312186#M726679, it seems it may be a problem with properly assigning device numbers.  (The new GPIB card  may have been assigned a new device number while the program is calling the old one).  However, the solution offered is to right-click on the device in MAX and change the device number, but when I right-click I am not given that option (see attached image). On the other hand, it could also be some sort of driver problem.  
    I am running LabVIEW 8.2.1 and Measurement and Automation Explorer 4.2.1.3001 on Windows XP SP2.  Any help is greatly appreciated.  
    Attachments:
    error.PNG ‏89 KB
    right click.PNG ‏77 KB
    hierarchy.PNG ‏94 KB

    Hi bh424,
    I would make sure that you have updated drivers as you mentioned. If you are using TDAQ make sure to reset the device driver mentioned in the KB you listed.
    Another thought would to be to remove and readd the device in MAX to refresh it, and potentially change the naming in your program to reference a new named device. If you cannot rename the device in MAX you could look at repointing the device in your code.
    Are you able to communicate with the device at all in MAX through simple queries? From the right click screenshot it looks like *IDN did not communicate properly.
    Have you also refreshed the list or rebooted your machine?
    http://digital.ni.com/public.nsf/allkb/23B5918E5604915B86256C2B005F4D70?OpenDocument
    I would first ensure you can communicate with the new card in MAX alone. Here are some troublehsooting steps if that is not the case:
    http://digital.ni.com/public.nsf/allkb/A80DBFCCAC36EBDE862562C80058856E?OpenDocument
    There is also the possibility that the card is broken as well. If it was indeed purchased from a 3rd party vendor, there is less we know about the card or what could have been done to it before you acquired it.
    Regards,
    James W.
    Applications Engineer
    National Instruments

  • Finding "digital single write.vi" and "digital group config.vi" for DAQ6507

    i am looking for the following two vi's:
    digital single write.vi and digital group config.vi, as mentioned and required by the example on:
    http://sine.ni.com/apps/we/niepd_web_display.display_epd4?p_guid=B45EACE3E73956A4E034080020E74861&p_node=201227&p_source=External
    can someone please help me with this?
    thanks!
    -gjs

    Hello Gaurav,
    After you install Traditional DAQ, you should have access to these VIs, if you installed the correct version of Traditional
    DAQ for your system and LabVIEW.  The link given above is for Traditional
    DAQ 7.4.1 which works with LabVIEW 7.0, 7.1 and 8.0.  If you do not have
    one of these versions, the LabVIEW support is not installed and that would be
    why you cannot open the example. 
    Therefore, if you are using LabVIEW 6 and you want to run this VI you will need
    to install an older version of DAQ.  To see what versions of Traditional
    DAQ are available for your version of LabVIEW please look here.
    You can find and download that driver from here.
    If this does not help you out, can you please post back which version of
    LabVIEW and Traditional DAQ you have installed?
    I hope this helps,
    Jesse O.
    Applications Engineering
    National Instruments
    Jesse O. | National Instruments R&D

  • An error occurred loading VI'AI Group Config.vi,.

    I am trying to move a program from windows 98 to my laptop which runs XP and I keep getting the following two error messages when I try to run the program:
    1. An error occurred loading VI'AI Group Config.vi,. LabVIEW load error code 21: An external subroutine required for execution could not be found
    2. Error - 10243 occurred at DIO Port Config.
    Does anybody have suggestions as how to fix these errors?

    Hello,
    It it very possible that you have developed your application (.exe) with one version of the NI-DAQ driver on the 98 machine and have loaded a different version of NI-DAQ on to the XP machine.  This would explain both error 21 and 10243.  There are only a couple of versions of the NI-DAQ driver that support both 98 and XP.  Thus, it is very likely that you could have developed on the 98 machine with a version of NI-DAQ that does not support XP.  Please check that you are developing on 98 with either of these versions of NI-DAQ 6.9.0, 6.9.3 with patch 6.9.3f5, 7.0, or 7.1.  I would recommend using 7.1, since it is the most recent of the Traditional NI-DAQ drivers that support both OS.  If you find that your .exe was developed with a version older than 6.9.0 you might need to upgrade the driver on the developement machine.
    For error 21, please refer to the KnowledgeBase linked below for more detail.
    KB 0ZTKCAWV: Error 21 While Loading LabVIEW Executable on Target Machine
    For error 10243, it is looking for a the configuration that it can not open or acces.  Please also refer to the linked KnowledgeBase.
    KB 3ADBL74B: LabVIEW Error 10243
    KB 18K8B88U: All my LabVIEW DAQ VIs return error -10243
    Please also make sure that you are using the same version of LabVIEW and DAQ driver on both the developement and target machine.
    Samantha
    National Instruments
    Applications Engineer

  • Business Partner Field Grouping Config for BBPMAININT transaction

    Hi,
    Vendor from ECC (6.0) are replicated to SRM (5.0) via the standard vendor replication program BBP_VENDOR_SYNC.  In SRM, I want to hide/suppress some fields (ie: tax numbers) on the business partner transactions BBPMAININT and BP.  I tried to acheive this via Business Partner Field Grouping config, and it works for BP transaction but it does not work for BBPMAININT transaction.
    Does anyone know how to hide/suppress fields for BBPMAININT transaction?
    Reference to Field Grouping config:
    SPRO -> Cross-application oomponents -> SAP Business Partner -> Business Partner -> Basic Settings -> Field Groupings -> Configure Field Attribute per Client
    Thanks,
    Susan Wang

    Hi,
    See the foll threads for more pointers:
    Vendor Master Extension in SRM
    Business Partner Custome Fields Mandatory
    BR,
    Disha.
    Do reward points for useful answers.

  • HA - ACE20-MOD-K9 - FT Group Config Will Not Synch (SSL)

    Hi,
    We have a pair of ACE20-MOD-K9 in Fault Tolerant mode. They are running multiple contexts and we have a problem with one particular context which is running SSL off-loading. Despite the config being identical on both (accept for the peer addresses obviously) and both having the same SSL Key and Cert files loaded on both, the configuration will not sync between them.
    Here is the outputs from both:
    XXXX-DC2-00-ACE1/XXXXX-CISCO-QUAD-SERVICES# sh ft group brief
    FT Group ID: 8  My State:FSM_FT_STATE_ACTIVE    Peer State:FSM_FT_STATE_STANDBY_COLD
                    Context Name: XXXXX-CISCO-QUAD-SERVICES        Context Id: 2   Running Cfg Sync Status: Successful
    XXXX-DC1-00-ACE1/XXXXX-CISCO-QUAD-SERVICES# sh ft group brief
    FT Group ID: 8  My State:FSM_FT_STATE_STANDBY_COLD      Peer State:FSM_FT_STATE_ACTIVE
                    Context Name: XXXXX-CISCO-QUAD-SERVICES        Context Id: 11  Running Cfg Sync Status: Successful
    XXXX-DC2-00-ACE1/XXXXX-CISCO-QUAD-SERVICES# sh ft group stat
    FT Group                     : 8
    Configured Status            : in-service
    Maintenance mode             : MAINT_MODE_OFF
    My State                     : FSM_FT_STATE_ACTIVE
    Peer State                   : FSM_FT_STATE_STANDBY_COLD
    Peer Id                      : 1
    No. of Contexts              : 1
    Running cfg sync status      : Peer in Cold State. Incremental Sync Failure: SSL Keyfile does not exist
    Startup cfg sync status      : Peer in Cold State. Incremental Sync Failure: SSL Keyfile does not exist
    XXXX-DC1-00-ACE1/XXXXX-CISCO-QUAD-SERVICES# sh ft group stat
    FT Group                     : 8
    Configured Status            : in-service
    Maintenance mode             : MAINT_MODE_OFF
    My State                     : FSM_FT_STATE_STANDBY_COLD
    Peer State                   : FSM_FT_STATE_ACTIVE
    Peer Id                      : 1
    No. of Contexts              : 1
    Running cfg sync status      : Incremental Sync Failure: SSL Keyfile does not exist
    Startup cfg sync status      : Incremental Sync Failure: SSL Keyfile does not exist
    XXXX-DC2-00-ACE1/XXXXX-CISCO-QUAD-SERVICES# sh crypto file
    Filename                                 File  File    Expor      Key/
                                             Size  Type    table      Cert
    fn42604_cert.pem                         1850  PEM     Yes        CERT
    fn42604_privatekey.pem                   1679  PEM     Yes         KEY
    quad2.pem                                1675  PEM     Yes         KEY
    quad2_cer.pem                            2582  PEM     Yes        CERT
    quad_prod_abbrv                          1675  PEM     Yes         KEY
    quad_prod_abbrv_cer.pem                  2556  PEM     Yes        CERT
    quad_prod_fqdn                           1675  PEM     Yes         KEY
    quad_prod_fqdn_cer.pem                   2578  PEM     Yes        CERT
    XXXX-DC1-00-ACE1/XXXXX-CISCO-QUAD-SERVICES# sh crypto file
    Filename                                 File  File    Expor      Key/
                                             Size  Type    table      Cert
    fn42604_cert.pem                         1850  PEM     Yes        CERT
    fn42604_privatekey.pem                   1679  PEM     Yes         KEY
    quad2.pem                                1675  PEM     Yes         KEY
    quad2_cer.pem                            2582  PEM     Yes        CERT
    quad_prod_abbrv                          1675  PEM     Yes         KEY
    quad_prod_abbrv_cer.pem                  2556  PEM     Yes        CERT
    quad_prod_fqdn                           1675  PEM     Yes         KEY
    quad_prod_fqdn_cer.pem                   2578  PEM     Yes        CERT
    All the Crypto files are identical as I copied them from one ACE to the other.
    Can anyone shed any light on why this context is not syncing its configuration?
    Thanks,
    Dom Wilkinson

    Hi,
    Can you restart autosync and see if it fixes the issue,
    no ft auto-sync startup-config
    no ft auto-sync running-config
    ft auto-sync startup-config
    ft auto-sync running-config
    Regards,
    Siva

  • How to Purchase group configer in dev system and how to traverse quality

    Hi All
    I need ur help regarding for how to configer the Purchaseing  group in dev system and how to traverse to Quality and production.
    Thanks
    Happy

    Hi,
    You can create the Purchasing Groups using the following settings.
    SPRO-MM-Purchasing-Create Purchasing Groups.
    Create a new entry for Purchasing group & save it in a Transport request & transport it to QAS & PRD.
    Note: We define the Purchasing Groups @ client level
    Thanks & Regards,

Maybe you are looking for