Generic Deltas vs. LO Deltas

Dear All,
I am learner of SAP BI/BW I have one query mentioned below
1)     I would like to know the difference between Generic Deltas vs. LO Deltas u2013 when we used to prefer both the Deltas.
2)     When did you go for Function module and let me know the real time scenario which you faced.
Regards,
Divyesh

Hi..
1) I would like to know the difference between Generic Deltas vs. LO Deltas u2013 when we used to prefer both the Deltas.
Generaic datasource is something which you create when the standard ones doesn't fulfill your requirement.....
To make it delta enable you should select some delta specific field.......which will work as a timestamp.......which will record the changes based on which the new or changed records (delta records) will get fetched......
You have to do the init......and then you can execute the delta.......
Here you are directly fetching data from some Application table, view, Infoset........
Or if the logic is complex..........means you have fetch data from multiple table you can go for a Function Module......
Now...LO deltas are different........here Set up table is mandatory..........because it cannot access data directly from the Application table......
First, you have to fill the set up table..........then run the init.........once the init is done..........after that changes will automatically get recorded in the Delta queue........but here also once catch is there........
Different Update modes are there...........if it is a Queued delta or Unserialized V3 update ..........then the changes and new records will get stored in the Extraction Queue(LBWQ) and Update table (SM13) respectively............then you have to schedule the Collective run in LBWQ to pull the records in RSA7..............only in case of Direct delta changes will directly get recorded in RSA7........
2) When did you go for Function module and let me know the real time scenario which you faced.
if the logic is complex..........means you have fetch data from multiple table you can go for a Function Module......
For an example..........for FI logic is quite complicated.........business specific.......if you just create a view it will not fulfill the requirement.........you will have some business specific logic..........
So in this case you have to go for a FM......
Regards,
Debjani....

