Difference between client system and logical system

[Former Member]

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

[Former Member]

Hi,

refer the link

https://forums.sdn.sap.com/click.jspa?searchID=11168866&messageID=5076621

Regards

Kiran Sure

[Former Member]

Hi Arun,

client system means the system which the client uses.the client may be your project client or the clients existed in your system like 100,200 etc.

actually we have a server and a client which we are working.chekc your sap system.we have different clients for one server.generally a logical system is the name of the system which we will use to call the system.technically a logical system is the combination of a server and client.

we will use message type to define the type of data we are sending.

reward points if helpful.

[Former Member]

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.saptechnical.com/Tutorials/ALE/ALEMainPage.htm

thanks

karthik

reward me points if usefull