Data interpreter for loading of DASYLAB data into DIADEM

Can NI deliver a data interpreter for loading DASYLAB data into DIADEM?

Hi zzzz,
It is my understanding that DasyLab has the ability to write DIAdem *.DAT files. This I have gathered from the fact that US customers have sent me *.DAT data files generated by their DasyLab version, in which several properties are called by their German names. So I assume the DasyLab *.DAT file output was originally written for a German audience, but the data made it over just fine. I suppose that could have been a special feature of their particular DasyLab, but check if you can output *.DAT files with yours. If not, please write back.
Regards,
Brad Turpin

Similar Messages

Example for loading a csv file into diadem from a labview application

Hi everyone, i'm using labview 8.2 and DIAdem 10.1.
I've been searching in NI example finder but I had no luck so far.
I have already downloaded the labview connectivity VIs.
Can anyone provide a example that can help me loading a csv file into diadem from a labview application?
Thanks

Hi Alexandre.
I attach an example for you.
Best Regards.
Message Edité par R_Duval le 01-15-2008 02:44 PM
Romain D.
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
NIDays 2010 : Conférence mondiale de l'instrumentation virtuelle
>>Détails et Inscription<<
Attachments:
Classeur1.csv ‏1 KB
Load CSV to Diadem.vi ‏15 KB

Changing date format for some of the date columns in a subject area

Hi,
I have a requirement to change the date format for some of the date columns to dd-mon-yyy for only a particular subject area. Is there a feature available in the RPD which can help me do this?
In Answers - Column Properties for a Particular column of a report, we can save the style and formatting as system wide default for the particular column or the data type, but that applies across subject areas.
I tried with the config files too , but that too applies to all suject areas.
Thanks in Advance,
Gaurav

Why don't you create 2 logical column derived from same date physical col and then change the format for one logical column and use it in Subject Area ?

Long time for loading Planning books/data views

Hi
Could someone throw some pointers/solutions for extremely horrible time taken for a planning view (data view) to load and populate for certains selection profiles that already have large number of trasactional records. In my case it is specifically the run time dumps thrown for a popular combination (large number of transactions).
Urgent suggestions/solutions required. Pls. call 9923170825. India, if you are lazy enough to type it out. or just type in some key words, tcodes etc.
Thanks

I hope you dont have too many macros hogging the memory in interactive book. The other thing is to be on the latest LC build. Also try to have default unit of measures (keep the dataview settings for UoM blank).
Can you confirm if you build the TLB view brand new in 5.0 or did you do some migration of the books ? The first time opening of book takes longer due to some compilation of certain objects. in SM50, try to identify where the process takes longest - whether it is at client end, at the DB procedure of LC or at application level.

"master data deletion for requisition" before master data loading

Hello Gurus,
in our bw syetem , for process chains for loading master infoobjects, all include "u201C master data deletion for requisition" ABAP
process except for one process chain. my question is:
why that process chain for master data loading is different from others as for lacking "master data deletion for requisition" in it?
so it does not matter if you include " master data deletion for requisition" ABAP process in process chain for master data loading ?
Many thank.

Hi,
ABAP Process means some ABAP program is being executed in this particular step.
It's possible that for all of your process chains except for that one requirement was to do some ABAP program processing.
You can check which program is executed by following below process:
Open your process chain in planning view -> Double click on that particular ABAP process -> Here you can see program name as well as program variant.
Hope this helps!
Regards,
Nilima

What is the best data structure for loading an enterprise Power BI site?

Hi folks, I'd sure appreciate some help here!
I'm a kinda old-fashioned gal and a bit of a traditionalist, building enterprise data warehouses out of Analysis Service hypercubes with a whole raft of MDX for analytics. Those puppies would sit up and beg when you asked them to deliver up goodies
to SSRS or PowerView.
But Power BI is a whole new game for me.
Should I be exposing each dimension and fact table in the relational data warehouse as a single Odata feed?
Should I be running Data Management Gateway and exposing each table in my RDW individually?
Should I be flattening my stars and snowflakes and creating a very wide First Normal Form dataset with everything relating to each fact?
I guess my real question, folks, is what's the optimum way of exposing data to the Power BI cloud?
And my subsidiary question is this: am I right in saying that all the data management, validation, cleansing, and regular ETTL processes are still required
before the data is suitable to expose to Power BI?
Or, to put it another way, is it not the case that you need to have a clean and properly structured data warehouse
before the data is ready to be massaged and presented by Power BI?
I'd sure value your thoughts and opinions,
Cheers, Donna
Donna Kelly

