Sending Material by BD10

[Former Member]

Hi,

I am trying to send a material from R3 to XI using the transaction BD10.On executing i get 2 messages:

1. 1 master IDocs set up for message type MATMAS

2. 0 communication IDoc(s) generated for message type

MATMAS.

However, when i send by WE19 , the IDOC is sent sucessfully.

As we19 is successfull, I think that i have done all the ALE settings as well.

Please help.

Thanx.

[former_member214364 · Accepted solution]

Hi Prashant,

Yes You have to maintain

Port to XI from R/3 (TA-WE21)

Partner profiles in R/3 (TA-WE20 ) and

Distribution model in R/3 (TA-BD64)

Cheers,

Jag

[Former Member]

Hi Prashant,

If you are not able to create the "Communication Idoc", then the problem is outbound side only.

Check you distribution model. Before this check your Partner Profile, tRFC port and RFC destination and make sure you are using correct port.

And try with different materials no's range.

Regards,

Naveen

[Former Member]

However, when i send by WE19 , the IDOC is sent sucessfully

--->

Check your partner profile--> outbound parameters

have you selected option Transfer Immediately.

If not then after executing BD10, you will have to go to WE19 to send Idoc manually.

Better use Transfer immediately option so that executing BD10 will trigger IDoc

[Former Member]

Hi

1, The filter in not mandatory

2. The process code in hte partner profile should be MATM so you got ot change that.

Regards,

[prateek]

U may check the following:

1. The filters in the distribution model

2. Check the process codes specified

Regards,

Prateek

[Former Member]

Hi Prateek,

I checked the distribution model.....Under the message type(IDOC) added , the display is "NO FILTER SET".

Do i need to set any filter, if so plz guide me thru dat.

And the process code for Inbound parameter is set as :

"APLI :Inbound IDoc: Individual Processing ".

Do tell me if i need to change dat.

Thanx.

[prateek]

Try using the process code MATM

Regards,

Prateek

[Former Member]

Hi guys,

I changed the process code to matm but however the problem still persists.