Sorting the Non qualifier values.. Is it Possible!!

Hi Experts,
I have a qualified table.
week day -> Non qualifier
Time In -> Qualifier
Time out -> Qualifier
The Week day Field is fileed with all 7 days of the week.
Monday, Tuesday,wednesday,Th..... sunday
Wehave 2 issues here..
1) In DM qualified lookup selection for a record, i can see it is autiomaticallyy sorted Based on Alphabetical order..
that is Friday, Monday, Saturday, Sunday, thursday, Tuesday, Wednesday.
we require this to be in Monday to Sunday order..
2) Also i selected Monday first and gave timein time out values, and for the same record when i ALSO select Friday and provided Time in and Time out values and once i Hit save, then i can see that Friday is seen first and Monday is seen Next to it.
Which means it is also saving the Entries for Qualified table in a Non qualifier Alphabetical sorting order.
Can we get rid of this??
User should see the Qualifid Lookup selection box in Monday to sunday order
Once user selects the any of the values in non qualifiers they should be seen in Monday to Sunday order once they save.
Note: Sort Type option at Non qualifier Field level did not help.
did anyone face similar issue??
KR
John

Hi,
I used a Integer field called Code.
which has 1-7 numbers.
Name                 :     Code
Monday                     1
Tuesday                   2
Wednesday              3
thursday                   4
Friday                       5
Saturday                   6
Sunday                     7
These 2 fields are Non qualifiers, But in Portal we have hidden the Code field.
This way the sorting worked.
Closing thread.
KR
John

Similar Messages

Fetching Non Qualifier value frm main table

Hi All,
       I have a requirement where I need to get 3 Non-Qualifier value present in the Main table .
       These 3 Non-Qualifier values are present in 1 Qualified Table.
        Kindly send me some sample code for this scenario
awaiting for your reply
Regards

Hi Sudheendra,
              Get the record result set by serching one particular column(other than field of type qualified) of the main table.
