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

Finding Z idocs triggering points

Former Member
0 Likes
536

Experts,

In my system there are few Z message types and Z basic types .

I wanted to know from which program these IDOCS are getting triggered.

Can you please let me know how to find IDOCS treggering points.

Or is there any transaction to find " Where used list" for Z message types?

Please let me know

Your answers will be appreiated!

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
494

You can find the method used for processing the given message type for inbound idocs.

go to WE57 and enter message type for filtering.

It will list down the functiona module used.

If you further want to test go to we19 enter the basic type ,before this put a breakpoint inside the functiona module selected above.

now click on inbound function module tab , select the function module from F4 and check "call n debugging mode".

This will give an idea how the processing happens.

hope this helps.

Experts,

In my system there are few Z message types and Z basic types .

I wanted to know from which program these IDOCS are getting triggered.

Can you please let me know how to find IDOCS treggering points.

Or is there any transaction to find " Where used list" for Z message types?

Please let me know

Your answers will be appreiated!

2 REPLIES 2
Read only

Former Member
0 Likes
494

Hi Priya

Try this-

From Basic Type, find segments.

Copy these Segments name in SE11 & then use 'Where-used List'.

Regards.

Read only

Former Member
0 Likes
495

You can find the method used for processing the given message type for inbound idocs.

go to WE57 and enter message type for filtering.

It will list down the functiona module used.

If you further want to test go to we19 enter the basic type ,before this put a breakpoint inside the functiona module selected above.

now click on inbound function module tab , select the function module from F4 and check "call n debugging mode".

This will give an idea how the processing happens.

hope this helps.