BS- Adapter Specific Identifies - Logical System: value is missing

Hi,
I've created a simple scenario in which idoc is being received in ECC (by idoc receiver). my communication channel (i.e., soapSender) is part of my INTEGRATION_SERVER business system. i checked, for the relevant business system the Adapter Specific Identifies -> Logical System values and it was missing. therefore, i had to update the correlated technical system definition (at SLD) and updated required value (i.e., logical system). somehow the value is still missing when i re-check the business system (at Integration Builder).
i took the following actions:
1. delete and re-import BS from SLD.
2. re-start xI
and nothing was changed.
What can be done?
Regards,
Uri

Hi Uri,
>Indeed, the LS was not exits
I do not 100% understand your statement. Plz check AGAIN (in SLD) if the logical system name is still there.
My suspect was that a ABAP job (you can look to it in RZ70) is overwriting the technical system.
Regards,
Udo

Similar Messages

Logical system value in a BAPI

i am using a BAPI, its asking for logical system . How do i know that value ?

Logical system- 'logical system' is used to identify an individual client in a system, for ALE
communication between SAP systems. That's why you see a field for 'logical
system' in the client master data in SCC4 (table T000). You use logical systems
in ALE config - this should be documented further in the IMG guide, or SALE and
BALE transactions.
Check the link
http://www.sap-img.com/bc059.htm
please use Function Modules for this task:
CALL FUNCTION 'OWN_LOGICAL_SYSTEM_GET'...
You can also check the table -
The field is T000-LOGSYS. (Logical System)
Regards,
Amit
Reward all helpful replies.

Logical System for Integration Process

I am getting a error message for my Integration Process: "Unable to convert sender service IP_Kleinschmidt_Shipments to an ALE logical system"
I am confused as to what i need to put in the IP -> Service -> Adapter Specific Identifires ->Logical System.
I won't let me enter either the R3 system nor the XI system.
What value do I need to put here so my acknoldgement can go back to the R3 system?

Use header mapping in receiver agreement to apply a business system as sender of the Idoc message.
That business system must have a logical system aplied and this should be maintained in R/3 as well.
if you use XI system as logical system as IDoc receiver in R/3, then you can apply also XI as sender here.
But you have to load the PI as business system to ID for this reason.
You cannot apply a logical system to the business system, which already used elsewhere.
I discused that issue with the developer a couple of years ago. He told me to use the workaround.

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

Adapter Specific Paramters for Integration Process in Configuration

I want to send the data from flat file to idoc through BPM
While doing configuration do I need to explicitly give Adapter specific parameters(Logical System Name) for BPM(Integration Process) or not?
Is it mandatory to give Adapter Specific Parameters for this scenario?
FILE-->BPM--->IDOC(R/3)
Thanks & Regards
Katta Mohan Reddy

Hi,
why would you require Adapter specific parameters (I assume you mean Adapter specific Attributes) - Logical System should be there through the routing (Receiver Determination). What exactly do you want to accomplish by that?
regards,
Peter

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.

Logical system name in SRM system

We are into SRM version 5.(SRM server 5.5) with the backend system as SAP ECC 6.0 .
The logical system is defined as '0000000050' for backend SAP system . All the systems like CRM and BW uses this as the logical system name for backend system . Recently SRM is implemented in our organization and we have no other choice and have to use the logical system name as '0000000050'
When product categories are assigned in the org attributes , the system stores the back end system as 50 and this is the issue. SAP support mentions that this is issue with logical system naming convention and that need to be fixed . But they fail to understand that the same name works fine in all other systems and also in SRM system except product categories .
Is there any OSS note for this fix. I would like to hear your experiences in this scenario.
Thanks
Mani