Dear All,
My original question was:
what's the optimum way of exposing data to the Power BI cloud?
Having spent the last month faffing about with Power BI – and reading about many people’s experiences using it – I think I can offer a few preliminary conclusions.
Before I do that, though, let me summarise a few points:
Melissa said “My initial thoughts: I would expose each dim & fact as a separate OData feed” and went on to say “one of the hardest things . . . is
the data modeling piece . . . I think we should try to expose the data in a way that'll help usability . . . which wouldn't be a wide, flat table ”.
Greg said “data modeling is not a good thing to expose end users to . . . we've had better luck with is building out the data model, and teaching the users
how to combine pre-built elements”
I had commented “. . . end users and data modelling don't mix . . . self-service so
far has been mostly a bust”.
Here at Redwing, we give out a short White Paper on Business Intelligence Reporting. It goes to clients and anyone else who wants one. The heart
of the Paper is the Reporting Pyramid, which states: Business intelligence is all about the creation and delivery of actionable intelligence to the right audience at the right time
For most of the audience, that means Corporate BI: pre-built reports delivered on a schedule.
For most of the remaining audience, that means parameterised, drillable, and sliceable reporting available via the web, running the gamut from the dashboard to the details, available on
demand.
For the relatively few business analysts, that means the ability for business users to create their own semi-customised visual reports when required, to serve
their audiences.
For the very few high-power users, that means the ability to interrogate the data warehouse directly, extract the required data, and construct data mining models, spreadsheets and other
intricate analyses as needed.
On the subject of self-service, the Redwing view says: Although many vendors want tot sell self-service reporting tools to the enterprise, the facts of the matter are these:
v
80%+ of all enterprise reporting requirement is satisfied by corporate BI . . . if it’s done right.
v Very few staff members have the time, skills, or inclination to learn and employ self-service business intelligence in the course of their activities.
I cannot just expose raw data and tell everyone to get on with it. That way lies madness!
I think that clean and well-structured data is a prerequisite for delivering business intelligence.
Assuming that data is properly integrated, historically accurate and non-volatile as well, then I've just described
a data warehouse, which is the physical expression of the dimensional model.
Therefore, exposing the presentation layer of the data warehouse is – in my opinion – the appropriate interface for self-service business intelligence.
Of course, we can choose to expose perspectives as well, which is functionally identical to building and exposing subject data marts.
That way, all calculations, KPIs, definitions, and even field names, and all consistent because they all come from the single source of the truth, and not from spreadmart hell.
So my conclusion is that exposing the presentation layer of the properly modelled data warehouse is – in general - the way to expose data for self-service.
That’s fine for the general case, but what about Power BI? Well, it’s important to distinguish between new capabilities in Excel, and the ones in Office 365.
I think that to all intents and purposes, we’re talking about exposing data through the Data Management Gateway and reading it via Power Query.
The question boils down to what data structures should go down that pipe.
According to
Create a Data Source and Enable OData Feed in Power BI Admin Center, the possibilities are tables and views. I guess I could have repeating data in there, so it could be a flattened structure of the kind Melissa doesn’t like (and neither do I).
I could expose all the dims and all the facts . . . but that would mean essentially re-building the DW in the PowerPivot DM, and that would be just plain stoopid. I mean, not a toy system, but a real one with scores of facts and maybe hundreds of dimensions?
Fact is, I cannot for the life of me see what advantages DMG/PQ
has over just telling corporate users to go directly to the Cube Perspective they want, that has already all the right calcs, KPIs, security, analytics, field names . . . and most importantly, is already modelled correctly!
If I’m a real Power User, then I can use PQ on my desktop to pull mashup data from the world, along with all my on-prem data through my exposed Cube presentation layer, and PowerPivot the
heck out of that to produce all the reporting I’d ever want. It'd be a zillion times faster reading the data directly from the Cube instead of via the DMG, as well (I think Power BI performance sucks, actually).
Of course, your enterprise might not
have a DW, just a heterogeneous mass of dirty unstructured data. If that’s the case,
choosing Power BI data structures is the least of your problems! :-)
Cheers, Donna
Donna Kelly

Need Help..!! Loading Data Using Outline Load Utility - No Data

Hi All,
I've tried to load data using Outline Load Utility but the data is not loaded into my Essbase.
Here are the step what I've done :
1. In planning, Administration > Data Load Settings
- Entity as the data load dimension,
- Account as the driver dimension and selected Rental, test_desc as the member
2. The .csv file
Entity, Rental, test_desc, Point-of-View,Data Load Cube Name
TLT, 100, 100, "FY11,Plan,Working,No Product,No Condition Type,No Vehicle Type,No Term Period,No Term,No Movement, Local, Apr", Retail
3. Run the Outline Load through cmd
E:\Oracle\Middleware\user_projects\epmsystem1\Planning\planning1>OutlineLoad /A:PLNDEV /U:xyz /M /N /I:E:/testload.csv /D:Entity /L:E:/OutlineLogs /X:E:/outlineLoad.exc
and below it the OutlineLogs :
[Mon Jul 25 04:01:42 PDT 2011]Successfully located and opened input file "E:\testload.csv".
[Mon Jul 25 04:01:42 PDT 2011]Header record fields: Entity, Rental, test_desc, Point-of-View, Data Load Cube Name
[Mon Jul 25 04:01:42 PDT 2011]Located and using "Entity" dimension for loading data in "PLNDEV" application.
[Mon Jul 25 04:01:42 PDT 2011]Load dimension "Entity" has been unlocked successfully.
[Mon Jul 25 04:01:42 PDT 2011]A cube refresh operation will not be performed.
[Mon Jul 25 04:01:42 PDT 2011]Create security filters operation will not be performed.
[Mon Jul 25 04:01:42 PDT 2011]Examine the Essbase log files for status if Essbase data was loaded.
[Mon Jul 25 04:01:42 PDT 2011]Planning Outline load process finished (with no data load as specified (/N)). 1 data record was read, 1 data record was processed, 1 was accepted, 0 were rejected.
No data rejected there, but when I tried to retrieve the data from my Planning Form or Essbase Add-In, there is no data.
Do I miss something in my step above..??
Please advise.
Thanks.
Regards,
VieN

Hi John,
thanks for reply..
I'm not check the essbase log yet..
From the OutlineLogs (Planning Outline load process finished (with no data load as specified (/N)). 1 data record was read, 1 data record was processed, 1 was accepted, 0 were rejected.), it doesn't mean the data successfully loaded, isn't it...??
Thanks.
Regards,
VieN

Help for loading of XML File into Oracle 10.2 DB.

