Taxonomy syndication

Hello,
My requirement is that I have to syndicate material number along with the assigned class along with its attribute names and values in a flat file.
The file would have the below format
Material number Class Attribute name Attribute value.
Could anyone let me know of how to do the same?
Regards
Nilanjan
Edited by: Nilanjan Dey on Jun 22, 2010 2:20 PM

Hi Nilanjan,
I think you need to change manually in Excel file for your last two fields if you want into this format only. I think this is not Possible either using Data Manager or Syndicator to get into this Specific Format. As you now first row always syndicated out from Data Manager or syndicator conatin field names and rest all rows values.
Since here Your Material Number, Class and Attributes acts like Fields, you will get this as 1strow always and values of records as below rows.
You can check ni Record mode of Data Manager of Main table. In Record Detail tab you have format as
Field and its values
Material number and its value say 123
Class and its value Category name say XYZ
Attribute Name say Attr1, Attr2 etc and its Values say PQR
Since value(PQR) is not a field here not in left hand side, you cant get this format.
Regards,
Mandeep Saini

Similar Messages

Syndication of Taxonomy values

Hi All,
I need to syndicate the Attribute values for the attributes of a taxonomy table to ECC system. For example, for attribute "Colour" Red and Green in values are maintained in ECC. In MDM, I have added Blue and Black for this attribute.
Is it possible for me to syndicate the values "Blue and Black" to ECC from MDM?
Regards,
Ritam.

Hi Ritam,
As rightly pointed out by Pramod,When you are working with MDM integration with ECC you need to make sure that you are using lookup table and lookup values of ECC as MDM lookups.
And you assing one of these from the lookups to the main table records,You cannot give a value to a record outside the lookups as, when you try to syndicate the same from MDM ,it will fail in ECC as ECC does not know from where these values have come and this may result in an Idoc failure.
However if you already have maintained all the values in MDM as present in ECC then you can change the values and resend to ECC.
Hope It Helped
Thanks & Regards
Simona Pinto

Syndication taxonomy to R/3 Classification

Hello,
Excuse me for my english.
There is standard IDOC for syndication the Classification with clinging material from MDM to R/3.
Shall be grateful for any help.
Elena.

Hello ,
(This is point to point scenario)
Process is like that whn u create a material record in MDM and u syndicate it by using matmas and classification MAPs through MDM, it will generate XML at outbound port and R/3 wil read these XML from outbound of MDM.
Then It takes it as a IDoc for generating Material in SAP R/3.
There are standard IDoc structure availble throug which materail can be created in SAP R/3.
Thanks
Himanshu

CLFMAS syndication problem

Hello ,
I need to syndicate MDM CLFMAS data to SAP.
Can I use XSD of CLFMAS.CLFMAS02 IDOC of ECC.
How is the CLFMAS data is enterd in main material table in mdm. Is it that CLFMAS data is stored as attribute in mdm.
If I keep CLFMAS data as a field in main table can I use
XSD of CLFMAS.CLFMAS02.
as per mdm team , they cannnot give me syndicated data in CLFMAS.CLFMAS02. MDM person wants to change the xsd of standard idoc and repeat the segment E1AUSPM. Means if
todays mdm has to send 200 CLFMAS records , person is going to copy segment E1AUSPM in xsd and that XSD will be used while defining syndication map.
Pl suggest at the earliest possible.
thanks,
Sharada

Hi Sharada,
Yes CLFMAS02 can be used to syndicate classification data. Follow below steps:
1] For <OBKEY> which is a material number use <RemoteKey Value>.
2] You need to have a field in main table looking upto a taxonomy table which actually stores all classification data. (Class/Subclass hierarchy , attributes and values).
3] Once you have this field , syndicator will start showing up a field "Attrubute Name and Values" with two childrens "Attribute Name" and "Attribute Value" in source pane.
4] Map this parent node to <E1AUSPM> node of CLFMAS.
5] Map "Attribute Name" to <ATNAM> node of CLFMAS and "Attribute Value" to <ATWRT> node of CLFMAS.
6] This would map all the required fields for Classification.
Regards,
Amol.