Similar Messages

  • Generic Datasource with Additive Delta

    Hi all
    I have a question.
    In whic case can I use a generic datasource with additive delta?
    Does this delta mode make sens only with function module extraction?
    If I extract data directly from a table, can I use this delta mode only if a field represents changes?
    Thanks for your help!
    S.

    Stefania,
        To my knowledge what you are thinking is wrong.
    we have 2 Methods for Generic DS.
    1. New status for changed Records.
    2. Additive delta.
    New status for changed records means
    New Order
    order no    quantity
    1000          10
    order changed to quntity 8. then 2 records will posted 2 BW in first case.
    1000          -10
    1000            8
    if you come to Additve delta.
    for the same case it will send the same record as
    1000          10
    changed records
    1000          -2
    this is the difference. New status with changed records should be used only in association with ODS not cube becoz we don't have overwrite option.
    Additive delta we can use for ODS and Cubes with update mode Addition.
    Hope this is clear.
    Regards,
    Nagesh Ganisetti.

  • Delta Initialization vs Delta Update

    We're having some issues with performance when loading our GL cube.  What I would like to do is perform many delta initializations, each delta inititialization containing one month/period.
    My confusion is in the fact that the last time I attempted this, when I subsequently went to run my delta UPDATE the same selection criteria was automatically inserted into my delta update.
    So for example my INIT may look like this;
    REQUEST1: Selection = 001.2005
    REQUEST2: Selection = 002.2005
    etc........etc...
    REQUEST12: Selection = 012.2005
    Next the UPDATE info package seems to inherit the same criteria... doesn't this mean it will not update anything beyond that criteria??
    I'm just wondering if it is possible to do an incremental initialization and still be able to enable delta updates for future periods?
    Thanks!

    Hi Patrick,
    The delta update will load the data as per the selections made in the Init run. A delta requested after several initializations, contains the sum of all the successful initial selections as a selection condition. This selection condition can then no longer be changed for the delta.
    Take a look here for more info:
    http://help.sap.com/saphelp_nw04/helpdata/en/80/1a65dce07211d2acb80000e829fbfe/content.htm
    Hope this helps...

  • R/3 extraction.{direct delta and queued delta and V3}

    Hi,
    I am new to BW.Can anyone explain me about R/3 extraction in detail and steps to extract from R/3 to BW.
    I understood direct delta.But i couldn't understand queued delta.Can anyone please explain queued delta and also V3.Are queued delta and V3 same?
    Detail explanation or links will help a lot.
    Thanks,
    Sunny.

    Hi Sunny,
    Procurement - MM :
    MM is a part of SCM. There are several section in this, say Procurement, manufacturing, vendor evaluation etc... All can be found under follwoing link.
    Please find the procedure and important links for LO extraction..
    LO'S Procedure:
    Go to transaction code RSA3 and see if any data is available related to your DataSource. If data is there in RSA3 then go to transaction code LBWG (Delete Setup data) and delete the data by entering the application name.
    Go to transaction SBIW --> Settings for Application Specific Datasource --> Logistics --> Managing extract structures --> Initialization --> Filling the Setup table --> Application specific setup of statistical data --> perform setup (relevant application)
    In OLI*** (for example OLI7BW for Statistical setup for old documents : Orders) give the name of the run and execute. Now all the available records from R/3 will be loaded to setup tables.
    Go to transaction RSA3 and check the data.
    Go to transaction LBWE and make sure the update mode for the corresponding DataSource is serialized V3 update.
    Go to BW system and create infopackage and under the update tab select the initialize delta process. And schedule the package. Now all the data available in the setup tables are now loaded into the data target.
    Now for the delta records go to LBWE in R/3 and change the update mode for the corresponding DataSource to Direct/Queue delta. By doing this record will bypass SM13 and directly go to RSA7. Go to transaction code RSA7 there you can see green light # Once the new records are added immediately you can see the record in RSA7.
    Go to BW system and create a new infopackage for delta loads. Double click on new infopackage. Under update tab you can see the delta update radio button.
    Now you can go to your data target and see the delta record.
    Re: LO-Cockpit  V1 and V2 update
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
    Also Refer this link:
    http://www.sap-img.com/business/lo-cockpit-step-by-step.htm
    Inventory.. dwload go thru it
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
    *Steps*:
    1st delet the septup table----lbwg(for application 3)(need to cleanup the setup tables in r/3 side by using (LBWG for AC:03)
    1) Fill setup table (fill up the set up tables BX, BF and UM by using (MCNB,OLI1BW and OLIZBW).
    for BX(Open stock)-tcode--MCNB,
    for BF Tcode(oli1bw)
    for UM tcode(olizbw)
    after that pull data to BW with (Once the data is ready in RSA3, then in BW you have to set up compression for zero marker update for the Cube (coz is related to Noncummulative Keyfiger scenario) then load BX data. onces its completed load normally the BF and UMs.
    BW side:-
    make the compression
    for BX load normally
    and BF&UM(step table data):-compression with zero mark update(select that check box option)
    after completion of compression do delta(Note: for deltas follow the compression normally)
    http://help.sap.com/saphelp_nw2004s/helpdata/en/29/79eb3cad744026e10000000a11405a/frameset.htm
    http://help.sap.com/saphelp_nw70/helpdata/en/c5/a26f37eb997866e10000009b38f8cf/frameset.htm
    SD - Enterprise Sales and Distribution
    SD comes under CRM application component (ERP Analytics).
    sd flow
    salesorder:
    VBRK - header
    VBAP - item
    VBEP - scheduling
    delivery:
    LIKP - header
    LIPS - item
    billing:
    VBRK - header
    VBRP - item
    shipement
    VTTK - header
    VTTP - item
    customer data
    SD links FI table
    salesarea data general data companycode data
    knvp kna1 knb1
    material master data
    SD link to MM table
    salesdata Basic data salestext data
    MARC MARA STXH(Textfile header)
    MVKE MAKT STXL
    process:
    1.sales reresntive enter sales order in R/3 system, it sotres the transaction into three
    SD tables.
    2.delivery due list is executed for all sales orders and delivers are created in table LIKP, LIPS.
    A goodsissue updating MKPF & MSEG.
    3.invoice due list is then executed for all deliviers. after an invoice is created, which creates an acct.doc ( BKPF & BSEG, FI TABLES) and set up the receivalbe in table BSID (open tem).
    4.The receivalbe is cleared when paymen check is required. anoher acct.doc is created ( BKPF & BSEG) the open receivable is cleared and table BSAD (closed line item) is updated
    First u select application component.. SD,MM,FI,PM
    then got to rsa5.. u can install data source...
    after next step RSA6-Display data sources
    Then select our ds which we need to enhance then click on the
    append structure (application tool bar)
    u can see start with ZAGTFIGL_4 ( fi example)
    u given component name and component type ( here given to existing
    data element)
    save + activate....
    then go to the t code CMOD...>there select the project
    name--> go to the exit in RSAP0001->
    or also u can goto tcode se37 fuction module.. EXIT_SAPLRSAP_001
    transactional data
    click on display...
    then u can see INCLUDE ZXRSAU01( program ) double click it.....
    then u can change option click it.
    So please follow the link below:
    http://help.sap.com/saphelp_nw70/helpdata/en/c5/bbe737a294946fe10000009b38f8cf/frameset.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/17/cd5e407aa4c44ce10000000a1550b0/frameset.htm
    Check these links,
    http://help.sap.com/saphelp_47x200/helpdata/en/dd/55f33e545a11d1a7020000e829fd11/frameset.htm
    http://www.sapbrain.com/TUTORIALS/FUNCTIONAL/SD_tutorial.html
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MYSAP/SR_MM.pdf
    http://sap-img.com/materials/what-is-the-dataflow-of-mm.htm
    http://www.erpgenie.com/abap/tables_sd.htm
    http://www.erpgenie.com/abap/tables_mm.htm
    /people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
    /people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
    /people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
    /people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
    /people/sap.user72/blog/2005/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis
    Re: LO-Cockpit  V1 and V2 update
    http://www.sap-img.com/business/lo-cockpit-step-by-step.htm
    Regards
    CSM Reddy

  • How to do delta detection and delta creation

    Hi
    i am new to OWB , please help me in
    how to do delta detection and delta creation using OWB
    Thanks

    Hi Bassem,
    for delta detection in your data source there are three possibilities:
    1. the source data has some identifier when it has been modified and deleted data is marked an not physically deleted
    In this case you just filter the data that has been changed in your owb mappings.
    2. you use some change data capture technologies
    You have to install this manually when using owb 11.1 or older versions (google for oracle and cdc). owb 11R2 brings built in support for change data capture.
    3. you get all the data and identify the delta manually
    In the owb mapping you left outer join the data from your source with the existing data in your target and filter for the data that is new or has been modified. In a second step you identify the deleted data by selecting the data in your target minus the data from your source.
    Which approach is the best depends on your specific system architecture.
    Regards,
    Carsten.

  • Direct delta and Qued delta.............

    Hi Gurus !
    Both Direct delta and Qued delta in LO are independent of the success of the V2 Update process( Roberto Negro too mentioned this in his weblog).This means that V2 update Exists both in Direct and qued delta( Am I correct?).
    As the data is written in the Delta que within V1 Update
    for the case of direct delta, in Extraction que in Qued delta ,  where does the V2 Update come into the Picture?
    Pls can anyone help in this regard.
    Regards
    Durai

    Hi !
    I am very eager to know the answer.
    Regards
    Durai

  • Repeat Delta bringing previous delta too

    Hi BIs,
    SAP system sometimes acting strangely by bringing Current days delta + previous days delta when Delta Info package was requested again.In Monitor it is displaying as Repeat delta only.
    This strange behavior is occuring once in a while and not evry time
    Could any one tell me why it is behaving like this,if so any possible ways to avoid this
    Thanks and regards
    Bala

    HI ,
    generally if you make the delta request red and then repeat it that only will set your init pointer ..
    but i think  there is some problem with the init pointer setting .. so can try one thing run once init without data transfer that will set you init flag .. and run your deltas... this might solve  your problem ..
    Regards,
    shikha

  • Differences between FULL, DELTA and REPEAT DELTAs

    Please distinguish Full, Delta and Repeat Delta loading from R/3 to BW/BI and give some example for their uses
    Your answer would be appreciated.
    Cheers,
    Nari

    please search in SDN before posting Novice questions

  • Generic function module for delta - which FM ?

    Hi all,
    I want to create a custom generic datasource in R3 which uses a function module for delta extraction. This is straight forward for full extract (copy FM RSAX_BIW_GET_DATA_SIMPLE - I already did this and have a full extraction working to BW). However I need to extract delta - and the above function module does not have example code for that (I have seen some forum posts that it 'can' be used - but this looks like a pseudo get around where the delta field name is passed in I_T_SELECT).
    FM RSVD_BW_GET_DELTA_DATA seems to be an example code of a FM which can allow delta (i.e. manually codes how to fill date/time stamp information). However when I code this and try test in RSA3 it seems to try to populate the delta selection field before calling my function module! I need it to call my function and allow the function to specifiy the date criteria.
    Can anyone help with an example of how this should best  be done ?
    Or can it only be done in a pseudo form using 'RSAX_BIW_GET_DATA_SIMPLE' example FM.
    Note: I have setup the RSO2 datasource to allow delta.
    Also - I have spent several hours searching the forum - but please answer with a link if you think it does answer exactly this problem.
    Thanks for any help
    Martin

    Hi again,
    Have had a few requests for the code I used - I created a new custom function copied from 'RSAX_BIW_GET_DATA_SIMPLE'. AEDAT has been set as the delta date for this data source in transaction RSO2.
    Main sample code is -
    1. Code to receive selection criteria and store in internal ranges -
    FUNCTION zbw_sodetail_get_detail.                                   
    ""Global interface:                                               
    *"   IMPORTING                                                  
    *"       VALUE(I_REQUNR) TYPE  SRSC_S_IF_SIMPLE-REQUNR        
    *"       VALUE(I_DSOURCE) TYPE  SRSC_S_IF_SIMPLE-DSOURCE      
    *"       VALUE(I_MAXSIZE) TYPE  SRSC_S_IF_SIMPLE-MAXSIZE      
    *"       VALUE(I_INITFLAG) TYPE  SRSC_S_IF_SIMPLE-INITFLAG    
    *"       VALUE(I_READ_ONLY) TYPE  SRSC_S_IF_SIMPLE-READONLY   
    *"       TABLES                                                     
    *"              I_T_SELECT TYPE  SRSC_S_IF_SIMPLE-T_SELECT OPTIONAL 
    *"              I_T_FIELDS TYPE  SRSC_S_IF_SIMPLE-T_FIELDS OPTIONAL 
    *"              E_T_DATA STRUCTURE  ZBW_SODETAIL OPTIONAL           
    *--- Sales order item create date                                      
       LOOP AT i_t_select INTO l_s_select WHERE fieldnm = 'ERDAT'.         
          MOVE-CORRESPONDING l_s_select TO r_erdat.                        
          APPEND r_erdat.                                                  
       ENDLOOP.                                                                               
    *--- Sales order item change date - DELTA only - auto filled before    
       this function is called.                                          
       C (Initialise Delta) - Low = blank, High = today - safety limit   
       D (Delta) - low = , High =   .       *from roosgendlm             
       LOOP AT i_t_select INTO l_s_select WHERE fieldnm = 'AEDAT'.         
          MOVE-CORRESPONDING l_s_select TO r_aedat.                        
          APPEND r_aedat.                                                  
       ENDLOOP.                                                                               
    2. Code to use selection criteria to get initial or delta. Note that for delta the delta date field to be used is automatically populated with the date of the last delta run (from table roosgendlm) -
       SELECT VBAK~KNUMV
              VBAPVBELN VBAPPOSNR VBAPMATNR VBAPARKTX VBAP~SPART
              VBAPWERKS VBAPERDAT VBAPAEDAT VBAPNETWR VBAP~WAERK
              VBAPABGRU VBAPZPROMISE VBAP~CUOBJ
              VBEP~EDATU
          INTO CORRESPONDING FIELDS OF TABLE ZBW_SODETAIL_ITAB
          FROM VBAK JOIN VBAP ON VBAKVBELN = VBAPVBELN
                    JOIN VBEP ON VBAPVBELN = VBEPVBELN
                             AND VBAPPOSNR = VBEPPOSNR
       WHERE VBAP~VBELN IN R_VBELN        "Order number
         AND VBAP~POSNR IN R_POSNR        "Order item number
         AND VBAP~ERDAT IN R_ERDAT        "Order item date created
        AND ( VBAP~ERDAT IN R_AEDAT OR   "Created date in      Delta range
                  VBAP~AEDAT IN R_AEDAT OR   "Order item change    Delta range
                  VBAK~AEDAT IN R_AEDAT ).   "Order header change  Delta range
    Note that if the data source is called in initial or full extract mode the delta change date (aedat) will automatically be blank.
    I have been using this successfully.
    I hope this helps
    Martin.

  • Generic and Master data delta.

    HI,
       Will you please give me the solution for 'The differenet delats we have in generic delta,what actually is a numeric pointer.. how does it pick delat..is it something like it picks a record which has changes in it or it it each neew record..
    if suppose we have 1 to 10 customers, will numeric pointer pick every new customer like (11, 12 , 13) as deltas or changes in 1 to 10 customers itself..
    And Regarding master data deltas,how will the master data pick the deltas, is it every new record as customer mentioned above will be picked or something other..
    the basic thing i want to know is, will it pick any changes in attributes as delta also.. if suppose we have a customer 001 with an attribute as 0ACCNT_GRP, if in any case if this 0ACCNT_GRP has change.. will it even pick this as an delata or not...
    i would appreciate your response..
    Thanks & Regards,
    Shashikanth.

    Hi Shashi,
    Well....I could give some points on the master data delta..Its achieved by the ALE change pointers mechanism.
    There are some tables responsible for storing the changes...CDHDR and CDPOS are good candidates for this.
    Hope this helps..
    Regards,
    Marc.

  • Standard Generic Delta Extractor 0CRM_SRV_COSTS - Delta stop working

    Hello all,
    Has anyone experienced an issue with the standard generic extractor 0CRM_SRV_COSTS (reside in SAP R/3 system) where its delta suddenly just stop working? The issue is that the datasource keeps extracting the same delta records and from RSA7 and SMQ1, only have the olda data records and no new data coming through (ie. from RSA7 data are only in the Delta Repetition).
    The extractor uses Function Module and Numeric Pointer for the delta and I tried to investigate (via RSA2 and ROOSOURCE ) if there is a way to see what field is being used for the Numeric Pointer and how to trace it - but no luck so far.
    Has anyone experienced the similar/same issue on other extractor which can provide some inputs?
    Any ideas/suggestions will be very much appreciated.
    Thanks,
    Andy

    Maybe someone knows if records in tables SMOXRELP_S and SMOXRELP should match perfectly? I see that table SMOXRELP lacks one record that I have in table SMOXRELP_S.

  • Generic data source. Delta based on the changes in the CDHDR & CDPOS

    Hello all,
    I need to create a generic data source using fun module. This fun module has to execute delta based on changes in table CDHDR & CDPOS for purchase order info records.
    can I use RSAX_BIW_GET_DTA_SIMPLE?
    Is there any other way to implement this requirement?
    waiting for ur suggestions ...........
    Thanks,
    zak.

    hi
    check the below extractor... it will extract status from both table.. u may not be required to build a generic one..
    0TE_OBJ_STATUS_HIST

  • Generic Extractor with  ALE-Delta  Capability

    Hi all,
          I need to create a generic Data source based  on 2 tables with fields: MARA-SPART.
                        MAKT-MATNR,SPRAS,MAKTX.
    so  i created a view  on same and  used it in creation of  data source in T.C: RSO2.
      My  requirement is to make this Data source
    Delta-capable using <b>ALE-Delta  mechanisum</b>.
    Please let me know  your views regarding same.
    And i promise to return and reward the answers.
    Thanks&Regards,
    Augustine.

    Hi Augustine and welcome to the sdn,
    it is not possible to get a delta on the fields you added to your view. You have 2 options.
    1st: add fields aedat and erdat of table mara to your view. Create 2 infopackages in BW to load all records created and all records changed in a specific time range.
    2nd: create a fm and select the required fields from mara and makt that are created or changed in a specific time range. Create a ddic structure as extract structure containing spart, matnr, spras, maktx and a date field for the generic delta. See also this information about fm-extraction: /people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
    Hope this helps
    regards
    Siggi

  • Generic DataSource using FM - Delta doubt

    Hi All,
    I have few doubts on Generic DataSource Delta.
    I am working on one HR requirement. where I need to pull the Mandatory courses information.
    to get this done, we have created one Generic DataSource using Function Module.
    FM has huge and complex logic, at present it is taking long time when I run in RSA3, if I continue with this to BI, daily running FULL load to BI is not suggestible, because it takes much time to load.
    I have planned to set the Delta, just want to know what would be the best option to set the delta option for this requirement? and how?  I have 2 dates (Course Start and End dates), Employee, Course Id, Course Type, Position, Job, etc in my DS structure.
    Please suggest someone so that I can do FULL load once in BI and continue with Delta without missing any delta records going forward. 
    Regards,
    Kiran

    Hi,
    In mystrucure used dates are not relating to aedat and erdat, they are CHAR type. here the requirement is little different.
    Regards,
    Kiran

  • Generic FM extractor with Delta

    Hello all,
    I am trying to create a delta function module extractor on a table. I have creation date ANDAT, last change date AEDAT and a deletion flag on the table.
    FM has to handle history, new and changes.
    How can I generate delta? Can I just use RSO2 to set up delta? How can it be done? Also, can I get the code for a generic FM delta extractor?
    Please help.
    Thanks,
    Anirudh.

    Hi Sajeed,
    So, I do not have to handle delta in the extractor at all? Just create a function module based extractor with all the fields and actually take care of delta in the infopackage??
    The creation date is for newly created records and the change date is for changed records.
    My email is [email protected]
    Thanks,
    Anirudh.

  • Difference between RDA delta and normal Delta

    Hi All
    I have some doubts regarding the RDA [Real Time data Acquisition] process I am aware  that RDA enables us to get the data every  minute with help of Daemon process.What is the diffrence between th delta mechanism that is followed in RDa and normal dataflow.
    Thanks & Regards
    Santosh Varada

    Hi Varda ,
    RDA is Real Time Data Acquisition . In this We can retrieve Live data . While using Normal DTP We can t pull live data
    For example :- Today We have Create a 50 orders . This 50 order information pulled after completion of  sales order creation . we can t see live . But RDA process pulled the data at the point of sales order creation it self ,It support only Stranded DSO .It will use Some industries like FMCG.Retail,banking sector they want to know current data information from BI Side then RDA.
    Please Find below link for Demonstration of Real-Time Data Acquisition (RDA) for SAP BI 7.0 using Web Services API.
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00db64ee-82f0-2b10-01b0-fe9543dc227e?quicklink=index&overridelayout=true.
    Real-Time Data Acquisition (RDA) for SAP BI 7.0 using Web Services API
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20f704bd-b6e8-2c10-569e-d726784388ce?quicklink=index&overridelayout=true
    Thanks & Regards,
    Praveen Yagnamurthy,
    SAP BI Consultant,
    Blue Marlin Systems-INDIA.
    http://www.bluemarlinsys.com/
    http://bluemarlinsys.com/bi

Maybe you are looking for

  • HTTP Server for Windows 64 bit not on the companion CD

    Hi, I cannot find the HTTP Server for Windows 64 bit on the companion CD. Any idea where I can get it from? For the 32bit version the HTTP Server is on the Companion CD. Thanks in advance, Florin

  • Can I show 3 timeplots on one graph?

    I've created three separate timeplot lines in Numbers, on separate charts (can't seem to upload a screenshot.) Is there any way that I can import them all onto one chart, despite the fact that they are on different scales (In context, it is a study o

  • Uploading doc extention file taxonomy promot is not coming even compilsory field as metadata

    i am trying to Upload doc file with doc extention in a document library which have taxonomy enabled as metadata column it is not giving the promot for selecting the taxonomy either the field of taxonomy is must but it is working if the file type is D

  • Why won't chapter markers in FCP5 import to idvd6?

    I recently imported a video project that I created in FCP5 into iDVD6 for DVD authoring. I put chapter markers in the video project with the idea that IDVD6 would create the sub menus. For some reason they are not showing up. I've checked the appropr

  • ScanFile function in CVI 9.0.0

    Hello, I use ScaFile function to read binary file that exists floating points array. My file have a 1601 points (double). The function works properly in CVI 8.5.1. When I upgrade to new version CVI 9.0.0, the function return wrong index number. I use