Message type and Basic type related to IDOC

[Former Member]

Hello Friends,

1) What is the difference between Message type and Basic type related to IDOC..Could any give example for explaining this.

2)whether message type depends on bsic type or reverse.

3)How to create message type and basic type for IDOC..

Could any one give example for this.

4)what is custom IDOC .How to define this.any example

[Former Member]

1) What is the difference between Message type and Basic type related to IDOC..Could any give example for explaining this.

Message Type

Message type identifies the message being exchanged

Every IDoc type is assigned to a Message type

All IDoc carrying similar message ( similar IDoc type ) can be recognized by message type

Transaction WE81 is used to create message types Transaction WE82 is used to assign message types to IDoc types

Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.

3)How to create message type and basic type for IDOC..

Create Message Type

Go to transaction code WE81

Change the details from Display mode to Change mode

After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter

Click New Entries to create new Message Type

Fill details

Save it and go back

Assign Message Type to IDoc Type

Go to transaction code WE82

Change the details from Display mode to Change mode

After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.

Click New Entries to create new Message Type.

Fill details

Save it and go back

Could any one give example for this.

4)what is custom IDOC .How to define this.any example

Ans: 1)What is custom idoc? How we developed it.? Is it possible to develop through a program.?

Sol: Custom IDOC means IDOC created by user. It is developed by WE30 either basic type idoc or extension type idoc. It is not possible to develop throguh program.

2)How we configured it?

Sol: First we create segments and message types and idoc types. Then assign that idoc type with message type throguh WE82. Port can be coonfigured through WE21 and partner profile can be configured throguh WE20 and RFC destination can be configured throguh SM59.

3)How the idoc is being sent.

Sol: These IDOCs can be sent through coding. All the data can be stored in EDIDD,EDIDC and EDIDS. take internal tables with that strucutres and populate the data into that.

4)Where it is going to reach?

Sol: Data (IDOCs) will reach to senders system with the help of port and partner profile configurations and RFC destination.

Hope this helps you, reply for queries, Shall post you the updates

[former_member556603]

Hello sunil,

1.Message type holds the information about the application.

We can create the message type using the

TCode:WE81.

Create a Distribution Model

A distribution model models a distributed environment in which you specify messages

Exchanged between sending and receiving systems. You must create the model on the system that will be the model owner. This model owner is responsible for maintaining the model and distributing it to various systems. In our case, we assume that there are only two systems.

1. SAP transaction code: BD64 – Type /nbd64 in the SAP input window and press the

Enter key.

2. Notice that the Create model view push button is gray. This means that the function is

disabled.

3. Click the Distributional Model pull-down menu.

4. Select Switch processing mode to enable the Create model view function.

5. Click Create model view.

6. Fill in the Short text field.

7. Enter a meaningful Technical name.

8. Keep the Start date and the End date unchanged. The SAP system will prompt the

current date as the Start date. It will also prompt an end date, which is beyond most of

our lifetimes (December 31, 9999).

9. Click the green check icon to continue.

You will now see a new entry created with the short text you entered on the left side and the technical name on the right side.

10. Highlight the new entry.

11. Click Add message type on the top of the screen.

12. Fill in the information Sender as the SAP LS, Receiver as the LS of the remote system and message Type as MATMAS.

If you expand the new distribution model you will see that a new entry for the

message type MATMAS was created. If you need to support more message types, you need to repeat the Add message type operation for each of the SAP message types you will support.

The message type MATMAS will be supported for the outbound operations. SAP will send the MATMAS message type to remote LS.

If you will support inbound messages, you will need to specify Remote System LS as the sender and SAP LS as the receiver.

After you added all message types you want to support, you need to save your work:

14. Click the save icon (or press Ctrl+S) to save the model you just created.

15. You will see the message “Distribution model has been saved” displayed at the bottom of the SAP screen indicating that your work has been saved.

2.Basic Type jus holds information regarding the application.

We will create the basic or extention of the IDOC in WE30.

3.Message type and basic Type or interdependent.So, they can be assigned in WE82.

4.Custome IDoc is nothing but ,creating the IDOC as Basic type.That is also created in WE30.

Steps to create Custom IDOC..

The SAP message type we support in this example is MATMAS. Its associated Idoc is

