New Logical System for every BPM in R3?

Do I need to set up a new Logical System in my R3 system for every BPM in XI that sends IDOC to it?
I need several BPM to split messages which I want to send to a R3 system. When I configure the scenario, the BMP is imported to the Configurator and the Adapter-Specific Identifiers need be added. A Logical System must be entered for the IDOC adapter. This Logcial System must be unique.
Is it possible to have several BPM without setting up a logical system in R3 for each of them?

Hi Elling,
You can overwrite the logical system name in the receiver agreement. If you select a different system (from the SLD) as Sender Service, the IDOC will be send using the logical system name of this sender service.
What we normally do is, set the sender service for a BPM to the original sender service.
Regards,
Christiaan Schaake

Similar Messages

Creation of new logical systems in IS Retail

Hi All,
"For every new store opened, create one Logical System"...i have come across this sentence in 1 of the documents which spaeks about creation of logical systems
So should i create one Logical System for every store and if i am sending Gift Vouchers to POS so should i create Logical systems for it
Regards

Hi,
Logical system is a System in which applications sharing a common data basis run. In SAP terms, a logical system is a client in a database. Messages are exchanged between logical systems.
Now the context you are talking about is not clear. Can you point out the specific information about the statement
"For every new store opened, create one Logical System"
It depesnds upon the background discription in that document.
Thanks
swarup

Logical system for new client

Hello experts,
I want to copy all users and assigned roles from Quality to the production system.
But as a safety measure I want to copy the existing users and role assignment from production system too one of the test system.
For this I created a new client in test system. My question is:
1) Do I've to create a logical system for this new client?
2) Is there any other step that I need to take beside creating RFC connection?
Thanks in advance

