"Cannot Determine Logical System"

"Cannot determine Logical System is an error I am facing in an RFC connection. What changes to the sttings do I need to make to remove this error?

Hi Yogesh,
just check with the below links they may help you.
help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
help.sap.com/saphelp_nw70/helpdata/en/e9/9bc93f92908032e10000000a11405a/content.htm - 22k
www.*******************/2007/05/ale-abap-cross-applications.html - 138k
www.sap-img.com/bc059.htm - 6k
help.sap.com/saphelp_nw04/helpdata/en/da/5990df015b5b43a36f6ce7fa1ee8c0/content.htm - 8k
help.sap.com/saphelp_nw70/helpdata/en/cb/0f3040cbe60d418d7b4373c0cbf84a/content.htm - 12k
thanks
karthik

Similar Messages

How to determine logical system in a routine

Hello everybody,
I want to extract data from a ODS-Object (let's say A) to the other ODS-Object (B).
The A-ODS includes data from different R/3-source-system, where I want to select the data from one R/3-source system into B-ODS. Normally I can use the InfoObject 0LOGSYS (which exist as a key-field in A-ODS) with a constant string ofR/3-source system. But the Problem I we have when tranposting to different BW-System.
My question is: how can I determin the BW-System (logical system in a routine, where I can program the coding more flexible? Is there a field for source system similar to sy-datum or is there a function module ?
Thanks so much in advance!
Van Anh

Welcome to SDN
Check the table RSOSFIELDMAP
Assign points if useful
Regards
N Ganesh

Same logical system name for two productive systems - BW, PI issues

Dear all,
we have a productive system which serves two companies (different company codes). This system is connected both to BW and PI for both companies.
There is a requirement that these two companies must use their own system, so the whole landscape (dev,qa,prd) will be copied to different systems (different server with different system id).
As a result of the above procedure we wll have two different productive systems, as required, but we wll have the same logical system name for the two productive systems, which must be both connect to bw and PI.
However as far as I know:
- we cannot connect systems with same logical system name to BW,PI
- we cannot convert logical system name of the one of the two productive systems as they are productive and so this is not supported.
How can we overcome the problem?
Please advice.

> However as far as I know:
> - we cannot connect systems with same logical system name to BW,PI
> - we cannot convert logical system name of the one of the two productive systems as they are productive and so this is not supported.
Right.
> How can we overcome the problem?
Since you split up systems (or plan to) I highly recommend booking an SLO service (http://service.sap.com/slo). Those people have to the tools and the knowlege to help you. I would not do this on my own.
Markus

SWO1 - No destination could be determined for logical system

Hi there,
I am trying to call a remote transaction via SWO1, but I am getting the following error:
No destination could be determined for logical system TSTCLNT120
Message no. OL860
Diagnosis
You attempted to instantiate an object with the specified logical system within the distributed runtime environment. However, an RFC destination has not been defined for this logical system.
System Response
The object instance cannot be generated.
Procedure
Define the RFC destination or use the local runtime environment.
I go to SW01 --> Type an object name "TSTC" --> Click TEST --> New Dialog window Clicked on the Full key --> Entered the Logical Name for remote system (ECC), and also Entered Key: SU01 --> When I click on the continue, I am getting the above mentioned error.
I can clearly see that it is looking for mapping Destination for that Logical name. Can someone please tell me what t-code or table I need to go and map the Logical Name with a RFC destination?
Thanks in Advance
Kumar

hi
try these links
Re: R/3 Connections in RFC destination node.
Assign a logical system in RFC
Regards
Sajid

Could not determine BW release of logical system 'BWPCLNT100

after a BI systemcopy (production to development) we get the following
error when we run load jobs of type "delta load". full loads work fine
"Could not determine BW release of logical system 'BWPCLNT100'"
even if i start the deltaload from the R/3 system with transaction RSA3
with update mode "C" i get the same error . when i use update mode "F"
it works fine , but that's not the thing we want.
BWPCLNT100 is the logical system of the productive system .
we have changed all the logical system setting to BWDCLNT100 using
transaction BDLS and we have also changed all entries in RSBASIDOC,
RSISOSMAP, RSOSFIELDMAP,.... .
we have done several systemcopies in the past , they all worked fine
and without this error. this is the first copy in BI 7.00 .
are there any loadmodules which have to be regenerated with the new logical system name?
thank you for your help and kind regards hannes toefferl

Hi,
As you said you are getting error after system copy when you are doing the delta load and full load is working fine for you.
This mainly happens due to init disturbance in the source system.
I would suggest you to delete the init and rerun the Init from BW once again.
This should solve your problem.
Thanks
Mayank

No logical system group can be determined for administrative unit &1

Dear GTS gurus,
In Risk Management module when we execute the report "Analyze LTVD Request Relevance of Products" (/SAPSLL/PRE_VD_OPT_ANL_PROD) we sometimes get the error message:
No logical system group can be determined for administrative unit *******
Now I did some googling and found the following website: consolut - /SAPSLL/PRE_VDEC139 - No logical system group can be determined for administrative unit &amp;1 - /SAPSLL/…
It says that in customizing item "Define Administrative Unit Attributes" some assignment is missing but I was not able to figure out what exactly. I compared it with Administrative Units which did not not issue any error messages and customizing looks good to me.
Can you share your insights on this topic?
Best Regards
Greg

Hello Gregor,
Under the Admin Unit attributes, you must have a Plant Group defined.
Is that Plant Group assigned to a logical system ?
(IMG: General Settings -> Organizational Structure -> Define Cross-Plant evaluation (or Define Plant-based BOM evaluation)
By the way, the site you have found is one of the many sites out there that lists the messages available in a SAP system. The same information is available within GTS (Transaction SE91).
Regards.
Mouaz BEN REDJEB

ATP Check Issue - No business system could be determined for logical system

Dear all
Got an issue while executing ATP check on a planned order in product view,
with a message: "No business system could be determined for logical system"
CIF setting wise:
regular business system group maintained and assigned in place,
master data wise:
business system group info fine in product master,
Is there anywhere suggested to check under ATP setting:
category, check mode, business event, check control/check instruction?
Your kindest enlighting is appreciated,
Thank you,
mandy

Dear Mandy,
usually this error is caused by a missing customizing entry:
spro:
Integration with SAP Components
   Integration via APO Core Interface (CIF)
     Basic Settings for Creating the System Landscape
       - Maintain Business System Group
       - Assign Logical System and Queue Type :
Please read the documentation for these two transactions and create the systems.
You need to specifiy there all systems that are in your BSG. The documentation for the customizing of 'name logical system' in APO says:
To enable the transfer of data between SAP R/3 and SAP APO, you need to name both the SAP APO system in which you are working and the SAP R/3 system to which you want to transfer data as logical systems.
I hope this helps.
Regards,
Tibor

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.

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]

BPM--cannot convert sender logical system to ALE

Hi
My Scenario is file-bpm-idoc.. Where i am getting an error saying "cannot convert sender logical system to ALE" for the BPM.
i tried entering the logical system for the BPM in adapter specific attributes but it says logical system is already being used by some other service..
So i tried header mapping in receiver agreement now the messages are failed at the intital stage before entering the BPM only only saying cannnot find recvr agreement..
My sender system BS_EXT_100
BPM IP_calldoc
Recvr system BS_EDCR/3_200
i did the header mapping for recvr agreement of BPM by selecting the sender service and entering "BS_EXT_100"
Where am i going wrong...

solved it myself.. Thanks

Dynamic Determination of Logical System- Transaction Launcher

Hi Friends,
Need your suggestions and inputs on how to dynamically determine the logical system for the transaction launcher.
Our system landscape is like this.
We have one CRM connected to mulitple back end ECC Boxes. Currently, we have created separate TL's fo VA01 ( One each for each back end application ) and provided the same in logical link and controlled the same via business role.
For eg: BROLE1 - LLINK1 having (TL VA01) pointing to ECC System1
BROLE2 - LLINK2 having (TL VA01) pointing to ECC System2
BROLE3 - LLINK3 having (TL VA01) pointing to ECC System3
The above procedure is working fine. But what we are trying to do is, when the end user clicks on the TL link in WEB UI, Based on the assigned business role, it should dynamically determine the back end system and open the VA01 Screen in that system.
I have activated indicator multiple systems in the customizing of mapped logical systems.
In debugging mode, i have tried changing the LOGSYS value @ run time in the handler class.
Any pointers on this would be of great help.
Thanks,
Madhu

Hi,
Try this..
To maintain RFC destination in each business role, there is one functional profile "ERP_SALES_ORDER" where in you can maintain respective rfc destination.
Create z-functional profile's for "ERP_SALES_ORDER" and maintain corresponding rfc destination, later assign these erp sales order function profiles in respective business roles trxn (CRMC_UI_PROFILE).
you can use the below statement to fetch rfc destination whcih assigned to business role via functional profile.
If gv_rfc is INITIAL.
gv_rfc = CL_CRM_IC_ERP_SERVICE=>GS_ERPPROF-RFCDEST.
ENDIF.
Hope this helps.
Cheers,
Sumit Mittal

File2idoc receiver service cannot be converted into ale/logical system

hi
i m working with file to idoc the file adapter is working fine bit\ut wen i checked in
sx_monitor i found the red flag and it shows the error
receiver service cannot be converted in to ale/logicalsystem

Go to the Business System / Service you have maintained for your File.
Double Click ,Business System --> Adapetr Specific Identifiers.
Here, maintain the Logical System name of the Sender System. This logical system name should be the value for which the partner profile
has been created in your SAP system in we20.
The same should also be maintained for your Receievr Business System.
Regards
Bhavesh

Logical system determination

Hi,
how can I determine own logical system.
Thanks.
Marian

U can determine the own logical system using the FM OWN_LOGICAL_SYSTEM_GET.See the example code below :
data : l_ownsys   TYPE logsys.
CALL FUNCTION 'OWN_LOGICAL_SYSTEM_GET'
    IMPORTING
      own_logical_system             = l_ownsys
    EXCEPTIONS
      own_logical_system_not_defined = 1
      OTHERS                         = 2.
l_ownsys will contain the logical system.
Cheers
Nishanth

Scm:Logical system Name is changed. cannot access BW system.

Hi,
plz help me to solve thi problem.
SCM : Logical system Name is changed. cannot access BW system. system throw an error "Logical System has changed".

Hi Raj,
We can create the Logical system name in SALE or BD54 and we can assign the same logical system name in SCC4 for that particular Client.
If you want to change the logical system name after a client copy or System copy. Use BDLS.
Thanks,
Pundari

Cannot find the Recv Logical system in Distribution Model

HI experts,
Im triying a Idoc to file scenario, the logical system for PI and R3 has been already created and assinged for the appropriate clients.
and i ve created the port from r3 using tcode we21 and in PI using idx1 and Idx2. The RFC destination also created for PI and R3 system.. when i created the distribution model using BD64 in R2. when i assigning message type i can give the source logical system and i cant find the Receiver logical system... Also in WE19 i cant find the receiver port (which i created in IDX1 and IDX2)..
Could u tell me how to solve this prob???
Regards
Balaji

Hii Ravi,
Thanks for your reply,
Yes i have created the port (RFC800) idx1 and give RFC destination which points the R3 system.
I have assigned the meta data to that port using tcode idx2.
And I have created port with port name "PORT800" in R3 using we21 and give the RFC destination which points the PI system
when im using the WE19... i gave source logical system as R3 Logical system and receiver logical system as PI Logical system.
now im getting error like "PORT RFC800 DOESNT EXIT IN THE THE TABLE OF PORT DISCRIPTIONS".
Regards,
Balaji
Edited by: Balaji Pichaimuthu on Jul 25, 2009 9:32 AM
Edited by: Balaji Pichaimuthu on Jul 25, 2009 9:32 AM

"Cannot Determine Logical System"

Similar Messages

Maybe you are looking for