Message Type to Logical Systems

Hi all,
in SAP PI 7.1 I have a question for you.
With transaction WE20 (into R/3 system) I find the logical system with each message type (inbound or inbound)
My question is:
Is there a transaction which is the contrary?
That is,for a specific message type , I obtain all the associated logical system?
Thank all
Davide

Hi Davide,
Do you want to see all the logical systems that are associated with a particular message type?
Then you can go to tables EDP12 (Pass MESTYP value to get the logical system in the field RCVPRN where RCVPRT = LS
Regards,
Ravi

Similar Messages

Message type from Logical system

Dear All,
I need develop an inbound where the info is coming from HR system. I found Message Type HRMD_A can be utilized for the development, however im not so sure if the message type HRMD_A is originally exist in my R/3 4.7 or it was being distributed by the HR system previously via BD64.
Please comment on how can i check for it.
Below are the related info for Message type HRMD_A that i found in my R/3 4.7:
Message type - HRMD_A
Basic type - HRMD_A06 (for release 620)
Process code - HRMD
Inbound FM - IDOC_INPUT_HRMD
Thank you.

Hi Atish,
Thanks for your reply. Let me recap my scenario and please point me out if i'm wrong again.
For my case, Message type HRMD_A exist in both R/3 and HR system. Since it exist, then we do not need to distribute from HR again via BD64. Right?
IDOC can be passed from HR to R/3 without any additional config right? Assume partner profile and RFC destination has been configured correctly.
Please comment.

Sending IDocs as 'control messages' to a Logical System

Hi all,
I have defined an external Logical System to where I send Idocs. The Idocs are received and processed by a SAP Java Connector on that LS.
At the moment, when for example a purchase order is created for a specific vendor, a message to that vendor is sent through ALE, and the receiver port for that Vendor is set so that it resembles/is sent to the Logical System.
My question is, is it possible, for example when you create a purchase order, to define the message control in such a way that a regular 'New Printout' (or other message) is send to the Vendor (as it normally would), as well as an IDoc message for that purchase order to the Logical System: so send 2 messages to different systems upon creation of the purchase order .
The main idea is that the IDocs are sent to the Logical System to keep track of the actions done by a user, transparant to the user, so that its actions are logged.
Hope this is clear,
David

Yes, You can do it through outbound IDoc. Create another output types and configure the same from NACE and the processing would be done through EDI.
Then you need to configure the partner profile in WE20 with that output types.
Thanks
Subhankar

Partner type -only logical system?

Hi!
I have a scenario where I want to send an idoc to SAP using XI idoc adapter. It works fine using a partner type "logical system" (LS). But now i would like a scenario where the partner i a type "customer" (KU). I have defined a new business system in the SLD as a sender (just in case) and the partner of course exist in SAP under customers). I have also mapped the korrekt values to the IDOC (sndprt, sndpor and so on) -but these are of course overwritten using the values from the SLD (which only operates using logical system). Is there a way to integrate using a partner of type customer? I have made a similar scenario work using the Business Connector -what is the missing link to make it work in XI?
best regards

Hi Martin,
> I have a scenario where I want to send an idoc to SAP
> using XI idoc adapter. It works fine using a partner
> type "logical system" (LS). But now i would like a
> scenario where the partner i a type "customer" (KU).
This is not foreseen in XI 2.0. You need to wait for XI 3.0, there it will be possible.
Regards
Stefan

Download of PERSO1 message type to external system - Urgent

Hi all,
We are downloading our PP and Service related master data by using TCode CI33 & CI43 (Workcenters, Reason for variance, UoM etc..).
Likewise we need to download personnel data from R3 to external system. The relevant message type is PERSO1.
From the forum we get to know that PU12 can be used for this. But we are not sure how to download using PU12.
Thanks in advance.
Regards,
Vivek K

thanks for the tip but no luck.
My email works fine with the gmail POP account. Its the Exchange inbox (we actually use Scalix, an Exchange compatible mail server) and the gmail IMAP mailbox that i have this problem with.
My guess is that PRE doesnt like IMAP and MAPI (exchange protocol) for some reason.
This is a big prob, i am going to have to return this phone. My speaker is awful too. No one can hear me.

How to trigger EDI output type by logical system

Hi,
I am trying to propose a delivery output on delivery document based on logical system.
I have maintained partner profile by logical system. In the partner profile, i have given the delivery output type and the process code.
I have also maintained condition records for the delivery output.
I would like the system to propose the delivery output not by ship to party or sold to party but by the logical system.
Because i do not want to maintain 3000 customers in the partner profiles, instead trigger the output by logical system.
Please let me know, if anyone has gone thru this situation and resolved.
Thank you in advance.
-Naga

