Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

problem with custom idoc type

Former Member
0 Likes
729

Hi All,

I have created a custom idoc type in we30 and assigned it to standard message type HRMD_A in we82 and created partner profiles with HRMD_A and custom message type .

Created some custom segment and added that to custom idoc type and trying to fill the additional fields in the custom segment using the enhancement RHALE001 but when i debug i still see message type HRMD_A is still referring to standard idoc type HRMD_A07 .do i need to change the settings anywhere so that HRMD_A refers to custom idoc type

Thanks

Bala Duvvuri

3 REPLIES 3
Read only

Former Member
0 Likes
621

Check out WE81 and WE82

Read only

Former Member
0 Likes
621

Hi,

Did you release the custom segment definition. The released checkbox needs to be ticked .

Regards,

Sugopa

Read only

Former Member
0 Likes
621

I didn't check this properly, so please take this with a grain of salt...

I suspect you're using ALE to create the IDoc/distribute the data. As far as I remember the function module for generating the IDocs simply picks the last IDoc type it finds assigned to HRMD_A (from WE82). For this it evaluates the if an IDoc type is a successor to another one (i.e. you can see this information in WE30, if you look at the IDoc header data). Unfortunately you cannot define a custom successor IDoc for a standard SAP IDoc and the other option of using an extension type also doesn't work (the extension type is not picked up). The IDoc type in the partner profile is ignored as far as I know (didn't doublecheck though to test this).

You could get around this by also defining your own message type and assigning it to your own IDoc type (though you'd then also have to do some further customizing to fix change pointers etc.). Another, more simple alternative should be to overwrite the IDoc type via customer exit EXIT_SAPLRHA0_004. There's possibly other, better ways, this is what I remember (and I don't have the time to search in the system right now).

Cheers, harald