Hi,
>
> 1) Do I've to create a logical system for this new client?
Yes.
> 2) Is there any other step that I need to take beside creating RFC connection?
>
I think this is sufficient. Check this [link|http://help.sap.com/saphelp_sm40/helpdata/EN/4e/2d5dfaedbf11d3b7f60000e8160175/content.htm]
Thanks
Sunny

Can we add new logical system in Entitlement tab in SAP Authentication.

Hi ,
We already Installed and configured sap integration kit and every thing works fine. My question is as of now we connected our sap BW Dev system to BOBJ but we would like to connect to BW Prod System to same BOBJ System. What are the steps we need to follow to do this.
Can we just add the new logical system in entitlement tab of sap authentication in BOBJ 3.1? and import the roles and login to BOBJ USING THE Newly added SYSTEM Credentials. Thanks in Advance.
Thanks,
SK.

Hi Ingo,
Thanks for the information.
Are there any specific steps you need to follow when you are adding one more system to sap authentication. can you please give the steps we need to follow to setup this in right way. Thanks in advance.
Is there any thing we need to configure on sap side other than sap logon ticket parametre. If you can please provide the steps it will be great. Thankyou very much In advance.
Thanks,
SK.
Edited by: Vallabhaneni SK on Jul 14, 2009 8:53 AM

Creating new logical ports for WSDL with several port types not working

Hi all,
I am trying to integrate some BODS webservice into the BPM. I am using CE 7.2 Kernel Version: 7.20.3710. When I am trying to assign a provider system in the application configuration I get following error:
The provider system successfully found the needed service, but its wsdl is without webservice policy. Thus the generated client configuration might not work because of different configurations between service and client (most probable a difference in the security settings). Either assign a provider system with access to wsdl with policy or manually create the client configuration.
The regarding provider system is using a communication profil where the authentication method is set to "none". Normally this configuration should work, but it isn't.
So I started to create new logical ports for each port type. But then I get the error:
Port type name of loaded WSDL does not match the port type name of the Service Reference.
I checked already the port type names in the WSDL but they are 100% the same. What I found was that the configuration is always trying to use the first port type in the WSDL. So I am not able to configure the other port types in the service group.
I also tried to do the same thing using a WSDL with just one port type and surprise it is working...
I hope somebody can help me out
Thanks in advance
Andy

Hi Andy,
Please check this Link: https://cw.sdn.sap.com/cw/docs/DOC-45012
Regards,
Naresh B

ALE logical systems for business service or process

Hi,
I am trying to send an IDOC into my R/3 system. It is the same IDOC type that I have sucessfully sent out to parties. All the config is in place for communicating with the system, because I have sent others IDOCs in the past. However, they always were sent from another R/3 business system. They processed sucessfully.
I am now trying to sending IDOC's from a BPM,as well as, from a business service. They are under the "With Party" section of the directory. These obviously do not have logical systems, so when I try to send the IDOC I get
"Unable to convert the sender service Purchase_Orders to an ALE logical system", where purchase_Orders being the name of the business serice.
How can I handle this problem?
Should I hard code values somewhere?
Which ones?
I have read the other posts for the error above, but my situation seems to be different.
Help!
Chris

Hi,
To solve your problem, here my solution:
1/ In your Business Process of your ID (configurator), go to menu "Service > Adapter-specific identifier" and in the part "IDoc Adapter", write your Logical System.
2/ Create this Logical System on your target system (R/3).
WARNING: XI allows you to used a Logical System for only one service (Business Process). Thus, if you are several interfaces, you must used different Logical Systems.
Mickael.

Wrong logical system for prod categories

We had made a client copy and now the logical system name of R3MATCLASS in t.code COMM_HIERARCHY is still pointing to the old client; How can change we change this to the New client ?

Hello Rahul,
In case of client copy, you have to run transaction BDLS in order to convert old logical system name to new logical system name.
In this way, all tables containing reference to old logical system are updated with new value.
This should be true for logical system assigned to your product categories (table COMM_CATEGORY ).
Regards.
Laurent.

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

Internal order - Error - Different logical system for order

Hello all,
I try to send IDoc (INTERNAL_ORDER) from system A to system B.
I have done:
- BD64 / WE20 / WE21
But after having customizing I have got following error:
Different logical system for order xxxxxx
Message no. 2075ALE001
Diagnosis
Internal order xxxxxxx already exists in system B. Its master system B is different from the master system A of the new internal order to be distributed with the same order number xxxxxxx.
System Response
Internal order xxxxxxx with master system A cannot be distributed in system B.
Procedure
Check customizing for ALE for internal orders.
How to solve this?
My aim is to maintain internal order master data in test system.
Thanks for your help.
David

I have found something.
If I change in table AUFK, logical from empty to A (master) and I run IDOC then IDOC has been correctly integrated.
Then: how to define "master"?

Define one logical system for PI or multiple LS for 3rd-party system?

Hi gurus,
We are using IDOC2SOAP and SOAP2IDOC scenario in PI7.11. My question is regarding the logical system(or partner profile) on R3 side. We have two 3rd party system:A and B, so we have two choices.
1. define one single logical system for PI integration server;
2. define two logical systems for A and B.
For choice 1, it seems we can only use one business sytem or business component (business service in 7.0) as the two 3rd party system, especially for SOAP2IDOC scenario.
For choice 2, it seems we have no restrictions.
Is it correct?Any help will be appreciated.

technically you can use both options.
The question is - do you want all the IDOCs in your R3 system to appear as though they were sent from the PI?
What if a lot of 3rd party systems were sending the same IDOC (for example - ORDERS) and you want to investigate only those who were sent from system A?
I like it configured that every system will be identified by a name I give it.
I just use the IDOC communication channel checkbox of "Take Sender from Payload"
or use a different service in the IBC that has a different logical system configured in its Adapter specific identifiers.
Hope it helps,
Imanuel Rahamim.

Logical systems for ALE

HI all,
I'm configuring for an IDoc to be generated and downloaded to a file via a file port.
This IDoc is of message type PAYEXT.
The file is to be sent ot the bank via the meansa of third party software.
Do I have to create logical systems for these? Or only the outbound logical system?
Do I also need to set up the distribution model , and if so, how far do i need to set it up?
Points wil be awarded. Thanks!

Hi
Use BD64 Tcode to setup distribution Model
Define the 2 logical systems.
see the flow:
Outbound:
Step 1. Application document is created when transaction is saved.
         2. Message control is invoked.
         3. Messages are processed by system.
         4. Messages are Edited (if desired).
         5. Output (ALE / EDI) is checked
         6. Validate against Message control record from Partner Profile
         7. Application Document is saved.
         8. Entry NAST table is created for every selected output program
              along with Medium & Timing.
         9. Check for Process Immediately .
                 If (yes)
                   Determine Processing Program from TNAPR Table.
                 ELSE
                   Execute RSNASTED Program.
       10. Read Partner Profile to determine Process Code.
       11. Process Code points to the Function Module & Invoked.
       12. IDoc is generated.
       13. Check for ALE Request.
                    if (Yes)
                        Perform Filters, Conversions, Version Changes etc.
                    Else.
                        IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
        2.   Subsystem calls Functional Module                                 EDI_DATA_INCOMING from startRFC program.
         3. Data in Control Record is validate against the Partner                       Profile.
        4. IDoc is generated in Database and syntax check is                      carried out.
        5. IDoc file is deleted once file read.
        6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
                   7. Check for Process Immediately.
               If NO
                 Execute RBDAPP01 Program
               Else
                  Read Process Code from Partner Profile
                       Process Code Points to Function Module
                 Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
Reward points if useful
Regards
Anji

Same logical systems for two environments productive

Hi gurus.
I have a question for ALE
There are two production systems a copy of another, who want to connect both to configure the ALE, but by mistake, both systems were the same logical system when they made the copy. Since this change takes months. At the moment I can not make this change in BDLS because it is a productive environment.
When trying to configure the ALE, I am have problems with the logical system name, although one of the settings I gave it another name when you configure the transaction BD64.
Guys, what I find solution to configure the ALE, without changing the logical system to a productive environments ??????
Regards,
Desiré

Hi Mark, thanks for the replay.
I understand also that the solution is to execute the BDLS to change the logical system and convert all tables to new logical system.
I don´t know how the process copy for both system productive.
The problem is that both environments are connected to BW, and other applications and they opened an OSS note to SAP consulting and and the answer given is that they did not recommend changing the logical system.
I thought if there was another way to configure ALE without having the problem of changing the logical system environments.
Regards,
Desiré

Logical Systems for client 000 and 001

I've just install solman 7.0 ehp1 sr1 and am going to create a new client from 001.
Do I need to create logical systems for clients 000 and 001?
Do I need to creat rfc's for these?
Thanks,
Daniel

no, no need.
you will create a logical system name for the copied client (such as 100)

Logical System for RFC-Business system?

Hi,
I want use RFC adapter for my scenario like File to RFC.
The query is like, is there any importance to use Logical system for my Business System which is using for my RFC Adapter in my communication channel.
Regards
Gopi

logical system name is relevant only for Idocs, but it is always a good idea to maintain the technical and business systems with all the information you can provide.
you can check the logical system names of ABAP application servers at bd54 tx code.
Regards,
Henrique.

Logical system for client 001 for SAP NETWEAVER ABAP TRIAL VERSION for BI

Hi,
I have installed SAP NETWEAVER ABAP TRIAL VERSION for BI. In that I have to create logical system for client 001. I have taken a list of available clients from the abap R3 side. Here is a list of it.
Clients View
Cl. Name City Crcy
000 SAP AG Konzern Walldorf EUR
001 Auslieferungsmandant R11 Kundstadt USD
066 Test EarlyWatch Profiles Walldorf EUR
I cannot get inside the BW side for it asks me to create a logical system for client 001. What to do?
Kindly help me.
Kannan

hi,
? First log on to SAP R/3 server connections Go to SCC4 in R/3 & in Scc4 BW server. A screen opens in that logical name of the system would be opened in both (R/3 & BW).
? Take notepad in it save .R/3 & BW logical names go to R/3 & click SM59 to create R/3 connections click then a screen opens gives BW logical name in RFC Destination option & give connection. type 3 & give some description & then press enter.
? You will get another screen under it then at target host gives BW server name we will get it from BW logon change ID, IP address option & give the system no. The system no go to logon pad just drag it then you will see the name.
? Then click on log on securities go to log on give BW server details like No, client user Password. Then save it then click test connection tab if there are errors then it gives yellow color if they are no error the whole thing come as white.
? Then click on the Remote Logon then we go to BW server give RFC SM59 & click create. Then give the server name which is at the bottom right corner give it then give the no, name, password in logon Security save it & test connection & then remote logon.
? R/3 - B W - R/3
? Logical connection source system connection is used to transfer the data from R/3 to BW. Go to BW system& click RSA1 go to source system option go to top to the source systems right click on it. Then click create then a screens opens then.
? PC ?Flat file , DB ? Database
? Select the option manual then a screen appears RFC Destination, Logical source name then click OK then it goes to opens other screen save it test connection then remote login then it go back to the then a screen opens then click only activate.
? BW ? RS1 ? SOURCE SYSTEM ? CREATE MANUAL AUTOMATIC CELL
? R/3 ? Test connections login ? back ? replicate method ? active data R/3 Source system you will able to.
hope it helps u
Ramesh

New Logical System for every BPM in R3?

Similar Messages

Maybe you are looking for