Filter IDOC MATMAS04 by plant

Question

Hi all,
I have configured an idoc in order to send information of materials to an external warehouse. But this warehouse is only from a specific plant, for only one company. When other companies create their materials, my idoc matmas04 is activated anyway, but this material (idoc) must not be send to this external warehouse. Is there a way to filter the activation of change pointers, in order to activate it only for materials of a specific plant?
Is it possible to create a Z FM copying the standard MASTERIDOC_CREATE_SMD_MATMAS, and create a filter here?
Thanks in advance. Reward points to helpful answers.

Answer 1

Hi ,
you need to do create a filter for plant in BD64 ,
You can proceed with following transactions to do so ..............
2.2.2. Maintain object type for message type (BD59) Client independent
The ALE objects are used to create links between IDocs and applications objects, to control the serialisation, to filter messages in the customer model and to use listings.
For our own message type and IDoc you must maintain object types for the links.
If you want to check the serialisation for the message type, then you must maintain object types for the serialisation. If no serialisation object has been maintained for a given message type, then the serialisation will not be checked for this message type.
To add an object type to our message type, follow these next few steps:
• Enter transaction BD59 (ALE -> Extensions -> ALE object maintenance -> Maintain object types)
• Type in your message type ZINVRV and press enter
• Click on New entries
• Enter your object type, LIFNR (We need to use the vendor as a filter object), the segment name where LIFNR resides, Z1INVRV, a number 1 for the sequence followed by the actual field name LIFNR
• Save and exit.
You have now created an object that we’ll use as a filter object in the customer model to direct the flow of messages to the various logical systems based on the vendors in the filter of the message type ZINVRV.
We now need to add our new message type to the distribution model.
2.3. Configuring the Distribution Model
This task is performed on your ALE reference client.
2.3.1. Manual Configuration (BD64) Client dependent
To manually configure the customer distribution model, read the ALE configuration procedure, and follow these steps:
• Perform the Maintain customer distribution model directly function. (ALE -> Distribution customer model -> Maintain customer distribution model directly)
• Specify the customer model you want to maintain and the logical system that is to be the sender of the messages OR create a new model. (Create model ALE with logical system ALELS1C400)
• Choose the receiving systems to which the sending system must forward message type ZINVRV to.
• For each receiving logical system allocate the message type necessary for communication to the receiving systems as per ALE configuration procedure.
• Create filter objects (in our case LIFNR as the object type with the associated vendor number, 0000018001 with leading zeros, in the object area) for the message types.
• Save the entries.