ABAP API MDM vs Standard MDM !!!

Maybe the expression that I am using is not the best one and hope that someone can give me any clarifications.
What I am intending is to know:
1)     If using ABAP API is the best way to implement MDM purposes or if hes an alternative to implement MDM using ABAP API?
2)     In the proof of concept that I am implementing, I only use the principal components of MDM (Import, Data Manager, Syndicator and Console) in order to find the solution of our enterprise business.
3)     Using ABAP API, I have to use programming method, implement by myself some functionalities in ABAP to connect and resolve my MDM purposes.
4)     If am not using ABAP API (The way that I am proceeding right now) , I have to use the standard software component (enterprises services ) of the R3 Systems in order to connect MDM with client systems.
Thanks guy for your assistance. We just want to know the best way to proceed with MDM .

The best method for implementing MDM depends on the requirements of each scenario. For example, if you have a program in R/3 that needs to pull some data from MDM for analysis then perhaps using the ABAP API would be the best route to take. If you need to transfer materials or vendors from MDM to various R/3 systems, perhaps using XI would be the best route to take. I would recommend looking at the <a href="https://websmp106.sap-ag.de/~sapidb/011000358700004656452006E">IT Scenario Configuration Guide</a> to get a better understanding of SAP's recommended practices given different scenarios

Similar Messages

ABAP API for MDM work flow

Hi SDN,
I need some information related to ABAP API for MDM workflow. I did search in SDN and I found one solution in a thered posted on Jul-2008.
ABAP API - MDM Workflow execute
My dought is: Do we have any ABAP API for call MDM work flow. Please provide me the solution ASAP. Apprciate for your immediate response.
Regards,
Kumar.

Hi LAKSHMAN ,
To answer your question specifically
Using ABAP api you cannot call MDM workflows as of mdm 5.5 there are no functions specific to calling MDM workflows in ABAP.If you want to implement workflows on ABAP side you need to go for SAP ECC workflows which is a different topic than MDM>
To call MDM workflows over the Java stack ie WAS (SAP portal),You have 2 ways
- UWL
- Guided Procedures.
- UWL is a way of calling MDM workflows on EP.Wherein the workflow design will be done in MDM and it will only be called in portal using appropiate connections and configurations.
You can refer the below links to know more on them:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/771f1a61-0e01-0010-daa9-93a52905da09 (uwl)
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a3461636-0301-0010-3787-978f5ac8bd45 (UWL config)
- GP is a way where by you need to design the entire workflow on SAP portal the logic can be pertaining to MDM but the design is completely on portal using webdynpros and api.
You can refer the below links to know more on them:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/92811997-0d01-0010-9584-f7d535177831 (Guided procedures)
Enterprise Master Data Management (EP Guided)
To know more on ABAP api and its provider classes you can refer the below:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/601ddb01-e5c8-2910-d981-b190b51fca44 (abap api webinar)
Re: Abap api error (Abap api provider classes Forum)
Hope It Helped
Thanks & Regards
Simona Pinto

MDM ABAP API.

Hi All,
We have installed MDMTECH_554_700 on our 2004s.
We also configured all post installation steps like
1)MDM Repositories
2)MDM Server Connections
3)Mdm Dbms Hosts
4)ABAP Implementation for MDM Version Support
5)MDM API Trace Configuration.
It seems all connection settings are fine.Is there anyway to test the connection properties/configuration?
We tried to execute MDM_ADMIN_RETRIEVE_ALL_REPS with
1) MDM Connection which we created in the above configuration steps.(i.e..,MDMTECH_554_700)
We are getting like "Error in repository configuration: MDMTECH_554_700 not found"
Please help us.

You actually named your logical object name, MDMTECH_554_700? The logical object name that the function module is looking for is actually the key name that you supplied in transaction MDMAPIC when you setup your MDM Repository.
Also to use MDM_ADMIN_RETRIEVE_ALL_REPS, you also want to supply the DBMS information as well since you want cross repository information.
Actually the function module that I use to test MDM API ABAP connections is MDM_ADMIN_RETRIEVE_USERS. It has a simplier interface, in that you only have to specify the logical object name.
If you have any problems determining what the logical object name refers to, feel free to send me an email (it is in my SDN business card and also not too difficult to figure out standard SAP addresses). If you email me some screen shots of you configuration in MDMAPIC, I can tell you what value you should be using.

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

Locking options in MDM ABAP API

Hi,
In our project, we have a BSP application screen, through which the end-users create/modify material master data and post it in MDM, through MDM ABAP APIs.
If one user is editing material data, through our BSP screen, related to a particular material, if the same material is being tried for editing by another user, we would like to ensure, that the 2nd user gets the appropriate locking message like it happens in standard SAP application. To achieve the above scenario, what are the options available in MDM to lock the material record through MDM ABAP APIs?
Also, we would like to know, if we u201CCheck Outu201D or u201CProtectu201D a material record, and the user gets disconnected or logs off abruptly, how would that record become u201Cfreeu201D / u201Cunlockedu201D again?
Thanks in Advance,
Neethu

