Communication IDoc is not generating after master IDoc for "DEBMAS"

[Former Member]

Hi gurus,

i have done all steps from the beginning to the end for an Idoc transfer of type "DEBMAS".I have created the settings in BD61,BD50 and BD52.And also i can work with other master message types like ARTMAS.I didn't give any filter groups in BD64 for the message type "DEBMAS".When ever i execute BD21(RBDMIDOC) only master idoc is generating,there is no communication idocs for the message type "DEBMAS".Please help someone in this issue.

My special question / doubt is, when ever a master idoc creating ,is it must to create a communication idoc ,if there is no filter in "DEBMAS"?

Please clear someone and explain my doubt.

your help will be highly appreciative...

rgds

tom

Moderator message: Please don't use all upper case in subject line

Edited by: Thomas Zloch on Feb 28, 2010 5:25 PM

[Former Member]

hi,

communication IDoc is missing when ...

- Distribution Modell is missing

- Filter in Distribution Model is existing an no IDoc is generated (Filter at KNA1M segment only)

try the following.

Goto BD12. Choose your partner and the receiving System and send an IDoc.

Is the Comm. IDoc generated ?

if yes ... there is something with your ChangePointer Logik (BD52, .... look at Table BDCP/V)

if no ... you should take a deeper look at BD64 distribution model.

Maybe the receiver partner or filter is not correct.

good luck,

Gordon

Edited by: Gordon Breuer on Feb 25, 2010 1:12 PM

[Former Member]

dear sir,

i had mentioned before,i exactly changed the field of the customer which one i given already in the change pointer.And i activated the change pointer already.That is why master idoc is generating,i think so.Then about the BD64,i didn't give any filter group for this message type.That means for each and every change of a customer master ,i doc must be generated .Isn't it?But unfortunately only master idocs are generating,there is no communication idocs...I hope you got the exact issue...

thanks for your immediate response...

[Former Member]

do you have these problems with DEBMAS only ? or are there any other interfaces with this problems, too ?

Do you have set the "logical system" for the sender system ?

Goto SALE -> logical system -> assign ls to client -> choose client and check the Logical System name .

[Former Member]

ofcourse we are working on it.We have connection between SAP R3 production system and one another WMS production system.We are sending different master idocs like ARTMAS ans CREMAS.There is no problem regarding that two.only with this DEBMAS.I have tried different ways as i can.Please help us...

thanks in advance

[Former Member]

ok, step by step.

1. Do you have entries for your messagetype in Table BDCPV ?

2. IF no ... change a customer data like name or (check fields in BD52).

waiting for your go.

[Former Member]

dear,

we have entries in those two cases.Everything is ok regarding the settigs,but somewhere,something is missing....

pls help us as soon as posible...

thanks in advance

[Former Member]

hi,

years ago, but anyhow. We just recognised the same error using a kind of matmas.

The reason is here that we used the same message type for two different receipients. That should not be a problem in general. But when the material does only fulfil the requirements for one of the receipients, no message is generated. When both are fulfilled, all message are going to be created.

Further analysis is outstanding, but as I could enjoy the comments here to feel not allone in the world, I felt free to add the hint.

Good luck...

[Jeffm42]

Hi Tom or Mary,

Did you check the tcode SM59 entry that's used in tcode BD64. Try a connection test.

regards,

Jeff