Distributing message type MATQM using ALE

[roland_spindler]

Hi everybody!

I am using ALE to distribute material data. This already works. Now I also want to distribute material data for quality management.

When I try to distribute materials using BD10 I get this message:

Could not determine recipients for message type MATQM

So I tried to create a new distribution model for MATQM using BD64. Unfortunately I could not choose MATQM or MATQM01 as the message type. (Error: Message type MATQM01 unknown)

However, in transaction WE60 I can display message type MATQM01.

What is the problem?

best regards

Roland

[Former Member]

Create a partners who can recieve the message MATQM in WE20 transaction. That should take out the error message.

Regards,

Ravi

[roland_spindler]

Hi again!

I tried to create partner profiles, but it still doesn't work.

I think the problem is that I couldn't even create a distribution model.

Roland

[abdul_hakim]

HI

you should use the transaction <b>QL11</b><b>for MATQM</b>

Thanks,

Abdul Hakim

[Former Member]

I encountered the below error on adding MATQM in my model.

Message type MATQM belongs to BAPI MatInspectionControl.SaveReplica: Use the BAPI in the model

Message no. BDDISTMODEL077

Diagnosis

You have tried to enter the message type MATQM in the distribution model. This message type belongs to the asynchronous interface of the BAPI MatInspectionControl.SaveReplica.

Procedure

Use the "Add BAPI" button with this BAPI.

Try implementing the solution in the Diagnosis section.

-Kiran

[Former Member]

Hi Roland,

BD10 only can be used with message type MATMAS.

If you want to send message type MATQM and IDoc type, please use this FM <b>MASTERIDOC_CREATE_SMD_MATQM</b>. You still need to maintain partner profile (WE20) and IDoc Port (WE21).

Other you can use <b>Change Pointer</b> (BD21) to send out and ensure you have activated the change pointer for message type MATQM (BD50).

Hope this will help.

Regards,

Ferry Lianto

Please reward points if helpful.

[Former Member]

Hi Roland,

It worked in my system. What was the error message?

For inbound parameter, please use process code BAPI.

Regards,

Ferry Lianto

[roland_spindler]

> you should use the transaction QL11for MATQM

I got the same error message: Could not determine recipients for message type MATQM

> It worked in my system. What was the error message?

> For inbound parameter, please use process code BAPI.

I used process code BAPI. (see above for error message)

[Former Member]

Lets assume the recipient of the message is the logical system LS100.

You need to go to WE20,

Select the node Partner type LS,

Expand the node,

Select the entry for LS100, If the entry does not exist you need to create an entry for LS100.

Next add the message MATQM in the outbound parameters.

Run the transaction QL11 again

-Kiran

*Please reward useful answers

[roland_spindler]

That's exactly what I did. An outbound entry (message type MATQM) exists for the correct logical system, but I still get the error message.

[Former Member]

Use BD64 and add MATQM to your distribution model using BAPI as per my previous message. Use Object BUS1001004 method SAVEREPLICA.

Generate the partner profile using BD64.

Run the program QL11 again.

-Kiran

[roland_spindler]

Hi!

That's what I'm trying to do, but I cannot select MATQM in BD64. Error: "Message type MATQM unknown"

Thanks for your patience.

Roland

[Former Member]

What option r u selecting in BD64. Is it Add message type or Add BAPI?

-Kiran

[roland_spindler]

That's it!

I chose "Add BAPI" instead of "Add message type". Then I selected

Obj.name/Interface: MatInspectionControl

Method: SaveReplica

and it worked!

Thanks Kiran!

(btw, the data is transported along with the material data in BD10 if you select "Send material in full")

[Former Member]

Hi,

<b>This is as simple as that got to BD64 .

1. check whether the distribution model generates partner profile or not.

2. send material thru BD10 and check the status in WE05

3. after checking it got to WE19 for outbound and select the latest idoc and click on outbound.

4. check in the partner system if it is not posted.

5. check in we19 for inbound</b>.