Partner profile tables.

Hi,
We need to add new vendors to the partner profile tables. The user has given us the vendor number, agent code and company code.
Which are the tables we need to update?
Thanks in advance.
Mick

Hi,
For your information, the data are stored in the following tables -
KNVK - Customer Master Contact Partner
KNVP - Customer Master Partner Functions
Hope this helps!

Similar Messages

Partner Profile Table

Does anyone know what table(s) contain the partner profile info. F1 and technical info on the WE20 partner number field points to a view that appears to be incorrect.
Thanks Nic

hi nic,
check in the table EDPP1.. for part no
check in the table TEDST...for partner type
regards,
venkat.
Edited by: venkat appikonda on Mar 18, 2008 8:55 PM

How can we transport the partner profiles and Port configurations

Hi everybody,
How can we transport the partner profiles and Port configurations. While creating these , system will not ask for Dev class and we cant assign any Transport request number. Then How can we transport these settings?
Your replies are really apreciable.
Thanks and Regards,
Vijay.

Hi,
please have a look of the OSS note: 182172
>>
The partner profiles are stored in the following tables:
Table EDPP1: General partner profile
Table EDP12: Partner profile outbound, additional data NAST
Table EDP13: Partner profile outbound
Table EDP21: Partner profile inbound
Table EDIPHONE: Connection to SAP telephony (optional)
You can use R3TR TABU to manually set the tables into a Customizing request (as of Release 46, into a SYST-type request).
<<
Rgd
Frédéric

Master tables of Partner Profile (WE20)

Hello Experts,
Kindly guide me on which are the backend tables for all the parameters maintained in Partner Profile.
Basically, i would want to capture all data pertaining to a patner no e.g: partner no. type, function, agent, i/b & o/b parameters etc...
Thanks in advance,
Elizabeth.

Hi Elizabeth,
Check this please
Partner Number : VEDI_TDPP1-PARNUM
Partner Type : VEDI_TDPP1-PARTYP
Partner class: VEDI_TDPP1-CLASS
Agent: VEDI_TDPP1-USRKEY
The table VEDI_TDPP1 is the main componenet of the fields used in the transaction.
I hope your query resolves.
Have a best day ahead.
Edited by: Srivastava.G on Aug 6, 2009 7:46 AM

Error while creating Partner Profile

Hi.
While generating the Partner profile for the distribution model
The following error is coming :
Outbound parameters for message type CREMAS CREMAS04 could not be created
Please enter a valid value for the output mode
Outbound parameters for message type SYNCH SYNCHRON could not be created
Please enter a valid value for the output mode.
Furher while processing the Idoc its giving the error 'Entry not found in outbound table'.
Kindly help in resolving the error.
Thank u in advance.
Pranali.

Hello Prashant,
You are missing some configuration for the partner function;
Go- to
SPRO>IMG>QM>Quality Notifications>Notification Creation>Partners>Define partner Determination Procedure>
Again Select "Define Partner Determination Procedure".
Select Quality management> Change Partner
Now Select Q2.
Compare settings with Partner Determination Procedure on any other client. Also check Partner functions on the same screen.
Amol.

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

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

Partner Profile and its configuration.

Hi all,
I am creating an SD IDoc using EDI and send it between two servers.
I need to know what is a partner profile and why should we create it.
what are the steps to be followed in maintaining a partner profile and its configuration.
Any pointers will be highly apppreciated.
Thanks in advance,
Regards,
Jose
Edited by: Jose Anthony Reddy on Dec 17, 2007 11:23 PM