Error while deleting a Lookup Taxonomy field

Hi Experts,
I have created a main table Products and there is a field Manufacturer which is a Lookup Taxonomy field. When I try to delete the field there comes an error stating 'The field cannot be deleted until references to it in Family Hierarchy are removed'. But in data manager there exists no data for that table. Even in the other mode I have checked whether there exists any relationships. There seems to be nothing, still I can't able to delete that field. Please help!!!
Thanks in Advance,
Thamizharasi N

Hi Thamizharasi,
I feel you have defined a Family table in your repository. This family table is referring to this taxonomy field. To resolve this, try below steps:
1. Open MDM Console and login to the repository.
2. Once connected to the repository, click on the repository name, Search for the "Families" table in the Tables Sub-window on right hand side, and check the family field.
3. If the family field is manufacturer Lookup taxonomy field, then delete the family table.
4. Delete the lookup taxonomy field from the main table.
Hope this will solve your issue. Revert with the result..
- Shiv

Query based taxonomy from scratch gives NoSuchMethodError...

I'm trying to create a query based taxonomy following the instuctions specified in the help docs: KM Platform -> Admin Guide -> Content Mgmt -> Taxonomies and Classification -> Creating a QBT -> from scratch. I created an index on a newly created (hence empty) folder in the 'documents' repository. So, essentially, the data source points to that folder. Also, I selected 'TREX Classification' on the 'Service' drop-down while creating the index. I left the crwler profile as blank. Then I went on to create a new 'Query Based Taxonomy'. I was able to create it alright, but as soon as I click on it to add folder and the such, I get this error:
java.lang.NoSuchMethodError
     at com.sapportals.wcm.repository.manager.taxonomy.TaxonomyNamespaceManager.getDocumentTaxRMRids(TaxonomyNamespaceManager.java:1876)
     at com.sapportals.wcm.repository.manager.taxonomy.TaxonomyNamespaceManager.getTaxonomyClassResources(TaxonomyNamespaceManager.java:1831)
     at com.sapportals.wcm.repository.manager.taxonomy.TaxonomyNamespaceManager.addChildDocuments(TaxonomyNamespaceManager.java:1942)
     at com.sapportals.wcm.repository.manager.taxonomy.TaxonomyNamespaceManager.getChildren(TaxonomyNamespaceManager.java:368)
     at com.sapportals.wcm.repository.CollectionImpl.internalGetChildren(CollectionImpl.java:966)
     at com.sapportals.wcm.repository.CollectionImpl.getChildren(CollectionImpl.java:179)
Any help in solving this is highly apprecaited.
We run EP6 SP2.
I did NOT create a 'crawler profile' for this set up.
thanks,
Biju.

Hi Biju,
re. your NW'04 SP stack 4 migration intention:
NW'04 is still in ramp-up (SP stack 4 is the current shipment bundle of it) so at the current point in time, only participating ramp-up customers can use it.
A migration from EP6.0 SP2 to NW'04 will be possible (but not during the ramp-up phase).
From a Knowledge Management & Collaboration perspective, we will port most of the NW'04 SP stack 4 functions to EP6.0 SP2 as well. These functions will be shipped as EP6.0 SP2 Patch 5 (planned shipment date beginning of Q4 / 2004) so for mid-term, you can also plan to stay on EP6.0 SP2 if you have no other pressing reasons for going to NW'04 (e.g. enhanced Web AS functions).
This feature porting from NW -> EP6.0 SP2 is an 'only-once' action, however, and NetWeaver will be the release for new features in the future.
Regards,
Joerg

Not able to get the taxonomy field value of meta data field type

Hi Everyone,
Not able to get the taxonomy filed value from the metadata filed type.
Any one can help me on this.
Label, TermGuid, ValidatedString are showing empty when i debug the code.
Below is the code which i used to get the taxonomy filed value

