Model Domain attribute as NUMERIC datatype

I have an attribute which has a set of allowable integers as accepted values (domain values). I could model it using domain based entity but both Name and Code are
Text data types by default and cant be changed. I think this is a limitation of MDS 2012 where we can achieve the results but with a workaround. Any suggestions?
Thanks, Ashish Singh

You could have another Numeric column in your Domain based Entity that is truly a number.
Name Column MyNumber
'One' '1' 1 (quotes to show its a string)
Then you would have Business Rule Access to this Column from the main Entity. ( when you expand the domain based entity in BRs you will see all fields inside of the child entity, in the example above you would see MyNumber)
If used by BR then you are done.
If you wanted to sort on this or filter just in UI , you could (ok I know not the best but) create another numeric column and set it to the value via Business Rule from the underlying Domain Based entity value.

Similar Messages

Logical Model - Entity Attribute?

Hi ,
Thanks in responding to my posting.
I am using SQL DM 3.0.0.665. I need your thoughs on following.
1) Do we able to select multiple entities for entity reporting? I find an option for all entities then it ask us to pick only one entity to report.
2) Are we able to build a report for all entities in a subview?
3) I see Formula (Default Value), Preferred Abbreviation and Synonyms for each attribute in Entity Details report. I am not able to find a place to fill those in attribute definitions. Where can we supply those details, so it could print in reports?
Thanks in helping us out.

I find the following for Attribute Properties in SQL DM Help
=============
Attribute Properties
This dialog box displays the properties of an attribute, which is a component of an entity in the Logical Model.
General
Name: Name of the attribute.
Synonym: Synonym for the attribute.
Preferred Abbreviation: Name that will be used for any corresponding table column during forward-engineering if the Use Preferred Abbreviations option is enabled in the Engineering dialog box.
Long Name: Long name in the format: entity-name.attribute-name.
Allow Nulls: Controls whether null values are allowed for the attribute. If this option is enabled, a non-null value is mandatory.
Datatype: Enables you to specify a domain, logical type, distinct type, collection type, or structured type as the data type of the attribute. You can click the ellipsis (...) button to specify further details for the selected type.
Entity: Name of the entity with which the attribute is associated.
Source Name: User-specified name of the source for this attribute.
Source Type: Manual, System, Derived, or Aggregate.
Formula Description: For a derived or aggregate source type, the formula for the attribute.
Scope: For a structured type with Reference enabled, limits the scope by specifying the table in which the type is implemented.
Type Substitution: For a structured type with Reference disabled, or for a structured type applied to an entity, controls whether a substitutional structured type is generated in the DDL.
Default and Constraint
Constraint Name: Name of the constraint.
Default Value: Default value for the attribute.
Use Domain Constraints: Controls whether the properties defined in Domains Administration for the associated domain are used. If this option is disabled, you can use the remaining fields to specify the database type for the constraint and the ranges or a list of values.
Constraint: Enables you to specify a constraint for one or more types of databases.
Ranges: Enables you to specify one or more value ranges for the attribute.
Value List: Enables you to specify a list of valid values for the attribute.
Permitted Subtypes
For a structured data type, lists all subtypes for the attribute, and lets you specify whether each is permitted for the attribute.
=============
but most of the above are not showing up in attribute definition window. How do we see those?

Engineer to Relational Model: deleted attributes / undeleted columns

Hello,
I am using Datamodeler 3.3.0.744.
I'm modifying an existing logical model: I'm deleting one or more attributes in an Entity.
Then I'm executing "Engineer to Relational Model" in oder to get an up to date Relational Model (it existed already).
The corresponding columns are not deleted in the Relational Model, even though attributes don't exist anymore at the logical level.
I can't find any option available in order to do that...
In the previous release (3.1), it worked fine, I could choose the behavior related to the deleted attributes (deleting or not deleting corresponding columns).
Edited by: user4995029 on 27 mai 2013 02:43

When your forward engineer for a 2nd time you should see a dialog that has the logical on the left and the relational on the right. Entities that are new or changes have an exclamation point next to them. If you open that you will eventually drill down to see the attribute/columns. Where your dropped an attribute it will say "To drop". The check box is unchecked by default. If you check it then when you forward engineer those should get dropped from the associated table.
Is it not working that way in 3.3?

How tp populate EVS from a Model node attribute

