Regarding partner profiles LI and KU

Hi,
I need to send a PO created in one SAP system to a vendor system where it needs to create SO automatically.In this senario which partner type i need to use for outbound and which partner type i need to use for inbound ....(i.e in LI and KU which is used for outbound and which is used for inbound)
Thanks&Regards
Giridhar Karnam

Hello Giridhar,
In Outbound settings we need to select partner type as LI and Inbound settings we need to select partner type as KU in this Scenario.
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b809b43d711d1893e0000e8323c4f/frameset.htm
Above scenario is beautifully explained in the following blog. Refer this
/people/srinivas.vanamala2/blog/2006/12/11/edi-basics
Regards
Srikanth
Reward me if helpful

Similar Messages

Partner profile LI and unit of measure

Hi gurus,
I am experiencing a weird situation and probably you have any clue about it.
I have configured an output to send the Purchase order information via EDI. I have used the standard function and programs to create the output. I have created the condition record for that particular vendor and output.
Then i have created the LI partner profile in we20 with the vendor number and the message types ORDERS and ORDCHG and I have also included my output with the ME10 and the ME11 in each of the messages.
When i create the PO and the output is sent I have the PO number but then i have the standard error message " Update was terminated" with the error "There is no conversion factor for material and unit of measure !" I have reviewed the PO and i have used a UoM PC that i have as an ISO code.
the point is if I use a different LI partner profile with exactly the same information then the idoc is sent without any problem. I have deleted the partner LI that I orinally created and i created it again as a copy of the one that is working but without sucess.
I have reviewed the vendor master data...but all is exactly the same.
I think or there is some config missing or that I have created the partner profile incorrectly. But it is rare that the partner profile has any link to the UoM.
Do you have any idea what it can be?
thanks so much

I understand from your mail, you have maintained the ISO equivalence to your UOM. When you change your vendor in WE20, did you change that information in MN04? This is the place where the right output type is triggered.
Other than that make sure you configured all the necessary items in WE20 -> Outbound Parameters -> process code and all otehr necessary settings.
Let me know, how it works?
Regards,

Regarding partner profiles

Hi,
How to use the partner types LI and KU in WE20 transaction.
Thanks&Regards
Giridhar Karnam

Hi,
WE20 is used for partner profile setups.In other words it is here where you define the partners who will send/receive a particular type idoc.
You can set up the partner profile for either inbound or outbound idoc by giving in the following details.
Enter the partner no. and the partner type(LI or WE).
After giving the values goto Outbound parameters for outbound idoc.Give the partner role(OA,VN or any other),give the message type of the idoc.Give the receiver port and idoc type.
Similarly do for inbound idoc.
In WE20 the parner profile must be setup before you post any idoc to that partner.
Hope it is useful.
Thanks,
Sandeep.

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

What is PDC in partner profile? and PDC time req. ID card

Hi all,
These are actually tabs when you click F4 on agent in WE20 (partner profile). What is PDC? Please point me to related files or threads.
Thanks,
Charles.

Hi,
Please check this online document.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ed60b490-0201-0010-dc82-8bea16db1dfd
Regards,
Ferry Lianto

Regarding Partner types LI and KU in WE20 transaction

Hi,
I want to send a purchase order to a particular vendor through EDI. When ever I create a PO if the customer is CUST1(for example) and vendor is VEND1(for example) then only EDI should trigger. Pls give me the possible configuration steps. Is it possible by using LI and KU partner types in WE20.
Points will be awarded for all helpful points.
Thanks&Regards
Giridhar Karnam

Hi Giridhar,
Please check the tab Permitted agent that might be used for specifying the vendor name.
I think these validatikons can be carried out while executing the Function Module.
Regards,
Ravi G

When I open the browser, it says as an alert regarding the profile directory and says that read/write should be changed and it doesn't work then.i uninstalled and re-installed firefox6.0.2.how can i overcome this problem

could not initialize the application's security component .the most likely cause is problems with files in your application's probile directory.please check that this directory had no read/write restrictionsand ur hard disk is not full or close to full .It is recommended that you exit the application and fix the problem.if you continue to use this session ,you mightsee incorrect application behaviour when accessing security features....THIS IS THE ALERT I GET WHENEVER I TRY TO OPEN FIREFOX.

See:
*https://support.mozilla.com/kb/Could+not+initialize+the+browser+security+component

Partner profile...port....logical system....!!!!!!!

Hello Everyone,
few stupid questions came to my mind but no document cleard it, so thought that someone might throw some light on this.

What is logical system in R/3 and why do we create that ?
what do we mean by partner profile and what is its significance?
what is use of port...???
these all three parameters we look when we create outbound IDOCs for IDOC to file (of any other) scenario.
thanks,
Pranav

Hi Pranav,
What is logical system in R/3 and why do we create that ?
A logical system is your R/3 address where you can distribute data to and from an R/3 system.
http://download-west.oracle.com/docs/cd/B10464_05/integrate.904/b10299/ale.htm This link gives you a better idea of a logical system.
what do we mean by partner profile and what is its significance?
Based on an existing logical system, a partner profile is an identifier for a system used for communicating messages.
http://download-east.oracle.com/docs/cd/B10465_01/integrate.904/b10408/ale.htm gives you a very good idea regarding partner profiles and ports.
Hope these help,
Regards
Kiran..

Partner Profile settings for IDOCs

Hi,
when i posted the IDOC, it left the status 51.
i think which means "Application not posted".
do i need to change the partner profile!
if yes please let me know how to change that.
its very urgent please.
thanks in advance.
Regards,
ravi.

