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

Similar Messages

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

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.

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/

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

Partner profile for INBOUND IDOC

Dear experts,
Need your help to define partner profile for inbound idoc to R/3 system. There is a third party (Non SAP) based application from which idocs need to be sent to the R/3 system. There is no need to send an outbound idoc from the R/3 system. Can some one please suggest what are the steps to be taken to b configure the partner profile in the R/3 system for the inbound idoc?
Thanks,
Priyanka

Hi
This is not the right location to post this question.
You got to post this query in Data transfers section of SDN ABAP Development forums
Now regarding your question,
You need to create a Logical System with the help of the transaction SALE.
Assign the created LS to the client with the help of same transaction
Go to WE20 and create the partner with the same Logical System name
Now..as you are recieving the Inbound Idoc from external Non-SAP System, you need to maintain the message type in the Inbound Parameters by clicking on ADD Icon over there.
Before doing the above step, you got to create the connection between SAP and Non-SAP System.
Use transaction SM59 to do this. Type of connection would be R/3 I guess
Thanks
Hope it helps.

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

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.

Generating partner profile for File to Idoc(CREMAS) scenario.

Dear friend,
Completed all the steps in SLD, IR and ID.
I do not know how to create Partner profile and I skipped this step.
While testing I got the error "Unable to convert sender service to an ALE logical system".
I think i got this error because I have not created partner profile.
Could anybody tell step by step process of creating partner profile including logical system names( Sender and Receiver)?
I have seen many blogs and i couldn't get clear picture on how to generate partner profile.
My sender system is XI server and receiver is R/3.
I have created RFC destination, Port also.
Thanks in Advance
Chiru

generally u create partner profiles using transaction WE20.
SAP Menu -> Tools -> IDoc Interface/ALE -> Administration -> Runtime Settings -> Partner Agreement (WE20).
go through this link for step by steps
http://help.sap.com/saphelp_nw2004s/helpdata/en/dc/6b808e43d711d1893e0000e8323c4f/content.htm
http://www.thespot4sap.com/Articles/SAP_ALE_Configuring.asp

Idoc setup::Partner profile for Logical system

HI All,
I am using Idocs to transmit my invoice details from ECC to PI, but every time I do this for a new customer I have to setup a partner profile for the customer whose invoice is to be sent. I setup the partner profile using WE20, I setup the partner profile for partner type KU(Customer) in the we20,
Is there any way we can setup partner profile for LS(Logical system) in we20 & I don't have to setup partner profile for each & every customer for which Idoc is to be generated.
Please provide some useful information/help to handle this business scenario.
Regards,
Saurav Singh

Hi Saurabh,
Please refer SAP Note 1103146 and check.
Please also refer the below link:-
http://www.sapgeek.net/2011/07/sap-idoc-tutorial-maintain-partner-profile/
Thanks & regards,
Rahul Verulkar

IDoc Receiver, Error in we02 - EDI: Partner profile inbound not available

Hi All,
I have a problem when creating a receiver IDoc from XI to R/3.
I have successfully tested the IDoc when populating the receiver information from the payload. However I want this information to be populated automatically based on the logical systems.
When I do this I get the following error in the IDoc in R/3:
EDI: Partner profile inbound not available
In the control record the sender information is all correct but in the recipient information the partner Number with type LS is populated, but port is not populated.
I have done the following steps.
     the sender is a Business Service so I have created a logical system directly adapter-specific identifiers in the sender service in the integration directory.
     In the receiver business system I have imported the logical system into the adapter-specific identifiers in the ID from that specified in the SLD.
     In the receiving R/3 system using SALE/BD54 I have created a logical system for the source system.
     In the receiving R/3 system using we20 I have created a partner profile of type LS with the same name as the source logical system.
     IN PI/XI system in transaction IDX1 Ive created a port (SAP<SID> where <SID> is the system ID of the receiving R/3 system) and the client of the R/3 system, and the RFC destination of that system (<SID>CLNT<clnt>, as specified in SM59).
     In the IDOC Adapter (receiver) I have entered the RFC destination and port matching those created above. All checkboxes are UN-checked eg. take sender from payload, take receiver from payload, Apply control record values from payload, etc. are all NOT checked.
I think that Ive done everything correctly, but I get the error in we02 in R/3: EDI: Partner profile inbound not available.
Any help will be greatly appreciated (and rewarded, obviously).
Thanks,
Matt.

