In ale client and logical system

Hi,
do we need to assing logical system to client in ale configuration.
thanks,
Jigar

Hi,
Yes, you need to define and assign logical system for ALE client.
Path: SALE -> Basic Settings -> Logical Systems -> Define Logical System
Path: SALE -> Basic Settings -> Logical Systems -> Assign Logical System to Client
Regards,
Ferry Lianto

Similar Messages

Create a client and logical system for BW

Hi all,
Can anyone show me how to create a BW client?
create a BW client and logical system for BW client.
create sourcesystems for the other clients in BW.
I have follow some documents
B84: BI Connectivity
B03: General Settings BI Integration
But it's not working the data can't flow to BW server.

hi,
check out the following thread's. it will guide you
Connection steps for SAP BW and R/3
Info required while creating source system
R/3 Source system creation error in BW 7.0
regards
harikrishna N

Difference between client system and logical system

Hi all
Can any one explain about the client system and logical system??
When this message type will comes in to picture at the time idoc processing??
Thanks and Regards
Arun Joseph

hi Arun,
I am giving the complete info on idoc.pls chk once.then ur issue will be solved.ok
and to know the diffrence between client and logical system very keenly go thru this link
https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=abouttheclientsystemandlogicalsystem&adv=false&sortby=cm_rnd_rankvalue
IDOC Administration
Step 1: Tcode: WE 46
Setting the Global Parameter for IDOC Interface
Step 2: Maintaing a Logical System
Path: From the ALE Customizing in IMG, choose Sending and Recieving Systems,
Logical Systems, Define Logical systems
Go to Spro transaction
Step 3: Allocating Logical systems to the Client
Path: From the ALE Customizing in IMG, choose Sending and Recieving Systems,
Logical Systems, Assign Client to Logical systems
Go to Spro transaction
Step 4: Setting up an RFC destination
Tcode: SM 59
Path: From the ALE Customizing in IMG, choose Communication, Define RFC
Destination
You can also do the Advanced Settings in the RFC Destination
Step 5: The PORT definition
TCode: WE 21
Path: From the ALE Customizing in IMG, choose Sending and Recieving Systems,
Systems in Network, Asynchronous Processing, Assign Ports, Define Port
Step 6: Generating Partner Profiles
TCode: BD 82
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, PArtner Profiles and Time of Processing, Generate Partner Profiles
Step 7: Distributing the Model
TCode: BD 64
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, Maintain Distribution Model and Distribute Views
Technques for Distributing the Master Data:
Technique 1: The Push Approach
Executing the Process:
TCode: BD 10
Path: from the ALE Main Menu, choose Material Data Distribution, Cross
Application, Material, Send
Technique 2: The Change Pointer Technique
Enable Change Pointers Globally
TCode: BD 61
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution, Replication of Modified Data, Activate
Change Pointers
Enable Change Pointers Globally
TCode: BD 50
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution, Replication of Modified Data, Activate
Change Pointers for Message Type
Specify the Fields for which Change Pointers are to be written
TCode: BD 52
Path: From the ALE main Menu, Choose ALE Development, IDOCs, Change , Define
Change-Relevant Fields
How the Classification system works:
Creating a Class Type
TCode: O1 CL(it is CAPITAL O)
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Distribution using Object Classes, Maintain Class Types
Maintaing Status for the Class Types:
TCode: O1 CL(it is CAPITAL O)
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Distribution using Object Classes, Maintain Class Types
Maintaing Classification Status:
TCode: O1 CL(it is CAPITAL O)
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Distribution using Object Classes, Maintain Class Types
Maintaing Classes:
TCode: CL 01 (it is zero)
TCode: O1 CL(it is CAPITAL O)
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Distribution using Object Classes, Maintain Classes
Allocating classes to the Logical Syatems
TCode: BD 68
TCode: O1 CL(it is CAPITAL O)
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Distribution using Object Classes, Assign classes
to Logical systems
Filering at the IDOC level:
Identify the Filter Object:
TCode: BD 59
Path: From the ALE main Menu, Choose ALE Development, IDOCs,Data Filtering, Assign Filter Objects
Type to IDOC Field
Modify the Distribution model
How Segment Filtering Works:
Configuration:
Configring the segment-filtering technique is a one-step process.Just specify the segments to be filtered
TCode: BD 56
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Scope of the Data for Distribution, Filter IDOC Segments
The Reduced IDOC Type:
The reduced IDOC type allows to get down to the field level and specify the fields a recieving system does not need.
The System still needs the fields, but this has no effect on the recieving system because each field has a null value,
represented by a forward slash(/) in the field.
TCode: BD 53
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Scope of the Data for Distribution, Message Reduction,
Create Reduced Message Type
IDOC:
Complete Documentaion on any IDOC using TCode: WE 60
IDOC Display Tool: TCode: WE 02 or WE 05
IDOC DEfinition components:
Segment Components:
1. Segment Type (E1, Z1)
2. Segment Definition(E2, Z2)
3. Segment Documentation(E3, Z3)
E- SAP Defined
z- Custom Defined
IDOC runtime componets:
control Record:
Data Record:
Staus Record:
First Create the Segments using TCode: WE 31
and then create the IDOC using TCode: We3 30
first release the segments and then IDOC.
Creating a new Basic IDOC Type:
STEP 1: Analyze the Data:
STEP 2: Create Data Elements:
STEP 3: Create Segments:
STEP 4: Create Basic IDOC Type:
1. Execute TCode: WE 30
2. Select the Create new option and enter a description for your basic IDOC type
3. click the IDOC name, and click the create icon.
Enter the segment type and its attributes.
4. Keep on adding the segments as in step 3.
5. Save the basic IDOC type
Step 5: Release the Segment Type and Basic IDOC Type
STEP 6: Transport the Segments and Basic IDOC Type
Extending a Basic IDOC type:
STEP 1: Analyze the Data:
STEP 2: Create Custom Segments:
STEP 3: Create the IDOC Type:
STEP 4: Release the custom Segment and IDOC Extension
Develop the function module for fteching the Data and then inserting the data into IDOC using
EDIDD(for control Record) and EDIDC table(for DATA Record)
Configuring the Systen for IDOCs
Configure an Outboubd Process that uses Message Control
Step 1: Create a new Message Type
TCode: We 81
Path: From the Area menu of EDI, choose Development, IDOC Type/ Message
Step 2: link the IDOC type to the Message Type
TCode: We 82
Path: From the Area menu of EDI, choose Development, IDOC Type/ Message
Step 3: Create a new Process Code
TCode: We 41
Path: From the Area menu of EDI, choose Control,Outbound Process COde
Step 4: Create or Change a Partner Profile
TCode: We 41
Path: From the Area menu of EDI, choose IDOC,Partner Profile
Configure an Outboubd Process for Stand-Alone Programs
1. Create a new message type
2. Link the IDOC type to the Message Type
3. Add the message to the ALE Distribution Model(use BD 64)
4. Create or change the Partner Profile
go through the following site to have screen shots.
http://www.****************/Tutorials/ALE/ALEMainPage.htm
thanks
karthik
reward me points if usefull