Hello People,
I need help with below XML File, I need to get it loaded into Oracle 10.2.After brainstorming I could have figured out 2 best ways to do so :
1.Through ctrl file and log file using SQL Loader
2.Using XQuery and XML datatype.
Tried with option 1 but dint succeed.Could you please help me out with a solution of the same ??
<?xml version="1.0" encoding="ISO-8859-1" standalone="no" ?>
- <sta:entity-data xmlns:sta="http://www.vendavo.com/omi/StandardDeal" xsi:schemaLocation="http://www.vendavo.com/omi/StandardDeal StandardDeal-ImportAgreement 100912 - Updated.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- <StandardDeal>
<IsImported>true</IsImported>
<ModelNReferenceID>00144105-009-000</ModelNReferenceID>
<DealName>00144105-009-000CV Magellan Arteriocyte Inc 1164385</DealName>
<AccountGroup>SoldTo</AccountGroup>
<CustomerSalesData.VCustomer.VName>0001164385</CustomerSalesData.VCustomer.VName>
<DistrictManager />
<MultipleSalesReps>false</MultipleSalesReps>
<OnBehalfOf>Brian Smith</OnBehalfOf>
<FOBDestination>false</FOBDestination>
<ConsultingGroupInformation />
<AgreementStartDate>11/15/2007</AgreementStartDate>
<AgreementEndDate>12/31/2013</AgreementEndDate>
<BaselineReviewDate>01/10/2013</BaselineReviewDate>
<BaseLineReviewPeriod>Quarterly</BaseLineReviewPeriod>
<RequestedDate>10/12/2012</RequestedDate>
<RFPDueDate>10/12/2012</RFPDueDate>
<WaiveFreight>false</WaiveFreight>
- <HeaderDiscountPercentageoffALP>
- <VPercentage documentId="1">
<Amount>0</Amount>
</VPercentage>
</HeaderDiscountPercentageoffALP>
<CustomerCommitmentType>Others</CustomerCommitmentType>
<ManualApproval>true</ManualApproval>
<LegalReviewRequired>false</LegalReviewRequired>
<TechnologyClause>false</TechnologyClause>
<ComplianceTracking>false</ComplianceTracking>
<ComplianceStatus>false</ComplianceStatus>
<VState.VLabel>draft</VState.VLabel>
<Eval>false</Eval>
<CustomerAccepted>true</CustomerAccepted>
<VNotes>CV Magellan Arteriocyte Inc 1164385</VNotes>
- <VItems>
- <StandardDealLineItem documentId="5235485">
<IsImported>true</IsImported>
<VCatalogEntity.VName>MAG100</VCatalogEntity.VName>
<PricingCPG>Magellan</PricingCPG>
- <ExpectedAnnualQuantity>
- <VQuantity>
<VAmount>1</VAmount>
<VUOM>EA</VUOM>
</VQuantity>
</ExpectedAnnualQuantity>
<PercentageBase>false</PercentageBase>
<DiscountALP>N/A</DiscountALP>
- <DiscountPercentage>
- <VPercentage documentId="2">
<Amount />
</VPercentage>
</DiscountPercentage>
<ProposedAgreementPrice />
- <CustomerRequestedPrice>
- <VMoney documentId="4">
<Amount />
</VMoney>
</CustomerRequestedPrice>
<Monthly>No</Monthly>
<PpaNoCap>N/A</PpaNoCap>
- <ProjectedMarketShare>
- <VPercentage documentId="5">
<Amount>0</Amount>
</VPercentage>
</ProjectedMarketShare>
<CustomerCommitted>Yes</CustomerCommitted>
<VState.VName>draft</VState.VName>
</StandardDealLineItem>
- <StandardDealLineItem documentId="5235486">
<IsImported>true</IsImported>
<VCatalogEntity.VName>MAG100</VCatalogEntity.VName>
<PricingCPG>Magellan</PricingCPG>
- <ExpectedAnnualQuantity>
- <VQuantity>
<VAmount>1</VAmount>
<VUOM>EA</VUOM>
</VQuantity>
</ExpectedAnnualQuantity>
<EffectiveFrom>11/15/2007</EffectiveFrom>
<DurationMonths>19</DurationMonths>
<PercentageBase>false</PercentageBase>
<DiscountALP>N/A</DiscountALP>
- <DiscountPercentage>
- <VPercentage documentId="2">
<Amount />
</VPercentage>
</DiscountPercentage>
<ProposedAgreementPrice />
- <CustomerRequestedPrice>
- <VMoney documentId="4">
<Amount />
</VMoney>
</CustomerRequestedPrice>
<Monthly>No</Monthly>
<PpaNoCap>N/A</PpaNoCap>
- <ProjectedMarketShare>
- <VPercentage documentId="5">
<Amount>0</Amount>
</VPercentage>
</ProjectedMarketShare>
<CustomerCommitted>Yes</CustomerCommitted>
<VValidity.from>11/15/2007</VValidity.from>
<VValidity.to>05/31/2009</VValidity.to>
<VState.VName>draft</VState.VName>
</StandardDealLineItem>
- <StandardDealLineItem documentId="5235487">
<IsImported>true</IsImported>
<VCatalogEntity.VName>MAG100</VCatalogEntity.VName>
<PricingCPG>Magellan</PricingCPG>
- <ExpectedAnnualQuantity>
- <VQuantity>
<VAmount>1</VAmount>
<VUOM>EA</VUOM>
</VQuantity>
</ExpectedAnnualQuantity>
<EffectiveFrom>11/15/2007</EffectiveFrom>
<DurationMonths>74</DurationMonths>
<PercentageBase>false</PercentageBase>
<DiscountALP>N/A</DiscountALP>
- <DiscountPercentage>
- <VPercentage documentId="2">
<Amount />
</VPercentage>
</DiscountPercentage>
<ProposedAgreementPrice />
- <CustomerRequestedPrice>
- <VMoney documentId="4">
<Amount />
</VMoney>
</CustomerRequestedPrice>
<Monthly>No</Monthly>
<PpaNoCap>N/A</PpaNoCap>
- <ProjectedMarketShare>
- <VPercentage documentId="5">
<Amount>0</Amount>
</VPercentage>
</ProjectedMarketShare>
<CustomerCommitted>Yes</CustomerCommitted>
<VValidity.from>11/15/2007</VValidity.from>
<VValidity.to>12/31/2013</VValidity.to>
<VState.VName>draft</VState.VName>
</StandardDealLineItem>
- <StandardDealLineItem documentId="5235489">
<IsImported>true</IsImported>
<VCatalogEntity.VName>MAG200</VCatalogEntity.VName>
<PricingCPG>Magellan</PricingCPG>
- <ExpectedAnnualQuantity>
- <VQuantity>
<VAmount>1</VAmount>
<VUOM>EA</VUOM>
</VQuantity>
</ExpectedAnnualQuantity>
<PercentageBase>false</PercentageBase>
<DiscountALP>N/A</DiscountALP>
- <DiscountPercentage>
- <VPercentage documentId="2">
<Amount />
</VPercentage>
</DiscountPercentage>
<ProposedAgreementPrice />
- <CustomerRequestedPrice>
- <VMoney documentId="4">
<Amount />
</VMoney>
</CustomerRequestedPrice>
<Monthly>No</Monthly>
<PpaNoCap>N/A</PpaNoCap>
- <ProjectedMarketShare>
- <VPercentage documentId="5">
<Amount>0</Amount>
</VPercentage>
</ProjectedMarketShare>
<CustomerCommitted>Yes</CustomerCommitted>
<VState.VName>draft</VState.VName>
</StandardDealLineItem>
- <StandardDealLineItem documentId="5235490">
<IsImported>true</IsImported>
<VCatalogEntity.VName>MAG200</VCatalogEntity.VName>
<PricingCPG>Magellan</PricingCPG>
- <ExpectedAnnualQuantity>
- <VQuantity>
<VAmount>1</VAmount>
<VUOM>EA</VUOM>
</VQuantity>
</ExpectedAnnualQuantity>
<EffectiveFrom>11/15/2007</EffectiveFrom>
<DurationMonths>19</DurationMonths>
<PercentageBase>false</PercentageBase>
<DiscountALP>N/A</DiscountALP>
- <DiscountPercentage>
- <VPercentage documentId="2">
<Amount />
</VPercentage>
</DiscountPercentage>
<ProposedAgreementPrice />
- <CustomerRequestedPrice>
- <VMoney documentId="4">
<Amount />
</VMoney>
</CustomerRequestedPrice>
<Monthly>No</Monthly>
<PpaNoCap>N/A</PpaNoCap>
- <ProjectedMarketShare>
- <VPercentage documentId="5">
<Amount>0</Amount>
</VPercentage>
</ProjectedMarketShare>
<CustomerCommitted>Yes</CustomerCommitted>
<VValidity.from>11/15/2007</VValidity.from>
<VValidity.to>05/31/2009</VValidity.to>
<VState.VName>draft</VState.VName>
</StandardDealLineItem>
- <StandardDealLineItem documentId="5235491">
<IsImported>true</IsImported>
<VCatalogEntity.VName>MAG200</VCatalogEntity.VName>
<PricingCPG>Magellan</PricingCPG>
- <ExpectedAnnualQuantity>
- <VQuantity>
<VAmount>1</VAmount>
<VUOM>EA</VUOM>
</VQuantity>
</ExpectedAnnualQuantity>
<EffectiveFrom>11/15/2007</EffectiveFrom>
<DurationMonths>74</DurationMonths>
<PercentageBase>false</PercentageBase>
<DiscountALP>N/A</DiscountALP>
- <DiscountPercentage>
- <VPercentage documentId="2">
<Amount />
</VPercentage>
</DiscountPercentage>
<ProposedAgreementPrice />
- <CustomerRequestedPrice>
- <VMoney documentId="4">
<Amount />
</VMoney>
</CustomerRequestedPrice>
<Monthly>No</Monthly>
<PpaNoCap>N/A</PpaNoCap>
- <ProjectedMarketShare>
- <VPercentage documentId="5">
<Amount>0</Amount>
</VPercentage>
</ProjectedMarketShare>
<CustomerCommitted>Yes</CustomerCommitted>
<VValidity.from>11/15/2007</VValidity.from>
<VValidity.to>12/31/2013</VValidity.to>
<VState.VName>draft</VState.VName>
</StandardDealLineItem>
- <StandardDealLineItem documentId="5235493">
<IsImported>true</IsImported>
<VCatalogEntity.VName>RMAG100</VCatalogEntity.VName>
<PricingCPG>Magellan</PricingCPG>
- <ExpectedAnnualQuantity>
- <VQuantity>
<VAmount>1</VAmount>
<VUOM>EA</VUOM>
</VQuantity>
</ExpectedAnnualQuantity>
<PercentageBase>false</PercentageBase>
<DiscountALP>N/A</DiscountALP>
- <DiscountPercentage>
- <VPercentage documentId="2">
<Amount />
</VPercentage>
</DiscountPercentage>
<ProposedAgreementPrice />
- <CustomerRequestedPrice>
- <VMoney documentId="4">
<Amount />
</VMoney>
</CustomerRequestedPrice>
<Monthly>No</Monthly>
<PpaNoCap>N/A</PpaNoCap>
- <ProjectedMarketShare>
- <VPercentage documentId="5">
<Amount>0</Amount>
</VPercentage>
</ProjectedMarketShare>
<CustomerCommitted>Yes</CustomerCommitted>
<VState.VName>draft</VState.VName>
</StandardDealLineItem>
- <StandardDealLineItem documentId="5235494">
<IsImported>true</IsImported>
<VCatalogEntity.VName>RMAG100</VCatalogEntity.VName>
<PricingCPG>Magellan</PricingCPG>
- <ExpectedAnnualQuantity>
- <VQuantity>
<VAmount>1</VAmount>
<VUOM>EA</VUOM>
</VQuantity>
</ExpectedAnnualQuantity>
<EffectiveFrom>11/15/2007</EffectiveFrom>
<DurationMonths>74</DurationMonths>
<PercentageBase>false</PercentageBase>
<DiscountALP>N/A</DiscountALP>
- <DiscountPercentage>
- <VPercentage documentId="2">
<Amount />
</VPercentage>
</DiscountPercentage>
<ProposedAgreementPrice />
- <CustomerRequestedPrice>
- <VMoney documentId="4">
<Amount />
</VMoney>
</CustomerRequestedPrice>
<Monthly>No</Monthly>
<PpaNoCap>N/A</PpaNoCap>
- <ProjectedMarketShare>
- <VPercentage documentId="5">
<Amount>0</Amount>
</VPercentage>
</ProjectedMarketShare>
<CustomerCommitted>Yes</CustomerCommitted>
<VValidity.from>11/15/2007</VValidity.from>
<VValidity.to>12/31/2013</VValidity.to>
<VState.VName>draft</VState.VName>
</StandardDealLineItem>
- <StandardDealLineItem documentId="5235495">
<IsImported>true</IsImported>
<VCatalogEntity.VName>RMAG100</VCatalogEntity.VName>
<PricingCPG>Magellan</PricingCPG>
- <ExpectedAnnualQuantity>
- <VQuantity>
<VAmount>1</VAmount>
<VUOM>EA</VUOM>
</VQuantity>
</ExpectedAnnualQuantity>
<EffectiveFrom>11/15/2007</EffectiveFrom>
<DurationMonths>19</DurationMonths>
<PercentageBase>false</PercentageBase>
<DiscountALP>N/A</DiscountALP>
- <DiscountPercentage>
- <VPercentage documentId="2">
<Amount />
</VPercentage>
</DiscountPercentage>
<ProposedAgreementPrice />
- <CustomerRequestedPrice>
- <VMoney documentId="4">
<Amount />
</VMoney>
</CustomerRequestedPrice>
<Monthly>No</Monthly>
<PpaNoCap>N/A</PpaNoCap>
- <ProjectedMarketShare>
- <VPercentage documentId="5">
<Amount>0</Amount>
</VPercentage>
</ProjectedMarketShare>
<CustomerCommitted>Yes</CustomerCommitted>
<VValidity.from>11/15/2007</VValidity.from>
<VValidity.to>05/31/2009</VValidity.to>
<VState.VName>draft</VState.VName>
</StandardDealLineItem>
- <StandardDealLineItem documentId="5235497">
<IsImported>true</IsImported>
<VCatalogEntity.VName>309604</VCatalogEntity.VName>
<PricingCPG>Magellan</PricingCPG>
- <ExpectedAnnualQuantity>
- <VQuantity>
<VAmount>1</VAmount>
<VUOM>EA</VUOM>
</VQuantity>
</ExpectedAnnualQuantity>
<PercentageBase>false</PercentageBase>
<DiscountALP>N/A</DiscountALP>
- <DiscountPercentage>
- <VPercentage documentId="2">
<Amount />
</VPercentage>
</DiscountPercentage>
<ProposedAgreementPrice />
- <CustomerRequestedPrice>
- <VMoney documentId="4">
<Amount />
</VMoney>
</CustomerRequestedPrice>
<Monthly>No</Monthly>
<PpaNoCap>N/A</PpaNoCap>
- <ProjectedMarketShare>
- <VPercentage documentId="5">
<Amount>0</Amount>
</VPercentage>
</ProjectedMarketShare>
<CustomerCommitted>Yes</CustomerCommitted>
<VState.VName>draft</VState.VName>
</StandardDealLineItem>
- <StandardDealLineItem documentId="5235498">
<IsImported>true</IsImported>
<VCatalogEntity.VName>309604</VCatalogEntity.VName>
<PricingCPG>Magellan</PricingCPG>
- <ExpectedAnnualQuantity>
- <VQuantity>
<VAmount>1</VAmount>
<VUOM>EA</VUOM>
</VQuantity>
</ExpectedAnnualQuantity>
<EffectiveFrom>11/15/2007</EffectiveFrom>
<DurationMonths>74</DurationMonths>
<PercentageBase>false</PercentageBase>
<DiscountALP>N/A</DiscountALP>
- <DiscountPercentage>
- <VPercentage documentId="2">
<Amount />
</VPercentage>
</DiscountPercentage>
<ProposedAgreementPrice />
- <CustomerRequestedPrice>
- <VMoney documentId="4">
<Amount />
</VMoney>
</CustomerRequestedPrice>
<Monthly>No</Monthly>
<PpaNoCap>N/A</PpaNoCap>
- <ProjectedMarketShare>
- <VPercentage documentId="5">
<Amount>0</Amount>
</VPercentage>
</ProjectedMarketShare>
<CustomerCommitted>Yes</CustomerCommitted>
<VValidity.from>11/15/2007</VValidity.from>
<VValidity.to>12/31/2013</VValidity.to>
<VState.VName>draft</VState.VName>
</StandardDealLineItem>
- <StandardDealLineItem documentId="5235499">
<IsImported>true</IsImported>
<VCatalogEntity.VName>309604</VCatalogEntity.VName>
<PricingCPG>Magellan</PricingCPG>
- <ExpectedAnnualQuantity>
- <VQuantity>
<VAmount>1</VAmount>
<VUOM>EA</VUOM>
</VQuantity>
</ExpectedAnnualQuantity>
<EffectiveFrom>11/15/2007</EffectiveFrom>
<DurationMonths>19</DurationMonths>
<PercentageBase>false</PercentageBase>
<DiscountALP>N/A</DiscountALP>
- <DiscountPercentage>
- <VPercentage documentId="2">
<Amount />
</VPercentage>
</DiscountPercentage>
<ProposedAgreementPrice />
- <CustomerRequestedPrice>
- <VMoney documentId="4">
<Amount />
</VMoney>
</CustomerRequestedPrice>
<Monthly>No</Monthly>
<PpaNoCap>N/A</PpaNoCap>
- <ProjectedMarketShare>
- <VPercentage documentId="5">
<Amount>0</Amount>
</VPercentage>
</ProjectedMarketShare>
<CustomerCommitted>Yes</CustomerCommitted>
<VValidity.from>11/15/2007</VValidity.from>
<VValidity.to>05/31/2009</VValidity.to>
<VState.VName>draft</VState.VName>
</StandardDealLineItem>
- <StandardDealLineItem documentId="5235501">
<IsImported>true</IsImported>
<VCatalogEntity.VName>309653</VCatalogEntity.VName>
<PricingCPG>Magellan</PricingCPG>
- <ExpectedAnnualQuantity>
- <VQuantity>
<VAmount>1</VAmount>
<VUOM>EA</VUOM>
</VQuantity>
</ExpectedAnnualQuantity>
<PercentageBase>false</PercentageBase>
<DiscountALP>N/A</DiscountALP>
- <DiscountPercentage>
- <VPercentage documentId="2">
<Amount />
</VPercentage>
</DiscountPercentage>
<ProposedAgreementPrice />
- <CustomerRequestedPrice>
- <VMoney documentId="4">
<Amount />
</VMoney>
</CustomerRequestedPrice>
<Monthly>No</Monthly>
<PpaNoCap>N/A</PpaNoCap>
- <ProjectedMarketShare>
- <VPercentage documentId="5">
<Amount>0</Amount>
</VPercentage>
</ProjectedMarketShare>
<CustomerCommitted>Yes</CustomerCommitted>
<VState.VName>draft</VState.VName>
</StandardDealLineItem>
- <StandardDealLineItem documentId="5235502">
<IsImported>true</IsImported>
<VCatalogEntity.VName>309653</VCatalogEntity.VName>
<PricingCPG>Magellan</PricingCPG>
- <ExpectedAnnualQuantity>
- <VQuantity>
<VAmount>1</VAmount>
<VUOM>EA</VUOM>
</VQuantity>
</ExpectedAnnualQuantity>
<EffectiveFrom>11/15/2007</EffectiveFrom>
<DurationMonths>74</DurationMonths>
<PercentageBase>false</PercentageBase>
<DiscountALP>N/A</DiscountALP>
- <DiscountPercentage>
- <VPercentage documentId="2">
<Amount />
</VPercentage>
</DiscountPercentage>
<ProposedAgreementPrice />
- <CustomerRequestedPrice>
- <VMoney documentId="4">
<Amount />
</VMoney>
</CustomerRequestedPrice>
<Monthly>No</Monthly>
<PpaNoCap>N/A</PpaNoCap>
- <ProjectedMarketShare>
- <VPercentage documentId="5">
<Amount>0</Amount>
</VPercentage>
</ProjectedMarketShare>
<CustomerCommitted>Yes</CustomerCommitted>
<VValidity.from>11/15/2007</VValidity.from>
<VValidity.to>12/31/2013</VValidity.to>
<VState.VName>draft</VState.VName>
</StandardDealLineItem>
- <StandardDealLineItem documentId="5235503">
<IsImported>true</IsImported>
<VCatalogEntity.VName>309653</VCatalogEntity.VName>
<PricingCPG>Magellan</PricingCPG>
- <ExpectedAnnualQuantity>
- <VQuantity>
<VAmount>1</VAmount>
<VUOM>EA</VUOM>
</VQuantity>
</ExpectedAnnualQuantity>
<EffectiveFrom>11/15/2007</EffectiveFrom>
<DurationMonths>19</DurationMonths>
<PercentageBase>false</PercentageBase>
<DiscountALP>N/A</DiscountALP>
- <DiscountPercentage>
- <VPercentage documentId="2">
<Amount />
</VPercentage>
</DiscountPercentage>
<ProposedAgreementPrice />
- <CustomerRequestedPrice>
- <VMoney documentId="4">
<Amount />
</VMoney>
</CustomerRequestedPrice>
<Monthly>No</Monthly>
<PpaNoCap>N/A</PpaNoCap>
- <ProjectedMarketShare>
- <VPercentage documentId="5">
<Amount>0</Amount>
</VPercentage>
</ProjectedMarketShare>
<CustomerCommitted>Yes</CustomerCommitted>
<VValidity.from>11/15/2007</VValidity.from>
<VValidity.to>05/31/2009</VValidity.to>
<VState.VName>draft</VState.VName>
</StandardDealLineItem>
- <StandardDealLineItem documentId="5235505">
<IsImported>true</IsImported>
<VCatalogEntity.VName>BOS350</VCatalogEntity.VName>
<PricingCPG>Magellan</PricingCPG>
- <ExpectedAnnualQuantity>
- <VQuantity>
<VAmount>1</VAmount>
<VUOM>EA</VUOM>
</VQuantity>
</ExpectedAnnualQuantity>
<PercentageBase>false</PercentageBase>
<DiscountALP>N/A</DiscountALP>
- <DiscountPercentage>
- <VPercentage documentId="2">
<Amount />
</VPercentage>
</DiscountPercentage>
<ProposedAgreementPrice />
- <CustomerRequestedPrice>
- <VMoney documentId="4">
<Amount />
</VMoney>
</CustomerRequestedPrice>
<Monthly>No</Monthly>
<PpaNoCap>N/A</PpaNoCap>
- <ProjectedMarketShare>
- <VPercentage documentId="5">
<Amount>0</Amount>
</VPercentage>
</ProjectedMarketShare>
<CustomerCommitted>Yes</CustomerCommitted>
<VState.VName>draft</VState.VName>
</StandardDealLineItem>
- <StandardDealLineItem documentId="5235506">
<IsImported>true</IsImported>
<VCatalogEntity.VName>BOS350</VCatalogEntity.VName>
<PricingCPG>Magellan</PricingCPG>
- <ExpectedAnnualQuantity>
- <VQuantity>
<VAmount>1</VAmount>
<VUOM>EA</VUOM>
</VQuantity>
</ExpectedAnnualQuantity>
<EffectiveFrom>11/15/2007</EffectiveFrom>
<DurationMonths>19</DurationMonths>
<PercentageBase>false</PercentageBase>
<DiscountALP>N/A</DiscountALP>
- <DiscountPercentage>
- <VPercentage documentId="2">
<Amount />
</VPercentage>
</DiscountPercentage>
<ProposedAgreementPrice />
- <CustomerRequestedPrice>
- <VMoney documentId="4">
<Amount />
</VMoney>
</CustomerRequestedPrice>
<Monthly>No</Monthly>
<PpaNoCap>N/A</PpaNoCap>
- <ProjectedMarketShare>
- <VPercentage documentId="5">
<Amount>0</Amount>
</VPercentage>
</ProjectedMarketShare>
<CustomerCommitted>Yes</CustomerCommitted>
<VValidity.from>11/15/2007</VValidity.from>
<VValidity.to>05/31/2009</VValidity.to>
<VState.VName>draft</VState.VName>
</StandardDealLineItem>
- <StandardDealLineItem documentId="5235655">
<IsImported>true</IsImported>
<VCatalogEntity.VName>AMS300</VCatalogEntity.VName>
<PricingCPG>Magellan</PricingCPG>
- <ExpectedAnnualQuantity>
- <VQuantity>
<VAmount>1</VAmount>
<VUOM>EA</VUOM>
</VQuantity>
</ExpectedAnnualQuantity>
<EffectiveFrom>11/15/2007</EffectiveFrom>
<DurationMonths>74</DurationMonths>
<PercentageBase>false</PercentageBase>
<DiscountALP>N/A</DiscountALP>
- <DiscountPercentage>
- <VPercentage documentId="2">
<Amount />
</VPercentage>
</DiscountPercentage>
<ProposedAgreementPrice />
- <CustomerRequestedPrice>
- <VMoney documentId="4">
<Amount />
</VMoney>
</CustomerRequestedPrice>
<Monthly>No</Monthly>
<PpaNoCap>N/A</PpaNoCap>
- <ProjectedMarketShare>
- <VPercentage documentId="5">
<Amount>0</Amount>
</VPercentage>
</ProjectedMarketShare>
<CustomerCommitted>Yes</CustomerCommitted>
<VValidity.from>11/15/2007</VValidity.from>
<VValidity.to>12/31/2013</VValidity.to>
<VState.VName>draft</VState.VName>
</StandardDealLineItem>
</VItems>
</StandardDeal>
</sta:entity-data>
Regards,
Ekta

