7 Replies Latest reply: May 16, 2013 6:41 AM by Celvin Kattookaran RSS

    Data Export

    Abhi
      Hi,

      Exxporting data using column format needs a dense dimension to be mentioned in

      DataExportColHeader "Period";

      Bu it give a non sensical report with all the period members in the first line, whithout knowing which line belongs to which period whereas if i change version dimension to dense and change the script to


      DataExportColHeader "Version"; its working but its taking very long time to export but "increases my calc scrtipts execution time"

      any remedy for this.

      Thanks
        • 1. Re: Data Export
          Celvin Kattookaran
          Why is it a nonsensical report?

          Did you try to use a load rule and open the exported file?

          When you use dataexport without a delimiter, it creates a tab delimited file.

          So lets say you have

          Jan Feb Mar

          Your data lines will have 3 numbers which corresponds to each month. First will Jan, Feb and so on.

          Regards

          Celvin
          http://www.orahyplabs.com
          • 2. Re: Data Export
            Abhi
            HI Celvin Thats because i had 365 days in period dimension, its time consuming to map each and every day in rules file
            • 3. Re: Data Export
              Celvin Kattookaran
              Wow 365 days and a BSO!!!!

              What other dense dimensions do you have in the cube? Is that a full level0 export or a restricted dataexport? (do you have another dense dimension with lesser members in the fix?)

              Regards

              Celvin
              http://www.orahyplabs.com
              • 4. Re: Data Export
                Abhi
                HI Celvin thanks for your reply,

                yes its BSO, (for write back functionality), no dense dimension with lesser members, the dense dimension with least members has approximately 90 members.

                Thanks
                • 5. Re: Data Export
                  Celvin Kattookaran
                  What about removing the load file itself?

                  Do something like
                  SET DATAEXPORTOPTIONS
                  {
                      DataExportLevel "LEVEL0";
                      DataExportDynamicCalc OFF;
                            DataExportColFormat ON;
                            DataExportColHeader Measures;     
                      DataExportOverWriteFile ON;
                  };
                  
                  FIX("New York",Actual,@LEVMBRS(Year,0),@LEVMBRS(Product,0),Sales)
                  
                  DATAEXPORT  "File""     ""Samp.txt"; 
                  
                  ENDFIX
                  You can then just use the file to load into Essbase. (key is to use tab as delimiter)

                  Regards

                  Celvin
                  http://www.orahyplabs.com
                  • 6. Re: Data Export
                    Abhi
                    hi Celvin,

                    The only difference comes with this script is it dosent export dynamic calc members, and as i have atleast 90 members in dense dimension , i need to map atleast 50, 60 level 0 members in rules file isnt it?


                    Thanks
                    • 7. Re: Data Export
                      Celvin Kattookaran
                      You don't need a rule file to load into essbase if you use that script. (If you are loading to a different cube with different dimensionality then yes you'll need a rule file.)

                      Did you try report script to pull the values?

                      Regards

                      Celvin
                      http://www.orahyplabs.com