How do I stop send the IDoc of MATMAS when material has transfaction

[Former Member]

Dear Expert,

I learn and knew how I sent the IDoc of material master that message type is MATMAS from here, and I create one schedule to read the change pointer then send the IDoc of MATMAS.

I meet one issue, I find a lot of IDoc of MATMAS messages are generated and sent but they are not created by my schedule job. When I use SM58 - Transactional RFC, I find the program name of SAPMSSY1. I suppose they are from material transaction level, likes good issue or good receiving. Do I possible stop it? It is created and sent only by my schedule job that read change pointer. If I do, how can I change the configuration or setting? Thank you so much.

[Former Member]

Hi,

In WE20 change you logical system for your message type, check Collect Idocs instead of Transfer IDoc immediately .

Then you just collect idocs in BDCP2 table and your Job will send the IDocs.

Regards

[Former Member]

Hi Jorge,

Thanks for your help.

I change the output mode to "Collect IDocs" method, if I use SAP standard function POIM (RCCLMDAT), it will depend on change pointer to generate IDoc, and it includes function: RSEOUT00 ( and MASS_RSEOUT00 ) to collect and send IDoc.

The collect table is BDCP.

BR,

[former_member1064577]

There is a BADI -> IDOC_CREATION_CHECK serves as a central enhancement point if you want to stop certain type of IDOC generation. You need to implement custom class and then write the logic.

NOTE: This badi can run for multiple message type like MATMAS,CREMAS. So please put a custom check also, custom class only triggers for specific matmas and not others..