MDM Syndication

Hi All,
We are trying standard vendor scenario. we are using MDM 5.5 . We import the data using the remote system MDC R/3, which is the default one in the standard.For syndicating we use the standard map CREMDM04_R3 which came with the standard. But while syndicating using these standards, some fields are not getting filled. eg: Account group, Land1.
Please help in solving this problem
Regards,
Nikhil

Hi Nikhil,
define/add the missing mapped fields in Syndicator. You can do this easily on your own. And save the map. If you want to keep the existing map, you can choose the "Save As" option and save your map with a new name.
BR Michael

Similar Messages

MDM Syndication - IDOC mapping ?

Hi Gurus,
I was going thru the following blog.
MDM Syndication
/people/harrison.holland5/blog/2006/11/27/mdm-syndication
What is the purpose of remote system(ECC) in MDM ? Is it required to get IDOC structure from ECC into MDM repository ?
If so, what are the pre requisites/configurations required for connection to ECC from MDM. Is it enough to mention technical/Logical name of ECC server (as in SLD) for creating remote system in MDM ?
Appreciate your help

Ports(Outbound) is for automating the Syndication.
You create Ports in MDM Console.
You do NOT have to import the IDoc structure into MDM.
MDM is not like Integration Repository of XI. You do not have to import the Idoc structure at all.
SAP provides business content (out of the box) for the XI - MDM mapping.
File Adapter of XI(Inbound to XI) picks up the created xml file.
In the outbound side of XI, Idoc Adapters are used.
In the port definition of MDM, you specify the map to be used to syndicate the data.
SAP delivers the map and XSD for predefined Repository like Material, Customer, Vendor, Business Partner etc..

MDM Syndication automatic error notification

I am currently helping to design workflows for my client and one of their requirements is that they have some sort of notification workflow when a syndication fails. So far, it is my understanding that there is no method to track syndication errors other than the syndication just won't go through. Is this accurate? Is there a way to perform this workflow. I am working with MDM 7.1 and we are using a PI adapter, however I am not sure of the version at this time.
Thanks

Hi Steven,
I am currently helping to design workflows for my client and one of their requirements is that they have some sort of notification workflow when a syndication fails. So far, it is my understanding that there is no method to track syndication errors other than the syndication just won't go through. Is this accurate? Is there a way to perform this workflow. I am working with MDM 7.1 and we are using a PI adapter, however I am not sure of the version at this time
Yes, you are correct. There is no robust mechanism to find out any Syndication errors. Foe ex, if its an automatic syndication, and there is some problems with the MDSS, the syndication wont happen, however there will be no error. Hence its difficult for setting any Email Notification for the same.
The main thing is if we are using Automatic Syndication, the export file is sent to the Ready Outbound folder. But it is not passed on to the Archives automatically as it does in Import. And again in Manual syndication anyways it not possible to trigger any notification on failure.Hence, as far as I know there is not much help on this.
Thanks and Regards
Nitin Jain

Mdm syndication demmdm06 issue..

Hi,
we are using mdm 7.1.03.53.
In customer repository, we added url communication as qualified table as this is not part of standard mdm content.
But,In standard debmdm06.xsd we have E1BPADURI as repeatable ( max ocurrs 9999999). (under ADRMAS)
In syndication map, we see repatable unchecked for E1BPADURI and we are not able to change the flag.
Can anyone throw a light on this?

