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

basic type show in WE05 not same as per defined

Former Member
0 Likes
1,465

Hi All,

I have created a customised message type ZMATMAS1, using customised basic type ZMATMAS1 too.

already assigned in WE81 WE82 BD69 & activated in BD50

When idoc generated from BD21, I found that the idoc in WE05 shows the basic type is MATMAS05, why it doesn't follow ZMATMAS1 as I defined ?

Thanks in advanced

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
1,345

Well, the problem is that you cannot just reconfigure the system to utilize a different IDoc type or IDoc extension type. The reason is pretty straightforward: If you want to use a different IDoc type, that means that your IDoc container changed and thus your logic for filling the IDoc must be updated.

In general the function module used for creating the IDoc via change pointers is defined for a given message type in transaction BD60. However, instead of replacing this generic SAP function module with your own creation you should check out the exits available for material master IDocs generated via change pointers. I'd recommend to take a look at customer exit EXIT_SAPLMV01_002, which allows you to define an IDoc extension type and furthermore gives you the chance to fill additional segments that you defined in your IDoc extension type.

Cheers, harald

Hi All,

I have created a customised message type ZMATMAS1, using customised basic type ZMATMAS1 too.

already assigned in WE81 WE82 BD69 & activated in BD50

When idoc generated from BD21, I found that the idoc in WE05 shows the basic type is MATMAS05, why it doesn't follow ZMATMAS1 as I defined ?

Thanks in advanced

6 REPLIES 6
Read only

Former Member
0 Likes
1,345

Check whether the custom message type is assigned to MATMAS05 also.

Regards

Vinod

Read only

Former Member
0 Likes
1,346

Well, the problem is that you cannot just reconfigure the system to utilize a different IDoc type or IDoc extension type. The reason is pretty straightforward: If you want to use a different IDoc type, that means that your IDoc container changed and thus your logic for filling the IDoc must be updated.

In general the function module used for creating the IDoc via change pointers is defined for a given message type in transaction BD60. However, instead of replacing this generic SAP function module with your own creation you should check out the exits available for material master IDocs generated via change pointers. I'd recommend to take a look at customer exit EXIT_SAPLMV01_002, which allows you to define an IDoc extension type and furthermore gives you the chance to fill additional segments that you defined in your IDoc extension type.

Cheers, harald

Read only

0 Likes
1,345

Hi Harald,

Thanks for the reply.

I need to pass only few fields of material master to a non sap system via biztalk

I can't use reduced type of MATMAS bcos some mandatory fields cannot be omitted.

Thus I use this customised ZMATMAS1.

I'm not sure this is the correct method or is there any way have to do on the reduced msg type ?

If using the EXIT as you mentioned, wht shall I do in the EXIT ? chg the IDOC_DATA details ?

Rgds,

Janice

Read only

0 Likes
1,345

Hi Janice,

Create view in WE32 by including desired fileds. Give the view name in WE20 outbound parameters of the receiving system.

--

Reddy

Read only

0 Likes
1,345

Hi Janice,

Sorry, just noticed that I initially read your posting wrong. You have defined a new basic IDoc type and not a new extension type. So my reference to the customer exit is not applicable, because the one I referenced cannot be used to change the basic IDoc type.

Have you taken a look at message type MATCOR with IDoc type MATCOR01 (basically MARA + MAKT)? This might be what you want if you just need some basic material data.

I can't use reduced type of MATMAS bcos some mandatory fields cannot be omitted.

I'm not aware of any mandatory fields. Within IDocs you have a concept of mandatory segments and you cannot remove mandatory segments via IDoc reduction. So for MATMAS05 you cannot remove E1MARAM and E1MAKTM, but other segments you can remove. Thus a reduced message type actually is an option.

Cheers, harald

Read only

Former Member
0 Likes
1,345

Hello,

Did you 'Release' your idoc type and Idoc segments?

This is in we30 in menu Edit> set release and in we31 menu Edit> set release

Best Regards.