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!

Similar Messages

I need to know , how to handle partner profile using BDC.

hi all ,
i need to know how to handle the Partner Profile using BDC, i need the basics behind if any one address regarding this it ill be very helpfull for me. i need a detail description for the above.
Thanks a Lot in Advance........
Thanks
senmaar.

I need the basic behind , need to know how its works..... And i need to know could you give me a simple scenario so that i can easily understand.
Could anyone Describe the Basics about that.......
Thanks in Advance
Regards ,
Senthil Kumar

Define Port, Partner Profiles, Process Code

Hi All,
Please provide the following valueble information
Define the below and why do we create them?
1. Port
2. Partner Profile
3. IDOC type and IDOC
4. Process Code
5. Message Type
Thanks and Regards
Sowjanya

>>1. Port
Ports are channel through which idocs are exchanged.
>>2. Partner Profile
Partner Profile specifies the kind of message that we are going to exchange with our business partner
>>3. IDOC type and IDOC
IDoc type defines the structure of the idoc. IDoc is a container which carries the data from one system to the another.
>>4. Process Code
Process Code refers to inbound function module which will read the data from the idoc and post it in the system.
>>5. Message Type
Message Type defines the kind of data that you are exchanging with your business partner.
Cheers,
Hakim

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

Partner profile in case of Idoc to File scenario

Hi
I have ECC system and PI system. Scenario as :
ECC will send the Idoc to PI ..PI system will Convert this to flat file and provide it to Legarcy system
I made Partner profile in sending system (ECC) and maintained Message type 'MATMAS' as Outbound.
Do i need to maintained the MATMAS in Partner profile of PI also?.
As PI has copied the Idoc MATMAS.MATMAS05 from ECC.
I am confused please suggest

Hi,
MATMAS05 should be configured as outbound paramters of ECC and no need to configure any thing at PI Partner Profile..
All you need to do is to create the Distribution model as sender (ECC) receiver (PI) and message type as MATMAS05...
with appropraite RFC destination name and port.....
if you are new to distribution model and like to know tcodes for the same just check the below link
http://pavelgk.pbworks.com/Step-by-step-tutorial-for-creating-Idocs#221Creationofanewdistributionmodelview
HTH
Rajesh

Status 56 : EDI Inbound Partner Profile not available

I am trying to load an inbound 856 IDoc from EdI subsystem to SAP. It si giving me an error 56 saying Inbound partner profile not available.
I have set up the partner as Vendor in we20. Is there any other place that I need to set up the partner. We have inbound docs coming in as a customer(KU) but this is first vendor set up
Do you know what I am missing?
When I clicked on status message 56 -- says /ICPLPLIVA/LI/LF/DESADV///T/....key fields missing in EDP21? is the error really meant that?
Thanks in advance

Hi,
Can you tell us about the IDoc control record?
In order to determine whether need to setup LI or KU partner profile.
Please go to WE02 and check the IDoc control record.
What are the values in partner tab?
Port             ???
Partner number   ???
Partn.Type       ???
Function
Port             ???
Partner number   ???
Partn.Type       ???
Partner Role
Regards,
Ferry Lianto

Send emails to specified users,but SAP is picking from partner profile WE20

Hello
By using FM 'SAP_WAPI_START_WORKFLOW', passing with task = 'TS00007989' amd triggering workflow, if at all my IDOC get fails! This work flow/task will send en emaill to the Permitted Agent defined in partner profile, WE20 for that partner type/message type, fine. In our case, the Permitted Agent is 'Workflow Administrator', so he is getting emails for IDOC errors.
But, we do not want to let SAP pick this Adminstartor from partner profile, we want to maintain a custom table for users IDs and we want to SAP pick this receivers/recepients from this custom table for User IDs
Note: already am passing user IDs in ' agents' table parameter explicitly, but still SAP is picking workflow admin from partner profile!
How can i achive this? any user-exit or any BADI or ENH? Pls. let me know
Thank you

HI
Can you please give inputs on following
1. Where you are triggering WF using 'SAP_WAPI_START_WORKFLOW'
2. is that workflow custom workflow ?
There in one way triggering custom workflow when IDoc is in error mode.
1. When you assign function module to process code there is ALE table button in front of FM.
2. Once you click that you can assign Object type, start event, end event.
3. To this particular event custom worklfow will be triggered.
4. In your custom workflow you can select agents as per your requirement.
Regards
Sachin

Get trading partner profile identifiers

Hi,
Can you advise which function/expression in BPEL Process Manager that can be call to get the B2B trading partner profile identifiers? Because I have a use case where by I'm evaluating trading partner to perform specific logic.
For example, I want to get the value of the identifier type "Name", the expected value would be "Acme".
Regards,
Scott.

Hi Anuj,
Your example is correct if the message receive from B2B partner link.
However, my scenario is the reverse. I am receiving the message from a File Adapter partner link, then I need to fetch properties in trading partner profile for decision logic.
Essentially, I'm looking for APIs that are used in the Oracle B2B partners tab. I want to call these APIs from BPEL to get trading partner profile details.
Regards,
Scott.

For file to IDOC scenario, do i need to make a partner profile in XI ?

for a file--->XI--->IDOC scenario, do i need to make a partner profile in XI(for the R/3 system which is going to receive the IDOC),
or only a port maintenance in idx1 will do.....