Hi All,
i have some records in the model table mapped to a node in the view. i wanna to use the OVS to select the particular attribute but don't know how to do it.
i have bounded that particular column to the inputField but when i write this code
IWDAttributeInfo atInfo =
wdContext.nodeActivity().getNodeInfo().getAttribute( IPrivateEVSView.IActivityElement.SYNC__KEY);
ISimpleType synckeyType = atInfo.getSimpleType();
<b>ISimpleValueSet valueset = synckeyType.getSVServices().getValues();</b>
i get the NUllPointerException at the last line.
How to get the ValueSet in this case and populate the OVS.
Plz help
Rgds.
Vilish
I have studied EVS tutorial at SDN.

Hi Vilish,
OVS is quite different thing, what you are trying to do here is to create modifiable value set (SVS), right?
Then you have to use:
ISimpleTypeModifiable type =
atInfo.getModifiableSimpleType();
IModifiableSimpleValueSet msvs =
type.getSVServices().getModifiableSimpleValueSet();
msvs.put(<key>, <value>);
Also check that type of attribute is simple type (string, integer etc) or derivate thereof.
Valery Silaev
EPAM Systems
http://www.netweaverteam.com/
P.S. If you really need to use OVS then corresponding tutorial is https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/5dcbe990-0201-0010-2c99-a2bc9e61acfc

Data Modeler: FK attribute name synchronization

I have this option enabled by default .
How can i disable this on per table basis?
thank you
Andrew

I don't understand, sorry.
"FK attribute name synchronization" is an option in the tools->general options->model -> logical . Once set it enforces the name of the PK column to be used as a name of the column in FK. this works as expected. The problem that i have is when i have self-reference relation ( employee_id -> manager_id ) - in this case the column name is the name of the PK column and number "1".
CREATE TABLE USER_STRATIFICATION_BIN
     user_stratification_bin_id NUMBER NOT NULL ,
     node_id VARCHAR2 (256) NOT NULL ,
     <skip>
     user_stratification_bin_id1 NUMBER ,
     user_stratification_display_id NUMBER NOT NULL
    ) LOGGING
ALTER TABLE USER_STRATIFICATION_BIN
    ADD CONSTRAINT USR_STRT_BIN_USR_STRT_BIN_FK FOREIGN KEY
     user_stratification_bin_id1
    REFERENCES RMBSWLOAN.USER_STRATIFICATION_BIN
     user_stratification_bin_id
    ON DELETE SET NULL
    NOT DEFERRABLE
;i need it to be smth else BUT "user_stratification_bin_id1".
Please advise.
Edited by: AndrewZ on Jan 26, 2010 9:17 AM

Options for modeling massterdata attributes which can have multiple values

Hallo All BW Experts!
here is a modelling requirement which i find quite interesting and challenging.
How can we use attributes for a masterdata which can have multiplevalues. Currently these kind of attributes are stored in seperate ODS. One example for such a requirement might be the Busines Partner groupes. Each Business partner can be in more than one group.
my question is , How can we modell such kind of masterdata model which enables us to use these attributes for restrictions in reporting from various independent infoproviders. Main problem is due to the condition that the no of such groups per each user is not fixed and can be changed in runtime.
any suggession will be rewarded.
with regards
ashwin

Hi Arun!
Is there any possiblily to create such a model in BW which is flexible. One option might be to use a heirarchy. Actually the requirement looks like this. We must be able to analyse all businesspartner data and with that data we will be able to group the customers into various target groups. now we want to anyalyse the performance of such target grouops in past time.
to be simple
1) it is possible to create customer groups based on masterdata charecteristics.(there is lot of facilitiey available in BW3.5 and more in 7.0 for this) this is very dynamic
2) Now is it in anyway possible to analayse the performance of such a group. I think currently heirarchies serve such purpose but small limitation in SAP is that they must not contain more than 100000 records otherwise the performance is siverly limited.
any suggestion
with regards
ashwin

Create Attribute Dimension - Numeric

Hi,
11.1.2.2 - ASO
Have a Customer dimension about 500K leaf level members. Want to create a numeric attribute dimension named 'Cust_ID' and the values would be 1 to 500K or so. I create the dim, manually create two sample leaf level children ( 1 and 2). I keep getting this error:
1: Attribute level 0 member name must match attribute format name setting
I can't figure out where to change this. On base dim or attrib dim. I have never created a numeric attribute dim before.
Thanks

I just forced save and re-opened and then verified and it verified. I knew something weird like that was happening. Looks like a bug.

Default model search attributes

