Partner Profile vanishes in BW system

Hi All,
We are facing a recurring issue which happens in BW QA system after we refresh is from the BW production system.
After about a week or so after the refresh, the data loads halt in the BW QA system and the BW team gets an error "EDI partner profile not available".
After i checked, i found that the logical system name entry for the EDW QA system (i.e. self system entry) is missing from the table EDPP1 and also from transaction WE20.
I re-created it in WE20 and the entry automatically got created in EDPP1 table.
My question is : I suspect that some job or application program is deleting this entry. We checked the background jobs but no luck.
How do i resolve this error. The client has come up with this question and he wants an answer as to why this
entry is being automatically.
Can you please help?
Regards,
Hari Kishan

Hi,
See the following SAP Notes:
SAP Note 886102 - System Landscape Copy for SAP NetWeaver BW
SAP Note 325470 - Activities after client copy in BW source systems
SAP Note 325525 - Copying and renaming systems in a BW environment
SAP Note 886102 - System Landscape Copy for SAP NetWeaver BW
SAP Note 1333302 - Special procedure for BW system copy
SAP Note 996238 - Dump 'RFC connection error' after BW system copy
Search for PDF in SDN
How Tou2026System Copy in SAP Business Intelligence System Landscapes
Thanks
Reddy

Similar Messages

Partner profile value for XI system

I got a outbound message with partner profile value as
<SAP:SNDPOR>XIDEV</SAP:SNDPOR>
<SAP:SNDPRN>XiALE01</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
Where do I go and change the SNDPRN value in SLD? or is it SLD I change it. SAP R3 is looking for sender partner profile in caps. How to change this value in XI
thanks

Hi,
Please update few things.
1. Since it is an outbound from XI into another R/3 machine, I would first suggest you to check IDOC posted in R/3 which has an error message tagged to it. This is applicable only when Message went from XI into R/3 and we see an error in the SXMB_MONI as RFC destination not found etc.,.
In such a case, IDOC error message with 53/51 etc, will post an error message like "SENDER NOT IDENTIFIED". This SENDER and RECEIVERs can be seen in the CONTROL RECORD of the IDOC.
From R/3, use transaction WE02/WE05 and locate your IDOC (normally in the OUTBOUND folder on left, look at last few messages which have RED TRAFFIC SIGNAL and match the partners).
To resolve this, create the RFC PORT first. XIDEV using WE21 referring to your XI client. The prerequisite for this is to have a RFC destination already created to port XI and a logical system (BD54 transaction).
Create a Logical System (Business Partner) of type LS using WE20 and (Logical system you have created or identified in BD54) should be configured as you want.
This should resolve your issue.
2. If the issue is with XI and message is not seen in R/3, make sure you have assigned proper logical system in the SLD for your technical landscape. If this is pointing to a different logical system, then probaboy you may want to change to suitable logical system.
Suggest you to look for the definitions using SM59 and IDX1 in R/3.
Hope this answers, please let us know your findings.
Thanks,
Srini.

Can I transport partner profile settings frm one system to other?

hello,
is it poosible that whatever partner profile settings i have maintained in development server that i can trasport into production server?
or i have to maintain it manually?

Hi,
Usually you have to maintain manually the partner profile in production system due to security and data integrity purposes.
For example, you don't want to send any testing data to your partners (vendor, customer, etc) and you want to make sure the interfaces (inbound and outbound) work properly and free errors.
Having said that you can distribute and generate partner profile (BD64) from DEV to QA without using transport system. Please ensure RFC connection are setup properly for DEV and QA systems prior to distribute.
Regards,
Ferry Lianto

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

Using SYPART01 IDOC for setting partner profiles from external system

We wish to maintain our partner profiles from an external system.
Is there any existing interface for doing this.
It seems that the sypart message is only for output, not input.
Any ideas or suggestions?
Thanks!
Dan

Hello Dan,
Thanks for your post.
I hope the following code helps in future.
http://wiki.sdn.sap.com/wiki/display/Snippets/Copy+partner+profiles+with+SYPART+message+quickly.

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.

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).

Partner Profile creation

Hi
I have an idoc-xi-file scenario. For this I want to create partner profile(of partner type LS) in ECC system using we20.
When I entered partner no. as DX1CLNT100 and saved (after filling all the information) it is throwing the error saying
"The partner number 'DX1CLNT100' does not exist for the partner type LS".
If it won't exist how to make it available ??
thanks
kumar

Hi,
You need to have the Logical system available for this, - BD54
SAP Network Blog: Configuration steps required for posting idoc's(XI)
Configuration steps required for posting idoc's(XI)
A Step-by-Step Guide on IDoc-to-File Using Business Service in the Exchange Infrastructure Integration Directory
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
These are the required steps for IDoc to File scenario...
In R3 (i.e., your IDES system)...
RFC dest to XI (sm59) - any name
Logical system (bd54) - any name
Port to XI (we21) - any name
Partner profile for the logical system (we20) - use Logical system name created in bd54
In XI...
RFC dest to R3 (sm59) -
Port to R3 (idx1) -
create metadata for the idoc (idx2)
In sld...
create business system for R3 with Logical system name as r3 sys.
In we19
and give in control record as
Sender : Port ; Partner
Receiver : Port = <Port created in WE21> ; Partner = <Partner created in we20>
see the below links
ALE configuration for pushing idocs from SAP to XI
Introduction to IDoc-XI-File scenario and complete walk through for starters.
idoc settings Configuration steps required for posting idoc's(XI)
Also
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
IDOc testing - Generate Test Case for an IDOC Scenario
Thanks
Swarup
Edited by: Swarup Sawant on Sep 8, 2008 3:53 PM

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

