Attributes of result container

Hi!
At design time of the sequence file I want to add additional information to the result containers to control the reporting of the step result. This additional information
must be possible to attach to every kind of step - even to NI step types. So (using TS2010) I think
attributes are the ideal solution.
Unfortunately attributes which I add to the 'Step.Result' property do not show up after executing the step in 'Locals.ResultList[x].Result' .
With subproperties of the result container this works as expected but not with the container itself.
Any ideas?
Ciao
sailor

The results in Locals.ResultList[] are created by copying the contents of Step.Result, but not Step.Result itself. If you want to attribute the result, you''ll need to put the attribute on the corresponding element of Locals.ResultList.
While in a step, this will typically be the last element in the locals.ResultList array. You might also find the Step.LastStepResult and Step.CurrentLoopResult properties useful. Note that steps that loop via loop properties create a result for each loop iteration and a final loop summary result.

Similar Messages

Error MDX result contains too many cells (more than 1 million). (WIS 10901)

Hi,
We have developed an universe on BI query and developed report on it. But while running this BO query in Web Intelligence we get the following error
A database error occured. The database error text is: Error in MDDataSetBW.GetCellData. MDX result contains too many cells (more than 1 million). (WIS 10901)
This BO query is restricted for one document number.
Now when i check in the BI cube there are not more than 300-400 records for that document number.
If i restrict the BO query for document number, delivery number, material and acknowledged date then the query runs successfully.
Can anyone please help with this issue.

follow this article to get the mdx generated by the webi report.
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/90b02218-d909-2e10-1988-a2ca74547900
then try to execute the same in mdxtest transaction in bw

Programmatically creating a Rendezvous : missing variable in Result container

Hi everybody,
For my tests purpose, I need to programmatically create a sequence. In this sequence, I need to insert Rendezvous steps.
Everything works fine when creating them, but when I execute the sequence / steps created this error always show up for rendezvous step :
Unknown variable 'TimeoutOccured' ; Error accessing item 'Result.TimeoutOccured'
According to the TS help, this variable should be created when I configure the step for the rendezvous operation. Drag and dropping the step from the TS insertion palette works fine, and the variable is created when chosing the operation 'rendezvous'. But when doing the same thing through programmation, the variable is not created.
Here are the steps executed to create the RDV step :
I create a new step using method Engine.NewStep
I set the step name using Step.Name
I set the rendezvous properties using a statement (Parameters.BranchesRendezVous.RDVStep is the variable holding the the step reference) :
Parameters.BranchesRendezVous.RDVStep.AsStep.Operation = 1, //A value that specifies the operation for the step to perform. The valid values are 0 = Create, 1 = Rendezvous, and 2 = Get Status
Parameters.BranchesRendezVous.RDVStep.AsStep.NameOrRefExpr = Parameters.BranchesRendezVous.RefName, //Contains the Rendezvous Name expression for the Create operation and the Rendezvous Name or Reference expression for all other Rendezvous operations
Parameters.BranchesRendezVous.RDVStep.AsStep.TimeoutEnabled = False, //The Timeout Enabled setting for the Rendezvous operation
Parameters.BranchesRendezVous.RDVStep.AsStep.ErrorOnTimeout = True, //The Timeout Causes Run-Time Error setting for the Rendezvous operation
Parameters.BranchesRendezVous.RDVStep.AsStep.RendezvousCountExpr = Parameters.NbBranches, //The Number of Threads Per Rendezvous expression for the Create operation
Parameters.BranchesRendezVous.RDVStep.AsStep.Lifetime = 3, //A value that specifies the Lifetime setting to use for the Create operation. The valid values are 0 = Same as Sequence, 1 = Same as Thread, 2 = Use Object Reference, and 3 = Same as Execution
4. Then I insert the step in my current sequence using method Sequence.InsertStep
Everything works fine, the rendezvous step is perfectly created and all properties are set finely. However, the variable TimeouOccured is missing in the Step.Result container (TS help says that this propoerty exists when the step is configured as a rendezvous operation (cf. Operation = 1)).
Am I doing something wrong somewhere ? Why is this variable missing ?
Solved!
Go to Solution.

Hi Doug,
TS help says that this property exists when the step is configured as a rendezvous operation (cf. Operation = 1)... So shouldn't it be created when I create / insert the step ?
I find it very weired to add a subproperty to a StepType, in the Result container...

