topic Re: Standard Message type in Application Development and Automation Discussions

Standard Message type

Former Member — Fri, 04 Jun 2010 05:04:56 GMT

hi ,

i am working on creation of Zshipment idoc , which resembles the same as shipment05 idoc but i have added some zsegments in the custom idoc . My question is whether i can continue using the standard messge type or shall i create an Zmessage type . kindly suggest

regards

Re: Standard Message type

Former Member — Fri, 04 Jun 2010 05:09:33 GMT

I'm not sure why you are creating a new IDOC instead of just extend the standard one? I would suggest you to go with standard message type as long as possible.

Re: Standard Message type

Former Member — Fri, 04 Jun 2010 05:16:59 GMT

Hi amit ,

i am sending ASN using this custom idoc , the standard shpmt05 idoc doesn't support the edi standard of ASN . That is why we went for custom idoc . now my client wants to continue using the standard message type SHPMNT , because it resembles like the standard but what i feel is to go for Zmsg type only . but my client is asking what is the disadvantage is going for an standard msg type . so kindly could you suggest me on this .

regards,

Re: Standard Message type

Former Member — Fri, 04 Jun 2010 06:35:07 GMT

Hi Gurunath ,

i don't think there is any disadvantage of using zmessage type it works same as standard .

one point i want to know what is your reciever system...

Re: Standard Message type

Former Member — Fri, 04 Jun 2010 06:51:46 GMT

Hi ,

I would suggest you to go ahead with zmessage type , it will also give you more flexibility in having user friendly messages.

Regard,

Uma

Re: Standard Message type

Former Member — Fri, 04 Jun 2010 07:11:53 GMT

One message type can be assigned to multiple IDOc types, it can be done by WE82.

So you can still use standard message type for ur custom IDOc type.

Reddy

Re: Standard Message type

Former Member — Fri, 04 Jun 2010 09:27:42 GMT

hi gaurav ,

The idoc is being picked by the XI system and then converted into standard edi ASN format and sent to customer as Xml file .

Regards

Re: Standard Message type

Former Member — Fri, 04 Jun 2010 09:54:37 GMT

Hi Gurunath,

Just create an extension for your basic type SHPMNT05 in the tcode WE30 and just maintain that extension in the WE20 & WE82 transactions. Make sure that your process code populates the extra ZSEGMENTS which you have created. You can do this through some user exits available in the standard process code. After doing this when you generate the IDOC, you can see the Z segments in your IDOC.

Refer the below blog on how to create the extension using WE30 transaction.

/people/jiaxiang.huang/blog/2008/01/14/some-experience-on-idoc-enhancement

~Vaas

Edited by: VaasPal on Jun 4, 2010 11:56 AM

Re: Standard Message type

Former Member — Fri, 04 Jun 2010 11:00:33 GMT

Hi gurunath,

Use Zmessage type it will work absolutely fine . My concern was inbound processing but as u told it is going to XI system so no problem of reciever system also.

revert for further help.