ALE - Error - Assign client to logical system

Hi All,
When i am working in ALE [SAP IDES]. In SALE transaction when i try to do ' Assign client to logical system' -
in the second screen 'Change View: clients details' after i give all the details, it's showing error
'An entry already exists in the same key' & the cursor is in the client field [i entered 800 as i m working in client 800],
Kindly help.

Hi,
You did create a client in SCC4.
firstly,
1. did you create a logical system via BD54 and then did you assign that logical system to this newly created client ?
2. did you perform a local client copy to put data into this new client from an old or from a standard client like 000 ?
If you didn't perform above two things, then please do.
Hope it works!!
Regards,
Amruta

RFC and Logical System names

Hello......is it necessary to have RFC and Logical system name for the connected system to be identical?Is there any explanation behind this if thats true....

Hi Gaurav,
It is recommended, but not mandatory, right, Muthuraman?
The system uses some transactions to determine which RFC will be used for the communication between one system and another, for example, in transaction 'Define backend systems' in SPRO, you can define that the current SRM client has an ECC backend system named X and the RFC destination for this X system is Y (not necessarily the same name).
Regards,

RFC Destination and Logical System

Hi Friends,
Can anybody tell me how the RFC Destination and Logical System are related to each other?

Hi,
In any ALE scenario u need one sender and one receiver system.
Logical systems are just logical representation of these systems but in case of RFC destination u specify technical parameters for those systems like IP address and username and password to connect to that system.
Thus when u create port i.e.we21 u specify actual RFC destination for the system to which u want to connect and when u create partner profile for that logical system u specify this port so when u want to send data to this logical system i.e receiver system port will be used which in turn has RFC destination which will be used to connect to that system.
In simple terms logical systems are logical representation of any system and RFC destinations are physical/techinical systems.
Thanks.

Diffebetween Business system and Logical system...

what is the difference between Business system and Logical system...

Hi
Business system is a logical layer needed for configuration in integration directory. On the other site technical system is physical representation of your technical landscape. In case of SAP technical systems you can have more than one business system relation. In that situation there is relation one client to one business system.
If your technical system changes, then you definitely need to point this new technical system to the existing Business system which has been used to do all the Configurations in the Integration Builder.
Re: business system
Re: business system
Thanks