Attribute for user contains errors. Inform system admin

Hello,
We've got an issue with shopping carts created by a user that was deleted from system. When trying to see in Monitoring Shopping Carts header or item details of a given sc. A web error occurs:
The URL http://srp.srm.gruposalinas.com.mx:8000/sap/bc/gui/sap/its/bbpsc11/! was not called due to an error.
Note
The following error text was processed in the system SRP : Attribute for user contains errors. Inform system admin.
The error occurred on the application server srm-pro_SRP_00 and in the work process 2 .
The termination type was: TH_RES_FREE
The ABAP call stack was:
Form: OUTPUT_EXPRESS_MESSAGES of program SAPLBBP_SC_UI_ITS
Form: EXTERNAL_SCREEN_DETERMINE of program SAPLBBP_SC_UI_ITS
Module: EXTERNAL_SCREEN_DETERMINE of program SAPLBBP_SC_UI_ITS
We've cheked SAP NOTE 312058-BBPPU99: Error: Attribute for ... is missing. Inform ...
But it seems that none of the information applies to us, since this issue is only present for Shopping carts that were created by this deleted user.
So we tried to re-assing one of this sc, chaning PARTNER_NO,ADDR_NR
ADDR NP data in table CRMD_PARTNER according to a new given user, but it didn't work. So we need to know how to re-assing this sc or perhaps how to find what specific attribute is missing.
Any advice is welcome.
Thanks in advance.

Hi
Which SRM version are you using ? This is an SRM error message.
The manager role should be enough to change user attribute. The transaction is BBPATTRMAINT. Employee role should have BBPUM02 or BBPAT05 to change their own attribute.
Please check whether the User ID you are using to Log into BBP_PD (and seems to be assigned in the org structure also)is consistent and has no errors in tcode USERS_GEN. You should check the user, it's not set up properly in USERS_GEN Transaction, Else repair the user.
To maintain the user attributes you must have the Administrator role.. Your user should have role SAP_BBP-STAL_ADMINISTRATOR and be integrated in the org structure. your user must be integrated in SRM organizational structure. To see which attributes are missing, you can click on the user in PPOMA_BBP to see details, and go to last tab "Check". This will list all required attributes depending on used scenarios (so you may not require all of them). You can also use transaction BBP_ATTR_CHECK to check user's attributes for a particular scenario.
Please go through the following links as well ->
bbp_mon_sc attributes
Re: FM for attribute's value assignation in PPOMA ?
Note 751022 - Monitor Shopping Cart: Item deletion causes termination
Re: User Settings are not saved
Re: Not able to generate user users_gen
Re: SRM organization plan...
Re: User creation error
Hope this will definitely help. Do let me know.
Regards
- Atul

Step status, number of steps and result container

Hi All.
I have several problems with my OI.
1. I am using my own execution viewer, its build up on UIMessages, that is executed from my custom step types as a poststeprun. The problem is that when poststeprun is executed then the status expression is not executed. I can see one solution, that is to evaluate the status myself in the routine that writes to the OI. I think this is not a good solution, because it takes time, and status expression will do exactly the same afterwards. So any other ideas ?
2. Is there any way that I can count how many steps there is in my seq, this number should be used to "count down" in a progressbar on the OI.
3. How do I "enable" more variables to be included in the result container, I have my own "test result container" that I want to be included in the normal result cluster, so I afterwards can get the results in the processmodel. I tried to build something in SeqFilePostStep, but the problem is that this is called after every step... so you need a lot of controlling to take care of while and for loops.....

