Skip to Content
0
Former Member
Nov 30, 2006 at 10:42 AM

SAP Classification PLM system

131 Views

Hi Folks,

We follow these following steps:

1) Create a characteristic say 'XYZ' and check the 'Required Entry' box (transaction CT04).

2) Create a class and add the previous characteristic to the class material type 001 (transaction CL02).

3) Find a FERT or HALB type material and add it to the 001 class using transaction CL20N. Do not assign any values to the characteristic and click save. Go back and view the material. You should see a status 3 red 'X' next to the class.

4) Go back to the characteristic 'XYZ' and remove the check from the 'Required Entry' box (transaction CT04).

5) Go back to transaction CL20N and view the material. You'll still see the red 'X'. You have to click Save and view the material again to see the status change to 1 green check.

6) Reset all the values and repeat this process with SE37 using BAPI_OBJCL_CHANGE and BAPI_TRANSACTION_COMMIT. You will see that the BAPI_OBJCL_CHANGE will not change the status to 1, because the characteristic values have not been changed. There is an information message returned that states Assignment not changed: message CL738

We need a solution to gather all the materials in the class when there is a change to the 'Required Entry' field and have the BAPI_OBJCL_CHANGE function move the status to 1.

Because as the no. of. materials will be more in the production server, we cannot run the t-code for each material. Is there any t-code where this mass change of all the materials in the class 001 type changes to status 1 - Released.

Regards,

JLN