topic Re: IDOC Help Required in Application Development and Automation Discussions

IDOC Help Required

Former Member — Mon, 02 Apr 2007 15:18:46 GMT

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

Re: IDOC Help Required

Laxmana_Appana_ — Mon, 02 Apr 2007 15:24:16 GMT

Hi,

Check this link for IDOC Extension help.

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

Regards

L Appana

Re: IDOC Help Required

Former Member — Mon, 02 Apr 2007 16:54:43 GMT

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

Re: IDOC Help Required

Former Member — Mon, 02 Apr 2007 20:05:37 GMT

Hi,

Go through the following link:

http://www.sapbrain.com

Regards,

Bhaskar

Re: IDOC Help Required

Former Member — Tue, 03 Apr 2007 08:30:04 GMT

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

Re: IDOC Help Required

Former Member — Tue, 03 Apr 2007 08:45:43 GMT

Hi Johann,

For custom messages you can try with WE81 and WE82.

Thanks and Regards,

Kunjal Patel

Re: IDOC Help Required

Former Member — Tue, 03 Apr 2007 08:49:10 GMT

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

Re: IDOC Help Required

Former Member — Tue, 03 Apr 2007 08:52:57 GMT

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.

Re: IDOC Help Required

Former Member — Tue, 03 Apr 2007 13:35:58 GMT

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

Re: IDOC Help Required

Former Member — Tue, 03 Apr 2007 13:41:29 GMT

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

Re: IDOC Help Required

Former Member — Tue, 03 Apr 2007 13:44:24 GMT

Yes I am using it.

Re: IDOC Help Required

Former Member — Tue, 03 Apr 2007 13:46:29 GMT

Martin,

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

JOhann

Re: IDOC Help Required

Former Member — Tue, 03 Apr 2007 13:53:56 GMT

Does that message appear in WE20.

Re: IDOC Help Required

Former Member — Tue, 03 Apr 2007 14:00:34 GMT

This message appears after I execute the RSNAST00 program.

Re: IDOC Help Required

Former Member — Tue, 03 Apr 2007 14:04:51 GMT

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.

Re: IDOC Help Required

Former Member — Tue, 03 Apr 2007 14:13:30 GMT

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 transaction WE82. 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,

Re: IDOC Help Required

Former Member — Tue, 03 Apr 2007 14:35:29 GMT

I am using a different Output Types in WE20.

Re: IDOC Help Required

Former Member — Tue, 03 Apr 2007 14:42:43 GMT

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

Re: IDOC Help Required

Former Member — Tue, 03 Apr 2007 15:13:11 GMT

Hi,

Here is the deal.

You do not need to create a custom message type ( ZDESADV ). Just assing your extension idoc to standard idoc and standard message type using WE82. 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 EXIT_SAPLV56K_002 ( SMOD enhancement V56K0001 ) to populate custom idoc segments.

Let me know if you have any question.

Regards,

Re: IDOC Help Required

Former Member — Tue, 03 Apr 2007 15:20:35 GMT

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