Ale, partner profiles

Hi,
I'm not able to create partner profiles, i'm getting log 'no messages defined for
selection condition in model'.
I'm creating it using BD82 transaction.
no i dont have any conditions defined
Message was edited by: veeresh kinagi

Hai Veeresh try with this Steps
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
Thanks & Regards
Sreenivasulu P

Similar Messages

Billing invoice idoc out to file server via ALE partner profile

Hi Folks,
Can anyone tell me what partner profile I need to configure to have an INVOIC idoc go to a directory on the app server? Also I want to do this at the same time the invoice is physically printed. I do not want to do this in EDI as this would mean configuring partner profiles for all customers, so I want to do this in ALE.
I am assuming I use the partner profile for LS a logical system and have an output type in invoice message control for the idoc with suitable condition records to ensure that paper and idoc media are both selected at runtime?
Also I can get the idoc produced and to status 30 using EDI but what pushes the idoc out automatically from this point and will that be the same method once I get the idoc produced using ALE?
Cheers,
Ross Goodman

no longer an issue

ALE partner profile setup for diff. IDOC extension

Hi,
We have three extensions of IDOC type HRMD_A06 and message type HRMD_A. In one of the extensions segment IT0002 is extended.
In the partner profile extension is not specified. Due to this when the IDOC is generated Custom segment is not getting picked up.
I pu the extension in the partner profile then it woks fine.
But I do not want disturb the existing profile setup. Is there any option in WE20 where we can define two profiles with one message type, basic type and different extensions.
Also if we define the custom message type then distribution model and the partner profile needs to be generated for the new custom message type.
Appriciate quick response.
Regards,
Sonali

Hi,
just check the FM 'BAPI_BUPA_CENTRAL_GETDETAIL'.
Or just search for oher FMs with BAPI_BUPA*.
Hope this helps...
vasanth

Generation Partner Profiles from ALE Distribution Model

