PI 7.4: wrong logical system

I am configuring a managed system (SAP Netweaver 7.4) which will be used as PI Development system. However, in step 10 "Create Logical Components" (Solution Manager 7.1), the development system that appears is BWD:001, which correspond to another system. I think the right system to show should be PID:001
How could I fix this? and Thanks in advance...

Hi Reynaldo,
The logical system can be viewed in tcode BD54. Not sure if you should change it, please consult with your Basis
Regards,
Mark

Similar Messages

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

Reg: Table name where logical system name will store in R/3 and CRM..

Hi
We are trying to replicate the sales order from CRM 5.0 to ECC 6.0. we mainatined publication, site, subscription and rfc connections. When the sales order is created in the CRM the BDOC is getting posted but it is picking up the wrong logical system which we were using earlier. Due to this wrong logical system, out-bound queue is getting generated in CRM but In-bound queue is not getting generated in the ECC.
Can anybody tell me where (in which table) we need to modify the things for getting the correct logical system.
Regards

Hi,
In CRM: look for the table CRMMLSGUID. This should have the logical system name of the R/3 that it is connected to CRM and also the GUID. To check if the GUID is correct cross check with GUID from R/3 table CRMPRLS.
In R/3: look for the table CRMRFCPAR. This will give you all the RFC connections that R3 is connected to. If you want to check whether the CRM RFC value is defined correctly compare it with RFC destination in the Administration Console (smoeac) from CRM.
If the entries are matching then the systems are connected correctly if not you need to look at the RFC destinations from SM59 transaction.
Hope this helps.
Thanks,
Karuna.

Use and impact of the logical system (SCC4)

An error has been made in our SAP system (production environment), transaction SCC4. The field «Logicial system» has been changed from «PRD460» to «QAS460». It has been left this way for few weeks and when we realized the mistake, we changed it back from «QAS460» to «PRD460».
For few hours, the document numbers in MM (t-code MIGO) were generated, but were not found in t-code MB03. We were able to generate them manually in t-code SM13 and the problem was solved.
What is the use of the «Logicial system» ? What could have been the impact on our database and on the integrity of our system of having the wrong logical system set to our production environment for few weeks ?
Thanks.

Hi,
Logical System Names
When data is distributed between different systems, each system within a network has to be clearly identifiable. The u201Clogical systemu201D deals with this issue.
A logical system is an application system in which the applications work together on a common data basis. In SAP terms, the logical system is a client.
Since the logical system name is used to identify a system uniquely within the network, two systems cannot have the same name if they are connected to each other as BW systems or as source systems, or if there are plans to connect them in any way.
Although SAP does not recommend that you connect test systems to production systems, a test system can have the same name as a production system. This makes copying production systems to test systems a lot simpler.
You are only allowed to change the logical system name of a system if the system is not connected to any other systems, because changing the logical system name would render all the connections to other systems useless.
Anil

R/3 Logical Systems in BW

Hi All,
I have an idea that we have to create logical systems(SALE) for all BW clients and R/3 clients in BW system. After that, we will assign the BW logical systems to the respective BW Clients in SCC4. But we are not using the logical systems of R/3 system in BW anywhere(please correct me if I am wrong). Then what is the point in creating the logical systems for R/3 in BW?
Thanks,
RPK.

Hi RPK,
I think here you are getting confused..
You have to create logical system for R3 in R3 system only , and Logical system for BW in BW only.
The name you used for the source system (logical system) must be used again for the creation of the source system in the Administrator Workbench for the BW and vice versa..so that BW and R3 can understand each other...
I hope i am clear to you now ..please let me know If I am not....
Regards,
BRB

BDLS updating logical systems in CIF models?

Hi
The BDLS tool can be used to update logical system names in systems. As I understand this tool is often used when copying systems (Production system to Q system for instance).
In a situation where you copy the productive system to the Q system:
Does anyone know if BDLS is capable of updating the logical systems in the generated CIF models that you get copied from the productive system? In this case you'd get a big chunk of models that point to the wrong logical name. If you could get the target system changed in the generated model then you could save a lot of time in generating and activating models.
Any comments much appreciated
Simon

