Data Type Evaluation Order

Hi,
I want to get some clarification regarding the Data Type Evaluation Order (DTEO) for a Planning application.
In the EPMA Administrator's guide it says that the DTEO defines the order of precedence when at the intersection of two members of two dimensions have separate data types. I have a specific case and couldn't find any details regarding that in the documentation.
If I take two dimensions A and B. For one particular member of A I choose percent as the data type and the other members are all unspecified. For dimension B all members have data type currency.
In the evaluation order I specify A first followed by B. So when the percent member of A will intersect with any member of B, the data type should be percent because of the evaluation order.
However, the other members are unspecified. In case of intersection of those members of A with any member of B, which data type will take precedence - Unspecified from A or Currency from B (remember that A is higher in the order but in this case the data type is unspecified)?
Shehzad

If you've specified dimension A above dimension B in the evaluation order, then dimension A will <em>always </em>take precedence over dimension B, even when the data type of the particular dimension A member is "Unspecified." In that case, the member data will be displayed on forms without any of the formatting characteristics specified for currency, non-currency, or percentages on the <em>Other Options</em> tab of the form definition.
You should be able to prove or disprove this by constructing a simple form that reflects the scenario in question.

Similar Messages

LOCID is not defiend for Order data type ORDR

Dear All,
I am trying to load data in to Order forecast details in Dynamic
replenishment of SNC in the WEB UI, after entering the Product and
Customer location, when I clicked on GO system is giving the below
error.
Time series error in class /SCF/CL_ICHDM_DEMANDMN_DATAAXS
method /SCF/IF_ICHDMAXS_2_CNTL~SELECT
Access error for time series type DFC01, key figure CORDEROR, ODM
message: Parameter LOCID is not define for order data type ORDR
Could you please help me out what to do in this case.
I have re activated the following components mentioned, still system is
giving the above problem.
Activate Order Component
Activate Order Data Type
Activate Order Data Area
and
Activate Time Series Data Type
Activate Time Series Data Area
Thanks and Regards,
T.Muthyalappa

Hi,
Make sure you have proper authorization.(sometime system does not display the error but user don't have authorization to create/update/modify table entries to be on safer side assign SAP_ALL profile to your ID if it is allowed as per your company security process).
I think issue is with InfoObject 9ALOCID is not activated properly.
You need activate InfoObject 9ALOCID as mention i below step2 but it is better you follow below steps.
1) Then force generate ODM.
2)Go to transaction code:/N/SCA/TSDM09 enter time series DFC01 and select Radio button Activate Planning object Structure.
Regards,
Nikhil.

Details on data types for posting data to DB2 on AS400 from XI

Hi
We have a scenario in which we post data from XI (3.0, SP23 ) to DB2 on AS400 and we are using jdbc adapters ( jdbc drivers from IBM deployed on XI J2EE server as per SAP's instructions )
On AS400-DB2, there are two files F1 and F2 that we have to update in a particular library L1 - on a server S1. Each of the two files has a single field with the same name as that of the file.
I have the following questions :
1. How do we construct/specify the data type in order to convert XML from XI to the sql that DB2 needs - I do understand there is a standard data type structure used to convert XML to sql calls when we use JDBC receiver adapter type communication channel. Do we use the same for posting XML data from XI to DB2 too ?
2. What is the url for the jdbc driver - to connect to DB2 on AS400 ?
Please share experiences of XI -- > posting to DB2 using JDBC.

Used standard xml -->SQL constructs

Explain me briefly about evaluation order.As per my knowledge it show data type order.but I have different data type in same diemension ex:account- acc_001 is smart list data type.account-ac_002 is percentage.So fot this i will accont dim in evaluation or

Explain me briefly about evaluation order.As per my knowledge it show data type order.but I have different data type in same dimension ex:account->acc_001 is smart list data type.account-ac_002 is percentage.So fot this i will accont dim in evaluation order.What going can any one explaining brifly ?

2786712 wrote:
thanks John for reply.If you dont mine can you explain clearly with example and screenshot.
@John: You got a task
Here you go: Hyperion Planning and More...

Dynamic ORDER BY clause - Possible different data types...

I have a lexical parameter in my ORDER BY clause:
ORDER BY &P_ORDER_BY
My problem is that I have to designate this parameter as either a date, character or number, but the user defined column being ordered by could be any one of these. When I designate the parameter as a character type, and a number data type column is chosen, it orders by that value, but it orders it as though it were a character field, referencing the initial digit and not the overall numeric value. If I choose a number parameter type, and a character value is chosen, I get an invalid number error, and so on.
Anyone have any ideas how I can do this?

Okay, now we're on the right track. The lexical parameter I'm using allows the user to choose from a list of the columns being retrieved in the SELECT statement, so it will always be one that's in there, as you said. Now, since I don't know which one it's going to be, I can't just make all but one of them 'None' for the break order, BUT, what I intended to do was to add a column to the SELECT statement that would always return the column they chose, and I could put the break order on that column, leaving all the rest 'None'. However, in the past, this has created 2 problems for me.
1.) As I mentioned in the first post, the column being returned could have a data type of character, number or date, but the parameter must be designated as only one of these. So, if the user chooses to order by a column having a value with a data type other than what the parameter is designated to be, then I get errors, it doesn't order correctly, etc...
2.) This is the strange, but anytime I've marked all but one column as 'None' for the Break Order, my child data doesn't always stay with the parent. For example, the report is on an IT request database. The 'group fields' consist of data elements that are demographic info.of a request (requester, date requested, description, etc...), and the details for each request list out the comments that have been made in the system for that request. The problem I'm seeing when I set the break orders this way is that each request displays not only its own comments, but it lists out comments for other requests as well, and there doesn't seem to be any logic to which request's comments it lists in addition to its own, it just lists as many as will fit on the page...I don't know if I explained that very well, but that's what's happening.
Does any of that make sense? Any ideas?

