We have a custom message type for material master. The partner profile is set up correctly with synch as one of the message types in the outbound parameters. The distribution model is set up fine and has been distributed. All the config is set up and I have debugged the program RBDSEMAT. The communication idoc is not created at all although the master idoc is created. Code works for other partner profiles which have been set up similarly, only diff is that in this message type the config is collect idocs. The program RSEOUT00 does not trigger the idoc either. Any suggestions.
Check out question: "Problem in triggering MATMAS IDOC through BD10 transaction"
Martin Grimm remarks: "I had the same problem with an existing ModelView (BD64) for MATMAS. It turns out that the ModelView EndDate was expired.
You can check that by double-clicking on the ModelViews Name. A window appears where the shorttext and StartDate /EndDate can be modified. If the current date isn't in that timespan, the modelview isn't taken into account and no communication IDoc will be generated."
I solved the same problem by creating a new model view and adding the messagetype MATMAS. This made BD10 work with MATMAS.