Hi,
Due to the execution order within a step's execution a post step substep will be called directly after the code module itself has run.
You could evaluate the status as part of the step if you wanted, or you could move to using a post step callback in the sequence, then you could get a handle to the step, and in theory (I've not tried this) use the step's adapter to get to the adapter API and find out the path to a custom substep (rather than a post step substep) and run this, thus giving you a generic method of calling into the step after the status is resolved.
Counting the number of steps in a sequence is part of the sequence object (such as runstate.sequence) where you can call a method (use an activex/COM adapter to call an action step) and call the method GetNumSteps (this is based per step group, so run it out 3 times)
There are a few methods of including more variables into the resultlist - try looking at the AddExtraResult method of the Execution object, used in the process model sequencefile (from the sequential model, go to the test uuts entry point, and open the sequence call setup result settings (8 or so down in the main step group). That calls into the ModelSupport.seq and the Setup Result Settings sequence. In there are two pre-conditioned action steps that say if there is a property of the step called "x" then add it to the step result element in the resultlist array and call it "res x".
Hope that helps
Thanks
Sacha
// it takes almost no time to rate an answer

MDX result contains too many cells - But relese note applied!!!!!!

Hi experts!
When I create a query with my infoview, it retrive me the following error:
<ERROR COMPONENT="WIS" ERRORCODE="10901" ERRORTYPE="USER" MESSAGE="Si è verificato un errore del database. Il testo dell'errore del database è: Errore in MDDataSetBW.GetCellData. MDX result contains too many cells (more than 1 million). (WIS 10901)" PREFIX="ERR">
I try to understand if there are some problems about the sap.notes. In particular I ask to the technical people if the following note had installed into my system:
Note 931479 - MDX: More than 1,000,000 instances per axis
The technical people said me that this note had been installed because the system is to level 23.
bold
Then what problem may be due the fact that my mdx is not able to contains more than 1 million of cell ?
bold
thank'you in advance !

Hi,
whats the release of the SAP BW System - including patch level ?
whats the release of the SAP BusinessObjects system including patch level ?
Ingo

MDX result contains too many cells - NUMC 6

Hi to all.
I'm using I bex query in order to retrieve the field to my universe.
I know that when there is an element defined as NUMC (6), some errors may occurs into the MDX extraction (e.g. MDX result contains too many cells (more than 1 million)).
Can I set everythink in my BEX query or in my universe definition in order to not change the caratcteristic in my SAP BW system ?
Indeed I will have some bureaucratic and formal problem to change the sap bw type definition of the caracteristics.
Thank'you in advance.

hi Ingo,
Are you sure ? Indeed when I try to run a query where I have a NUMC6 filed and another field there is the error attached above.
Instead when I run the same query without the NUMC6 field the query ends correctly.
Moreover I see in the "SAP Note 1378064" where I see in the "Reason and Prerequisites": The internal data types are incorrect due to NUMC(6). The conversion to integer is required.
But I don't know if this conversion is allowed in the Bex Query step or in the universe filed definition.
Any advice will be accepted !

MDX result contains many cells. (more than 1 million)

Hi experts!!!
I have a webi report, but when i try to refresh te report, the report show me the following message:
The database error text is: Error in MDDataSetBW.GetCellData. MDX result contains many cells. (more than 1 million). (WIS 10901)
I was reading that this error is because the report has too many information but it can be solve.
I was reading the following sap notes:
1232751 (this note is for sap bw release 7)
931479 (this note is for sap bw 3.5 Package 17)
We have SAP BW 3.5 and package 22, for this reason this notes are not for me.
Do you know some sap note that solve this problem and works with my sap bw??
I will wait for your answer.
Ruddy Alvarado.

Hi!!
This is my mdx query:
[Z_0SD_C03/ZSD_BO_QUERY_JR]: SELECT { [Measures].[4LGOGRXW55RLOXZEFNWEPC11Z], [Measures].[4LB85FFRHOZZJ7NWNWG082RTJ], [Measures].[4LGOGWMVQB172PVA01BWUJ8T3], [Measures].[4LGOGS5KO4DB7KIULHYQZDZRR], [Measures].[4LGOGSD972Z0Q72ARC139FYHJ], [Measures].[4LGOGSKXQ1KQ8TLQX63FJHX7B], [Measures].[4LGOGSSM906FRG57305RTJVX3], [Measures].[4LGOGT0ARYS5A2ON8U843LUMV], [Measures].[4LGOGT7ZAXDUSP83EOAGDNTCN], [Measures].[4LGOGWF77CFHK3BTU79KKHA3B], [Measures].[4LHBQ76F39D7U6OU6M260ZVBR] } ON COLUMNS , NON EMPTY CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( [0CUST_SALES__0SALES_DIST].[LEVEL01].MEMBERS, [ZSIOCOPRO__ZSIOSABOR].[LEVEL01].MEMBERS ), [0CALDAY].[LEVEL01].MEMBERS ), [ZSIOCOPRO__ZSIOTAMAN].[LEVEL01].MEMBERS ), [0MATERIAL__0MATL_TYPE].[LEVEL01].MEMBERS ), [0CUST_SALES__0SALES_GRP].[LEVEL01].MEMBERS ), [0CUST_SALES__0SALES_OFF].[LEVEL01].MEMBERS ), { [0SOLD_TO__0REGION].[GT G20] } ) DIMENSION PROPERTIES [0CALDAY].[20CALDAY], [0CUST_SALES__0SALES_DIST].[10CUST_SALES__0SALES_DIST], [0CUST_SALES__0SALES_DIST].[20CUST_SALES__0SALES_DIST], [0CUST_SALES__0SALES_GRP].[10CUST_SALES__0SALES_GRP], [0CUST_SALES__0SALES_OFF].[10CUST_SALES__0SALES_OFF], [0MATERIAL__0MATL_TYPE].[50MATERIAL__0MATL_TYPE], [0SOLD_TO__0REGION].[10SOLD_TO__0REGION], [ZSIOCOPRO__ZSIOSABOR].[5ZSIOCOPRO__ZSIOSABOR], [ZSIOCOPRO__ZSIOTAMAN].[5ZSIOCOPRO__ZSIOTAMAN] ON ROWS FROM [Z_0SD_C03/ZSD_BO_QUERY_JR]
[Z_0SD_C03/ZSD_BO_QUERY_JR]: SELECT { [Measures].[4LGOGWMVQB172PVA01BWUJ8T3], [Measures].[4LHBQ76F39D7U6OU6M260ZVBR], [Measures].[4LB85FFRHOZZJ7NWNWG082RTJ] } ON COLUMNS , NON EMPTY CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( [0CUST_SALES__0SALES_OFF].[LEVEL01].MEMBERS, { [0SOLD_TO__0REGION].[GT G20] } ), [0CUST_SALES__0SALES_GRP].[LEVEL01].MEMBERS ), [0CUST_SALES__0SALES_DIST].[LEVEL01].MEMBERS ), [0MATERIAL__0MATL_TYPE].[LEVEL01].MEMBERS ), [ZSIOCOPRO__ZSIOTAMAN].[LEVEL01].MEMBERS ) DIMENSION PROPERTIES [0CUST_SALES__0SALES_DIST].[20CUST_SALES__0SALES_DIST], [0CUST_SALES__0SALES_GRP].[10CUST_SALES__0SALES_GRP], [0CUST_SALES__0SALES_OFF].[10CUST_SALES__0SALES_OFF], [0MATERIAL__0MATL_TYPE].[50MATERIAL__0MATL_TYPE], [0SOLD_TO__0REGION].[10SOLD_TO__0REGION], [ZSIOCOPRO__ZSIOTAMAN].[5ZSIOCOPRO__ZSIOTAMAN] ON ROWS FROM [Z_0SD_C03/ZSD_BO_QUERY_JR]
[Z_0SD_C03/ZSD_BO_QUERY_JR]: SELECT { [Measures].[4LGOGWMVQB172PVA01BWUJ8T3], [Measures].[4LHBQ76F39D7U6OU6M260ZVBR], [Measures].[4LB85FFRHOZZJ7NWNWG082RTJ] } ON COLUMNS , NON EMPTY CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( [0CUST_SALES__0SALES_OFF].[LEVEL01].MEMBERS, { [0SOLD_TO__0REGION].[GT G20] } ), [0CUST_SALES__0SALES_GRP].[LEVEL01].MEMBERS ), [0CUST_SALES__0SALES_DIST].[LEVEL01].MEMBERS ), [0MATERIAL__0MATL_TYPE].[LEVEL01].MEMBERS ) DIMENSION PROPERTIES [0CUST_SALES__0SALES_DIST].[20CUST_SALES__0SALES_DIST], [0CUST_SALES__0SALES_GRP].[10CUST_SALES__0SALES_GRP], [0CUST_SALES__0SALES_OFF].[10CUST_SALES__0SALES_OFF], [0MATERIAL__0MATL_TYPE].[50MATERIAL__0MATL_TYPE], [0SOLD_TO__0REGION].[10SOLD_TO__0REGION] ON ROWS FROM [Z_0SD_C03/ZSD_BO_QUERY_JR]
[Z_0SD_C03/ZSD_BO_QUERY_JR]: SELECT { [Measures].[4LGOGWMVQB172PVA01BWUJ8T3], [Measures].[4LHBQ76F39D7U6OU6M260ZVBR], [Measures].[4LB85FFRHOZZJ7NWNWG082RTJ] } ON COLUMNS , NON EMPTY CROSSJOIN( CROSSJOIN( CROSSJOIN( [0CUST_SALES__0SALES_OFF].[LEVEL01].MEMBERS, { [0SOLD_TO__0REGION].[GT G20] } ), [0CUST_SALES__0SALES_GRP].[LEVEL01].MEMBERS ), [0CUST_SALES__0SALES_DIST].[LEVEL01].MEMBERS ) DIMENSION PROPERTIES [0CUST_SALES__0SALES_DIST].[20CUST_SALES__0SALES_DIST], [0CUST_SALES__0SALES_GRP].[10CUST_SALES__0SALES_GRP], [0CUST_SALES__0SALES_OFF].[10CUST_SALES__0SALES_OFF], [0SOLD_TO__0REGION].[10SOLD_TO__0REGION] ON ROWS FROM [Z_0SD_C03/ZSD_BO_QUERY_JR]
[Z_0SD_C03/ZSD_BO_QUERY_JR]: SELECT { [Measures].[4LGOGWMVQB172PVA01BWUJ8T3], [Measures].[4LHBQ76F39D7U6OU6M260ZVBR], [Measures].[4LB85FFRHOZZJ7NWNWG082RTJ] } ON COLUMNS , NON EMPTY CROSSJOIN( CROSSJOIN( [0CUST_SALES__0SALES_OFF].[LEVEL01].MEMBERS, { [0SOLD_TO__0REGION].[GT G20] } ), [0CUST_SALES__0SALES_GRP].[LEVEL01].MEMBERS ) DIMENSION PROPERTIES [0CUST_SALES__0SALES_GRP].[10CUST_SALES__0SALES_GRP], [0CUST_SALES__0SALES_OFF].[10CUST_SALES__0SALES_OFF], [0SOLD_TO__0REGION].[10SOLD_TO__0REGION] ON ROWS FROM [Z_0SD_C03/ZSD_BO_QUERY_JR]
[Z_0SD_C03/ZSD_BO_QUERY_JR]: SELECT { [Measures].[4LGOGWMVQB172PVA01BWUJ8T3], [Measures].[4LHBQ76F39D7U6OU6M260ZVBR], [Measures].[4LB85FFRHOZZJ7NWNWG082RTJ] } ON COLUMNS , NON EMPTY CROSSJOIN( [0CUST_SALES__0SALES_OFF].[LEVEL01].MEMBERS, { [0SOLD_TO__0REGION].[GT G20] } ) DIMENSION PROPERTIES [0CUST_SALES__0SALES_OFF].[10CUST_SALES__0SALES_OFF], [0SOLD_TO__0REGION].[10SOLD_TO__0REGION] ON ROWS FROM [Z_0SD_C03/ZSD_BO_QUERY_JR]
[Z_0SD_C03/ZSD_BO_QUERY_JR]: SELECT { [Measures].[4LGOGWMVQB172PVA01BWUJ8T3], [Measures].[4LHBQ76F39D7U6OU6M260ZVBR], [Measures].[4LB85FFRHOZZJ7NWNWG082RTJ] } ON COLUMNS , NON EMPTY { [0SOLD_TO__0REGION].[GT G20] } DIMENSION PROPERTIES [0SOLD_TO__0REGION].[10SOLD_TO__0REGION] ON ROWS FROM [Z_0SD_C03/ZSD_BO_QUERY_JR]
[ZSIOCTCOR/ZSIO_BO_CXC]: SELECT { [Measures].[3Z4D1BQHVZ7VR5IJWHLKNPIL8], [Measures].[3Z4D1BY6EXTL9S202BNWXRHB0], [Measures].[3Z4D1BITD0M68IZ3QNJ8DNJVG], [Measures].[3Z4D1BB4U20GPWFNKTGW3LL5O], [Measures].[3Z4D1B3GB3ER79W7EZEJTJMFW], [Measures].[3Z4D1AGEQ7LMNE9UXH7IZDQAK], [Measures].[3Z4D1AVRS4T1ONCR95C7JHNQ4], [Measures].[480ABQOBFURXYE3L9IUXLSHNB] } ON COLUMNS , NON EMPTY CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( [ZSIOCLIE__ZSIOTCOB].[LEVEL01].MEMBERS, [ZSIOCLIE__ZSIORUTA].[LEVEL01].MEMBERS ), [ZSIODAFA].[LEVEL01].MEMBERS ), [ZSIOCLIE].[LEVEL01].MEMBERS ), [ZSIOCLIE__ZSIOCET].[LEVEL01].MEMBERS ), [ZSIOAGENC].[LEVEL01].MEMBERS ), { [ZSIOCLIE__ZSIOREGIO].[90120] } ) DIMENSION PROPERTIES [ZSIOAGENC].[5ZSIOAGENC], [ZSIOCLIE].[2ZSIOCOSIM], [ZSIOCLIE].[2ZSIOLICRE], [ZSIOCLIE].[4ZSIOCLIE], [ZSIOCLIE__ZSIOCET].[5ZSIOCLIE__ZSIOCET], [ZSIOCLIE__ZSIOREGIO].[5ZSIOCLIE__ZSIOREGIO], [ZSIOCLIE__ZSIORUTA].[5ZSIOCLIE__ZSIORUTA], [ZSIOCLIE__ZSIOTCOB].[1ZSIOCLIE__ZSIOTCOB], [ZSIODAFA].[2ZSIODAFA] ON ROWS FROM [ZSIOCTCOR/ZSIO_BO_CXC]
[Z_0SD_C03/ZSD_BO_QUERY_JR_COBERTURA]: SELECT { [Measures].[4LGOQ5A0UT58OU46P0PO9LN4N] } ON COLUMNS , NON EMPTY CROSSJOIN( CROSSJOIN( CROSSJOIN( [0CUST_SALES__0SALES_GRP].[LEVEL01].MEMBERS, [0CALDAY].[LEVEL01].MEMBERS ), [0MATERIAL__0MATL_TYPE].[LEVEL01].MEMBERS ), { [0SOLD_TO__0REGION].[GT G20] } ) DIMENSION PROPERTIES [0CALDAY].[20CALDAY], [0CUST_SALES__0SALES_GRP].[10CUST_SALES__0SALES_GRP], [0MATERIAL__0MATL_TYPE].[50MATERIAL__0MATL_TYPE], [0SOLD_TO__0REGION].[10SOLD_TO__0REGION] ON ROWS FROM [Z_0SD_C03/ZSD_BO_QUERY_JR_COBERTURA]
[Z_0SD_C03/ZSD_BO_QUERY_JR_COBERTURA]: SELECT { [Measures].[4LGOQ5A0UT58OU46P0PO9LN4N] } ON COLUMNS , NON EMPTY CROSSJOIN( CROSSJOIN( [0MATERIAL__0MATL_TYPE].[LEVEL01].MEMBERS, { [0SOLD_TO__0REGION].[GT G20] } ), [0CUST_SALES__0SALES_GRP].[LEVEL01].MEMBERS ) DIMENSION PROPERTIES [0CUST_SALES__0SALES_GRP].[10CUST_SALES__0SALES_GRP], [0MATERIAL__0MATL_TYPE].[50MATERIAL__0MATL_TYPE], [0SOLD_TO__0REGION].[10SOLD_TO__0REGION] ON ROWS FROM [Z_0SD_C03/ZSD_BO_QUERY_JR_COBERTURA]
[Z_0SD_C03/ZSD_BO_QUERY_JR_COBERTURA]: SELECT { [Measures].[4LGOQ5A0UT58OU46P0PO9LN4N] } ON COLUMNS , NON EMPTY { [0SOLD_TO__0REGION].[GT G20] } DIMENSION PROPERTIES [0SOLD_TO__0REGION].[10SOLD_TO__0REGION] ON ROWS FROM [Z_0SD_C03/ZSD_BO_QUERY_JR_COBERTURA]
[Z_0SD_C03/ZSD_BO_QUERY_JR_COBERTURA]: SELECT { [Measures].[4LGOQ5A0UT58OU46P0PO9LN4N] } ON COLUMNS , NON EMPTY CROSSJOIN( [0MATERIAL__0MATL_TYPE].[LEVEL01].MEMBERS, { [0SOLD_TO__0REGION].[GT G20] } ) DIMENSION PROPERTIES [0MATERIAL__0MATL_TYPE].[50MATERIAL__0MATL_TYPE], [0SOLD_TO__0REGION].[10SOLD_TO__0REGION] ON ROWS FROM [Z_0SD_C03/ZSD_BO_QUERY_JR_COBERTURA]
[Z_0SD_C03/ZSD_BO_QUERY_JR_COBERTURA]: SELECT { [Measures].[4LGOQ5A0UT58OU46P0PO9LN4N] } ON COLUMNS , NON EMPTY CROSSJOIN( [0CALDAY].[LEVEL01].MEMBERS, { [0SOLD_TO__0REGION].[GT G20] } ) DIMENSION PROPERTIES [0CALDAY].[20CALDAY], [0SOLD_TO__0REGION].[10SOLD_TO__0REGION] ON ROWS FROM [Z_0SD_C03/ZSD_BO_QUERY_JR_COBERTURA]
[Z_0SD_C03/ZSD_BO_QUERY_JR_COBERTURA]: SELECT { [Measures].[4LGOQ5A0UT58OU46P0PO9LN4N] } ON COLUMNS , NON EMPTY CROSSJOIN( CROSSJOIN( [0CALDAY].[LEVEL01].MEMBERS, { [0SOLD_TO__0REGION].[GT G20] } ), [0MATERIAL__0MATL_TYPE].[LEVEL01].MEMBERS ) DIMENSION PROPERTIES [0CALDAY].[20CALDAY], [0MATERIAL__0MATL_TYPE].[50MATERIAL__0MATL_TYPE], [0SOLD_TO__0REGION].[10SOLD_TO__0REGION] ON ROWS FROM [Z_0SD_C03/ZSD_BO_QUERY_JR_COBERTURA]
How to put it on mdxtest??

