cancel
Showing results for 
Search instead for 
Did you mean: 

Type conflict Error while activating service

Former Member
0 Kudos

Hi All,

I'm facing type conflict error while activating service , which was created using SEGW T.code.

But the services which are created via code based where working fine .

Please find the attached screen shot.

Please suggest is there any note needs to implement.

Regards,

Lokeswar.

Tags edited by: Jitendra Kansal

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

The issue got resolved by implementing the below .

Note : 2006602.

Thanks lot for your valuable suggestions.

Answers (2)

Answers (2)

srinivasan_vinayagam
Active Contributor
0 Kudos

Hi Lokesh,

Apply the correction:

1933505 - Dump in transaction /IWFND/MAINT_SERVICE (service activation)

Regards,

V Srinivasan

Former Member
0 Kudos

Hi Srinivasan,

I have implemented the note 1933505 , but still i'm facing the same issue .

Please suggest

srinivasan_vinayagam
Active Contributor
0 Kudos

Hi Lokeshwar,

paste your error log and detailed screen, above screen was partial.

Regards,

V Srinivasan

Former Member
0 Kudos

Hi Srinivasan,

After implementing the note , i'm facing the below error which is in detail in error log.

..ERROR_INFOThe function call of /IWBEP/FM_MGW_MED_LOAD failed; a field may have been assigned to the parameter ES_MSG_CONTAINER_H whose typ

AshwinDutt
Active Contributor
0 Kudos

Hello Lokesh,

Please check the below ->

In this check the note suggested by Krishna ( http://service.sap.com/sap/support/notes/1637045 )

Regards,

Ashwin

Former Member
0 Kudos

Hi Ashwin,

the below are the errors which im facing :

1. when executing the get entity set URL :

the function call of /IWBEP/FM_MGW_READ ENTITYSET failed; a field may have been assigned to the parameter ES_MSG_CONTAINER_H who.

2. when executing just service URL like metadata URL :

the function call of /IWBEP/FM_MGW_MED_LOAD failed; a field may have been assigned to the parameter ES_MSG_CONTAINER_H whose type

Please suggest.

kammaje_cis
Active Contributor
0 Kudos

This is most probably due to SP level mismatch between BEP and FND layer. May be you can post the SP levels of these components here.

Former Member
0 Kudos

Hi Krishna,

The SP level's are as below :

Gateway system :

IW_BEP - SP level - 0008

IW_FND - SP level - 0007

GW_CORE - SP level - 0007

SAP ECC system :

IW_BEP - SP level - 0009

Please suggest..,

Regards,

Lokeswar .