IDOC Filter

[Former Member]

Hi All,

I am migrating classification data for batch classification using message type CLFMAS. The standard program to transfer all classification data does not have an option of restricting material + batch.

I created filter in the BD64, it works well if I give the exact match. I have around 20 batches for a material and not all are existing in the target system. I want to avoid creating large no of idocs.

Is there a possibility of filter with a wildcard ...for eg. Filter Object OBJEK = 000000000000010353*

I tried and it does not create any idocs. If I assign OBJEK = 0000000000000103532643A (Material + Batch), it creates one IDOC.

I checked the inbound function module, and it does not have any user exit, for me to validate before creating idocs in receiver system. I ended up creating 40,000 IDOCs, actually posted are just 3000.

Please help.

Thanks and have a nice day.

[Former Member]

Hi All,

I am migrating classification data for batch classification using message type CLFMAS. The standard program to transfer all classification data does not have an option of restricting material + batch.

I created filter in the BD64, it works well if I give the exact match. I have around 20 batches for a material and not all are existing in the target system. I want to avoid creating large no of idocs.

Is there a possibility of filter with a wildcard ...for eg. Filter Object OBJEK = 000000000000010353*

I tried and it does not create any idocs. If I assign OBJEK = 0000000000000103532643A (Material + Batch), it creates one IDOC.

I checked the inbound function module, and it does not have any user exit, for me to validate before creating idocs in receiver system. I ended up creating 40,000 IDOCs, actually posted are just 3000.

Please help.

Thanks and have a nice day.

[Former Member]

You need to find out the User Exit/ Badi at the sender side.

[Former Member]

At our location, we developed a customer ABAP based on the RBDSECLF program that allows us to enter a single or range of vendors/objects to be distributed, and also allowed us to specifiy the receiving target system of the IDOCS. This was something that we needed to do to avoid ALE'ing multiple IDOCS to systems that did not require them.

Hope this helps. Dave