1.Through ctrl file and log file using SQL LoaderPlease clarify :
Do you want to load the entire file into a single column (XMLType or CLOB), or do you want to extract XML data and store it into different relational columns?
Please also edit your first post and use tags to enclose the XML source, and do not copy/paste directly from your browser, use "view source" feature so that the content doesn't retain navigation characters (+/-).
Edited by: odie_63 on 11 nov. 2012 13:20

Data integrator for HP-UX missing data quality and data profiling

Hi All,
I have installed ODI 10.1.3.40.0 from odi_unix_generic_10.1.3.4.0.zip in HP unix 11.23.
Data quality and data profiling is missing in that zip ? Could anyone please help me how to get installer of data quality and data profiling for Oracle data integrator in HP UX 11.23.
Any response will be highly appreciated.
Thanks in advance.
regards
Umapada
Edited by: user10612738 on Nov 28, 2008 1:54 AM

The integrated packaged( ODi, data quality and data profiling) for HP-UX wount available till 10.1.3.5.0 which will be released by this year end.

EasyDMS - search by date range for characteristics of type date

Hi Folks,
I have a characteristic of type date in the additional data of a DMS document. If I enter the date (for example validity date) as 08/31/2009 and search using cv04n and give a date range for the characteristic (i.e. 01/01/2009 - 12/31/2009), the search result will bring up the document.
However, I cannot do this from the EasyDMS find function. I need to specify an exact date. This is not very helpful for user who need to find documents with a validity date between 01/01/2009 - 12/31/2009 for example. Is there a way users can search for date range in EasyDMS find function?
Thanks,
Lashan