Reg:"No result returned or xml returned in the result contains an Error

Dear All,
After adding a query to VC storyboard and than trying to use the option define/test query for this query element, I am facing the below error on pressing the execute button.
"No result returned or xml returned in the result contains an error"
Query is working fine and giving the desired output in BW system.
How can i resolve my problem?
Regards,
Hemalatha J
Edited by: hema latha on Nov 19, 2009 3:21 PM

Hi Hemalatha,
this can have several reasons, usually there are variables in the query that aren't filled correctly in the "specify filter" box.
One thing you could do is to personalize all variables in the query and then try to fill one after another in the "specify filter" box.
If you don't get values after you have filled a specific one of them, then this one is passed incorrectly.
Best wishes
Markus

Notification activity's message must have a respond attribute name 'RESULT'

I've created a basic approval notification using the WFSTD_APPROVAL lookup type of Approve or Reject. I have it routing so that if the document is rejected it directs to the "End" Function Activity and if the document is approved it continues on with the remaining workflow. I keep getting this error when trying to save or verify the workflow. "Notification activity's message must have a respond attribute name 'RESULT' with lookup type 'WFSTD_APPROVAL'" Can anyone please direct me as to how I would set this respond attribute or how can I get rid of the warning message?

Hi,
On the message (within Workflow Builder), click on the Result tab, and populate the details of the result type, display name (prompt) etc. there. This will need to match the result type of the notification.
That should do it!
HTH,
Matt
WorkflowFAQ.com - the ONLY independent resource for Oracle Workflow development
Alpha review chapters from my book "Developing With Oracle Workflow" are available via my website http://www.workflowfaq.com
Have you read the blog at http://thoughts.workflowfaq.com ?
WorkflowFAQ support forum: http://forum.workflowfaq.com

