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

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

Unexpected namespace change after mapping change

Unexpected namespace change after mapping change
Posted: Apr 18, 2006 5:17 AM Reply
Hi all
We developped a mapping about one year ago on XI SP9.
The source of the message was an Idoc and the target an XML sample (and not a xsd!) of what our customer expected.
Everything was working fine at that point.
Here is an extract of the output we had:
<?xml version="1.0" encoding="UTF-8" ?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/">
<env:Header xmlns:p="http://localhost/webs/msgDetails.xsd">
<p:msgDetails xmlns:p="http://localhost/webs/msgDetails.xsd">
<p:sender>
<p:senderId>XXX</p:senderId>
<p:senderName>AUSTRALIA/NEW ZEALAND</p:senderName>
</p:sender>
We are now running SP14 and we had to change the mapping. Since we changed it the namespaces defined in the sample XML we use as a target structure are not used anymore, instead they are replaced by ns0, ns1...
Now the output looks like this:
<?xml version="1.0" encoding="UTF-8" ?>
<ns0:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns0="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://www.w3.org/2001/XMLSchema-instance" ns1:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/">
<ns0:Header>
<ns2:msgDetails xmlns:p="http://localhost/webs/msgDetails.xsd" xmlns:ns2="http://localhost/webs/msgDetails.xsd">
<ns2:sender>
<ns2:senderId>21873</ns2:senderId>
<ns2:senderName>XXX</ns2:senderName>
</ns2:sender>
Any idea what has happened here?
Thanks in advance
Gregory

Hi Gregory,
after a short view I would say that the two structures you have posted are logically equivalent.
I try to make it clear for the sender-element.
In the first example you have a tag <p:sender>. Obviously the namespace prefix 'p' is used here. In order to find out the qualified name of the element represented by that tag you have to find the namespace declaration for prefix p. As the tag itself does not contain such a declaration you have to go to the parent-tag. Indeed, here you find a declaration for p which says that p is just an alias for 'http://localhost/webs/msgDetails.xsd'. Hence the qualified name for the element is: 'sender' in namespace 'http://localhost/webs/msgDetails.xsd'.
Now let us look at the corresponding tag <ns2:sender> in the second document. In oder to identify the qualified name of the element you have to find out, which namespace is bound to the namespace prefix ns2 which has been used here. Again you cannot find this in the tag itself but in its parent. Here you find that ns2 is bound to 'http://localhost/webs/msgDetails.xsd'. (Indeed, here you see that prefix p is also bound to that namespace. This seems to be superfluous to me, as the prefix is never used.)
Consequently, the qualified name of that element is: 'sender' in namespace 'http://localhost/webs/msgDetails.xsd'.
Thus, both tags represent elements with the same qualified name. For more details look at http://www.w3.org/TR/REC-xml-names/.
Greetings Stephan

Get Message ID and namespace from ABAP Mapping

Hi XI Expert,
Please advise how to get the message ID and namespace from ABAP Mapping.
Thank You and best Regards
Fernand

Hi,
To access the message ID, use the method GET_MESSAGE_ID of the controller object:
1. Fetch a protocol instance for the protocol IF_WSPROTOCOL_MESSAGE_ID.
2. To have the system return the message ID after the sender has sent a request message or the receiver has received a request message, use the method GET_MESSAGE_ID of this instance. This returns the ID by using the parameter MESSAGE_ID of type SXMSGUID.
Also you could do the same by this way also:
IF_WSPROTOCOL_XI_HEADER
has attributes messageid and interface namespace.
using this you can read the XI message header

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>

OMB02904: Namespace conflict for map name

Hello all,
I was running an OMB script which was to create the several Mappings, and after the creation of all the mappings it was supposed to commit. This script was being run in UNIX env, but unfortunately the UNIX session got killed and script terminated, persumably before commit, because I do not see any of the mappings in OWB.
So I started the script again but got this message,
OMB02904: Namespace conflict for map name MAP_1: PRS-00303: Name <MAP_1> Already reserved under your user name. with
oracle session ID: 31
I cleaned up the oracle sessions in Design Rep, but still getting the same error message both at command line and in GUI.
Has anyone else in the forum experienced similar problem. Any suggestions or pointer on How to fix thi will be appreciated.
TIA

It seems that the mapping got created. Have you tried to refresh the OWB client to see the mapping by clicking on the "Synchronize this view with the repository" button (second icon from the left just under the "Project" menu entry)? If this is true, you will either have to delete the existing mapping and commit, or rename your mapping.
Regards:
Igor

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

OMB02904 Namespace Conflict Creating Mapping

Hi, we are running OWB 11GR2 on Windows and I am having trouble creating a mapping as allegedly it already exists. I can find no trace of this either through the GUI, through OMBPlus, or even using the JAVA APIs to find the offending mapping. It is also not visible in owbsys.all_iv_xform_maps or owbsys.all_iv_objects.
I cannot OMBDROP the mapping as it does not exist !
The full message in OMBPLUS is OMB02904 Namespace Conflict for map name WORK_SELF_EMPLOYED_INCOM_TA1M1: API0408 Within same namespace domain one object has already used the name WORK_SELF_EMPLOYED_INCOM_TA1M1
If you have any suggestions they would be gratefully received !
Phil