Hi,
Can you please try getting this way?
var taxonomyField = listItem.Fields.GetFieldByInternalName(fieldName) as TaxonomyField;
if (taxonomyField.AllowMultipleValues)
var fieldValuesCollection = listItem[taxonomyField.Title] as TaxonomyFieldValueCollection;
return fieldValuesCollection.Select(x => new Guid(x.TermGuid)).ToList();
else
var fieldValue = listItem[taxonomyField.Title] as TaxonomyFieldValue;
return new List<Guid>() { new Guid(fieldValue.TermGuid) };
Hope it helps!
Thanks,
Avni Bhatt
If this helped you resolve your issue, please mark it Answered

Syndication of attributes in diff. languages is not working.

Hi
I have this huge problem with syndicating attributes
We have a material rep. with a taxonomy containing of 2212 attributes mixed in numeric, text, range, logical
The main language is English.
When I set up a port to syndicate a material XML file with local attrib. lang. it can only be syndicated in English, so eventhoug all multilanguage fields are in local language, the taxonomy attributes are locked to English.
We have raised it with SAP, but did not get an answer we can use so far, so I wondered if somebody in here has found a solution or workaround
I know we can split attributes into languages, but not when they are mixed, only text attributes it seems.
What I do today to solve this situation is the following:
1.     log into the local language in syndicator
2.     File > New
3.     select the port
4.     u201Cexecute syndicationu201D
Thatu2019s all I do, but itu2019s manual.
Is there a way to automate this u201Cworkflowu201D via API, Java, Clix, or PI ?
All ports, PI and channels to legacy web portal are in place, I just need to trigger the port in the right language.
MDM 7.01.03.53
/Kurt

Hi RDNPrasad,
The attribute names are not same in both Norwegian and English layers. So in this case I need Norwegian attribute names in Norwegian.
Here I want to add that Attribute name is nothing but just like Field name, if it is carrying the same values as you said I agree the values of numeric attributes are same in all languages. I mean if you want Attribute name in Norwegian it does not matter what Source attribute Name you map whether its in English or Norwegian as here your Target Structure Attribute name really matters. So in this case you should give Attributes name at Target Side in all languages (English, Norwegian) etc and for source you can map clone Attribute fields as i said in my above post. Further as you said, Because I have maintained attribute names in Norwegian language also So similarly you need to maintain attribute names in Norwegian language (and all other languages) in Target structure along with English language and when you get this file from MDM, thus will have attributes name in all languages. So you need to give attribute name in all languages at target side(Destination Items).
e.g. I have two Attributes of Type Numeric languages Eng and Norwegian maintained in MDM.
InMDM TagetStructure
Color--Should map with>Target Attribute Name Color
Color(Clone)-Should map with -->Target Attribute name Farge , So in this way you will have required Attribute name in different languages with same values as Values would be remain same as it is Numeric.
suppose even if you get Attribute name of Type Numeric somehow Split, does it really matters..?
InMDM TargetStructure
Color--> Color
Farge-->Color , So here you getting Attribute name in English language though you have MDM Attributes name available in both languages. So please try to understand since all in all what matters the attribute Values. For Type Text , you can get Attribute values in different language using Split Multi-lingual and for Numeric you can use Clone or not need at all since values will remain same. So if you want Attribute name in all languages then it should be Target Side(Destination Item) and for Values in different languages it matters at source side(MDM side). I hope you got my point.
Kindly revert if you still have doubts else can mark thread as answered.
Regards,
Mandeep Saini

Full path mapping not working for Taxonomy values

Hi Friends,
I'm trying to update a main table field, which is of type Lookup [Taxonomy]. The taxonomy table has a 5-level hierarchy, with two columns, Code (Display Field 1) and Name (Display Field 2). There are no attributes maintained.
001, A   [Remote Key : 001] <ROOT NODE> {Level 1}
|---000, A1   [Remote Key : 000] {Level 2}
      |---001, A2   [Remote Key : 001] {Level 3}
            |---001000, A3   [Remote Key : 001000] {Level 4}
            |---000102, SYST [Remote Key : 000102] {Level 5}
            |---001001, A4   [Remote Key : 000101] {Level 4}
            |---000102, SYST {Level 5}