As mentioned in the earlier reply you need to check idoc listing WE02.
You may also want to look into the partner profile- WE20 and see if what you are trying to pass thru has been set up correctly. Make sure the correct port is defined along with the partner details.
If you need to edit the IDoc , you can do it from WE02 by clicking on the segment and then going into the Change mode. The other option of re- processing Idocs is using the testing tool- WE19 or the re-process Idocs BD87 transactions.

Partner profiles usage

Hi,
Please can any one send me details about partner profiles usage and the tcode where exactly we have to maintain this.
If anyone have documentation on AlE is added advantage for me.
Regards,
Koti

Hi,
Logical System name is used to indicate the application system to which you are sending the data. Partner profiles use the above Logical System name to determine the system to which the data is to be sent ie you have to tell wether inbound or outbound.
Below are the links for ALE IDOC related materials.
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)
Reward points if useful.
Regards,
Soumya.

Error creating partner profiles using we20

hi friends,
I am trying to create a new partner profile from an existing one..but it giving me an error "Please enter a permitted partner number"... but when i give another number its accepting....
can someone help me understand what am i missing?
cheers
charlie

Hi
assign the partner profile number in fi12 and save then click on the partner profile button and copy the partner profile u want and create a new one and save.
Regards
genie

Partner Profiles overwritten by TDMS-Copy

Hello,
our TDMS-Copy succeeded by overwriting an old client, but copied Partner Profiles (WE20) and Ports (WE21) too, which we didnu2019t want to be changed. Is there a way to save this data?
Regards
p121848

Hi,
The table names are
TBD00 EDIMSG
EDP21
EDP13
EDP12
EDIDD
EDIPHONE
EDP13
EDP21
EDPP1
EDMAT
EDMA
EDADM
EDAYTYPBLOCK
EDAYTYPBLOCKDEF
EDAYTYPBLOCKT
EDAYTYPE
EDAYTYPET
EDBDMSKY
EDCPIC
EDE1T
EDE2T
EDE5T
EDE6T
EDEREGPARCONF
EDEREGPARCONFT
EDEREGPARVAL
EDEREGPODGROUP
EDEREGPODGROUPT
EDEREGPROCPARDIS
EDEREGSCENAGREE
EDEREGSCENARIO
EDEREGSCENARIOT
EDEREGSCENCONTR
EDEREGSCENCONTRT
EDEREGSCENDATEX
EDEREGSCENSERV
EDEREGSCENSERVT
EDEREGSPAGREE
EDEREGSWITCHDIAL
EDEREGSWITCHPROC
EDEREGSWITCHSYST
EDEREG_SERIDENT
EDEREG_SERIDENTT
TBD001
TBD002
TBD00T
TBD03
TBD05
TBD06
TBD20
TBD30
TBD40
TBD41
TBD52
TBD55
TBD56
TBD61
TBD611
TBD61B
TBD62
TBD71
TBD71T
TBD72
TBD73
TBD74
TBDA1
TBDA2
TBDBANKC
TBDBR
TBDBRF
TBDC001
TBDC002
TBDIBAN
TBDLI
TBDLT
TBDMO
TBDMO_DET
TBDRCSTATE
TBDSE
TBDSET
EDEREG_SIDPRO
EDEREG_SIDPROINT
EDEREG_SIDPROT
EDEVCHECK_BACKUP
EDEVGR
EDEXCOMMFORMALE
EDEXCOMMFORMAT
EDEXCOMMFORMATT
EDEXCOMMFORMFTP
EDEXCOMMFORMINTR
EDEXCOMMFORMMAIL
EDEXCOMMFORMPART
EDEXCOMMFORMVERS
EDEXCOMMFORMXML
EDEXCOMMMAILADDR
EDEXDEFSERVPROV
EDEXDEFUI
EDEXDUECONTR
EDEXDUECONTRT
EDEXIDOCSEND
EDEXIDOCSENDT
EDEXPROC
EDEXPROCPAR
EDEXPROCPODGEN
EDEXPROCSPGEN
EDEXPROCT
EDEXPROCUI
EDEXTASK
EDEXTASKASS
EDEXTASKERROR
EDEXTASKIDOC
EDEXTASKREF
EDEXTASKWKFLOW
EDGE
EDICONFIG
EDID3
EDIDD_OLD
EDIDOCINDX
EDILOGADR
EDIPHONE
EDIPO2
EDIPOA
EDIPOACODPAG
EDIPOD
EDIPOF
EDIPOI
EDIPORT
EDIPOX
EDIPOXH
EDIPOXU
EDIQI
EDIQO
EDISCACT
EDISCDOC
EDISCOBJ
EDISCOBJH
EDISCORDSTATE
EDISCORDSTATET
EDISCPOS
EDISCREMOV
EDISCTYPE
EDISCTYPET
EDISCVAR
EDISCVART
EDIVDIM
EDI_MONIT
EDLTYP
EDMMS
EDMS_AT01
EDMS_CONDITION
EDMS_CT01
EDMS_CT01T
EDMS_FILTER
EDMS_LAYOUT
EDMS_LAY_DETAIL
EDMS_PREFS
EDP12
EDP13
EDP21
EDPAR
EDPI1
EDPO1
EDPO3
EDPP1
EDPPV
EDPST
EDPVW
EDRGPODGRASSIG
EDRGSPAGRTYPE
EDRGSPAGRTYPET
EDSC
EDSCH
EDSCHINDEXA
EDSCT
EDSDC
These tables are involved in transaction We20 and Bd64

Changes to partner profile

Hi,
Which log can give me details who had changed the partner profile (we20)and what has been changed?
Regards,
Ravi

Hi Ravi,
Welcome to SDN.
Unfortunately, there is no log or table which keep track the user who made changes to partner profile (WE20).
Regards,
Ferry Lianto

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

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

Regarding partner profiles LI and KU

Similar Messages

Maybe you are looking for