Hi guys,
Using JDeveloper 11.1.1.6 and JHeadstart 11.1.1.4.26.
I'm having problems with the default model search component. As per section 7.1.2 of the JHS Developers guide, I have "not specified any view criteria which results in a default search where the user can select all attributes that have "Queryable" checked in the view object attribute editor".
This works fine until I need to change the queryable status of some of the view attributes. Even after unselecting the queryable attribute in the view object, the attribute is still being shown in the quick and advanced search fields. I have tried deleting the page/page def/task flow etc and regenerating but the original attributes always remain in the search area. This seems to work ok for view objects based on entities but does not for non-entity view objects.
I can see in the pageDef that the searchregion component has an attribute "Criteria" populated with "__ImplicitViewCriteria__". How does this criteria get populated ? And why do my original attributes remain in the search fields even though they no longer are specified as "queryable" in the view object.
I'm tearing my hair out trying to get these old fields to disappear from the search components - HELP !
Cheers,
Brent

Brent,
Can you create a drag and drop page without JHeadstart on the same VO?
Do you get the same behavior? If so, you might try the JDeveloper forum, maybe it is a known issue.
Steven Davelaar,
JHeadstart Team.

Precision and scale for numeric datatypes

Could be in XSU, could be in Oracle thin driver, but I'd expect the SAL column of the EMP table to include its precision and scale, e.g. 800.00 and not 800.
oracle: decribe EMP
NAME TYPE
SAL NUMBER(7,2)
sql server: sp_help EMP
Column_name Type Length Prec Scale
SAL numeric 5 7 2
sql server:
java myOracleXML getXML -conn "jdbc:inetdae7:aetius:1433?database=Northwind" -user "sa/sa" "select SAL from EMP where EMPNO > 7999"
<?xml version = '1.0'?>
<ROWSET>
<ROW num="1">
<SAL>800.00</SAL>
</ROW>
</ROWSET>
oracle:
java OracleXML getXML -user "scott/tiger" "select sal from
emp where empno > 7999"
<?xml version = '1.0'?>
<ROWSET>
<ROW num="1">
<SAL>800</SAL>
</ROW>
</ROWSET>
So who loses the scale in the Oracle case, the driver or XSU.
Steve.

user4928701 wrote:
Specifying precision and scale in the datatype when creating a procedure does not work:
create or replace function SqlTxFunctionTesting(inparam in number(9,2)
Error(1,48): PLS-00103: Encountered the symbol "(" when expecting one of the following: := . ) , @ % default character The symbol ":=" was substituted for "(" to continue.
And one of the cons in the PL/SQL language in my view.
The language does not allow parameters to be declared in the fashion you are attempting to. Even declaring a subtype and using that, does not enforce either the precision or scale, on the parameter value passed.
Even worse - the parameter value can be a different data type all together from the defined parameter type - and a silent and implicit data type conversion will be done at run-time.
So you can expect run-time errors in your code unit caused by the caller passing invalid values, despite the compiler okaying the call from the caller to your code.
There are pros and cons to this approach. But if you are from a very strong type language environment like C or Pascal, you tend to see more cons than pros in this specific case.

Problems displaying Sybase Numeric DataTypes

Hello,
I have a universe built on top of a Sybase ASE database. The universe contains a Number object which maps to a Sybase Numeric data type with a data type length of 9 and precision of 19.
When we pull the data form this object onto a webi report the values are being rounded up for example 75000000041611650 instead of 75000000041611700.
Has anyone encountered this problem before and what was the solution? We are on SAP BI 4.1 SP5
Thanks..

Hi ,
For numeric data Bo will not support data having digits > 15.
So for correct output convert the numberic data to varchar in universe then use the same object on report.
Thanks,
Swapnil

Default behavior of numeric datatype

Discoverer 10g Rel.2: 10g BI Tool
The default behavior for numerics in Discoverer appears to require that you choose sum, count, etc when creating a workbook. Our data is mostly numeric codes, some of which would obviously be innapropriate to do calculation on. How do I over-ride this default behavior? I cannot see in the administrator tool where it allows me, under properties, to modify this. TIA.

Hi TIA
You go to the Properties of the item in Discoverer Administrator. If you look down the list, about one third of the way down, you will see a property called Default Position. This is the property that determines whether an item is used in calculations or not.
The default setting for numbers is Data Point. Changing this from this to any of the other settings will stop the calculation behavior. The one I would use is Top or Side.
By the way, this setting determines which axis the item will be placed on by default. In Discoverer there are four axes:
1. Data Points - these are the items that will be used in calculations
2. Side - on the side of a Crosstab, otherwise on the top
3. Top - on the top of a table or crosstab
4. Page - in page items
Hope this helps
Best wishes
Michael