To search a date range with EasyDMS Client you have to set the registry key
\HKEY_CURRENT_USER\Software\SAP\EasyDms\Generel\DateSearchPick to Value 0
Then you can use the input field like in SAP-Gui. (01.01.2009-31.01.2009)
If you set the value to 1 or the key is not defined you can only search for one specified date.
If you don't find this key on your PC create it as dword.
Maybe you must restart you PC for takeing effect.
Hope this will help you.
Regards Wolfgang

Caching system for loading reference table data

Hi,
I want to load the small reference table data into memory and later i want to query the data in the memory. That table wont be updated frequenctly.I dont want to to load the query results in the memory. As i know i can do it by IBatis or Hibernate. I want to load the reference table data into memory once and want to use the data in memory for querying. Suppose i have a Department table with 100 rows with columns as DeptNO, DeptName and NoOfEmployees. I want to load all the records in to memory and later i want to run queries like getDepartmes where NoEmployees >50. queries can be dynamic.Is it possible with any Java caching systems.

They allow you to manipulate collections (duh) of objects. Typically, but not exclusively, using a comparator or somesuch. The sort of operation you're describing can be carried out reasonably swiftly by merely iterating over the items - unlikely to be as slow as a database round-trip.
If you need something particularly sophisticated then you can either craft a suitable data structure to contain it, or go for the generic solution of an embedded database (and if you go for this option, you might want to apologise for biting my head off).
Or, indeed, you can use a query cache if you need no dynamic capabilities whatsoever (i.e. query with a <50 constraint twice and the second one is fast, but do it again with a <49 constraint and it takes just as long as the first one).

