Matmas IDOC in custom progra.

[former_member437950]

Hello Experts,

We have implemented idoc MATMAS05 in our system and it sends data to non-sap system and it works fine with background job 'RBDMIDOC'.

But we have a Z* program where we use statement CALL TRANSACTION MM02 and do many specific changes in sap system. We don't need this changes to be migrate(IDoc).

What we can do to prevent creating IDoc when we use custom program (but we use CALL TRANSACTION MM01/MM02 statement).

[gayathri_jayajeevan2]

Create a IDOC Filter in BD64 for MATMAS. If there is no distinguishing field/filtering object for your scenario, then create a new one in BD59 (new field).

[JonathanEemans]

Hi,

If you include a filter in your distribution model via transaction BD64, only changes according to your filter, are distributed/sent. Thus, it's possible to prevent sending IDocs in this way according to filter criterion/criteria.

Best regards,

Jonathan Eemans

[former_member437950]

Gayathri, thank you for response.

But I can't understand how filtering help me with my issue?