Hi ABAP/EDI experts,
I am a trainee. I am getting training from Pvt consultancy. I am working on SAP Demo systems.
I am trying t generate an IDoc using ALE method.
IN SALE window, I created two logical systems,ZVK_SS_800 and ZVK_SS_820. I assigned them to two clients 800 and 820 respectively.
In SM59 i created an RFC connection ZVK_RFC004 of type 3. Here I gave the client Number as 820. ( I'm not sure what to give)
In BD64, I created an ALE Model and added the message type MATMAS with Sending and Receiving Logical systems.
From the Environment drop down menu , selected generate partner profiles and executed with defaults checked. ( Transfer IDocs Immediatley and Trigger Immediately).
I got the following log.
Log For Partner Profile Generation:
Partner:
In Green Color
Partner ZVK_SS_800 as partner has been Created ( Sending System)
Partner ZVK_SS_820 as partner has been Created (Receiving System)
Port:
In Red Color
Port Cloud not be Created
RFC destination ZVK_SS_820 not specified for system ZVK_SS_820
Enter the RFC destination and Restart the generation.
Please help me to fix this probelm.
Any kind of Help will be surely rewarded.
Thanks,

From SM59, you can Test your RFC Connections between Clients. I would do this from Client 800 and test the Connection to Client 820. If that checks okay, I would then try SM59 on Client 820. Check the RFC Connection from Client 820 to Client 800. Be sure you have your Logical Systems defined on Both Clients. You can also double click on your Error Message to see if there is a Long Text Available that might give you further information as what needs to be corrected. I am not an Expert in this area, but have setup several ALE Models for my Variant Configuration without any problems. If you could include your EMail Address on your Business Card I could EMail you my instructions. Your Basis person may also be able to help you based upon your Error Message.

Configuring ALE Logical Systems and Partner Profiles

hi,
Trying to build a scenario which deals with two third party systems transfering XML file from one to another. Sender is using a file adapter. Reciever is using an Idoc adapter. However the pre-requisite mentioned for this exercise are that ALE logical systems and partner profiles must be configured (these steps are not outlined in the exercise) . Could i get help on what steps i need to carry out for sender/reciever to configure logical systems and partner profiles.
regards,
Manpreet

Hi Manpreet
At the R/3 system the partner profile should be maintained for both the third parties.
for creating the partner profile go to transaction we20, give the
partner number :your logical system name or customer number or vendor no
partner type:LS(logical system)or ku(customer)OR LI(vendor)
give the message type in the outbound parameters
after this double click on the message type and give the login deatils for the RFC destination define the port and all
if you still have problem please reply back
Thanks
Rinku

LSMW: ALE/IDOC, getting the Create a partner profile for message type

Hi Gurus,
In my current project, i need to upload the employee data using the ALE/IDOC method with the LSMW
when i'm generating the idoc in the 13th step, its posing the information message stating that:
Create a partner profile for message type 'ZEMP_MSG'
In partner profile i already assigned the message type .
How to solve this issue, <inappropriate urgency removed by moderator>
Thnks&regards,
sree
Edited by: Thomas Zloch on May 13, 2011 9:55 AM

This forum's aim is not only to search for information and ask the members questions, but also to share knowledge. When you have asked a question and found a solution, do share with the rest.

ALE Partner type ( Parnter profiles)

Can I select vendor and customer as partner type while creating partner profile in ALE configuration.
If 'YES',please let me know, where to maintain the mapping between vendor(sending system part type)
and customer(receiving system partner type).
Thanks
N.Prasad Babu

Hi friends,
     Thanks for ur prompt response.I have already created
partner profiles.Still I am getting errors in the receiving end.
In scenario is :
SENDING SYSTEM: 800(client)
Partner profile was created whose
Part.type: vendor
Port    : trfc port which has rfc desination to client 110
RECEIVING SYSTEM: 110(client)
Partner profile was created whose
Part.type: customer
Port    : trfc port which has rfc desination to client 800
Now,Do I need relate partnet type vendor to partner type customer. if "YES", how do i do it.

ALE issue:No partner profiles (message control) maintained

Hi,gurus:
My ALE scenario is tranferring PO from client 800 to 900 client.
Now the logical system,partner profile，port，rfc，distribution model are created both the sender and receiver side.
In ME21N->MESSAGE, the output type is NEU,and medium is A,partner function is LS,partner is ECCCLNT900.
When I saved the PO,the status is red,and no idoc was generated.
I viewed the processing log,the information is: No partner profiles (message control) maintained.
But my distribution model is sender:ECCCLNT800;receiver:ECCCLNT900;MESSAGE：ORDERS;
The partner profile is ECCCLNT900(LS),and the outbound parameters are ORDERS,SYNCH. For ORDERS,the message control is EF,NEU,ME10.
Have you ever met this issue?
Thanks in advance.

Hi Li,
Please refer this threads...
Re: Message is not proposing automatically
Re: IDoc was saved but cannot or should not be sent
Hope you have to post this thread in ABAP General category..
Regards,
kumar.

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

FM to get partner profile details for ALE-IDOCs?

hi
is there any function module to get partner profile details in current system?
extremly sorry my mistake......
for ALE-IDOCs
Message was edited by:
 ashwinee mali

BAPI_BUSINESS_PARTNER_MODIFY CBP: BAPI for Modifying (Creating/Changing) Business Partner
BAPI_BUSINESS_PARTN_GET_DETAIL CBP: Business Partner Detailed Information
regards,
srinivas
*reward for useful answers*

Same message type in different partner profiles in ALE

Hi,
I have a situation where we need to send an IDoc of message type ORDERS to two partners of type 'LS'. Configured partner profiles in WE20 and added message type for both the partners. Also configured the condition records.Now the question is how the system will know for particular vendors a particular partner 'LS' should be chosen? In condition records we don't have option to configure a vendor for a particular logical system.
Please advice.
Regards,
Krishna

For Vendors, why are you using LS, u need to use LI.

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

Wrong logical system for partner profile

Dear gurus,
we have been sending ORDERS Idocs for some time now, using to a logical system called MSC_MM_PRD, a RFC connection called MSC_MM_PRD and a port for Idoc processing called A000000003.
Now, we would like to send ORDERS Idocs to another logical system. We created that new logical system called MES001, a RFC connection (MES) and a Port for IDoc processing using that RFC destination (A00000004).
After that we maintained a partner profile for the new logical system MES001 with outbound parameters for ORDERS Idocs. So far, so good.
But then, I had to create a new message type for purchase orders to use that new connection (called ZEDI) and I guess that is where I made a mistake: I copied the existing message type for the old ALE connection and changed some parameters (like name etc.).
Now, when I create a new purchase order and add a message of the new type and save the order, I get an error message:
EDI: Partner profile outbound process code not available
Message no. E0335
Diagnosis
An outbound partner profile could not be found with the following key:
/MSC_MM_PRD/LS//EF/ZEDI//
[u2026]
Procedure
Please check the outbound partner profiles for the assignment of the process code:
As you can see, SAP tries to find an outbound partner profile using the old logical system (MSC_MM_PRD) and the new message type (ZEDI) as a key and obviously fails.
Can anyone please tell me why SAP uses the old logical system and how I can change that?
Cheers
Alicia

Hi,
problem was, that we had not created a proper distribution model for the message type (BD64). After we did that, it worked fine.
Cheers
Alicia

Ale, partner profiles

Similar Messages

Maybe you are looking for