IQ 16, jConnect 16 and numeric datatype

Hi,
I have a situation where I create a table like this:
CREATE TABLE DBA.A_TEST (
PK INTEGER DEFAULT AUTOINCREMENT NOT NULL,
TEST_9_2 NUMERIC(9,2),
PRIMARY KEY (PK)
INSERT INTO A_TEST (TEST_9_2) VALUES (2.01)
When I select the value 2.01 into a BigDecimal (java) value and then use that value to update it on the IQ server (jConnect version is:
jConnect Driver version: jConnect (TM) for JDBC(TM)/16.0 PL03 (Build 27073)/P/EBF23152/JDK 1.6.0/jdbcmain/OPT/Wed Jul 16 00:36:57 PDT 2014
the value 2 is sent. This occurs when DynamicPrepare = true (default value for jConnect 7.X and 16.0).
I find that the Update command, when sent in DYNAMIC tds receives this from IQ:
PARAMFMT
returns TDS_INT4, usertype = 58
jConnect then calls sp_sql_type_name with the 56 for data type and 58 for user type. This seems to cause the update statement to send "2" instead of "2.01". Is this a known issue?
It does seem if I set DYNAMIC_PREPARE = false, then the update works fine (since it explicitly depends on the binding for the parameter.)
File bigdeciTest157.txt is the java jdbc source
testbd_iq16_dp_true_esd05.txt is the TDS on a run - using 7.07 ESD#5 (16.0 PL03 jConnect had same behavior).
I'm thinking the dynamic prepare might not be fully supported on IQ? I notice the dynamic prepare is allocated but on executions only TDS_LANGUAGE is sent and executed. Is this normal as well?
Cheers,
-Paul

Hi Paul,
Likely Jconnect CR#762132 (allableStatement with BigDecimal , SQL Types.DECIMAL scale zero should error.)
fixed in Conn 15.7 SP130 and Conn16 PL04.
Regards,
Tayeb.

Lync Federation and Push Notification with Lync Trusted model domain

Hi Team,
One of our customer has the query about office 365 push nofification support.
We have three kinds of federation types:
Dynamic
Direct
Enhanced
Questions:
Whether all the three are supported by office 365 push notification server or only specific federation type is supported?
Please advise. Many Thanks.

Hi,
Base on my understanding, as there is no special DNS requirements to enable federation for push notification. You only need to do the following steps:
Enable federation and public IM connectivity in Lync Server 2013
Create public SIP federated providers in Lync Server 2013
Create hosted SIP federated providers Lync Server 2013
More details:
https://technet.microsoft.com/en-us/library/hh690047.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Right-click remove favicon from tab ( domain ) + attribute a tab color or custom favicon from it

Hi, I'm a developer, huge user of firefox, and my work gets messy each time I have 3 tabs of a front + 3 tabs of different backoffices adresses, having the same favicon .. all of those pinned .. and I spend most of my time ctrl tabbing between each of those ..
I'm wondering if there's a way to remove the favicon display from a tab, so there will be none and another plugin could put a random color favicon in place :)
regards

Maybe:
*Colorful Tabs: https://addons.mozilla.org/firefox/addon/colorfultabs/

Attribute member datatype is not matching in Essbase Studio

Hi All,
When I was trying to build the ASO cube by adding attributes it throwing below error
Failed to deploy Essbase cube.
Caused by: Cannot end incremental build. Essbase Error(1007083): Dimension build failed. Error code [-1]. Check the server log file and the dimension build error file for possible additional info.
\\Outline verification errors:
\\Attribute member datatype is not matching with Attribute dimensions datatype.
\\Illegal datatype for attribute member
\\Attribute member (Name) datatype is not matching with Attribute dimensions datatype.
\\Illegal datatype for attribute member Name
Here every thing is "String only" and i verified in backend it will show ing datatype as "Varchar".
Can someone assit me how to resolve this error.Thanks in Advance
Regards,
SatyaB

Did you tried CASTing your source data to match it attribute dimension type? Just CAST all source data before its loaded and it should help resolve any data mismatch type errors.
I think I have an integration where we use VARCHAR2 type data mapped to string dimension.

Model Domain attribute as NUMERIC datatype

Similar Messages

Maybe you are looking for