Hi,
First thing you should make sure that, when you create the output type , partner function should have an entry for EDI - LS combination.
Secondly , make sure you have option for EDI transmission on the output type (medium 6).
Third, when you create partner profile for LS, make sure you give partner function as LS, even though SAP gives warning that its not required.
Last but not least, i didnt create any distribution model , because when i created distribution model and generate partner profile, system was not generating the profile properly.
I am not sure, whatever i did was right, but its working for me.
-Naga

ALE: Logical system

Hi
I want to send IDOCS from SAP(client100) to a non-SAP system through an RFC port.
I created 2 logical systems.
100SAP : Sending system
NONSAP : Receiving system
Am i correct to say that i need to assign LS-NONSAP to client100. or should it be LS-100SAP ?
Message was edited by: Giovanni Baumann
Message was edited by: Giovanni Baumann

Hai
Check the following Setting
ALE IDOC
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
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
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Thanks & regards
Sreenivasulu P

Message determination and Partner function LS (Logical system) for PO

Hi,
I have worked in the past with vendors (VN) as partner roles in a PO, with the message to create an EDI outpout to Partner Type: LI (Vendor), and this works succesfully.
Now, the idea was to use in EDI, a Partner Type: LS (Logical system) as a receiver of EDI messages (message types: ORDERS) for inbound Purchase Orders to the Partner.
So, we have set up a respective message condition, with Partner Function: LS (Logical System), in transaction: MN04 (Create Output-condition records).
A. When we use ME59N and create a PO with ref. from a PR (created from a sales order), the message determination works well, it reads the condition set in MN04 (condition records for messages), and creates a message (with output type for EDI , medium: 6, and partner function LS: Logical system). Message is created and idoc is sent to partner.
B. When we try with ME21N, ME21 and we create the PO with ref. to the same PR, either by entering manually the PR in the document overview of ME21N or by selecting the PR (without entering the PR number), i.e with date, the message is not created in the PO.
Company code is assigned to purchase organization, and so is purchase organization to plant.
Any idea why there is no automatic message determination in the case of the transaction: ME21N?
There is a single message condition that is to be read for both cases (trans: ME59N and ME21N).
Note: If I try ME21N, and enter the output type and partner (=Logical System), manually, I receive a warning message :
VN006 (Partner XXXX does not exist for partner function LS). If I accept this warning message, then message is saved- idoc is sent.
However you can not assign a partner function LS to a vendor, in vendor master data, because of message CZ 327 (Can not use this partner role).
Anyone with similar experience? Thank you for your advice.

Hi,
I well understand that the receiving partner can be a partner: Vendor (LI).
I have seen that working.
However, in the Partner Profiles (trans: WE20), the receiver was created as a Logical System (LS).
We want the partner Logical system (LS) to receive the idoc for purchase order (ORDERS).
After that, I think that the idea is that the LS can generate an idoc for a sales order creation that will then outbound to another partner. I think that this is the concept.
The issue is that I have seen that the POs created with transaction: ME59N, have received from message determination (trans: MN04) the message with partner LS (automatically), and the idoc of the purchase order (ORDERS) have reached the partner LS.
The question is why the message determination fails when creating the PO from trans: ME21N or ME21, with reference to the PR. Message condition is the same and message determination procedure is the same for both cases.
There is no issue with customizing for the LS in trans: WE20
(Port processing agent is Active for LS and ORDERS have the proper processing code for application EF).
I hope I am helping more with this.

Logical System is not defined in table SMOF_ERPSH!

Hi,
When i am replicating a material group to SRM system, in SMQ2, the error message appears as 'Logical System is not defined in table SMOF_ERPSH!'.
can any one please let me know why this comes up, i have checked the SMOEAC settings, its fine and the logical system entries are already present in the tabe

Hi,
Can you verify all your settings as per note 720819?
Also under SMOEAC transaction, site attributes for your site type 'CRM' may not have any value. Please define attributes for your SRM RFC destination. Select the correct RFC destination, then click on button 'Get Values'.After doing this, table SMOF_ERPSH should be populated correctly.
Regards,
Nikhil

RFC destination for synchronous communication (message type SYNCH)

