WE20 - Partner profile Creation

Hi all
I am an FI consultant and working on task - generating the I docs for the Billing documents. We have configured the Out put determination for Billing documents.
I have to create the partner profile for the specified customer in WE20.
Do we have to maintain both Inbound and Out bound parameters?
Also please guide me what are the parameters i need to select for adding in both the cases for the Customer partner profile creation ?
Please let me know.
Thanks
Meenakshi

Hi
You need to work with Basis Consultant and as well as with ABAP Consultant
Settings for customer
You need create Partner Profiles, Partner Type, Agent ,
Outbound Parameters
Partner Role : BP, Message type:INVOIC, Message variant MM,
Outbound Options tab
Receiver Port: XXXXX
Pack. Size: 1
Output Mode
Select Transfer Idoc Immed- In general depends on your requirement
Idoc Type INV0IC01
Check the Check box for Cancel Processing After Syntax Error
Message Control Tab
Application V3
Message type: RD04
Process code : SD08
Settings for Vendor
Define Partner Type
Agent
Inbound Parmeters
Message type : INVOIC
Message Variant: xx
Inbound Options Tab
Process code : INVG
Check the check box Cancel Processing After Syntax Error
Processing by Functional Module
Trigger by background program
Select Trigger Immediately u2013 Ingeneral
These settings are needed
Regards
Odaiah Pelley

Similar Messages

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

EDI Partner Profile creation at Transaction Code FI12

How is the partner profile created when you select the Icon Partner Profiles, which is transaction code WE20 that is accessing from transaction code FI12.
The type is B for bank. Can the partner number be a end user defined number? Can this be the vendor number for the bank? That does not appear to be an option!
Here are my questions of the Post processing permit agent design.
How are the values for the "Types" created?
Thanks
Chris Courter

Rohan Patil wrote:>
> BEGIN = 1.
> edi_dc40 segment values
> SEGMENT = 1.
> TABNAM = EDI_DC40.
> MANDT = 120.
> DIRECT = 2.
> IDOCTYP = CREMAS05.
> MESTYP = CREMAS.
> SNDPORT = SAPNBD.(XI port)
> SNDPRT = LS.
> SNDPRFC = LS
> SNDPRN = NXICLNT120.
> RCVPOR = SAPNED.(ECCport)
> RCVPRT = LS
> RCVPFC = LS
> RCVPRN = ECCCLNT120(ECC partner number).
Hello Rohan,
IDocs SNDPRN/SNDPRT/MESTYP will be taken in SAP for processing the received IDOC,so in your case either you need to create the partner profile NXICLNT120 with all inbound details or need to change the same in mapping and pass the values of your partner in SNDPRN SNDPRT fileds of control record
HTH
Rajesh

Issue !!! Partner Profile Creation Using EDI !!!

Hi!
   Can anyone tell me whats the use of <b>Message Code & Message Function</b> for Creating Partner Profiles using<b> EDI</b>
    Transacion WE20 for EDI.
   Thanks.

Hi,
These fields can be used to differentiate between processing of the same message type. You can create several partner profiles using the same message type. By populating these fields, you are able to assign different process codes. Otherwise you are only allowed one entry for the message type.
For example, you need to setup two inbound partner profile for delivery advice. One is dealing with incoming shipment (process code DELS) and the other one dealing with purchasing (process code DESA). Both are using same message type DESADV. If you did not specify message code or message function. They system will allow to setup only one inbound message type for DESADV and not for two entries in inbound partner profile. For this case, you need to populate both the message function fields, for example SHP (Shipment) and PUR (Purchasing).
By doing these, system will allow you to assign different process codes for same message type.
Also these will allow you to split/group the IDocs processing (running parallel).
For example, if you want to post the incoming above message types, you can use standard program RBDAPP01 to process and running parallel by specify message function in selection screen or you can setup different variants to run in the background.
Regards,
Ferry Lianto

Partner Profile - Creation date

