multiple message types for an idoc type

[Former Member]

Hi all,

I created one custom idoc type with six segments. I heard that one idoc type can have any number of message types

if it is so pls tell me how to assign these two message types for my idoc .

i want to create multiple message types because i want to send same idoc type to diff legacy systems.

My requirement is message type one is only for first three segments and message type two is for another three segments .

The outbound program 1 for mess type 1 should fill fill the data for only first three segments and second outbound program corresponding to mess type 2 should fill the data for last three segments

how should i design for my requirement. suppose if the idoc has two message types then it has two outbound programs?

[former_member200345]

Hi Kunal,

Use the tcode WE82 to assign the Message type to IDOC type.

Regards,

Vijaymadhur.

[Former Member]

I am looking for design of my requirement,i know the t-code to assign a message type

[Former Member]

Hi Kunal,

Below are my thoughts from a design perspective,

My requirement is message type one is only for first three segments and message type two is for another three segments .
The outbound program 1 for mess type 1 should fill fill the data for only first three segments and second outbound program corresponding to mess type 2 should fill the data for last three segments

Before you look upon the no. of message types you need, i guess you need to look at the business requirement. Per your requirement you want to send send two sub sets of data. The first subset in the first 3 segments and other three segments for the second subset of data.

Is the structure of the first subset of data similar to the second subset If not, better to create two IDOC Types. If they are similar, then create one IDOC Type with three segments and have two message types for each subset of data.

For Ex: ORDERS05 is the IDOC type for Orders, this IDOC type provides capability to carry data related to any type of orders

but the action on the data is facilitated by the message type like ORDERS for create, ORDCHG for change, ORDRSP for Order response etc.

OR

Are these two subsets of data related to each other, if yes understand the relation? If not related at all then you might be better of creating two separate IDOC Types.

Like in the above example A purchase order is related to a sales order so you can use the same IDOC type, but in case of a order response and ASN that data sent is different and hence you will need different IDOC types (even though a SO is related to a DN).

how should i design for my requirement. suppose if the idoc has two message types then it has two outbound programs?

The above again depends on the how tightly/loosely coupled are the data sets, you can have just one program and have a simple case statement on the message types or have two different programs.

You will also have to consider points like, if any of the subsets is more prone to more change in terms of the structure and associated business logic. If yes, then you might want to keep the programs separate to reduce work on regression testing etc.

I am sure you will receive more inputs from the experts on the forum and the list of points to look for will get longer , so understand the requirement, dependencies and if you have any specific questions you could post it on the forum.

Regards,

Chen