Partner profile activation

hi,
basis team did some work(replacing logical system of r/3 dev system) and i checked whether bw objects configuration is fine. i'm unable to see datasources in datasource level of rsa1, but able to see in infoprovider(data flow) level of rsa1,eventhough i replicated datasources meta data. i tested on bw dev system whether full update or delta updates are working or not. i'm getting same error message: partner profile not active. after error analysis given by system: xxx(parner number) entry, check edpp1(parmer profile) table'(partner number & partner type). Checked particular entry xxx partner profile is inactive status. how to make partner profile active? can basis or abaper do this work?
regards,
V N

Hi,
Tell the BASIS team to maintain the EDI partner profile. They can do this work.
Cheers,
Kedar

Similar Messages

"no active plan version exists" while adding system in partner profile

Hi,
i am getting "no active plan version exists" while adding logical system in partner profile. while duble click on this it showing "set active plan version".
Can anyone answer me how to do the set active plan version. I asked my functional team and they didnt know how to set it.
Thanks,
Gowthaman.

Thanks Sonia,
in OOAP i could not able to edit so i maintained plan version in OOPV and in sm30 in table T77S0 maintained PLOGI group.
Now i am getting different error while creating partner profile in we20..
*Object type US, ID CENTRALADMIN unknown (please observe upper/lower case)*
    *Message no. E0624*
*Diagnosis*
    *Object CENTRALADMIN of type US is not known in the system.*
*Procedure*
    *Enter a valid object and check the type.*
    *Make sure upper case and lower case are used correctly.*

EDI: Partner Profile not active

Hi
I have a Delivery and a message that should create an IDOC.Whenever i call that message for my delivery ,i get this error:
EDI: Partner Profile not active
I checked to see in the table EDDP1 and the status is set to active.I also checked using the transaction WE20 and my partner was active there too,what can be the problem?
thanks

hi,
If your Receiver Business System is suppose BS_ECC, check in SLD what Logical system is maintained for BS_ECC. If for example Logical system for BS_ECC is ZLOG900 then check in ECC if in WE20 partner ZLOG900 exists or not. For ZLOG900 maintained inbound parameter for Idoc you are receiving in ECC like MATMAS.
Check the parameters accordingly in your system.
Reg,
NJ

Will idoc be generate to a particular partner if the partner profile is in in active?

Hi ,
I have a quetion for IDoc communication in SAP.
Will idoc be generate to a particular partner if the partner profile is in in active?
Please help to my doubt..
Thank you,
Yogesh.

Hi Yogesh,
IDOC will be triggered for active partners which are configured in partner profile. Please check the below wiki
Connection Settings between ECC and PI system - Process Integration - SCN Wiki
regards,
Harish

Getting EDI:Partner profile not available.

Hi,
I am a newbie to SAP XI. As I am doing File to IDOC scenario, I am getting error - EDI:Partner profile not available.
My Scenario details:
1. Created RFC Destination, RFC port, logical System and Partner profile in both Sender (XI) as well as Receiver(SAP R/3) systems.
2. Created SWCV, Technical sys, Business Systems in SLD. I used the Logical system created (for SAP R/3) on XI system in my business system.
3. Created Data type, Message type, Message interface, Message Mapping and Interface mapping in Integration Repository and activated them.
4. Imported IDOC from SAP r/3 system during Namespace creation and used it for mapping.
5. used Integration Directory wizard to create Communication channels, Sender & Receiver agreements, Receiver Determination, Interface Determination.
6. Creaed a new business service for sender and added "Adapter Specific Identifier with Logical system created (for SAP R/3) on SAP XI.
7. Activated all Standard Change list items.
The file for the above Scenario has been picked up amd i am getting "Chequered Flag" on both ends in "SXMB_MONI" monitor. When i change over to SAP R/3 to check idocs created (i.e., T.code - we05) my scenario idoc status is 56 and it says.. Status; Idoc with errors added.
I have gone through many of the forum suggestions and blogs regarding this issue, but still not able to resolve my problem.
can somebody suggest me solution please.
Thanks,
Vijay.

Hi,
6. Creaed a new business service for sender and added "Adapter Specific Identifier with Logical system created (for SAP R/3) on SAP XI.
>>>Check this for Reciever Business System.. not for Sender system..
BTW, if you get chequered flag in XI, then idoc data is sent from XI. Can you check all the data from XI is populated in the idoc structure in SAP R/3 in we05...by clicking each segment.. if so, then there is no problem from XI..
check WE20 ..partner profile configuration in R/3 also check inbound parameters are given
Regards,
Moorthy

Partner no and partner profile

