edi : partner profile not available

[rasjoshi]

Hi Gurus,

We have MDM to CRS scenario through PI.... Data is picked from MDM..we got success flag also in SXMB_MONI of PI...but when I check in CRS system using WE02 we see error that profile partner is not available(EDI : partner profile not available)...So I checked Data records, under partner tab I see sender partner number is coming wrong as MD2....

We have created CRSMAT profile using tcode WE20 type LS.... I dont know why it is taking MD2 as sender partner.....

Is this PI issue??? Please provide solution for this.....

[nabendu_sen]

Hi Rashmi,

Either you can manually generate Control Segments in PI by Mapping or you can maintain Partner Profile details in WE20 transaction of target CRS system. I think you are not manually generating this. Check WE20 of CRS, find the sample screenshot.

[rasjoshi]

We have created partner profile in CRS which is CRSMAT...... I checked in Data record inside then i checked in partner tab.... here sender partner number it is taking MD2...it should take CRSMAT... where this MD2 is coming from.....???

[nabendu_sen]

HI Rashmi,

I think your Partner profile is not configured with Correct Partner Type as LS in CRS system. Please cross check.

[rasjoshi]

Can u pls tell me how to check

[nabendu_sen]

Hi Rashmi,

Go to WE20 of CRS, open the Partner Profile and check whether IDoc message type is configured correctly as Inbound. May be IDoc inbound message type is added with MD2, thats why run time its taking wrong value.

http://www.riyaz.net/sap/xipi-settings-in-r3-partner-system-to-receive-idocs/26/

[rasjoshi]

In WE20... created Partner No - CRS100
                             Partner Type - LS

           inbound parameter - message type - zzcrm_transfer...

Wat next i ve to check?

[Former Member]

check logical system name in Business system adapter specific configuration, what you mentioned  there.

[rasjoshi]

Hi rambo,

In system specific adapter config I have logical name of my sender system...........

[MichalKrawczyk]

Hi,

>>>>I dont know why it is taking MD2 as sender partner.....

check IDOC adapter - it can take this from:

a) header mapping - in receiver agreement (or ICO)

b) from the mapping

these are the only two places where this can be set up,

Regards,

Michal Krawczyk 

[rasjoshi]

We are not using header mapping in IDoc communication channel.....

Can u pls tell me how can it come from mapping???