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

Similar Messages

Adding BW 3.50 in logical system problems!!

Hi All
I am trying to create a landscape for our BW systems and I cannot add our BW.3.5 systems as on each of the elements I get the message
'No system found for this product/main instance'
I have also looked and can only find BW 3.1. In SMSY i can see BW under SAP Netweaver.
Can anyone help or point me in the right direction?
Thanks
Phil

This might be an issue with missing RFC Connections. Verify in SM59 whether the RFC destination for BW 3.5 is correctly pointed. Then in TCODE: SALE verify if the Logical System is defined and the client is assigned to Logical System.
Thanks
Sudhan Shan

Unable to convert send system to ALE logical system

Hi Expters,
I am doing FILE 2 IDoc Scenario as follows...
Created 1 BS for sender as Third Party...
Created 1 BS for receiver as WebAs ABAP...
I did everything perfect in IR and ID. But I am getting error in end to end testing. I am placing file in my local drive and the file has been picked up correctly.
And also I can see my Logical System name in ID(Adapter Specific Identifiers) towards my receiver BS. But There is no logical system is displaying for the sender BS in ID.
Still I am getting Error: Unable to Convert Sender System to ALE Logical System...
I have followed blogs and wikis but not successfull...
Do needful in this regard...
Regards,
Basha.

Hi,
Refer this link
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
Problem Unable to convert the sender service to an ALE logical system
http://wiki.sdn.sap.com/wiki/display/XI/UnabletoconvertSendersystemtoALElogicalsystem
Regards,
Nithiyanandam

Party/Receiver determination/agreement with logical system

Hi all
I have gone thru various messages in the forum dealing more or less with the issue, but haven't really found an answer to my problem yet.
XML orders from a Web shop are sent to XI, which I am mapping to an IDoc of type ORDERS.ORDERS05 to be sent to the SAP R/3 backend system. The partner profile in the backend system is defined as a logical system because (a) even though the Web shop is for a closed user group of known customers, I could not possible create a partner profile of type KU for every of them, and (b) I need to do some special stuff for IDocs of this order process which is triggered by a separate process code.
My plan in XI configuration was to create a new scenario and setting up either two parties or one party and a service without party (with a business service). I have tried both ways, but I am not getting it to work. The main reason for that is because of "Unable to convert sender service xxx to an ALE logical system". The "standard logical system" is used in another scenario already, and because of the special processing in the backend, I would like to keep it separate by a logical system defined for this process only anyway.
Posts with party definitions and logical system problems exist already, but I haven't really found a applicable answer. Can something be done in the header mapping (which I am not so familiar with yet) to get one or the other way to work, or is there another "good" way completely to handle this?
I am a little bit lost right now, and would appreciate your feedback. Thanks,
Daniel

Hi Michal
Thanks for your feedback. I have implemented the scenario anew based on your input, and other information that I've found. I've got a working solution after playing around with the settings for a while, and is as following now:
R/3:
System id: D01
Client: 200
WE20: Partner Type LS
...Partner no.: XI_ABC
...Parter type: LS
...Inbound message type: ORDERS
SLD - Technical system:
Technical system type: Third-Party
Name: XI_ABC on xy01sys01cs
...Installed products: SAP R/3 ENTERPRISE, 47X200
...Business systems: XI_ABC
SLD - Business system:
Business system type: Third-Party
Name: XI_ABC
...Related integration server: XD1
Integration Directory:
Scenario: CSC_ABC_ORDER
...Party: PP_ABC_SYSTEM
......Business service: BS_All_Data
......Communication channel: CC_S_File_ABC_Order
......Adapter type: File
...Party: PP_SAPSYS_ABC
......Business system: XI_ABC
......Adapter-specific identifiers: Logical system XI_ABC
......Communication channel: CC_R_IDoc_To_SAP
......Adapter type: IDoc
......RFC destination: D01_200
......Port: SAPD01
......NO Apply Control Record Values from Payload
......NO Identifiers
...Service without Party:
......Business system: XI_ABC
......Adapter-specific identifiers: Logical system XI_ABC
...Receiver Agreement
......Sender party: PP_ABC_SYSTEM
......Service: BS_All_Data
......Receiver: PP_SAPSYS_ABC
......Service: XI_ABC
......Interface: ORDERS.ORDERS05
......Receiver communication channel: CC_R_IDoc_To_SAP
......Sender service constant: XI_ABC
......Receiver party constant: <space>
Once again, thanks for your input.
Regards,
Daniel

Problem with logical system name