No clickabel title shown when the search result containing .xlsx Office Excel 2010 file

in sharepoint 2013 search, everything works fine. but there is no tiltle shown when the search result contains xlsx items. and no issue at all on both docx, pptx, and even xls extension, which is lower than office 2010, any ideas?

Does the April 2015 CU fix that bug? I don't see it written in the CU's description. Regards
We found out, that it does not fix the problem and so we digged into it a little deeper. First thing is that our
documents from FileShares without set metadata are those without clickable titles in search results. So one solution might be to start setting metadata for all those documents correctly, but who would want to do that. We would expect the enginge
to find something as title anyways, i.e. at least the documents name.
For finding a valubale title out of the documents there is the "MetadataExtractorTitle" component as MappedProperty for the ManagedProperty "Title". Unfourtenatly this component seems to be a little bit bugy. It looks like that in some
cases it does not correctly return that it couldn't find anything for the document to be used as title.
Since this component is on pole position in the priority list of "Title" it leads to search results without clickable titles in such cases, where the extractor returns an empty result.
So what we did is to move MetadataExtractorTitle to the end of the priority list, so the engine at first evaluates the documents properties the classic way. We had to do a IndexReset and a FullCrawl to completely
apply this workaround. After this we did not get search results without clickable titles anymore.
I hope this also helps in your cases.
You can also get some information about this issue in this blog post: http://consultant.tamjid.com/425/fixed-search-results-not-showing-document-titles/
Regards

