MDM Layout Server ABAP API

Hi
I need to install MDM Layout Server X64 for MDM5.5 SP6
I cant find MDM Layout server in this CD ( SAP Master Data Management 5.5 SP6)
Can you guys please let me where to download MDM Layout Server for X64??
IS MDM Layout server is Mandatory
We have PI 7.1, ECC6 in our landscape
For ECC6 (EHP3) I need to apply this Addon Component MDM_TECH 555 700?
Do I need to install Addon for PI7.1 server as well? if yes what Addon?
Regards
Musaab

Hi Musaab,
As fas as I know, Layout Server is not required for normal processes in MDM like import and export. I feel layout server is used when you are looking for publishing purposes with the DTP applications. You will be generally using MDM server, Import server and Syndication Server,
Please go through the installation guide for MDM components in the link below:
https://websmp102.sap-ag.de/~sapidb/011000358700001119842007E
The above link will help you guide on the installations related to MDM.
Coming to your query regarding ABAP API - MDM_TECH 555 700
This tech add on will installed from the SAINT transaction.
Please follow the link below and go to Page No-5 to see the details.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/601ddb01-e5c8-2910-d981-b190b51fca44
Hope this info helps.
Thanks and Regards
Simona Pinto

Similar Messages

MDM Layout server crashes when trying to open Publisher

hi,
I have MDM Layout Server and Publisher installed on my machine. When I try to open the Publisher, it is asking me for the server to connect to. I am providing the name of my machine. I am then seeing a Runtime Error dialog box with the message Microsoft Visual C++ Runtime Library Runtime Error! R6025 - pure virtual function call and the Layout server is crashing after that instance.
I tried to look at the log files ServerXXXX.xml and AssertionXXXX.xml files that got generated inside the Layout Server directory. This is the message in the Server XXXX.xml
+ <Trace ts="2008/02/09 21:42:32.578 GMT" tid="3924" entry-no="0">Server does not register to System Landscape Directory. Set parameter 'SLDRegistration' to true in the .ini file for registration to System Landscape Directory.</Trace>+
Here is the message from the AssertionXXXX.xml file.
+ <Assert ts="2008/02/09 21:45:54.406 GMT" tid="4932" entry-no="1" file="..\..\..\MDM\Servers\MDLS\FamilyAccessSession.cpp" line="81">false</Assert>+
I have set the SLDRegistration parameter to False in the Layout Server.ini file. I am missing something or Is this a bug? Can someone please help me with this?
Thanks.

Not sure but you can try with these:
Set SLDRegistration variable in both the files in mds.ini as well as in layout server.ini to False and then try.
If does not work Set SLDRegistration variable in both the files to True and then try.
hope it may work.
BR,
Alok

Error when connecting to MDM Layout Server

Hi Experts,
Can any one help ? I keep getting this runtime error when starting MDM5.5 SP06 Publisher GUI on version 5.5.64.84 to connect local Layout Server:
Program: c:\Program1\SAPMDM1.5\Layout~1\mdls.exe
R6025
- Pure virtual function call
I have also searched in google related for the above message and I got to know from MS MSDN lib:
Calling a pure virtual function is a programming error, so you need to find the call to the pure virtual function and rewrite the code so it is not called.
But I still don't know where I can see the code in this circumstance ? Or any possibilities to fix it ?
Thanks very much for your help
Kind regards,
Wei Dona

Hi Wei Dona,
The following are thre links to the installation and sizing guides, there some specificaitons and requirements described in these documents.
Hope these will help in your case.
https://websmp203.sap-ag.de/~sapidb/011000358700006267202006E
https://websmp203.sap-ag.de/~sapidb/011000358700001119842007E
Best Regards,
Silpa Chillakuru

How to use MDM ABAP API?

Hi Guys,
I want to use ABAP API for manipulating MDM records(EX Adding two field values and assign into another field value).
Can anybody guide me step by step process?
Best Regards
Devaraj PK

Hi Devraj,
Please go through this pdf:
1. How To identify identical master data records using SAP MDM 5.5 ABAP APIs
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e060251e-b58d-2910-02a2-c9a1d60d9116
2. MDM ABAP API
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/media/uuid/00c49ffb-e5e5-2910-73ba-c85af1da5b0a
http://help.sap.com/saphelp_mdm550/helpdata/en/44/93aa6831381053e10000000a422035/content.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/connectivity-ABAP+API&
Pls rewrds if found helpful.
BR,
Alok Sharma

ABAP API - MDM Workflow execute