Error when activating Order Data Type ORDR

Hi all
We were activating all the ODM components acc to note 1178483 and got the following error when trying to activate Order Data Type ORDR:
Parameter CONFSTAT in access path TSTP of order data type ORDR unknown (/SCMB/ODM_ORDTYPE043)
Do any of you know what is triggering this error?
In order to carry on we removed the CONFSTAT entry and were then able to activate ORDR afterwards. However, we would like to know what the consequences are (if any) of this action.
Thank you in advance.
Best regards,
Dan Bruun

Hello Dan,
First of all you should not remove any SAP standard entry (without advice of any experts.) so now you won't get any support from SAP for this issue.
ODM activation require for creation of tables(which stores transactional data) in each client.
CONFSTAT is a field in /1OM/ORDROEHD<Your_client_number> table which stores data about PO/RO confirmation status.
You got this error because of ODM component OEHD was not activated properly.(Even it shows warning/error while component activation but it is not activated properly).
As you have removed CONFSTAT entry system won't behave normally for PO/RO creation/change/confirmation.
What you can do now restore your back-up before deletion of this entry try to do ODM activation again if you still get error then try to do force ODM activation(transaction code:/N/SCMB/ODM_GEN_ORC also checked Force Genration check box).
Even after force generation of ODM gives you error raised an OSS with SAP support for resolution.
Regards,
Nikhil

What's going on with re-ordering custom data types?

OK, I can't make heads or tails out of this one:
I've got a bunch of custom data types in my own typedef file (and it's part of my type palettes).
I open up my types browser, select my type file, go browse to the "custom data types" section.
I want them in a different order so I can better understand them.
(actually I select the one below it (TekTimestamp) and try dragging it up and down the list. anywhere I go I get the circle with a cross through it saying I can't drag it here.
OK, give up on that one.
Then I'll grab TekSimulateMode typedef
Try dragging it around, and I get the nice black line saying I can drag it somewhere else -- looks kinda like this:
Notice I dragged it only one spot down, and the item I dragged it across is used in exactly the usage locations, and neither has any nested typedefs (they are only containers of primitive boolean/string). Also notice that it and everything I dragged it across is owned by this type file.
Once I let up on the mouse, I get this warning message popping up:
What's up?? Why can't I change the location of the first typedef (ordering) within the file, but I can for the second??
Why do I get this dialog when I move a typedef within a file that already owns it??

Oop. My bad. I was so eager to help you out...
I know it has to do with the Usage column. Since you are changing your Station Globals.ini by dragging them around I think the warning is from there. I know that once you have instances of them then you are now changing that data type for all those locations. That's why you can't delete them if you have an instance. It won't (or shouldn't) affect anything by moving them other than you may now have to save your station globals and sequence files again. Not sure if it revs the version or not, it doesn't look like it did on mine.
As for the one that won't move? Not sure on that one. I've never seen that. Possible some instance is restricting it.
Hope this helps some,
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~