Hi,
I am not too sure if this thread is followed. I was looking for some info where we had a similar issue recently when we did a production refersh to Quality and all our integration model variants are pointing to our production system.
Our basis team has taken all the necessary steps like BDLS etc, but we had this issue. I dropped a message to SAP and they gave a report name RCIFVARIANTCHANGE to change the logical system name from old one to the new one for CIF variants.
Thanks,
Murali

Local logical system is not defined when tried to create new maint. trx.

Dear Experts,
I encountered this message "Local logical system is not defined" when I tried to create new maintenance transaction in DWSP (at Maintenance Optimizer of Solution Manager).
This message kept on appeared even though I've created and assigned the logical system at SALE.
Does anyone know what went wrong?
regards,
Abraham

Hi
there are workarround suggested to solve this problem
login to your solman system, go to the table T000 and update the logical system name in the field LOGSYS
this vanish the error message.Please try.
Thanks,
Jansi

Logical system problem

Hi Everybody,
I am using nwds for creating a web dynpro for java application which call the bapi to get the flight details. When I deploy and run the application this error is coming :-
<b>'WD_FLIGHTLIST_RFC_METADATA_DEST ' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_FLIGHTLIST_RFC_METADATA_DEST ' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections).</b>
Please help me out.
Thanks in advance,
regards,
Madhu.

hi,
1) The JCO name you have provided must not be defined in the Content Administrator of Web Dynpro.
2) If you know the Jco exist there then there is something wrong in JCO name you have given , Mind you JCO name are case sensetive and should be exactly the ones you defined in Content Admin.
3)Ask basis person to configure JCO or if u hav rights create JCO 'WD_FLIGHTLIST_RFC_METADATA_DEST ' yourself.
After creating it check by clicking on "Test" and "Ping" it should do both of these successfully
hope it helps
regards

Error in the logical system (BW - R3 connection)

Hey guys, i need help, actually i created a connection between BW and R3 system, but i think i wrongly assigned the details to another BW system and now whenever i tried to load the data, it's not being processed.
And i checked and it shows me that the connecetion is between source system (538) and BW (B3T800), though my BW client is BW (BW TEST). so how do you think i can change my background users i assigned while creating the source systems, because i think, while creating the source system, i used wrong background users. So instead of connecting via logical system (BW test), its connecting via (B3T800) to SAP R3 (538).
--> Also i tried changing the Logical system name, as i checked and showed that for my BW client now it has a entry of the BW system (B3T800) and when i tried chnging it, it let me change that, but when i went to the RSA1, SAP doesn't let me access that, saying a message "your logical system has been changed", so can i change the logical system, do you guys think my problem will be solved?
Regards,
Amit Jaidka

I have checked in SM37 taking that request number and when i checked the job log , its showing
5 LUWs confirmed and 5 LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DATA
Lock table overflow
Job cancelled after system exception ERROR_MESSAGE
what is the reason for this termination in R/3.
Thanks

SAP* or DDIC being unable to create logical system in SAP PI 7.1

greetings !
I am not a basis person.
I had freshly installed PI 7.1. I was finding that I am being unable to create new logical systems . I tried logging to both clients 000 and 001 using sap* , ddic , and pisuper . pisuper does not even have the authorization to execute SALE . SAP* and DDIC can excecute SALE but unable to create or assign clients.
I reinstalled my system from scratch thinking i must have errored on something, as creating clients is a very simple task. but even the new PI 7.1 gives me the same problem.
is something wrong with my installation , or there are additional roles/authrizations I need to assign to a user.
regards
rishi

