Syndication mapping

Hello!
I need to know how to create a map in syndicator so that i can syndicate records to Port's ready folder from where PI will pick the files. How do we map the PI structure.
Pls reply.
-Shaa

Hi,
I think this thread is a good start to find the answer:
Syndication of data in mdm 7.1
Regards,
Viktor

Similar Messages

Import and Syndication maps - change in XSD

HI All,
Can any one let me know are these are correct if it is then are there any work around solutions?
We created manually Import and syndication maps.. fine..After few days we changed data type/deleted the filed/added new fields.... In all these above incidents do we need to recreate import and syndication maps????
There is no other work around for this ??
2) Even if there is no change in Repository structure but change in import or syndication XSD do we need to recreate all import and syndication maps???
Your inputs are really helpful.
Thanks
Rajeev

HI Rajeev,
So for any change in the MDM repository Import maps and syndication maps are not needed to recreate from scrach right?
For minor changes like field add there is no need.For changes involving deletion of mapped fields,changing types of already mapped fields,deleting mapped tables,one should first unmap the current map and then carry out structural changes.Later one can remap them again,this is to avoid maps from getting corrupt.
If there is any change in the XSD then there is a possibility to recreate the map from scrach??
Yes
Do Update XML schema option avaliable only in MDM 7.1?? not in 5.5?
Yes
A good description and usage is given by Aamir here Update of XML syndication map when XSD is changed
One more thing want to clear : I created a scheme and assigned the XSD.. Now when I created the port I am unable to assing the schema like I do for import map??? then what is the use of XSD schema for outbbound??
Seems you are not using in the way it is supposed to.the exact usage and defining what feature is available with which port is mentioned in pg no 356 of Console guide.
What is the usual method of import XSD and Outbound XSD?? Do Source and Target systems provide XSDs to MDM or MDM provides to Source and Target Systems?
For Standard contents SAP provides ready made xsds.
It is important to note that xsds are only to make MDM and other system understand the xml so they should be same.
To do this you can use Altova tool to create xsds based on your xml,also PI can help you do the same.
You can create xsd with PI for other idoc type too.
Hope this helps.
Thanks,
Ravi

Update of XML syndication map when XSD is changed

All,
So we recently upgraded to MDM 7.1 SP 06 and found a new feature which we were waiting for quiet some time. Thought i'll share with the community as well.
Update of XML syndication map when XSD is changed in Console
In earlier SP's of MDM, if we had to update an XML syndication map, we had to upload the new XSD in Console, go to syndicator and basically re-create the whole map. there was no way for syndicator to preserve the old mapping.
Well with this new feature, the old mapping is preserved, we only need to re-map the new fields.
The process is as below:
1. Upload the new XSD in Console.
2. Go to syndicator and open the syndication map which you want to update(File->Open).
3. Click File -> Update XML Schema. (this is the new option)
4. It will give a pop-up, select the new schema you have uploaded in console and hit OK.
5. You will get a prompt saying that syndication map is being changed, hit OK.
6. Now you will see the new XSD in syndicator, the older fields are still mapped, you only need to map the new fields.
It a nice feature which will definitely save lot of time. Thanks SAP
Regards
Aamir