Hi All
We are facing problem when connecting Ecc 6.0 and BW
When i execute the RSA 1 transaction, i am getting the following error:
Logical system name has been changed for this system
I raised this issue to SAP.
I got the following reply:
Please see if the RSADMIN table has the correct logical system in BW.
If the logical system name here is incorrect, use report
sap_rsadmin_maintain to change the logical system name.
We reffered the Table RSADMIN, but couldnt identify which field has got logical system name.
Then we executed sap_rsadmin_maintain program in se38, but dont know what to enter in value and object field.
Can anyone help in this regard
Thanks in advance
Regards
Rak

Hi Lars,
I would start RSA1 in debugging mode. Try to establish which check is giving you this message by e.g. trying to set breakpoint at message.
Like this you can at least check which entry must be converted in order to be able to proceed.
Best regards,
Olav

Problems with CIF (Logical system not assign to BSG)

Hello,
We are sending all master data from ECC to APO. We set up the CIF in DEV and all worked fine. But when we try to send the data from ECC to APO in QA an error appears. It says that the logical system is not assign in the BSG. Apparently the configuration that we have in DEV is the same that we have in QA. The logical systems in all instances (DEV & QA) have the same name. Could this be the problem?
Thanks,
David

Hi David,
1) Check whether BSG is defined in customisation under the below
link
SAP - Implementation Guide > Integration with SAP Components
     > Integration via APO Core Interface (CIF)    >
    Basic Settings for Creating the System Landscape   > Maintain Business System Group
2) Check the BSG is assinged to the logical system under the
spro transaction
SAP - Implementation Guide > Integration with SAP Components
     > Integration via APO Core Interface (CIF)    >
    Basic Settings for Creating the System Landscape   >
Assign Logical System and Queue Type
3) Check BSG is showing in APO material master for a location
product under "Properties" tab.
Regards
R. Senthil Mareeswaran.

Problem in populating data to Logical System field

Hi All,
I am extracting GR data through Generic extraction. I am created a view using four tables MSEG, EKBE, EKKO and T001. I have a field LOGSY (Logical System). This field is in EKKO table. My problem is LOGSY field have no any data. I have to write a routine to populate data to this field. Can anybody plz tell me the code?
Edited by: Kasi Viswanath Aurangabad on Jun 18, 2008 7:50 AM

Hello,
the code is:
SELECT SINGLE logsys
FROM T000
INTO your_variable
WHERE mandt = sy-mandt.
Assign points if useful,
Best Regards,
Maciej

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

Hi to All..
I'm facing a problem in one scenario File to Idoc .. I got this problem
"Unable to convert the sender service to an ALE logical system" in pipeline Call Adapter.
I check this blog but the problem persist . /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
Also I have another scenario in other Software Component Version SCW and the Idoc works correctly..
I wonder if I miss something
this the trace
<Trace level="1" type="T">----
</Trace>
- <Trace level="1" type="B" name="CL_IDX_IDOC_SERVICE-ENTER_PLSRV">
<Trace level="1" type="T">Pipeline Service ID: PLSRV_CALL_ADAPTER</Trace>
<Trace level="1" type="T">Get Information from IS-Header Objekt</Trace>
<Trace level="1" type="T">Get Information from SD-IDoc-Endpoint</Trace>
<Trace level="1" type="T">Sender and Receiver after Header-Mapping</Trace>
<Trace level="1" type="T">Sender service Sys_XXX</Trace>
<Trace level="1" type="T">Receiver service Sys_EDV_XXX</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
Edited by: Luis Ortiz on Jan 25, 2010 3:37 PM