Hi,
Where i have to config partner no in SAP.
While i am config. partner profile in WE20 system is asking Partner no.
Please guide me
Sateesh Kumar

Hi,
Thanks for every one.
My scenario is: Client is asking sending the payment advices through IDoc.
For that i configured
1) partner and partner profile.
2) Activated House Bank for EDI and Data medium exchange
3) Created partenr profiles for 1 vendor and 1 customer
4) Assigned partner profiles for House Bank also.
Still i have to do any configuration settings?
Please guide me with complete info.
Sateesh

Partner Profile disappeared

Hi
I was trying to extract data from APO system to within APO BW system. It was running fine for many months. One day, it suddenly failed. The error analysis says Partner profile not active. When Checked in WE20, the Logical system name is missing.
I dont know how that could happen. My BASIS says they can't help with that, as no one can trace, who created/ deleted.
They say something triggers automatically by some action.
So any idea, how this could happen, and how to fix it ? As I just can't make an entry, as it does not allow me to add message type.
Thanks for any help..
Venkat

see if this can help you or the basis team
http://help.sap.com/SAPHELP_470/helpdata/EN/52/16adef543311d1891c0000e8322f96/content.htm
Partner Profile not maintained - WE19

Workflow not routing to agent specified in partner profile

have included below notes regarding the mis-routing of workflow messages of "translation error" STATUS message idocs that are uploaded into R/3.
The testing that I have been performing has been in Development System. The first thing that I check is that the Partner profile parameters are set to send the STATUS message type idoc to an agent via t-code we20. This agent does exist in the organization structure found at t-code ppome. I have been using the logical system (partner type LS) user=GEIS, inbound parameter message type=STATUS, message variant=AP, where myself is setup as the agent to receive workflow.
When processing an inbound STATUS idoc containing an error code of "05", meaning that translation failed on the outbound corresponding idoc (e.g. invoice, desadv, etc.) in the EC subsystem, workflow should be triggered and route the message to the agent specified at the message type level of the partner profile. In the event that an agent is not configured at the message type level of the partner profile, then the workflow message should be routed to the agent specified at the partner profile global level. However, in the event that an agent is not specified at the message type level or partner profile global level, then the workflow message should be routed to the IDOC Administrator, which is configured in t-code we46.
The results of my testing has been that regardless of the agent configuration set at the message type level or partner profile global level, all workflow messages are routed to the IDOC Administrator configured in we46.
The request is to have development work completed so that error STATUS idocs can trigger workflow messages that will be routed to various agents for resolution, versus workflow messages being routed just to the IDOC Administrator - which is how it is working today.
I would greatly appreciate for your immediate response.
Regards,
Shankar

Hi Stacey
If DEV is working and PRD is not have you gone through and compared both and ensure latest MSMP configuration in PRD has been activated?
Also, is the approver COCHGG00 also the Role Owner?
Are you able to show you MSMP configuration? It's makes sense to analyse the log in the context of your configuration. E.g. does the Z_ADDTNL_ACCESS_PATH path have two stages: Manager and Role Owner of which there is a routing rule on the Manager approval to go to the NO_ROLE_OWNER path where the business role has no role owner?
Regards
Colleen

Task properties - General task - Partner profile

Hi Experts,
I'm using user decision step for manager approval, and in development server i've selected task as general task in task properties and everything was working fine in development server.
When above workflow development transported to testing server, the task properties are not transported. So, agent assignment is de-activated. And when i'm trying to set general task attribute in task properties, its saying "Entry in outbound table not found" error message. Can anyone help me in resolving this.
Entry in outbound table not found
Message no. E0400
Diagnosis
No partner profile (outbound parameter) could be found using the following key:
DC1CLNT10/LS//HRMD_ABA///
This refers to the key fields in table EDP13:
RCVPRN Partner number
RCVPRT Partner type
RCVPFC Partner function
MESTYP Logical message
MESTYP Message code
MESCOD Message function
TEST Test indicator
Thanks in advance,
Siva Sankar.

Hi Siva,
I have always found that I need to go make change the agent assignment on custom tasks to 'General' as the workflows get transported - or you can investigate here:
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/d00a1cb4-913c-2c10-d991-caf663ab9b16&overridelayout=true
As Jocelyn Dart has said:
Folks, This is an oldie but a goodie.
You need to execute program RHMOVE30 to add your General Task settings to Transports.
Enter your task numbers (you can enter a workflow and use eval path TASK_HIER to pick up all sub tasks) Select the Transport checkbox
On the second screen
Select all and press Add to Transport
Select all again and press Transport/Delete
You should get a message confirming they have been added to your change request.
You will see infotype 1217 entries on your transport request.
However your issue seems to be a different one. I searched and it looks as though you need to check partner profiles using WE20? Have you tried this?
Hope this helps,
Sue