Is creation date for partner profile stored in any tables?
I looked at EDPP1 but could not find it.
-Thanks
Bob

Bob,
Table EDPP1 is for partner profiles general parameters.
Suppose you want to find the creation date of your customer of partner type KU, you`ll look for the following tables : KNA1 and EDPP1.
Sample Code
data : l_date like sy-datum.
***if your partner no. is 1000 and he is your customer.
select single erdat from kna1 into l_date
where kunnr = '0000001000'.
***kindly note that abovesaid zeroes are necessary, since **the field KUNNR is of length 10
now l_date will have the value of created date.
Hope this serves purpose.
Reward points if helpful.
Regards

Customizing (Automatically add a customer in WE20 partner profiles under KU

Hi,
Is it possible to add a customer automatically in WE20 under Partner type KU.
I mean when ever a customer is added in R3 or by any standard transaction code where we can create automatically all the existing customers under Partner type KU?

Hello,
          It is not possible to add a Customer automatically to the Partner Profiles (WE20).
          I believe creating Customer and maintaining the same Customer Number in Partner Profiles are two different & independent tasks because it is not necessary for every customer to be part of the EDI Transmission.
         Hence, people maintain partner profiles as per their requirement, not necessarily for every Customer created in SAP.
Hope it was clear.
Thanks and Regards,
Venkat Phani Prasad Konduri
Edited by: Konduri Venkata Phani Prasad on Sep 11, 2008 11:05 PM

WE20 - partner profiles: inbound parameters - how to determine process code

Running standalone scenario on SRM 5.0.
First of all, it is not possible to "generate partner profiles" automatically in BD64 (distrubution model) in the backend system for message types:
BBPIV, BBPCP, ACC_GOODS_MOVEMENT, ACLPAY and MBGMCR.
The following error is displayed:
BBPCO
Inbound parameters for message type BBPCO could not be created
Enter a valid process code
etc.
When trying to create partner profiles manually in WE20, how do I determine the process codes for the different message types?

Note 330401 - Process code does not exist f. BBPCO01, BBPIV01
Solution
Check and if necessary, correct the following entries:
1. Assign function module to message type
Transaction WE57
The following entries are required:
Module IDOC_INPUT_BBP_IV IDOC_INPUT_BBP_ACC_PO
Type F F
Basic type BBPIV01 BBPCO01
Msg type BBPIV BBPCO
Direction 2 2
Object type BBPBUS2081 (not for Release 3.1)
Note that object type BBPBUS2081 is not defined in Release 3.1*. In
this case, the 'Object type' entry remains empty.
2. Characteristics of inbound function modules
Transaction BD51
The following entries are required:
Inbound FM IDOC_INPUT_BBP_IV IDOC_INPUT_BBP_ACC_PO
Input type 1 1
03.09.2008 Page 2 of 3
Note 330401 - Process code does not exist f. BBPCO01, BBPIV01
Dialog allowed No No
3. Create the missing process code with Transaction WE42 (change inbound
process code). You can name the process code whatever you want. 'IV01'
or 'CO01' are examples.
The entry should look like this:
Process code IV01 (CO01)
Description BBPIV (BBPCO) inbound invoice
Option ALE Processing with ALE service
Processing Type Processing by function module
Save the entry. You are then on the detail screen. Enter:
Module (inbound)
Function module
IDOC_INPUT_BBP_IV (IDOC_INPUT_BBP_ACC_PO)
Application object
Object type
BBPBUS2081 (- no entry -)
4. Maintain the process code that has just been created in the partner
profile for the logical system.
Transaction WE20
Partner type 'LS'
regards
Muthu

Why we maintain Partner Profiles in WE20??

HI,
What is the affect of entries in the following T-codes:
And the following are the entries maintained for respective T-CODEs, in our project.
OBCA: ( LOGICAL SYSTEM - SYSTEM - CUSTOMER - CUSTOMER COMPANY CODE)
OBCE: (LOGICAL SYSTEM - SYSTEM - CUSTOMER COMPANY CODE)
And what about WE20 partner profiles maintenance why do we need to do so?
Please explain about these three T-CODES
Regards,
Venkat

it is just another way to maintain the same thing in the same tables. Classification notspecific to release strategies, materials and batches, vendors and customers can be classified too.
You can do this from withion those objects, or from the central classification menu using the classification transactions.
People here recommending this for production system after you have transported the strategy from developement to production. Becaues classification is master data and cannot be transported the usual way. And many here do not know how this can be done with ALE

IDOC question on Message type and Basic Type - Partner Profile

Hi all,
I am wonder if I can post any IDoc question in this right forum/module. If not please direct me to the right forum/module. I am a newbie in IDOC setup.
My question is about the setup of Partner Profile creation (WE20).
When creating a new partner, for example with partner type LI, I notice there is outbound parameter and inbound parameter.
Questions:
1 u2013 It makes sense to have only one message type record appear in EITHER one of these two tables. I notice that some partner in my system has message type record exist on both the inbound and outbound parameters table, why system allows? What is the business rational?
2 u2013 May I have a list of standard SAPu2019s Message Type object of its usage description, and its allowable Basic Type (ie. IDOC TYPE). Basically a website to describe their (i.e. Message type and its Basic Type) business usage.
Thanks.
tuff

Tuff,
Below are my thoughts,
There is a partner sing partner type LI. This partner in the WE20, has one record (i.e. with Message Type ORDERS) exist in the Outbound Parameter table. This partner also has 4 records (i.w. with Message Type DESADV, INVOIC, MBGMCR, and ORDRSP) exist in the Inbound Parameter table. So my question is what is the business rational behind this kind of setup. Because I am confuse when come to create a partner profile, whether I need to create a message type in Inbound Parameter table or Outbound Parameter table, or I need both.
OK, so looking at the above example, you have an orders message type(This is for creating an order) in the outbound, this means that you are sending out an IDOC(purchase order for ex) to this partner, so that this partner can create an SO in his system and fulfill your order.
Now you also, mention that you have other four Message types for the same partner on the inbound, now let us look at the above scenario, you have asked your partner to fulfill the order, i guess you would like to get a confirmation from him/her if the order was created or not in his/her system and how and when is he/she going to fulfill your order requirement. This he/she does by sending an response to your order - ORDRSP.
And when the partner is ready to ship your order to you, he/she sends out a Advance Shipping Notice - ASN via the IDOC of message type DESADV.
Finally and most importantly , he/she will send you the invoice - INVOIC for the order.
In general, you interact with your partner via Business Docs - Order, Delivery, ASN, Invoice etc, so whatever document come from your partner - ORDRSP, INVOIC etc will be on the inbound profile of the partner. Whatever docs that you send ORDERS, ORDCHG etc etc will be on the outbound profile of the partner.
2 - Bascially I would like a reference in any website that allow me to choose which message type is best use for my partner profile, so that I don't have to reinvent.
Well, there is no choice of choosing/best message type for a given requirement - So for sending an Invoice the message type is INVOIC, ORDERS - For order creation, ORDCHG for order change etc. However the IDOC type, is some thing that you can choose, for Ex: ORDERS01 - ORDERS05, these are the IDOC types that are available, so if you are interacting with a partner who are running an old version of SAP and their system has only upto ORDERS02 in their version of SAP then you would use ORDERS02.
Regards,
Chen

Partner profiles and ports

How to transport the configuration of partner profiles and ports from Development to Quality systems.

Hi vidya,
Go through this hope u can get the solution.
WE20 Partner Profile
Here we create partner profile for each and every partner from / to which
the messages will be exchanged.There are 6 types of PF generally only
profiles of type LS(Logical System) ,KU(Customer) ,LI(Vendor) is used.
We specify the partner number and partner type and the agent and
the agent type responsible for handling of errors .
For every message send to the partner we have a outbound record and for
evry message coming from the partner we have the inbound record .
We specify the message in the otbound/inbound records ,double
clicking will take us to the detailed screen where the IDOC Type ,Port
and whether the IDCO will be immediatelt processed or collected are
mentioned.
WE21 Port Definition.
There are 6 types of ports but only 2 types File and Transactional RFC
types of ports are important.
We have to specify the RFC Destination before a port can be created.
SM59 RFC Destination
Here we specify the login settings for the destination including
the I.P address or Application Server name and the User name and
password.The information entered here is used to run Remote Function
Calls(RFC ) on the destination server .We can create number of types
of RFC Destinations but 3 types are important .
R/3 (R/3 to R/3), LS(logical system) and TCP/IP.
The name of the RFC destination should be same as that of Logical
System as it helps in creation of automatic partner profiles.
BD64 Distribution Model . Also known as Customer Distribution Model Used to
define all the messages that will be exchanged between remote systems
and the name of thes logical systems. Any filters can also be specified.
The model once created has to be distributed on every system which will
be communicating ,It can be maintained on only One system.
Reward points if helpful.
Thanks
Naveen khan

Regarding ports and partner profiles in ALE.

Hi All,
Please tell me how to transport the partner profiles and ports from Development to Quality systems.
Please reply asap.

SALE Area Menu for ALE configurations.It includes transactions for
Logical System definition and linking it to a client, Transactions for
RFC Destination and Port Definition Etc.
SM59 RFC Destination
Here we specify the login settings for the destination including
the I.P address or Application Server name and the User name and
password.The information entered here is used to run Remote Function
Calls(RFC ) on the destination server .We can create number of types
of RFC Destinations but 3 types are important .
R/3 (R/3 to R/3), LS(logical system) and TCP/IP.
The name of the RFC destination should be same as that of Logical
System as it helps in creation of automatic partner profiles.
WE21 Port Definition.
There are 6 types of ports but only 2 types File and Transactional RFC
types of ports are important.
We have to specify the RFC Destination before a port can be created.
WE20 Partner Profile
Here we create partner profile for each and every partner from / to which
the messages will be exchanged.There are 6 types of PF generally only
profiles of type LS(Logical System) ,KU(Customer) ,LI(Vendor) is used.
We specify the partner number and partner type and the agent and
the agent type responsible for handling of errors .
For every message send to the partner we have a outbound record and for
evry message coming from the partner we have the inbound record .
We specify the message in the otbound/inbound records ,double
clicking will take us to the detailed screen where the IDOC Type ,Port
and whether the IDCO will be immediatelt processed or collected are
mentioned.
Reward points if helpful.
Thanks
Naveen khan
Message was edited by:
Pattan Naveen

Limitation on number of partner profiles

Hi,
I am working on SAP Retail implementation. As you know, in SAP Retail, we consider each store as customer and there will be seperate partner profile of type customer for each store.This is for integrating SAP with point of sale (store).
Since number of stores are more, around 1000, i feel it's not good solution to create 1000 partner profiles. Please let me know whether there is any alternative for this and also whether there is any limitation on number of partner profiles that we can create.

There is no limitation for partner profile creation
Regards,
Prateek

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 not Generated

hi! all
Generating the Partner Profile Using BD64
while generating received the message in Green for parameters: Partner (Sender, Receiver); Port (Zport); Outbound Parameter(Zsender).
while checking in WE20 - Partner Profile ; Profile has been generated for the Reciver System with the created message type and port in Outbound parameter. But not generates the Inbound parameter.
As like Profile has not generated for the Sender system.
While testing the idoc using WE19 it says Profile not generated for Sender system
whats the mistake i have done. How to correct it.
Regards,
Kv

Hello,
The distribution model view for which you are generating the partner profile (PP) check the sending & receiving logical systems (LS).
if you want to generate the PP with inbound params you have to assign the your own LS as the receiver & not the sender.
BR,
Suhas
PS: If this bothers you too much maintain the inbound params manually in WE20

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

WE20 - Partner profile Creation

Similar Messages

Maybe you are looking for