Liquid data type updates

Hi everyone,
With the next release (to go out on Monday) we're adding proper date format support in liquid for all modules. Besides all the improvements and additions made available with this release, one important note, which requires you to do some updates after the release, is that we're breaking backwards compatibility for liquid date tags by outputting the dates in ISO 8601 format ("yyyy-MM-ddTHH:mm:ss") instead of current format(“yyyy-MM-dd”).
Here is a brief overview of the changes:
All module fields which represent date or date times are now passed to Liquid as date time objects (previously they were passed as strings). This brings the following benefits:
Comparison between date time objects works correctly
It is possible to compute the difference between two date time objects using the minus filter. Example: {% assign dateDiff = Globals.Site.DateNow| minus: myDate %}
We added the means for obtaining the current date time: Globals.site.dateNow. The returned date is in the site’s time zone.
By default, when no filter is applied, all date variables will be output in the following ISO 8601 format: “yyyy-MM-ddTHH:mm:ss”. For example {{ myDate }} would output something similar to: “2014-12-12T07:19:49”. (Note: this is a backwards compatibility breaking change, as previously we outputted dates using the following format: “yyyy-MM-dd”. The breaking change only affects Liquid tags). Following the release, you should update your sites using the provided date filters to format the dates as you need.
The output of date time variables can be formatted using the following filters:
date (with no parameters)– displays a nice to read string representing just the date part from the date time variable. The date is formatted in the site’s culture. This compatible with the way older BC tags display dates. For example {{ myDate | date }}, in the English US culture will output a string similar to: “12-Dec-2014”.
datetime (new filter) – displays a nice to read string of the date time variable using the site’s culture. This compatible with the way older BC tags display date time. For example {{ myDate | datetime }}, in the English US culture will output a string similar to: “12-Dec-2014”.
date “format” (existing filter, nothing updated, mentioned here just for consistency) – displays the date in the site’s culture using a format specified by the format variable. The list with the available formats is available here: http://msdn.microsoft.com/en-us/library/8kb3ddd4%28v=vs.110%29.aspx. Note that the date filter can also be used to format objects that result as a difference between two date time objects, however, in this case the format string will respect a different set of rules as defined here: http://msdn.microsoft.com/en-us/library/ee372287%28v=vs.110%29.aspx. The following example demonstrates how to display just the number of days in the difference between two dates: {{ Globals.Site.DateNow| minus: myDate| date: "%d" }}
We added the Convert filter which can be used for converting variables to a certain type. The syntax is: variable | convert: “type”. Below are the values supported by the type parameter:
“date” – converts a variable to a date time instance. We only support the following formats for strings that are converted to date time: “yyyy-MM-ddTHH:mm:ss” and “yyyy-MM-dd”.
“number” – converts a variable to a number instance. If converting from string, only period “.” is supported as a decimal separator. This filter will probably be most useful when trying to convert GET query parameters: {% assign pageNumber = Globals.get.pageNumber | convert: “number” %}. The previous example assumes that URL that loaded the page contains a parameter named pageNumber. The convert numeric filter is an alternative to the rather hack-ish approach of converting to numbers using mathematical operators: {% assign myNumber = variable | plus: 0 }. Please note that it is not recommended to use the convert numeric filter just to assign numeric constants. For example, this approach is not recommended: {% assign myNumber = “3.14” | convert: “number” %}. Use the following approach instead: {% assign myNumber = 3.14 %} (note the lack of quotes around 3.14 in the second example).
“boolean” – converts a variable to a boolean instance. Please note, that just as it is the case with numerics, it is not recommended to use the “boolean” filter for declaring a boolean constant. For example this is not recommended: {% assign myBool = “false” | convert: “boolean” %}. Use the following syntax instead: {% assign myBool = false %}
“string” – converts a variable to its string representation.
We added implicit casting to the most relevant type in comparisons and inside filters representing mathematical operations (plus, minus, times, divide, modulo). With implicit casting, if one of the two operands is of type string and the other is of a different type (for example numeric or date time), we will attempt to convert the string operand to the type of the other. The conversion will fail if the string is not in an appropriate format for the type it is converted to (same rules as in the Convert filter are applied). In comparisons, if the implicit casting fails, the comparison is made with both operands converted to strings. Additional notes:
Implicit casting allows using date time literals directly in comparisons if the other operand is of date time type. For example, this will work correctly since "2015-01"15" will automatically be converted to date time before making the comparison: {% if myDate > "2015-01-15" %}Some message{% endif %}
Date parts obtained using the date filter can be used directly in comparisons with numerics. For example:
         {% assign daysDiff = Globals.Site.DateNow| minus: myDate| date: "%d" %}
          {% if daysDiff < 10 %}
            A message
          {% endif %}