then follow the steps.
QualifiedLookupValue LVAL =(QualifiedLookupValue) temprs.getRecords()[0].getFieldValue(repoSchemacmd.getRepositorySchema().getTableSchema("mainTableName").getField("MaintableFieldName").getId());
QualifiedLinkValue[] qlinks = LVAL.getQualifiedLinks();
for (int k = 0; k < qlinks.length; k++) {
   //check whether qualifiercolumn is Display field or not.
   if(displayField){
   RecordId RID[] = new RecordId[1];
   RID[0] = qlinks[k].getLookupId();
        ResultDefinition rd =new ResultDefinition(repoSchema.getTable("qualifertableName").getId());
        rd.setSelectFields(repoSchemacmd.getRepositorySchema().getTableSchema("qualifertableName").getDisplayFieldIds());
        RetrieveRecordsByIdCommand retrievedRecords =new RetrieveRecordsByIdCommand(conAccessor);
       retrievedRecords.setSession(userSessionID);
       retrievedRecords.setIds(RID);
       retrievedRecords.setResultDefinition(rd);
          try {
               retrievedRecords.execute();
              } catch (CommandException e) {
          Record[] rec = retrievedRecords.getRecords().getRecords();
                 for (int m = 0; m < rec.length; m++) {
                     //if the field value is String.
                    String Value = qlinks[k].getQualifierValue(repoSchemacmd.getRepositorySchema().getFieldId(tableName,column)).toString();
else{
       //if columt type in qualifier table is StringValue.
       String value1 =qlinks[k].getQualifierValue(repoSchemacmd.getRepositorySchema().getFieldId("qualifertableName","qualifiercolumn")).toString();
Regards,
Sandeep.

Sorting the list of value like in BEX but out of crystal report

All,
I have created a crystal report base on a BEX query where I have a variable for which i am filtering base on a field period.fiscalyear.
for the list of values that prompt you for this variable ...
l in BEX we can do the sort by either alphabetical ascending order or descending alphabetical order such as:
here is for ascending
001.2008
001.2009
or by clicking on it we can do the following: (descending)
012.2009
012.2009
however in crystal when refreshing the report in infoview it sorts the list of value base on the month
something like this :
JAN 2008 [0FISCPER].[K42008001]
FEB 2008 [0FISCPER].[K42008002]
We would like to have in crystal the same behaviour than in BEX, so in crystal we would like to be able to get the list of values sorted in either ascending order to descending order. is there a way to do so ?
notes also that we would like to avoid to create the variable in crystal
Philippe

Hi,
in Crystal Reports you have per InfoObject - depending on the definition - the key value, the description and the member unique name. In BW these objects are defined as NUMC in most cases - which means it is a character / string.
In your example the value is 001.2008 and 001.2009. What you can do in Crystal Reports is to split up the values into year and month and then sort based on the actual numbers.
Ingo

Cannot sort the managed metadata values in refinement panel

1. I created a site column based on the managed metadata type named color.
2. I changed the managed property owstaxIdcolor to refinable:yes.
3. I added the managed property owstaxIdcolor in the refinement Web Part and request it to be sorted by name in ascending order.
4. The order stays displayed by number in the refinement panel. It doesn't want to show by alphabetical order. I already have used it with success on other types of column. Have you experience the same effect? Do you know how to obtain an alphabetical
order?

Hi,
As I noticed, you used OOB managed property owstaxIdcolor as refiner. Please locate something like ows_color in crawled property, and create a new managed property and map ows_color to it. Then use it as refiner and test the issue again.
For more information:
http://blogs.msdn.com/b/aatishblogs/archive/2014/02/02/refiners-for-managed-metadata-columns-in-sharepoint-online.aspx
Regards,
Rebecca Tu
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Values of Non-Qualifiers (lookups) not auto-converting.

We've been trying to use Import Server to automatically import records (XML) that had data for qualified lookup tables. Apparently there is an issue with namespaces in both the schema that we mapped to and the source field.
After removing the namespaces, we now have an issue with the non-qualifier that uses a lookup table not automapping it's values and thus retaining the compound field at the Customer main level.
First, the Partner Function is mapped to the Partner Function flat lookup table. At this level, the value auto-converts and the green dot is visible to the left.
Second, at the Customer Partner qualified lookup, the Partner Function is again mapped to the Partner Function lookup. This time, however, the values do not automatically convert and the "AUTOMAP" button must be manually pushed for them to map. The other non-qualifiers (CustomerID, PartnerNum, PartnerSAP_ID) are also mapped and their values auto-convert (green dot).
Finally, at the Customer main level, all of the non-qualified field from the Customer Partner table are mapped and all auto-convert except for the Partner Function field. This requires us to manually push "Automap". Then, and only then, does it allow us to right click on one of the fields and create the compound field to map to the Customer Partner field. Again, the value mapping is not automatic but must be done manually.
This map is then saved and ImpMgr closed. When the IM is reopened with the same map, the compound field is not recreated due to the fact that the Partner Function values did not convert. Once these are redone manually, then and only then can the compound field be recreated and value mapped.
When this same map is used in the Import Server, the error is that the qualified fields cannot be mapped. This brings us back to the lookup fields not value mapping. Likewise, if this same file is opened in Import Manager mannually, and the map applied, it STILL does not convert the values and the Compound Field for the Qualified L/Up table is dropped.
We are using MDM 5.5 SP4 Patch 3.

Hello Christiane,
Yes, this is a very important point and I should have noted it in my original post. Yes, my Default Batch Handling settings are:
Yes - Automap unmapped values
Add - Unmapped Value Handling
Plus:
Replace - Default multi-valued update
Append - Deault qualified update
None - Default matching qualifiers
Also, in my mdis.ini file, my settings are:
Automap Unmapped Value = True
Unmapped Value Handling = Add
Always Use Unmapped Value Handling = True
It used to work when we were in SP4, Patch 2, but have since upgraded to Patch 3, Hotfix 2(?) and can't get it to work.
Thanks for helping!
Don

Non zero values in the extraction of the planning area

In our DP implementation we have been trying to extract 2 key figures from the planning area, one of the key figures might have zero values, when we set the indicator for the non zero values then it only eliminates the records for which both the key figure are zero but that is not what I want. I am trying to have a setting in the data source where we can reject the records even if one of the key figure has zero values.
Are there any settings for that while we are generating the data source.
Thanks in advance

Hi Colin,
This can be easily solved using a slightly different ABAP routine. You can assign the fields that you need to check into other field symbols and then check the value of those field symbols.
Here's one possible solution. I based in from the ABAP code you posted.
field-symbols: <LS_EXTR_BLOCK> TYPE any,
                     <ls_fcst> type any,
                     <ls_hist> type any.
data: w_pos type sy-tabix.
loop at ct_data assigning <LS_EXTR_BLOCK>.
w_pos = sy-tabix.
assign component '/BI0/9AVCORFCST'
   of STRUCTURE <LS_EXTR_BLOCK> to <ls_fcst>.
assign component '/BI0/9AVCORHIST'
   of STRUCTURE <LS_EXTR_BLOCK> to <ls_hist>.
if <ls_fcst> = 0 and <ls_hist> = 0.
delete ct_data index w_pos.
endif.
endloop.
Aside from the solution above, you can also define the structure of CT_DATA (that's basically the structure of the extract structure of your datasource). You can then assign the contents of CT_DATA to a field-symbol and the delete data using that field symbol.
Here's an example:
TYPES:
TY_DATA_TABLE type table of *PUT THE NAME OF YOUR EXTRACT STRUCTURE HERE*.
field-symbols:
<FS_DATA_TABLE> type TY_DATA_TABLE.
DELETE <FS_DATA_TABLE> WHERE /bi0/9avcorfcst = 0
and /bi0/9avcorhist = 0.
You can check the name of the extract structure by viewing table /SAPAPO/TSAREAEX field EXPORT_STRU. You can also see the name of the extract structure in debug mode by looking at the value of the parameter IV_DDIC_REFERENCE.
Hope this helps

What is the need to combine non qualifiers during IMPORT

Hi Experts,
I want to know the need to combine the non qualifiers during import in the match records field.
what is the significance of it?
Thanks in advance.
Sandhya.

Hi Alex,
Thanks for the reply.
i need a small clarification about the same. as per my understanding the NON QUALIFIERS are text fields so how do they effect the value in the qualified fields? or should the NON Qualifiers be lookup fileds (in your example company code and Plant)
Case 1 - if the Non qualifiers are of type lookup:
Then based on the combination of the qualifiers how can we define the valid values in the qualifier fields
Eg: if company code is 2000 (where company code is Non qualifiers of type lookup) then the available dropdown value for plant field should only be P001 and P002 (Whare plant field is qualifier)
Case 2: If the Non qualifiers are of type lookup :
Then how does the value in the Non qualifier decide the available values in the Qualifiers.
Please help me understand the above two scenerios
Regards,
SS

The InfoCube contains non-cumulative values

Hi,
While creating multicube for inventory on two cubes its askin the below "The InfoCube contains non-cumulative values. A validity table is created for these non-cumulative values, in which the time interval is stored, for which the non-cumulative values are valid.
The validity table automatically contains the "most detailed" of the selected time characteristics (if such a one does not exist, it must be defined by the user, meaning transfered into the InfoCube)", what is that and how to solve this,
Please through some light on this its urgent.
Chandan

Hi,
Your multi cube is probably based on the infociune 0IC_C03 containing non cumulative key figures taht's why you get this message.
You generaly don't have to maintain validity area unless you are in a special configuration (for exemple loading data from two source systems).
UThe following link should give more information about validity area with non cumulative :
[http://help.sap.com/saphelp_nw04/helpdata/en/02/9a6a1c244411d5b2e30050da4c74dc/frameset.htm|http://help.sap.com/saphelp_nw04/helpdata/en/02/9a6a1c244411d5b2e30050da4c74dc/frameset.htm]
Hope this helps.
Cyril

Get Qualifier value from Qualified table

Hi,
I am trying to get all the qualifier value for a qualified table. What is the best way to do it. Can I use QualifierSearchDimension to search for all the qualifier value.
Re: Lookup [Qualified Flat] type field how to use as a query condition? link gives us a way to do this , but it talk about getting the non - qualifiers only , so How can we get the qualifier values.
The link Search Qualifier Fields : MDM Java APIs gives us a way to this , but it is using old Java API , does anyone know how to do it using MDM API SP06.
Thanks and Regards,
Subhasis

Hi Subhasis,
The Search API's will only search for a particular value in the qualified tables. In order to read all the qualifier and non qualifier for a record, please follow the below mentioned steps.
Assuming 'rec' is the variable that holds the reference for the current record.
MdmValue lookUpVal = rec.getFieldValuel(<Field Id of the field>);
com.sap.mdm.valuetypes.QualifiedLookupValue val = (com.sap.mdm.valuetypes.QualifiedLookupValue) lookUpVal;
// Get the total number of qualified records present for that field
int size = val.getValuesCount();
// Iterate through each qualified record to fetch the details
for(int i=0;i<size;i++){
    MdmValue nqVal = val.getValue(i);
   if(nqVal != null){
         MdmValue incVal = val.getQualifierFieldValue(i,<Field Id of the qualifier field value>);
Regards,
Ponraj M
Edited by: Ponraj M on Jul 10, 2009 10:12 AM

Qualifier values are not part of a qualified lookup record

Hi
     I am getting the exception "Qualifier values are not part of a qualified lookup record" when I serach for a record in the Qualified table. The Table has both Qualfier and non-Qualifier fields, but all are of type display fields.
My question is If the filed is of type Qualifier then is it mandatory that it should be non-display Field?
if not can any one suggest me to get the record.
If we make Qualifier fields as NON-Dispaly fields in repository then it is working fine.
Here with I am providing the code
               Search serarch = new Search(repoSchemaCmd.getRepositorySchema().getTable("QT_NOTES").getId());
               serarch.addSearchItem(new FieldSearchDimension(repoSchemaCmd.getRepositorySchema().getFieldId("QT_NOTES","USER_PMF_ID")),new TextSearchConstraint("test", TextSearchConstraint.EQUALS));
               ResultDefinition rd =new ResultDefinition(repoSchemaCmd.getRepositorySchema().getTable("QT_NOTES").getId());
               //Returns the array of IDs for all display fields associated with the table
               rd.setSelectFields(repoSchemaCmd.getRepositorySchema().getTableSchema("QT_NOTES").getDisplayFieldIds());
               RetrieveLimitedRecordsCommand retrievedRecords =new RetrieveLimitedRecordsCommand(conn);
               retrievedRecords.setSession(userSessionID);
               retrievedRecords.setSearch(serarch);
               //retrievedRecords.setIds(RID);
               retrievedRecords.setResultDefinition(rd);
               try {
                    retrievedRecords.execute();
               } catch (CommandException e) {
                    throw new CommandException(e);
Regards,
Sandeep.

Hi Sandeep
I have a similar problem, would like to know what is the resolution to this issue.
Regards
Dilip

Can MDM Web Services return qualifier values?

We are running MDM 5.5 SP06 Patch04 (we will be doing a technical upgrade to MDM 7 later this year).
I am investigating the MDM web services and came upon a potential problem. In the test harness, I searched for a record, specifying ALL for the result definition and everything seemed to come back except qualifiers; lookup values came back, taxonomy values came back, qualified lookup display values came back, qualified link ids came back, but no qualifier values.
I searched again on the qualified link record ids in the qualified lookup table and I got the non-qualifiers, which is the expected behavior. The qualifiers have to come back with the main table record, though.
Are qualifiers not fully supported in the MDM 5.5 web services, or am I not searching properly?
Thanks for any help you can provide.
Doug

Hi Doug
For me all are working good.
Can you look at pages 24-26 from "Portal content development guide"
https://websmp201.sap-ag.de/~sapidb/011000358700001119612007E
Regards
Kanstantsin

FA Account Generator: Non Qualified Segment

Hi,
Currently we have a requirement of customizing the account generator to accommodate the following requirement.
COA structure: Company-Branch-CostCenter-NaturalAccount-Product-Future1
The account generator should generate the Account based on the Branch and the CostCenter that owns the asset.
I understand that we can get Cost Center segment value in FA account generator.(by using the Cost center qualifier)
Currently i need to derive the non qualifier segment BRANCH also.
Can someone throw some light on this, like how can this be acheived?
Regards,
Senthil
Edited by: Senthil Velavan J R on Oct 8, 2009 2:59 PM

Accounting Segments that are not qualifiers will have to be derived programmatically.

Non-cumulative values

HI All,
when I run a query of a non-cumulative infocube,there's always a "initial record" which actually doesn't exist in the fact table. Documents say "This entry does not remain physically in the table, but it is available for rebuilding the non-cumulative values". So where exactly is the initial value stored ?
Thanks
han.

Hi,
What is teh DataSource and InfoCube?
If you are talking about 0IC_C03, please see the steps.
Treatment of historical full loads with Inventory cube
Setting up material movement/inventory with limit locking time
See about Non-Cumulatives
http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/da1640dc88e769e10000000a155106/content.htm
Thanks
Reddy

Counting non null values

I have a column of data and there are values and nulls how would I count just the values on a summary?
Everything I have tried give me the total number of rows not the non null values.....
tia
Rose

no you did not say something wrong -- but when we included a case statement for another field in the sql ---
when we referenced the new field and tried to sum it in bi publisher gave us a 'Na' don't know why......
Rose

Need help Sorting a Hashtable using values??

I have a hastable whose keys are unique but values are not. The problem is that i have to sort the hashtable by values.

You can't really sort a Hashtable by values, at least not directly. What you probably want is a way to be able to iterate through all the values contained in the Hashtable in a way that is consistent with some order defined on those values. An easy way to do this goes as follows:
Map m; // let that be your Hashtable
List vals = new ArrayList(m.values());
Collections.sort(vals); // uses the values natural order OR
Collections.sort(vals, my_comparator); // uses the order defined by my_comparator
// this will iterate in the order defined on the values
Iterator it = vals.iterator();
while(it.hasNext()) {
Object val = it.next();
}

Sorting the Non qualifier values.. Is it Possible!!

Similar Messages

Maybe you are looking for