EDI partner profile not maintained.

I am currently working on BI 7 and on trying to install ODS from BC its giving me error that
EDI partner Profile is not maintained.
Can somebody please send me the documents on how to maintain EDI partner profile for transferring data from ODS to Infocube.

Hi Amit,
EDI partner profile is maintained using Tcode WE20.
YOu need to select LS (Logical System ) and your Source System.
And maintain Inbound and Outbound parameters here.
Check OSS Note 886102 - System Landscape Copy for SAP BW 2.X, 3.X and NW2004s BI
Step 6.8: Reactivate all partner profiles that carry the new logical system name after renaming
Execute Transaction WE20 to reactivate the partner profiles. Choose "Partner type LS (logical system)" enter the logical system name of the partner in tab "classification", change the partner status from "I" (inactive) to "A" (active) and save.
Hope this Solves your problem
Thanks
Ck

Regarding partner profile

HI all
i am configuring an outbound partner profile for an outbound IDOC ,when i try to give the post processing:permitted agent,here i am getting this message NO ACTIVE PLAN VERSION EXISTS.
CAN ANYBODY HELP ME ON THIS
regards
kish

Hi,
Go trough this
2 Introduction
Configuring IDoc adapter in Exchange Infrastructure 3.0 requires some configuration on the SAP
systems, for both XI and the backend system where the IDoc message is to be sent. These steps, although
simple, are many times missed or mis-configured, causing the delivery of messages to fail.
Since IDoc adapter uses the ABAP stack, instead of J2EE, the configuration requirements are mainly in
ABAP.
Setting up IDoc adapters requires the XI integration server to be able to communicate with the backend
SAP system, and also to make sure that the Logical System Name used when posting IDoc exists on the
backend SAP system.
3 The Step By Step Solution
The basic steps for the IDoc configuration are outline below:
1. Configure SM59 on XI to communicate to SAP backend system.
2. Configure port on XI for IDoc communication.
3. Create or verify the Logical System Name on the SAP backend system.
4. Create or verify business system in XIs System Landscape Directory.
5. Verify the Logical System Name of the business system.
6. Verify or add the Logical System Name for the sender business system.
7. Create/configure the Communication Channel for the IDoc receiver adapter
3.1 Configure SM59 on XI to communicate to SAP backend system.
1. Using transaction SM59, create an RFC destination with Connection Type = 3.
In this example, the RFC destination name is NDVCLNT510.
2. Enter the logon information:
3. Test the connection by clicking on Testing connection and Remote logon.
Both must be successful.
3.2 Configure port on XI for IDoc communication.
4. Go to transaction IDX1 on XI, and create a port. In this example, the Port name is SAPNDV.
 The Port name must be in the form of SAPxxx, where xxx is the system ID of the backend SAP
system.
 The Client must be the client number of the backend SAP system.
 Select the RFC Destination which was created in the previous step.
3.3 Create or verify the Logical System Name on the SAP backend system.
5. Enter transaction SALE on the SAP backend system.
6. Create or verify the Logical System Name. In our example, NDVCLNT510 is verified.
3.4 Create or verify business system in XIs System Landscape Directory.
The business system name for the SAP backend system must contain a valid Logical System Name. This Logical System Name is the one verified or created in the previous step.
7. In the System Landscape Directory, select the SAP backend business system. If one does not exist, then create the business system. Verify the Logical System Name.
3.5 Verify the Logical System Name of the business system.
8. In the Integration Directory, doubleclick on the business system (in our example, it is NDVCLNT510).
Navigate the menu:
Service Adapter Specific Identifiers.
If information is empty or incorrect, then it will have to be synchronized with the content of the System Landscape Directory. Follow the steps below for synchronization.
9. (Optional) Synchronization of the business system in Integration Directory to the business system in System
Landscape Directory.
 Double-click on the business system in the Integration Directory.
 Switch to Edit mode.
 Select menu: Service Adapter-Specific Identifiers
10. (Optional) Within the dialog box, click on the button as indicated below to resynchronize.
11. (Optional) If the expected data from the System Landscape Directory is not updated, then the SLD cache may need to be cleared first.
3.7 Create/configure the Communication Channel for the IDoc receiver adapter.
15. In the Integration Directory, create an IDoc receiver communication channel.
 The RFC Destination is from step 3.1.
 The Port is from step 3.2.