Hi Jose,
Below is a material you can go through .
Creating an Outbound Partner Profile
Here you must enter the data manually. Alternatively, you can also transfer the default values from Customizing.
If you are not yet on the change screen of your desired partner, choose SAP Menu ® Tools ® IDoc Interface/ALE ® Administration ® Runtime Settings ® Partner Agreement (WE20).
1. Position the mouse on your partner in the required partner type node. Choose in the Outbound Parameter table.
Key Fields
2. You have already determined partner number and partner type in general partner processing. The partner function from the master data defines the addressee, that is, it is used for further classification purposes. If you have selected outbound processing under Message Control (MC), the function must be identical to the corresponding Message Control field. Otherwise, it is optional.
Partner A (customer 1110) wants to order a material from partner B (vendor 1014). Partner B is of the partner type LI (vendor) and must choose the Message Control value VD (vendor) as the partner function because orders must always be processed using Message Control.
3. Specify the business process with the logical message, within which the IDoc type is used. The logical message is described by three parameters: The message type is based on EDIFACT message types: For example, a purchase order is of type ORDERS. You can further divide the message type with the optional fields message code and message function.
4. Configure the test indicator if you want to send the message as a test.
Message, partner and test indicator are the seven key fields of the outbound partner profiles (the client comes in addition to these). Also see the graphic at the end of this section.
Other Fields
5. In the Outbound options tab page, you can determine whether IDocs are forwarded immediately to the receiving system. You should ensure that your entries are compatible with the Message Control priorities, if you have chosen outbound processing under Message Control. A list of recommended combinations is provided in the section Outbound Processing Under MC: Procedure.
6. You have already defined the Recipient port in Port definition.
7. If a port of type TRFC is used, the Queue Processing field is visible. You can use the indicator to specify whether IDocs are to be sent with qRFC. This sending technique is only possible for recipient SAP systems as of SAP Web AS 6.20.
You should only set this flag if it is really necessary that the IDocs sent are received in the receiving system in the same sequence as they were sent by the sender system. Queuing can cause posting delays in the receiving system, because an IDoc in the queue cannot be posted. In this case, the following IDocs in the queue cannot be posted until the error is resolved.
8. If you have set the Queue Processing indicator, the Rule Name field, which you must then also maintain, appears as well. The rule name defines the rules for queue names. You can specify these rules in the transaction qRFC IDoc Queue Name Rules (WE85).
9. Specify the IDoc type as the Basic type with or without extension. If you want to use a view of your IDoc type (for example, to improve the performance), specify this here.
The figure below shows the m-to-n relationship between logical messages (business meaning) and IDoc types (technical format). Message 1, for example, is always assigned to one IDoc type, while message 3 is assigned to two IDoc types. IDoc type 2, in turn, is also assigned to 2 logical messages.
10. The segment release specifies the release from which the segment definitions (not the IDoc type definition) originates. We recommend that you leave this field blank so that the most recent segment definition is used.
11. You can propose an EDI standard, version and EDI message type for the receiving system in the tab page EDI Standard. Most subsystems, however, should be able to determine these EDI settings themselves (from the logical message).
12. You can define permitted agents for cases in which exceptions occur. This entry overrides the entry in the general partner profiles. Depending on the message, therefore, the exception can be handled by different agents of the same partner.
13. You can specify whether syntax errors are to be ignored or are to lead to a processing error (Cancel Processing flag under syntax check in the tab page outbound options). For more information about exception handling and permitted agents, refer to the following section: Exception Handling
14. If your hardware supports it, create partner and message specific telephony data for outbound IDocs. For more information, see General Partner Profile.
Graphic: Outbound partner profile fields (general)
Key fields are shown in gray. The values for partner, message and test indicator (and client) therefore provide a unique ID for the IDoc type in outbound processing.
Regards,
Praveen

"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.*

Partner Profile Configuration(Outbound Enteries)

Hi,
I was trying to make a business partner with the BP Role Master Tenant with Customer Account. At the time of saving I got following error:
Entry in Outbound Table not found
Message No E0400
No partner profile(Outbound) could be foundusing following key
B3TCLNT800/LS//HRMD_ABA///
This refers to 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
Please check EDI profiles.
And it directed me to transaction code WE20.
Could you please help me in making the desired settings and explain why this needs to be done.
Regards,
Lata

Hi,
I guess either you are using CRM or Flexible Real Estate Management.
Pl confirm the exact transaction code you are using. Are you using BAPI ?
For creating the Partner profile,
Go to WE20,
Click on Create button.
Give the Partner Number, Give Partner Type as " LS"
User type- US
Agent - Your User ID
Give the Message types in the Outbound/ inbound parameters.
Pl reply for further clarifications
Thanks
Siva

Partner Profile Problem

In checking my partner profiles on WE20 I'm finding some issues
On the BW system looking at my ECC system I see:
    Partner profile XYZSE3010/LS
      Header entry (table EDPP1)
      Correct partner status
      Recipient of notifications exists
      Entries for outbound processing (table EDP13)
      Entry XYZSE3010/LS/ /RSRQST /
      *No Message Control entry for this entry*
      Port exists
      Basic type exists
      Link exists between logical message and IDoc type
      Recipient of notifications exists
      Entries for inbound processing (table EDP21)
      Entry XYZSE3010/LS/ /RSINFO /
      Process code (inbound) exists
      Recipient of notifications exists
      Entry XYZSE3010/LS/ /RSSEND /
      Process code (inbound) exists
      Recipient of notifications exists
On the ECC system looking at my BW system I see:
      Partner profile XYZSB2010/LS
      Header entry (table EDPP1)
      Correct partner status
      Recipient of notifications exists
      Entries for outbound processing (table EDP13)
      Entry XYZSB2010/LS/ /RSINFO /
      *No Message Control entry for this entry*
      Port exists
      Basic type exists
      Link exists between logical message and IDoc type
      Recipient of notifications exists
      Entry XYZSB2010/LS/ /RSSEND /
      *No Message Control entry for this entry*
      Port exists
      Basic type exists
      Link exists between logical message and IDoc type
      Recipient of notifications exists
      Entries for inbound processing (table EDP21)
      Entry XYZSB2010/LS/ /RSRQST /
      Process code (inbound) exists
      Recipient of notifications exists
So I see the Message Control Tab, but I have no idea what should go there.
Any help is appreciated.
MIke