Our repository DB uses a Windows character set WE8MSWIN1252.
I have done a trawl through mappings and tables through all our Modules in a couple of ways (note my OMBPlus may not be the best you have ever seen). Note that these code snippets do work with 'real' mappings, but they do not find my phantom mapping.
set objectToFind WORK_SELF_EMPLOYED_INCOM.*
OMBCC '/IDP'
set moduleList [OMBLIST MODULES]
#set moduleList [list IPS2_SA1]
foreach moduleName $moduleList {
puts "Module name = $moduleName"
OMBCC '/IDP/$moduleName'
set tableList [OMBLIST TABLES '$objectToFind']
foreach tableName $tableList {
puts "=== Found table $moduleName/$tableName"
set mapList [OMBLIST MAPPINGS '$objectToFind']
foreach mapName $mapList {
puts "=== Found mapping $moduleName/$mapName"
============================================
Java API based search
set mapToFind WORK_SELF_EMPLOYED_INCOM_TA1M1
set repManager [java::call oracle.owb.connection.RepositoryManager getInstance]
set owbConnection [$repManager getConnection]
set projectManager [java::call oracle.owb.project.ProjectManager getInstance]
set project [$projectManager getWorkingProject]
# for every module
set modList [$project getOracleModuleNames]
set modCnt [$modList length]
for {set ic1 0} {$ic1 < $modCnt} {incr ic1} {
# Find your Oracle module
set modName [$modList get $ic1]
set modObj [$project findOracleModule $modName]
if {("$modName" != "RELEASES") && ("$modName" != "ARCHIVE")} {
# Proc logit defined earlier to output to a file
logit "Processing module $projName/$modName"
set mapList [$modObj getMapNames ]
set mapCnt [$mapList length]
for {set ic2 0} {$ic2 < $mapCnt} {incr ic2} {
set mapName [$mapList get $ic2]
if { "$mapName" == "$mapToFind" } {
logit "======= Found the bugger $mapName"
===============================
Nothing here either ....
SELECT *
FROM owbsys.all_iv_xform_maps
WHERE business_name LIKE 'WORK_SELF_EMPLOYED_INCOM%';
SELECT *
FROM owbsys.all_iv_objects
WHERE object_name LIKE 'WORK_SELF_EMPLOYED_INCOM%';

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

Add Namespace in message mapping

Hi gurus,
we have following requirement to solve;
on receiver side we have a segment without namespace. It is possible to add namespace at the graphical mapping?
<root>
    <id>1111</id>
    <name>max mustermann</name>
    <unit>B1</unit>
</root>
expected structure
<root xmlns="http://www.org/xml/v0300">
    <id>1111</id>
    <name>max mustermann</name>
    <unit>B1</unit>
</root>
solution for this problem will be much appreciated,
Kind Regards
PM

Hi Peter,
                You can use the following java mapping to meet your requirement
for PI 7.1 and above (if you are working with lower versions please let us know, since java mapping code will be different for lower versions)
import java.io.FileInputStream;
import java.io.FileOutputStream;
import java.io.InputStream;
import java.io.OutputStream;
import java.util.Map;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.transform.Transformer;
import javax.xml.transform.TransformerFactory;
import javax.xml.transform.dom.DOMSource;
import javax.xml.transform.stream.StreamResult;
import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.w3c.dom.Node;
import com.sap.aii.mapping.api.AbstractTransformation;
import com.sap.aii.mapping.api.StreamTransformationException;
import com.sap.aii.mapping.api.TransformationInput;
import com.sap.aii.mapping.api.TransformationOutput;
public class copyNode extends AbstractTransformation {
      * @param args
     public void execute(InputStream in, OutputStream out)
               throws StreamTransformationException {
          // TODO Auto-generated method stub
          try
               DocumentBuilderFactory factory=DocumentBuilderFactory.newInstance();
               DocumentBuilder builderel=factory.newDocumentBuilder();
               /*input document in form of XML*/
               Document docIn=builderel.parse(in);
               /*document after parsing*/
               Document docOut=builderel.newDocument();
               TransformerFactory tf=TransformerFactory.newInstance();
               Transformer transform=tf.newTransformer();
               Element rootin;
               Node rootout;
               Element r;
               rootin=docIn.getDocumentElement();
               rootout=docOut.importNode(rootin, true);
               docOut.appendChild(rootout);
               r=(Element)docOut.getElementsByTagName("root").item(0);
               r.setAttribute("xmlns", "\"http://www.org/xml/v0300\"");
               transform.transform(new DOMSource(docOut), new StreamResult(out));
          catch(Exception e)
     public void setParameter(Map arg0) {
          // TODO Auto-generated method stub
     public void transform(TransformationInput arg0, TransformationOutput arg1)
     throws StreamTransformationException {
// TODO Auto-generated method stub
          this.execute(arg0.getInputPayload().getInputStream(), arg1.getOutputPayload().getOutputStream());
     public static void main(String[] args) {
          // TODO Auto-generated method stub
          try{
               copyNode genFormat=new copyNode();
               FileInputStream in=new FileInputStream("C:\\Apps\\my folder\\sdn\\namespaceAdd.xml");
               FileOutputStream out=new FileOutputStream("C:\\Apps\\my folder\\sdn\\namespaceAdd1.xml");
               genFormat.execute(in,out);
               catch(Exception e)
               e.printStackTrace();
One more thing, you have not mentioned the scenario. If the scenario has a file adapter in sender side, and you are using File content conversion, then please put the namespace value in content conversion parameters -> Document namespace. Then you will receive the namespace value in source message.
regards
Anupam

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

MDM7.1 SP07 NameSpace in Syndication Map

Similar Messages

Maybe you are looking for