Material where used list with 200 Class and Object Dependency

[jez_lawson]

Hi Experts,

I am looking at building a where used lookup for component materials on BOMs. The caveat being the materials are tied to a 200 class lookup and to add further complexity I have characteristics within the 200 class being altered via an object dependency in some but not all cases. The plan is to do this via ABAP and in a Z transaction, but have been trying to map out transactionally how it would be done to help the developer.

I was looking at pulling the 200 class from the material and using CSC5 logic to determine all the configurable materials with the class in the BOM. From here using CL30N with the 300 class to determine anything the matches the 200 class characteristics. This fails when an object dependency overrides one of the characteristics within the BOM itself.

I realise that potentially I could explode all the BOM's from the list returned in the CL30N search and compare the results against my initial component, but even one of our smaller 200 lookup classes has 5,000 materials, so I believe the speed of running this way would be prohibitive.

[jez_lawson · Accepted solution]

For anyone interested we eventually decided to use the RESB table to see where the components had actually been used. This excludes 200 class lookups that have never been used, so potential usage of the component, but for our purposes it was sufficient and much faster that trying to resolve all the 200 class lookups.