Multiline attribute vs. table type based attribute in workflow container

Hi,
When we are talking about definition of workflow container attribute, you have to choose a type of attribute from a dictionary and have to decide if it is multiline attribute or single line (flat). If we want to define a multiline string-based attribute, we can do it in the following ways:
— define an attribute type of string and set checkbox on multiline;
— define an attribute table type of string and do not set checkbox on multiline.
My question is:
Is there any difference between these two approaches, described above (flat type + multiline vs. table type + single line)?
Thanks.

I don't think that there is any difference. If you set a table type as container element data type, the multiline checbox is checked automatically (and you cannot change that). So eventually the table type container element is the same as a structure type container element with multiline checkbox checked.
EDIT: Or does it behave differently for you?
Regards,
Karri

Marketing attributes in result table

Hello experts,
how can I display marketing attributes belonging to an account in a result table in account search?
Thank you in advance!
Kind regards,
Martin

Hi Martin,
The Base Entity for BP Account Search Result is 'BuilHeader'.
(You can check in the context node class attributes).
I think the Marketing Attributes are available in relation 'BuilMktAttributeRel' of 'BuilHeader'. Just validate this in GENIL_BOL_BROWSER searching an existing Account.
If what I sais is true then you have two methods.
1. Either create new attributes on Search Result context node using BOL entity BuilMktAttribute or
2. Create Display only Value attributes and populate them by writing code to access BuilMktAttributeRel and populate in GET method as you did for Department Name in Target Group. As you will normally only display fields on Search Result.
I did a basic analysis, please validate.
Regards,
Masood Imrani S.