Besides PISUPER other users are also created some of the are PIAFUSER, PIDIRUSER, PIRWBUSER etc. Every user has a specific purpose in a PI system. For activities like creating logical system etc. own id's should be used.
There are couple of guides out there which explains in detail the purpose of all the users in PI system.
Hope this helps.
Thanks,
Naveed

Receiver service ??? cannot be converted into an ALE logical system

Hi,
I am hoping for some help with an Idoc issue in XI version 3.0. The scenario is like this:
Flat file->File adapter->XI->Idoc adapter->R/3
I have configured a scenario in one system like this that works fine. But in the current system I am getting the error message "Receiver service ??? cannot be converted into an ALE logical system" from the Idoc adapter.
As it is XI 3.0, I have set the Agency and Scheme in the destination communication channel to <Service>, ALE#LS and in the destination party, I have created a alternative identifier <Service>, ALE#LS, SYSCLNT200.
I have configured an ALE logical system name in the SLD.
I have cleared the SLD cache in the integration builder.
The ALE logical system name was not in the SLD when the message first appeared, but I thought clearing the cache would fix that. I have not tried deleting the service and re creating it. That is my next step....if all else fails.
Not sure what else I haven't tried.
Can anyone offer any advice?

Thanks Sam Raju for the reply.
On your questions:
1. I checked IDX1 - port for the receiving R/3 is defined as SAPIR1_300 (port: SAPIR1 and Client: 300) and it is mapped to RFC destination of IR1300.
2. Checked RFC destination IR1300 - it is setup as R/3 connection and checked test connection and remote login and both are working fine
3. Checked IDX5 - did find one message (status is successful) corresponding to the file I am sending into R/3 and this entry is an Outbound entry.
Question: Should there be two entries here in IDX5 - one for inbound and the other for outbound?
May be I am doing something wrong here in setting up the interface mapping and endpoints. Anyway when I check the IDOCOutbound in the Soap Header, I see the following:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:IDocOutbound xmlns:SAP="http://sap.com/exchange/MessageFormat/">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>100</SAP:MANDT>
<SAP:DOCNUM>0000000000008002</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>FLIGHT_SAVEREPLICA01</SAP:IDOCTYP>
<SAP:MESTYP>FLIGHT_SAVEREPLICA</SAP:MESTYP>
<SAP:SNDPOR>SAPBXI</SAP:SNDPOR>
<SAP:SNDPRN>PRISM</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:RCVPOR>SAPIR1</SAP:RCVPOR>
<SAP:RCVPRN>IR1CLNT300</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
</SAP:IDocOutbound>
Do you see anything wrong or missing here. SNDPOR is XI port, SNDPRN is the source partner (file) and RCV... information is all the receiving R/3.
I am suspecting that something is missing either here or in the endpoint setup.
Also, in the TechnicalRouting I have this:
- <SAP:address version="20">
<SAP:systemKey>IR1CLNT300</SAP:systemKey>
<SAP:endpointType>IDOC</SAP:endpointType>
<SAP:url>IDOC://SAPIR1?RFCDEST=IR1300&DOCREL=&VERSION=3&SAPREL=46C</SAP:url>
</SAP:address>
Any issues you see here in url?
Also, when I look on the XI server, I do not see these files deposited anywhere- so they are going somewhere (as the status in IDX5 is successful)!
Do I need to activate any queues or triggers anywhere.
Can you please offer advice and help us out.
Thanks again.
Srini
[email protected]

Unable to convert the sender service BS_PARTNER to an ALE logical system..!

Hi All,
File to IDoc scenario.
1. Business system is correct because its working for other scenarios.
2. I checked Adapter Specific attributes in Business service and given Partner number which in maintained in WE20 for the partner in R/3.
3. Refreshed cache.
But still... its showing the below error.
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1>BS_PARTNER</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert the sender service BS_PARTNER to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Any idea what might be wrong?
Regards
Deepthi.