i am not sure on what u are exactly trying ... but to make it simple - if u are trying to access the MDM ABAP APIs from the SRM ABAP env. - its very much possible.
thanks
-Adrivit

MDM ABAP API Performance Problems

Hi all,
we developed a custom transaction into our ECC 6.0 system to remotely retreive data coming from MDM (7.1 SP05) and show them to the user. The 2 systems phisically reside in different datacenters, so running in the same WAN but in 2 different AD domains and 2 different ip networks.
In short the transaction is working using the standard MDM ABAP API functionalities and getting the MDM data using the following methods:
      CALL METHOD lr_api->mo_accessor->connect
      CALL METHOD lr_api->mo_core_service->query
      CALL METHOD lr_api->mo_core_service->retrieve
      CALL METHOD lr_api->mo_accessor->disconnect.
This is working, but with awful performances. for example to get a subset of materials (around 500 codes) it takes more than 1 minute, and the quantity of data transfered from MDM to ECC (around 30 KB) is not justifying this time.
Please be so kind to suggest any kind of activity that I can perform to improve the situation.
Thanks in advance.

I am trying to retreieve date from MDM to ECC using ABAP API.I am getting the below dump.
Short text
    An exception occurred that was not caught.
What happened?
    The exception 'CX_MDM_PROVIDER' was raised, but it was not
     along
    the call hierarchy.
    Since exceptions represent error situations and this error
    adequately responded to, the running ABAP program
     'CL_MDM_PROVIDER_71_SP00_PL00==CP' has to be
    terminated.
What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can loo
    at and manage termination messages, and you can also
    keep them for a long time.
Error analysis
    An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_MDM_PROVIDER', was not caught in
procedure "GET_LOC_SUPP" "(METHOD)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
Internal error: field 'SEARCH_GROUPS' not found; contact your system
administrator
Please check at this point I am getting dump:
LT_SEARCH_TUPLE_PATH
    Table IT_1806[0x12]
    \CLASS=CL_MDM_PROVIDER_71_SP00_PL00\METHOD=IF_MDM_CORE_SERVICES~QUERY\DATA=LT_SEARCH_TUPLE_PAT
    Table reference: 1612
    TABH+ 0(20) = 000000000000000007000000579D710000000000
    TABH+ 20(20) = 0000064C0000070E000000000000000CFFFFFFFF
    TABH+ 40(16) = 04000138000F44A0000424E403000000
    store        = 0x0000000000000000
    ext1         = 0x07000000579D7100
    shmId        = 0     (0x00000000)
    id           = 1612 (0x0000064C)
    label        = 1806 (0x0000070E)
    fill         = 0     (0x00000000)
    leng         = 12    (0x0000000C)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000300
    occu         = 4     (0x00000004)
    accKind      = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniNo)
    keyKind      = 1     (default)
    cmpMode      = 12    (ILLEGAL)
    occu0        = 1
    stMode       = 0
    groupCntl    = 0
    rfc          = 0
    unShareable = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId = 0
    isUsed       = 1
    isCtfyAble   = 1
    hasScndKeys = 0
    hasRowId     = 0
    scndKeysOutdated = 0
    scndUniKeysOutdated = 0
LV_MESS
    field 'SEARCH_GROUPS' not found
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    6666622544544545455522667266766222222222222222222222222222222222222222222222222222222222222222
    695C407351238F72F50370EF406F5E4000000000000000000000000000000000000000000000000000000000000000
SY-REPID
I am picking the data from MAIN TABLE MDM_SUPPLIER_MAP and below is the code.
CALL METHOD lv_mdm_api->mo_core_service->query
      EXPORTING
*Main Table
      iv_object_type_code = 'MDM_SUPPLIER_MAP'               "#EC NOTEXT
*      it_query = lt_query
      IMPORTING
      et_result_set = lt_result_set.
Please suggest solution to get the records from MDM to ECC.
When I am tring to replace the abpove with the below code it is working.But in this case I need to retreive all the data instead of using DO and ENDO.Could any please suggest solution.
DO 10 TIMES.
APPEND sy-index TO keys.
ENDDO.
CALL METHOD lv_mdm_api->mo_core_service->retrieve_simple
EXPORTING
iv_object_type_code = 'MDM_SUPPLIER_MAP'
it_keys = keys
IMPORTING
et_ddic_structure = result_ddic

How could JAVA API and ABAP API useful to MDM.

Hi Experts,
How could JAVA API and ABAP API useful to MDM, and any coding in Java or ABAP is required in MDM.