Hi,
in order to use only one logical system (PI's) in we20 in ECC and not as many as you have sender systems
Regards,
Michal Krawczyk

Problem: logical system has been changed once it has already been assinged

hai,
we have started ebp configuration with a fresh client.and we assinged logical systems,but unfortunately someone has worked in the same client and made his own logical name...but later in console transaction the system promts that you have no backend rfc connection.my senior told that someone has changed..i tried to rectify in smoeac trx....but the system cannot takes the receiver logical id....plz tell me anyone how to solve my problem...hx in advance

Hi
Please check first in scc4 what is the logical system for your client . Ask your administaror to broadcast a message not to change a logical system to every one.so that everyone uses only one logical system for one client.
regards
Muth

Regarding problem while assigning logical system

Hi Friends,
I had a problem while assigning logical system to the client where in both of my systems are having same client number which belong to 2 different systems.
while assigning the sender and receiver logical system to the same client i am facing problem stating that an entry has already been made for the same key.
could any one plz give me a clear idea...while assigning logical systems (cross clients) for 2 different systems having same client number.
Regards,
Madhu

Hello Madhusree,
I'm running with same problem. I've created two logical systems and assigned them to two different clients. But here pops up the issue while generating partner profiles, throwing error "No active plan version exists". Later when I researched about the issue, I came to know that T77S0 table doesn't have any entries regarding plan versions. Basically, I created two clients by doing "client copy" from source client (800 & 100). And I could see plan version entries in the T77S0 of client 800. So, I thought of assigning just defined logical system to the source client 800 itself. But it throws error saying "entry already exists"; as client (800) is already assigned with other logical system.
By coming across your post, gives me leap of hope that two logical systems can be assigned to same client. Could you please share me those troubleshooting steps concerning this issue. Points will be awarded.
Regards, Anil.

OCI Catalog for Vendor problem : Logical system for catalog not maintained

We have set up an OCI catalog with on of our vendors. This works fine untill we transfer shopping basket data from Vendor sysem into our SRM-system (SRM5.0). Then data is not being transfered and Vendor Webshop screen remains 'open'.
in SLG1 i have found an error "Logical system for catalog not maintained. Inform system administrator'
Anyone an idea what the cause of this error can be or what we need to check ?
Thanks in advance

Hi,
I have not seen that error before. However, I think it may have to do with the LOGICAL_SYSTEM OCI field. Can you check if your punch-out catalog vendor is populating that field? Also, check if you have the correct BP# populated in the catalog configuration and the LOGICAL SYSTEM Field on the define External Webservices is blank.
SG

Problem with RBDMIDOC in executing for diff logical systems

Hi ALL,
We are using message type HRMD_A and we have configured two logical systems using that message.So when we execute RBDMIDOC to generate idoc for change pointers it triggers idocs to both the logical system which we dont want.Is there any other program apart PFAL which does the same job of RBDMIDOC and we can give logical system as input parameter
Thanks
Bala Duvvuri

Vijay,
we cannot have the scenario which I mentioned unless we develop a custom program from scratch that accepts logical system as input parameter
Thanks
Bala Duvvuri

Problem converting Integration Process to ALE logical system(acknowledgmen)

Hello,
I have a scenario where a sender SAP system sends an IDoc via an Interface Mapping to an Integration Process.
This worked perfectly fine on our development environment, but after transporting the scenario to our quality systems I got the following acknowledgement error:
Unable to convert the sender service name of integration process to an ALE logical system.
What could be the reason for this? We have a logical system on the sender SAP system set up for the XI system itself but not for the Integration Process.
We also use SYSTAT IDocs and there we set the the logical sender system name to the logical system for SAP XI and not for the integration process.
Is this also necessary for acknowledgements? Where could this be done. Strange thing is that it works perfectly fine on our development environment.

I raised the same question a few months back.Answer to this question is in the same thread.
Idoc Acknowledgements - Logical System Name
You will have to select option "Restore Original Parties for Idoc Acknowledgments " in the Acknowledgment Idoc adapter.
Regards
Bhavesh

Logical System in file 2 idoc

Hi
I am developing an scenario of file to idoc.
My problem is, when it is generating the idoc in target system, the Parner Number in control record is filling with the logical system name given when creating the business system.
I tried changing the logical system name with actual partner number which I want but giving an error ' The selected integration server already has a business system with logical name "pidclnt001". Select a different integration server or change the logical name. '
Can anybody advice me, is it not possible to create two scenarios to send same Idoc to same system ?
Regards,
Shylesh

Hi Shylesh !
You need to enable the header mapping option in your receiver agreement to overwrite the Logical System name that is sent to the R/3 destination system...which now is the Logical System name linked to your sender system (info is in SLD if is a business SYSTEM or in the Adapter Specific identifier attributes if it is a business SERVICE)
You cannot have more than 1 business service/system with the same Logical System name...but you can overwrite the sender logical system name that arrives to the destination R/3 system using the header mapping section of the receiver agreement as noted above.
Regards,
Matias.

Already used Logical System in Business Service?!

Hi, well i am facing a JMS2IDoc-Scenario.
As sender i configured a Business Service (K15) with the CC_JMS. The receiver is a business system (HRT) with the CC_IDoc.
While i test the scenario i received following error:
"Unable to convert sender service to an ALE logical system"
Thats fine so far, therefore i checked the Adapter-Specific Identifiers and entered the Logical-System name. This is already in use at the business system (HRT) because of some CC for other Scenarios.
Now there is the problem that i can't use this logical system name at K15, no idea why.
Because of not having the technical details of the source-system (JMS) i choose to use business service. Is there another idea?! Party?!
br, Jens

Hi,
The issue is with the fact that this Logical System Name has been assigned to another Business System ( say Buss System X) .And you want to use this same Logical System Name for the sender JMS service( Buss System Y) as well , correct?
Solution is,
In the Receiver Agreement , Select Header Mapping and for the Sender Servicce, select the Correspodning Sender Service ( Sleect Buss System X )to which the Logical System Name is assigned.
Now in the runtime this will be used as the Sender Service from which the Logical System Needs to be taken.
Regards
Bhavesh

Logical system problem

Similar Messages

Maybe you are looking for