Skip to Content
avatar image
Former Member

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

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

3 Answers

  • avatar image
    Former Member
    Jul 17, 2008 at 06:22 AM

    Hi,

    If you are using SP05, use the corresponding provider class. I think the problem is due to that.

    For MDM5.5 SP05 Patch 1, Server Build 5.5.41.29 - 5.5.41.xx , use CL_MDM_PROVIDER_55_SP05_PL01

    For MDM5.5 SP05 Patch 2, Server Build 5.5.42.30 - 5.5.42.xx, use

    CL_MDM_PROVIDER_55_SP05_PL02.

    Regards,

    Nikhil

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jul 17, 2008 at 07:15 AM

    Hi,

    Please check the last 4 characters of your provider type like PL00 or PL01. This tells you about the patch you are using. If you are using MDM SP06 at patch level 1 (say). Then your provider type for SP06 should be ending with PL01.

    Regards

    Richa

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi,

      As you said, your MDM server Build is 5.5.40.83. and you are using provider class as CL_MDM_PROVIDER_55_42_XX and you think Provider you are using is proper since it is higher build.

      But i strongly feel this is not the case. As per your MDM server build i feel it is SAP MDM 5.5 SP5 Patch 00. so you need to use provider type as CL_MDM_PROVIDER_55_SP05_PL00. it must work.

      Hope it will help you,

      Rewards if Useful....

      Mandeep Saini

  • avatar image
    Former Member
    Jul 17, 2008 at 07:19 AM

    Hi,

    I think this shd be due to patch version mismatch error of MDM server and CL_MDM_Provider .

    Just check.

    Rgds

    Ankit

    Add comment
    10|10000 characters needed characters exceeded