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.

Similar Messages

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

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

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 PRODUCT -> S/W COM VERSION -> TECHNICAL SYSTEM (LOGICAL SYSTEM) -> BUSINESS SYSTEM
As per file to idoc scenario where BUSINESS SERVICE 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*

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

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

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,

Business System and Technical System ??

Hi Experts,
Please tell, What is the Technical System and Business System. How many Technical and Busniess Systems do we have in XI ?
Early responses are welcome.

Hi,
Business systems:
Business systems are logical systems, which function as senders or receivers within PI. Business systems can be SAP systems or third-party systems.
Depending on the associated technical system, the following types of business systems are defined in the SLD:
Web AS ABAP:
A business system, which is associated with a Web AS ABAP.
A business system, which is associated with a Web AS ABAP, can play the role either of an application system or an integration server. An integration server is the central component of PI, which provides a framework for the exchange of information among various internal and external entities of a company. The integration server facilitates the interaction between the different operating systems and applications across internal and external networks.
Web AS Java:
A business system, which is associated with a Web AS Java.
Standalone:
A business system, which is associated with a standalone Java application.
Third-party:
A business system, which is associated with a third-party technical system.
Technical systems:
Technical systems are application systems that are installed in your system landscape. An example of an application system is a Customer Relationship Management (CRM) server. In the SLD, there are five types of technical systems:
Web AS ABAP:
Web AS ABAP technical systems, ranging from any SAP system to an APO server or CRM server, are based on the same Basis Component (BC), which includes the ABAP interpreter, ABAP Dictionary, ABAP Workbench, and so on. A dedicated database, which stores most of the data of the BC and the application components, is associated with the system.
Web AS Java:
Web AS Java systems consist of one or more instances and each instance is installed on a separate host. An instance itself consists of cluster nodes that can communicate with each other.
Standalone Java:
Standalone Java technical systems are standalone Java applications that are installed in a computer system from an administration perspective. They can also be installed as an operating system service or as a daemon.
Third-Party:
Third-party technical systems contain third-party software components and products.
Regards,
Prakasu

Use of Business Systems and Technical Systems

Hi
What is the use of having business systems and technical systems in SAP XI. I don't see any configuration details needed to create these. I understand that it logically divides the interfaces into different business systems but is that the only use? The only place I see the real configuration done is in the adapter configuration.
Vijay

Vijay,
The technical system actually works better for our non-SAP systems than the SAP systems. Here is our scenario:
We have an AS400 business system that uses a file adapter to send files to XI and then uploaded to SAP ECC. The file adapter does not ask for the system information so we can switch between dev and test by changing the DNS address in the technical system entry (dynamic reference like a property file lookup). The communication channel settings do not have to change.
The receiver is SAP using an RFC adapter which requires the system ID, and client (hard coded). Everytime we change clients, we have to change the settings in the RFC adapter. This is more to your point of why do we have a technical system if we have to provide the settings in the adapter as well. The RFC adapter should read the application server and client values from it's parent business system so the changes don't have to be made everytime we point to a new client( such as QA). This is irritating.
So maybe the theory is good but the implementation could be better in this case.
Thanks,
Troy

How to creat a Business System and Tech System in SLD for the DB2 DataBase?

Hi,
How to creat a Business System and Tech System in SLD for the DB2 DataBase?
Joseph

Hi,
Technical System
In SLD, click on technical landscape->New Technical System->WebAS ABAP.
Business System.
1.Goto Business Landscape->New Business System->Name the business system.
2. Choose the technical system that needs to be attached->WebAS ABAP->Technical System Name.
Go Through this links..
TBIT41:
https://websmp201.sap-ag.de/~form/ehandler?_APP=00200682500000001337&_EVENT=DISPLAY&COURSE=TBIT41&LANGUAGE=
TBIT42:
https://websmp206.sap-ag.de/~form/ehandler?_APP=00200682500000001337&_EVENT=DISPLAY&COURSE=TBIT42&LANGUAGE=
TBIT43:
http://www50.sap.com/useducation/curriculum/course.asp?cid=60161651
TBIT44:
https://websmp102.sap-ag.de/~form/ehandler?_APP=00200682500000001337&_EVENT=DISPLAY&COURSE=TBIT44
Also try elearning.
https://www.sdn.sap.com/irj/sdn/elearn
Thanks,
Satya Kumar

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.

What is a R/3 system, logical system, and legacy system...???

Hi,
Please throw some light on...What is a R/3 system, logical system, and legacy system...???

Hi,
R/3 system is a normal SAP system that stores data.
A legacy system is an existing computer system or application program which continues to be used because the user does not want to replace or redesign it.
Logical System:
http://help.sap.com/saphelp_nw2004s/helpdata/en/c8/5aa2a0deb91548a1842f8485dee4a2/frameset.htm
Technical System:
http://help.sap.com/saphelp_nw2004s/helpdata/en/24/8fa93e08503614e10000000a114084/frameset.htm
Regards,
Subhasha

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

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

Business system and technical system in XI

Hi to all
Iam new to XI. I what to know about business system and technical system in XI.
and when does we go to configure a business system and technical system .
with regards
satish.

hi,
in terms of R3
technical system is the server
business system is a client
you can find more about those two in:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
how to register R3 technical system - have a look at my blog:
/people/michal.krawczyk2/blog/2005/03/10/registering-a-new-technical-system-in-sld--abap-based
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Business system and logical system names

Similar Messages

Maybe you are looking for