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"/>

Similar Messages

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 - 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 ABAP API ISSUE ( server is getting down )

Hi Folks,
I am trying to retrieve matching results using MDM ABAP API.
I am spiting source and target records into lot of blocks dynamically
in program. I am getting output 2 to 3 times if i can run program
sequential after that server is getting down (before running program
i am completely going out and rerunning).After server bring's up
running couple of times and server getting down.
Please help me how can i solve this issue.
Thanks,
Anil.

Hi Anil,
You can have a look at the below links can cross check the steps you have performed in establishing the connection correctly:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/media/uuid/00c49ffb-e5e5-2910-73ba-c85af1da5b0a
ABAP APIs: Error "The connection is not trusted"
Comaptible ABAP APIs for MDM 5.5 SP6 Patch 1
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/tip%2b%2bMDM%2bABAP-API%2b%2bThings%2bto%2bRemember%2b(for%2bStarters)
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e060251e-b58d-2910-02a2-c9a1d60d9116
Hope It Helped
Thanks & Regards
Simona Pinto

MDM Sender Adapter issue in SAP PI7.1

Hi All,
How to schedule(there is no poll interval in Sender communication channel) MDM PI sender Adapter.
Everytime we need to start and stop the channel then only file is being picked up.
I checked port details, file is not picking up automatically
Please suggest me.
Reagrds,
Hemanth

Hi Hemanth,
There are different versions of the MDM PI Adapter which correspond to the relevant PI version: one for PI 7.0 and the other for PI 7.1; the two are not interchangeable. Ensure that you have downloaded the correct version for your landscape i.e. PI 7.1
Setting Up Outbound Messaging from MDM:
Make sure that the MDM Java API (Connector) deployed on the J2EE engine matches the version of the MDM server on which the repository is mounted.
Also, Check that there is no more than one MDM sender configured per MDM outbound port in your system landscape
For more details, refer this below link
http://help.sap.com/saphelp_nwmdm71/helpdata/en/48/9854c94d3217cee10000000a421937/content.htm
Also, refer SAP Note 1337471 - Help for analysis of MDM PI Adapter messaging issues
https://websmp130.sap-ag.de/sap/support/notes/1337471
Thanks and Regards,
Mandeep Saini

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 ABAP API issue

Hi Floks,
We are getting core dump and server is getting down.
If i can run same program with same variant working couple of times
sequentially after that getting this issue.
Thanks,
Anil.

Hi Anil,
You can have a look at the below links can cross check the steps you have performed in establishing the connection correctly:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/media/uuid/00c49ffb-e5e5-2910-73ba-c85af1da5b0a
ABAP APIs: Error "The connection is not trusted"
Comaptible ABAP APIs for MDM 5.5 SP6 Patch 1
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/tip%2b%2bMDM%2bABAP-API%2b%2bThings%2bto%2bRemember%2b(for%2bStarters)
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e060251e-b58d-2910-02a2-c9a1d60d9116
Hope It Helped
Thanks & Regards
Simona Pinto

Syndication server issue

Hi All,
I am facing an issue with the syndication server. The syndication server is scanning only 2-3 ports out of a total of 30.
It is bypassing the rest of the ports.
When i am checking the syndication server logs, i am able to see few ports only.
Can you let me know what could be the reason for this unusual thing.
I have unloaded the repository and again loaded it. Restarted the syndication service as well as the syndication server
We are still in MDM5.5 SP04.
Please let me know what i need to do now.
BR
SK

Sushil -
make sure below points
Type : Outbound
Processing Type : Automatic
Map: Name of the syndication map to use with the port
When MDSS completes a syndication to a port, it places the syndication file in the portu2019s Ready folder. The Ready folder is part of the following fixed directory structure, located beneath the Master Data Serveru2019s distribution root directory
root/DBMSinstance_DBMStype/RepositoryName/Outbound/ RemoteSystem/PortName/Ready
here root need to set in mds.ini
This time again see the exact log and let us know.
thx
Deep

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

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.