Hi Experts,
Could you please help me to fix this.
SCENARIO: SAP - IDOC -
> XI -
> SOAP Adapter (Webservice)
Workaround:
1. Verified Adapter Specific configurations and its fine with same Logical system in SLD and ALE service.
2. Header mapping in Receiver com channel : Sender service and Receiver Service is assigned
3. Identifier Tab in comm channel details: Its empty - no values.
SXMB_MONI :
Error Details:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1>CAPTOR3_PRU</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert sender service X12345X to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks in Advance,
Sunil.

Unable to convert the sender service PPG to an ALE logical system

Hello all,
maybe anybody can help or give me further information.
I have set up a scenario to send IDOC from a business system ( ERP ) to a business service ( EXT ).
Receiver is a linux system so I use the FTP-FILE adapter as communication channel.
The send-process is so far ok.
Here my tests:
1) exclude the specific IDOC in IDXNOALE table ( means no technical acknowledgment for this IDOC )
     result :
     a) message in SXMB_MONI:   status-flag: processed,   acknowledgment-flag: not in use
     b) message in RWB-Monitor: Sender ERP -->   Receiver EXT   ok
2) But I would like to have a system status.....   here now the problem
    add specific IDOC into IDXNOALE table   ( for request acknowledgments )
    result:
    a) message in SXMB_MONI: status-flag: processed,   acknowledgment-flag:   acknowledgment not possible
                                               --> error message: unable to convert the sender service EXT to an ALE logical system
    b) message in RWB-Monitor: there are now two message,
         first:        Sender ERP -->   Receiver EXT   =   ok
         second:   Sender EXT --->   Receiver ERP =   system error
                         Receiver-Interface is : http/ww.ahlstrom.com/EXT/ MI_IN
   3) furhter tests:
        a) change FTP apdapter channel ( put some wrong settings )
              message in SXMB_MONI:   status-flag: processed,   acknowledgment-flag:   contains system errors
              message in RWB-Monitor 3 messages ( one ok, and two error messages )
         b) changed only the receiver communication channel to HTTP ( other extisting scenario )
              then the acknowledgment works fine wihout errors.
              I'm wondering, but here Receiver-Interface is:   http://sap.com/xi/xI/Message/30/Acknowledgment
Summary: The process works, but strange:
                  message in SXMB_MONI: unable to convert the sender service EXT to an ALE logical system
                  message in RWB: system error
                  No problems with HTTP adapter
Regards,
Reinhard Doeker

Hi,
Addition to the above said by Udo...
for routing the ack back to the sender system you need to create communication channel of type idoc with name as Ack.....
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe?quicklink=index&overridelayout=true
Check the above link section 3.2
HTH
Rajesh

Unable to convert the sender service to an ALE logical system... Urgent..!!

Hi,
Im DOing File to Idoc scenario.
Firstly i check LS name exist or not in BS.. then i found its not maintained.
I edited the BS and provided the required LS name.
and the same has been tested in ID
Business System -> Service -> Adapter Specific Identifiers .
Now i got logical system name in "Adapter Specific Identifiers".
Pressed Apply, save and activate the changes.
But still it is showing the same error.
1. Any idea what might have gone wrong??
2. I need to maintain the
   LS name of R/3 in XI system? and
   LS name of XI in R/3 system?
    Is it necessary?
Waiting for your answers.
Regards
Seema.
Edited by: reddy seema on Dec 27, 2007 1:37 AM

Hi Reddy,
        just mention the logical system name in the Sender Business system or Service ( click on sender business service> Service(menu)> Adapter Specific Identifiers--> specify the logical system name which you configured in R/3 WE20 ..) in R/3 side WE20 you need to configure the Inbound parameters of your Idoc ..
Here sender business system and Reciver Business system logical system names are different.. for checking just go to Services and check the adapater specific identifiers..--> then you   can find the name of logical system.. like that you need to check for both systems.. and both should be different..
try with this option..
Regards
@jay

PI 7.4: wrong logical system

Similar Messages

Maybe you are looking for