HI Matt,
Can you please copy paste the exact error message....In your error message it will show you Exact partner Number / Logical System name and other parameters...just compared if you have all parameters set in your partner profile comparing to error message...
If you can giev screen shot of both..then probably would be easy to point out error.
Hope this will help.
Nilesh

Inbound Idoc processing issues - Partner Profiles - error status 56

Hello All,
I'm having a little difficulty posting an idoc coming from MDM. It's a CREMDM04 xml coming from an MDM system. It is getting mapped through PI and is being split into ADRMAS02 and CREMAS04 Idocs. The message is being passed through XI and being posted to the ECC system, but certain fields in the EDI_DC40 header table are not being populated correctly (i believe). I'm using nothing but standard mapping/material from the SAP Business Content for XI. After looking through the standard XSLTs i cannot find the field-to-field mapping where the fields below are being populated.
The RCVPOR value (SAP[SID]) is correct when i view it in SOAP Header, but does not appear in the remote system under the receiver port for the inbound idoc.
The RCVPRN value ([String Value]) is incorrect in the SOAP Header and does appear in the remote system under the receiver partner number for the inbound idoc. How is the RCVPRN value being populated?
SOAP Header in IDocOutbound tag
<SAP:RCVPOR>SAP[SID]</SAP:RCVPOR>
<SAP:RCVPRN>[String Value]</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
I've been trying to trace down the string value for the RCVPRN, but i cannot find it anywhere. Perhaps i'm just overlooking it?
When i set the proper values (port = SAP<SIDofECC> and partner number = <LSnameof ECC>) using WE19 in the remote system then the partner profile is found and i'm left with different error to please specify an address group.
Any help is very much appreciated! :-D

Hi Jason ,
Just check out if you have done the following steps most of us make minor mistake here ....... I think this would solve your problem
To Configure the IDOC SCENARIOS ,PROCEED AS FOLLOWS
STEP 1:ALE SETTINGS TO POST IDOC INTO SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Receiving System in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a) Select Create New button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client
d) Enter the RFC Destination created in XI towards R/3
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) Create an RFC Destination to XI in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Inbound Parameters (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Inbound Parameters.So click on ADD TO Create Inbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Message Type and Process Code.
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
do let me know if it helped
Edited by: Tom Jose on Feb 21, 2008 9:04 AM

ALE partner profile setup for diff. IDOC extension

Hi,
We have three extensions of IDOC type HRMD_A06 and message type HRMD_A. In one of the extensions segment IT0002 is extended.
In the partner profile extension is not specified. Due to this when the IDOC is generated Custom segment is not getting picked up.
I pu the extension in the partner profile then it woks fine.
But I do not want disturb the existing profile setup. Is there any option in WE20 where we can define two profiles with one message type, basic type and different extensions.
Also if we define the custom message type then distribution model and the partner profile needs to be generated for the new custom message type.
Appriciate quick response.
Regards,
Sonali

Hi,
just check the FM 'BAPI_BUPA_CENTRAL_GETDETAIL'.
Or just search for oher FMs with BAPI_BUPA*.
Hope this helps...
vasanth

Issue in Partner Profile config for Outbound IDOC

Hi Experts,
I have requirement like, When ever there will be any change in a Sales Order an Outbound IDOC will get triggered though a output type. This IDOC will save a file in the Application Server.
The Message Type i am using is ORDERS and the Basic Type is ORDERS05.
I have created a Partner Profile also a Receiver Port of type FILE.
I have Assigned Message type in Outbound Parameters.
I have assigned Receiver Port and Basic type under "Outbound Option".
I have Assigned Applications as 'V', Message type as 'Output Type' and Process Code under "Message Control".
When i am changing any Sales Order no IDOC is getting Triggered. I checked the Sales Order>Extras> Output> Header> Edit, the Output type is in Status RED with Message " No Partner Profiles (Message Control) Maintained".
Please guide me if i have missed any configs.
Help me solving this issue.
Thanks in Advance!
Priyabrata

Hi Priyabrata,
please try changing in your partner profile the application from V to V1. Another problem that's often causing the partner profile not to be found are the partner functions that are added automatically by SAP, but sometimes forgotten in the partner profile.
I don't have a SAP system at the moment, but as far as I remember the long text of the message indicates the partner profile parameters that SAP uses for the lookup.
If all of this doesn't help, I'd quickly debug this and see why SAP's not picking up the correct partner profile.
Cheers, harald

Help on idoc (partner profile)

Similar Messages

Maybe you are looking for