Just one partner profile for SAP XI?!

Hi,
well i have some thoughts concerning configuring the partner profile on sender side.
I have different systems to which e.g. IDocs will be send to. Therefore i was thinking to set one partner profile for each connected system.
But on the other hand it is also possible to just configure one partner profile, e.g. called SAP XI, and seperate the different IDocs inside this partner profile because of different Message-Types of the Outb-parameters, and inside this because of the IDoc-Type.
So what is the most propriate way to solve this, is there a suggestion by SAP?!
thx in advance, Jens

Hey guys,
Just thought I'd add my experiences here.
In one of our implementations we created partner profiles with respect to XI. We had multiple source systems , but the Target ECC team was like, we do not care who sends the data to XI, as far as we are concerned we get data from XI. So we create only one partner profile. We agreed to this and so all Idoc's posting from XI had the XI as the sender partner name. The project went into production and things were fine.
Then comes the next release. And what do we realise, that the same Idoc will not be posted from XI but for different source systems with different formats. The Inbound processing for the idoc was also being changed stating that Idoc from Source system A needs to be processed with this T code and Idoc's from System B with this code. reason was different bsuiness rules across different geographies.
Now, at this juncture we realised in vain that it would have been better had we maintained the partner profiles with respect to the End Systems . having it with respect to XI caused issues in the fact that we are unableto trace out which Idoc belonged to which system.
Since, then we always recommend all partner profiles with respect to End Systems and not with respect to XI. Helps the business also understand how many idoc's were posted for which source system and so on.
Just my 2 cents and experience here. Would love to heard more on this topic as well.
Regards
Bhavesh

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.

Process code & Partner Profile Issue

Hi Experts ,
Hi ,
I need to configure partner profile with a external system . I will be receiving customer data from the ext System .
I though of using msg type DEBMAS and msg type
and process code DEBM. I see its uses function module IDOC_INPUT_DEBITOR.
So what exactly this function module does ?
I was wandering if I need to create new Process code / Function Module .
My requirement is receiving the customer data along with address , shipping informations , customer no . So that when I drop orders its becomes available.
Thanks
MM_sD

Hi ,
Check all the settings needed for an R/3 - XI- R/3 scenario..... In ur case R/3 to XI is working fine and u have to check the XI-R/3 side.
Check the RFC destination ( Both in XI and in R/3)
Check the logical system name
PORT, Partner profile .....
Regards,
Jude

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 profiles in PI

Hello all,
I am doing a File to Idoc Scenario. I have done almost all the configutations and now a bit confused about the partner profiles. What are they for and where they are used? Should I create the partner profiles both for the sender (third party) and the receiver systems (ECC) on the receiver system (ECC)? or Should I create just for the Sender system?
Please help.
Thank you.
Ramesh.

Hi
1. You must have a partner profile to communicate with a partner using the IDOC interface. This will provide the parameters for electronic interchange of data with Trading partner in SAP
2. Partner profile should be created at receiver system for sender system to receive the IDOC this is called Outbound partner profle
http://help.sap.com/saphelp_nw04/helpdata/en/2d/f371e4d24a11d289810000e8216438/frameset.htm
3. You can send partner profiles to the receiving systems if you are sending IDOC
http://help.sap.com/saphelp_nw04/helpdata/en/2d/f371e4d24a11d289810000e8216438/frameset.htm
Useful document
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
Thanks
Gaurav

Need a Clarification in defining a Partner Profile

Hi Experts,
I have a requirment wherein i need to send delivery idoc delvry01 for all the deliveries created for a shipping point.
I have created a output type ZLD0 and has Shipping point as the access seq. I have maintained condition records for the shipping point to create idocs for.
I have created partner profile with the logical system. But its not working.
Is there anyway to trigger idoc on the delivery document by not defining each and every customer on the partner profile.
i mean to say in this case how to create the partner profile, is it with logical system or Customer number. if it is with customer number, if i have 1000 customers, creating 1000 Partner profiles is doesn't make sensce...
Please clarify this...
Thanks in Advance
Narendra.

I haven't done this for deliveries but we did something similar for the Purchase Orders, so maybe this will give you some food for thought.
We defined one Logical System per Purchasing Organization. Unfortunately, the PO output could not have been assigned to the 'logical system' partner type. So what we ended up doing - we created a new outout type ZNEU (copy of standard NEU) and set up access sequence Doc.Type / Purch. Org. / Vendor. Then in MN04 for this option we added a record for each Purchasing Org (EKORG) and all the applicable Vendor Numbers. It is pain in the back but it's much faster than creating individual profiles.
Now when I look at the PO output there is a line with ZNEU and vendor # as a partner but when I run RSEOUT00 I get an IDoc for the whole Purchasing Org.
So replace Purch. Org with Shippint point and Vendor with Customer and it's pretty much your scenario. I'm not sure what's the SD transaction similar to MN04, try VV31.
Good luck!

Partner Profile vanishes in BW system

Similar Messages

Maybe you are looking for