custom message type problem

[Former Member]

Hi Experts,

I was created one Message type ZODNAM_RPM_ITEM in WE81.

And attached basic type MATMAS05 and extension MATMASNA1 to

ZODNAM_RPM_ITEM in WE82.

while iam trying to create IDOC with this message type, it is creating with MATMAS05,

not with ZODNAM_RPM_ITEM.

What might be the reason? Where iam doing wrong??

I need IDOC with ZODNAM_RPM_ITEM message type. What i need to do?

Thanks

Kaki

[Former Member]

while creating partner profiles in we20 you have to specify the extension.

other wise it will trigger standard one.

[former_member194669]

Please check in We20 what will be your message type in the Outbound options tab.

a®

[Former Member]

Hi Vijay,

I got the same doubt.

I mentioned baisc type & extension in the WE20.

Eventhough iam getting standard one. What i need to do still??

[Former Member]

are you filling the extension in IDOC control record, i think SIMTYPE is the field, just check it,

eddidc-simtype = 'ExTEnSION'.

[Former Member]

Hi Vijay,

You are right. I was not filled EDIDC-CIMTYP.

Could you pls let me know how to fill this field?

Everything i mentioned correctly in WE81,WE82 etc etc...

Now IDOC is generationg with error 37(Entry in outbound table not found)...

thanks

[Former Member]

how are you triggering the IDOC, it depends on that. which method you are using. are you using the message control or change pointers or any program.

you need to set the EDIDC-CIMTYP = 'ZEXTENSION'.

[Former Member]

Currently iam doing manually using WE19,

by clicking the button "Standard outbound Processing".

Iam getting information message that

"IDoc 0000000005361030 was saved but cannot or should not be sent"

and getting 37 status....

thanks

[Former Member]

Currently iam doing manually using WE19,

by clicking the button "Standard outbound Processing".

Iam getting information message that

"IDoc 0000000005361030 was saved but cannot or should not be sent"

and getting 37 status....

thanks

[Former Member]

Did you maintain the distribution model using BD64. if not maintain it for the message type , providing the sender and receiver details.

[Former Member]

Hi Vijay,

I got it. Full points alloted.