MDM Sender Adapter issue

Hi All,
How to schedule(there is no poll interval in Sender communication channel) MDM PI sender Adapter.
Everytime we need to start and stop the channel then only file is being picked up.
I checked port details, file is not picking up automatically
Please suggest me.
Reagrds,
Hemanth

couple of check that I can suggest from this [help.sap guide|http://help.sap.com/saphelp_nwmdm71/helpdata/en/48/9854c94d3217cee10000000a421937/content.htm] guide...
1. Does the Java API match the MDM serve repository version.
2. No duplicate MDM sender channel exist.
~SaNv...

MDM API Connection issue

Hi,
I am trying to establish connection to MDM server by the following statement ( Java stadalone app)
ConnectionPoolFactory.getInstance("Host:6000");
But I am getting exception "com.sap.mdm.net.ConnectionException: Could not open minimum connections."
Am I missing some config on MDM side??
Thanks, Anil

Dear Anil,
first of all you need to connect to the MDM server.
This is done without any repository consideration just by the hostname of the MDM-Server.
The standard port used to make this connection from your (Java) client is 20005.
You can change this port where MDM-Server is listening in mds.ini by providing another one.
CODE:
public ConnectionAccessor getConnection() {
String sHostName = MyServerName;
ConnectionAccessor connection = null;
// We need a try / catch statement or a throws for the method
try {
    /* retrieve connection from Factory
     * The hostname can be the name of the server if it is listening on the standard port 20005
     * or a combination of Servername:Portnumber eg. MDMSERVER:40000
    connection = SimpleConnectionFactory.getInstance(sHostName);
} catch (ConnectionException e){
    // Do some exception handling
    e.printStackTrace();
// return the connection or if an exception occurred a NULL value
return connection;
Then you can think about the Session you want to make to the repository.
This is taken from my Blog:
In general there are three different kinds of connections and depending on the thing you want to do, you will need a different kind. But let me point out the three different kinds available:
   1. Server session:
      A server session is used for management operations of a running MDM Server. This could be mounting- or unarchive a repository. You could even stop the server with this kind of session if needed. In fact u could say that the operations done with MDM Console partly need a server session.
      The associated command would be: CreateServerSessionCommand
   2. Repository Session:
      A repository session is bound to a specific repository and is used for management operations. Operations could be CRUD (Create, Read, Update, Delete) on Repository elements (user roles, model data such as fields, tables...) not the data in the repository itself. Same as with the server session we could say that a repository session is partly needed by the MDM Console.
      The associated command would be: CreateRepositorySessionCommand
   3. User session
      A user session is used for any operation that might be performed by the MDM Datamanager. Basically any kind of data manipulation is done using a user session (CRUD of Data). So having this session we will be able to perform searches, creating, updating and deleting data records.
      The associated command would be: CreateUserSessionCommand
Most of the time you will need a User Session to read/write data from MDM.
So to get a User-Session you will need to use the CreateUserSessionCommand.
   RepositoryIdentifier repId = new RepositoryIdentifier(RepositoryNameAsString, DBServerNameAsString, DBMSTypeAsString);
   // Create the command to get the Session
   CreateUserSessionCommand createUserSessionCommand = new CreateUserSessionCommand(connection);
   // Set the identifier
   createUserSessionCommand.setRepositoryIdentifier(repId);
   // Set the region to use for Session - (Language)
   createUserSessionCommand.setDataRegion(dataRegionAsString);
   // Execute the command
   createUserSessionCommand.execute();
   // Get the session identifier
   String session = createUserSessionCommand.getUserSession();
Please node that if the RepositoryIdentifier is set the wrong way you will not be able to create a connection as well. So please double check this parameters.
After all you need to authenticate the session but for further details please have a look at the blog Regina provided the link to.
Hope this helped to find the problem!
Best regards,
Tobi

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

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 demmdm06 issue..

Similar Messages

Maybe you are looking for