If this post answered your question or helped, please mark it as such.
This works.
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml">
<mx:Script>
    <![CDATA[
      import mx.events.DataGridEvent;
      import mx.collections.ArrayCollection;
      [Bindable] private var ac:ArrayCollection = new ArrayCollection([
        {bgColor: "0xFF0000", num: 100, name: "Test1"},
        {bgColor: "0xFF0000", num: 200, name: "Test2"},
        {bgColor: "0xFF0000", num: 300, name: "Test3"},
      private function changeBK(evt:DataGridEvent):void{
        var row:uint = evt.rowIndex;
        var data:Object = ac.getItemAt(row);
        data.bgColor = "0x00FF00";
    ]]>
</mx:Script>
<mx:DataGrid id="dg" dataProvider="{ac}" itemEditEnd="changeBK(event);"
    editable="true">
    <mx:columns>
      <mx:DataGridColumn dataField="num">
        <mx:itemRenderer>
          <mx:Component>
            <mx:TextArea backgroundColor="{data.bgColor}" text="{data.num}"/>
          </mx:Component>
        </mx:itemRenderer>
      </mx:DataGridColumn>
      <mx:DataGridColumn dataField="name"/>
    </mx:columns>
</mx:DataGrid>
</mx:Application>

Syndication Mapping Issues: Tuples

Hello experts,
I am trying to map values in my Syndication map. I am trying to map the Tuple table itself to the corresponding segment in MDM, and child values (fields underneath its segment).
For some reason, the synidcator is NOT letting me map ANYTHING related to this tuple or any fields beneath it.
There are multiple other tuples that are able to be mapped (along with the child fields), but not this one for some reason. It has the same properties as the others, and is multi-valued.
Any suggestions as to why it will not allow me to map?
Nichole

Hi Niki,
First thing i am not able to see your xsd.
Second thing is just check the property of other tuple field in xsd are same or not.
I was talking about the maxoccurs = "unbounded" property that we have to set if there are multiple occurence of element as in your case.
Kindly provide the xsd.
Thanks,
Sudhanshu

Syndication Map Issues

Hi Experts,
I am trying to populate the LFM2 segment in SAP (Plant Data) from MDM. Since it is underneath the LFM1 segment (Purchase Org) I have created a tuple with all necessary fields, then in the Purchase Org tuple I have added a 'Plant' field that is a tuple (that points to my Plant Tuple). So essentially, I have nested it (in MDM) inside the Purchase Org tuple to mimic how it is on the iDoc.
My question is, I've mapped all of the fields on the Syndication Map (the fields under the nested tuple - NOT the multi-valued Plant Tuple itself - nested tuple in the Purchase Org is pointing to).
In Syndicator under the Destination Properties tab: I also put an 'X' in the static text field WERKR (suggestion by an SAP consultant)
When I syndicate to ECC 6.0, I am getting an iDoc error: "enter a valid value"
If I do not have an 'X' in the static text field - I get an iDoc error (something to the effect of) "Plant data not defined in SAP"
Cannot figure out why this is erroring out in SAP! Any suggestions?
Niki

Hello Niki
SAP MDM may syndicate data to outbound directory in text or xml formats.
For check your syndication map you can do it through Syndicator application.
If syndication map is OK
You can configure syndication server for automatic syndication
Syndicated file should be created in outbound directory.
In another case error file wil be create in "Exception" directory.
After that SAP Netweaver PI(XI) get syndicated file from outbound directory and send it to ECC
File may be modified or transform to another format into PI(XI)
If first part work fine - search error in SAP NetWeaver PI(XI)
Regards
Kanstantsin Chernichenka

Redo the syndication map if the Repository schema changes?

Hi ,
We have changed the repository structure after creating the syndication map which is based on the repository schema.Now when I load the syndication map with the updated schema ,i am not seeing the newly added fields on the destination items,so we loaded the destination properties with new schema again but the map of all the fields are no more available which leaves us to redo the map again.Is there anyway that the destination is updated with new fields without redoing the map again.
Thanks

Hi Aravind,
unfortunately there is no way to solve this issue but rebuilding the map. The reason is the way syndciation maps are stored in MDM 5.5. This is subject to change (and improve a lot!) in MDM 7.1. But in 5.5 you'll have to rebuild the syndication map completely if you change the repository schema, respectively the XSD file you use as a basis for XML distribution.
Best regards
Michael

Need to apply condition to the syndication map

Hi All,
I need to apply a condition in one of the syndication maps. The condition is as follows.
Active Home Client(Field in Main table)-            Active host client-                                          Need to syndicate from MDM
JDE----                                                                   Blank -
                                                                 Yes
JDE -
                                                                  JDE -
                                                                   Yes
JDE -
                                                                  R3   -
                                                                    Yes
R3 -
                                                                    JDE -
                                                                    Yes
R3 -
                                                                    R3 -
                                                                      No
R3 -
                                                                   Blank -
                                                                 No
So it comes down to the condition that if either of the two fields has the remote system which starts with JDE, it has to be syndicated from MDM. I tried putting up an expression but it did not work. How can this be worked out?
Thanks,
Ankush
Edited by: Ankush Trivedi on Jun 10, 2011 6:32 AM
Edited by: Ankush Trivedi on Jun 10, 2011 6:35 AM
Edited by: Ankush Trivedi on Jun 10, 2011 6:36 AM
Edited by: Ankush Trivedi on Jun 10, 2011 6:41 AM
Edited by: Ankush Trivedi on Jun 10, 2011 6:43 AM
Edited by: Ankush Trivedi on Jun 10, 2011 6:44 AM
Edited by: Ankush Trivedi on Jun 10, 2011 6:46 AM
Edited by: Ankush Trivedi on Jun 10, 2011 6:48 AM
Edited by: Ankush Trivedi on Jun 10, 2011 6:48 AM
Edited by: Ankush Trivedi on Jun 10, 2011 6:49 AM

Hi Ankush,
You should use only the first expression ignore the 2nd point, because LEFT function would not work on the Lookup values...... i just learned it too..
Lets solve this in a different way as you have multiple JDE values in your scenario,field Active Home Client is a lookup field in your main table.
In your lookup table add new fields say JDE Syndication and SAP Syndication create the fields as lookup flats with Yes/no indicator as a lookup table ( Which needs to be created with values Yes and No)
Your Active home client lookup structure looks like this
Name (Field Type Text)
JDE Syndication (Field Type Lookup[flat] with Yes/No indicator as Lookup table)
SAP Syndication (Field Type Lookup[flat] with Yes/No indicator as Lookup table)
Then your data looks like this in the table.
Name| JDE Syndication |SAP Syndication
JDE RS|Yes|No
JDEIND|Yes|No
JDEANG|Yes|No
JDEBRA|Yes|No
R31|No|Yes
R32|No|Yes
R3#|No|Yes
In Syndicator expression operator will be set to TRUE and the code will be
HAS_ANY_VALUES(Active home client .JDE Syndication,YesNoIndicator [Yes])
I did not try this at my end.... but i definetly feel it will work. if in future any of JDE System is migrated to SAP System then you need to change the name of that system and JDE Syndication to No and SAP Syndication to Yes in the lookup table in data manager instead of changing the code in the Syndication Maps.
Hope this helps you...
Regards
Sowseel

How do i update & test import maps and syndication maps?

HI,
Can anyone guide me/ let me know the steps - how do i update & test import maps & syndication maps during upgrade in development system>
Regards,
Harmony

Hello Harmony
Different service packs SAP MDM 7.1 supprot the same Syndication and Import map format.
For Import map is updating you can use Import manager
For syndication map is updating - Syndicator
If your syndication and import map have been saved into repository just archive repository from your source landscape and unarchive it in destination.
If your syndication and import map haven't been saved in repository.
Exporting your maps to xml(syndication maps from syndicator and import maps from Import Manager) before migration and importing it to new repository.
According updating(modification) repository structure:
For Import map is updating you can use Import manager
For syndication map is updating - Syndicator
Another way(very exotic) - make changes in exported xml maps.
That's all
Regards
Kanstantsin Chernichenka

Delimiter in Syndication Maps for Multi-Valued Fields

We are in the process of upgrading to MDM 7.1 from MDM 5.5. In one of our syndication maps we are syndicating a multi-valued hierarchy field with no particular limit as to how many values the field can hold. In the old MDM 5.5 Syndication map the xml output delimits this data with ";" (semi-colon) as in the below example.
<Field>Level 1Level 2Value 1; Level 1Level 2Value 2;Level 1Level2Value 3</Field>
In MDM 7.1 the values are separated by a "," (comma) like in the example below.
<Field>Level 1Level 2Value 1, Level 1Level 2Value 2, Level 1Level2Value 3</Field>
Is there anyway to change the delimiter in MDM 7.1 from a "," (comma) to a ";" (semi-colon) with out splitting the field?
Thanks!
Sincerely,
Courtney

Hi Brewer,
Is there anyway to change the delimiter in MDM 7.1 from a "," (comma) to a ";" (semi-colon) with out splitting the field?
Yes, for e.g in in your syndication map at source item lookup field display as follows
Country
|___ Code
|___ Name
just map country to destination item instead of using Code or Name, multi vaule will display with ; operator
In one of our syndication maps we are syndicating a multi-valued hierarchy field with no particular limit as to how many values the field can hold.
if you want to set length of field you require to set properties at destination item as follows :
Fixed Column Width : the specific with destination item
Max Item Length : Maximum length allowed for the item
Hope Above mention point will resolved your problem if not revert back
Thanks,
Jignesh Patel

MDM7.1 SP07 NameSpace in Syndication Map

Hi ,
We have upgraded from SP05 to SP07. Post upgrade we have observed below issues and impact in Syndication Map. Can you please advise if these is a workaround to manage the impact ?
1. In XML schema based Syndication map, Map property 'Namespace' was set as Flagged by default. Post upgrade to SP07, this property has been unflagged. SP07 doesnt allow this to be flagged in map properties.
Impact : We are facing Idoc failures for CLFMAS in ECC. We are not sure if missing Namespace is causing the idoc failures. Please advise.
2. In Syndication map, Include UNICODE Byte Order Mark is also unflagged. SP07 doesnt allow this to be flagged in map properties.
Impact : Can missing Flag for this property cause Idoc failures ?
Please advise a workaround to manage these.
Regards,
Vinay

Hi Vinay,
Generally SP upgrade is only for the SAP MDM software so ideally the properties such as flagging should not get affected.
It is best practice to take a back up of profile parameters of SAP MDM in SP5 before upgrade and use the same after the upgrade to SP7. By doing this, any changes made or caused during the upgrade can be restored to the existing with the help of profile back up taken before upgrade. Basis Team does this and try this solution with the help of that team.
Once the map is saved, the properties customized will also will exist unchanged after upgrade.
Moreover this is an application level change and software upgrade may not be the exact reason.
If you feel the software upgrade is the reason for the change of flag status, then try deleting the existing ports and xml schemas in MDM Console for the repository and add it once again with the same XML schema maps that is saved and already in use now. So that the properties saved in the existing map will be restored.
Also there are two operations WRT map properties "SAVE MAP PROPERTIES" & "RESTORE MAP PROPERTIES".
If the map is already saved, then you can try "Restore Map Properties" which will "Reverts property changes to their last-saved values."
Regards,
Aruvie
Edited by: aruvie on Dec 1, 2011 9:07 AM

Syndication Map properties Issues!!!!!!!!!

Hi Guru's,
I am having some issue while doing settings for "SYNDICATING ALL RECORDS TO ONE XML FILE".
I had followed instruction as per SYndication guide pg 140,where it says:-
To syndicate all records to a single XML file
1. On the Map Properties tab, click in the Value cell of the XML File
Output property and select Single File (All Records) from the drop-down
list.
2. Click in the Value cell of the Repeating Record Node property and
select the repeating XML element which contains the record structure
But the issue is when i do the above still field "Repeatable record Name/Node" is greyed out and doesnot allow me to select IDOC segment.
So is this the issue with XML schema file OR is there something i am doing wrong?
Please let me know if anyone has got these issues..
Regards
Vikrant M Kelkar.

Hi Preethi,
Thanks for your reply.
Issue is, we had a XSD to which we added/extended some more fields..As a result root node of XSD was changed and the whole map now needs to be redone.
Old XSD was/is still allowing us to select Segment in Reapaetable node in Map Properties, but new XSD doesnot allow .
How is this possible that for same MDM version system allows to choose Repeatable node segment selection(in Map Properties tab) for one XSd and stops doing it for other?
Also if we dont select the repeatble node how will you map qualified tables?
Regards
Vikrant M Kelkar

Syndication Map Change Track

Hi Experts,
Somebody have changed the map in MDM Syndicator and created huge problem in PI.
can we track the User Name who last changed the map?
Thanks,
Sekhar

Hi Sekhar,
I can understand your pain. But unfortunately it is not possible with Standard MDM Components. Using Database management tool Give a try and check the MDM repository database tables and see if you can get something there. I am not very positive about it.
- Shiv

Syndication mapping when changing XML schema

I have used a ARTMAS04 XML schema and done mapping in the syndicator and saved the map. Then we are doing changes i SAP R/3 and need to add some extentions in the IDOC and therefor also the XML schema. I then add my new schema with the extentions into the the syndicator, and try to open the mapping. Then the mapping is done using the old schema. This means that if I do a change in an XML schema, I need to to map everything from scratch. Does anyone have a solution to this problem?
Regards John-Kjell

Hi John,
The maps saves not only the mappings but also the destination properties for that particular scenario.
Hence as soon as you change the destination properties i.e your XML schema, and try to open your old map which is using different XML schema your changes will be lost and you will end up with using old XML schema only.
As far as i know, to handle this situation you have to do all the mappings again.
Hope this helps.
Regards,
Pooja

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 activates Versus Import Manager

Hello,
I have Key mapping activated in the console and Supress Unchaged Records activated in my syndication map.
Case : I import files (suppliers catalogs) to MDM via Import Manager manually. I am not sure about it, but since I activated Key mapping property,
I noticed that for each supplier ID in the Supplier table, a lot of remote keys were created. Previously I only had one remote key for each supplier and now I have a list of other supplier's ID. ( Existent or nonexistent supplier IDs). This becomes an issue for my import, because when I try to import a file where the supplier id does not exist in the MDM ( this scenario used to block my import and this is what a expect, as supplier is a key in my mapping), the system automatically maps that nonexistent supplier to other supplier.
Can you help me to understand if this is caused for the key mapping property ? Any Idea ?
Thank you very much
Luciana.

Hello Stanley,
The remote keys are form the same remote system.
My story is : When I am importing a file , suppose my file has an invalid supplier ID. ( this means this supplier is not in the lookup table Suppliers)
1)The import manager will give me a message such as : Map Supplier ID Values. This behavior was expected.
2)I decided to test the automap. The invalid supplier was not mapped to a different value. I am ok with that.
3)If the user ( dont ask me the reason ;-)) decides to map that invalid supplier ID to a different one, he/she is allowed to do so. I remember when the key mapping was not activated this option did not exist. The map and automap button was deactivated.
What I am trying to make sure is : a remote key will be created for invalid suppliers ONLY if I choose to map it with a different supplier ID.
Do you have any comments about it ?
Thank you very much
Luciana.

Syndication mapping

Similar Messages

Maybe you are looking for