topic Re: Idoc type extension in Application Development and Automation Discussions

Idoc type extension

Former Member — Mon, 28 Nov 2011 09:46:39 GMT

Hi Experts ,

I have created an extesnion for standrad message type DEBMAS and Idoc type DEBMAS05 . In devlopment system it is working fine . when transported to other system it is not working and after analsys it is found that EDISYN table has differnt values for differnt systems .Please let me know how can solve this , is any customization need to be mainatined or how it can be done .

Regards

Arun .

Re: Idoc type extension

Former Member — Mon, 28 Nov 2011 10:22:07 GMT

Could you please give more details about the scenario(Inbound Vs Outbound).The required customization is dependant on that.

Kind regards

Manoj

Re: Idoc type extension

Former Member — Mon, 28 Nov 2011 10:33:43 GMT

Hi ,

The scenario is for outbound IDoc . In we 20 it is mainatined correctly as well as we82 i have mainatined correctly.

Regards

Arun

Re: Idoc type extension

Former Member — Mon, 28 Nov 2011 10:40:03 GMT

What is the partner type you are using ,i assume it is KU,if so please cross chek table EDPAR between your test and development system.

Kind regards

Manoj

Re: Idoc type extension

Former Member — Mon, 28 Nov 2011 10:53:39 GMT

Hi,

You have to transport the idoc Extension object to fix this issue. It is not related to customization and it is more of IDOC development related. Try to find out the request under which the idoc extn is saved and retransport the request or include the extn related objects into new request and move it to target system. This should solve your problem.

Cheers,

Prasanna