IDOC Help Required

[Former Member]

Hi all,

I am new to this IDOC concept, can someone please help me in resolving this issue.

I have to create a Custom Message Type and attach this message type to my IDOC.I am using an IDOC extension. Can someone please let me know the steps involved in this.

Also I am using a User-Exit, Should I do any configuration to get my custom message type flowing in the program(control_record_out-mestyp).

Thanks in Advance.

JOhann

[Laxmana_Appana_]

Hi,

Check this link for IDOC Extension help.

http://www.intelligententerprise.com/channels/applications/feature/archive/kasturi.jhtml

Regards

L Appana

[Former Member]

Hi JOhann

You can create your own message types using transaction WE81 and using WE82 transaction you can link message type to the IDOC type.

I hope you are using SAP provided standard Process code, if yes than find the appropriate userexit and populate the extended segements.

I hope i have clarified your points, let me know, if you have further clarification

Regards

Madhan Doraikannan

[Former Member]

Hi Madhan,

Thanks for your reply. I created the custom message type in WE81, and linked this message type with the IDOC type in WE82.

I am using a user-exit for this interface. Should I do any configuration to get my custom message type flowing in the include program(control_record_out-mestyp).

THanks & Regards

Johann

[Former Member]

hi johann,

I dont think u need to do any configuration regarding that user exit.

Your user exit will pick your message type from system only.

Correct me if i am wrong.

Thanks

Billi

[Former Member]

You will need to assign a Process Code in your partner profile. This process code whether it is a standard or bespoke will point to a Function Module. If a standard process code is to be used then there will be user exits in place. If you are using a bespoke function module then you will not need to use any user exits.

[Former Member]

Hi Martin,

I am using a User-Exit. In my user-exit,

IF control_record_out-mestyp EQ 'ZDESADV', then I am proceeding further in my User-Exit.

When I run the program RSNAST00, the User-Exit is trigerring but with a different message type. Can someone please help me in this.

Thanks in advance.

Johann

[Former Member]

Are you using a partner profile for you new message type.

[Former Member]

Yes I am using it.

[Former Member]

Martin,

I am getting a message like "A message type could not be (uniquely) identified".

JOhann

[Former Member]

Does that message appear in WE20.

[Former Member]

This message appears after I execute the RSNAST00 program.

[Former Member]

Do you have the same Output Type specified against more than one message type in WE20 or the distribution channel is being read and more than one message type is being determined.

[Former Member]

I am using a different Output Types in WE20.

[Former Member]

Hi,

Go through the following link:

http://www.sapbrain.com

Regards,

Bhaskar

[Former Member]

Hi Johann,

For custom messages you can try with WE81 and WE82.

Thanks and Regards,

Kunjal Patel

[Former Member]

Hi,

Few question for you before i suggest some solution.

- You are saying that you are using IDOC extension. That means that you are using extension IDOC of standard IDOC? If it is correct then why are you using custom message type. There should be a standard message type attached to standard IDOC.

- When you extend the IDOC it does not mean that you have to create a custom message type. Just assing this extesion IDOC to standard IDOC and message type using <b>transaction WE82</b>. In this transaction you switch into change mode, hit 'new entries' button. Then you enter your 'Standard IDOC type', 'Standard message type' and "Entension IDOC type'. Now save this entry.

Later you can use user-exit ( if available ) to populated the custom segments you have added in to extension idoc.

Let me know following info.

- Standard IDOC type

- Extension IDOC type

- Custom message type ( which you have created )

- Inbound OR outbound idoc

- How the IDOC is triggered.

I think the issue is with custom message type. Just use standard message type and create a entry in WE82 as i have mentioned above and it should work.

Let me know if you have any question.

Regards,

RS

[Former Member]

Hi RS,

Please find the info which u wanted to know :

- Standard IDOC type : DELVRY03

- Extension IDOC type : ZDELVRY03

- Custom message type ( which you have created ) : ZDESADV

- Inbound OR outbound idoc : Outbound

- How the IDOC is triggered : using the program RSNAST00, I am trigerring a user-exit.

Thanks in Advance

JM

[Former Member]

Hi,

Here is the deal.

<b>You do not need to create a custom message type</b> ( ZDESADV ). Just assing your extension idoc to standard idoc and standard message type using <b>WE82</b>. Follow the steps i have mentioned in my previous post

- Go to transaction We82.

- Switch to change mode

- Hit 'New entries" button.

- Create entry with these vaues

Message type = DESDAV

Basic type = DELVRY03

Extension = ZDELVRY03. Save this entry.

Now when you define your partner profile, use message type = DESDAV.

Also where you mention idoc type, enter both 'basic type' and 'extension type'

- Bsic type = 'DELVRY03'

- Extension = 'ZDELVRY03'.

You have to user usre-exit <b>EXIT_SAPLV56K_002</b> ( SMOD enhancement <b>V56K0001</b> ) to populate custom idoc segments.

Let me know if you have any question.

Regards,

RS

[Former Member]

Hi RS,

