IDOC Partner Profile

Hi Experts,
What is the partner type we use in Partner profile for XI Linkage. I know we use LS for ALE Links.
Thank you
Kris

Please check the following links which explains about the partner type Customer (KU) and Vendor (LI)
http://www.*******************/2009/02/edi-idoc.html
http://www.sap-img.com/sap-sd/partner-determination-for-sales-doc.htm
http://www.sapdb.info/partner-determination-in-sap-sd/

Similar Messages

File -XI-Idoc partner profile error.

Hi All,
Iam trying to post a file to idoc scenario thru xi..when I post the idoc into the r3 system, it gives me an error saying partenr profile not available.
I checked in the r3 system and have created a partner profile for my XI system and also added the idoc chrmas into inbound and outbound parameters in the dev and XI instance there..
please could anyone guide me as to where else should i check for this error.. my idoc is in status 56.
Thanks.

Hello Shabrish,
Thanks for your responce.. I went through all the mentioned steps..
the issue was with the sender port. hence it was giving the exception and the status 56.. its been resolved..
thanks again.

Help on idoc (partner profile)

Hi All
I am facing a weired problem , I am creating Idoc i R3 system and sending it to XI , every thing works fine men suddenly the status of the idon remains 32 by the RSEOUT00 program .
Then I delet the partner profile and creat it again and thnigs turn out to be fine again.
What can be the problem , I can not go on deleting the partner profile each time specially in he production system.
any help is apreciated.
Thanks.

Hi malu,
Make sure there is no other session remains open for triggering the IDOC (with same user id) when you are triggering the IDOC from R3. This could lock the IDOC and hence the it will be get stucked.
Regards,
Sarvesh

IDOC Partner Profile for Sales Orders

What kind of Partner Profile should i create to receive Sales Orders by IDOC from external non-SAP system by RFC?

I created Partner Profile type KU (Customer) with name AAA001.
AAA001 is customer, created in VD01.
Added to inbound parameters:
- Message type - ORDERS
- Process code - ORDE
- Trigger immediately
Testing in WE19:
E1EDK01-RECIPNT_NO = AAA001
E1EDKA1-PARVW = AG, E1EDKA1-PARTN = AAA001
Sales Order is not created.
IDOC has following status:
EDI: Partner profile not available
Message no. E0 332
Diagnosis
A partner profile could not be found with the following key:
     /0000000000/ /
This involves the key fields of the table EDPP1:
-PARNUM partner number
     -PARTYP partner type
Procedure
Please check the EDI partner profiles.
Edited by: S S on Dec 21, 2008 4:51 PM

Posting IDocs, partner profile setting

Hello,
I want to ask for advice.
It happens IDoc hangs on R/3 side while requesting data to load them to BW. This IDoc has no error and after manual processing (BD87) data are transfered correctly and IDoc posted. It is message type : RSRQST and it has set up " Trigger by background program" option in Partner profile / inbound parameters.
What could be the reason that IDocs hang without any error?
Addtionally:
what is recommended as IDoc processing option?
is it : Trigger by background program or trigger immediatelly?
Thank you in advance, Peter

Thank you for fast feedback.
I checked notes 561880 , 555229 and 535172 but they point to issues with resources during IDoc processing to application. I am not quite sure if this is my case. I Think my problem occured before the IDoc processing to appliccation.
I suppose if there is a problem with resources the IDoc gets " status 64, "NO RESOURCES, IMMED. PROCESSING NOT POSSIBLE:
However the problem I am referring to is that IDoc gets "Status 64, No filters , No conversion , No version change . If I understand it right this means that IDoc was processed by ALE and waits for further processing to Application. Unfortunately it doesn't start.
any idea what could be the problem? or does it really have something to do with resources?
Thank you,
Peter

How workflow will be triggered from the Idoc partner profiles

Hi,
We have scenario like, We are doing business with the same vendor in different countries. When ever we receive the Idoc from that vendor, Agent will be notified based on the agent details, which is mentioned in the Inbound partner profiles for that vendor. Now they like to enhance the scenario like different agents should be notified for different countries, based on the company code from the same vendor. I came to know that its possible through workflow, can you please let me know the step by step procedure to achieve this scenario. Since this is very important issue, need your help as soon as possible.
Thanks
Satyasuresh