hi Sudheer,
yes u need to maintain partner profile in R/3
Check below link in WIKi for complete File to IDOC
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/fileToIDOC&
Sachin

Need log of the users who changed the partner profiles.

Hi,
Some user has been changed partner profiles of the CUA configuration Setup.
It is displaying only Agent Name. They delete the Inbound and outbound parameters of the partner profiles created by CUA. So, I need to trace out the user who changed these parameters.
It will be appreciate if anybody can help in this issue.
Thanks,
Shiva.

I resolved this issue by deleting the partner profiles created by CUA in all child clients. And delete the Distribution model in all child clients and re-distribute the distribution model from Master client.
Now its working fine.
But I am not able to trace out the user who changed partner profiles. I checked in ST03N but i didnt get the information abt the we20. ( I am using ECC 6.0 version).
And in WE20 it is not showing any User ID who changed the partner profiles. I checked in following tables but I didnt find any changed details of partner profiles.
EDIPHO
EDMSG
EDP12
EDP13
EDP21
EDPP1
T002T
T005T
Regards,
shiva.

TC related for IDOC (Defining Port,Defining Partner Profiles...etc) RFC and

Hi All
Can anyone pls give me all the TC related for IDOC (Defining Port,Defining Partner Profiles...etc) RFC and BAPI
Thanks
ss

Hi SS..
 SM59-For creating the RFC destination
 we21- For ports
 we20-Partner profiles.
For more inforamtion Please look at the below information:
SAP XI
1) RFC Destination (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.
2) Create Port (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 SAP XI towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (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.
2) Create Port (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)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (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.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
 Thanks and Regards,
 Chandu.
Message was edited by:
 Chandu
null

Needed urgent clarification on FILE TO IDOC scenario

Hi Experts,
                  I need urgent clarification on FILE TO IDOC scenario plz clarify it
1.In FILE TO IDOC scenario after creation of RFC dest ,performing steps in IDX1&IDX2
what configurations to be done on target system?
2.In some blogs it is given that steps should be done in RFC dest,we21,we20 .
But is it mandatory to do so RFC dest and WE21 steps [OR] directly can we configure partner profile in WE20?
3.on integ server IDX2 has to be done (or) is it optional for FILE TO IDOC scenario?
Too many to answer plz clarify good explanations will be rewarded.
                                                                                Regards,
                                                                                Vinod.

Hi,
Please follow the below process for configuration:
Pre-requisites for Inbound IDoc to R/3 from PI:
Configuration required at Xi side:
Go to IDX1: configure the port.
Go to IDX2: load the DOC metadata.
Go to SM59: Create RFC destination which points to R3 system this is require in the case where your IDOC is sent to R 3 system,
Configiration required at R3 side:
Maintain Logical System for PI (SALE transaction):
Maintain Partner Profile for XI system(WE20):
Pre-requisites for Outbound IDoc from R/3 to PI:
Configurations required in R/3:
Maintain Logical System (SALE)
Define RFC Destination (SM59) which points to PI system
Maintain Port (WE21)
Maintain partner profile. (WE20):
Maintain Distribution Model (BD64):
DO let me know if you need more information
Thanks and Regards,
Chirag Gohil.

Partner Profile - LS

I have two decentralized system which needs to receive ASN and POs from SAP. Each of these systems consist of 3 plants. How would I set up the Partner profile to group the 3 plants under on each decentralized system?
Would I set up the partner profile with a partner type of Vendor(plant) or is there a way to set up the partner profile as Logical System and somehow group the 3 plants under each logical system?
I have seen a screen in SAP which allows you to put a small bit of ABAP during a partner function call, but I dont remember the transaction.
Any help would be greatly appreciated

you can make it by having two seperate output types defined for each receiving systems.
For example ZNE1 for system 1,ZNE2 for system 2.
Maitain cond. records for the plants.
So based on the plant system proposes the output.
Now you have got the output proposed.
next thing define the two logical system reprsents the receiving systems.
Then use BD64 to define the distribution model whereas you specfiy sendinf system 'YOUR SYSTEM' Receiving system 'LS_RECVSYS1' message type 'ORDERS' and save it.
Then again add another entry Receiving system 'LS_RECVSYS2' and message type 'ORDERS'.
maintain partner profiles for the two logical systems.
specify the output type ZNE1 and application as EF for LS_RECVSYS1.
specify the output type ZNE2 and application as EF for LS_RECVSYS1.
This is done to send out the purchase order.
different output types specified under message control tab makes the system to decide which system should get the outbound IDOC.
So the flow is like,you have the output proposed for 3 Plants,system checks the partner profiles.Then it check for ALE dist. model to get the actual rec. system to send out the IDOC.
Same procedure can be followed for sending out ASN too.
This works .

Partner profile to send Idoc to PI 7.4 system from ECC

Dear Experts ,
Do we need a partner profile to send Idoc to PI 7.4 system from ECC.
or Just Port on TRFC is enough ..?
if i need to create a Partner profile ...how to define a logical system and how Assign Logical System to Client... when there is no client for JAVA only PI system ..?
thanks
Shakif

Hi Mohamed,
You need to create a tRFC port on sending ECC system. The RFC destination selected in this port os the one created for IDOC transfer.
Also you need a logical system, use client 000, i.e. PI1CLNT000.
At last you have to create a partner profile to define the IDOC type used.
Best Regards
Harald

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

Need a Clarification in defining a Partner Profile

Similar Messages

Maybe you are looking for