Hi experts,
I am trying to configuare ALE settings.waht i did is
My sending & receiving systems are one server with different clients.By using SALE transaction
1.crated logical systems.(LS_800 &LR_810)
2.Assigned those to clients.
3.Created RFC destination
4. Created modelview assign sending & receiving
systems and message type.saved it.
4.generated Partner profile.Here i am getting below problem
Target system LR_810
RFC destination for synchronous communication (message
type SYNCH)
Partner profile LR_810 SYNCH does not exist
Generate partner profile or
specify outbound partner profiles for message type
SYNCH
Target system LS_800
RFC destination for synchronous communication (message
type SYNCH)
Partner profile LS_810 SYNCH does not exist
Generate partner profile or
specify outbound partner profiles for message type
SYNCH
Regards;
Upender.

Hi Shital;
Thanks for your replay;
Still am getting the Same Error;
Thanks;
Upender.

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

Configure logical systems

Hi,
I have shipping data in 4.6c and they migrated to ECC6.0 . In that my requirement is i have to cofigure logical systems using we20 T.code and By using Inbound Parameter i am providing Message type and Process Code.
Regarding this my question is it necessary to assign process code to function module in ECC6.0 OR when i mention process code it will take automatically ?
if how can i configure process code to function module?
Thanks
vijay

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

IDOC - IDOC scenario with different message types

Dear Experts
I will like to have your expert opinion in the following question:
I have an IDOC -> IDOC scenario. Wherein at the destination system I have a message type which does not exist at the source system.
Also the IDOC type at destination system does not exist at the source system.
Let say, I will be creating custom message type at source system (Z****) and will also be creating the custom IDOC type (z****) with the same structure, definition as the destination.
Now my question is, even if there will be different message types and different IDOC types but with the same structure (the segment level definition
and field attribute remains the same at both the system). The difference lies with the names. And I have proper mapping though process code.
Will I be able to receive the IDOC correctly at destination?
Thanks & Best Regards

Hi All
I figured out the answer myself now.
You got to have same name for message type. All of you said this and this is rite.
Coming to IDOC type, I did not really got clear idea on this from this discussion.
But after working on a scenario, I learnt that, you can have different names for IDOCs, but provided that, whichever IDOC type the source system is sending, the same type must exist in your destination as well. Otherwise, system wont process your IDOC. But from mapping point of view, its upto individual how do thay handle mapping inside inbound process code for different idoc types / strucutes.
Lesson learnt by me, ideally try to keep same name for both logical message and idoc type at both source and destination. If possible try to keep the structure level also the same. This is my view, learnt it the hard way.
Cheers
Shane

How do you change message type linked to partner in WE20?

Good Morning,
May please have a piece of info about this subject:
In we20 (partner Profiles) i can see that a partner of type LS (Logical System)
has, as Outbound parameters, the CRMXIF_PARTNER_SAVE Message type.
I want to change that to CRMXIF_PARTNER_SAVE_M Message type and also add another Message type, that is to say CRMXIF_PARTNER_REL_SAVE_M.
Notwithstanding, I am not able to edit the grid.
Am I lacking any of the authorizations? Or is it the wrong place to do that?
Thank you very much
Riccardo

<i>Hai,
you can open tcode we20 and make it in edit mode or other wise you can add a outbound parameter using the add button shown bellow the outbound parameter grid.
regards,
Gopinathan.
</i>
Hello,
this seems the right direction.
Yet, in my right - click menu, I have these choices:
- Help
- Choose
- Back
- Display
- Cancel
- Exit
- Check
- IDoc Output
- Tree output
- Position
- Expand subtree
- Collapse subtree
In the "Edit" menu I have
- Position
- Expand subtree
- Collapse subtree
If I click on "position", I just have a "choose partner" window, but then I do not have the "choose message type" or anything that helps me choose the messages...
Does this mean I am lacking any authorizations?
thanks a lot, Riccardo

Wrong Partner Type in IDoc with message type REMADV

Dear all,
We have created 2 IDocs, one for outbound (first in one company code) and one for inbound (receiving company code) with transaction F110 (message type REMADV, Idoc basic type PEXR2001). However, for the first outbound IDoc we have created, we have the wrong Partner type (we would like it to get type KU (customer)) LS (Logic system).
Does anyone know how to change the partner type from the Idoc generationg?
Many thanks,
Ronny

Hi,
Welcome to SDN.
Please delete the exisiting outbound partner profile (WE20) for message type REMADV which under partner type LS (Logical System) and setup new outbound partner profile for partner type KU (Customer).
Regards,
Ferry Lianto

Message Type to Logical Systems

Similar Messages

Maybe you are looking for