Hi,
In Tx. WE42, Select the process code for the corresponding partner and bind your workflow / task inplace of the function module with the process code. Now, this will enable the idoc to get placed in the agents(identified by that workflow)inbox.
But to design the workflow, you`ll have to use tx. swdd and prior to that get some basic understanding of Business Workflow from SAP Library.
Hope the info. is helpful and reward points if so.
Regards

No partner profiles (message control) maintained.

Hi Friends,
I have created a PO but getting error message in output type that
No partner profiles (message control) maintained.
Message no. B1127
Diagnosis
No IDOC partner profiles have been created for the message control for for application EF, condition key ZDPO and change message '' with partner type 'LS' and partner role ' '.
Procedure
Please create the partner profiles for the logical system that should contain the IDOC. You can either generate them from the ALE model or create them manually.
Any pointers.
Regards

Hi,
I get the same Error message can someone help?
No partner profiles (message control) maintained
Message no. B1127
Diagnosis
No IDOC partner profiles have been created for the message control for for application EF, condition key ZZVA and change message '' with partner type 'LS' and partner role ' '.
Procedure
Please create the partner profiles for the logical system that should contain the IDOC. You can either generate them from the ALE model or create them manually.
I need to send my PO information to a Logical system.
1) Created new message type ZZBA. Message type triggers automatically but fails.
2) I did create a LS Partner profile (PART123) in WE20
3) In outbound parameters, in partner profile I entered
LS/ORDERS
4) Basic type- ORDERS01
5) In message control i have
EF/ZZBA/ME10
6) Maintained condition record for ZZBA
PO type/ LS/PART123/A/4/EN
please help
Regards
Raj

Partner profile in case of Idoc to File scenario

Hi
I have ECC system and PI system. Scenario as :
ECC will send the Idoc to PI ..PI system will Convert this to flat file and provide it to Legarcy system
I made Partner profile in sending system (ECC) and maintained Message type 'MATMAS' as Outbound.
Do i need to maintained the MATMAS in Partner profile of PI also?.
As PI has copied the Idoc MATMAS.MATMAS05 from ECC.
I am confused please suggest

Hi,
MATMAS05 should be configured as outbound paramters of ECC and no need to configure any thing at PI Partner Profile..
All you need to do is to create the Distribution model as sender (ECC) receiver (PI) and message type as MATMAS05...
with appropraite RFC destination name and port.....
if you are new to distribution model and like to know tcodes for the same just check the below link
http://pavelgk.pbworks.com/Step-by-step-tutorial-for-creating-Idocs#221Creationofanewdistributionmodelview
HTH
Rajesh

Partner Profile in Idoc

Hi ,
I have created a partner profile of type logical system. If i dont specify anything in the inbound parameters and send an idoc to this partner profile then how would the system respond.
Regards
Arun

INBOUND processing the IDOCs are transferred to the interface and stored in te SAP system. The document data is generated in the course of workflow.
In this section the SAP system is made known to the upstream system (startrfc program parameters). Conversele, the upstream system is made known to the SAP System via the port definition.
INBOUND Processing - Create Function Module.
This function module is called when a message type, of the ZINVRV, comes into the receiving system. This needs to be configured. The function module is passed the IDOC as a parameter.
Use the T.code WE19 to test inbound function module in debugging mode.
Use the T.code EW05 to view the IDOCs and their statuses.
Rewards if useful.

Partner Profile not fnd (file-to-idoc)

Hi,
Idoc in r/3 failed with 56 error. Partner profile not found.
partner profile was set up (between XI logical system and R/3 system) in R/3 server.
Control record of idoc is showing sending system as MDMSBX01 with port SAPXI0. Actually, MDMSBX01 is the source sytem(file server). I can't even find this port SAPXI0 in IDX1. Not sure, how this got picked up.
I was testing the scenario by using "test message" in Integration Engine(RWB) since I do not have access to FTP server. I am sure this is causing to pick up wrong source system(instead of XI server system as source). Please clarify.
Below is XML message from MONI.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>100</SAP:MANDT>
<SAP:DOCREL>700</SAP:DOCREL>
<SAP:DOCNUM>0000000000011006</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>CREMAS05</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>CREMAS</SAP:MESTYP>
<SAP:MESCOD />
<SAP:MESFCT />
<SAP:SNDPOR>SAPXI0</SAP:SNDPOR>
<SAP:SNDPRN>MDMSBX01</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC />
<SAP:RCVPOR>SAPEC0</SAP:RCVPOR>
<SAP:RCVPRN>EC0CLNT100</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC />
<SAP:TEST />
<SAP:SERIAL />
<SAP:EXPRSS />
<SAP:STD />
<SAP:STDVRS />
<SAP:STATUS>03</SAP:STATUS>
<SAP:OUTMOD />
<SAP:SNDSAD />
<SAP:SNDLAD />
<SAP:RCVSAD />
<SAP:RCVLAD />
<SAP:STDMES />
<SAP:REFINT />
<SAP:REFGRP />
<SAP:REFMES />
<SAP:CREDAT>2007-04-20</SAP:CREDAT>
<SAP:CRETIM>14:36:52</SAP:CRETIM>
<SAP:ARCKEY>40697C80EF8711DBB286000F203CD31A</SAP:ARCKEY>
</SAP:IDocOutbound>

Hi,
as explained by Ahmad, see the Partner profile os created or not in , R3 system,
At the same time in receiver Idoc adapter select the apply control record from payload checkox .As per moni , the parner profile is in xml, so try to see the partner profile is created in R3 by TcWE21,check for inbound messgae type the said Idoc is existed or not and the corresponding process code is selected or not..
Regards
Chilla

Partner profile to send Idoc to PI 7.4 system from ECC

Dear Experts ,
Do we need a partner profile to send Idoc to PI 7.4 system from ECC.
or Just Port on TRFC is enough ..?
if i need to create a Partner profile ...how to define a logical system and how Assign Logical System to Client... when there is no client for JAVA only PI system ..?
thanks
Shakif

Hi Mohamed,
You need to create a tRFC port on sending ECC system. The RFC destination selected in this port os the one created for IDOC transfer.
Also you need a logical system, use client 000, i.e. PI1CLNT000.
At last you have to create a partner profile to define the IDOC type used.
Best Regards
Harald

Partner Profile for IDOC - configuration

Hi..
I have an inbound IDOC TPSSHT01, which has been extended by adding a Z segment.. But I keep getting an error message.. The IDOC is created with status 56 and the message says "No inbound profile found".. I have configured the Inbound profile to include the message type 'SHIP' in WE20 and also added the message type in WE57 and WE82... Do i need to do any further settings?
Thanks
Rishi

hI,
Please use transaction code WE20 to generate inbound partner profile
Goto WE20 transaction of the client 200 where you are posting the idoc and maintain the partner profile for the inbound type for the idoc type and the corresponding message type of SHIP. This is because you would have maintained it as the outbound parameter from client 100. But at the receiver end also you need to configure the same.
Status 56 comes up when the partner profile for the idoc type is not maintained. Once its maintained, the idocs which you post will go into 53 if its successfully processed and to 51 if its failing due to any inbound processing program validation
*Reward points
Regards

IDocs, INVOIC partner profile configuration

Hi,
I need to receive the INVOIC IDocs from sender system.
Sender(S) system is new system
receiver(R) system is already exisitng system.
I tried to configure the inbound settings in receiver syste. But message type INVOIC, process code INVL, FM all are already available and configured for some ohter systems.
Now if i configure only partner profiles and distribution model, then is it work.
Thanks
Kiran

Kiran,
INOVOIC, INVL, Process codes etc come with the standard system. They can be configured for any partner profile and any sender system.
First, you need to determine the inbound connection. Will the new sender system (S) going to follow the same RFC connection already setup for other sender systems? E.g. Are all the inbound IDOC's flowing through PI or a single EAI system?
If yes, then you just need to setup a new partner profile and use the same port already setup for your existing connections.
If no, then you have to determine how the sender system will connect with SAP. Will they drop files in the SAP's application server? After dropping can they execute the startrfc.exe with required parameters. If they can then you can just proceed with creation of a port to listen that folder (assuming the RFC connection is already setup for that connection) and move ahead with partner profile creation and other mandatory setups. If they cannot trigger the startrfc.exe, then you have to define a new RFC destination (SM59) and a new port (WE21) to read data for this RFC destination. You have to determine when to read the data (e.g. explicit host type etc).

Idoc: BS and Partner profile

Hi Experts
Does the partner profile created in R3 and the business system created in SLD needs to be the same for any idoc scenario. If yes why do we need to do so? and is it applicable for all types in partner profile?
thkx

They do not need to be the same, but it may help with a complex landscape if they are.
The systems are linked via hostname to SLD
A standard naming convention is recomended across the landscape and applied through all connections.

File to IDOC - issue with partner profile

I have done File to IDOC scenario and tested it end to end successfully. For same have done all require configuration setting in R/3 like defining logical System and partner profile. And it sends new IDOC successfully in R/3 with status code 50 (IDoc added).
But when I create new logical system and partner profile in R/3 and when I use same logical system in my above mention scenario then my new generate IDOC in R/3 return status code 56 (EDI: Partner profile inbound not available). But same scenario work fine with my earlier partner profile. Here I have done all require changes at adapter level like adapter specific identification and same new logical system I have update in SLD with my business system Logical System Name.

Hi Bhavesh,
Thanks for your reply.
In control record, I checked with sender and receiver partner. In this sender partner is new partner profile which I have created with port details. Receiver partner has logical system name which I have mentioned in my SLD for my receiver business system. But in receiver partner dont have any port details.
But still it has same problem.
-Sunil

IDOC Partner Profile

Similar Messages

Maybe you are looking for