Search Result contains only Pages/Attachments

Dear All,
We are using 10g portal. When we search some keywords using simple/custom/advanced search.
Are there any setting that the result just limit to pages/attachments??
As if I use "Custom" search, I can only limit to search either "Page only" or "Item" only, which can not fulfill our requirement.
Pls HELP!!
Regards,
Calvin

In your steps (testcase) do not select the option 'this portlet' under 'Where should the search results be displayed?' for 'My Search Result' page.Let it be the default one - 'Default Search Results Page (Default when displaying a search form)'. This should work.
Regarding your second question, it is possible to have two search form and two search results associated 1-1 . Follow the same steps as mentioned above.

Copy result container - why do I get a property types do not match error?

I am creating a Teststand sequence that parses through the ResultsList and creates my own format of text reporting file. (I need to do this because our database needs the data in a very specific text format). I am trying to copy a Result from a subsequence back up into the first level of the ResultList. (see attached screen shot for the details). I use the following statement:
Locals.TestResultListLocalCopy[3] = Locals.TestResultListLocalCopy[1].TS.SequenceCall.ResultList[0]
When I execute the sequence I get the following error for the above line:
-17321; Variable or property types do not match or are not compatible.
As you can see from the screen shot that I took at run-time, both of the array elements are of type Result, so why do I get the type error?
Thanks for any help - LAW
Attachments:
TSResultScreenShot.gif ‏119 KB

Hi LAW
I have rewritten your programm. I used the Methods Clone and SetPropertyObject from PropertyObject Class.
Test it.
I hope it was you are looking for
Greetings
Juergen
=s=i=g=n=a=t=u=r=e= Click on the Star and see what happens :-) =s=i=g=n=a=t=u=r=e=
Attachments:
ResultTypeCopyError_Version2.seq ‏7 KB

Attributes of result container

Similar Messages

Maybe you are looking for