Hi Reema,
Java API and ABAP API are verry usefull to MDM to integrate MDM with other SAP componants like SAP R\3, EP etc. :
It dose not required any coding in MDM infact in JAVA API coding can be done on NWDS(Netweaver Developer Studio).And for ABAP API coding is done on SAP R\3 System in ABAP editor.
JAVA API:
By using Java API MDM client operations can be performed.For one need to install NWDS and to deploy some .jar files and with the help of standard classes and interfaces it can be connected to MDM server and various operations like create repository ,connect to repository ,Data mainuplation etc.
ABAP API:
Suppose you have an Expert abaper and you want him to perform MDM operations.In that case he need not to learn MDM basic Data types infact by doing some settings on R\3 and MDM server side an ABAPer can perform
MDM Cnsole and MDM Data Manager level operations.
you can go through these links
http://help.sap.com/javadocs/MDM/SP06/overview-summary.html
/people/bv.pillai/blog/2006/11/28/installing-mdmtech-add-on-and-configuring-the-mdm4a-mdm-for-abap-api
Here the coding is done on SAP R\3 system.
hope it will give you some idea about Java API and ABAP API
Reward if helpful
Thanks ,
Vinay Yadav

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

Retrieving hierarchy fields from MDM to SAP R/3 using MDM ABAP API's

Hi all,
I have developed a code to retrieve fields from MDM to SAP R/3 using MDM ABAP API's, i could retrieve all of the fields excluding the Lookup[Hierarchy] fields like- FACILITY CODE etc...
please update me if anyone has any experience on this.
Thanks and regards,
Aastha Mehrotra

Hi ,
Any one worked in the MDM API to retrieve Hierarchy fields ???
Regards,
Arun.

ABAP API to store DATE value in MDM 5.5

Hello All,
Currently I am working on MDM 5.5 and need to have some suggestions on ABAP API Function module to store date values in MDM.
We have interface from where we take the user input which updates the field value back in the MDM.
On the basis of similar scenario we have "DATE" field on the interface which will update the date and time in MDM, also we are making use of ABAP API for development.
The problem is that data type mismatch is happening between MDM and ABAP API,please let me know which ABAP API Function module should we use which simply accepts the DATE and TIME for every single record.
Source code provided will be much more appreciable.
Regards,
Swapnil

Hi Swapnil.
In the same link provided by Sudhanshu, can you navigate to the node "Retrieving Complex Types".
It has sample codes and MDM interfaces for TimeStamp, Time Stamp, User Stamp, Literal Date, Literal Time etc.
As suggested, you can also try to use the type MDM_CDT_DATE_TIME.
See the sample code provided in the link as below:
Type: MDM Literal date:
    CLEAR lv_date.
    CONVERT TIME STAMP ls_result_ddic_ex-fieldliteraldate-content TIME ZONE sy-zonlo INTO DATE lv_date.
    WRITE: AT (10) lv_date, '|'.
Type: MDM Literal time:
    CLEAR lv_time.
    CONVERT TIME STAMP ls_result_ddic_ex-fieldliteraltime-content TIME ZONE sy-zonlo INTO TIME lv_time.
    WRITE: AT (10) lv_time, '|'.
Regards
Bala

MDM ABAP API - Language information not valid for repository

Dear all,
We're programming an interface in SAP R/3 to MDM catalog through 'MDM ABAP API's'. Automatically, it creates an RFC connection to MMD, but we're getting the following connection errorwhen executing the API:
E MDM_ABAP_API 078 Language information ENG US USA not valid for MDM repository XXXYYYZZZ*.
*where XXXYYYZZZ is the repository name.
W'e've established the connection in R/3 through transaction MDMAPIC and we've created the same user in R/3 and MDM Console.
This is the code written on the program where we are defining the language (ENG), country (US) and region (USA).
*maintain logon language information
ls_repository_language-language = 'ENG'.
ls_repository_language-country = 'US'.
**no region information needed here
ls_repository_language-region = 'USA'.
How can I see the repository language definition?
Which are the correct codes to be used for language 'English', Country 'United States' and Region 'USA'? And for other countries, like spanish language, country Spain and Region ¿spain?
In fact, we copied this code from website:
http://help.sap.com/saphelp_nwmdm71/helpdata/en/44/93ad8931381053e10000000a422035/frameset.htm
Maybe the problem is that any RFC configuration is missing, and it has to be done in transaction SM59?
Thanks for your feecback,
Carlos Santamaría.

The problem is now solved.
The correct languague information codes for Language Spanish, Country Spain and Region, are as follows:
Language: 'spa'
Country: 'ES'
Region: '___'
It is important to respect the CAPS, otherwise it doesn't work.
Regards,
Carlos Santamaría.

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'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.

MDM ABAP API AND BUSINESS WORKFLOWS...

Hi All,
In the following vedio blog, SAP saying SAP buisiness workflows & MDM ABAP API combination for certain scenarios.
http://www.sdn.sap.com/irj/scn/shop?rid=/media/uuid/40923f37-3483-2c10-5b87-967a607fa3b2
Anyone implemented this approach?

Hi.
you can utilize example program provide by SAP, follow this path which may help you
http://help.sap.com/saphelp_nwmdm71/helpdata/en/47/5fd3f2cbd75518e10000000a421138/frameset.htm
Thanks,
Jignesh Patel

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

ABAP API MDM vs Standard MDM !!!

Similar Messages

Maybe you are looking for