Abap api error

Hi All
I am trying to use abap api to fetch data from MDM and I am using the provider class for SP06 for MDM 5.5 SP05 installation .
I get the below dump  when I execute my program.
" Protocol header 0108000000010000 has invalid signature"
on debugging I found that the program dumps at the place where the method INIT_SOCKET gets called.
Kindly someone help me resolve this error.
awaiting for reply
Regards

Hi everybody,
I guess this list will help most:
API Provider:>>>>>>>>>>>>>>>>>>>>>  MDM Server Version:>>>>>>Name on marketplace:
CL_MDM_PROVIDER_55_SP05_PL00 >> 5.5.40.79 - 5.5.40.xx >>>>>> MDM_TECH_555
CL_MDM_PROVIDER_55_SP05_PL01 >> 5.5.41.29 - 5.5.41.xx >>>>>> MDM_TECH_555: patch 01
CL_MDM_PROVIDER_55_SP05_PL02 >> 5.5.42.30 - 5.5.42.xx >>>>>> MDM_TECH_555: patch 02
CL_MDM_PROVIDER_55_SP06_PL00 >> 5.5.60.59 - 5.5.60.xx >>>>>> MDM_TECH_555: patch 03
CL_MDM_PROVIDER_55_SP06_PL01 >> 5.5.61.43 - 5.5.61.xx >>>>>> MDM_TECH_555: patch 04
CL_MDM_PROVIDER_55_SP06_PL02 >> 5.5.62.29 - 5.5.62.xx >>>>>> MDM_TECH_555: patch 05
Thanks for rewards.
Regards
  Andreas

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

  • MDM_TECH 554_700 ABAP API giving socket connection error

    Hi,
    I have recently installed the MDM_TECH 554_700 on a 64Bit R/3 system and configured the ABAP API thru customization for a 32Bit MDM Server. Currently I am facing a problem with 'NiRaw2ConnectError: Connection refused' error and when I checked the detailed log it shows that "ERROR => mdeKernelError, NiRawToConnectError: The attempt to establish a socket connection caused an error (rc=-10) [mdm_mdeClien 265]". I have checked the necessary kernel files ( dw_mdm.dll) to make the socket connection between the MDM system, the OSS note 965209 & 950245 and not able to trace the problem. Is it possible to make the connection between 64Bit R/3 and 32Bit MDM server? Help on this issue is highly appreciated.
    Regards,
    Velu

    Alejandro,
    The MDM ABAP API & MDM Server Versions are same. Both of them are in SP04. Here is the details on the versions:
    MDM ABAP API - MDM SP04 provider, Server build  5.5.32.48  -  5.5.32.x
    MDM Server 5.5 - SP04  ( 5.5.32.65)
    Regards,
    Velu

  • ABAP API'S - CONFIGURATION ERROR

    Hi All,
    I am curently working on ABAP API's. While configuring the connection between the ECC and MDM in Transaction- MDMAPIC,
    If  the MDM server HOST name and the DBMS HOST name are exactly same, Will the configuration work?
    Helpful answer will be rewarded points..
    Thanks and regards
    Nitin jain

    Hi Nitin,
    If MDM host and the DBMS host server names are same then it wont matter because in the background the they are mainly connected with the IP address.
    Note: Have u entered the Ecc host name in the MDM server host file.
    You can find it at the following location or just enter  in Start -->> Run -->> drivers
    C:\WINNT\system32\drivers\etc\host
    Open host file in notepad and make an entry of IP Address and host name.
    This host file contains the mappings of IP addresses to host names. Each entry should be kept on an individual line. The IP address should be placed in the first column followed by the corresponding host name.
    The IP address and the host name should be separated by at least one space.
    Hope dis helps u
    Regards Tejas........

  • 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 Connection Problem

    Hi folks,
    I am working with the MDM ABAP API and there are some errors that do not make any sense to me.
    Here is a list with the technical information:
    MDM 5.5 SP 5 (5.5.40.83)
    SAP NetWeaver 2004s (700)
    MDM API 555/700
    I have set up the Repository information in MDMAPIC, using a new created provider of the type CL_MDM_PROVIDER_55_SP05_PL00 ( MDM5.5  SP05 Patch 0, Server Build  5.5.40.79  -  5.5.40.xx ).
    I then have tried to establish the connection to the server and repository and so on according to the HowTo Guides.
    When I finished yesterday, I managed to connect to my local MDM Server and to retrieve the names of the mounted repositories, but I was not able to retrieve records from a certain repository. When I wanted to solve that problem today, I was not able to connect to my MDM server anymore. There have been no changes in the coding or the configuration since then, only the MDM server has been restarted and the repository has been reloaded. But apart from that, nothing has changed but still I am not able to establish the connection anymore ( Connection refused ). Then I have tried to connect to another MDM server, but there I get another error ( Connection is not trusted ), although I have rechecked a dozen times that there is the allow.ip with the proper ID of my SAP system and the according user in the MDM repository.
    From time to time, the errors change without changing anything else, just by trying to execute it a couple of times. I have figured out, that sometimes I get an error out of the above mentioned provider class ( CL_MDM_PROVIDER_55_SP05_PL00 ). Is it possible, that the MDM API is not working properly with the PL00?
    Hints are appreciated a lot...!
    Thanks and best regards,
    Sabine

    Hi,
    Check whether the server is down or not. If the server is down, u will get the same error message
    regards,
    Nikhil

  • 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

    Hi All,
        I am working on a scenario where I need to use abap api to fetch data from mdm system.
      Here have coded to fetch data from mdm system and done the required configurations in mdmapic transaction.  but I get a dump.
    It says "BSEI_MSG_BADCRC" error.
    Kindly someone help me resolve this error.
    I have done mdmapic configuration to use the provider class of sp06 . I also used the provider class of sp05 .both give the same error.
    The build of SAPMDM is 5.5.40.83 and the provider class of spo5 in mdmapic has a build 5.5.42.79 .should the provider system have the same build .  I also checked for add on with that build in service market place. It was not available.
    Regards
    Sudheendra

    Hi,
    I strongly feel it comes just because of Version Mis-matching. Your MDM Server and Provider Class shold be of same Version. as CRC always indicates Version Mismatching.
    E.g. For MDM server version 5.5 SP6 patch1 then install MDM_Tech 5.5.5_640:patch004 or MDM_Tech 5.5.5_700:patch004 as per your R/3 system release.
    you could check it using HowTo_07. pdf , on executing this report you could know connection to your MDM Server is estabilishing Properly or not. here in this report you have to change one Parameter logical object name which you have given in transaction MDMAPIC
    you could find more Add-on patch on Service Market Place while searching in Searching for All Categories. here search using MDM_TECH
    Hope it will Help you,
    Rewards if useful....
    Mandeep Saini

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

  • ABAP API For SP06?

    Hi
    We are trying to integrate MDM (5.5 SP06 Patch 3) with an ECC 6.0 server. We downloaded the MDM TECHNOLOGY 5.5.5.7.00 CAR file from service market  place. It was installed successfully in the ECC 6.0 server. But we are unable to find the relevant ABAP component for our MDM version in the "ABAP implementation for MDM version support" of the mdmapic transaction. The components in that table are the ones for SP04 and SP05 but not SP06.
    Has anyone successfully used ABAP APIs in their SP06 environment? If yes, then what was the CAR file that was used?
    Thanks.
    Regards
    Swarna

    Hi Kanstantsin
    In the begininng we had downloaded from the same path you have mentioned.
    After raising OSS note SAP responded by saying that - the installations should be downloaded from the path:
    Download ->
    Support Packages and Patches ->
    Support Packages and Patches - Entry by Application Group ->
    SAP NetWeaver ->
    SAP MDM ->
    SAP MDM 5.5 ->
    Entry by Component ->
    ABAP API for NW 7.0
    After doing that we are able to see the SP06 components.
    But now when i try the sample code in the ABAP API How to guide,  for creating a repository through API, i'm getting an error -
    "Server return code 0X84020003: DCNI_MSG_ErrInitDB"
    I verified the ip (same for server host and dbms host), port (20005), dbms username/password. They all seem to be fine.
    Has anyone faced this issue before?
    Thanks
    Swarna

  • MDM ABAP API - Retrieval of Qualified Flat lookup fields

    Hi,
    I am having trouble retrieving the records using MDM ABAP API when the fields that are being retrieved includes a Qualified Flat lookup field. An exception is being thrown with the error message <b>Value with type id 0 is not supported</b>. I don't see any problem when I am trying to retrieve other fields of types String or Real. The type of the Qualified Flat lookup field is set to MDM_QUALIFIED_LINK_TABLE as per the How to guides given by SAP. Any ideas on why the exception is occuring?
    Thanks
    Suman

    Hi Suman,
    Please check if the How to guide (#13) in SMP -operations is of help https://websmp204.sap-ag.de/nw04operation
    Regards,
    Anita

  • 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

  • MDM ABAP APIs

    Hi All,
    After creating Repository on MDM Server Using MDM ABAP APIs, when i call MDM_Accessor_connnect function module to connect the Repository i am geeting Error: Server Return Code 0XFFAA0201 :User not found. Even i have created same Identical user name with Password who has logged onto the R/3 System as suggested in HowTo_02.pdf
    Assure Points will be awarded if problem solves.
    Am i missing any settings please suggest.
    Regards,
    Mandy

    Hi Mandy,
    Give the user name which is same as R/3 system in Capital letter. Dont give any password .
    Regards,
    Nikhil

Maybe you are looking for