Hi,
Do we have any methods/function modules available to access MDM Workflow using ABAP API?
I have checked through the 19 tutorials of MDM ABAP API available at service.sap.com but was not successful.
Regards,
Subramanian V.

Up to now the MDM workflow is not supported by the MDM ABAP API.
Regards
Andreas

Layout Server in MDM Publishing

Dear MDM follower.
We have created the repository in console and maintained the records in Data Manager.When we go in MDM publisher,it is asking for MDM Layout Server.What is this layout server.Can anyone explain me.
Waiting for an early rejoinder.
Yogesh Walde

hi yogesh,
To publish your catalog, prior to that you have to create layout for the records(how the product should be shown i.e layout design) could be done in layout server.
Prior to MDM SP4, we have layout mode, in that mode we will design the layout, --- hope this will help you.
srinivas

ABAP API and Key Mapping

Hello there,
I am trying to use the MDM 7.1 ABAP API to access MDM data from within a BI system.
Now I am wondering how to access key mapping for records in the Main Table.
In the Java API there is the RetrieveRecordsKeyMappingsCommand which returns all key mapping information for a list of record IDs. But I cannot find something similar in the ABAP API.
Who knows where to start?
Thanks for hints
Ingo

Hi ,
In ABAP API also you can retrieve key mapping of main table records using function 'MDM_API_RETR_CLIENT_SYS_KEYS'.
You will get details of this function in sap library or ABAP API documentation provided by SAP.
For any further queries kindly reply.
Regards,
Neethu Joy

Layout Server Installation

Hi All,
As per my knowledge, layout server installation can be done in two ways:
1. layout server as a central server with Multiple Publisher clients accessing common server.
2. layout server on individual clients system
I want to know Pros and cons of both installation approaches of Layout server and which one is preferred.
Also any idea which installation design for layout server is recommended by SAP (i.e. installing layout server as a central server or on local machine.). I searched, but couldnu2019t find any standard SAP document on this. If you have any such document, please forward it to me. It will be of great help. Thanks.
Regards,
Shiv

Hi Shiv,
I didn't find any documentation related to this. However i would like to add my understanding
Note: As per the Sizing Guide, MDM Layout server should be installed on the m/c having min of 2GB RAM (4GB Recommended).
1. layout server as a central server with Multiple Publisher clients accessing common server
Advantages
1. Only one layout server needs to be installed and all the Clients i.e. MDM Publisher will access this centralized layout server.
2. It reduces Hardware cost since only one centralized m/c is required.
3. One layout server needs to be managed if any configuration changes are required.
Disadvantages
1. Simultaneous access of this centralized server affects the performance
2. Would be slow as compare to Approach-2 because of delay due to network.
2. layout server on individual clients system
Advantages
1. Better performance as compare to Approach-1 since no n/w connections are involved in communication between the Layout server and MDM Publisher.
2. No extra hardware is required for layout server installation since every individual m/c contains its own layout server.
Disadvantages
1. As per the Note above, individual machines should have min of 2GB RAM just because of Layout Server. Hence if the number of clients increases so does the cost of hardware as well.
2. Difficult to manage as compare to Approach-1 (Ref to Adv-3).
Based on above points, I would recommend the first approach since it is cost effective, easy maintainance. As far as performance goes, n/w speed could be enhanced even at the lower cost as compare to installing multiple layout servers on individual m/cs.
Regards,
Jitesh Talreja

ABAP API + Workflow

Hi All,
How can we access or trigger MDM Workflow using ABAP API.
Please help...
Regards,
Nikhil

Hi ,
Please check the operation guides available in service marketplace https://websmp204.sap-ag.de/nw04operation (ABAP API /ABAP API how to guides) for information.
Regards,
Anita

Layout server issues

Hi,
while I am connecting to layout server from Publisher its showing RPC error.
I have installed Layout server , MDS in same machine.
before open MDM publisher MDLS, MDS are up & running.
While connecting to Layout server from Publisher its throwing error & MDLS is automatically stopping.
Could any have idea about this issue. any solution to solve the problem.
Thanks in Advance.
Audi

Hi Audinarayana,
Kindly go thru this links,it might help you in analyzing your problem:
MDM Layout server crashes when trying to open Publisher
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/20beeeb5-7316-2a10-d7b4-af61e95c11a5
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c4e3bf90-0201-0010-418f-c40d2264a63a
Hope It Helped
Thanks & Regards
Simona Pinto

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

Program _____.MDS not registered..PI 7.1 EHP 1-MDM 7.1 Integration-ABAP API