MATMAS03.The scenario of this example works like this. Whenever an SAP user creates or updates a material master record, SAP sends an IDoc (IDoc type MATMAS03) to the remote system (Logical System). The IDoc is converted to the format whatever the SAP adapter supports on the remote system.

There are certain tasks that needed to be performed to make the legacy system to get the Idoc from the SAP System.

So here I am describing SAP ALE settings for linking between SAP system ie the Logical system on sap side with the SAP adapter agent on the legacy system ie the Logical system of the legacy system.

Step 1 :

This step is to create the Logical system for the remote system.

A logical system allows SAP internal functions to interface with external systems, either an SAP system or a non-SAP system. We also need to have a logical system name for the SAP system,.

SALE is the transaction.

Expand the Sending and receiving Systems and then the Logical systems click on define logical system.

You will receive the informational message, “The table is cross-client.” Click the green check icon to continue.

Now click on the New Entries.

The Screen appears like this here you will be giving the LS name and the description of that.

After u click on the save button a window will be displayed like the bellow asking for the Request ID. Here we can create our own or we can use the existing one.

After that we see the message blow as DATA SAVED.

Now the step is to Link the LS to the client.

Click on the Assign Client to LS .

The Screen as below will be appearing.

Double click on the client on which u r going to work and there specify the SAP LS(IDS47800) and you also need to specify the City and Std Currency and the client role as Test for the drop down box.

Register the RFC server module with the

SAP gateway

The RFC (Remote Function Call) destination is a logical name used to define the

Characteristics of a communication link to a remote system (in our case, LS for the remote system) on which a function needs to be executed. In ALE, the RFC specifies information required to log on to the remote SAP system to which an IDoc is being sent.

To register the RFC Sever Module as the RFC destination:

SAP transaction code: SM59 – Type /nsm59 on the SAP input window and press the

Enter key.

Expand the TCP/IP connections directory.

Give some name to the RFC Destination (ALESERVER), Connection type as T. and fill the Description field.

In technical settings give the program name as you desired.

Click on save

Create the tRFC port definition

Refer to the following steps to create the tRFC port definition.

1. SAP transaction code: WE21 – Type /nwe21 on the SAP input window and press the

Enter key.

2. Highlight Transactional RFC.

3. Click the Port pull-down menu, which is located in the upper left corner of the SAP

screen. Click Create (or press F7).

4. Select the own port name radio button.

5. Type a port name such as ALEport. If you use a port name different from this, update

Table 2 at the beginning of this chapter for future reference.

6. Click the green check icon to continue.

7. Fill in the description field with tRFC port (You are free to write anything you want here).

8. Fill in the RFC destination field with ALESERVER. This must match the name you used on the previous RFC Destination step. If the name you enter here does not exist, the

system will flag an error and you will need to provide an existing RFC destination.

9. Make sure that IDoc record types SAP Release 4.x is selected.

10. Click on save.

Create a Distribution Model

A distribution model models a distributed environment in which you specify messages

Exchanged between sending and receiving systems. You must create the model on the system that will be the model owner. This model owner is responsible for maintaining the model and distributing it to various systems. In our case, we assume that there are only two systems.

1. SAP transaction code: BD64 – Type /nbd64 in the SAP input window and press the

Enter key.

2. Notice that the Create model view push button is gray. This means that the function is

disabled.

3. Click the Distributional Model pull-down menu.

4. Select Switch processing mode to enable the Create model view function.

5. Click Create model view.

6. Fill in the Short text field.

7. Enter a meaningful Technical name.

8. Keep the Start date and the End date unchanged. The SAP system will prompt the

current date as the Start date. It will also prompt an end date, which is beyond most of

our lifetimes (December 31, 9999).

9. Click the green check icon to continue.

You will now see a new entry created with the short text you entered on the left side and the technical name on the right side.

10. Highlight the new entry.

11. Click Add message type on the top of the screen.

12. Fill in the information Sender as the SAP LS, Receiver as the LS of the remote system and message Type as MATMAS.

If you expand the new distribution model you will see that a new entry for the

message type MATMAS was created. If you need to support more message types, you need to repeat the Add message type operation for each of the SAP message types you will support.

The message type MATMAS will be supported for the outbound operations. SAP will send the MATMAS message type to remote LS.

If you will support inbound messages, you will need to specify Remote System LS as the sender and SAP LS as the receiver.

After you added all message types you want to support, you need to save your work:

14. Click the save icon (or press Ctrl+S) to save the model you just created.

15. You will see the message “Distribution model has been saved” displayed at the bottom of the SAP screen indicating that your work has been saved.

Generate a Partner Profile

A Partner Profile is defined for every SAP business partner. A partner is a remote SAP system or legacy system with which you exchange data. In our example, the partner is the remote system LS.

1. Highlight the newly created distribution entry in the SAP distribution model

screen.

2. Click the Environment pull-down menu.

3. Select Generate partner profiles.

4. In the Postprocessing:Authorized processors section of the previous screen, enter US as the user type. In partner system specify the remote LS.

5. Change the ID field if it is necessary. The field’s default is the user id currently signed on to the SAP system. You may change it to the person who will be responsible for maintaining this partner profile.

6. Change the Outbound parmtrs: Output mode and Inbound parmtrs: Processing fields if it is necessary. Transfer IDoc immediately and Trigger immediately are selected as the default values,

7. Click on the execute button on the left corner of the system(resembles like a timer).

8. The return screen shown following will display. It is typical for you to receive a warning (pink/red) message such as “Port could not be created". The reason for this message is you have not had an opportunity to tell SAP which port you will use for this partner profile. We will set it manually in the next step.

Modify the profile of the partner logical

system

The following steps explain how to modify the profile of the partner logical system.

1. Transaction code: WE20 – Type /nwe20 on the SAP input window and press the Enter key.

2. Expand Partner Type LS (Logical System).

3. Click item remote system LS (or the name you use for the partner logical system).

4. Scroll down to see the Create outbound parameter icon +(add) below Outbound parmtrs table.

5. The Partner profiles: Outbound parameters will be displayed. Enter the following information:

•Partn. funct.: Leave blank, as it is.

•Message type: MATMAS

•Receiver port: ALEport (or the port name you used.

•Output mode: Select Transfer IDoc immed and Do not start subsystem.

•IDoc Type:

o Basic Type: MATMAS03.

o Leave other fields as they are.

6. If you have more outbound parameters, repeat steps 4 and 5. If you support any inbound

parameters, perform the steps for creating inbound parameter. The steps for creating inbound parameters are similar to those for creating outbound parameters. The Create inbound parameter icon is located under the inbound params table, which is located below the outbound parameter table. If you are not sure whether you support any inbound messages, check the previous section, Create a distributional model, or use the SAP transaction code BD64 to view the distributional model.

7. Click the save icon (or press Ctrl+S) to save the outbound parameters you just created for the message type MATMAS.

8. You will see a message, “Data saved” displayed at the bottom of the SAP screen indicating that your work has been saved.

9. You will see that the MATMAS entry is added to the outbound parameter table.

Generating an Idoc definition file:WE61

give the basic type as matmas03 and right click on the screen you will find Parser click on that

This screen will be displayed.

now go to System-list-save-local file

We will get screen like this and here make sure that radio button is unconverted and then click on enter.

A window or pop up will be coming where in u can specify directory where the file is to be saved.

BD10 will be used for the transportation of the Idoc.

Hope this info is very useful to you..

Reward points if it is useful..

Thanks,

Satya Kuamr..

[Former Member]

Hi,

Steps To Create Custom IDOC

1.Create Segment Type (WE31)

Go to Transaction code WE31

Enter Segment type, click on Create

Give Description

Enter the Necessary Fields & Data Elements for those Fields.

Save the Changes.

2.Create Idoc Type (WE30)

Go to transaction code WE30

Enter the Object Name, select Basic type and click Create icon

Select the create new option and enter a description for your basic IDOC type and press enter

Select the IDOC Name and click Create icon

The system prompts us to enter a segment type and its attributes

Choose the appropriate values and press Enter

The system transfers the name of the segment type to the IDOC editor.

Follow these steps to add more number of segments to Parent or as Parent-child relation

Save it and go back

Go to Edit -> Set release

3.Create Message Type (WE81)

Go to transaction code WE81

Change the details from Display mode to Change modenAfter selection, the system will give this message “The table is cross-client (see Help for further info)”. Press EnternClick New Entries to create new Message Type

Fill details

Save it and go back

4.Assign Idoc Type to Message Type (WE82)

Go to transaction code WE82

Change the details from Display mode to Change moden After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.

Click New Entries to create new Message Type.

Fill details

Save it and go back

Regards

Seshagiri