Partner profile

[Former Member]

Hi,

I am implementing File to Idoc (Vendor master, cremas03) scenario.

In the we20 tx, when i create the inbound parameters for the partner profile, what is the process code that i need to give. what other parameters are mandatory there.

Can I use the existing logical system?

Regards,

Ashish

[Former Member · Accepted solution]

Hi,

<i>In the we20 tx, when i create the inbound parameters for the partner profile, what is the process code that i need to give. what other parameters are mandatory there.</i>

Depends on your BP. your Functional consultant can give you the Process code needed

Can I use the existing logical system?

Yes if you are already using IDoc as mode of communication and have a LS then you can use the same.

Regards

Vijaya

[Former Member]

Hi Ashish,

I have used CREMAS .

cheers,

Prashanth

P.S Please mark helpful answers

[Former Member]

What will be the inbound message type:

CREMAS (vendor master data distribution) or CREFET (Get vendor data)

Regards,

Ashish

Message was edited by:

Ashish Goyal

[agasthuri_doss]

Hi,

I have sent a document to your mail,

It will be helpfull.

Regards

Agasthuri Doss

[Former Member]

Thanks Agasthuri,

Can you also help me with the other doubt???

I am implementing File to Idoc (Vendor master, cremas03) scenario.

In the we20 tx, when i create the inbound parameters for the partner profile, what is the process code that i need to give. what other parameters are mandatory there.

Regards,

Ashish

[agasthuri_doss]

Hi,

Welcome,

I have used- CRE1 Process code, Go to the Table TBD52 you can find it.

Regards

Agasthuri Doss

[Former Member]

When i run the scenario with CRE1 as process code in the partner profile:

the scenario runs properly. There is a checked flag in MONI. But when i run TX: WE05 to check the idoc was posted or not, it shows red button and the following error:

EDI: Partner profile inbound not available

Message no. E0337

<b>Diagnosis

An inbound partner profile could not be found with the following key:

/LOGSYS800/LS//CREMAS////

This involves the key fields of table EDP21:

-SNDPRN partner number of sender

-SNDPRT partner type of sender

-SNDPFC partner function of sender

-MESTYP logical message type

-MESCOD logical message code

-MESFCT logical message function

-TEST test flag

pls advice:</b>

Regards,

ashish

[Former Member]

Hi,

Have you created message type with your IDOC type? It is transactions WE81 and WE82.

Regards,

Wojciech

[Former Member]

Agasthuri could you pls send me the file again at goyal.ashish@siemens.com

Also in the inbound parameter processing, do i need to give the parnter number info of the sender system or the receiver system.

I am implementing File to Idoc scenario.

Regards,

Ashish

[Former Member]

Hi Ashish,

Have you created your Inbound partner profile against the LS: LOGSYS800?

Thats what the error says.

Regards

Vijaya

[Former Member]

Hi Vijaya,

LOGSYS800 is the logical system name of the sender file system.

Now LOGSYS800 was already exixting in the partner profile I just added a new Inbound parameter to it. With Message type 'CREMAS' and Process Code as 'CRE1'

Test check box is marked

Partner function as 'LS'

There is nothing in message code and message function. Is there anything like activating the above or saving it is enough?

Regards,

Ashish

[Former Member]

Hi Wojciech,

Sorry but i didn't get you? why do we have to create a message type of IDOC??

Regards,

Ashish

[agasthuri_doss]

Hi,

Document is sent to goyal.ashish@siemens.com

Regards

Agasthuri Doss

[former_member184619]

Hey i think u r choosing the wrong logical sys. Is it the same u use for File System in SLD.

u need to give the logical sys. name from which u r getting the idoc.

Here u r getting it from file sys. via. XI.

Just have a look at this link.

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6f...

Regards

Sachin

[Former Member]

Hi Ashish,

Partner profile is using message type and each message type is connected to idoc basic type and idoc enhancement in transaction we82. If there is no such entry you can have a problems with inbound IDOCs.

Sample: Basic type Release

DEBMAS DEBMAS06 46D

Regards,

Wojciech

[Former Member]

Hi Sachin and Wojciech,

Yes i have checked we81 and we82 and there are entries of CREMAS in both of them, although I didn't create them they were already there.

Secondly, as i don't have rights to create a new logical system, i was adviced by basis guys to use the existing logical system 'LOGSYSFILE'. <i>I don't know where else this is being used.</i> I just gave the same logical system name to File system business service in ID. (My scenario is File to Idoc)

For the above already created logical sys there was already an outbound parameter present I just added one inbound parameter for cremas as i am sending data from file to idoc only.

There is no sld entry for File system as i am using business service and not business system.

Regards,

Ashish

[former_member184619]

Hi Goyal,

for standard CREMAS IDOC it is CRE1.

also check this blog

/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi

yes u can use existing logical sys.

regards

Sachin

[Former Member]

Hi Ashish,

See these too..

http://help.sap.com/saphelp_erp2005vp/helpdata/en/dc/6b80b543d711d1893e0000e8323c4f/frameset.htm

http://help.sap.com/saphelp_erp2005vp/helpdata/en/71/9bbdde2f66454bb9771170369bae81/frameset.htm

cheers,

Prashanth

[bhavesh_kantilal]

Ashsih,

the process code depends on the Idoc you are going to process. The functional team would be able to help you better, but, if it is a standard idoc, there are standard process codes available for these idocs. Just use the selection screen to select the corresponding process code.

For example , for matmas idoc, the process code is MATM ( or something of this sort) . Most of the process code match with their idoc.

Regards,

Bhavesh