MDM7.1 SP07 NameSpace in Syndication Map

[former_member189669]

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

[Former Member]

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

[Former Member]

Hello,

Please mention the Error that you are gettiing in ECC system, when the IDoc is falling, this will help to understand the reason for failure.

Also try to reprocess the same IDoc using we19 in the ECC system,

But do it in foreground this way you will get to see where and when the error is occuring in the during IDoc processing.

Regards,

Abhishek

[former_member189669]

Hi Abhishek,

We are not facing Idoc failures. Idoc CLFMAS will still get posted successfully.But, required segments carrying classification data wil not flow in them.

Regards,

Vinay

[Former Member]

Hello,

Kindly do a test run with manual syndication and do check the destination preview.

If any segment is missing data just added 1 in the static text.

This will generate the segment with data.

Regards,

Abhishek

[former_member189669]

Hi Abhishek ,

When static text is set to 1, we are noticing that the field value is replaced by 1 during syndication.We tried passing / also. / replaces MDM field value.

We have noticed pne more observation - If a field value blank in MDM, then the element of that field in xml is now missing.

Preupgrade xmls have blank elements for null values in MDM.

Can you please advise how to restore blank field elements in xml when field value in MDM is blank ?

Regards,

Vinay

[Former Member]

Hi Vinay,

There can be 2 ways to handle this issue:

->Create the node you want always to be there as use = "Required" in the XSD

->As a workaround you can go to syndication map's output item properties tab and set the static text property for the SEGMENT attributes to "1". This will ensure that these attributes are added to the text, even if they are empty.

This change in nature is due to change in the libraries for the output of XML data.

For your reference I am adding an excerpt from release note of MDM 7.1 SP06

"MDM Syndicator and MDM Syndicator Server MDSS:

For XML maps, a new Namespace field is added to the Create Map and Refresh Map dialog boxes of MDM Syndicator. The field's available values are taken from the namespaces present in the selected root of the map's XSD, and are used to populate namespaces in the syndication file. The Namespace map property is now read-only

For XML maps, a new Refresh Map operation in the Syndicator enables users to refresh a map with any changes made to the map's XML Schema file (.xsd)."

Hope this helps.

Thanks,

Ravi

[former_member189669]

Hi Ravi,

We do not want either to change XSD with namespace definition or by creating a node as required in XSD.

We tried workaround suggested by you - "As a workaround you can go to syndication map's output item properties tab and set the static text property for the SEGMENT attributes to "1". This will ensure that these attributes are added to the text, even if they are empty."

We tried setting static text to 1 both at FIeld element node as well as value nodes. In both the cases, static text value 1 will replace value being syndicated from MDM.

Eg. A country code 'IN' in MDM will be relaced with '1' in xml file !!

Can you please suggest the right node at which we need to enable static text value to 1 ? Also, we have many nodes not getting populated when value in MDM is null. Do we have to set the static text value at all nodes in destination properties tab or should we set at topmost node of the xml structure.

Regards,

Vinay.

[Former Member]

Hello,

As a XML parser logic has been changed in the SP06 upgrade, you will not get empty tags in the XML in destination preview.

Do we have to set the static text value at all nodes in destination properties tab or should we set at topmost node of the xml structure.

yes, you have to set the static text value at the node level in destination item tab.

Regards,

Abhishek

[Former Member]

Hi Vinay,

For your help I am detailing steps from reference guide pertaining to both the ways:

Updating a Map's XML Schema

Syndicator uses the XML schema associated with an XML map to define the destination items available on that map. If changes are made to the XML schema after a map has been created, or if you wish to use a different XML schema with the map, you can use the Update XML Schema operation to reload the XML schema into the map.

 To update or switch a map's XML schema:

1. Choose File > Update XML Schemau2026 from the main menu (map must be in an unmodified state for this option to be enabled).

2. Choose the new or updated XML schema and its related properties.

3. Syndicator refreshes the map's Destination items tree with the information contained in the selected XML schema.

NOTE ►► Existing destination items and mappings may change or disappear according to the new XML schema. Syndicator displays warnings and enters log messages in these cases.

For Static text method:

Static Text

Text entered here becomes the value of the selected item on all syndicated records.

 Applies only to required items that are unmapped.

 Mapping an item replaces static text with source values.

Thanks,

Ravi