I have already done all these settings. Also I am using a Custom Message type bcos it is a requirement from the client to use a custom one.

I am using the same exit(EXIT_SAPLV56K_002) which you have mentioned.But the only problem is I am not getting my custom message type

" control_record_out-mestyp EQ 'ZDESADV' " in the exit. I am getting another message type 'ZDELVRY05'. When I change this messgae type in the debugging mode and put my message type, the IDOC is getting populated with the new segment value which is a part of my requirement. But the problem is the IDOC is having a status message 26 and also the Basic Type, Extension, Message type comming in the IDOC is not mine but something else.

THanks

JM

[Former Member]

Hi,

Check in your system that if any message type called "ZDELVRY05" exist. You can check this in <b>table EDMSG</b>.

Also, check if this message type exist, then if is also assinged to IDOC DELVRY03 and extension ZDELVRY03. Check this in <b>transaction WE82 or table EDIMSG</b>.

Also, reconfirm your partner profile of also contains the entry for DELIVERY idoc with message type ZDELVRY05.

I suspect that someone had created a message type ZDELVRY05 before and it is still configure in your system.

Let me know what you found out.

Regards,

RS

[Former Member]

Hi RS,

I checked in table EDMSG and I found my Custom message type 'ZDESADV' as well as 'ZDELVRY05'.

I Checked the in transaction WE82 and table EDIMSG the configuration is done correct.

My partner profile also is being configured correctly.

I wanted to share with you another thing which I did tell in my previous queries.

In the User-Exit(EXIT_SAPLV56K_002) which I am using, there is another program written in the same include(ZXTRKU02) which uses the Message type 'ZDELV05'. This is already existing in the include. My code I have written after this.

Thanks,

JM

[Former Member]

Hi,

It seems taht the code with message type 'ZDELV05' is obsolete. Some one was using before and now it is of no use. Please check with your Tech lead / Functional consultant to see if they still use message thye 'ZDELV05'.

<b>If no body is using this message</b> the then you shold remove this code. Also, make sure that there is no entry in transaction WE82 regarding this message type and there no Partner profile too.

<b>If this message type is used</b> for some purpose, then you will have to find the way to distinguish when to use message type 'ZDELV05' or 'ZDESADV'. Please check with your tech lead / Functional owner.

Let me know if you have any question.

Regards,

RS

[Former Member]

Hi RS,

Thanks for your quick response. THe message type 'ZDELV05' is still being used.

Can we have both the message types used in the same Exit.

Thanks & Regards

JM

[Former Member]

Hi,

Yes, we can code related to both message type in exit. You just have to distinguish, which condition to code. The code can be something like this.

*----------------------------------------------------------------------*
*----------------------------------------------------------------------*
CASE message_type.

  WHEN 'ZDELV05'.

*"  Add code related to message type 'ZDELV05' here

  WHEN 'ZDESADV'.

*"  Add code related to message type 'ZDESADV' here

  WHEN OTHERS.
  
*"  Do not write any code here

ENDCASE.
*----------------------------------------------------------------------*
*----------------------------------------------------------------------*

Let me know if you have any question.

Regards,

RS

[Former Member]

Hi RS,

I have written a IF statement in the User-Exit. But the problem is the message type which flows into the exit is 'ZDELV05'.

Regards

JM

[Former Member]

Hi,

This means that IDOC which is triggering is of message type 'ZDELV05'.

How, the IDOC is triggered in your case? I mean which transaction? I remember that you said program RSNAST00, but for this program to generate IDOC the ouput record should exist.

I think your idoc is generated using transaction VL01 / VL02. Once you are go to this transaction, you see output condition under menu "Header --> Output". Check here what is the output type selected.

Now, i am definitely sure that there is a partner profile for 'ZDELV05' in WE20. Check this partner profile and see under tab "message control" if the output type you see in VL01/ VL02 is define here.

I still do not understand why you are using both the message type. You can not configure both the message type to create same IDOC with same application. It is wrong method. Pleae talk to your functional owner / tech lead and try to understand why they want both message type. There should be something to distinguish between them.

Regards,

RS

[Former Member]

Hi,

You are perfect, the IDOC is triggering is of message type 'ZDELV05'.

My IDOC is getting trigerred using the program RSNAST00. Here am giving output type as 'LD01'.

My idoc is generated using transaction VL02N. Once you are go to this transaction, you see output condition under menu "Header --> Output". Here my output type is 'LD01'.

You are perfectly right, there is a partner profile for 'ZDELV05' in WE20 and this partner profile -->under the 'message control' is using the same output type which I was using it. What I did now is I deleted the Output types under this message type, when I did this, my custom message is flowing in the user-exit.

Regarding two message types comming in the user-exit, I guess there is someother functionality which is being handled in the same user-exit.

Thanks a lot for your inputs.

JM

[Former Member]

Hi,

If your problem is solved, please close the thread by awarding appropriate point so in future some when have similar problem and look this thread and see it answered, then can refer to this thread to get solution.

Let me know if you have any other question.

Regards,

RS