With the implementation of implicit casting we also fixed some rather funny bugs related to comparisons and mathematical operations. For example, previously, 5 < 5.5 was evaluated as false, but 5.5 > 5 was evaluated as true. Also the result of 5| plus: 5.5 was 10, but the result of 5.5| plus: 5 was 10.5 (now 10.5 is the result of both operations, as expected).
As a potential caveat, note that implicit casting will bring the operands to the relevant type only if one of them is actually of that type. If both operands are of type string, the comparison is made as of between strings. This means that following condition is evaluated as false {% if "3" < "15" %}, because as a string "15" is smaller than "3".
Implicit casting from string to numeric only works if the string represents just a numeric. If the string contains additional characters, like a currency symbol, the conversion will fail. For example, this will not work correctly {% "$15" < 20 %}. Our goal, in the next releases, is to update all modules containing price related tags to have them in plain numeric format.
We added the following filters for easily formatting numeric values representing prices.
number - displays numbers with a fixed number of two decimals using the decimal separator appropriate to the site's culture. For example, in the English US culture, {{ 99| number }} will display 99.00
currency - displays numbers in the same way as number but also inserts the currency symbol at the beginning of the returned value. The currency symbol respects the site's culture. For example, in the English US culture, {{ 99| currency }} will display $99.00
In the next release or releases, we're going to focus on fixing the remaining data types for modules.
Cristinel

Liam, the server date isn't helpful for converting timezones. We would need a direct date filter. With a filter for UTC and one for the user we should be able to do quite a bit from there.
The most powerful things that could be implemented for date time are the following:
• moment.js and Moment Timezone built into the filters.
• the ability to add time info into date time fields
But I know that's a tall order.

How to set the date date type to work

This may be a silly question, but I can't seem to get the Date data type to work for a date account member. When I go into the Planning app and choose an account that I want to set as a date entry account, the web form doesn't seem to show that the date setting works for the account. I even set my account type to be Saved Assumption. For example, I expect to see the date formatted to 10/20/2009 when I enter that value in the web form under my account "Hire Date". I also checked the display options under the Planning preferences. So does anyone know if this function even works on 9.3 or 11.1?

Hi,
Sounds like you have not set the evaluation order for accounts. Administration > Dimensions > Evaluation Order > select plan type > move accounts to the other window, apply.
Try the form again.
Cheers
John
http://john-goodwin.blogspot.com/

Issue is De-serializing nested date type using Axiss 1.4

We are using Axis 1.4 and face issue during deserialization in handling date types. The scenario is explained below. I couldn’t find enough information on net on below and hence asking question to the apache team. Please note when we switch to Axis 2, issue is not seen. Upgrading may not be a simple option for us as of now, and hence I was evaluating possible workarounds or solution if any.
The XSD contains type “DateofBirthType” which is of type xsd:date
Child XSDs contains element “DateofBirth” of type “DateOfBirthType”
When Java client invokes the web service, IllegalArgumentException is seen while de-serializing this “DateOfBirthType” element. If we remove “DateOfBirthType” and map it directly to xsd:date type all works fine.
We have generated the stub using Axis 1.4 and trying to access the RetrieveIndividualCustInformation operation through stub, but getting the (IllegalArgumentException) while axis tries to deserialize the response for all the fields having data types as date which is indirectly mapped (nested mapping) as shown below.
e.g. IndividualInfo-----DateOfBirth(Type—DateOfbirth ---Which is of Type Date)-_you will face illegal argument exception.
So, when we changed the type to simple date (not nested),then it worked fine. So it confirms that this problem is only for type date which is clearly seen in Axis 1.4 client.
Please let me know if anyone faces similar/same issue or even know any such issue already persists and there are no possible workarounds and/or fixes for this. In that case we can put up case to migrate to Axis2.
Please reply ASAP.