Data Type for saving Base64 image string into SQL database

Hi Team! I have image base64 string to be save into sql database. I use Varchar(MAX) data type. The problem is there are certain image string that cannot be enter (paste) into the table (due to the size) then i need to resize the image then i can paste
the string into the table. How to make all image string size be able to be save in the table? Or there is limit on the image size to be save into the table? I'm using mssql 2008. Thanks a lot.

There is a limit of 2GB. Which means that the actual image size must be less, since you encode the image in Base64 for some reason.
Now, "pasting" strings is not the normal way to store data in an SQL Server database, so the question is a little funny. Normally data is stored in a database through a program of some sort. One way is to use OPENROWSET(BULK) as HuaMin suggested.
Here is a link to a simple example of how to do it from .NET:
http://www.sommarskog.se/blobload.txt
Erland Sommarskog, SQL Server MVP, [email protected]

ABAP routine for loading previous months data in infopackage

Hi,
I have an infopackage included in a process chain. The issue is that I need to load previous month's data through the infopackage and I have a data field which is of date type. I could not find an appropriate OLAP variable so I chose the ABAP code in the infopackage. My knowledge of ABAP is not very good so I thought I could get some insight from someone. Need this to be a periodic job/regular without any developer interference.
Edited by: BG on Apr 9, 2008 1:03 PM