Hi,
I am on the way of integrating ABAP API in PI 7.1 EHP 1 with MDM 7.1
I installed MDM ABAP API in PI system.
In transaction MDMAPIC, created MDM Server Connection with default port, DBMS Hosts and MDM Repository.
After I did the above tasks, I tested the RFC Connection, But its failed with the following error.
Connection Test MDM_API_GEN_DEFIANCEDEP
Connection Type TCP/IP Connection
Logon     Connection Error
Error Details     Error when opening an RFC connection (CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=67
Error Details     ERROR: program DEFIANCEDEP.MDS not registered
Error Details     LOCATION: SAP-Gateway on host DEFIANCEDPI / sapgw00
Error Details     DETAIL: TP DEFIANCEDEP.MDS not registered
Error Details     COMPONENT: SAP-Gateway
Error Details     COUNTER: 87
Error Details     MODULE: gwr3cpic.c
Error Details     LINE: 1714
Error Details     RETURN CODE: 679
Error Details     SUBRC: 0
Error Details     RELEASE: 711
Error Details     TIME: Sat Mar 12 13:53:55 2011
Error Details     VERSION: 2
Appreciated if replied with the proper resolution at the earliest.
Thanks in Advance
Pradeep Shetty

Hi Kanstantsin Chernichenka,
Thanks for your reply.
I tried the given suggestion. And even restarted the PI and MDM system.
Still, I am facing the same problem.
My allow.ip file contains
122.183.187.24;
122.183.187.25;
115.242.211.112;
115.184.2.47;
My MDS.ini file contents are
[MDM Server]
XCS Ini Version=1
Accelerator Dir=E:\usr\sap\MDM\MDS02\mdm\accelerators
Log Dir=E:\usr\sap\MDM\MDS02\log
Report Dir=E:\usr\sap\MDM\MDS02\mdm\reports
Archive Dir=E:\usr\sap\MDM\MDS02\mdm\archives
Distribution Root Dir=E:\usr\sap\MDM\MDS02\mdm\distributions
Transport Dir=E:\usr\sap\MDM\MDS02\mdm\transport
Modifications Dir=E:\usr\sap\MDM\MDS02\mdm\modifications
Lexicon Dir=E:\usr\sap\MDM\MDS02\exe\Lexicons\
Extra DBConnection Validation=True
Log SQL Errors=True
String Resource Dir=E:\usr\sap\MDM\MDS02\exe\LangStrings\
Stemmer Install Dir=E:\usr\sap\MDM\MDS02\exe
Wily Instrumentation=False
Wily Instrumentation Level Threshold=10
SLD Registration=True
Skip Unchanged Records=False
Autostart=0
MDS Ini Version=1
RELEASE\UseAssert=True
Tracing Level=3
LogViewer Format Logging=False
LogViewer Format Tracing=False
Trusted SAP Systems=DPI
TrustFiles Dir=E:\usr\sap\MDM\MDS02\config
Max Threads Per Operation=Auto
Lock Account After Failed Password Attempts=5
Lock Account Duration=1800
Minimal Password Length=5
Password Expiration Days=90
Password Expiration Warning=7
Disable Read Access To Corrupt Repositories=False
MDS Scone=
Log SQL Modifications=False
Maximum DBMS Bind Count=512
Oracle\Dll=OCI.DLL
Allow Console to Retrieve Files=True
Oracle Tablespace Files=1
Default Interface Language Code=eng
Default Interface Country Code=US
Client Ping Timeout Minutes=0
Inactive Client Timeout Minutes=30
Value Retrieval Threshold=0
Protect Family Nodes With Locked Data=False
Number Of Stemmers Per Language=2
TrexDllPath=
Import Slice Size=2048
Bulk Import Silo=True
Safe Silo Mode=False
Enable Change Stamp Logging=False
Always Verify DBMS Connection Before Executing SQL Statements=False
Disable Read Access To Repositories That Require Restart=False
Family Retrieval Threshold=30000
Enable Client Dictionaries=False
Restricted Url For Client Export=
Index_Page_Margin=10
Default Slice Size=500
Default Slice Wait Time MS=300
Enable Slicing For Non-Bulk Operations=False
Multithreaded Matching=True
SAP RFC Gateways=
[MDM Server\Databases\MDM_1MDMORCL_5_3_4_3]
Port=2345
Login=SYSTEM
Password+=ES066H2NVHDCFSJ206LJ9I995SLBVSA21OMQPM0
Stemmer Language=
Stemmer Variant=
Valid Keyword Chars=abcdefghijklmnopqrstuvwxyz0123456789
Max Large Text Length=250000
Number of Rows Per Fetch=100
Max Initial MB to Retain=4
Max Send Failure MB to Retain=4
Workflow Detailed Report=False
Mail Server=
Mail SMTP Timeout=1
Here I am requesting you to send your valuable feedback at the earliest.
Thanks
Pradeep Shetty

ABAP API--Server return code 0xFFAA2011:

Hello SDN,
I was stuck with new issue regarding ABAP API. I am trying to update the attribute value through ABAP API, but it is giving me the error "Server return code 0xFFAA2011: RC_CM_RECORDS_LINKED_TO_DOMAINVALUE".
we are using the class for APIs CL_MDM_PROVIDER_55_SP06_PL05. MDM version is 5.5 and patch 5.
Please help me out from this issue. I am getting this error.
api that I am using was
"UPDATE_ATTRIBUT".
Waiting for your valuable response.
Regard

done. This API is working from MDM7 version, not available in MDM5

ABAP API's - URGENT- Tracking of changes in MDM.

Hello Experts,
I want to track all the changes made in MDM In ECC. I know that i can do it using ABAP API's tracking feature.
I have already established the connection between ECC and MDM.
I would want to know all the exact steps to enable tracking and monitoring through ABAP API's.
Helpful answers will be highly appreciated.
Thanks and Regards
Nitin jain
Edited by: Nitin Jain on Jan 29, 2008 4:45 AM

Hi Nitin,
As you have already connected to MDM through R/3.
For Changing Tracking, you have to call the function 'MDM_ADMIN_RETR_CHANGE_TRACKING' for that you have to use structure MDM_AUDIT_INFORMATION.
I am not quite sure will it work. Please try.
Hope it helps you,
Regarding CCMS montoring in MDM ABAP APIs, refer the link:
How TO Guides available on Service Market Place.
https://websmp210.sap-ag.de/~sapidb/011000358700004121872006E --> operations
Here apart from How to guides you will also get
HowTo_CCMS_Trace.pdf : It will guide you if there any errors come in connection b/w R/3 and MDM. it does the following:
. Collect and evaluate application log data
- Collect and evaluate kernel trace data
- Problem solution showcasecomes
if your HowTo_07.pdf on Tracing report is working fine then you can identify whether is there any error coming or not.
Lets take an example : if you Shut down the MDM Server.
Then in R/3 On running HowTO_07 program:you will get ERROR DURING CONNECT: 3 , ERROR DURING DISCONNECT: 3
The Reason for this is the unavailable server. but here you will not get more details. For this
After implementing HowTo_CCMS_Trace guide: under transaction RZ20 : In Application Trace you will see error Partner not reached (hostXXX, Service 20005) and
In Kernel WorkProcess Trace: You will get error: MDE Kernel Error, NiRaw2ConnectError: the attempt to establish a socket connect caused an error.
So in this way you evaluate the error in more details.
Note: For this you should have authroize to use the transaction RZ20 in R/3 System.
Hope it helps you,
Mandeep Saini.

Read data from MDM For Lookup and Flat table using MDM ABAP API

Hi,
I have requriment to read data from MDM from FLAT and Lookup table using MDM ABAP API. My design is like this ,
I have one ITEMS (Main table in MDM) and inside that i have one Lookup flat table ITEM_TYPE , my requriment is to read Item number and its related Item type.
From ABAP.
Please help if any body has any idea.
Regards,
Shyam

HI Guys,
I found my solution by myself. Below is the solution , hope this will help others:-
Retrieve data from MDM using MDM ABAP API.
Step- 1. Create structure in SAP with the same name as that of MDM field code for MDM Main table.
Step-2. Create another structure in SAP having all lookup fields of MDM , fieldname in ECC must be same as that of MDM field
code.
Step-3.Create structure in SAP for individual lookup field(Single Field only)   with the same name as MDM Field code.
Step-4.
DATA: IT_QUERY            TYPE STANDARD TABLE OF MDM_QUERY, "MDM_QUERY_TABLE,
      WA_QUERY            TYPE MDM_QUERY,
      WA_CDT_TEXT         TYPE MDM_CDT_TEXT,
      IT_RESULT_SET_KEY   TYPE MDM_SEARCH_RESULT_TABLE,
      WA_RESULT_SET_KEY   TYPE MDM_SEARCH_RESULT,
      WA_STRING           TYPE STRING.
DATA:<Internal table> TYPE STANDARD TABLE OF <SAP Str Having all LOOKup Fields>
DATA: :<Internal table>TYPE STANDARD TABLE OF <SAP Str one LOOKup field>,
     <Workarea> LIKE LINE OF :<Internal table>.
*PASS LOGICAL OBJECT NAME.
V_LOG_OBJECT_NAME = 'Logical object name defined in Customization'.
Define logon language, country & region for server
WA_LANGUAGE-LANGUAGE = 'eng'.
WA_LANGUAGE-COUNTRY = 'US'.
WA_LANGUAGE-REGION = 'USA'.
TRY.
    CREATE OBJECT LR_API
      EXPORTING
        IV_LOG_OBJECT_NAME = V_LOG_OBJECT_NAME.
ENDTRY.
CONNECT to repository. Apply particular logon language info
CALL METHOD LR_API->MO_ACCESSOR->CONNECT
EXPORTING
    IS_REPOSITORY_LANGUAGE = WA_LANGUAGE.
*NOW PASS ITEM NO AND GET KEY FROM MDM.
CLEAR WA_QUERY.
WA_QUERY-PARAMETER_CODE = <MDM FIELD CODE>. "Field code
WA_QUERY-OPERATOR        = 'EQ'. "Contains
WA_QUERY-DIMENSION_TYPE = 1. "Field search
WA_QUERY-CONSTRAINT_TYPE = 8. "Text search
WA_STRING                = <Field Value>.
GET REFERENCE OF WA_STRING INTO WA_QUERY-VALUE_LOW.
APPEND WA_QUERY TO IT_QUERY.
CLEAR WA_QUERY.
*PASS ITEM NUMBER AND GET RELATED KEY FROM MDM.
TRY.
    CALL METHOD LR_API->MO_CORE_SERVICE->QUERY
      EXPORTING
        IV_OBJECT_TYPE_CODE = <MDM Main Table>
        IT_QUERY            = IT_QUERY
      IMPORTING
        ET_RESULT_SET       = IT_RESULT_SET_KEY.
CATCH CX_MDM_COMMUNICATION_FAILURE .
CATCH CX_MDM_KERNEL .
CATCH CX_MDM_NOT_SUPPORTED .
CATCH CX_MDM_USAGE_ERROR .
CATCH CX_MDM_PROVIDER .
CATCH CX_MDM_SERVER_RC_CODE .
ENDTRY.
Pass record id into keys.
LOOP AT IT_RESULT_SET_KEY INTO WA_RESULT_SET_KEY.
WA_KEYS = WA_RESULT_SET_KEY-RECORD_IDS.
ENDLOOP.
WA_RESULT_SET_DEFINITION-FIELD_NAME = <Look field name>.
APPEND WA_RESULT_SET_DEFINITION TO IT_RESULT_SET_DEFINITION.
CALL METHOD LR_API->MO_CORE_SERVICE->RETRIEVE
EXPORTING
    IV_OBJECT_TYPE_CODE      = <MDM Main Table>
    IT_RESULT_SET_DEFINITION = IT_RESULT_SET_DEFINITION
    IT_KEYS                  = WA_KEYS
IMPORTING
    ET_RESULT_SET            = IT_RESULT_SET.
LOOP AT IT_RESULT_SET INTO
        WA_RESULT_SET.
*PASS KEYS INTO MAIN TABLE TO GET Structure for FALT or Look up Table
TRY.
      CALL METHOD LR_API->MO_CORE_SERVICE->RETRIEVE_SIMPLE
        EXPORTING
          IV_OBJECT_TYPE_CODE = <MDM Main Table>
          IT_KEYS             = WA_KEYS
        IMPORTING
          ET_DDIC_STRUCTURE =<SAP Strct having all Look up fileds of MDM>
ENDTRY.
LOOP AT <SAP Strct having all Look up fileds of MDM> INTO <Work area>.
    CLEAR WA_KEYS.
    APPEND <Work area>-field name TO WA_KEYS.
    CALL METHOD LR_API->MO_CORE_SERVICE->RETRIEVE_SIMPLE
      EXPORTING
        IV_OBJECT_TYPE_CODE = <MDM Lookup table name>
        IT_KEYS             = WA_KEYS
      IMPORTING
        ET_DDIC_STRUCTURE   = <Single Structure in SAP For Lookup field>.
    READ TABLE <Single Structure in SAP For Lookup field>. INTO <Work Area> INDEX 1.
Here you can get the value of realted lookup fields associated with main table data.
ENDLOOP.
ENDLOOP.
LR_API->MO_ACCESSOR->DISCONNECT( ).
Edited by: Shyam Babu Sah on Nov 24, 2009 4:52 AM

MDM Layout Server ABAP API

Similar Messages

Maybe you are looking for