Hi Mani,
Logical System names are system specific, hence you have a different name in SRM system which will represent your backend system and this is not at all an issue. As suggested by SAP; '0000000050' is not the best name as per best practices.
You should have a name which should be of the pattern: <SID>CLNT<Client Number>.
Now here is the solution/work around. But be very careful and try this in sandbox system before being carried out in Dev/QA/PRD systems. Please make sure no other users are performing any activity while these tasks are being carried out.
In addition, please read through the ["Set up and system copy of SRM server 5.5";|https://websmp204.sap-ag.de/~sapidb/011000358700000310782007E/SRM50_SetupTranspCopy.pdf] guide before you carry out this activity:
The below activities are to be carried out only in SRM system
I assume SRM & Backend are separate instances
1. Create a new logical system name for the backend system in SRM system as per the standard suggested above.
2. Then use the transaction BDLS, to convert the old logical system name to new logical system name in all the tables.
3. Now, the step 2 ensure the logical system name is converted appropriately in all tables except SRM Org Structure related table.
4. Use the report RHOMATTRIBUTES_REPLACE, for replacing all the old logical system value with new logical system value. Please note while providing the inputs in the screen, there will be a Checkbox field called "Sub-String", you must check this one for all attributes you enter in the report. Then when you execute the report, a list will be display, here you have to select all the rows and click the first button on the toolbar. Only then the attributes will be updated.
Please let me know, if further inputs are required.
Regards, Kathirvel

Clarification Regarding Logical System Names

HI all,
I read the blogs regarding Logical System Name, even I am having the some problems in my system.
For PI system client is 100.
R/3 System Client is 100 is created.
IN PI when I checked the sale->basic setting-> LOgical Settings-> Assign Logical Systems
I found there is only one client 100, and it is having the same logical system name as 'PICLNT100'.
In SLD one Business System is created for Client 100 and having the Logical System Name is 'PICLNT100'.
When I checking in the R/3 system that logical system Name ('PICLNT100') is not there and for r/3 client 100 having the different logical system name.
IN ID when I found the Goto ID->File Buinsess system and Menu ->Services->Adapter Specific Identifiers->Logical Ssytem,
It is different from the SLD logical System Name.
How Can I know in PI, that Logical System is belongs to r/3 or PI client 100,
when I running the sceanrio it is giving error as ATTRIBUTE_INV_SND_SERV while doing the file to Idoc scenario.
How I have to maintain the logical system names in this case?
please help me in this.
Regards,
Sree

hi.
each r3 system has his own SLN (PI,BI,ECC,etc). this name identify each R3 sytem.
http://help.sap.com/saphelp_nw04/helpdata/en/78/217dc151ce11d189570000e829fbbd/frameset.htm
IN ID when I found the Goto ID->File Buinsess system and Menu ->Services->Adapter Specific Identifiers->Logical Ssytem,
to export data of your R3 system to SLD, just do it from TCODE RZ70 in your r3 system, not PI.
once you configure it all data from r3 system is exported to SLD.
if the SLN does not match in Adapter Specific Identifiers->Logical Ssytem, edit the Bussines System (press in the little pencil) go to Adapter Specific Identifiers->Logical Ssytem and prees in the little hand icon. in the SLN in not refresh, go to menu enviroment--> CLEAR SLD DELTA CACHE. and repeat the steps before.
each time you send data to an R3 system and the sender system is a legacy. in your receiver communication channel>header mapping>sender system--> select the PI Bussines system and try again.
hope its helps
Rodrigo
PD: rewards points if useful

Error "Unable to convert the sender service to an ALE logical system"

Hi,
I send I message from XI to R3 and I get the error "Unable to convert the sender service to an ALE logical system" in transaction "sxmb_moni". I've configured the idoc-adapter, as following:
-I have created a business system "r3sys_bs" with a logical system "r3system". This business system is the idoc-adapter. This logical system is also created in transaction "bd54". In the ID I have assigned the business system the logical system (adapterspecific identification).
So, this error still appears.
Can anybody help me please?
Regards
Stefan

Hi,
our scenario is JMS --> XI --> IDoc
so, I have created a business system "jms_bs" without a logical system in sld, that I use for the jms-connection to another software. so, the business system is a "third party".
Then I have created a business system with assigned logical system for the IDoc-Receiver as I in my first posting mentioned.
Which of both business systems need a logical system?
Thanks
Regards
Stefan

How to get the current logical system?

Dear Abapers:
I can't find the logical system value from the table SYST, pls tell me how to get the current logical system name, Thanks!

Hi,
Check with the table T000, the Logical system field name is LOGSYS.
Regards
Thiru

Easy way to send every possible IDoc to a Logical System

Hi all,
With the help of the SAP Java Connector I'm trying to create an application that receives (and further processes) IDocs. The idea is then to walk through a process in SAP, e.g. Procure to Pay (PR, PR approval, Request for quotation, PO,...), and to receive an IDoc after each step of the process.
is there an easy way to enable the sending of all possible IDocs to a specific external Logical System (the JCo). This way the JCo can listen, identify and handle incoming IDocs, and thus reconstruct the process that was executed in SAP with the help of the IDocs.
I can already send some IDocs to my Java Connector, but setting this up for each action or process seems quite a lot of work.
Hope it's clear.
Cheers,
David

Hi,
Understand the query to establish the interface so as to send the IDocs to specific LS (Logical System) which will be connected to external system through JCo.
For Procure to Pay process, external documents (PO,Contract for e.g.) can be sent to external system through output determination process wherein settings can be made to send the output immediately (as soon as document is saved) and output conditions can be maintained per logical system (by maintaining LS as one of the partners) this will also reduce the condition records.
Further it can be achieved to deliver the output to specified folder per document/process wherein Jco will handle further process.In other words create no.of folders per process/document whichever best suits.
Regards,
Kiran

Logical system not updated in the business system adapter specific data par

Hello Guys,
I changed a logical system name in the sld for a business system and that that is not reflected in the Integration directory adapter specific data tab.
I did a cache refresh using :
1) sxi_cache --- Full cache refresh, delta cache refresh
2) Hard cache refresh
3) In ID "Cleared SLD data cahe "
4) Refreshed the exchange profile
But no use
Can you please tell how i can get the logical system name for the business system updated in the Integration Directory.

