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

Similar Messages

  • Difference between business service and business system in SLD

    hi all,
    i m very new to XI. can anybody tell me that what is the basic difference between Business Service and Business Systems?
    Is it necessary to use them? and if yes then when to use what?
    Thanx.
    Regards,
    Kunjal......

    Hi Kunjal,
    In SAP XI every system in your landscape with which you are interfacing is defined as Service.
    The service can be your Business service or Business system.
    Generally SAP systems are referred to Business system and you define them in the SLD before you import them.
    The Business service is a logical name referring to any system in your landscape.
    To communicate with any third party application you need to create communication channels which are associated to your service.
    More about this here:
    http://help.sap.com/saphelp_nw04/helpdata/en/7d/6b82cd0d1aef48ab5953524c9cc5b2/content.htm
    Regards
    Vijaya

  • Difference between R/3 and CRM systems

    Hi,
    I want to know difference between R/3 and other systems like CRM, SCM. Shall we need XI to integrate them..
    I think that CRM,SCM are the modules of R/3 is correct..
    What kind of applications they are...
    Thanks,
    RamuV

    Hi Ramu,
    As you said they are R3 Applications only.
    can be connected with the help of XI.
    CRM uses BDOCs but XI can only deal with IDOCs. So when you will be working with BDOCs of CRM, then in CRM you will have to create custom IDOCs for the corresponding BDOCs and then you can have File-IDOC and IDOC-file scenarios working via XI to communicate between your CRM server.
    BestRegards,
    Ramesh

  • 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

  • What's the difference between client combo and server combo? Also, what would happen if I install both?

    what's the difference between client combo and server combo? Also, what would happen if I install both?

    One is for the base version of the Mac OS, the other is for the Server version. You can only install the one that matches your system.

  • Difference between client proxy and server proxy

    hi all,
    could u explain me the differences between client proxy and server proxy,
    regards,
    AVR

    Hi AV,
    simple search in sdn may answer your question,
    There are two type of Proxy's in ABAP and JAVA(Clinet and Server),
    Clinet ABAP proxy used to send message from ANY SAP System to Integration server,in this case XI adapter not required .
    Server ABAP proxy used to send messages from Intergration server to any SAP System,in this case XI Adapter required.
    How to implement ABAP proxy comunication refer below link
    http://wiki.sdn.sap.com/wiki/display/stage/ABAPproxyproviderimplementationand+testing
    The sama way Client JAVA proxy used to send message to Integration sever from any Web Application ,
    Server JAVA proxy used to send messages to any destination system ,in both cases XI adapter required.
    refer below link
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/7d4db211-0d01-0010-1e8e-9b07fc2113ab&overridelayout=true
    Regards,
    Raj

  • Difference between physical join and logical join

    Hi Gurus,
    Can anyone tell me what is the difference between physical join and logical join
    Thanks,
    Chandra

    Hi,
    A physical join is at the physical layer and defines the join between two physical tables. Logical joins live at the BMM (logical) layer and define a join between two logical tables.
    The important differentiation is that at the BMM layer you do not tell the OBIEE server how to do the join, you just tell it that there is a relationship between these two logical entities. When the server comes to this logical join it will use the information in the physical joins and decides how the two logical tables are joined together.
    In BMM you use complex joins to establish which logical tables are joined which another, the OBI EE server will go to the physical level to search the physical join to make the query. You can also use physical joins in the BMM to override the join in the physical layer but only in very specific conditions.
    If you also set complex join in the physical layer OBI EE won't be able to construct the physical query.
    Hope this answers your question.
    Award points if helpful.
    Thanks,
    -Amith.

  • 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.

  • Difference between client 000 and 001.

    Hi,
    what is the difference between vclient 000 and 001 ?
    Best regards

    000: SAP standard client
    This client is used to set up new "neutral" clients by client copy. Do not change or delete this client.
    This is an SAP referce client
    Every time an SAP system is installed the 000 client is created by default woth 2 users SAP* and DDIC. Transport configurations are always done from 000 client. (they can t be done in any other client and they have to be done with the user DDIC).
    Other client like Customizing client, testing client etc are created form the 000 client. Similarly in the production environment also the productive environment client is copied from 000.
    001: SAP standard client
    This client is used to set up new "neutral " clients by client copy.
    This is also an SAP reference client. No changes should be done in this client either
    Do not change or delete client 000 or client 001.
    Regards,
    Prashant

  • 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

  • What's the difference between data source and source system in BI

    hello
    what's the basic and exact difference in BW 3.0 and BI 7.0. i am very urgent indeed. can anyone help me - how the things should be done here. it's preety confusing.
    Can anybody give me the step by step analysis.
    Thanks in advance
    C.S.Ramesh

    Hi,
    Chk the foll links...
    See this very nice presentation prepared by Dr Berg on new features of BI 7.0 (these are the differences between BI 7.0 and BW 3.5):
    http://csc-studentweb.lrc.edu/swp/Berg/Articles/NW2004s_what_is_new.ppt
    Check the release notes:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/a4/1be541f321c717e10000000a155106/content.htm
    This presentation:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/910aa7a7-0b01-0010-97a5-f28be23697d3
    Web Blog:
    /people/michael.eacrett/blog/2006/06/07/whats-new-in-sap-netweaver-702004s--an-introduction-to-the-functionality-deltas-and-major-changes
    You can also refer below posts:
    Re: BW 7.0 Release
    /message/1383908#1383908 [original link is broken]
    Upgrade from BW 3.5 to BW 7.0 (BI 7.0)
    Some features of BI 7 are
    1. In Infosets now you can include Infocubes as well.
    2. The Remodeling transaction helps you add new key figure and characteristics and handles historical data as well without much hassle. This is only for info cube.
    3. The BI accelerator (for now only for infocubes) helps in reducing query run time by almost a factor of 10 - 100. This BI accl is a separate box and would cost more. Vendors for these would be HP or IBM.
    4. The monitoring has been imprvoed with a new portal based cockpit. Which means you would need to have an EP guy in ur project for implementing the portal !
    5. Search functionality hass improved!! You can search any object. Not like 3.5
    6. Transformations are in and routines are passe! Yess, you can always revert to the old transactions too.
    this is a good PDF on Upgrade from BW 3.5 to BW 7.0
    latest on upgrade tp BI7.0
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/2e8e5288-0b01-0010-2ea8-bcd4df5084a7
    http://help.sap.com/bp_epv170/EP_US/Documentation/How-to/Planning/Master_Guide_NW2004s.pdf
    You can seek more information on BI 7.0 in the SAP NetWeaver2004s Ramp-Up.
    /community [original link is broken]
    Re: BW 7.0 Release
    Re: BW 7.0 Release
    Re: BW 7.0
    take a look presentation
    overview
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5ee3725b-0401-0010-e381-ac323362ce91
    detail
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5c46376d-0601-0010-83bf-c4f5f140e3d6
    https://www.sdn.sap.com/irj/sdn/developerareas/bi?rid=/webcontent/uuid/e78a5148-0701-0010-7da9-a6c721c6112e [original link is broken]
    may useful .....
    https://www.sdn.sap.com/irj/sdn/developerareas/bi
    http://help.sap.com/saphelp_nw04s/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm
    Hope this helps.

  • 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

  • Difference between jsp:forward and logic:forward

    Hi,
    Can anyone let me know??
    what is the difference between <jsp:forward> in and <logic:forward> in struts
    Thanks in advance,
    Regards
    Dhinesh kumar R

    See: http://java.oreilly.com/news/jsptips_1100.html (number 4)

  • Difference between client 800 and other client

    Dear Gurus,
    I have one more query one of my friend asked me is it possible to configure the client business process in client 800 in real time what makes the difference the client 800 from other client, i said 800 client is open client others are configured based on client bpp, but so we can configure the same process in 800 also so iam not confident in answering at that time, so looking for your input.
    Regards,
    Arun.

    Hi,
    Client 800 normally refer to IDES server. There is no hard rule that the client server numbering should be like this only.
    In general Client will be named as
    IDES is for training only.
    Development Client - Sand Box (for testing) which is can eb used for configuration has well as data testing. 
    Golden Client - Which will have only configuration setting and No Data.
    Quality Server   - Pre-produciton server, which will carry the copy of  Production Server.( configuraiton + data)
    Production Server - This is live server in which we do all day to day transctions.
    Note : All transportation request created in developement (ABAP - Work Bench) or Configuation done in Golden client will be move first to quality server, tested and then only it will be moved to production client. 
    Hope it is clear.
    Regards,
    R.Janakiraman

Maybe you are looking for