Hi,
In DEBMDM06.XSD, uNDER E1ADRMAS We have the following segments defined like this. All segments minouccurs "0" and maxoccurs "999999999". But, in syndicator map E1BPADTEL,E1BPADFAX,E1BPADSMTP only can see as repeatable.
why other segments are not repeatable?
Can anybody check this xsd in 7.1 and tell me?
<xsd:element name="E1BPAD1VL" type="DEBMDM06.E1BPAD1VL" minOccurs="0" maxOccurs="999999999"/>
<xsd:element name="E1BPADTEL" type="DEBMDM06.E1BPADTEL" minOccurs="0" maxOccurs="999999999"/>
<xsd:element name="E1BPADFAX" type="DEBMDM06.E1BPADFAX" minOccurs="0" maxOccurs="999999999"/>
<xsd:element name="E1BPADTTX" type="DEBMDM06.E1BPADTTX" minOccurs="0" maxOccurs="999999999"/>
<xsd:element name="E1BPADTLX" type="DEBMDM06.E1BPADTLX" minOccurs="0" maxOccurs="999999999"/>
<xsd:element name="E1BPADSMTP" type="DEBMDM06.E1BPADSMTP" minOccurs="0" maxOccurs="999999999"/>
<xsd:element name="E1BPADRML" type="DEBMDM06.E1BPADRML" minOccurs="0" maxOccurs="999999999"/>
<xsd:element name="E1BPADX400" type="DEBMDM06.E1BPADX400" minOccurs="0" maxOccurs="999999999"/>
<xsd:element name="E1BPADRFC" type="DEBMDM06.E1BPADRFC" minOccurs="0" maxOccurs="999999999"/>
<xsd:element name="E1BPADPRT" type="DEBMDM06.E1BPADPRT" minOccurs="0" maxOccurs="999999999"/>
<xsd:element name="E1BPADSSF" type="DEBMDM06.E1BPADSSF" minOccurs="0" maxOccurs="999999999"/>
<xsd:element name="E1BPADURI" type="DEBMDM06.E1BPADURI" minOccurs="0" maxOccurs="999999999"/>
<xsd:element name="E1BPADPAG" type="DEBMDM06.E1BPADPAG" minOccurs="0" maxOccurs="999999999"/>
<xsd:element name="E1BPAD_REM" type="DEBMDM06.E1BPAD_REM" minOccurs="0" maxOccurs="999999999"/>
<xsd:element name="E1BPCOMREM" type="DEBMDM06.E1BPCOMREM" minOccurs="0" maxOccurs="999999999"/>

MDM Syndication Automation Issue.

Hi
              Iam practising MDM asyndication process automation. As part of this I have created Syndication Map and assigned this map to Outbount port in MDM console. BUt i can not see any syndicated Files in outboud ready folder in MDM Server.
          can any one tell me the settings neede for this.Iin one of the blog(/people/harrison.holland5/blog/2007/01/22/testing-and-monitoring-an-interface-between-mdm-xi) it is given that we need to set Auto Syndication Task Enabled=True but i can not see this property in my mds_ini0 file.
Now I verified "C:\Program Files\SAP MDM 5.5\Server\Distributions\LOCALHOST-XP_MSQL\Sand\Outbound\NewRemoteSystem(3)\OutECC\Ready:
Regards,
Venki

Hi
      The Port is defined as Automatic with processing interval as continuous. I am getting exception as Auto syndication failed connecting to MDM Server localhost
I am doubtful on MDSS.iniSettings here with Iam providing those.
[GLOBAL]
MDM Server Name=localhost
Auto Syndication Task Enabled=True
Auto Syndication Task Delay (seconds)=5
Default Interface Language Code=eng
Default Interface Country Code=US
String Resource Dir=C:\Program Files\SAP MDM 5.5\Syndication Server\LangStrings\
Log Dir=C:\PROGRA1\SAPMDM1.5\SYNDIC~2\Logs\
SLD Registration=True
Wily Instrumentation=True
Wily Instrumentation Level Threshold=0
In the previous message it is said to set userid/Pw. I donot have any userid/Pw for MDM server.But the repository Name is Customers and repository User Name is Admin and there is no password for that.
Regards,
Venki.

MDM Syndication selection option restrictions

Hi all,
In the MDM Syndicator is it possible to only syndicate certain details of the header record for a header and detail hierarchy structure?
For our Scenario, GL Account has the hierarchy as a Single Chart of Accounts assigned to multiple Company Code records.
· GL Account Master Record
· Chart of Account Details (SKA1 - Header)
 o Company Code Details (SKB1 - Detail)
In the repository we have SKA1 as the Main table and SKB1 as a sub table within SKA1. While the content is imported it comes in as 1 Record with multiple Company code level details. Is there anyway to restrict the selection for syndication for a given SKA1 - Header and get only the selected SKB1 - Details syndicated?
For example if for Chart of Account has 5 company codes A, B, C, D and E. Can we restrict the syndication of the of the record with selected company code details only (Example B and D - without the details for A, B, C being syndicated).
I appreciate the time.
Thanks,
-Raj.

Hi Raj
Here I do have some suggestions regarding your request, correct me if i am wrong, basically you are looking to syndicate the records by applying the filter row wise or column wise.
Row wise : Required all the field but search criteria as one or two fields ( for example filtering based on COA and Company code).
Column wise : Required only few fields to be syndicate, either row wise filter applied or not.
Hope I understood your question.
Solution:
Row wise : Use search parameter tab, search for particular COA and Company code and save the search for future purpose [from MENu SEARCH->SAVE SEARCH].
Column wise : Create Destination items for the fields which u want to syndicate and try to map those fields wt Original source items and try to syndicate the same.
Hope I have covered the point what you expected.
thanks
Alexander
P.S. Kindly reward the points, i found helpful.