|---001, B   [Remote Key : 001] {Level 2}
      |---001, B1   [Remote Key : 001] {Level 3}
            |---001000, B2   [Remote Key : 001000] {Level 4}
            |---000102, SYST {Level 5}
            |---001001, B3   [Remote Key : 000101] {Level 4}
            |---000102, SYST {Level 5}
The figure, unfortunately doesn't come up right, so I've indicated the levels of the nodes.
The remote keys have been maintained at all the levels. I've also set my Configuration Options settings for Hierarchy Values Automap to Fullpath. However, when I try to do an "Automap", the values are being mapped to the wrong leaf node, taking only the leaf node remote key, rather than following the full path. The leaf node value (000102, SYST) repeats multiple times, and the remote key could be maintained only for one of them. But instead of following the hierarchy, the mapping happens to the value for which remote key was maintained, here 001->000->001->001000->000102, no matter what the hierarchy is.
Am I missing something? Any help would be appreciated.
Regards,
Anil Madhavan
Edited by: Anil Madhavan on Jan 20, 2010 8:48 AM
Edited by: Anil Madhavan on Jan 20, 2010 9:25 AM

Hello Anil,
As for Hierarchy field using leaf nodes only for matching - this is the current design and from memory allocation point of view, I think it is reasonable (keeping the full path to the Node will use huge amounts of memory).
they way workaround this is by adding the code field to the matching step, this will allow you to make sure that the currect nodes are being mapped.
Hope this information helps,
Idan

Not able to import Attribute Text Values in Taxonomy table

Hi Experts,
I have an excel file with 54K records of Attribute text values need to import in to taxonomy table. my excel file has 3 fields like ID, Name, Text Values. While mapping the fields in feild mapping grid, I have mapped ID field with Attribute Alias, Name with Attribute name, Text Value with Text Value and clone field of Text Value with [Text Value Remote Key]. Based on the field mapping I was trying to map values for ID filed with Attribute Alias field. Here I found Attribute Alias field has values in destination grid which were imported before for Attribute Name ID's in to the Alias field for attribute names.
Here I found these values are different when I tried to map these values and the Value map buttons(Automap/Map/Add) were disabled.
in the same way I tried with out maping the values for Attribute value id and selected the Attribute Alias field as value mapping field. but here in the import actions tab the records are active and disabled the import action option.
so I have executed the import process, but no attribute text values were imported in to Taxonomy table.
I am using the MDM 7.1 with build version 7.1.01.46.
Please let me know if anyone came across this situation.
Thanks,
RDNPrasad

problem solved

Syndication Search Using Remote System

Is there a way to use the Key Mapping's remote system as part of the search criteria for syndication?
I am not referring to the map property that allows you to suppress records that do not have a remote key.
For example, only send records when "remote system = DEV_100".
Thanks,
Keith

Hi,
When you create a map you have already defined the remote system for which is getting created and you have mapped key and name of that in the syndicator mapping.Suppose you craeted a map fro remote system DEV04
Now when you only want to syndicate the records for this remote system then you should define only this as a output remote systems and then if you have supressed records without key,then only records pertaining to the DEV04 system which have key will get syndicated and not others
Thanks
Vinay

Key mapping in Syndication

Hi,
I am working on Vendor master data.
The standerd syndication map for Vendor to R/3 system has the authorization groups mapped to BEGRU at target.
Well source is like
- authorization group
    [Remote key]       -
Mapped to-------> BEGRU
    Name [DF]
Where as the '[Remote key] ' field does not contain any value!!! and moreover the Name field has the value of authorization!!!
Then why did the [Remote key] FIELD mapped to BEGRU ??
I have worked on key mapping concept where a field is expecting different codes of same data from different systems are maintained in Edit key mapping tab.
This is achived by CLONING the code field and mapping it to remote Key field.
Can anyone help me in this issue!!!
Kind Regards
Eva