Business system and logical system names

hello experts,
Right now m creating scenarios of IDOCs, Files and RFCs. Just wanted to know that is it compulsory to give Business system name and Logical system names same?
Does it make difference if i will give both names different?
Regards,
H.S.

Hi,
I guess i have not explained you proprely.
Here logical system mean m asking abt the system name which we are using in RFC connections to make connection between two systems.
does Business system name and Logical system name should be same?
Actually right now we have done system copy of production system into our sandbox. So all the things are pointing to the production system.
I was just wondering, if i will just change ip/ hostname into the Technical system (ip of sandbox system) and keep business system name as it is( which is right now of production system)... then for me no need to create all ID Objects again. Its just an idea. So just wanted to check is it ok... bcz in ID i have more than 60 objects which i need to create again. and i have very less time
Or if anyone can tell me any good idea to do that.
Thankx in advance.
Regards,
H.S.

Client Delete and Logical System and CUA

I'm getting ready to do some client clean up in prep for an upgrade from ECC 5 to ECC 6 soon.
Currently we have a 3 system landscape: DV1 QA1 PR1
Clients on these systems are as follows: (not including 000, 001, 066)
PR1:100 - the production client
QA1:100 - Integration Master - not used except for RFC connections for Solution Manager
QA1:110 - Cycle 1 testing - not used
QA1:120 - Cycle 2 testing - not used
QA1:200 - Old training master client - not used
QA1:201 - Old training client - not used
QA1:710 - no longer being used for testing
QA1:720 - client used for system and integration testing
DV1:100 - Configuration - not used
DV1:110 - ABAP development
DV1:120 - Configuration
DV1:700 - Template for test - not used
DV1:710 - Test with prod data
Most have a logical system defined for the client.
I am going to delete those I've underlined above as they are no longer used.
Some of these are setup in the CUA system.
All are showing up in Solution Manager SMSY system landscape.
My plan is to backup the system database first!
Then:
1) Delete the client(s) (SCC5) one by one
2) Remove the client from CUA (SCUA)
3) Remove the logical name (SALE)
What I am unsure about is the order of the process. Should the CUA and ALE modifications come before actually deleting the client?
Does this sound like a reasonable plan to clean up our client landscape?
Thanks in advance for your suggestions and help.
Laurie McGinley

Dear Laurie,
Order should be like below:
1) Remove the client from CUA (SCUA)
2) Delete the client(s) (SCC5) one by one
3) Remove the logical name (SALE)
More over you should delete these clients from Solution Manager also inorder not to have error message when you go to solution Manager for doing anything on that system.
Please revert back for any queries.
Regards
Shailesh Mamidwar

Logical System and Logical System Name

Hi,
I would like to create the following and please tell me how do I go about doing this. I am doing this because I am trying to implement both RFC/Idoc to File and File to Idoc/RFC. The basis admin guys are unavailble at the moment so I am on my own at this moment.
Creating a port(I suppose I need to do this on the R3. What are the steps involved)
Create a Partner Profile

Hi Sonia,
For XI communicating with SAP R/3 through Idocs ALE settings need to be done,
just go through the following steps and Configure ALE :-
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2) a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
Regards,
Ashwin M
Reward If helpful

How to get RFC Destination and Logical System name dynamically

Hi all,
I have a RFC FM written in CRM. I need to call this FM in R/3. So, i use the syntax " Call function <func> destination <destination name>. My problem is that i need to fetch the destination name dynamically..
There is a way to do so in CRM which is as follows:
DATA: lt_siteselect TYPE TABLE OF siteselect INITIAL SIZE 0,
           ls_siteselect TYPE siteselect.
CALL FUNCTION 'SMOF0_READ_SITESELECT'
    TABLES
      to_siteselect = lt_siteselect.
READ TABLE lt_siteselect INTO ls_siteselect
         WITH KEY sitetypeid = cl_smw1_siteprovider=>c_sitetype_r3oltp.
The above piece of code returns the site and also takes care of the client you are currently working on. But the specified FM is present only in R/3..
I want to achieve the functionality fulfilled by the above code in R/3.
Kindly help.
Useful answers will be rewarded.
Thanks in advance,
Karan Merwana
I can not use FM LOG_SYSTEM_GET_RFC_DESTINATION as for that i need to provide the logical system name. And the logical system name would be different for different clients.
Message was edited by:
        Karan Merwana

For those referring this thread later, I could not find a solution to this and ultimately had to do away with hardcoding of system names based on the DEV, Q, and PROD system names.
If anyone does manage to get a workaround, please let me know.