XI XSD export fails in MDM syndication

Dear experts,
I have created a message type in XI and have exported the XSD. When I try to import the XSD in the syndicator, I get an error message: Root element required.
This is my structure which I exported:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_CSR_CUSTOMER xmlns:ns0="urn://xi/csr/customer">
<CSR_CUSTOMER_FILE>
<CSR_CUSTOMER>
<ZZSRCDTA/>
<ZZBMORG>53</ZZBMORG>
<CA_OUTNM>12449</CA_OUTNM>
<ZKATR7/>
<ZZDSBCHN/>
<ZZKEYACC/>
<ZZKEYCOD/>
<ZZSALCNR/>
<CA_CTRDN>17</CA_CTRDN>
<ZZACVDAT/>
<ZZINADAT/>
<TXTMD>TESCO</TXTMD>
</CSR_CUSTOMER>
</CSR_CUSTOMER_FILE>
</ns0:MT_CSR_CUSTOMER>
Then I tried to import the XSD into MS Access and export it again. MDM will accept this file, but if I then syndicate, the message is not accepted by XI because the </ns0:MT_CSR_CUSTOMER> is missing.
How can help out?
Thanks in advance!

Hi Ranjeet,
I export the XSD from the Message Type from within the XI Repository. And as I said in the post, the problem lies in MDM. MDM will not accept this XSD.
The error is: Root element required.
And when I import this XSD in e.g. Access, it works.... for access then...

MDM Syndication - Is it possible to split a text field?

I am trying to find a way to manage multilingual R/3 Purchase Order Text in MDM. The problem I am having is that we want to maintain this as one field in MDM, which the only feasible option appears to be a Text Large field. Text fields are too short now that they are only 333 characters, Lookups are not involved so this cannot be a multivalued Text field, Text Blocks don't seem to work for this, and Qualified Lookups don't appear to handle the multi-lingual aspect.
The problem is, somehow this one large text field needs to be broken down when sent back to R/3, as R/3 can only handle 133 characters per line. As far as I can tell, there is no way to do this.
Can anyone help?
Thanks!

Hi Ryan,
I am trying to find a way to manage multilingual R/3 Purchase Order Text in MDM. The problem I am having is that we want to maintain this as one field in MDM, which the only feasible option appears to be a Text Large field. Text fields are too short now that they are only 333 characters, Lookups are not involved so this cannot be a multivalued Text field, Text Blocks don't seem to work for this, and Qualified Lookups don't appear to handle the multi-lingual aspect.
The problem is, somehow this one large text field needs to be broken down when sent back to R/3, as R/3 can only handle 133 characters per line. As far as I can tell, there is no way to do this.
If I have understood your probelm correctly, then I think you want to import the Multilingual data in MDM. You can easily do that by Pivoting the source and then Importing the MUltilingual data into MDM.
Then in the Syndicator, you can split the Multilingual Fields BY Language BY Value, (which is a feature present in the Syndicator)into Various fields, which you can indivually map it to the different destination fields. For this, you must have multiple fields in your Destination side so that you can map them individually with the Splitted fields.
Please refer below to get info on the above mentioned feature:
http://help.sap.com/saphelp_mdm550/helpdata/en/ff/37e4c6857449388ddb6c77f160ac4f/frameset.htm -> GO to-> Multilingual Support-> Multilingual Opeartions->Splitting Multilingual Source Items.
I think this what is what your requirement is. For refrence , kindly go through the link below, which will guide you to import the Multilingual Data and then Syndicate the file in .CSV format.
End to End Solution to Multilingual Master Data :
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/90e42521-0645-2b10-d1b2-e9f6fab39856
Multiple Languages in MDM Part 1: Console Settings for Multilingual Master Data -
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30fddcb9-2a40-2b10-a9a9-db552d687617
Multiple Languages in MDM Part 4: Syndicating Data in Multiple Languages -
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/50b2702d-2b40-2b10-549e-92c0e88c8135
Hope it helps.
Thanks and Regards
Nitin Jain

Regarding MDM Import and Syndication Server

Hi,
I have earlier worked in MDM Import Server.
Today, I successfully did MDM Syndication by
MDM Syndicator.
Now, the point is I need to do Import and Syndication
by MDM Import Server and MDM Syndication Server.
The MDM Version is 5.5.
Now, the point is under my installed directory:
F:\MDM SERVER\Server
in mds.ini file:
I need to give the following path:
Distribution Root Dir=F:\MDMSER~1\Server\Distributions\
I think other than these I don't have to do any configuration
in mdis.ini or mdss.ini.
Also, I have already inbound and outbound ports made and linked
to inbound and outbound maps.
Is there any more configuration needed?
Regards
Neha Singh