When you change it in SLD and if not getting replected in the ID...make sure you run the cache again, perofmr the comeplete cache....
there is an option under the adapter specific mesage attributes compare with SLD you can click that, is nthing happening after clicking it?
Run the cache in the ID are there any errors there?
check the RWB cache monitoring is everything green there?

Adapter Specific Identifiers of business system

HI All,
I want to add Logical System Name in Adapter Specific Indentifiers for a business System. I am confused how to do it.. when i go to Service>Adapter Specific Identifiers> the "Logical System" field is completely greyed out i cannot type anything there..i even clicked on the "Compare with SLD" button but couldnt add anything there..Please suggest how to add the value for the Field Logical system Name.
Regards,
Raj

Hi Sitaram,
u can set the logical name in ID as well as in SLD also... check how here
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
regards
biplab
Use a Good Subject Line, One Question Per Posting - Award Points

IDoc Adapter - Logical System - File to IDOC configuration

I have a scenario reading a File ->XI->IDoc in R/3. I'm looking to have the control record parameter for SNDPRN reflect the Environment dealt with. I unchecked the 'Apply Control Record Values from Payload' & 'Take Sender from Payload' boxes but the problem I'm getting is that the system is reading from the business service (IDoc Adapter - Logical System) and feed it in the Partner Profile in the IDOC. This means that I should all the time redefine 3 this Logical System in config before transporting my scenario from DEV/QA/PRD. Any idea how I can avoid this kind of 'hardcode' ?
Thanks

Hi,
Why u r using three different LS can't u use only one LS and send all the IDOCs to same LS. That will ease ur task.
Do let me know why u r going for three different LS.
In the file r u getting any data which will help u to identify that this file is for which LS. IF that is the scenario then u can use the value mapping and based on the value which is coming in file u can map it to the IDOc filed which u have mentioned and in the configuration it will take the respective configuration.
Thnx
Chirag

IDoc Adapter Logical System Empty

Hello All,
For one of our scenarios for Reciver IDoc adapters we are getting the error "Receiver service cannot be converted into an ALE logical system ". On further investigation it seems the logical system stays on editing the Adapter Specific Message attributes option & even after clicking the Compare with SLD Option. Can you please assist us with this issue ? Also sldcheck runs fine but sldapicust gives an error CIM_ERR_FAILED. We recently upgraded our sld and we believe this might be the issue.
Thanks,
Kiran

Hi Debashish & Veera,
The issue has been resolved. When our SLD was migrated to a newer version 1 month ago back our logical system names got cleared. We did not face this issue until yesturday since the logical system names were still cached with the business system. Yesturday a newer IDoc scenario was imported in production and which caused the business system cache to be refeshed and it started pulling the new empty logical system name causing the scenarios to fail.
Thanks,
Kiran

BS- Adapter Specific Identifies - Logical System: value is missing

Similar Messages

Maybe you are looking for