Cross Application Definations

[Former Member]

hello all

can anybody tell the definitions for followings:

IDOC:

IDOC Type:

Message Type:

Basic Type:

Partner Profile:

Model View:

Port:

[athavanraja]

check out

help.sap.com to understand these concepts.

[SureshRa]

IDOC: Intermediate Document. This is an SAP structure of exchanging message.

IDOC Type: This is same as basic type. Refer Basic Type below.

Message Type: Type of the message. e.g. MATMAS is message type for Material Master. This may or may not have Basic Types (IDoc types) assigned to this. MATMAS03, MATMAS04 are Basic Types (IDoc Types). You create message types in WE81 transaction.

Basic Type: Basic type is definition of an IDoc structure. This is assigned to Message Type. You define Basic type through transaction WE30.

Partner Profile: Partners who exchange messages can be 'Vendor', 'Logical Systems', etc. You define your partner in tcode WE20. Here you also specify for each partner what are the inbound and outbound messages. You will specify both 'Message Type' as well as associated 'Basic Type(IDoc Type)' here. Apart from this, for inbound you will specify processing code which refers to inbound function module.

Model View: This is required if you exchange message using ALE. The exchanging systems communicate through ALE interface (Transactional RFC calls) to exchange IDocs and statuses. You define model view through BD64 transaction.

Port: Port is the gate-way through which the physical IDoc or T-RFC call is exchanged. Here you define which RFC Destination for ALE communication. You will specify physical / logical file-path for File-Port (EDI) communication.

Regards

Suresh Radhakrishnan

[Former Member]

hi,

IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.

The messages exchanged between systems are of various message types. The message type depends on the data contained and the process involved. It determines the technical structure of the message, the IDoc type. For example, the FIDCMT message type is used for journal messages.

The IDoc type indicates the SAP format that is to be used to interpret the data of a business transaction.

An IDoc type consists of the following components:

· a control record

This is identical for each IDoc type.

· several data records

One data record consists of a fixed key part and a variable data part. The data part is interpreted using segments, which differ depending on the IDoc type selected.

· several status records

These are identical for each IDoc type and describe the statuses an IDoc has already passed through or the status an IDoc has attained.

Message type :

A message type comprises a data type that describes the structure of a message. At the following points in SAP Exchange Infrastructure you can refer to the message to be exchanged at runtime by using the message type:

· More than one message interface can use the same message type. For example, an asynchronous outbound message interface and an asynchronous inbound message interface can reference the same message type because the request message does not need to be mapped.

· When defining a message mapping you can directly reference message types to map messages from an outbound interface to messages from a receiver interface.

Basic type :

An SAP development creates a new basic type, which represents a new business process within which data can be exchanged electronically.

Partner profile : The partner profile contains parameters that define the electronic interchange of data with a partner via that IDoc interface.

Ports are a logical representation of the communication channels in SAP. R/3 defines four types of ports viz. tRFC (transactional Remote Function Calls), File, R/2, and Internet. ALE can use all port types to distribute Idocs.

pls reward if helpful.