Hi
Try this code and see if you are able to achive the results
data: month(2).
data: date like sy-datum,
      last like sy-datum,
      first like sy-datum.
read table l_t_range with key
fieldname = 'BLDAT'.
l_idx = sy-tabix.
date = sy-datum.
month = date+4(2).
if month = 12.
month = 01.
else.
month = month - 1.
endif.
move month to date+4(2).
call function 'SLS_MISC_GET_LAST_DAY_OF_MONTH'
exporting
    day_in                  = date
IMPORTING
   LAST_DAY_OF_MONTH       = last
EXCEPTIONS
DAY_IN_NOT_VALID        = 1
OTHERS                  = 2
if sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
first = last.
move 01 to first+6(2).
l_t_range-low = first
l_t_range-high = last
l_t_range-sign = 'I'.
l_t_range-option = 'BT'.
modify l_t_range index l_idx.
p_subrc = 0.
paste the code as it is in your editor activate this and see if you are able to achive the results.
assign points if useful.
regards
Vishal
Edited by: Vishal Vashishta on Apr 9, 2008 2:33 PM

Do not Extract from PSA but Access Data Source (for Small Amounts of Data)

Hi Experts,
In the DTP, the above option is available for Full Loads for certain extractors but not for others, particularly, certain HR extractors?
Is there a way to make it available for HR extractors? Is there a setting that needs to be updated in ECC or in BI?
Thank you for your help!