NOTE:
There is no need to create an IDoc sender Communication Channel for XI. Instead, the backend SAP system must be configure to send the IDoc to XI.
4 Appendix
Transaction: IDX2
There are a couple of situation where IDX2 can be useful on the XI system.
1. When we want to test connection between the XI and SAP backend system.
2. When an IDoc has changed, and the meta data stored in XI needs to be update. When an IDoc is sent from the SAP backend system to XI, XI will first check to see if the meta data for the IDoc is already in its persistent cache. If not, then XI will use the configuration in IDX1 to retrieve the IDoc meta data from the backend system. If the
meta is already in cache, then it will NOT do so. Therefore, when an IDoc has changed, it is necessary to manually update the new meta data on XI, or delete it from the cache, so that the latest version can be retrieved. IDX2 is used for this purpose.
Go to transaction IDX2 and click on Create.
Enter the IDoc Type and the Source Port as defined in step #2. Click Continue.If successful, the following will show up. If error occurs, then the IDX1 configurations will need to be re-checked.
Regards
Hemant
award points if find helpful

Error: EDI partner profile not available

Hi all,
We just installed CRM and BW servers and trying to integrate them. After creating CRM Source system in BW, during Activation its giving following errors:
1. No Partner Profile (outbound parameter) could be found using the following key: /CLNT001/LS//RSSEND////This refers to the key fields in table EDP13: (RCVPRN, RCVPRT, RCVPFC, MESTYP, MESCOD,TEST)
2. No Partner Profile (outbound parameter) could be found using the following key: /CLNT001/LS//RSINFO////This refers to the key fields in table EDP13: (RCVPRN, RCVPRT, RCVPFC, MESTYP, MESCOD,TEST)
3. No Inbound Partner Profile could be found with the following key: /CLNT001/LS//RSRQST//// Key consists of following fields (SNDPRN, SNPPRT, SNDPFC, MESTYP, MESCOD, MESFCT, TEST)
4. A Partner Profile could not be found with the following key: /CLNT001/LS/, This involves the key fields of table EDPP1 (PARNUM, PARTYP)
Please let me know how to resolve these errors. I'm unable to solve these as i've very little experience with both CRM and BW.
Thanks & Regards,
Vikas Sharma

Hi Vikas,
Please check your partner profilesin the transaction WE20. Check if there is a TRFC port connected to your client system in transaction WE21. If not maintained, you will have to ask basis team to maintain these settings. If they are maintained, check your trfc connectivity in SM59.
Thanks and Regards
Subray Hegde

Error: "EDI: Partner profile inbound not available"

Hi All,
iam getting the following error while loading the FI related data.
"EDI: Partner profile inbound not available"
Suggestions are appreciated.
thanks
Kiran

Hi,
Refer the link:
Re: EDI: Partner profile not active
With rgdS,
Anil Kumar Sharma .P

Partner Profiles deleted after TDMS copyback

Recently we had a copyback activity using TDMS 4.0 for ECC system. After the copyback, we noticed that partner profiles has been deleted. One of our pre-steps is to delete the largest tables then delete the client(SCC5) and recreate a shell client. Would like to ask if how we could prevent the deletion of partner profiles during copyback? Or atleast, is there a way we could automate the configuration and return to previous state before the copyback this partner profiles? We're not sure other configurations being deleted during copyback.
Hope for your reply. Thanks in advance...

Hi Philip,
There are many based on your landscape few examples below which i generally use
As Mentioned By Anitha , you can very much do this using TDMS itself , exclude these tables from copying.
#SCC4
T000
#OSS1
EWOSS
#RFCs
RFCDES
RFCDOC
RFCSYSACL
RFCATTRIB
RFCCHECK
RFCDESSECU
RFCTRUST
RFCCMC
RFCGO
#RSA1 Transport conversion
RSLOGSYSMAP
#Transport Number
E070L
#SAP License
SAPLIKEY
#Access Keys
ADIRACCESS
DEVACCESS
#Logon Group
RZLLITAB
#Transport
TMSCROUTE
#BD54
TBDLS
TBDLST

Partner profile agent

Hello
Someone has changed the agent name in the partner profile(LS)
Can i track who made these changes?
Thanks and Regards
Manu

Hi,
The LS details would be updated in table EDPP1. To check for the logs or history, go to transaction SCU3 (evaluation of change logs) and check the logs for these tables by providing this table name, date duration and select the "Tables" radio button under the criteria "Evaluation for". You would be able to view the user who created or changed or deleted the partner profile along with the message type and the date of change made.
This could be possible only if the table logs is activated.
~Bineah.

Partner profile activation

Similar Messages

Maybe you are looking for