Hi,
Firstly i wish to clear that
1) in syndicator the table selected is 'Vendor' maintable.
2) structure of vendor is
     -- Vendor
           - Remote Key
                 Remote System
                 Value
           +Vendor number
           +Account Group
           - Authorozation group
                 Remote key             -
mapped to --> BEGRU
                  Name
           + Trading partner
Now like you said to add a code field at the source end, i have only 1 incoming value, so the NAME field it self is cloned .
it has RS specific data in the EDIT KEY mapping table.
Now, In syndicator if i map Name field to the BEGRU i will get ALL the values which are maintained in the main table RECORD.
If i wish to send the RS specific data only then how to do it??
If i select the Authorization grp Table in Syndicator then i can see the source structure as
-- Authorization grp
           - Remote Key
                 Remote System
                 Value
             Name
Here if i map Value field then i get my Output.
But I guess we need to do the mapping at Main table level to create a single XSD right!!!
Or am i confused..
Please clarify me..
Kind Regards
Eva

Key Mapping in Syndication Port

Hi,
Scenario -- Syndication through mdm outbound port (automatic mode) :
What will happen after XI successfully created data in R3 ? How MDM will get key mapping?
Do you need to execute import manager externaly to update key mappings or it will automatically take care?
Regards,
Ram

There are several options here :
1) If the Client system allows external numbering, the key can be generated on MDM, and would be transferred in the XML-File and once a new record is created in the Client system, it would takeover this key. When you look in the Console in the Remote system section, there's a field "Key-Generation", which cen be used for this.
2) Internal numbering on the CLient system. When the client system creates a key, this needs to be transferred back to MDM. This can be done e.g via calling a web-service "MDMAddRemoteKey".
Regards Klaus

Issues while Importing /Mapping hierarchy/taxonomy

Hi All,
We have multiple level hiererchies with different companies under the same banner..
When we try to map multiple level hierarchies in import manager to Taxonomy table ..We first map the Class to remote key and then clone Class(which has all hierearchy levels) and map this to Value in destination table..
When i try to map/Add values at top level i.e Merch categories it pops up with "Add as Child" while when i try to Add one more hiereachy level (which is actually a child component ) it doesnot allow me to do so..It just give "Add as Sibling" ,while "Add as Child" is Greyed out..
For eg we have Merch Cat--
00---
01----
0101
So i can add 00 as chile

Sorry all i just sent u half message..please check below
Hi All,
We have multiple level hiererchies with different companies under the same banner..
When we try to map multiple level hierarchies in import manager to Taxonomy table ..We first map the Class to remote key and then clone Class(which has all hierearchy levels) and map this to Value in destination table..
When i try to map/Add values at top level i.e Merch categories it pops up with "Add as Child" while when i try to Add one more hiereachy level (which is actually a child component ) it doesnot allow me to do so..It just give "Add as Sibling" ,while "Add as Child" is Greyed out..
For eg we have Merch Cat--
00---
01----
0101
So i can add 00 as child ,but cannot add 01 as child to 00..
How can i do this..
may be i am missing something
Please help.
Kind Regards
Vikrant M Kelkar

"The SPListItem being updated was not retrieved with all taxonomy fields." Exception while updating a taxaonomy field

Hi All,
I'm getting this exception "The SPListItem being updated was not retrieved with all taxonomy fields." when i try to programatically update a taxonomy field of a list item. Can any1 pls tell me why this exception occurs ???

Recently hit this myself, as well. Turns out it's a central admin setting that throttles the lookup return count, and Taxonomy fields are just lookups under the hood.
Go into Central Administration, Manage Web Applications, select your web application, and then in the ribbon choose the dropdown under General Settings select Resource Throttling. Find the setting for "List View Lookup Threshold" and raise
it from the default 8 (can go up to 1000, but 20 is likely fine depending how many lookup fields you're pulling back in your SPListItem).

Taxonomy syndication

Similar Messages

Maybe you are looking for