Hi,
There is no special setting for this, Please see the detail description:
Data is not extracted from the PSA for the DataSource; it is requested from the data source directly at DTP runtime.
Use
You use this mode for small data sets and full uploads, for example, small sets of master data. With file source systems, note that the file has to be available on the application server.
Dependencies
You do not have to create an InfoPackage in order to extract data from the source.
Data in the data source is accessed in "direct access mode". This has certain consequences, especially if you are extracting data from SAPI systems:
Data is extracted synchronously. This places a particular demand on the main memory, especially in remote systems.
The SAPI extractors may respond differently than during asynchronous load since they receive information by direct access.
SAPI customer enhancements are not processed. Fields that have been added using the append technology of the DataSource remain empty. The exits RSAP0001, exit_saplrsap_001, exit_saplrsap_002, exit_saplrsap_004 do not run.
If errors occur during processing in BI, you have to extract the data again since the PSA is not available as a buffer. This means that deltas are not possible.
In the DTP, the filter only contains fields that the DataSource allows as selection fields. With an intermediary PSA, you can filter in the DTP by any field.
Regards,
Kams

Data error when loading to master data?

Hi,
I am loading data from Data base to BW.It is a master data loading.I got an error in the 8th package of the load for the time field which is server update time(reference 0TIME) .The data server update time for that particular record is '19900101'.I am really confused what is the error with this kind of data?
Here is error message:
0TIME: Data record 1797 ('3YV4C0EJBWTGO1CA'): Version '199001' is not valid
Message no. RSDMD194
Diagnosis
Data record 2. with the key '3.' is invalid in value '4.' of the attribute/characteristic 1..
System Response
The system has recognized that the value mentioned above is invalid, and has processed this general error message. A subsequent message may give you more information on the error. This message refers to the same value, even though it does not state this explicitly.
Procedure
If this message appears during a data load, maintain the attribute in the PSA maintenance screens. If this message appears in the master data maintenance screens, leave the transaction and call it again. This allows you to maintain your master data.
Please help me to resolve this also explain what is the differnce in this kind of data?
Thanks,
Vasu

right click on the master data --> delete master date, BUT you will only be able to delete master data not used in a cube (you'll get a pop up to confirm this)...if you want to delete master data already used in a cube, you need to delete the contents of this cube first (and any other cube where this master data is used)...only then you can completely delete the master data entries
M.

Data interpreter for loading of DASYLAB data into DIADEM

Similar Messages

Maybe you are looking for