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

Similar Messages

  • 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

  • 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

  • How to keep MAPI properties when processing message data in RFC822 format in an Exchange Server 2007/2010 transport agent?

    We are developing an agent listening for the submit or endOfData event from the Exchange Server. Due to various reasons we need to convert the Exchange Mail
    internally to RFC822 format.
    So our MessageProcessor internally converts the message stream (usually TNEF) into RFC822 format. This means when written our modified content back to ‘e.MailItem’
    we write the converted content back.
    It seems that this conversion causes a loss of some MAPI properties of the message.
    When out-of-office-mails are enabled for an account the Exchange Server generates both messages the OOF message for internal recipients and the OOF message external
    recipients.
    When sending an internal message using voting buttons the message arrives without that voting information.
    void Agent_OnSubmittedMessage(SubmittedMessageEventSource source, QueuedMessageEventArgs e)
    MessageProcessor proc = new MessageProcessor();
    Stream messageContent = e.MailItem.GetMimeReadStream();
    Stream processedMail = proc.ProcessExchangeMessage(messageContent); // internally converts the message to RFC822
    Stream writeStream = e.MailItem.GetMimeWriteStream();
    processedMail.CopyToStream(writeStream);
    We also tried a dirty „hack“ using the Exchange Server internal method for converting the message from TNEF to RFC822 “ConvertAnyMimeToMime” from “Microsoft.Exchange.Data.Storage.OutboundConversionOptions”,
    but using that method causes the same issue.
    Now my idea was cloning all MAPI properties not related to the content of a message and reapply them after writing the RFC822 content back to into e.MailItem.
    Any idea how we can overcome our problems?
    Best regards,
    Harald Binkle
    Exchange Server Toolbox |
    SmartPOP2Exchange |
    SpamAssassin
    JAM Software GmbH
    Max-Planck-Str.22 * 54296 Trier * Germany
    http://www.jam-software.com

    Hello Scott,
    after posting this question I implemented a dirty workaround.
    Now I'd like to ged rid of that workaround. Are you still not allowed to discuss this?
    Best regards,
    Harald Binkle
    Exchange Server Toolbox |
    SmartPOP2Exchange |
    SpamAssassin
    JAM Software GmbH
    Am Wissenschaftspark.26 * 54296 Trier * Germany
    http://www.jam-software.com

  • 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

  • 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>

  • 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

  • Log MAPI Properties

    Hi,
    I would like to monitor all MAPI Properties that are sent from an Outlook client during the sending process of an EMail.
    Is there a way to configure Exchange's logging to meet such a requirement?
    Thanks for your help
    Tobias

    Hi Tobias,
    I recommend you use the Microsoft® Exchange Server User Monitor (EXMON) tool to monitor: 
    Microsoft Exchange Server User Monitor
    Using ExMon, administrators can view the following:
    IP addresses used by clients
    Microsoft Office Outlook® versions and mode, such as Cached Exchange Mode and classic online mode
    Outlook client-side monitoring data
    Resource use, such as:
    CPU usage
    Server-side processor latency
    Total latency for network and processing with Outlook 2003 and later versions of MAPI
    Network bytes
    Best regards,
    Niko Cheng
    TechNet Community Support

  • OC4J "classpath+properties" issue

    Hi,
    Is any fix available for the OC4J classpath+properties issue?
    It can't find *.properties files even if it is in the classpath.
    It's not convenient to jar properties files and edit the manifest.mf file in orion.jar every time you want to add new file
    Thanks

    The classpath for the Oc4j is entirely different than what is normal classpath. If you start your oc4j with -jar option the system classpath will never get effected. If you want your properties files to be recognized keep under the possible classpaths. Oc4j takes every thing from lib directory so you can keep there.
    If you have an application you can add <library path=""/> tags to your application.xml and keep the properties files in that directory.
    If you have webapplication usually web-inf\lib added in classpath.

  • What is Road map Analysis, Issue tracking,, Monitoring, Reporting?

    Hi
    Friends
    what is Road map Analysis, Issue tracking,, Monitoring, Reporting?
    can any one clear my doubts in detail full points will be given

    Dear Venkat,
    Your questions are very high level questions.
    Roadmap Analysis: This term is generally used in SAP Implementation where we compare the project status with the SAP roadmap. Generally in ASAP Roadmap, we have SAP specified standard deliverables, and there can be custom deliverables as per the client's requirements. If we need to do an analysis of custom deliverables viz standard deliverables or standard roadmap viz custom roadmap, we call it as roadmap analysis.
    Issue Tracking: Very broad level term - can be in Implementation as well as support projects. Issues are either support problems or implementation problems which are documented and recorded for solutioning and approval. These are generally steering committee terms used in a project.
    Monitoring: Again a broad level term. Any watch process can be termed as monitoring. Eg: Monitoring of Backup; Monitoring of System health check etc.
    Reporting: Again a broad level term. It is the same as defined in the english dictionary. Nothing related to any process in SAP with technical solution in mind.
    Regards,
    Anirban

  • Automapper mapping properties on a condition

    Hi there,
    I appreciate if anyone could assist me please?
    I am using AutoMapper but i am finding it difficult to map the contents depending on a condition.
    e.g
    I have a parameter called includeOptional which can be either null or 1 .
    If it is null I do not want to map the additional properties to the destination. The properties in the destination are nullable.
    if the value is 1 I would like to map the additional elements.
    Currently i am mapping everything from the source to destination as i am finding it difficult to map.
    I will share some of my code:
    IEnumerable<CustomersDAO> customers = databaseProvider.GetCustomersById(CustId);
    //additional processing..
    var result = null;
    if(includeOptional == null)
    result = Mapper.Map<List<CustomerDAO>, Customer[]>(customers);
    else
    result = Mapper.Map<List<CustomerDAO>, Customer[]>(customers);
    How would i go about mapping the properties from source to destination for each of the customers in the collection if the condition is met.
    I have the following but i cannot seem to get it work.
    configuration.CreateMap<CustomerDAO, Customer>()
    ForMember(dto => dto.StartDate, opt => opt.MapFrom(src => src.StartDate))
    .ForMember(dto => dto.Name, opt => opt.MapFrom(src => src.Name))
    .ForMember(dto => dto.Category, opt => opt.MapFrom(src => src.Category));

    Hello IndusKing,
    From your description, it seems that your issue is related the usage of the Automapper, for this, I suggest that you could post Automapper related issues to the Automapper specific forum:
    https://github.com/AutoMapper/AutoMapper/issues
    The current forum is used for Entity Framework.
    Regards.
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

Maybe you are looking for