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

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>

  • 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

  • Not able to view actual Price updated 'Value' in Change Tracker

    I was able to get my Change tracker to work and it is functioning. (SRM 5.0 MDM5.5 )... Configured Portal iViews for change tracker.
    If I change a description I can see it in the change tracker application. But if I try and track a Price change it only shows me a date-time  and user as to I when the price was changed it doesnu2019t show me the actual value changed, for my audit purposes.
    On the portal the change tracker "Field" dropdown shows -> Price Updated. this is what is tracking any change of price.
    In MDM Console-> Admin->Change Tracker I am tracking under Catalog Items: Price information, Price Updated, Special search terms, long description.
    When I look at the Data manager in the Record Detail, I see  u2018Price Updatedu2019 and it only has a Date and time stamp. In this same Record Detail,  I see the field Price Information that contains :Lower bound, Purchasing Info record ID, Purchasing Organization, Amount and Currency.  Amount-> contains the actual price value. This is what i want to see in the portal iView as Old value and New value....this is what I am unable to view? theres one small step i am not doing...
    I am trying to track the actual change in the filed u2018Amountu2019u2026 I have tried to search for it in the Portal iView fields (table, record contains, fields, record)
    cheers
    alex

    Hi Alex,
    I would not here comment on change Tracking functionality but can you suggest another workaround to achieve this requirement. If it fits in your requirement you can go ahead with it.
    In MDM, Create another field in Main table say Initial Price and for already existing field Amount replace its name with Updated Price in Qualified table Price.
    now after this you will see that your by default Updated Price has values as it was your Amount field earlier and Initial Price field as empty. Now for next time, if any record comes using Import Manager then MDM workflow should trigger at Record Import.
    This workflow contains following steps.
    Start(Checkout)>Assign>Stop(CheckIn)
    Assign step should have below expression and assignment:
    Price Information.Updated Price
    Where I am assuming Price Information is the field in main table which is look up to this qualified table Price.
    So in this way you can maintain both existing and updated values of Price and cant then show in your Catalog.
    suppose you have already existing record say 1 which has value of Amount as 20.
    So that means you have Updated Price as 20 and Initial Price as empty(Null)
    Now when same record 1 updates with new Amount say 40, it triggers this workflow on record import which will then assign value of existing updated Price 20 to Initial Field after that Updated Price will update by 40.
    Note: This Assignment works well only if your main table record has this Qualified table link as single record. If your main table record contains more than one qualified links then this Assignment would not work fine. So use only if it fits.
    Regards,
    Mandeep Saini

  • Issue in change tracking table on subscriber after reinitialization the subscriber

    Hi All,
    We have enabled change tracking on the subscriber tables and its getting dropped during a reinitialization.we are running an ETL on the subscriber tables basing on change Tracking.Our Initial ETL runs once and incremental ETL runs after that but
    after reinitialization i am getting fresh data and my initial ETL has already run.So how can i resolve this issue.Can't renireinitialization be done without disabling the Change Tracking.
    Kindly provide your feedback.
    Thanks

    The article property Action if name is in use correlates to the
    @pre_creation_cmd property of
    sp_addmergearticle.
    [ @pre_creation_cmd= ] 'pre_creation_cmd'
    Specifies what the system is to do if the table exists at the subscriber when applying the snapshot.
    pre_creation_cmd is nvarchar(10), and can be one of the following values.
    Value
    Description
    none
    If the table already exists at the Subscriber, no action is taken.
    delete
    Issues a delete based on the WHERE clause in the subset filter.
    drop (default)
    Drops the table before re-creating it. Required to support Microsoft SQL Server Compact Subscribers.
    truncate
    Truncates the destination table.
    Brandon Williams (blog |
    linkedin)

  • Issue in Change tracker application

    Hi all,
    We have enabled Change tracking in our repository when it was enabled there were only 3 Display fields in our repository and the tracking was done as is in the change tracking application under the column Record shows all the Display fields.
    Now because of business requirements we have activated another field in our repository as a Display field, now when i login to change tracking application old records under Record column still shows the 3 Display fields in the Record column of the change tracker application.
    I went and changed a record which falls in the Change tracking criteria, now i see 4 Display fields in the Record column of change tracker application as there are 4 display fields currently.
    There is an in consistency in the data in the application now for few records there are 3  and 4 fields in the record column. Is this how the system behaves?
    I think the logic is like this when ever there is a change happening in the repository, insert query is used to update the A2I_CM_History table with the existing data(at that moment how many fields were enabled as  DISPLAY )with out any relationship to the Main table Display fields. Please correct me if i am wrong, it was just an assumption.
    If any workarounds to this problem will be of a great help.
    regards
    Sowseel

    Hi Gabor,
    Thanks for your reply!
    We have checked that note and we have indexes existing for few other fields as well in the table, but still we are facing the same issue. 
    Thanks & Regards,
    Ravi

  • XSLT Mapping changes Required

    Hello Experts,
    I got one change requirment, where the name filed in the idoc contains special character (like semi colon) in between the name, I want to put double quotation for that special character at XSLT mapping.
    Eg:
    Input Name:   Ravi ; Kumar
    Out put would be: Ravi  ";" Kumar
    Please help me out with the required mapping changes in XSLT.
    Thanks in Advace.
    Edited by: ItsUrRock on Mar 23, 2011 11:55 AM

    Hi,
    use xpath function translate() and escape the semicolon and the quotes.
    <output><xsl:value-of select="translate(//Name,%3B,%25%3B%25)"/></output>
    If  that escapes do not work google for escape sequences.
    Regards,
    Udo

  • Mapping changes while upgrading from PI 7.0 to PI 7.31

    Hello Experts,
    We are upgrading from PI 7.0 EHP 2 to PI 7.31 SP 14 , Dual stack only.
    While migration, there are some doubts related with mapping, which are not getting cleared even from going through various blogs like:
    Migration Woes?
    PI/XI: PI 7.1 upgrade/migration - Message Mappings
    Below are my doubts:
    As there are mapping changes for IFS, IFSWITHOUT ELSE & Context functions, so exactly what these changes are and how would this work, how can we identify & rectify in all the mappings?
    What changes to be performed for Java mapping & XSLT mapping?
    Are there any changes for ABAP proxy?
    Any help is appreciated
    Many Thanks!!!

    Hi Lisin,
    You need to change in Java mapping accordingly and compile in jre1.6 as many methods used in older version are obsolete now.
    You need to write transform instead of execute which was used for PI 7.0
    public void transform(TransformationInput in, TransformationOutput out) 
                   throws StreamTransformationException { 
    You can easily write the code again in message mapping as discussed:
    Write Java Mapping directly in ESR!
    For XSLT mapping, the older version will be supported as the execution is done using SAP XML Toolkit which is supported in higher versions also.
    XSLT Mapping - Managing Services in the Enterprise Services Repository - SAP Library
    ABAP proxy will be as it is if you are going for classical scenario as you will be using 7.31 Dual stack.
    But if you want to go for AAE Integrated Configuration, you need to do required configuration changes in ECC for outbound Proxy:
    Proxy to file scenario using AAE - with full configuration
    I am not sure whether you need to change in Graphical standard mapping for those functions which are already there in PI 7.0.
    Regards,
    Suman

  • Change Tracking in SQL 2012 - Behavior Change

    Hi,
    We observed some change in behavior for Change Tracking feature in SQL 2012 Express. Sequence is as follows,
    CT is not enabled at DB level. (Of course at table level too)
    Created and populated table CTTEST with some rows, say 10 rows
    Enabled CT at DB level
    Enable CT for table CTTEST
    Queried change tracking data, using change table function (select CT.* from CHANGETABLE(changes CTTEST, 0) CT). No rows returned. Perfect.
    Updated few existing rows
    Queried change tracking data using CHANGETABLE function as above. Now it returns the modified records. But SYS_CHANGE_OPERATION column shows as 'U', indicating update. Same scenario was tested in SQL 2008 Express, and we got SYS_CHANGE_OPERATION column
    as 'I', indicating as Insert. 
    Is this a change in behavior? Can somebody clarify this?
    Note: SQL Version is, "Microsoft SQL Server 2012 - 11.0.2100.60 (X64) Express Edition  (Build 7601: Service Pack 1)"

    Please note that I am not talking about CDC, but CT - Change Tracking and that too in Express edition. 
    Yes, I know, when we update primary key value, we will get a delete and insert transactions in CT. But my scenario is different. I am updating the rows, which are already available prior to enabling Change Tracking in that table. In that case only, I am
    observing this. 

  • Change Tracking System in SQL Server 2012

    Hi,
    I have enabled change tracking to one of the database with retention period 1 day and auto clean is true. As per this setting changed data of one day old should get cleaned up automatically. But i am able to see 4 days
    old data also using CHANGETABLE function. Let me know is there any other setting or is this an issue in SQL server 2012 which quires some patch?
    SQL Server configuration: SQL Server 2012, Enterprise Edition, 64 bit.
    Thanks in advance for the support.
    Aruna Veluru

    please paste out:
    select * from sys.change_tracking_databases

Maybe you are looking for