System Copy and Logical system name conversion

Hello All,
Can any one let me know some inputs over these few queries.
1. How much time would a 500+GB clients take for Export and reimport after the system copy.
2. What would be run time of the BDLSS report ( Converting the logical system names) for a typical 1500 GB QTY system
The requirement is my QTY has 3 clients, and i would like to refresh it with my PRD data. How do i safely perform thia activity with the least downtine possible and please note, the clients are around 500+ GB huge..
Thanks in advance for your inputs.
Rgds,
Sri

Hi Frank,
the parameters of my installation are as folows.
Appl Serv : OS - AIX (5.2 Version) and CPU's - 4 (Mem 20480) ::: DB serv : OS - AIX(5.2 Version) and CPU - 6 (Mem 22528)
The DB version is Oracle 9.2
We are on 4.7 enterprise version of SAP with SAPKA62055 patrch level.
br
Sri

Tcode to assign Client to Logical System (except SCC4)

Hi all,
I have created logical system for sender and receiver in SALE Tocde.
Now my receiver client is not listed in SCC4 Tocde and I am not suppose to create it there also but I need to assigning my logical system to my receiver client.
I am told that there is another way to assign So can anyone tell me which is the other way to assigning logical system to client except SCC4.
Thanks,
Maharshi

Hi,
You did create a client in SCC4.
firstly,
1. did you create a logical system via BD54 and then did you assign that logical system to this newly created client ?
2. did you perform a local client copy to put data into this new client from an old or from a standard client like 000 ?
If you didn't perform above two things, then please do.
Hope it works!!
Regards,
Amruta

Business Service and logical system naming criteria across environments

Hi !
Imagine this scenario: File-XI-IDOC. There is a file server where files are uploaded by a legacy application. XI polls that directory, converts the file to IDOC and sends it to R/3.
R/3 is a production business system, for example "R3_PROD", the file server is a business SERVICE, because of its abstract nature.
Is it ok to give that business service a name such as "BS_FileServer" and then create the logical system "LS_FileServer" in R/3, to be able to receive IDOCs from the sender business service?
If we need to use 3 different file servers, one for development, one for test and another for production...is it ok to create the business service in each integration directory with SAME name, and the 3 logical systems with same name in each R/3 receiver...because creating business services as "BS_FileServer_DEV", "BS_FileServer_TEST" and "BS_FileServer_PROD" we imagine that could give us problems when transporting scenarios from dev to test, and from test to prod...because we will need to recreate the whole scenario using the new object denomination.. e.g. a scenario including BS_FileServer_DEV in development is called BS_FileServer_TEST in test..or worse..we could have the BS object transported and as a result we would have a BS_FileServer_DEV object in integration directory of our test environment...
Is this the right path?
Thanks,
Matias.

Hey,
When a technical system is defined for a product / s/w comp version we also enter the parameter for logical system name. If a buisness system is defined for a technical system then it in turns refers to the technical system with buisness system assigned to it.
Itz lyk linkage of <b>PRODUCT -> S/W COM VERSION -> TECHNICAL SYSTEM (LOGICAL SYSTEM) -> BUSINESS SYSTEM</b>
As per file to idoc scenario where <b>BUSINESS SERVICE</b> is used it doesn't refer to technical landscape so there is no question of Business system. With relevance to transports.
With File -XI-Idoc scenario the concept of logical system only comes into picture if we have a integration process also involved in the scenario. Where in adapter specific identifiers we specify the logical system name of the sender file system.
Integration Repository.
1) The Software Component version need to be same in all the landscapes that is a prerequisite else transport will fail.
Integration Directory:
2) Assuming that transport is being done for all the objects under a service and the objects has been transported to the test landscape business service with same name will be create in test sys only address and access parameters that have to be entered again and the change list has to be activated.
I haven't tried exporting individual object from ID so no clue.
Please refer the following link<a href="http://help.sap.com/saphelp_nw04/helpdata/en/93/a3a74046033913e10000000a155106/frameset.htm">Transporting XI Objects</a> .
Hope itz helpfull.
Cheers,
*RAJ*
*REWARD POINTS IF FOUND USEFULL*

Business System and Logical system

Hi Experts,
in SAP if we want to exchange the Data between the systems we use Logical Syestem. Why we need Logical systems basically? and Why need Business system in XI?
Thanks,
Manoj.

hi manoj,
check this link.
http://help.sap.com/saphelp_nw04s/helpdata/en/42/c817d9d2296bb2e10000000a1553f6/frameset.htm
regards
srinivas

In ale client and logical system

Similar Messages

Maybe you are looking for