Hi, Shank,
My guess is that you want:
, dense_rank () over (order by tmstp desc) AS rn RANK means you'll skip numbers when there's a tie. For example, if 3 rows all have the exact same latest tmstp, all 3 rows would be assigned number 1, RANK would assign 4 to the next row, but DENSE_RANK assigns 2.
"PARTITION BY x" means that you want a separate series of numbers (starting with 1) for every value of x. If you want just one series of numbers for the whole result set, then don't use a PARTITION BY clause at all. (PARTITION BY is never required.)
Maybe you wnat to PARTITON BY cd. I can't tell without some sample data, and an explanation of why you want the given results from that data.
You certainly don't want to PARTITION BY the same expression that you ORDER BY; that just means all rows tie for #1.
I hope this answers your question.
If not, post a little sample data (CREATE TABLE and INSERT statements, relevant columns only) for all tables involved, and also post the results you want from that data.
Explain, using specific examples, how you get those results from that data.
Simplify the problem as much as possible.
Always say which version of Oracle you're using.
See the forum FAQ {message:id=9360002}
Edited by: Frank Kulash on Aug 1, 2012 1:20 PM

Hyperion Planning:Text Data Type does not take text

Hi,
I am working on a asset addition form, and we have a member set up in a dimension that captures details, which takes the Description of the Asset.
We set this up as a text data type, but when we try entering even a single character, it does not accept it.
Can anyone clarify if this is possible?
THanks,
ANindyo

Hi John,
Thanks for replying.
Can you also tell me whether there is a logic or suite I should follow in positioning the dimension marked with a test data type member, or setting its evaluation order?
Thanks Again,
Anindyo

HP - Evaluation Order

What is the use of Evaluation Order in Planning, what does it impact and how and when is it used ?
Any reponse is greatly appreciated !

For example
You have an account members data type set as percentage
A entity members data type set as a smart list
If Account is the first in the evaluation list then the value agains the member will be shown as percentage.
If Entity was first in the evaluation list then the smart list would be shown.
Now if the account member data type was set as unspecified then this will not be evaluated and the next dimension in the list (entity) will be evaluated, if the entity member was set as a smart list then the smart list would be shown.
Hopefully you understand now.
Don't forget to mark the replies to your posts as correct or helpful as you don't seem to be doing it.
Cheers
John
http://john-goodwin.blogspot.com/

Setting Evaluation order and Reordering dimension

hi i was going through the hp admin pdf and i have a few doubts
what do you mean by setting the evaluation option in planning means and why is it reccomended to select only one dimension(setting evaluation order)
in "About Reordering Dimensions" topic it was mentioned about the ordering of aggregating sparse dimensions before non aggregatin ones , what are these two types and also it was said to arrange the sparse dimensions in the order of more sparse members to less sparse members but isnt it the opposite way around i mean as per the hour glass model the order should be from least sparse to most sparse dimension and attribute dimension in the end
what exactly is the diffrence in Setting Evaluation Order and Reordering dimensions ?

Reording the dimensions sets the order of the dimensions in essbase, reordering the dimensions can be part of optimizing the database.
Setting the evaluation order is more to do with how the dimensions are evaluated in forms, so if account is set to be first then the properties of the account members data type will be used first, for instance if the account member is set to Percentage then member will be displayed as a percentage.
Cheers
John
http://john-goodwin.blogspot.com/

Delivery Date in Sale Order

Dear All
Delivery date in sales order should automatically changed or by defalt it should be after 2 days of creating the sales order.
I have tried with lead time period and the ways given in the forum, but the schedule line/delivery date is by default coming as the day of sale order creation.
Please guide me how to do it.
Regards
SB

Hi,
Goto Tcode: VOV8
select sales document types
goto request delivery date tab
remove tick mark or uncheck propose delivery date
and maintain lead time 2 days.
thanks.

Error converting data type nvarchar to numeric 'witholding tax' (OWHT)

Hi Guys.
After I have upgraded my clients 2007 PL 30 database to 8.81 PL05, and running a repair to fix inconsistincies, I am receiveing some error when opening any sales documents.
It takes place when I open a sales document, or browse previous docs. When browsing previous docs, it onlly happens on some of them.
I also receive a different error when viewing sales orders: Error converting data type nvarchar to numeric (CRD2).
Any ideas how to fix it?
It does not limit me from processing and using the rest of the functionality. All calculations with queries in the docs are still working.
Thanks.

Hi,
Please check Note No. : 1402855 and see if the same applied to the issue mentioned by you.
Kind Regards,
Jitin
SAP Business One Forum Team

Data Type Evaluation Order

Similar Messages

Maybe you are looking for