Hi,
Check in SDN you have good Document on this
"Setting-Up a Connection between BW and R/3 for Data Load "
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0751ba5-b7a8-2b10-6d97-e91e85c0fafa
https://www.sdn.sap.com/irj/scn/articles-bi-all?startindex=21
Thannks
Reddy

Inbound EDI multiple customers using 1 partner profile

I would think that it's possible to set up a single partner profile in WE20 through which you can process multiple idocs against multiple customers for order processing. Can anyone guide me on how to achieve this.
Thanks, Mart

Absolutely. You could have an EDI Partner called 'GENERIC' for example, and could use that to process inbound EDI Sales Orders. Obviously you would need an identifier to represent the correct Customer account, ideally this would be the Sold-to number. If it's not your Internal Sold-to, but another unique number, then you should be able to add mapping via transaction VOE4 to table EDPAR. I.e the Customers sends an external number 123 representing their Store Id, you map that back to your internal Customer Number. Only trouble with this is if two different Customers had the same external Id, as you would have no control over that. For our generic EDI Partners, the Customer Number is mandatory.
Cheers, Paul.

Invoice EDI error : EDI: Partner profile inbound not available

Hi EDI experts ,
We are connecting our SAP ECC 6 ( Ehp 4) system to 3rd party system Mincom via SAP PI, to send PO Creation message (Outbound) and receive Vendor Invoice message( inbound). We already done all the settings..Output determination procedure, Partner Profile ( WE20) , Port creation , Condition Records, EDI settings in SPRO for invoice..etc as below:
Logical system ( BD54)
ECC system - EDACLNT112,
PI systems u2013 IDACLNT210
Third party u2013 LSMINCOM
Port ( WE21)
IDACLNT510 : For PI with RFC destination IDACLNT510
Partner ( WE20)
LSMINCOM : (Partn.Type LS)
Outbound parmtrs.- Partner Role- LS, Message : ORDERS , Port - IDACLNT510
Inbound parmtrs.- Partner Role- LS, Message : INVOIC , Message Variant- MM, Process code u2013 INVL, Trigger immediately (Process code INVL have Identification - IDOC_INPUT_INVOIC_MRM, Option ALE u2013 Processing with ALE services , Processing type- processing by functional module)
Here PO Creation is working fine . IDoC of PO outbound message have below details :
Recipient information:
Port :     IDACLNT510 (Logical system & Port created in WE21 )
Partner Number : LSMINCOM   ( Logical system and Partner created in WE20)
Partn.Type : LS
Function : LS
Sender information:
Port : SAPEDA ( donu2019t know how it created..but in WE21..it is not there)
Partner number:   EDACLNT112 ( Logical system and Partner created in WE20)
Partn.Type : LS
Partner Role :Blank
Just started testing, our PI team is sending the IDoC, with wrong information on partner & other data, so inbound IDoC failing with error u201CEDI: Partner profile not availableu201D. Oaky. I reprocessed these failed IDoCs by changing Partner data just opposite (i.e. Sender info as Recipient info & vice versa) to successful PO Creation O/B message in WE19 in EDIDC and when I click on u201CStandard Inboundu201D, then another window open giving error message u201CPartner profile not maintainedu201D and creates new IDoC with status 56
EDI: Partner profile inbound not availableMessage no. E0337
Diagnosis
An inbound partner profile could not be found with the following key:
/LSMINCOM/LS//INVOIC///X/
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
Procedure
Please check the inbound partner profiles.
Execute function
I am not getting exactly what inbound partner profile could not be found or what is the problem here . Can anyone suggest me what should be the problem and solution on it ?
Thanks
NAP

Narendra,
Please advice what was the solution.

EDI: Partner profile inbound not available Message no. E0337

Hi Friends,
I am facing very wiered issue for incoming vendor frieght invoice. When the IDOC is sent to SAP from the edi subsystem, it gets posted with status 56 and error message
EDI: Partner profile inbound not available
Message no. E0337
Diagnosis
An inbound partner profile could not be found with the following key:
/0040000010/LI/VN/INVOIC/MM///
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
I have created the partner profile in WE20 for Partner type LI, partner role VN and process code INVL, message type INVOIC, message code MM. I have also checked the entry in TABLE EDP21 and the entry exists.
When I open the IDOC in WE19, and click on standard inbound TAB it says partner profile not maintianed, however when i click on the control record it opens a dialog box, where we have all the entries for partner profile and when I just click on any field in the dialog box and click continue and when again click on standard inbound it say partner profile maintained.
None of the data is changed in the IDOC control record, I just click on any field and it finds the partner profile.
Please let me know your thoughts, what could be possible reason and a solution.
Thanks
Deepak

Hi Deepak,
I am facing the same problem with a different message type.
But same effect. I can copy the IDoc with WE19 and it will process nicely, completely unchanged.
Have you found the reason for this?
Thanks,
Florian

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

Partner profile tables.

Similar Messages

Maybe you are looking for