Hi Neha,
There are many configuration needed to complete the Automatic import and syndication using MDIS and MDSS.
Please go through the link below for the same:
Master Data Management Import Server and Master Data Management Syndication Server - Webinar Powerpoint
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/8973bcaf-0801-0010-b7a7-f6af6b1df00e
This will give you the complete steps to perform the same.
Hope it helps.
Thanks and Regards
Nitin Jain

Next Syndication Date and Time changing

Hi Experts,
While setting the Outbound port to Automatic with Daily processing interval i set Next Syndication Date and Time to some value.
but after the first occurrence of syndication, Next Syndication Date and Next Syndication Time are changing to new unexpected value.
I am using MDM 5.5 SP6 version.
Please help on this.

Hi Prashant
Copying from the SAP Note 1124246-
Bug Fixes
MDM SYNDICATION SERVER 5.5
Fixed: Change for auto syndication to update next syndication time without accumulating time offsets
Please close the thread if answered.
Thanks-Ravi

MDM scenario

Hello Folks
Wanted to understand how would we do a scenario like picking data from MDM and posting it to a portal?
Please advice.
Thanks

Please visit these blogs also
MDM Syndicator (Helpful)
/people/harrison.holland5/blog/2006/11/27/mdm-syndication
XI Configuration for MDM Integration
/people/harrison.holland5/blog/2006/12/20/xi-configuration-for-mdm-integration--sample-scenario
Testing and Monitoring an Interface between MDM and XI.
/people/harrison.holland5/blog/2007/01/22/testing-and-monitoring-an-interface-between-mdm-xi

ABAP APIs / Java APIs (MDM Extraction)

Hi All,
If I have to extract data out of MDM Repository without using the MDM Syndication functionality, How can I do that?
I know there is something called ABAP APIs / Java APIs. Can this ABAP/Java APIs be used to extract data out of MDM Repositories?
If yes, where exactly are these ABAP/Java programs written? In MDM server? Or Portal server?
Thanks,

You can actually do that with the help of API.
for similar issue follow below threads.
Data syndication using MDM Java API
Retrieve Data using Java API
Hope this help
thx
Deep

MDM with Business Connector

Does anyone know if MDM can work with Business Connector?

It's been a while since I have used Business Connector, but if I'm not mistaken BC can pick up files, correct? If so, then yes they will work together. The process would like something like this:
1. MDM Syndication Server generates XML file
2. Business Connector picks up file
3. Business Connector maps to desired format
4. Business Connector sends to target system.
Same as XI, except BC is the EAI tool instead.

MDM to R3 interface

Hi,
Can someone tell me how to build the XI interface between MDM and R3 using multi-mapping.
Idoc: Matmas
Farah

Hi ,
Please go through the below links...
/people/harrison.holland5/blog/2006/11/27/mdm-syndication : MDM Syndicator (Helpful)
/people/harrison.holland5/blog/2006/12/20/xi-configuration-for-mdm-integration--sample-scenario : XI Configuration for MDM Integration.
/people/harrison.holland5/blog/2007/01/22/testing-and-monitoring-an-interface-between-mdm-xi : Testing and Monitoring an Interface between MDM and XI.
/people/balas.gorla/blog/2007/02/05/r3-xi-mdm-outbound-scenario : R/3-XI-MDM (Outbound Scenario)
/people/balas.gorla/blog/2006/09/27/mdm-xi-r3-integration : MDM-XI-R/3 Integration
Hope this helps,
+ An

Xi-mdm integration

Hi all,
I am new to MDM,
I heard that Xi is used to migrate the data to the MDM server where the data is stored in the XML format.
I require the basic details of how to integrate Xi with MDM for doing the Same ,and also the basic details about MDM.
Thanks,
Srinivas

Hi Srinivas,
Please go through the below links... They give you a very clear description related to MDM integration with XI. All the three links are related to each other.
/people/harrison.holland5/blog/2006/11/27/mdm-syndication : MDM Syndicator (Helpful)
/people/harrison.holland5/blog/2006/12/20/xi-configuration-for-mdm-integration--sample-scenario : XI Configuration for MDM Integration.
/people/harrison.holland5/blog/2007/01/22/testing-and-monitoring-an-interface-between-mdm-xi : Testing and Monitoring an Interface between MDM and XI.
Hope this helps...
If you have any more doubts, you are welcome to get abck to me.
Regards
Kiran..

MDM Syndication

Similar Messages

Maybe you are looking for